From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Description of problem: Hi All, I am using White Box Enterprise Linux 4 (WBEL 4). My system runs off an LSI SATA-4 RAID controller. I also have an Adaptec 2047600, SATAConnect 1205SA controller that is used with my backup SATA hot swap drives (cheaper and faster than digital tape). Under WBEL 3, the SATA drive was treated as an IDE drive (/dev/hda). Under WBEL 4, it is now a SCSI drive. When the removable backup SATA drive is not installed, WBEL maps the RAID drive as /dev/sda. When the removable SATA drive is installed, it gets mapped as /dev/sda and the RAID drive gets bumped to /dev/sdb. Then whoever is responsible for /etc/fstab at boot goes through and fixes the drive mapping (except the swap partition, which it misses and I will post under another bug). This is a total pain in the neck. SATA drives are not SCSI drives. Please map them in the same manner as you did under WBEL 3. Many thanks, --Tony Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. please see description 2. 3. Additional info:
use filesystem labels or udev rules for a symlink... indeed SATA is now recognized as SCSI...
Dude! Shall we start calling floppy drives CD-ROM drives? Shall we call SAS drives ATA drives? (S)ATA drives are not SCSI drives. Thne technology is vastly different. You should only call drives that are connected to SCSI adapters or adapters that present themselves as SCSI adapters as SCSI drives. (This would cover SATA drives in RAID controllers that support both SAS and SATA). This is indeed a bug. Please fix. I(f you still disagree with me, please as a senior technican with hardware experience for help. --Tony
I agree, that (S)ATA drives are not SCSI drives. Your solution would be to use filesystem labels or rename (or better symlink) your drives with udev rules. For a discussion of why SATA drives are mapped in the SCSI driver layer, I'll reassign this bug to the component "kernel"