Re: SATA & SCSI
From: Rod Smith (rodsmith_at_rodsbooks.com)
Date: 03/28/04
- Next message: mcubed: "Re: Bare minimum"
- Previous message: Rob: "slide show"
- In reply to: chuck: "SATA & SCSI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 27 Mar 2004 21:15:04 -0500
On Sat, 27 Mar 2004 16:26:54 -0700, chuck wrote:
> I have a ASUS P4P800. Last week my 9gb hda drive flaked out
> on me and Compusa had a deal on a SATA (160/$99) - seemed to
> be a message from somewhere... Any how I installed my new
> SATA. Works fine. But when I connect my scsi drive the system
> won't boot - seems my SATA drive comes up as /dev/sda and
> the scsi drive says "we're here" - both of them as sda.
> Ah... did I just lock myself out from using any scsi drives?
They *SHOULD* work together. The system should see one drive as /dev/sda
and the other as /dev/sdb. That's the way it works for me, with a SCSI Zip
disk as /dev/sda and an SATA hard disk driven via the libata drivers as
/dev/sdb. What makes you think that your system is trying to map both
drives to /dev/sda? (I'm not trying to say you're wrong, just asking for
more information.) A couple of possibilities occur to me to work around
the problem:
1) Use a PATA driver for the SATA controller. I gather that this is
possible with some SATA controllers but not others. Check
http://linuxmafia.com/faq/Hardware/sata.html for more information.
If you're successful, your SATA drive will show up as a /dev/hdx
device (/dev/hda, /dev/hde, or whatever) rather than as /dev/sda.
2) Build your boot device's support into your kernel and load the other
device's support as a module, then load the module after you boot.
With luck this temporal separation of the driver registration will
work around any conflict that exists.
It also occurs to me that your problem might not be one of both drives
trying to be /dev/sda, but of the device filenames of your drives changing
when you add support for the second "SCSI" device. In other words, the
device you'd been identifying as /dev/sda becomes /dev/sdb when you add
the new device. That'll throw off the boot process, and you'll probably
get an error message about the kernel being unable to locate the root
filesystem. (I don't recall the exact wording, though.) If this is what's
happening, changing entries in /etc/fstab and the value you pass to the
kernel as the root device (in your LILO or GRUB configuration) will fix
the problem. Alternatively, option #2, above, should do the trick, as well.
-- Rod Smith, rodsmith@rodsbooks.com http://www.rodsbooks.com Author of books on Linux, FreeBSD, and networking
- Next message: mcubed: "Re: Bare minimum"
- Previous message: Rob: "slide show"
- In reply to: chuck: "SATA & SCSI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
