Post by: bil207 on August 13, 2007, 10:52:12 AM
I looked at the Console log and fount this;
"Can't load /Volumes/MainX//usr/standalone/i386/boot.efi
Error while getting file ID of /Volumes/MainX/System/Library/CoreServices/boot.efi. Ignoring...
Can't load /Volumes/MainX//usr/standalone/i386/boot.efi
Error while getting file ID of /Volumes/MainX/System/Library/CoreServices/boot.efi."
I suspect the power supply is the problem but would like to know if I'm on the right track.
Post by: Dick Miller on August 13, 2007, 11:08:58 AM
Post by: bil207 on August 13, 2007, 11:14:13 AM
Post by: Paddy on August 13, 2007, 04:38:29 PM
http://docs.info.apple.com/article.html?artnum=86760
Post by: bil207 on August 13, 2007, 05:03:46 PM
QUOTE(Paddy @ Aug 13 2007, 05:38 PM) <{POST_SNAPBACK}>
Have you tried resetting the PMU?
Not yet. I'm going to try replacing the PRAM battery (it's about 5 yrs. old) then i"ll also reset the PMU.
I'm hoping to get another 2-3 mos. out of this old QS G4 that I use when I'm here in upstate NY.
I figure on getting a new iMac when Leopard is released but if i can't keep this baby running I might have to adjust my plans.
Post by: chriskleeman on August 13, 2007, 05:43:06 PM
My bet is on the PRAM battery here. 5 years is really pushing it! Most of the time, they should be replaced around 3 years tops.
Hope it works our for you. My MDD is still having power supply issues. I'm ready to get out the shotgun...
Chris K
Post by: Xairbusdriver on August 13, 2007, 05:43:39 PM
Did you run DW and/or TTP from an external boot drive?
Post by: bil207 on August 13, 2007, 06:16:54 PM
I tried doing a restart and the problem is still there,. It took about ten tries to get it to startup.
Post by: kbeartx on August 13, 2007, 06:40:03 PM
QUOTE(bil207 @ Aug 13 2007, 10:52 AM) <{POST_SNAPBACK}>
"Can't load /Volumes/MainX//usr/standalone/i386/boot.efi
Error while getting file ID of /Volumes/MainX/System/Library/CoreServices/boot.efi. Ignoring...
Can't load /Volumes/MainX//usr/standalone/i386/boot.efi
Error while getting file ID of /Volumes/MainX/System/Library/CoreServices/boot.efi."
Error while getting file ID of /Volumes/MainX/System/Library/CoreServices/boot.efi. Ignoring...
Can't load /Volumes/MainX//usr/standalone/i386/boot.efi
Error while getting file ID of /Volumes/MainX/System/Library/CoreServices/boot.efi."
I'm suspicious b/c i386/ is a legacy Windoze directory - what's it doing on your QS?
Post by: chriskleeman on August 13, 2007, 08:49:27 PM
QUOTE(bil207 @ Aug 13 2007, 07:16 PM) <{POST_SNAPBACK}>
Okay, changed the pram battery ($20.63 boy do I love Lake Placid's Radio Shack), reset the pmu, pushed the power button and up she booted on the first try.
I tried doing a restart and the problem is still there,. It took about ten tries to get it to startup.
I tried doing a restart and the problem is still there,. It took about ten tries to get it to startup.
That's no good... try zapping the pram now. Wow, that battery price is pretty steep... I know the pram should have reset when you changed the battery, but in this situation zapping it again might not hurt. Can you do a safe boot?
And Kbeartx might have a point there!
Chris K
Post by: kps on August 13, 2007, 09:32:03 PM
1] your Mac is PPC
2] your Mac uses Open Firmware
Your QS is looking for boot.efi (intel Mac file which is not for OpenFirmware) in usr/standalone/i386/ when it should be looking for bootx in usr/standalone/PPC/
Try resetting open firmware's NVRAM or --reset all parameters.
If this doesn't work, the system files may be corrupted and an Archive and Install may be necessary.
Post by: bil207 on August 13, 2007, 09:41:40 PM
QUOTE
That's no good... try zapping the pram now. Wow, that battery price is pretty steep... I know the pram should have reset when you changed the battery, but in this situation zapping it again might not hurt. Can you do a safe boot?
I tried to zap the pram but after the first chime it shuts down.
Safe boot gives me the same result, also tried starting up from another OS X volume on a second HD and a OS 10.4 install dvd, no joy
Reinstalled OS 10.4, problem remains.
I found this on /usr/standalone/i386/boot.efi.
Post by: chriskleeman on August 13, 2007, 10:35:36 PM
But if you've re-installed the system software, do you still need to look at the NVRAM as kps suggests?
Probably worth a shot at this point? I'm wondering if cleaning and re-seating the RAM modules might be appropriate... when I had a RAM module that didn't want to co-exist with it's buddies I had all kinds of problems like this.
Bill, this can't be any fun.
I hope one or more of the latest suggestions gets your QS back to health.Chris K
Post by: krissel on August 13, 2007, 11:22:26 PM
That boot.efi file apparently is also created when a drive is formatted GUID which is for Intel use. Why your startup is looking for that file is really odd. How are your drives formatted? The external? Have you gone inside and actually checked the physical contacts for all the hardware in your G4?
Karl, can you help him with terminal commands to see if that file is actually there? And what would happen if he reblesses his startup volume via Terminal?
Post by: bil207 on August 14, 2007, 07:24:38 AM
QUOTE(krissel @ Aug 14 2007, 12:22 AM) <{POST_SNAPBACK}>
How did you reinstall 10.4 if you couldn't start up from 10.4 install DVD? Could you give a few more details as to what you have tried. Was the reinstall an archive and install? Have you tried a different user and restarted?
That boot.efi file apparently is also created when a drive is formatted GUID which is for Intel use. Why your startup is looking for that file is really odd. How are your drives formatted? The external? Have you gone inside and actually checked the physical contacts for all the hardware in your G4?
Karl, can you help him with terminal commands to see if that file is actually there? And what would happen if he reblesses his startup volume via Terminal?
That boot.efi file apparently is also created when a drive is formatted GUID which is for Intel use. Why your startup is looking for that file is really odd. How are your drives formatted? The external? Have you gone inside and actually checked the physical contacts for all the hardware in your G4?
Karl, can you help him with terminal commands to see if that file is actually there? And what would happen if he reblesses his startup volume via Terminal?
I can start up from the DVD but only after 8 - 10 times of pressing the power button. Each time that I press power I get the chime, i hear the drives spin up for 1 -2 secs. and the it dies.
The drive is HFS plus formatted.
No external HD, I have two internal drives each one has 10.4.xx on it one with a fresh install of OS 10.4 and the problem exists no matter which drive I select as the startup.
I'm going to check the connections and try re-seating the ram modules even though TT Pro's hardware check reports no problems.
Post by: kps on August 14, 2007, 08:12:30 AM
QUOTE(krissel @ Aug 14 2007, 12:22 AM) <{POST_SNAPBACK}>
Karl, can you help him with terminal commands to see if that file is actually there? And what would happen if he reblesses his startup volume via Terminal?
He can navigate to /usr using the finder through the GO menu. Then look in the 'standalone' directory.
He could rebless OS X through single user mode.
The PPC boot files and a blessed system must be there because the machine eventually boots, so all this may be pointless.
But at this point the issue could be with open firmware, or it's a hardware issue.
If he want to, he can look at 'man bless' and do a little digging first with some info commands to see what is going on:
bless --info /
MY output from a G5 running 10.4.9:
CODE
G5:~ shortname$ bless --info /
finderinfo[0]: 3048 => Blessed System Folder is /System/Library/CoreServices
finderinfo[1]: 0 => No Blessed System File
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 3804202 => OS 9 blessed folder is /System Folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 3048 => OS X blessed folder is /System/Library/CoreServices
64-bit VSDB volume id: 0x1E01446380AE9823
finderinfo[0]: 3048 => Blessed System Folder is /System/Library/CoreServices
finderinfo[1]: 0 => No Blessed System File
finderinfo[2]: 0 => Open-folder linked list empty
finderinfo[3]: 3804202 => OS 9 blessed folder is /System Folder
finderinfo[4]: 0 => Unused field unset
finderinfo[5]: 3048 => OS X blessed folder is /System/Library/CoreServices
64-bit VSDB volume id: 0x1E01446380AE9823
Best to try re-blessing /System/Library/CoreServices from single user mode as root with volumes mounted as per instructions.
Never having to do this, I have no first hand experience with this.
Kris --you must boot the machine first in order to be any user. Switching users is irrelevant, it only applies to login.
Note to Chris: I have a 350 G4 sawtooth with the original PRAM battery still running strong after more than 7 years.
Post by: chriskleeman on August 14, 2007, 09:38:07 AM
QUOTE
Note to Chris: I have a 350 G4 sawtooth with the original PRAM battery still running strong after more than 7 years.
Your battery is the exception, not the rule IMHO...
From Maclife forums
QUOTE
Pram batteries can last from 1 to 3 years. My experience, as a former Mac repair tech, is that unless it is known to be good, a new pram battery is the first step to troubleshooting any mal-functioning older Macs. Basically if you dont remember clearly installing a new pram battery in the last 2 years or so buy a new one.
Dead or dieing prams can produce random and unpredictable behavior.
Dead or dieing prams can produce random and unpredictable behavior.
Other folks recommend 3-5 years. My personal experience has been 3-4 years tops in all my Mac's.
Thought it was a good place to start, as many of these kind of problems are can easily be PRAM battery or faulty RAM induced sometimes...
And sometimes, trouble can come in multiples! I just hope your computer isn't dying Bill. Do you have a good voltmeter? I'm sure I can come up with power specs for your power supply if you can or want to test the connection points on the mother board.
Chris K
Post by: kps on August 14, 2007, 10:17:24 AM
PRAM batteries will usually give signs of failing. Sporadic boot issues, strange system dates, etc.
Bill, if you can't zap the PRAM, which you indicated earlier, I'd reset NVRAM through OpenFirmware first.
some good info here:
http://www.bombich.com/mactips/openfirmware.html
Full directions here:
http://docs.info.apple.com/article.html?artnum=42642
Have you tried "option" + boot on the secondary or with the DVD/CD boot disk in the drive?
If none of this resolves the issue, I'd look at hardware as the cause.
Why? Because you changed the battery, reinstalled the system, the machine won't boot properly from the secondary HD containing a blessed system or from the DVD/CD.
Post by: chriskleeman on August 14, 2007, 10:50:52 AM
No offense taken! We're all scratching our heads here, me more than anyone else!
I just want to send you a fresh PRAM Battery!
I got an extra one in April! 
Chris K
Post by: kps on August 14, 2007, 02:31:40 PM
Post by: bil207 on August 14, 2007, 02:52:13 PM
I haven't had a chance to try restting the NVRAM but will try next time that I have to restart.
Post by: krissel on August 14, 2007, 10:18:33 PM
QUOTE(kps @ Aug 14 2007, 09:12 AM) <{POST_SNAPBACK}>
Kris --you must boot the machine first in order to be any user. Switching users is irrelevant, it only applies to login.
Yup, I just thought if he managed to get it to start up at some point he could try that. The additional info that he has two fresh installs makes the suggestion rather useless.
If resetting the NVRAM doesn't work check all the hardware including trying a different power cord. I once had startup problems with my old 9600 and changing the power cord solved it.
Post by: bil207 on August 15, 2007, 08:37:32 AM
QUOTE(krissel @ Aug 14 2007, 11:18 PM) <{POST_SNAPBACK}>
QUOTE(kps @ Aug 14 2007, 09:12 AM) <{POST_SNAPBACK}>
Kris --you must boot the machine first in order to be any user. Switching users is irrelevant, it only applies to login.
Yup, I just thought if he managed to get it to start up at some point he could try that. The additional info that he has two fresh installs makes the suggestion rather useless.
If resetting the NVRAM doesn't work check all the hardware including trying a different power cord. I once had startup problems with my old 9600 and changing the power cord solved it.
The curios thing is once it's up and running everything is fine, go into deep sleep and wakes with no problem.
If I can keep it up and running until after Labor Day when I go back to Long Island I'll be fine.
Post by: krissel on August 16, 2007, 12:29:15 AM
Now just pray you don't have a power outage.