[Bug 1987679] [NEW] update-grub leaves filesystems (lvm-thin, lvm snap) mounted

mike 1987679 at bugs.launchpad.net
Thu Aug 25 15:36:51 UTC 2022


Public bug reported:

If one happens to have by accident (or on purpose) a thick LVM snapshot, or a thin-LV with a copy of a system on it, update-grub reports
/sbin/grub-probe: error: unknown filesystem.
Found Ubuntu 22.04.1 LTS on /dev/mapper/vgxubuntu-s22.04
and
/sbin/grub-probe: error: disk `lvmid/X7waXv-rMDA-5fQA-aw6l-ei1I-8Gz3-pQl3lr/k3Ze1u-Mfwc-pxUt-7fXa-FjSZ-7IkX-HAxf3b' not found.
Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/vgxubuntu-XR22.04.1U

and leaves the systems mounted rw on /var/lib/os-prober/mount.
On subsequent invocations update-grub spews out multiple
mdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy

I'm pretty sure this also causes a new install to hang (though a power-
reset seems to load the new system - not sure if it is complete or not.)

The missing umounts should be relatively easy to fix, but the thick
snapshot error is particularly vague as most users (I think) would take
the "unknown filesystem" to refer to the previous entry.

I have been playing with grub2-common-2.06-2ubuntu7 on xubuntu 22.04.1,
though I am sure this has been around a while

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- If on happens to have by accident (or on purpose) a thick LVM snapshot, or a thin-LV with a copy of a system on it, grub-install reports 
+ If one happens to have by accident (or on purpose) a thick LVM snapshot, or a thin-LV with a copy of a system on it, update-grub reports
  /sbin/grub-probe: error: unknown filesystem.
  Found Ubuntu 22.04.1 LTS on /dev/mapper/vgxubuntu-s22.04
  and
  /sbin/grub-probe: error: disk `lvmid/X7waXv-rMDA-5fQA-aw6l-ei1I-8Gz3-pQl3lr/k3Ze1u-Mfwc-pxUt-7fXa-FjSZ-7IkX-HAxf3b' not found.
  Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/vgxubuntu-XR22.04.1U
  
  and leaves the systems mounted rw on /var/lib/os-prober/mount.
- On subsequent invocations it spews out multipler
+ On subsequent invocations update-grub spews out multiple
  mdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy
  
  I'm pretty sure this also causes a new install to hang (though a power-
  reset seems to load the new system - not sure if it is complete or not.)
  
  The missing umounts should be relatively easy to fix, but the thick
  snapshot error is particularly vague as most users (I think) would take
  the "unknown filesystem" to refer to the previous entry.
  
  I have been playing with grub2-common-2.06-2ubuntu7 on xubuntu 22.04.1,
  though I am sure this has been around a while

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

Title:
  update-grub leaves filesystems (lvm-thin, lvm snap) mounted

Status in grub2 package in Ubuntu:
  New

Bug description:
  If one happens to have by accident (or on purpose) a thick LVM snapshot, or a thin-LV with a copy of a system on it, update-grub reports
  /sbin/grub-probe: error: unknown filesystem.
  Found Ubuntu 22.04.1 LTS on /dev/mapper/vgxubuntu-s22.04
  and
  /sbin/grub-probe: error: disk `lvmid/X7waXv-rMDA-5fQA-aw6l-ei1I-8Gz3-pQl3lr/k3Ze1u-Mfwc-pxUt-7fXa-FjSZ-7IkX-HAxf3b' not found.
  Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/vgxubuntu-XR22.04.1U

  and leaves the systems mounted rw on /var/lib/os-prober/mount.
  On subsequent invocations update-grub spews out multiple
  mdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy

  I'm pretty sure this also causes a new install to hang (though a
  power-reset seems to load the new system - not sure if it is complete
  or not.)

  The missing umounts should be relatively easy to fix, but the thick
  snapshot error is particularly vague as most users (I think) would
  take the "unknown filesystem" to refer to the previous entry.

  I have been playing with grub2-common-2.06-2ubuntu7 on xubuntu
  22.04.1, though I am sure this has been around a while

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1987679/+subscriptions




More information about the foundations-bugs mailing list