Re: [RFH] Errata and announcement help need
* martin f krafft <madduck@debian.org> [2010-02-11 12:23]:
> > Actually, it seems that root on RAID made with the new mdadm
> > doesn't boot. I'll try to investigate soon.
>
> The problem could be #492897?
I don't think so. This is on an ARM machine which boots from flash.
The problem is that the ramdisk never activates the RAID device, and
so it waits for root.
When I install testing with an installer that uses 3.0.3-2 everything
works. But when the installer uses the 3.1.1-1 udeb but installs
3.0.3-2 (from testing) it doesn't. I see the following when the
ramdisk is generated:
Feb 10 19:51:07 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-kirkwood
Feb 10 19:51:08 in-target: mdadm: cannot open /dev/md/0: No such file or directory
Feb 10 19:51:08 in-target: mdadm: cannot open /dev/md/0: No such file or directory
/dev/md/0 doesn't exist - only /dev/md0 does.
/etc/mdadm/mdadm.conf in the ramdisk contains this:
DEVICE partitions
HOMEHOST <system>
ARRAY /dev/md/0 metadata=1.1 UUID=f8d6999e:0d277d4a:ed6ff136:2bd5f46a name=NAS8C4EB8:0
Does this give any clues? If not, what kind of information would be
useful? Do you think this probably would go away if the 3.1.1-1 deb was
installed on the main system rather than 3.0.3-2 from testing?
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: