SCSI Problem

[Drew Lane]

>> Those would be times when the drive at ID 0 (for whatever reason) 
>> does manage to be scanned by the Linux kernel during the SCSI 
>> initialization process, and therefore ID 0 ends up as sda and ID 1 as 
>> sdb.  The no init found kernel panic means that the kernel could not 
>> find the init binary (init is the first process started) on the 
>> specified root FS.
>

I think you're dead on target.  Just need to figure out the reason.

> Any ideas?  Could this be a SCSI termination issue? 

> Possibly... how's your chain terminated?  It could also be a drive 
> that is somewhat slow to respond after a SCSI bus reset and doesn't 
> always get caught by the bus scan.  What kind of a drive is it? 

I'm sure the drive at ID 0 is very slow; it's the original Mac 1GB drive.
It's main purpose is to load BootX, so I can get to Linux.
Not sure about the speed.  One of those quantum fireball thingys.

The drive at ID 1 is fairly new.  It's a Western Digital 9.1 GB 7200 RPM 
Ultra 2
(with a 80 pin to 50 pin adapater, I might add)

As I recall, I've got it setup so that the drive at ID 0 is the last one 
on the chain
becuase that was the easiest way to arrange the internal scsi cable.

Maybe I should try rearranging the order?

BTW, the drive at ID 0 is just terminated with the jumper on the drive. 
 (I think!)

> (Ya wanna buy a drive?  :)  I've got three 9.2 GB Cheetah 18XL drives 
> (~35 MB/s, ~5ms seek) that got decommissioned a while back when I got 
> a 15K RPM drive, and I haven't found a use for them since, so I guess 
> it's time to find a new home for them...) 

Maybe, but the 9GB I just put in there was only $25.00

Shoot, I'm not sure if the SCSI bus on this old Mac can go more than 10 
MB/s anyways.

Drew