You are not logged in.
When I reboot my system systemd drops to an emergancy shell claiming it cannot mount /home subshell
Jul 12 19:00:23 mythbox systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-5733ff79\x2de45b\x2d4feb\x2db4a6\x2d6b5692
Jul 12 19:00:23 mythbox systemd[1]: Dependency failed for /home.
Jul 12 19:00:23 mythbox systemd[1]: Dependency failed for Local File Systems.
Jul 12 19:00:23 mythbox systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Jul 12 19:00:23 mythbox systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Jul 12 19:00:23 mythbox systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'.
Jul 12 19:00:23 mythbox systemd[1]: dev-disk-by\x2duuid-5733ff79\x2de45b\x2d4feb\x2db4a6\x2d6b5692b2cc7d.device: Job dev-disk-b
Jul 12 19:00:23 mythbox systemd[1]: Reached target Network.
Jul 12 19:00:23 mythbox systemd[1]: Reached target Timers.
Jul 12 19:00:23 mythbox systemd[1]: Starting Rebuild Dynamic Linker Cache...
Jul 12 19:00:23 mythbox systemd[1]: Starting Rebuild Journal Catalog...
Jul 12 19:00:23 mythbox systemd[1]: Started Emergency Shell.
However if I press ctrl-d to the system continues to boot fine (also will boot fine if I reboot the system)
Offline
(also will boot fine if I reboot the system)
What does that mean? It only happens sometimes?
Have you check the UUID in fstab against lsblk -f / blkid output?
Offline
UUID matches lsblk -f and fstab.
It seems to happen constantly on the first reboot or power on but does not occur if a reboot the system again, as I said the error also resolves itself if I continue booting after the emergency shell. It seems the system does not wait long enough for /home to mount.
Offline
Or possibly only when I boot into windows to play a game
Offline