Re: Problems with mdraid on initrd
On Mon, May 5, 2014 at 12:48 AM, Fredrik Tolf <fredrik@dolda2000.com> wrote:
>
> I recently upgraded to Wheezy a system that has its root filesystem on top
> of LVM and mdraid, and it gained a problem in booting, in that the initrd
> calls mdadm to scan for the mdraid devices before the kernel is done with
> detecting the physical drives on the machine. As such, mdadm sees none of
> its devices and initializes no arrays, and the initrd doesn't find the root
> filesystem.
>
> I can fix this easily during the boot process by simply waiting for the
> initrd to drop to a shell, and then scan for the mdraid devices and
> initialize LVM manually and then let the initrd continue booting, but it
> would be kinda nice if I didn't have to boot the system manually. :)
>
> Why would the initrd do this? What is the mechanism that normally makes the
> initrd wait for devices to be fully detected, and why doesn't work in this
> case? Could it have something to do with the fact that I'm running a
> custom-compiled kernel?
boot_delay and rootdelay are possible kernel cmdline parameters.
Reply to: