Some serious system problems.

hazmat

hazmat

Rusher of Din
I had been having off issues here and there with my system, so since I had a second drive in the system (2 60-gig drives), I switched master and slave and completely wiped the second drive and did a clean 10.2 install. Things have been going fine since, but all of a sudden yesterday I got a kernel panic. Since then , reboots more often than not will sit on "Waiting for local disks". With a verbose boot it will keep on repeating that until I do a reboot. After a few reboots it will boot fine and everything works fine. If I boot to a bootable OS 9 CD with DiskWarrior on it, it won't see the new master at all, only the original disk, which is now the slave. Anyone know what is going on here? I can't figure out if it's having a problem with the slave disk, the boot disk (which it's obviously booting to no problem), or something other than that.

Thanks for any help on the matter.
 
About the DiskWarrior CD thing: sounds like you formatted the drive with OS X and forgot to check "Install OS 9 drivers" on the disk. Any kind of OS 9 application or system won't be able to see drives formatted ONLY for OS X.
 
Originally posted by ElDiabloConCaca
About the DiskWarrior CD thing: sounds like you formatted the drive with OS X and forgot to check "Install OS 9 drivers" on the disk. Any kind of OS 9 application or system won't be able to see drives formatted ONLY for OS X.
Click to expand...

Ah, I see. I had the OS X install wipe the drive during install. The fact that the CD wasn't seeing the disk wasn't worrying me since I figured it was some issue with OS 9 not seeing it.

Can I install OS 9 drivers after the fact?
 
Hmmm... you could boot off the OS X install CD, open the disk utility from the menu bar (I think this is the right place), select your drive, and see if the option to install OS 9 drivers is there...
 
Ah, good point. I'll try that tonight. I'm also thinking of pulling the IDE cable from the slave drive to see how it affects my booting. When I hold down Option during boot and select the slave drive (former boot drive/master), it gives me the same issues I have been having with it, which DiskWarrior said were too much to repair. Nice. :)
 
I'll soon have approx. the same equipment as you : 2 disks (20Gb/60Gb) and no need of kernel panic ;).

- Partition your internal HD 2Gb OS9 / rest OSX (apps/system)
- Other disk OSX + OS9 drivers - :) - (data)
 
Master vs Slave not really important to booting choices. Switching this designation has no effect on startup choices, and maybe nanoseconds in data access speed. It's like lights in your house wiring; where they are in the circuit has no effect on when you use them. Concentrate your efforts on what's on the drives and if they function as needed.
 
Toast: How do I get the OS 9 drivers on the second drive which only has OS X on it?

modelamac: Thanks for that. I'm used to PCs where master/slave definitely matters.

For all: I booted to the 10.2 install disc and ran the repair but it said the disc was OK. I ran it on the old boot disk and I got the same problems, so I guess the disk is genuinely screwed. Since this IBM is so loud compared to the Maxtor that came in the Mac, I might, once I know everything is fine, wipe the Maxtor and get everything from the IBM over to it and use that as the boot disc again. Assuming the physical disk is fine.

But either way, for some reason now it's booting fine. I tried a bunch of times and it boots successfully. Very odd. Not sure if the disc repair from the CD did anything, but that's all I have done since I think.

Thanks for all the feedback.
 
You must log in or register to reply here.
Back
Top