FYI, I'm hitting something similar, but for mdraid. Now, according to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540549 my problem was
fixed long ago, in grub-1.97, but I'm running lucid, with grub-install
-v returning: grub-install (GNU GRUB 1.98-1ubuntu9)
My variant of this bug says:
grub-install /dev/sda
/usr/sbin/grub-probe: error: no mapping exists for `md1'.
Auto-detection of a filesystem module failed.
Please specify the module with the option `--modules' explicitly.
grub-install --modules=/boot/grub/mdraid.mod /dev/sda
/usr/sbin/grub-probe: error: no mapping exists for `md1'.
/usr/sbin/grub-probe: error: no mapping exists for `md1'.
/usr/sbin/grub-probe: error: no mapping exists for `md1'.
You attempted a cross-disk install, but the filesystem containing /boot/grub
does not support UUIDs.
cat /proc/mdstat
md1 : active raid1 sdc1[3] sda1[0]
530100 blocks super 1.0 [3/2] [UU_]
i.e. is mdraid version 1.0 and not version 0.9
Th fs itself is ext4
I believe I will be able to work around this by not using raid for the
/boot directory, but this is annoying :-(
** Bug watch added: Debian Bug tracker #540549
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540549
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/484798
Title:
grub-probe: error: no mapping exists (with encrypted root disk)
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
