Using grub in Recovery Menu fails with separate /boot partition

Bug #1438862 reported by Brian Murray
8
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 grub ... Update grub bootloader" fails to do anything.

/usr/sbin/grub-mkconfig: 250: /usr/sbin/grub-mkconfig: cannot create /boot/grub/grub.cfg.new: Directory nonexistent.

tags: added: systemd-boot vivid
Revision history for this message
Martin Pitt (pitti) wrote :

I cannot reproduce this. On a reasonably current installation, this updates grub just fine. But I do have a /boot/grub/ directory; can you check (in the root shell) whether that exists for you?

tags: removed: systemd-boot
Changed in friendly-recovery (Ubuntu):
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

This is probably related to my using an encrypted lvm partition.

Martin Pitt (pitti)
summary: - Using grub in Recovery Menu fails
+ Using grub in Recovery Menu fails with separate /boot partition
Changed in friendly-recovery (Ubuntu):
status: Incomplete → Triaged
tags: added: systemd-boot
Martin Pitt (pitti)
Changed in friendly-recovery (Ubuntu):
importance: Undecided → Medium
status: Triaged → Fix Committed
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Sun, 19 Apr 2015 12:49:11 +0100

Changed in friendly-recovery (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.