Bug#287415: mdadm: degraded md devices not assembled on boot

martin f krafft madduck at debian.org
Mon Jul 24 21:22:01 UTC 2006


also sprach Mau <mavog at hotmail.com> [2006.07.24.2138 +0100]:
> Assembling RAID array md0...done (already running).

Mh, why only md0? This is past the initrd stage...

> [/sbin/fsck.ext3 (1) -- /tmp] fsck.ext3 -a -C0 /dev/md2

well, the above explains this...

> root@(none):~# /etc/init.d/mdadm-raid start
> Assembling RAID array md0...done (already running).
> Assembling RAID array md2...failed (no devices found).
> Assembling RAID array md4...failed (no devices found).
> Assembling RAID array md5...failed (no devices found).
> root@(none):~#
> 
> [ ... and md1? it's a swap partition; trying something else ... ]
> 
> root@(none):~# mdadm -Av /dev/md2
> mdadm: looking for devices for /dev/md2
> mdadm: /dev/sda6 had wrong uuid.
> mdadm: /dev/sda5 had wrong uuid.
> mdadm: no recogniseable superblock on /dev/sda4
> mdadm: /dev/sda4 had wrong uuid.
> mdadm: cannot open device /dev/sda2: Device or resource busy
> mdadm: /dev/sda2 had wrong uuid.
> mdadm: cannot open device /dev/sda1: Device or resource busy
> mdadm: /dev/sda1 had wrong uuid.
> mdadm: cannot open device /dev/sda: Device or resource busy
> mdadm: /dev/sda had wrong uuid.
> mdadm: /dev/sda3 is identified as a member of /dev/md2, slot 0.
> mdadm: no uptodate device for slot 1 of /dev/md2
> mdadm: added /dev/sda3 to /dev/md2 as 0
> mdadm: /dev/md2 has been started with 1 drive (out of 2).
> root@(none):~#

This is *weird* and rather disconcerting.

Would it be much trouble for you to repeat the process and run

  sh -x /etc/init.d/mdadm-raid start

this time, and paste the output in an email to me?

> - why can't mdadm-raid assemble the arrays?
> - why can't mdadm-raid even find /dev/md1?

I don't have answers yet.

Is this a production machine? The reason I am asking is because it
would be a lot easier for me if you could give me root access, but
of course I understand that's only rarely possible...

> I also noticed that in /etc/init.d/mdadm-raid there is
> RUNDIR=/var/run/mdadm
> AUTOSTARTED_DEVICES=$RUNDIR/autostarted-devices
> but in my case /var is still unmounted when mdadm-raid is called: when
> the box will be up no /var/run/mdadm/autostarted-devices will be found.
> I really can't figure out if this is sane.

This is a very good point. I must remove this feature at once. :)

Dumb me.

Do share your full name with me so I can credit you for this,
please?

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`.     martin f. krafft <madduck at debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20060724/dad23b29/attachment.pgp


More information about the pkg-mdadm-devel mailing list