Bug#615893: grub-common: menu crashes and lvm/md disks detected incorrectly

[Colin Watson]

On Tue, Mar 01, 2011 at 07:23:46AM +1100, Craig Small wrote:
> I apologise if this is a duplicate.  I didn't get a response from the
> BTS and cannot find my bug anywhere.  I suspect I killed off the
> reportbug before I sent it.
> 
> In short, this is what is going wrong:
>   * My disks are being incorrectly detected
>   * A reboot halts at cannot find /init
>   * The grub menu crashes if the lines are too long

How long is "too long"?  I don't remember noticing any particular length
limit - did you happen to keep a note of how long it needed to be before
it fell over?

> I have my root drive on a LVM partition called elmo-root and /boot is on
> (md0).  While some of the grub setup clauses such as 00_header and
> 05_debian_theme have the right disks, 10_linux sets the root to md0 and
> detects the UUID of md0 too.  This plainly does not work too well at
> boot time.

Why "plainly"?  It sounds like you're saying that this obviously can't
work, but GRUB is supposed to have RAID support and in general I believe
it to work.  If it's not working for you then certainly we need to
investigate that.

> I got around this problem by going to the grub prompt and doing the
> following:
>     insmod raid,mdraid09,part_msdos
>     search --set=root -l root (detected correct elmo-root LVM)
>     linux (md0)/vmlinuz....   init=/sbin/init (must be not too long!!)
>     initrd (md0)/initrd.....
>     boot

Could you attach /boot/grub/grub.cfg so that I can compare it with what
you're entering by hand?

-- 
Colin Watson                                       [cjwatson at debian.org]