SATA SCSI Id assignments - two drives being assigned the same Channel/Id/Lun on boot

Claude Jones claude_jones at levitjames.com
Thu Nov 2 12:53:23 UTC 2006


In the thread "mount doesn't mount on boot-up" we have found a 
problem with the way my SATA drives are being ID'd, as seen below.

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3160023AS      Rev: 3.05
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3300622AS      Rev: 3.AA
  Type:   Direct-Access                    ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 01 Lun: 00
  Vendor: ATA      Model: WDC WD5000YS-01M Rev: 07.0
  Type:   Direct-Access                    ANSI SCSI revision: 05

The first two entries appear to have the same Channel/Id/Lun - 
the problem I'm having has to do with my third drive not being mounted 
at boot. My fstab looks like this:

LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot1            /boot                   ext2    defaults        1 2
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
LABEL=/home             /home                   ext3    defaults        1 2
proc                    /proc                   proc    defaults        0 0
sysfs                   /sys                    sysfs   defaults        0 0
LABEL=SWAP-sda2         swap                    swap    defaults        0 0
/dev/sdc1		/home/cj/archive	ext3	defaults	1 2

This results in this error in my system log while booting:

Nov  2 00:37:04 localhost kernel: audit(1162445820.853:6): avc:  denied  { mounton } for  pid=2338 comm="mount" name="archive" dev=sdb1 ino=65175554 scontext=system_u:system_r:mount_t:s0 tcontext=user_u:object_r:user_home_t:s0 tclass=dir
Nov  2 00:37:04 localhost kernel: audit(1162445820.853:7): avc:  denied  { mounton } for  pid=2338 comm="mount" name="archive" dev=sdb1 ino=65175554 scontext=system_u:system_r:mount_t:s0 tcontext=user_u:object_r:user_home_t:s0 tclass=dir

The last line in my fstab relating to sdc1 is the issue - when I boot, 
the process is trying to mount sdb1 instead, for a second time, since 
that drive is already mounted by the 5th line in my fstab which starts with 
LABEL=/home

Has anyone else encountered this? Guess I'm going to head over
to bugzilla and see if there are any reports of this, but, I'm wondering
if there's something I could have misconfigured that's causing this. 

-- 
Claude Jones
Brunswick, MD, USA




More information about the users mailing list