[Bug 1228712] The disk "start job" at boot should probably have timeout, and/or path to emergency shell if they get stuck, and/or print out what command they're even trying to run when stuck for longer than expected
https://bugzilla.suse.com/show_bug.cgi?id=1228712 https://bugzilla.suse.com/show_bug.cgi?id=1228712#c20 --- Comment #20 from Stefan Hundhammer <shundhammer@suse.com> --- Well, what else could systemd do if vital partitions cannot be mounted? It might boot into some "degraded" mode for partitions that are not really vital (i.e. boot without them); recognizing which partitions or filesystems are vital and which are not would probably be a good enhancement for systemd. But this is a change that would have to be done upstream by the systemd developers. As for useful error - at least it shows which filesystem it is currently trying to mount, so you do get a hint what the problem is. I am not sure if it could realistially give more details, in particular for more complex storage setups (LVM, LUKS, RAID, multi-volume Btrfs or all of these combined). -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com