| 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.