[hadocon]

I just installed Panther on the slave 120GB HDD on my girlfriends Quicksilver DP800. After the install I changed the jumpers so that the 120 would be the new master and the original 80GB drive would be the slave. When I first rebooted I kept getting kernel panics saying that I did not have the right kernel for my unknown system (to paraphrase) - I at least have the machine booting off the 120GB drive now, but the slave 80GB drive is not mounting at all. When I use Disk Utility I can see that the computer knows that the slave is there, and I even have the option to mount it - when I click the mount button nothing happens. No beachball or anything.

When I try to "Repair Disk" I get this:

Repairing disk for “Bebblebrox”
Checking HFS Plus volume.
Checking Extents Overflow file.
Volume check failed.

Error: The underlying task reported failure on exit (-9972)

Repair attempted on 1 volume
0 HFS volumes repaired
1 volume could not be repaired

When I tried to install Panther on the original 80GB drive the installer would not let me. I just got an error message saying that the installation could not be performed. I never installed the most recent HD update - I guess I'll try that now...

My girlfriend is going to get pretty pissed if I can't figure this out. Does anyone have any Ideas?

[Spliffdaddy]

I'm thinking that the master/slave relationship of ATA drives on a single (ATA66 or better using 80-pin cable) channel is determined not by jumper placement, but by the drive's location on the cable. Black header is master and grey header is slave (blue connects to motherboard).

The jumpers on the drives should be set to the drive's corresponding cable location - master or slave.

In some cases, the jumpers must be set to 'cable select' instead of master/slave. I don't know if this is ever the case with Macs, though. But if all else fails it's worth a try.

[hadocon]

Originally posted by Spliffdaddy:
I'm thinking that the master/slave relationship of ATA drives on a single (ATA66 or better using 80-pin cable) channel is determined not by jumper placement, but by the drive's location on the cable. Black header is master and grey header is slave (blue connects to motherboard).

The jumpers on the drives should be set to the drive's corresponding cable location - master or slave.

In some cases, the jumpers must be set to 'cable select' instead of master/slave. I don't know if this is ever the case with Macs, though. But if all else fails it's worth a try.

I read the jumper settings page for WD drives and it says that order on the ribbon has no effect, unless you configure for 'cable select' - which I did not do. According to the page everything is determined by the jumpers.

[ReggieX]

Spliffy's on the right track: the Master/Slave relationship on Macs is determined by the cable position.

Why did you change the jumpers if they were both working correctly in the first place?

[hadocon]

Originally posted by ReggieX:
Spliffy's on the right track: the Master/Slave relationship on Macs is determined by the cable position.

Why did you change the jumpers if they were both working correctly in the first place?

I wanted to change my boot drive from the old 80GB to the newer 120GB drive. I switched the jumpers only and now my 120GB drive reports as disk0 and the 80GB drive is disk1.

[ReggieX]

You didn't have to change the jumpers, it doesn't matter if the boot drive is slave or master on the IDE chain. Switch 'em back to how you had them and you should be good to go, unless you want to physically change their position in the case.