Prev: Installing memtest86 in Lenny fails to copy the actual binary
Next: Making use of volume control keys
From: d.sastre.medina on 1 Jun 2010 15:30
On Tue, Jun 01, 2010 at 03:31:41AM -0500, Stan Hoeppner wrote:
> d.sastre.medina(a)gmail.com put forth on 5/30/2010 4:45 PM:
> > On Sun, May 30, 2010 at 02:24:41PM -0500, Stan Hoeppner wrote:
> >> What happens when you use LILO instead of Grub?
> >
> > I haven't tried that yet.
> > [ snip ]
> > But first I'll need to refresh my LILO skills. It's been a while :)
>
> This is very old, but I think the basic information is still valid. BIOS has
> changed considerably in the past 10 years, and I'd assume is smarter across
> the sea of manufacturers. This should be taken into account regarding the
> enumeration of drives and the BIOS boot behavior.
>
> http://www.faqs.org/docs/Linux-mini/Boot+Root+Raid+LILO.html#ss3.1

It looks like my problem is init scripts related, so I'm working in
that direction for now.
Thanks for the link, I'll keep this around to survive the forthcomming
BootLoader Wars :-D

--
Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB
From: Tom H on 2 Jun 2010 09:00
On Mon, May 31, 2010 at 5:42 PM, <d.sastre.medina(a)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):
>
> 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 lvm present in some tests)
>        insmod ext2
>        set root='(md0)'
>        search --no-floppy --fs-uuid --set <here blkid /dev/md0>
>        echo    Loading Linux 2.6.32-3-686-bigmem ...
>        linux   /vmlinuz-2.6.32-3-686-bigmem root=UUID=<here blkid /dev/md1> ro rootdelay=15
>        echo    Loading initial ramdisk ...
>        initrd  /initrd.img-2.6.32-3-686-bigmem
> }
>
> It doesn't boot. Note a added `rootdelay=15' and removed `quiet' to be
> able to see what happens.
> 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.
>
> 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
>
> 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.

I agree. It's an initrd problem. You could start by deleting and
re-creating it with
update-initramfs -d -k...
update-initramfs -c -k...


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/AANLkTin92d6UrYFrTQlBFTwcpror4uPL6ImBA23RhT1H(a)mail.gmail.com
First  |  Prev  | 
Pages: 1 2 3
Prev: Installing memtest86 in Lenny fails to copy the actual binary
Next: Making use of volume control keys