[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [ squeeze ] Grub2 RAID1 LVM2 boot failure



I think my previous post requires some more info:

I've got three HDs, two of them (twin disks) have two partitions,
one /boot partition (md0) and the other one for LVM filesystems (md1),
where root_vg-root_lv lives (among others). The third disk is unpatitioned,
and has one only lv (var_lv)

So, provided this autogenerated grub.cfg entry:

menuentry "Debian GNU/Linux, with Linux 2.6.32-3-686-bigmem" --class debian --class gnu-linux --class gnu --class os {
        insmod raid
        insmod mdraid
        insmod ext2
        set root='(md0)'
        search --no-floppy --fs-uuid --set 785366b0-d597-4e9c-9284-b6b9161236ed
        echo    Loading Linux 2.6.32-3-686-bigmem ...
        linux   /vmlinuz-2.6.32-3-686-bigmem root=/dev/mapper/root_vg-root_lv ro  rootdelay=25 quiet
        echo    Loading initial ramdisk ...
        initrd  /initrd.img-2.6.32-3-686-bigmem
}

...and compared to the examples in the grub wiki¹:

Example grub.cfg for LVM

Below is a sample grub.cfg using LVM. Linux is installed under
MainGroup-linuxLV where MainGroup is the VolumeGroup und linuxLV is
the logical volume. Notice that vmlinuz (the linux kernel) and
initrd.img are lying in the logical volume and can be accessed by
symlinks.

set timeout=20
set default=0
menuentry "Linux on LVM" {
        insmod lvm
        set root=(MainGroup-linuxLV)
        linux /vmlinuz root=/dev/mapper/MainGroup-linuxLV
        initrd /initrd.img
} 

Example grub.cfg for RAID

This is an example of grub.cfg when the /boot filesystem is on a RAID
device.

insmod raid
set root=(md0)
search --fs-uuid --set 155c8fdb-607f-45a4-bd6d-0dd89f21eac2

menuentry "Linux" {
        insmod raid
        set root=(md0)
        search --fs-uuid --set 155c8fdb-607f-45a4-bd6d-0dd89f21eac2
        linux    /vmlinuz-2.6.31 root=LABEL=root ro
        initrd   /initrd.img-2.6.31
} 

I can't find documented the scenario when /boot resides in /dev/md0
and root filesystem is mounted in /dev/mapper/root_vg-root_lv (md1, in
my case).

Removing the `quiet' option shows LVM log lines appearing *before*
mdadm lines, which suggest some timming issues in the init scripts(?).

Again, any hints are appreciated.

Regards.

¹ http://grub.enbug.org/LVMandRAID

-- 
Huella de clave primaria: 0FDA C36F F110 54F4 D42B  D0EB 617D 396C 448B 31EB

Attachment: pgpz83de5phte.pgp
Description: PGP signature


Reply to: