[Bug 1438860] Re: Using fsck in Recovery Menu fails for encrypted/LVM root

[Launchpad Bug Tracker]

This bug was fixed in the package friendly-recovery - 0.2.30

---------------
friendly-recovery (0.2.30) vivid; urgency=medium

  * Implement fsck by ourselves instead of letting the boot sequence already
    do that for us. (LP: #1438860)
  * dpkg: Quiesce "file not found" errors in apt cleanup. (LP: #887589)
  * Mount all file systems after fsck (like with mountall under upstart), to
    also cover separate /boot partitions for grub. (LP: #1438862)
 -- Martin Pitt <martin.pitt at ubuntu.com>   Sun, 19 Apr 2015 12:49:11 +0100

** Branch linked: lp:ubuntu/vivid-proposed/friendly-recovery

** Changed in: friendly-recovery (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/1438860

Title:
  Using fsck in Recovery Menu fails for encrypted/LVM root

Status in friendly-recovery package in Ubuntu:
  Fix Released

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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1438860/+subscriptions