X3250 Server: stuck at firmware screen

The server is initialize, then it is stuck at the IBM System X Server Firmware screen (before F1, F12 appears, etc).
I load default setting in bios after that it is stuck firmware screen. No error light in hardware indicator.
Thanks

Sean,
Yes, I did get it solved. I just haven't had a chance to post back.
It was a permissions issue. The 'Everyone' permissions for the start up drive had gotten changed to 'No Access' somehow. I had to start up with the install disk, then open up Terminal and change the permission back to 'Read' and then run disk utility.
There is a thread here that gave me the exact command line command to use... but I'm sorry that I don't have it to link. Do a search on this forum and it should show up.
Alan

Similar Messages

Yosemite Server stuck at boot screen

Hello,
we have/had a Mac Mini Server running. He is administered via screen-sharing. We encountered problems with LDAP / Open Directory and I was trying to unload a launched configuration via:
sudo launchctl unload /System/Library/LaunchDaemons/org.openldap.slapd.plist
when the screen-sharing session was interrupted. I had to shut down the server pressing the on/off button and connected him to a monitor in order to find out what went wrong.
Now he gets stuck at half the progress bar of the apple boot screen.
Starting in single user mode I can:
1) $ /sbin/fsck -fy
and get: "The volume ... Appears to be ok
The Volume was modified."
and:
2) $ /sbin/mount -uw /
after
exit
I get out:
Bootcachecontrol: Unable to open /var/db/Bootcache.playlist: no such file or directory
pfctl: the use of -f option, could result in flushing of rules present in main ruleset added by the system at startup.
See /etc/pf.config for further details.
no ALTQ support in kernel
ALTQ related functions disabled
pf enabled
net.inet.tcp.delayed_ack: 3 -> 2
bash: /etc/rc.installer_cleanup: No such file or directory.
In Verbose i get:
** /dev/rdisk0s2 (NO WRITE)
** Root file system
Executing fsck_hfs (version hfs-285)
Warning: couldn't block sleep during cache update
Warning: proceeding w/o DiskArb
rebuilding //System/Library/Caches/com.apple.kext.caches/Startup/kernelcache
/dev/disk0s2 on / (hfs, local, journaled)
BootCacheControl: Unable rot open /var/db/BootCache.playlist: 2 No such file or directory
pfctl: Use of -f option, could result in flushing of rules
present in the main ruleset added by the system at startup.
See /etc/pf.conf for further details.
No ALTQ support in kernel
ALTQ related functions disabled
pf enabled
net.inet.tcp.delayed_ack: 3 -> 2
kern.maxfiles: 12288 -> 120000
bash: /etc/rc.installer_cleanup: No such file or directory
We have only Server running on the machine, but it would be nice to save the configuration somehow.
1) Is there a way to repair the system from command line?
2) Can I simply copy the missing files from another system (kernelcache, Bootcache...)?
3) Can I install Yosemite from the recovery partition and keep the server installation?
I hope someone can help...

The Apple Support told me to turn off the computer, then turn it on again, then press and hold "Option + Command + P + R" until de relaunch song play for the second time, then release it..... it worked here for me.... hope to help you too !!!

Mac OS X Server: Stuck on grey screen

I installed a Mac OS Server 10.5.4 onto Mac Pro Duo core workstation it has 2GB RAM. I'm using this machine as a storage machine for video. I have a Lacie Big Drive firewire and 5big Network hard drive. I disconnected the drives. I ran a disk utilities to repair permission then reboot. I used Energy Saver Schedule to reboot the machine once a week, and I notice it was reindex the whole time. It tried to reboot, but it got stuck during the boot up and I see grey Apple with spinning dial. I tried to do a cold boot three times and no luck. Also I tried safe which I don't fully understand it or succeeded in being that mode. I'm a novice at Mac OS X server.
Does anyone have any solution?
Thanks
Luis
Message was edited by: Luis Casale

I have not follow this method. I install the simple version of installation and setup groups, users. Since, I did not have the time do to any maintenance and spotlight was trying to reindexing, we had tons of videos files. Before grey went to grey screen, Spotlight was trying to re-indexing. I went ahead to schedule a restart once a week on Saturday. I found the machine with the grey screen and I waited for for two hours. I decide to try cold boot, didn't work and I even tried the started up disk. No luck! I been searching online for answers. Thank you for responding. I'm new on the server side. Don't have any one else who is an expert on Mac Server.
Thanks
Luis

Snow Leopard Server - Stuck at Welcome Screen

Hi Guys,
I have a Mac Mini on which I have just installed SL server 10.6. After reboot it sits on the Welcome Screen with buttons greyed out. I have seen this article : http://discussions.apple.com/message.jspa?messageID=10236544 as a resolution but what don't understand is how to log into the machine remotely if I have not given it an IP address or configured any services in SA?

Check your system date. Make sure its set to after the build date of the OS build.
The security stuff in the OS gets cranky when the system date is earlier than the
signatures on the signed binaries.
If you can get to the system log look for messages like:
servermgrd: createSelfSignedIdentity: Failed, SecAccessCreate returned -2147409653
Using the security tool to explain the error reveals:
security error -2147409653
Error: 0x8001210B -2147409653 CSSMERRTP_CERT_NOT_VALIDYET
HTH
- Leland

Server stuck on gray screen with spinning circle after software update 10.5

I'm not sure what I need to do to resolve. I'm knew to administering Apple servers and am doing the 'on the job training' thing. Step by step instructions would be MUCH APPRECIATED!!! Please help! Michele

Thanks for the suggestion, unfortunately it didn't work for me. I had our resident mac expert come in and assist me, it appears that mach_kernel didn't get an upgrade, also appears that it was crashing on directory services. He tried several things to resolve but was unsuccessful. His recommendation was to reinstall to OS. He did say it was nothing I did, it is a very basic server with no third party software installed. He believes it was something with the 10.5.4 software update, and recommended staying away from the software updates, if they aren't critical or security related. So... I'm currently reinstalling the OS, fortunately; I did have it backedup.

Ipod Touch Stuck On iTunes Screen. The iPod 'iPod' cannot be restored at this time because the ipod software update server could not be contacted or is temporarily unavailable.

I got a new ipod touch for Christmas.
Today I was going to put music on it, i was told there was updates.
So I went ahead to do them.
My Ipod is stuck on the screen with the usb cord pointing to the itunes logo.
In Itunes i'm told :
Itunes has dected an ipod in recovery mode. You must restore this ipod before it can be used with itunes.
Turning the ipod off - the same screen appears when it's back on.
When I click restore ipod and after restore and update is clicked ; Extracting software loads up at the top.
When its done this is the message I get:
The iPod 'iPod' cannot be restored at this time because the ipod software update server could not be contacted or is temporarily unavailable.
I've been looking up trying to figure it out myself and have read making sure a setting in Lan Settings in Internet Properties has ; Automatically detect settings checked. I still get the same ipod message.
I've tried holding the power and home key to turn it off, then powering it back on. But that doesn't work.
I installed itunes today, so its up to date - I checked.
I don't know what else to do.
Can someone help me out, please? :}
The operating system was ios 5 something? It wanted to update to 6 i believe.

I've tried the top part but now that i've looked to the bottom:
Additional Information
The “hosts” file may also be blocking gs.apple.com.
Select the hosts file (normally you can find your hosts file at C:\WINDOWS\SYSTEM32\DRIVERS\ETC).
I put this in the url bar?
When it gives me the list of names, im not sure what to do from there. The steps aren't that clear for me.

Need urgent help on Sawtooth stucked at Open Firmware screen

