OK, this is a bit of a weird one...and a bit long so please make yourself a cup of coffee first...

I have a 600MHz Snow G3 iMac running 10.2.8. Yesterday I was trying to track down a file on the system drive and couldn't find it. It wasn't on any of my backups so I decided, as a last resort, that I'd use the scavenge option in DiskWarrior 2.1 (which works with Jaguar, but veeerrry slowly). No such luck, but while running DW it found a few directory errors and I decided to rebuild...

...bad move. When I restarted, I was immediately greeted with a kernel panic. And the following saga began...

1) Restarted again....panic
2) Pulled all USB devices out except mouse and keyboard....panic
3) Zapped PRAM (5 times)...panic
4) Booted DW CD again and rebuilt...rebooted...panic
5) Booted from iBook running Panther via target disk mode just to check that it wasn't some kind of motherboard failure....started OK 6) Braced myself for a reinstall of the OS and prepared to boot into OS9 to do one last backup (to catch anything not backed up since the last run of Retrospect 6 days ago) 7) Restarted machine having forgotten to switch startup disks....machine tried booting into Jaguar....booted OK!

So somewhere between steps 5) and 7) the disk repaired itself and I carried on using the machine, having restarted a few times just to check, for the rest of the day.

Today I decided to record some stuff off the radio for burning onto CD for a car journey tomorrow, using ???. This used to crash the iMac occasionally but since upgrading OSX to 10.2.8 has been OK. Not today...machine locked solid and I had to hold the power key down to restart...

...back to the kernel panic again....gawd!!!

This time I also tried starting in single user mode and got:

"Recording startup extensions
Error: Extension archive has a bad checksum
Error: Couldn't unpack multi-extension archive
panic(cpu0): Unable to find driver for this platform (PowerMac 4.1)"

followed by a stack tracedump. Googling this error came up with many tales of woe and plenty of potential causes but nothing in the way of someone who had this error but managed to fix it.

What does everyone think? Two difficult issues that have resulted in the same panic (I've seen panics before, but never on boot-up), or an indication that the drive might be on its way out?

Meanwhile, I'm going through the above procedure again to see if the machine comes back to life.

Neil

--
The iMac List is sponsored by <http://lowendmac.com/> and...

Small Dog Electronics    http://www.smalldog.com  | Refurbished Drives |
- Epson Stylus Color 580 Printers - new at $69    |  & CDRWs on Sale!  |

     Support Low End Mac <http://lowendmac.com/lists/support.html>

iMac List info:         <http://lowendmac.com/imac/list.shtml>
 --> AOL users, remove "mailto:";
Send list messages to:  <mailto:[email protected]>
To unsubscribe, email:  <mailto:[EMAIL PROTECTED]>
For digest mode, email: <mailto:[EMAIL PROTECTED]>
Subscription questions: <mailto:[EMAIL PROTECTED]>
Archive: <http://www.mail-archive.com/imac-list%40mail.maclaunch.com/>


---------------------------------------------------------------
iPod Accessories for Less
at 1-800-iPOD.COM
Fast Delivery, Low Price, Good Deal
www.1800ipod.com
---------------------------------------------------------------

Reply via email to