1111 Views 10 Replies Latest reply: May 31, 2007 11:46 AM by MGW
Welcome to Discussions Sandy - have you tried booting from the install disc? Or in safe mode?
Safe Boot is a special way to start Mac OS X 10.2 or later when troubleshooting. Safe Mode is the state Mac OS X is in after a Safe Boot.
Starting up into Safe Mode does three things to simplify the startup and operation of your computer:
* It forces a directory check of the startup volume.
* It loads only required kernel extensions (some of the items in /System/Library/Extensions).
* In Mac OS X 10.3.9 or earlier, it runs only Apple-installed startup items (some of the items in /Library/StartupItems and /System/Library/StartupItems - and different than login items).
* Mac OS X 10.4 Tiger only: It disables all fonts other than those in /System/Library/Fonts .
* Mac OS X 10.4 Tiger only: It moves to the Trash all font caches normally stored in /Library/Caches/com.apple.ATS/(uid)/ , where (uid) is a user ID number such as 501.
* Mac OS X 10.4 Tiger only: It disables all startup items and any Login Items.
Taken together, these changes can work around issues caused by software or directory damage on the startup volume.
Some features don't work in Safe Mode
Safe Mode can be useful for troubleshooting. However, certain Mac OS X features do not work when you are started up in Safe Mode. For example, you can't use DVD Player, capture video in iMovie, use an AirPort card, use audio input or output devices, or use an internal or external USB modem.
Thanks Miriam, I think I have tried that. I have and can start from the "c" original disk and when I run the disk utility all is okay - it doesn't need any repairs. I've started holding down the "s" - is that the safe mode you speak of? If so, it get's hung up just before opening to the desktop page. See description on original to what appears on the screen. Still having no success.
Starting in safe mode:
1. Be sure the computer is shut down.
2. Press the power button.
3. Immediately after you hear the startup tone, press and hold the Shift key.
Tip: The Shift key should be held as soon as possible after the startup tone but not before.
4. Release the Shift key when you see the gray Apple and progress indicator (looks like a spinning gear).
Also, when you booted from your install disc, could you then choose your HD and start normally?
You may find this recent article from MacFixit helpful:
iMac G5: Fails to startup
Some users are reporting an issue where iMac G5s fail to properly startup -- apparently at a hardware level -- never reaching the Mac OS X startup splash screen (Apple logo with a spinning progress indicator).
[Note that in cases where the system does reach the Mac OS X startup splash screen or further progression but stalls, software issues may be to blame.]
Disconnect external devices External devices -- especially those that draw power from the system -- can cause issues with startup that manifest either at the beginning of or later in the boot process. Try temporarily any external FireWire or USB devices then re-attempt startup and check for persistence of the issue.
Reset SMU Although this workaround was not successful in Connors' case, resetting the iMac G5's SMU (system management unit) as described in Apple Knowledge Base article #301733 can resolve a variety of power-related problems, including sudden-onset startup failure.
Check power cables Check your power cord for a loose connection. As noted in the aforementioned reader case, unplugging and re-plugging the power cord can sometimes result in a successful startup -- likely the result of a more snug fit.
Also, power cables can become defective or ship in such a state. Try exchanging the power cable from a problematic machine with a system that starts up properly to eliminate this as a potential cause.
Sandy, you are the OP = Original Poster and what I meant was that your problem is likely to be a software one according to Apple's definition (
[Note that in cases where the system does reach the Mac OS X startup splash screen or further progression but stalls, software issues may be to blame.]), which is what I suspected all along.