Boot mount errors - partitions busy or already mounted
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Boot mount errors - partitions busy or already mounted
Hello,
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:
Code:
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.
Looking at SUDO MOUNT command to see which partitions are mounted:
Code:
/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)
Code:
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
Code:
/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)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.