[Bug 1231595] New: Encrypted root file system fsck error is difficult to recover
https://bugzilla.suse.com/show_bug.cgi?id=1231595 Bug ID: 1231595 Summary: Encrypted root file system fsck error is difficult to recover Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: opensuse@halobates.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- On a system with encrypted root file system I had a corruption in the ext4 orphan list that dropped the initrd into the recovery shell when trying to mount sysroot. I had to recover by cat /proc/cmdline e2fsck UUID=<copy root uuid from cmdline> While I was able to do that it was a very cumbersome procedure to copy the UUID exactly and was non obvious and difficult for the user. It would be good if the initrd detected such a case and offers to run fsck by itself. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231595 https://bugzilla.suse.com/show_bug.cgi?id=1231595#c3 Andi Kleen <susebz@halobates.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |susebz@halobates.de --- Comment #3 from Andi Kleen <susebz@halobates.de> --- It was not obvious what the device was (in this case it's a dmcrypt device mapper file). Also /proc/mounts only showed /dev/root unfortunately. Okay if systemd-fsck is already there, something didn't work with it. I guess it's a bug report then, not an enhancement request. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com