Yes, indeed - grub-probe -d /dev/md1 worked fine when running from my
previous 13.10 system as well as from the USB stick (Trusty 64bit desktop,
mdadm installed), but not after chroot to the /dev/md1 target.
I found that mdadm was not installed on /dev/md1, I installed it (and
Postfix) by hand, after which grub-install worked apparently fine.
There is one remaining oddity - even though the previous 13.10
installation on /dev/md0 is mounted (on /A), update-grub does not find
its kernel and hence does not add a boot entry for the 13.10 install.
Likewise, when the former was booted, and /dev/md1 was mounted as /B,
the 14.04 entry was not added. This behaviour is different from what I've
seen on other machines using physical partitions rather than md devices.
Is this expected? How can I fix this? Should I submit a dedicated bug
report?
Thanks for all your help!
Cheers,
Helge
----------------------------------------------------------------------------
Helge MEINHARD CERN, IT Department, CH-1211 Geneve 23, Switzerland
Phone: +41 22 76-76031, Fax: +41 22 76-69935
E-mail: helge.meinh...@cern.ch
On 07/05/14 17:39, Phillip Susi wrote:
> So sudo grub-probe -d /dev/md1 works ( prints "ext2 ) when run from the
> live cd. Does it work if you run it after the chroot?
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315344
Title:
Grub install failed on disks with software RAID
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1315344/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