Hello.
I've got a G4 Graphite Sawtooth Powermac running a Newertech MaxPower 2.0MHZ processor upgrade for about 3 years. It is running Leopard (10.5.8) system.
I've also installed a Seritek 1S2 card with a 500GB Sata disk.
Some days ago I've started to notice that sometimes when I did Log Off or Shut down the Mac cleaned all the desktop icons but then nothing happens.
Also, it started to freeze sometimes doing some tasks like open apps or working on Photoshop.
Today the Mac refused to boot on the main system disk (I have a secondary 80GB disk with Tigger installed on it).
Then I ran TechTool Pro Disck scan and it gave me an error on scanning the main disk.
I've booted into the Tiger disk (a 80GB one) and think to myself if this could be something to do with the Seriteck card or driver, or something related to it...
I've loaded the Seritek install CD and click the install firmware of the Seriteck disk, then I've booted and... it stucked on Open Firmware forever.
It is on the welcome screen of the open firmware and I can't do anything.
It says" To continue booting, type "mac-boot" and press return", but I can't type anything because it looks freezed. My keyboard don't respond.
I've tryed the firmware boot (that one with the long beep pressing the programmer button) at no avail.
I'm desesperate. I'm a freelancer and I've goot importante work to deliver to clients and I can't get my Mac to to boot into the system.
At this point I just want to boot normally into Tiger, Leopard, whatever.
I just need to boot and recover my works.
See screenshot of Open Firmware screen here:
http://img19.imageshack.us/i/dscn3061q.jpg/
Can someone please help?
Thank you for your time,
Macjaime

I ran TechTool Pro Disk scan and it gave me an error on scanning the main disk.
If you did a "Surface Scan", and not a "Volume Structures Repair", it is telling you there is a Bad Block on the Hard Drive.
There are two cases: It could be temporary, or it could be permanent. There are two sub-cases of each: It could be important or it could be unimportant.
When you run the test, and it tells you the Surface Scan has detected an error, you are supposed to ask it figure out what file is involved, and write it down. Then you can decide whether to delete that file and replace it with a good copy.
Bad blocks may mean your drive will not be working properly in six months, if you continue to use it full time. It could also die this afternoon -- no one knows. If you can re-initialize with Zero all Data (one pass) the drive will substitute some of its stash of spare blocks for any that remain bad after the zeroing. But of course all your data will be lost, and it takes a few hours to complete.
Some readers suggest that a drive that has had spare blocks substituted may last a long time at light duty, such as making an occasional backup.
The only article that comes up with a search for "default catch" has to do with drives that are really wacked out. It suggests you back up everything and re-initialize the drive.

Tried to install OS X on my G4 and it is now stuck on Open Firmware screen

I have a powermac g4, with dual 450 processors. Bought in 2000 - After buying a brand new G5 last year I recently tried to install my OS X Tiger I got with the G5 onto the G4. Initially it all booted up fine. However when I turned it back on instead of booting up it made a long tone and then went to an Open Firmware screen with the prompts to type ‘shut-down’ or ‘reset-all’
Neither prompt works and this happens every time I turn it on. I have tried holding ‘c’ with original CD I got with the G4 to bring it back, I have tried holding ‘c’ with the OS X cd, I have tried to re-set Pram by holding down the appropriate keys but nothing works it just always makes the long tone noise and goes to the Open Firmware screen.
I have also been informed about updating the Frimware -i now have the software on a CD but cannot get the system back to be able to do this
Can anyone help me bring the G4 back to life?
G4 Powermac Have a G5 too

Hi
You could order the Full Retail Version of OS X (Black DVD with a silver X on it). Regarding always starting up in Open Firmware, in this thread a bloke had the same problem until he disconnected his peripherals before restarting. See if the entire thread helps:
http://www.macworld.com/forums/ubbthreads/showflat.php?Cat=&Board=UBB13&Number=2 43591&Main=243591
Steve

VM Server stuck in "Error" state - cannot start or stop any VMs

