grub-probe fails in the presence of snapshot logical volumes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Found in: 2.02~beta2-6
My upgrade from saucy to trusty ran into problems, with grub-probe failing with "unknown filesystem", which propogated up to cause the kernel install to fail, resulting in a machine where I cannot install packages. After some debugging:
(missing here is the trace of it failing with the original snapshot in place, that I created to give me a way back in the event that trusty hated me horribly.)
-rover3(root) 351 : update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found memtest86+ image: /memtest86+.elf
Found Ubuntu 12.04.1 LTS (12.04) on /dev/mapper/
Found Ubuntu 13.04 (13.04) on /dev/mapper/
Found Ubuntu 13.10 (13.10) on /dev/mapper/
done
-rover3(root) 352 : lvcreate -s /dev/rover3/saucy -L 30G -n saucy-save
Logical volume "saucy-save" created
-rover3(root) 353 : update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Found memtest86+ image: /memtest86+.elf
grub-probe: error: unknown filesystem.
Found Ubuntu 12.04.1 LTS (12.04) on /dev/mapper/
Found Ubuntu 13.04 (13.04) on /dev/mapper/
/usr/sbin/
-rover3(root) 354 :
Bug # 563895 may or may not be relevant.
Here is the output of: grub-probe -d -vv --target=fs_uuid --device /dev/mapper/ rover3- saucy-- save