[SOLVED [not 100% sure how though]] No read /write on second drive

[half_life]

Half_life..... I like you explanation better     I know how to do it, but not the theoretical explanation of how linux looks at the system.   This is why explanations like this one you gave and like the ones Christian usually gives are good.  They explain the reason for something and theoretical knowledge..... not just ( hey... this is how you do it.... follow step 1 thought 5)... HAHAHA  !!!

Thank you.  I spent a few years teaching unix concepts to technicians while I worked for Areva.

[Pat]

hi

sorry for the delay in replying, I went away for the weekend

if I leave this line /dev/sdb1 /main/ vfat user,umask=000 0 0 in fstab to automount the drive on boot then I get the cant mount main error on boot, have to hit S to skip and it will then boot OK, but the old drive which was originally sda1is then changed to sdb1, if I change the fstab to /dev/sda1 /main/ vfat user,umask=000 0 0, and reboot, I still have to hit S to skip and boot, but the drive letters don't change and I can then change fstab back to /dev/sdb1 /main/ vfat user,umask=000 0 0 and mount manually and everything works OK.

once manually mounted if I type mount I get

Code: [Select]

/dev/mapper/server-root on / type ext4 (rw,errors=remount-ro,usrquota,grpquota,acl)
proc on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/sda1 on /boot type ext2 (rw)
/dev/sdb1 on /main type vfat (rw)


My current fstab is

Code: [Select]

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
/dev/mapper/server-root /               ext4    errors=remount-ro,usrquota,grpquota,acl 0       1
#/boot was on /dev/sda1 during installation
UUID=d5045cd7-331a-4cb1-b81c-ad976b7659b9 /boot           ext2    defaults        0       2
/dev/mapper/server-swap_1 none            swap    sw              0       0
/dev/sdb1 /main/ vfat user,umask=000 0 0

[Pat]

AAAAAAAAAAAAAAHHHHHHHHHHHHHHHHHH  !!!!!!!

I have just rebooted to show what mount showed with the fstab showed as above, and its automounted as it should now
:?

Glad it's working but would prefer to know why it did this time and not others