Wasn't there a change made recently to support the new md metadata
formats? I wonder if that is causing grub to detect the raid superblock
both at the end of the physical disk, as well as within the partition,
causing it to see the members twice?
On 5/3/2011 10:33 AM, Phillip Susi wrote:
After upgrading an Ubuntu server from Maverick to Natty ( grub2 version
1.99-rc1-13ubuntu3 ) the system no longer will boot. Grub complains
about the raid5 array:
error: Found two disks with the index 0 for RAID md0
error: Found two disks with the index 1 for RAID md0
error: Found two disks with the index 2 for RAID md0
error: Superfluous RAID member (4 found)
error: Unknown filesystem
This is a 4 disk raid5 array that mdadm still recognizes and looks fine,
with each disk having IDs 0 through 3 respectively. Despite the fact
that it complains about the raid, it still shows the LVM logical volumes
in the output of ls. The array is the sole LVM PV.
Bug filed at https://launchpad.net/bugs/776422. Any hints on how to
proceed with debugging this? Is there a way to check what modules are
built into the core image from the rescue shell?
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
