Boot only in emergency shell

Hi,
everytime I reboot the fedora server it fails to check the file system for /home and goes into the emergency shell. But the /home filesystem is ok and the system start without out any problems when I press ctrl-d.

boot.log 
  OK   Started Show Plymouth Boot Screen.
  OK   Reached target Paths.
  OK   Started Forward Password Requests to Plymouth Directory Watch.
  OK   Reached target Basic System.
  OK   Found device /dev/mapper/fedora-root.
  OK   Reached target Initrd Root Device.
  OK   Started dracut initqueue hook.
		Starting File System Check on /dev/mapper/fedora-root...
  OK   Reached target Remote File Systems (Pre).
  OK   Reached target Remote File Systems.
  OK   Started File System Check on /dev/mapper/fedora-root.
        Mounting /sysroot...
  OK   Mounted /sysroot.
  OK   Reached target Initrd Root File System.
        Starting Reload Configuration from the Real Root...
  OK   Started Reload Configuration from the Real Root.
  OK   Reached target Initrd File Systems.
  OK   Reached target Initrd Default Target.
        Starting dracut pre-pivot and cleanup hook...
  OK   Started dracut pre-pivot and cleanup hook.
        Starting Cleaning Up and Shutting Down Daemons...
  OK   Stopped target Timers.
  OK   Stopped dracut pre-pivot and cleanup hook.
  OK   Stopped target Remote File Systems.
        Starting Plymouth switch root service...
  OK   Stopped target Initrd Default Target.
  OK   Stopped target Basic System.
  OK   Stopped target Sockets.
  OK   Stopped target System Initialization.
  OK   Stopped target Swap.
  OK   Stopped Create Volatile Files and Directories.
  OK   Stopped target Paths.
        Stopping udev Kernel Device Manager...
  OK   Stopped target Initrd Root Device.
  OK   Stopped target Local File Systems.
        Starting Setup Virtual Console...
  OK   Stopped Apply Kernel Variables.
  OK   Stopped target Slices.
  OK   Stopped target Remote File Systems (Pre).
  OK   Stopped dracut initqueue hook.
  OK   Stopped udev Coldplug all Devices.
  OK   Started Cleaning Up and Shutting Down Daemons.
  OK   Stopped udev Kernel Device Manager.
  OK   Stopped Create Static Device Nodes in /dev.
  OK   Stopped Create list of required static device nodes for the current kernel.
  OK   Stopped dracut pre-udev hook.
  OK   Stopped dracut cmdline hook.
  OK   Closed udev Kernel Socket.
  OK   Closed udev Control Socket.
        Starting Cleanup udevd DB...
  OK   Started Plymouth switch root service.
  OK   Started Cleanup udevd DB.
  OK   Started Setup Virtual Console.
  OK   Reached target Switch Root.
          Starting Switch Root...
          A start job is running for udev Wait for Complete Device Initialization (5s / 2min 59s)^[[K[^[[0;1;31m*^[[0m^[[0;31m*    ^[[0m    ] 
		  A start job is running for udev Wait for Complete Device Initialization (5s / 2min 59s)^[[K[^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m*   
		  A start job is     running for udev Wait for Complete Device Initialization (6s / 2min 59s)^[[K[ ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m*  
		  A start job is running for udev     Wait for Complete Device Initialization (7s / 2min 59s)^[[K[  ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m*  
		  A start job is running for udev Wait for Complete     Device Initialization (7s / 2min 59s)^[[K[   ^[[0;31m*^[[0;1;31m*^[[0m^[[0;31m* 
		  A start job is running for udev Wait for Complete Device Initializ    ation (37us / 2min 51s)^[[K[^[[0;32m 
  OK   Started udev Wait for Complete Device Initialization.
          Starting Device-Mapper Multipath Device Controller...
  OK   Started Device-Mapper Multipath Device Controller.
  OK   Reached target Local File Systems (Pre).
          Mounting Mount unit for core18, revision 1223...
          Starting File System Check on /dev/disk/by-label/Home...
          Mounting Mount unit for node-red, revision 503...
          Mounting Mount unit for nextcloud, revision 16402...
          Starting File System Check on /dev/sda1...
          Mounting Mount unit for core18, revision 1192...
          Mounting Mount unit for node-red, revision 512...
          Mounting Mount unit for core, revision 7917...
          Mounting Mount unit for influxdb-ijohnson, revision 14...
          Mounting Mount unit for influxdb-ijohnson, revision 24...
          Mounting Mount unit for core, revision 7713...
          Mounting Mount unit for nextcloud, revision 16739...
  FAILED Failed to start File System Check on /dev/disk/by-label/Home.
          See 'systemctl status "systemd-fsck@dev-disk-by\\x2dlabel-Home.service"' for details.
  DEPEND Dependency failed for /home.
  DEPEND Dependency failed for Local File Systems.
  DEPEND Dependency failed for NFS server and services.
  DEPEND Dependency failed for NFS Mount Daemon.
  DEPEND Dependency failed for NFSv4 ID-name mapping service.

  OK   Started File System Check on /dev/sda1.
  OK   Mounted Mount unit for core18, revision 1223.
  OK   Mounted Mount unit for core18, revision 1192.
  OK   Mounted Mount unit for node-red, revision 512.
  OK   Mounted Mount unit for node-red, revision 503.
  OK   Mounted Mount unit for influxdb-ijohnson, revision 24.
        Starting Preprocess NFS configuration...
        Mounting /boot...
  OK   Reached target System Time Synchronized.
  OK   Stopped Forward Password Requests to Wall Directory Watch.
  OK   Reached target Host and Network Name Lookups.
  OK   Reached target Sound Card.
  OK   Reached target Timers.
          Starting Create Volatile Files and Directories...
          Starting Tell Plymouth To Write Out Runtime Data...
  OK   Started Emergency Shell.
  OK   Reached target Emergency Mode.

systemctl status “systemd-fsck@dev-disk-by\x2dlabel-Home.service” shows a failure.
If I run the check again in emergency mode (systemctl start “systemd-fsck@dev-disk-by\x2dlabel-Home.service” ) than all fin fine.
For me it looks like that the device mapper not finished when the check is started.
What can I do ? The impact is that the dnf system-upgrade reboot fails also and I can’t update my system.

best regards
Uwe

1 Like

Try to find out the exact cause of the failure if possible.

Try to use UUID instead of label to mount that partition.

Or try to create a custom mount unit like this:

$ systemctl cat var-backup.mount
# /etc/systemd/system/var-backup.mount
[Unit]
Description=/var/backup

[Mount]
What=/dev/fedora/backup
Where=/var/backup
Type=ext4

[Install]
WantedBy=multi-user.target