I have Oracle VM Server 3.0.2, VM Manager 3.0.2, and have a VM server stuck in an "Error" state. I've gone into all the Event tabs for the server + guests and acknowledged all the errors, but it's still in this state.
When I try to start a VM for example, I get this error on screen (I've obfuscated the server names):
OVMRU_005007E Virtual Machine: <vmname>, cannot be started/resumed on Server: <servername>. Reasons:
Server: <servername>, is in error
AdminServer-diagnostic.log reports:
[2012-03-23T16:58:05.078+13:00] [AdminServer] [ERROR] [] [com.oracle.ovm.mgr.faces.model.EO] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 87aae679e5ee7e1d:-14aa5e4e:1363307a070:-8000-000000000000eb79,0] [APP: ovm_console] Programming error![[
java.lang.NoSuchMethodException: com.oracle.ovm.mgr.api.collectable.ManagedObjectHandleImpl.getUser()
at java.lang.Class.getMethod(Class.java:1605)
at com.oracle.ovm.mgr.faces.model.EO.invokeStringAccessor(EO.java:551)
at com.oracle.ovm.mgr.faces.model.EO.invokeStringAccessor(EO.java:1124)
at com.oracle.ovm.mgr.faces.model.JobEO.getUsername(JobEO.java:608)
at com.oracle.ovm.mgr.faces.backing.task.TaskFilter.isAssociatedUser(TaskFilter.java:216)
at com.oracle.ovm.mgr.faces.backing.task.TaskFilter.isAssociatedWith(TaskFilter.java:241)
at com.oracle.ovm.mgr.faces.model.collection.EOList.isAssociatedWith(EOList.java:239)
at com.oracle.ovm.mgr.faces.model.collection.EventSupport.handleInsert(EventSupport.java:60)
at com.oracle.ovm.mgr.faces.model.collection.EOList.handleInsert(EOList.java:211)
at sun.reflect.GeneratedMethodAccessor1446.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.oracle.ovm.mgr.faces.model.ChangeSupport.fireChangeEvent(ChangeSupport.java:127)
at com.oracle.ovm.mgr.faces.model.ChangeSupport.fireInsert(ChangeSupport.java:66)
at com.oracle.ovm.mgr.faces.model.DataProvider$EventListener.fireInsert(DataProvider.java:312)
at com.oracle.ovm.mgr.faces.model.DataProvider$EventListener.timerExpired(DataProvider.java:284)
at weblogic.timers.internal.commonj.ListenerWrap.timerExpired(ListenerWrap.java:37)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Nothing gets written to AdminServer.log
Any ideas?

Hi Mannyabdon,
Based on your description, I recommend to check the things below:
1. Run the PowerShell command below to check the status of the Secure Store Service:
Get-SPServiceInstance |Where {$_.typename -like "Document Conversions Load Balancer Service"}
If it is not showing online, please stop the service first and then start it to see if the issue still occurs (the
<ServiceGUID> can be obtained obtained from the command above).
Stop the service:
Stop-SPServiceInstance -Identity <ServiceGUID>
Start the service:
Start-SPServiceInstance -Identity <ServiceGUID>
2. Check the ULS log for detailed error message.
For SharePoint 2013, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.
Thanks,
Victoria
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

HT1338 i cant get in to os system. the screen just stuck in white screen and apple logo

i can not get in to my os system. the screen just stuck in white screen and apple logo

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Step 3
Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is damaged and the drive is probably malfunctioning. In that case, go to step 5.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 4
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 5
Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
Step 6
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 7
Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a backup.
Step 8
A dead logic-board battery in a Mac Pro can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions.
Step 9
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested.

Imac 8,1 does not boot stuck on blue screen

imac8,1 mid (2008) 20" stuck on blue screen after boot ,It starts in safemode, below is a list of thing i have check so far
1 Apple hardware test (says every thing is ok)
2 Disk utility repair (was successfull)
3 reset PRAM ,SMC
3 Boot for OSX dvd and reinstalled (still only starts in safe mode )
4 boot in single user mode and used fsck ( said every thing was ok)
Yet when i boot i get stuck on a grey/blue screen . it starts in safe mode though, Is there some EFI , firmware restore file that i can install ???
What else can it try????

Please closely follow Apple's advice in Gray screen appears during startup. There are a number of steps to take, be methodical and follow the directions closely.

MacBook Pro stuck at grey screen after Yosemite upgrade

upgraded to yosemite yesterday. Reboot and stuck at grey screen(login in page) when i log in there is some codes thing at the left top corner of the screen. and then it reboots again. Which means I can never log onto the computer. what should I do

If you can't start up and log in in the usual way, try in safe mode.
During startup, you’ll see a progress bar, and then the login screen, which appears even if you normally log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Log in as an administrator to carry out these instructions. If you have only one account, you are the administrator.
☞ If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
Safe mode is slower than normal, and some things won’t work at all.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t start in safe mode.
If you're able to log in, launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
In the Console window, select
DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report.

Macbook pro retina 2012 mid year stuck on grey screen

Hi everyone.
I've just update for the lastest mac os x mountain lion update, when half way the progress and it goes stucked. All the function are unable to function, so i've force shut it down. After mac shutted down and i tried to boots it back it stuck on grey screen which below apple logo forever loading icon. i've tried Reset the PRAM, but it still not working for me. Also, i tried when when start up hold with cmd + r to reinstall the os x , but it just won't let me to reinstall it , it wrote you can't upgrade this version of OS X because a newer version is installed?
Help please! need a solution that wont delete all my files at the same time

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
a. Boot into the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Step 3
Boot in safe mode. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 5.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 4
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 5
Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.
Step 6
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 7
Repeat Step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
Step 8
This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. Both desktop and portable Macs used to have such a battery. The logic-board battery is separate from the main battery of a portable. A dead logic-board battery can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 9
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested. If you can't get to an Apple Store, go to another authorized service provider.

The charging display is stuck on my screen

The charging display is stuck on my screen and it won't do anything! I can't turn it on or off or anything else. What should I do?
Dell Windows XP Pro

Are you by any chance using iTunes 7.0.2 and firmware version 1.2?
If you are then I would surmise that you are the victim of a bug in the firmware (if you look at the forum there are thousands of people with the same issue)
Unfortunately for us users Apple appear to be burying their head in the sand on this one because there has been no official recognition of the problem, meanwhile people are continuing to download the firmware, oblivious to the fact that this will render their precious and much loved iPods completely useless.
This is clearly a completely cynical policy by Apple because they know that publicly admitting the problem would seriously harm their sales in the busy Christmas period.......POOR SHOW APPLE!!! THIS WILL HARM YOU MUCH MORE IN THE LONG TERM.
Fear not though, they will not be able to hide it for long because I know that the BBC are investigating this.

2008R2 RD Termimnal Server stuck at apply computer settings over an hour

Hi Everyone
I am currently experience issue with my 2008R2 RD Terminal Servers. Every time I reboot the server it stuck in the "Apply computer settings" screen for few hours. These RD Terminal server is part of our NLB cluster. User connect to the
RD terminal Servers via FQDN for the NLB cluster VIP . Each servers has dual network adaptor. The second network adaptor is link to a NLB cluster. If one of the servers stuck in the "Apply computer settings
screen" Open NLB manger from one of the RD Terminal server, NLB manager will end up not responding.
I have found a way to allow me to login to the problematic RD terminal server by disabling the network on the network adaptor of the vm. This allow me to login. Then I quickly re enable the network on the adaptor. Users complained when
they log in to that server stuck at "Apply computer settings" screen
We do have GPO policy apply to these terminal servers I have moved one of the RD Terminal server to another OU with minimum policy that makes no different.
Appreciate any advice
Thanks

I have managed to resolve the issue by going into safe mode and disable windows management instrumentation service after reboot I am able to login . remove VMware tools. restart the server. apply computer setting disappear. almost like something is conflicting
with VMware tools

X3250 Server: stuck at firmware screen

Similar Messages

Maybe you are looking for