I have a setup where one of user homes resides on usb disk. Recently (during last month, don't know exactly as I don't reboot often), mounting it during boot stopped working. Logging in as root and running "mount -a" mounts it without any problem. There is no error message about failed mount during boot, it just silently ignores the fstab entry. Reproducible: Always
I would guess that the kernel has not initialized the device by the time OpenRC is mounting disks. In any case, please share your fstab.
(In reply to Mike Gilbert from comment #1) > I would guess that the kernel has not initialized the device by the time > OpenRC is mounting disks. sdc comes up ~7 s after boot, before e.g. sd card controller or network however, in that case, I'd expect an error message like mount: /home/kavol: can't find LABEL=HD154UI. or Some local filesystem failed to mount somewhere onscreen/in messages ... (ok, I can't be sure what's on screen as it disappears after X start, but at least I don't see any red, all green OK) > In any case, please share your fstab. # /etc/fstab: static file system information. # # noatime turns off atimes for increased performance (atimes normally aren't # needed); notail increases performance of ReiserFS (at the expense of storage # efficiency). It's safe to drop the noatime options if you want and to # switch between notail / tail freely. # # The root filesystem should have a pass number of either 0 or 1. # All other filesystems should have a pass number of 0 or greater than 1. # # See the manpage fstab(5) for more information. # # <fs> <mountpoint> <type> <opts> <dump/pass> # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts. # # NOTE: Even though we list ext4 as the type here, it will work with ext2/ext3 # filesystems. This just tells the kernel to use the ext4 driver. # # NOTE: You can use full paths to devices like /dev/sda3, but it is often # more reliable to use filesystem labels or UUIDs. See your filesystem # documentation for details on setting a label. To obtain the UUID, use # the blkid(8) command. #LABEL=boot /boot ext4 noauto,noatime 1 2 #LABEL=swap none swap sw 0 0 #/dev/cdrom /mnt/cdrom auto noauto,ro 0 0 /dev/sda1 / auto rw 0 1 LABEL="HD154UI" /home/kavol auto noatime 0 2
if your disk has an LUKS signature you may be affected by https://bugs.gentoo.org/926950
(In reply to Joakim Tjernlund from comment #3) > if your disk has an LUKS signature you may be affected by > https://bugs.gentoo.org/926950 no encryption ... reading comments, I guess wipefs should list it, so checking: # wipefs -n /dev/sdc* DEVICE OFFSET TYPE UUID LABEL sdc 0x1fe dos sdc1 0x438 ext4 f1a7f1a8-0ff6-4156-b93a-914d8c9652c9 HD154UI
hm, while at it ... seems there is some deeper problem - I've tried to workaround (test if timing is the problem) simply by adding `sleep 5` to localmount script now the disk gets mounted, however, fsck is not run on it despite it should be run each time (and it worked before the mounting stopped working)
