I just tried something that failed.  I have been running my Dell
server with SATA disks on its dual-channel controller.  They are seen
as /dev/sda and /dev/sdb.  I also have a disk on USB, seen as
/dev/sdd.

The root partition (containing /boot) is on /dev/sda2, known to GRUB as hd(0,1).

I also have a SCSI controller, to which is attached a DDS2 tape drive.

[EMAIL PROTECTED] scsi]$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 05 Lun: 00
 Vendor: ARCHIVE  Model: Python 28388-XXX Rev: 5.AC
 Type:   Sequential-Access                ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 00
 Vendor: ATA      Model: Maxtor 6Y160P0   Rev: YAR4
 Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
 Vendor: ATA      Model: Maxtor 6Y200P0   Rev: YAR4
 Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
 Vendor: ST312002 Model: 6A               Rev: 3.06
 Type:   Direct-Access                    ANSI SCSI revision: 02

Here you can see the tape drive on scsi0 ID 05
The SATA drives on scsi1 and scsi2
The USB drive on scsi4

If I now try to attach a real SCSI drive to the same host adapter as
the tape drive, it seems to be assigned to /dev/sda at boot time, and
of course the system doesn't boot because that drive doesn't have
anything bootable on it.

So my question of the day is "how are /dev/sd? names assigned to
hardware devices, and how can I change this so the SATA drives are
assigned first".  I have not yet tried powering up the SCSI drives
after the system has booted, to see if they get "hotplug" mounted the
way that USB drives do.

I also have not tried looking at the BIOS view of the system with the
SCSI drives powered on.  I only looked at the Host Adapter BIOS to
verify that it saw them.  Maybe it's time for another system shutdown.
Makes it hard to read email, but I do have at least one other
computer.  :-)

   carl
--
   carl lowenstein         marine physical lab     u.c. san diego
                                                [EMAIL PROTECTED]


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to