[Bug 1043096] Re: Use UUID for root file systems on /dev/md*

[Martin Pitt]

Helpful hint from Tom H: "the usual reason for mdadm to rename
"/dev/md0p1" "/dev/md127p1" is that the hostname of the system on which
the array's first assembled is stored in the md metadata and the array's
assembled with a different name on a system with a different hostname. A
simple solution would be for the array creation use "--homehost" whether
it's automated or manual."

-- 
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/1043096

Title:
  Use UUID for root file systems on /dev/md*

Status in “grub2” package in Ubuntu:
  New

Bug description:
  As part of the ongoing discussion about dropping alternates [1] I
  wanted to find out whether it's currently possible at all to install
  on a RAID with Ubiquity. Turns out it is possible [2], but there are
  two post-installation steps which are not obvious and should be fixed.

  Creating partitions with gparted and building a RAID with mdadm on the
  live system works well. Ubiquity detects the devices and you can
  partition /dev/md0 and install on it just fine. The trouble starts
  because you need to install mdadm into the target system, which is
  covered in bug 1043094.

  After that, booting fails because the generated grub configuration
  hardcodes /dev/md0p1, but initramfs/kernel create it as /dev/md127p1.
  It would be nice if grub/Ubiquity used UUIDs for the root partition as
  usual; in the initramfs /dev/disks/by-uuid/... exists just fine.

  After that, the installed system boots perfectly.

  [1] https://lists.ubuntu.com/archives/ubuntu-devel/2012-August/035675.html
  [2] https://lists.ubuntu.com/archives/ubuntu-devel/2012-August/035680.html

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