Unusual fstab with eSATA cabled HD

[billcarson]

I have a functioning triple boot (XP, SuSE(KDE) and Ubuntu(Gnome) on an eSATA cabled external HD – connected to a SiImage RAID controller (hardware on the ASUS motherboard) . I didn’t need the RAID as such so I set up this HD as a JBOD using the SiI utility during boot up process.

My FSTAB’s are as follows:

openSuSE 10.2 (KDE) – FSTAB

/dev/mapper/sil_ahagdhdcdbicd_part6 / ext3 acl,user_xattr 1 1 (SuSE)
/dev/mapper/sil_ahagdhdcdbicd_part5 /boot ext3 acl,user_xattr 1 2
/dev/mapper/sil_ahagdhdcdbicd_part7 /home ext3 acl,user_xattr 1 2
/dev/mapper/sil_ahagdhdcdbicd_part3 Swap ext3 defaults 0 0

proc /proc pro defaults 0 0
sysfs /sys syfs noauto 0 0
debugfs /sys/kernel/debug usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/fd0 /media/floppy auto noauto,user,syn 0 0

______________________________________-


Ubuntu FF -FSTAB

/dev/sda1 UUID=xxxx /media/XPSATAVault vfat (WinXP)
defaults,utf8,unmask=007,gid=46 0 1
/dev/sda2 UUID=xxxx /media/UbuntuFF ext 3 (UbuntuFF)
user, auto, dev, exec, rw.,errors=remount-ro 0 1
/dev/sda3 UUID=xxxx none swap sw 0 0

dev/sda5 UUID=xxxx /media/SuSE_BootDirectory ext3 user, auto, dev, exec, rw. 0 2

dev/sda6 UUID=xxxxx /media/openSuSE 10.2 ext 3 ( OpenSuSE)
user, auto, dev, exec, rw.,utf8,unmask=007,gid=46 0 1

/dev/sda7 UUID=xxxx /media/Suse_Home_Directory ext user, auto, dev, exec, rw., utf8,unmask=007,gid=46 0 1

/dev/hda /media/cdrom0 udf,iso9660, user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

My question is this:

1/ Why are these so different. Does Ubuntu (GNOME) use mdadm as opposed to DM Raid?
2/ The Ubuntu distro lets me see every partition on the this HD and all the others as well on the LAN; the SuSE (KDE) doesn’t. I have tried to alter the mount options on the SuSE (KDE) fstab away from the acl_user, xattrib, but the system won’t boot up without it? Placing ‘defaults’ in the SuSE fstab also doesn’t work.

Help

Thanks in advance.

[billcarson]

Well, I took some advice and added DMRAID to Ubuntu !

Now the partitions on this single HD which contain both Ubuntu FF and Suse 10.2 match up. Specifically, with these commands:

ls /dev/mapper/*
and
dmraid -r

Also, of note:
lsmod | grep sil
sata_sil 30472 1
libata 145568 2 sata_nv,sata_sil

Interestingly, the “df -hT” command result differs:
SUSE 10.2
Filesystem Type Size Used Avail Use% Mounted on
udev tmpfs 503M 188K 502M 1% /dev
/dev/mapper/sil_ahagdhdcbicd_part7 ext3 22G 463M 20G 3% /home

Ubuntu FF:
Filesystem Type Size Used Avail Use% Mounted on
varrun tmpfs 506M 224K 506M 1% /var/run
varlock tmpfs 506M 0 506M 0% /var/lock
procbususb usbfs 506M 180K 506M 1% /proc/bus/usb
udev tmpfs 506M 180K 506M 1% /dev
devshm tmpfs 506M 0 506M 0% /dev/shm
lrm tmpfs 506M 33M 473M 7% /lib/modules/2.6.20-16-generic/volatile
/dev/sdd7 ext3 22G 464M 20G 3% /media/SuSE_Home_Direct

This may be a minor issue. But what I really don't understand is that my /etc/fstab has not changed since I added DMRAID to Ubuntu. In fact, this is the first time I noticed the “#” sign in front of all the devices !!

# /dev/sda1 UUID=1C41-4496 /media/XPSATAVault vfat defaults,utf8,umask=007,gid=46 0 1

# /dev/sda2 UUID=69b59949-dcf3-4f05-a7c6-fb740805200c /media/UBUNTU_FeistyFawn ext3 defaults,errors=remount-ro 0 1
# /dev/sda3 UUID=521cb38f-28f3-46da-97d6-6e77605f4c22 none swap sw 0 0
# /dev/sda5 UUID=ff1f4241-e319-4b21-a76f-e0a07132384e /media/Suse_BootDirectory ext3 defaults 0 2
# /dev/sda6 UUID=463D-D7DD /media/openSuSE10.2 ext3 defaults,utf8,umask=007,gid=46 0 1
# /dev/sda7 UUID=A0506BEC506BC81C /media/SuSE_Home_Directory ext3 defaults,users,umask=0,auto,nls=utf8,umask=007,gid =46 0 1
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0


Wouldn't you think that there would be at least some /dev/mapper/sil_xxxx lines in the new fstab?


Thanks. BC