Re: Debian Unstable won't boot on 2.6.15-1/grub/raid1
On Wed, Mar 22, 2006 at 10:53:02PM +0100, Florian Kulzer wrote:
> Robert Harris wrote:
> > I have a system that runs root on raid. There are currently 2
> >kernels installed in the system.
> >
> > 2.6.15-1 and 2.6.10-1. If I boot up on 2.6.16-1 the system will
> >say it can't find my root filesystem on /dev/md0 and drop me into the
> >busybox shell. If I imediately drop into 2.6.10-1 it boots fine.
> >2.6.15-1 configuration looks good. The only odd part is it seems
> >that the md devices are actually initialized after grub tries to boot
> >them. Once i get the busybox prompt I get the md startup output.
>
> Do you use udev rules to ensure a consistent naming of your devices?
> Otherwise Kernel 2.6.15 is much less predictable than 2.6.10, and
> unexpected changes in the device names might be the reason for your
> problem.
udev is not involved until after the root filesystem is mounted. The
problem is in the initrd, which prepares the system to mount root. The
initrd can be rebuilt with dpkg-reconfigure kernel-image-<version>.
The 2.6.15 kernel package on backports.org, at least, wants to use yaird
(although you can tell it to use mkinitrd). This problem is probably
a yaird bug (or bad yaird config). Robert, try rebuilding the initrd,
and if it still doesn't work, either switch back to initrd-tools or fix
yaird. It probably just needs to be told /dev/md0 is your rootfs.
(The thing to do first is make sure grub is actually loading the correct
initrd image; however, I would guess it is, since the initrd-tools
initrd, rather than launching a shell, lamely lets the kernel panic when
it can't mount the rootfs).
Reply to: