Using fsck in Recovery Menu fails for encrypted/LVM root
Bug #1438860 reported by
Brian Murray
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
friendly-recovery (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Using vivid with systemd the entry for "fsck ... Check all file systems" fails to do anything.
Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
tags: | added: systemd-boot vivd |
summary: |
- Using fsck in Recovery Menu fails + Using fsck in Recovery Menu fails for encrypted/LVM root |
Changed in friendly-recovery (Ubuntu): | |
status: | Incomplete → New |
Changed in friendly-recovery (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
fsck does work here. I do confirm the confusing error message about not being able to talk to polkit, but fsck does get started (see attached screen shot). How does it look for you?
(Mine is a current vivid amd64 QEMU installation)