Bug#515676: After "dist-upgrade" from etch to lenny the system can no longer assemble and mount mdadm RAID drives

martin f krafft madduck at debian.org
Tue Feb 17 11:24:53 UTC 2009


also sprach S D <sundimi at yahoo.com> [2009.02.17.1126 +0100]:
> Tried it, the system drops into BusyBox on boot with seemingly the same messages that were already described: 
> ....
> md: no devices found for /dev/md1
> md: no devices found for /dev/md2
> md: no devices found for /dev/md3

I found the reason for this: you have md superblocks on
/dev/sd[abc], and /dev/md0 gets assembled from those. Since the
components of /dev/md[123] are partitions /dev/sd[abc][123] and thus
are no longer visible once /dev/md0 is assembled, that's all you
get.

I suppose your forgot about the superblock on /dev/md0.
The real question, however, is why mdadm insists on using it instead
of honouring your /etc/mdadm/mdadm.conf file.

Could you please set VERBOSE=true in /etc/default/mdadm and paste to
me the output of

  update-initramfs -vuk 2.6.26-1-686

Thanks,

-- 
 .''`.   martin f. krafft <madduck at d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20090217/58a3fde4/attachment.pgp 


More information about the pkg-mdadm-devel mailing list