Hide Forgot
Description of problem: When booting a system with a degraded rootfs, systemd hangs indefinitely at basic.target instead of dropping to a shell and producing the sosreport for troubleshooting. Version-Release number of selected component (if applicable): systemd-212-4 How reproducible: Always Steps to Reproduce: 0. Any failure to mount /sysroot will do. In my case it's a Btrfs raid1 volume with one device removed, making it degraded which currently on Btrfs does not automatically mount degraded. Actual results: Indefinite hang, cyclon eye, at basic.target. Expected results: Eventual timeout and shell prompt. Additional info: This works as expected on Fedora 20, systemd-209. If I use systemctl enable debug-shell.service and retry, I still cannot get to a shell on any tty; but even without debug-shell enabled we really need to eventually fail on basic.target and drop to a shell. Indefinite hang prevents troubleshooting even basic causes for boot failures.
During hang, console text reads with the following four lines, repeated every 15s to 55s (variable). [ **] A start job is running for dev-disk-by\x2uuid-7b742…55s / no limit)G ot notification message of unit systemd-journald.service systemd-journald.service: Got notification message from PID 105 (WATCHDOG=1…) systemd-journald.service: got WATCHDOG=1
This also hangs on Fedora 20 after updating systemd-208-9 to systemd-208-16; however there's no timer it just says: [ *** ] A start job is running for dev-disk-by\x2uuid-9ff63..b4fb6d66.device After 1 hour it's still hung.
So far, the only way I have been able to fix a btrfs raid1 volume with a missing device is to boot up in rescue mode, btrfs-dev-add a new device and then btrfs-dev-delete-missing.
*** Bug 1186908 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.