
Update #4
Arghhhh! The screen locked up again and that annoying multi-languange message popped up telling me I had to shut down my computer by holding down the power button. It booted up okay but this message keeps popping up after an hour or so of use. I wonder if there is some bad RAM here after all?
How do I test it?
Update #3
This sure has been a learning day - but it's ending successfully.
Downloaded the DiskWarrior 3.0.1 update, burned it to a CD and though it wouldn't boot directly to the G5, I put it in the G4 laptop and FireWired the laptop to the G5 and ran DW again and .... voila!
It succcessfully repaired the G5 drive directories and... nine hours after this odyssey began... all seems fixed.
Thanks to all... The full record of all this - for those who will experience similar problems - is in the extended entry below.
Bottomline: I still don't know how the hard drive became corrupted and why I was getting the panic kernel crash. Stuff happens, I guess. But DiskWarrior is a terrific tool. Just make sure you get the latest version.
-update 2-
Another failure... rebooted...okay again. Applecare had me run disk repair from the OS X startup' and it showed unrepairable errors.
The tech said only solution was a total reload and reformat - which would wipe the drive clean.
That is not a good solution.
On his suggestion, I tried Disk Warrior.
It seems to be hung up.
Sigh.
It now says Disk Warrior successfully built a new directory but "the new directory cannot replace the original directory due to a Mac OS services failure."
Now how on earth am I suppossed to know what that means?
-update #1-
Could it really be this simple?
Following instructions in the comments, I opened the case up and looked at the RAM.
I pulled the modules out and swapped them around and then reseated them. When I rebooted...it suddenly worked again!
Could it be that RAM was somehow not properly seated? As I recall, it appeared to me that one of the locking tabs on one of the modules may not have been all the way in the locked and up position. I think. I wasn't paying attention to that at the time, instead wondering what bank I should test first.
But I noted in reseating the RAM modules that they really need to be firmly depressed to snap those tabs shut.
At any rate, it now seems to be working. I'll see how it does the rest of the day.
Gulp. That was scary.
That'll teach me from boasting about my uncrashable Mac.
It crashed.
Big time.
I was on the Net, updating this blog, when the screen dimmed and a message popped up saying I had to push the power button to shut down and restart. After that... a serious kernel failure, roardiong fans on the G5 and a bunch of code in black and white on the screen ending in the phrase:
"panic: We are hanging here..."
I'll say we are. I can't get the CD open to boot from Panther's install disks and none of the standard emergency start-up tricks seem to work - like zapping the pram or resetting the firmware.
This is serious-update #1-
Could it really be this simple?
Following instructions in the comments, I opened the case up and looked at the RAM.
I pulled the modules out and swapped them around and then reseated them. When I rebooted...it suddenly worked again!
Could it be that RAM was somehow not properly seated? As I recall, it appeared to me that one of the locking tabs on one of the modules may not have been all the way in the locked and up position. I think. I wasn't paying attention to that at the time, instead wondering what bank I should test first.
But I noted in reseating the RAM modules that they really need to be firmly depressed to snap those tabs shut.
At any rate, it now seems to be working. I'll see how it does the rest of the day.
Gulp. That was scary.
Also remove any third-party ram installed in the machine. That causes odd problems sometimes.
Posted by: Adam at February 15, 2004 01:34 PMIt's original Apple RAM... have tried unplugging everything.
Can't get Superdrive open to run Disk Warrior.
Still remove the RAM they added when you bought it-- leave base in-- Apple RAM is as succeptible as anyone else's to failure. If no go, swap the base for the added RAM.
Posted by: toeknee at February 15, 2004 01:46 PMAnd I assume you've tried calling Applecare?
Posted by: toeknee at February 15, 2004 01:52 PMYou can open the drawer by using a paper clip. If you push down the front piece, there's a small hole on the left side of the drive. Pushing the paperclip in there should pop it open a little -- you can then open with your fingers.
I don't think this is a problem with your drive, though, Mike: you wouldn't typically get a panic. It really sounds like a driver issue (I suppose it could be memory, but it seems unlikely).
Did you try booting up in "Safe Mode" (hold Shift down through tbe boot process)? Any PCI/PCI-X cards in there?
Posted by: Dave Nanian at February 15, 2004 02:12 PMThe other thing, and sorry if you've tried this: you can usually get the drive to open by holding down the mouse button through the boot sequence. As I recall, the CD is controlled by Open Firmware, and will eject.
There's a way to do it with Open Firmware as well: I'm researching this and will re-post when I figure it out.
Posted by: Dave Nanian at February 15, 2004 02:16 PMFound it, Mike: this should work without a paper clip.
1. Restart the computer.
2. Immediately after the startup sound, press and hold the key combination Command-Option-O-F.
3. Release the keys when you see a white screen that says "Welcome to Open Firmware."
4. At the prompt, type: eject cd
5. Press Return, then wait a few seconds. The disc drive should eject any disc that is present, and "ok" appears behind your command when the action is complete.
6. Type: mac-boot
7. Press Return.
Your computer should now start up normally.
Posted by: Dave Nanian at February 15, 2004 02:18 PMYou may be aware of this Apple support doc, but just in case you are not:
http://docs.info.apple.com/article.html?artnum=106464
Good luck.
Posted by: Gary L. Gray at February 15, 2004 02:31 PMYeah -- the problem with that article is that it's assuming he can get through the boot sequence even to Single User mode. Unfortunately, it sounds like it's hanging right during the initial boot & kernel driver load...
Posted by: Dave Nanian at February 15, 2004 02:46 PMCool... working again. Now I can stop refreshing this page!
Good luck, Mike!
Posted by: Dave Nanian at February 15, 2004 02:47 PMGlad to hear the good news! You had me worried, and now I can go back to plotting out how to get my hands on my own G5.
Posted by: Mickey at February 15, 2004 03:56 PMMike: the problem might be that the copy of Disk Warrior you're running is the "old" one: 3.0. I believe 3.0.1 fixes the problem you're running into...
It could also be that you're booted from the drive you're trying to check.
Of course, if you don't have 3.0.1, you can't boot a G5. But, if you have some other machine that can be booted with DW 3, you can mount the G5 with "firewire target disk mode" and check the drive that way...
Posted by: Dave Nanian at February 15, 2004 04:38 PMOh yeah. Been there witjh DW... I ran it from my G4 laptop FireWired to the G5 and ran it twice... got the same message "the new directory cannot replace the original directory due to a Mac OS services failure."
Man... this reminds me a lot of those old frustrating Windows days.
Is this with DW 3.0.1?
Posted by: Dave Nanian at February 15, 2004 05:30 PMWell, the good news Mike, is that once you get your system up, you can restore from backup.
Posted by: Annoyed at February 15, 2004 05:56 PMI would suggest trying Micromat's TechTool Pro 4.0.1. The testing modules with this product will test for both hardware issues as well as directory and file structure problems.
Posted by: ctolgc at February 15, 2004 06:58 PMWhat stuns me is there is no way to repair this... no way short of erasing everythging that I have painstakingly built over months.
At least with Windows XP, there was a system resore point.
This is horrible.
It will take the better part of two days to do this.
But they system crashes all the time... Disk Warrior and OS X's disk repair are useless.
This is scandalous it is so bad.
Mike,
I've never had a crash this bad, that I couldn't recover from. If you have a second hard drive around you could boot from that without reformatting your current drive. I suspect you may have a bad Hard Drive.
Mike Kaylor
Mike,
Why not just reinstall the OS using archive and install? If it is a software issue, this should be successful. If there is directory damage, Disk Warrior or TechTool Pro might help before reformatting the hard drive.
Posted by: ctolgc at February 15, 2004 07:59 PMIts a directory issue and Disk Warrior says it can't repair...
Posted by: Mike Wendland at February 15, 2004 08:00 PMDiskWarrior 3.01 won't boot from the G5 either when I hold down C and restart
Posted by: Mike Wendland at February 15, 2004 08:37 PMYeah, the "burnable" disk warrior won't boot the G5, because it doesn't have the updated OS on it. But, as you saw, you can still do the FW trick.
If you call AlSoft, you can place an order for a DW 3.0.1 disk that'll boot the G5. Unfortunately, it'll cost another $20 or so... might not be worth it as long as you've got the G4 Powerbook around!
Glad you're fixed, Mike. Nasty!
BTW, the System Restore points would not have corrected this problem on XP, since it only rolls back certain types of driver installs and registry changes, and doesn't do a very good job at that... I've lost untold amounts of data under XP, even with rigorous backups, but never anything under OS X... fortunately.
Anyway, congrats again on getting things working, and I'm sorry it was such a pain.
Posted by: Dave Nanian at February 15, 2004 09:04 PMThanks to everyone who offered suggestions.
The key was booting DW on the laptop, connecting it via Firewire to the desktop, and running the latest 3.0.1 verseion for the G5.
Mike,
Glad everything finally is in order. I would like to publicly thank Dave Nanian of
for his excellent utility SuperDuper!, and for the tremendous customer support he provides with this product.
Thanks Dave!
Posted by: ctolgc at February 15, 2004 09:18 PMWhat a way to spend your Birthday Mike! Glad your up & running again. No Mac jokes, not on your Birthday :-)
Posted by: Geek at February 15, 2004 10:02 PMYou're off my more than a week, geek.
It was 2/8
Thanks for the wishes anyway :-)
Mike, isn't your system under warranty? Might be time to call Apple.
Posted by: Kent at February 15, 2004 10:33 PMTo test for bad RAM, boot off the OS DVD that came with your G5 while pressing the Option key. After a while, you will see boot choices (including the session that has Hardware Test in it). Choose Hardware Test. Then, choose the long test. Your G5 will go through the entire test phase for around 40-50 minutes and the fans will go at full speed (you'll be surprised at how loud the G5 can get!). The Memory test will take the longest (depending on how much RAM you will have).
I've purchased my extra RAM from Crucial. It's the same RAM Apple used for my G5 and so far, I haven't had any problems.
BTW, to get the Superdrive open when booting, press the mouse key while you boot.
Good luck!
Have you run the Apple Hardware Test?
That generally finds problems with RAM in my experience.
Guess I should've posted that faster. :)
Posted by: Adam at February 15, 2004 11:01 PMI have no idea what it does, but I've heard that doing the PRAM reset does miracles.
Sorry I can't help more than that.
Thomas
Posted by: Mx at February 16, 2004 12:12 AMAgree with MGO on hardware test procedure, would only add you need to run full RAM test several times sometimes to find bad RAM-- which explains why the computer can run fine for a while before futzing out. But without a doubt, EVERY OS X problem that involved these types of errors I have come upon has turned out to be bad RAM. Not saying it couldn't be something else, but when you said your computer was affected pre-boot and would not boot from CD, I had major doubts it was either software or hard drive-- most likely RAM or motherboard, in my estimation.
T
Posted by: toeknee at February 16, 2004 01:15 AMIt's inexcusable that high end computers like the G5 don't come with error correcting memory, even as an option. That technology has been around for around 30 years and adds only a modest amount to the cost of a machine. If the problem you're having is a memory problem (and I agree that this is likely) error correcting memory would have found it immediately and very likely turned it into a mild warning about failing memory that you could deal with at your leisure. The really scary thing is that memory errors can sometimes go undetected and just cause incorrect results. In a way you're lucky that it caused your machine to crash so at least you know something is wrong.
Posted by: Mike Alexander at February 16, 2004 02:11 AMNot a great thing to wake up to this morning, Mike: sorry that things are still going wrong.
OK, first we need to figure out what's going wrong. That horrific screen is a "Kernel Panic", the most dreaded of all (non-disk) crashes. In pre-Jaguar versions of OSX, you ended up with a scary screen of numbers that sort of told you what's going on, but were nearly impossible to copy down properly.
Since Jaguar, OS X writes a file that MAY help determine the problem.
Once you get the machine booted again, snag the file "/Library/Logs/panic.log". There will likely be a record of all your crashes in there: send it to me via email and I'll see if there's anything in there that points to the problem.
Posted by: Dave Nanian at February 16, 2004 08:17 AM(BTW, thanks "ctolgc" -- I appreciate the mention, though I'm not sure this is the place!)
Posted by: Dave Nanian at February 16, 2004 08:23 AMI bought Warrior for the panic kernal message I was getting on my imac. I iput the disk in my computer and the panic message still came up when booting from the Warrior disk. Has anyone run into this problem or know why it could be happening?
thanks
m
I have a g5 here at my work and the HD took a crap on me after it being opened 3 weeks ago!!! These drives run mad hot and now I am trying everything to get the drive to even get recognized. Man, G5?
Posted by: Brian at April 20, 2004 02:48 PMDear Sir/Madam,
Recently I reformat my XP m/c dues to the Trojan Ghost virus, after reformated the hard drive there number of problems, the keyboard just frozen, even using the word document the m/c frozen.
Secondly, windows come out information on the screen saying hardware was not installed, software was not installed etc, after that I cann't even turn off the computer accept reset it.
Please advise me what should I do next.
Thank you for attending to my problem.
Regards,
Euguene Tan
Hmmmmm interesting !!!
Posted by: dzwonki polifoniczne at June 11, 2004 08:32 PM
Mike --
Unplug all of the devices you've got plugged into FW and USB other than the keyboard and mouse. It's possible that a device is doing something wacky, and confusing the kernel.
Make sure to power all of those devices completely off (unplug any external power supplies).
Reboot and see if it boots up. If it does, plug the devices in one at a time to see if any cause a failure. If not... be happy...
Posted by: Dave Nanian at February 15, 2004 01:22 PM