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

Bug#566192: initramfs-tools: md0 device not recognized at boot after upgrade to kernel 2.6.30

reassign 566192 mdadm
severity 566192 grave

On Thu, Jan 21, 2010 at 09:52:08PM +0100, Louis Richard Pirlet wrote:
> I upgraded my kernel from 2.6.26 to 2.6.30 and could not boot the system
> over the new kernel. I still can boot it from the old 2.6.26 kernel.
> My root disk is  on a mirror raid based on 2 SCSI disk. The boot process
> stopsand gives a message to the effect that the file system is unavailable.
> I have an extended knowledge on hardware (I used to be a DEC/Compaq/HP
> harware support engineer on pdp11/VAX/alpha under VMS and Tru64). I have
> no indepth knowledge of the linux system.
> I think there is a problem with the initramfs-tools because there is no
> mdadm.conf describing my md devices... In fact there is no mdadm directory
> under etc in the initrd.img- created by the upgrade.

Inclusion of mdadm.conf in initramfs is the responsibility of the mdadm
hook, not of initramfs-tools itself.  Reassigning.

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Attachment: signature.asc
Description: Digital signature

Reply to: