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

Re: [ squeeze ] Grub2 RAID1 LVM2 boot failure



d.sastre.medina@gmail.com wrote:

> Thanks for the comments and help.
> 
> I have edited /boot/grub/grub.cfg to match my devices by UUID as
> proposed, getting UUIDs from blkid /dev/md{0,1} (previously I run
> blkid -g):

Good.

> It doesn't boot.

Bummer.

> Note a added `rootdelay=15' and removed `quiet' to be
> able to see what happens.

Good thinking.

> Still LVM tries to initialize before mdadm (is that correct, anyway?),
> and ends up waiting for the root filesystem until I'm dropped to busybox.
> While at the initramfs prompt, simply by issuing `vgchange -ay' and
> exiting (Ctrl-D) I can boot the box. Luckily, I had a PS2 keyboard
> around, because the USB one wouldn't work.

Ah, good, so, grub correctly detects the kernel and initrd files and loads 
them. The kernel then takes control and starts the initramfs process which 
you are reporting as failing.

This is further down the boot process than any grub or kernel.

Have you tried the:

	update-initramfs -u

command to reconstruct the initramfs file used?


> The output of `vgchange -ay' might be informative. Here is one
> example, but one line is output for each LV:

> udevd-work[number]:kernel provided name 'dm-2' and
> NAME='mapper/root_vg-var_lv' disagree, please use SYMLINK+= or change
> the kernel to provide the proper name.
> 
> This looks like #581715 or #581593.
> In both reports, however, it is said it's a harmless warning.
> I can confirm that, at least, while testing the

Yes, it's a harmles warning.
 
> linux   /vmlinuz-2.6.32-3-686-bigmem root=/dev/mapper/root_vg-root_lv

> variant, I can boot the system from initramfs after
> `vgchange -ay' + <Ctrl-D>
> regardless the warnings.
 
> After booting, running `upgrade-grub or upgrade-grub2' won't help.
> This looks like a problem elsewhere (udev, initramfs-tools, ...), but
> not grub.

Try the `update-initramfs -u` command. It may solve the issue, if that 
doesn't work, contact the initramfs maintainer, or file a bug, that will 
solve the problem.

Good luck.
 

-- 
Antonio Perez


Reply to: