FS#29241 - Mounting local filesystems gives [FAIL] although all is well
Attached to Project:
Arch Linux
Opened by cfr (cfr42) - Monday, 02 April 2012, 21:03 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 04 April 2012, 16:13 GMT
Opened by cfr (cfr42) - Monday, 02 April 2012, 21:03 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 04 April 2012, 16:13 GMT
|
Details
Relevant forum thread:
https://bbs.archlinux.org/viewtopic.php?id=136653
(includes irrelevant stuff as well)
Description: Every time I boot, I get a "[FAIL]" report for mounting local filesystems although nothing fails to mount which is supposed to. fstab does contain entries for a USB external drive but the partitions on this drive all have the "nofail" option listed. boot log shows that the system looks for something in the position which I think would be taken by an sd card if I had one. Since I don't, the reader is empty and it does seem unhappy about this. Additional info: * package version(s) core/util-linux 2.21-6 (base) [installed] multilib/lib32-util-linux 2.21-1 [installed] * config and/or log files etc. fstab and /var/log/boot are attached (identifying info hopefully removed) Steps to reproduce: |
This task depends upon
Closed by Tom Gundersen (tomegun)
Wednesday, 04 April 2012, 16:13 GMT
Reason for closing: Not a bug
Additional comments about closing: mount works as advertised, and "nofail" does not apply to missing mountpoints.
Wednesday, 04 April 2012, 16:13 GMT
Reason for closing: Not a bug
Additional comments about closing: mount works as advertised, and "nofail" does not apply to missing mountpoints.
Try booting with a minimal fstab, e.g.:
UUID=<UUID> / ext4 errors=remount-ro,noatime 0 1
UUID=<UUID> /var ext4 defaults,noatime 0 2
Check if the problem persists, if not, then try to find the minimal fstab where the problem occurs. Furthermore, it might be useful to try to mount the offending fs with only "defaults", and if that does not trigger the problem figure out what options do.
Can I remove the existing files if they are useless?
You should be able to boot just fine without /home, it just means you won't get a graphical login, and you might not be able to login as anything other than root. For testing this is fine though.
If I add back in the root partition on the external drive, still no error.
If I add any further entries back, I get the error. I didn't actually test every possibility but I think I tested enough.
Basically, if the mount point does not exist, I get the error.
I can reproduce with:
# mount none -t tmpfs /non-existing-mount-point -o nofail
mount: mount point /non-existing-mount-point does not exist
# echo $?
32
e.g. on my backup /boot/efi, /home, /var etc. are mount points so fstab contains /mnt/external-disk/boot/efi and so on. But if the external disk is absent, although /mnt/external-disk exists, nothing beneath it will.
By the way, do you still want fstab etc.? I figured it was less interesting now, but I'm happy to post it if you'd like. (Now I can stop worrying about obfuscating the UUIDs, it will be a lot less hassle!)
The best I can suggest is to mark your partitions as "noauto", and mount them manually on need when your device is plugged in (which I suppose is what you have had to do anyway most of the time if you plug in your backup device after switching your computer on).