uhm when a system is bootet with "rd.plymouth=0 plymouth.enable=0" and hence plymouth is not installed a boot with "touch /forcefsck" should not lead needless in a emergency shell after or due the rootfs is checked and clean 776734] usbserial: usb_serial_init - returning with error -19 May 3 15:09:47 testserver kernel: usbserial: usb_serial_init - usb_register failed May 3 15:11:18 testserver systemd: Dependency failed for /Volumes/dune. May 3 15:11:18 testserver systemd: Dependency failed for Local File Systems. May 3 15:11:18 testserver systemd: Dependency failed for Relabel all filesystems, if necessary. May 3 15:11:18 testserver systemd: Dependency failed for Mark the need to relabel after reboot. May 3 15:11:18 testserver systemd: Triggering OnFailure= dependencies of local-fs.target. May 3 15:11:18 testserver systemd: Dependency failed for /usr/local/sftp-homes/flow/cms. May 3 15:11:18 testserver systemd: Dependency failed for /home/builduser. May 3 15:11:18 testserver systemd: Dependency failed for /tmp. May 3 15:11:18 testserver systemd: Dependency failed for /var/tmp. May 3 15:11:18 testserver systemd: Dependency failed for /Volumes/dune/www-servers/autotest. May 3 15:11:18 testserver systemd: Dependency failed for File System Check on /dev/disk/by-uuid/bb7dfa33-8d31-496c-99a9-a1978eef98ec. May 3 15:11:18 testserver systemd: Dependency failed for /boot. May 3 15:11:18 testserver systemd: Dependency failed for File System Check on /dev/disk/by-uuid/6f7807bd-a508-44c7-9e72-651f82b6ad6c. May 3 15:11:30 testserver systemd: Failed at step EXEC spawning /bin/plymouth: No such file or directory
i stand corrected - the problem is that after some time while the rootfs is still checked systemd decides to start other units - that's a timing problem which gets here likely visible because the machine is slow at the moment (raid-check and rsync with checksums over 1 TB on a different VM) May 3 15:19:59 testserver systemd-fsck: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system. May 3 15:19:59 testserver systemd: Started udev Coldplug all Devices. May 3 15:19:59 testserver systemd: Started Setup Virtual Console. May 3 15:21:29 testserver systemd: Job dev-disk-by\x2duuid-bb7dfa33\x2d8d31\x2d496c\x2d99a9\x2da1978eef98ec.device/start timed out. May 3 15:21:29 testserver systemd: Timed out waiting for device dev-disk-by\x2duuid-bb7dfa33\x2d8d31\x2d496c\x2d99a9\x2da1978eef98ec.device. May 3 15:21:29 testserver systemd: Dependency failed for /Volumes/dune. May 3 15:21:29 testserver systemd: Dependency failed for Local File Systems. May 3 15:21:29 testserver systemd: Dependency failed for Relabel all filesystems, if necessary. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Dependency failed for Mark the need to relabel after reboot. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Triggering OnFailure= dependencies of local-fs.target. May 3 15:21:29 testserver systemd: Dependency failed for /usr/local/sftp-homes/flow/cms. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Dependency failed for /home/builduser. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Dependency failed for /tmp. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Dependency failed for /var/tmp. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Dependency failed for /Volumes/dune/www-servers/autotest. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: failed for FilDependencye System Check on /dev/disk/by-uuid/bb7dfa33-8d31-496c-99a9-a1978eef98ec. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Job dev-disk-by\x2duuid-6f7807bd\x2da508\x2d44c7\x2d9e72\x2d651f82b6ad6c.device/start timed out. May 3 15:21:29 testserver systemd: Timed out waiting for device dev-disk-by\x2duuid-6f7807bd\x2da508\x2d44c7\x2d9e72\x2d651f82b6ad6c.device. May 3 15:21:29 testserver systemd: Dependency failed for /boot. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Dependency failed for File System Check on /dev/disk/by-uuid/6f7807bd-a508-44c7-9e72-651f82b6ad6c. May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: May 3 15:21:29 testserver systemd: Stopped Daily Cleanup of Temporary Directories.
it's in fact a timing problem, with no load on the host no emergency shell and that is really bad because boot becomes a lottery on slow machines
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.