Boot mount errors - partitions busy or already mounted

Hello,

Here goes my 1st post on the new site. :slight_smile:

I decided to look at my /var/log/boot.msg today and see if I could improve anything, for fun. Then I saw the following:

Mounting local file systems...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
mount: /dev/sda6 already mounted or /home busy
mount: /dev/sda8 already mounted or /img busy
mount: /dev/sda9 already mounted or /VM busy
mount: /dev/sda7 already mounted or /tmp busy
mount: special device /dev/disk/by-label/USB16GBFAT does not exist
failedRetry device configurationdone
Loading fuse module done
Mounting fuse control filesystemdone

The USB16GBFAT does not exist is normal, my USB stick is rarely connected at boot.
Other than SWAP, i’ve got 5 partitions, sda1, sda6, sda7, sda8 and sda9. SDA1 being /.

I have all of them in my fstab file with mount options.

/dev/sda1 /                       ext3       defaults,noatime              	                    0 1
/dev/sda6 /home                xfs         defaults,noatime,logbufs=8                         0 2
/dev/sda8 /img                   ext3       acl,user_xattr,noatime,data=writeback	 0 2
/dev/sda9 /VM                    xfs         defaults,noatime,logbufs=8                         0 2
/dev/sda7 /tmp                   xfs         defaults,noatime,logbufs=8                         0 2
/dev/sda5 swap                   swap      defaults 			                                   0 0
proc                 /proc            proc       defaults              	                                         0 0
sysfs                /sys             sysfs      noauto                	                                         0 0
debugfs           /sys/kernel/debug     debugfs     noauto                      	          0 0
usbfs               /proc/bus/usb           usbfs         noauto                         	        0 0
devpts             /dev/pts                     devpts       mode=0620,gid=5       	         0 0
LABEL=USB16GBFAT     /media/USB16GB	  vfat	     uid=1000,gid=100        	  0 0

Looking at SUDO MOUNT command to see which partitions are mounted:

/dev/sda1 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)

None but sda1 root!
I don’t understand.

But my system boots fine. I have all my partitions after booting. I run every day with no issue at all, though any of my SDA partitions are listed in MOUNT command.

What is happening?
Why during boot sequence it cannot mount my partitions?
Why they are mounted (obviously cuz I use them every day) but don’t show as being mounted in sudo mount command?
Is there a ghost (or angel, cuz I run flawlessly) in my 10.3 installation?
Do I really have my partitions mounted with the options I selected in fstab?
Is something gonna screw up sooner or later cuz nothing shows in mount command?
Am I at risk somehow?

I use openSUSE 10.3.
I have checked under vmware using openSUSE 11.0 and I don’t get those error lines in my boot.msg. Also I do get the SDA partitions listed in the sudo mount command of my openSUSE 11.0 installation (which I don’t use for every day stuff).

BOOT.MSG openSUSE 11.0 VMWare (one partition other than / and SWAP)

Mounting local file systems...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda3 on /home type xfs (rw,noatime,logbufs=8)
doneMounting securityfs on /sys/kernel/security done

SUDO MOUNT command openSUSE 11.0 VMWare

/dev/sda2 on / type ext3 (rw,noatime,data=writeback,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda3 on /home type xfs (rw,noatime,logbufs=8)
securityfs on /sys/kernel/security type securityfs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
gvfs-fuse-daemon on /home/frank/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=frank)

FSTAB openSUSE 11.0 VMWare

/dev/disk/by-id/scsi-SATA_VMware_Virtual_00000000000000000001-part1 swap                 swap       defaults              0 0
/dev/disk/by-id/scsi-SATA_VMware_Virtual_00000000000000000001-part2 /                    ext3       noatime,data=writeback,acl,user_xattr 1 1
/dev/disk/by-id/scsi-SATA_VMware_Virtual_00000000000000000001-part3 /home                xfs        noatime,logbufs=8     1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

tnx a lot for any help!

Hi.

Can you provide the output of the ‘mount’ command after your system is up and running? You said all your partitions are available after booting…

Other than that, your fstab seems fine. Although if you’re using a gui (KDE/Gnome), you can remove the USB16GBFAT line, as the flash-drive will be automounted whenever you insert it.

Be aware, with that USB16GBFAT, your system MAY decide that it not being available at boot time is an error and it’ll drop you into an error recovery shell. Very annoying! (especialy when you remote boot your machine from work and then have to hope the kitten can hear your desperate screams and will fix it for you)

Lornix

This (“Looking at sudo mount command” in previous post) was the output of mount after system is up and running in X.

/dev/sda1 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)

This is why I am speechless, cuz mount command does not show my partitions (except root) but I can access them no problem and they are listed in my gkrellm monitor.

If I remove the USB16GFAT line it won’t mount correctly using my gkrellm command. When I plug the stick, gkrellm sends a mount command and mounts it so it shows in the monitor and by a one-click click I can umount it. For some reason gkrellm seems to need the line in fstab.

But I could try and boot without that line and see if my partitions show as mounted correctly afterwards. If yes, then that line (in error at every boot anyway) would cause all that situation.

Hmmm, maybe Gkrellm is automounting them.

I imagine that if you were to open a konqueror window into one of your partition subdirectories, you’d see it listed in the mount command.

Really sounds like they’re being automounted.

is the fusefs daemon automounting them? maybe?

Lornix

Yeah I think you’re right, something automounts them.

I have removed the USB16GB line in fstab and I get the same error lines. There is something else that fails at that time but it went too fast on the screen and it’s unclear in the log. I will check on next boot.

My partitions don’t get umounted when I shutdown or reboot the machine, only sda1 gets umounted, at least written on the screen. Maybe I have an autoUmount function doing it’s job for the other partitions that seem to be automounted.

I might try without gkrellm, but gkrellm loads way after I have accessed X and /home partition, so I would doubt gkr is the problem. I think something else automounts them, like you mentioned.

Looking into /proc/mounts shows ALL of my partitions mounted with correct mount options as well. I think I am not at risk then, which was my main concern.

I don’t know how to check if fuse is automounting them, but I will google around for fuse and autmounting at boot sequence and see what I get.

tnx for the tips! :slight_smile: