Setting up memtest86+ hangs because of "grub-probe: error: unknown filesystem"
Bug #970260 reported by
Laurent Riffard
This bug affects 33 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Debian) |
Fix Released
|
Unknown
|
|||
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned | ||
memtest86+ (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Invalid
|
Undecided
|
Unassigned | ||
Raring |
Invalid
|
Undecided
|
Unassigned | ||
os-prober (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
High
|
Unassigned |
Bug Description
Installation of package memtest86+ fails, it does hang and never ends if lvm snapshot is present.
Prepare:
* create active lvm snapshot
Test case:
$ sudo apt-get install --reinstall memtest86+
<hang>
Recover from the hang with:
$ sudo pkill -f 'frontend /var/lib/
$ sudo killall grub-mount
$ sudo umount /var/lib/
(don't kill grub-mount nor umount if you want the next run to "succeed", well not run)
Actual problem:
update-grub / os-prober leave stray grub-mount behing.
workarounds applied in os-prober 1.57 doesn't actually help here.
upgrading to quantal's grub2 package resolves the hangs.
A minimal backport from grub has not been identified yet.
Changed in os-prober (Ubuntu): | |
importance: | Undecided → High |
Changed in memtest86+ (Ubuntu Precise): | |
status: | New → Invalid |
Changed in memtest86+ (Ubuntu Quantal): | |
status: | New → Invalid |
Changed in memtest86+ (Ubuntu Raring): | |
status: | Confirmed → Invalid |
Changed in os-prober (Ubuntu Quantal): | |
status: | New → Fix Released |
Changed in os-prober (Ubuntu Raring): | |
status: | Confirmed → Fix Released |
Changed in os-prober (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in grub2 (Ubuntu Raring): | |
status: | New → Fix Released |
Changed in grub2 (Ubuntu Quantal): | |
status: | New → Fix Released |
Changed in grub2 (Ubuntu Precise): | |
status: | New → Confirmed |
description: | updated |
Changed in memtest86+ (Ubuntu Precise): | |
status: | Invalid → Confirmed |
Changed in grub2 (Debian): | |
status: | Unknown → Fix Released |
To post a comment you must log in.
This evening, I noticed that "dpkg --configure memtest86 +" produced a "grub-mount" process :
# ps axf standard: amd64 debconf/ frontend /var/lib/ dpkg/info/ memtest86+ .postinst configure 4.20-1ubuntu1 vglinux1- lv_ubunutu_ oneiric /var/lib/ os-prober/ mount
[...]
21980 pts/2 S+ 0:00 \_ sudo apt-get -f install
21981 pts/2 S+ 0:01 \_ apt-get -f install
21989 pts/4 Ss+ 0:00 \_ /usr/bin/dpkg --status-fd 67 --configure memtest86+:amd64 ubuntu-
21990 pts/4 S+ 0:00 \_ /usr/bin/perl -w /usr/share/
21997 pts/4 Z+ 0:00 \_ [memtest86+.post] <defunct>
[...]
23816 ? Ss 0:00 grub-mount /dev/mapper/
[...]
Killing this "grub-mount" process allows dpkg to complete successfully.
So the problem was not the Reiser4 filesystems, it was the LVM snapshot.
# lvdisplay /dev/mapper/ vglinux1- lv_ubunutu_ oneiric lv_ubunutu_ oneiric YwJx-HQXW- ryD9-5zya- tI0g-J7Qosz lv_ubuntu
--- Logical volume ---
LV Name /dev/vglinux1/
VG Name vglinux1
LV UUID e8GxvT-
LV Write Access read/write
LV snapshot status active destination for /dev/vglinux1/
LV Status available
# open 0
LV Size 10,00 GiB
Current LE 2560
COW-table size 10,00 GiB
COW-table LE 2560
Allocated to snapshot 50,56%
Snapshot chunk size 512,00 KiB
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:13