Now Playing
AVForums Super Veteran
I'm getting some really strange mounting behaviour on my microserver running ubuntu server 10.10 and housing squeezeboxserver and my music library. I've moved/ added no disks since initial configuration and not modified the config either.
/etc/fstab specifies mounting the 5 drives in the system as follows:
/dev/sda1 /diskpool/d1 ext4 user,noatime,noexec,nodev 0 0
/dev/sdb1 /diskpool/d2 ext4 user,noatime,noexec,nodev 0 0
/dev/sdc1 /diskpool/d3 ext4 user,noatime,noexec,nodev 0 0
/dev/sdd1 /diskpool/d4 ext4 user,noatime,noexec,nodev 0 0
/dev/sde1 /diskpool/d5 ext4 user,noatime,noexec,nodev 0 0
yet sometimes (like right now) it fires up and loads the drives in a different order (which I'm guessing means the physical drives are being seen in a different sequence). Running mount I get:
/dev/sda1 on /diskpool/d1 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sdb1 on /diskpool/d2 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sdc1 on /diskpool/d3 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sdd1 on /diskpool/d4 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sde1 on /diskpool/d5 type ext4 (rw,noexec,nosuid,nodev,noatime)
which is what I'd expect to see, howver, looking at the contents of /diskpool/d1 I'm seeing what I know is actually on /sdb1 and should be appearing under /diskpool/d2 etc. This has happened on two occasions recently and the upshot is squeezeboxserver is completely confused as it cannot find its own DB.
I'm guessing referring to devices by UUID would resolve this, but I'm curious, has anyone else encountered this behaviour?
/etc/fstab specifies mounting the 5 drives in the system as follows:
/dev/sda1 /diskpool/d1 ext4 user,noatime,noexec,nodev 0 0
/dev/sdb1 /diskpool/d2 ext4 user,noatime,noexec,nodev 0 0
/dev/sdc1 /diskpool/d3 ext4 user,noatime,noexec,nodev 0 0
/dev/sdd1 /diskpool/d4 ext4 user,noatime,noexec,nodev 0 0
/dev/sde1 /diskpool/d5 ext4 user,noatime,noexec,nodev 0 0
yet sometimes (like right now) it fires up and loads the drives in a different order (which I'm guessing means the physical drives are being seen in a different sequence). Running mount I get:
/dev/sda1 on /diskpool/d1 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sdb1 on /diskpool/d2 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sdc1 on /diskpool/d3 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sdd1 on /diskpool/d4 type ext4 (rw,noexec,nosuid,nodev,noatime)
/dev/sde1 on /diskpool/d5 type ext4 (rw,noexec,nosuid,nodev,noatime)
which is what I'd expect to see, howver, looking at the contents of /diskpool/d1 I'm seeing what I know is actually on /sdb1 and should be appearing under /diskpool/d2 etc. This has happened on two occasions recently and the upshot is squeezeboxserver is completely confused as it cannot find its own DB.
I'm guessing referring to devices by UUID would resolve this, but I'm curious, has anyone else encountered this behaviour?
