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

Bug#705454: d-i puts wrong amount of spares into target mdadm.conf

Package: debian-installer


when using d-i to install Debian on a system with RAID,
which we normally preconfigure on the second console in
the shell with a few commands, mdadm.conf is wrong.

We use something like this:

mdadm --create --level=1 -n 4 --spares=1 /dev/md0 /dev/sd{a,b,c,d,e}1
mdadm --create --level=10 -n 4 --spares=1 /dev/md1 /dev/sd{a,b,c,d,e}2

Then put LVM on md1 and use d-i to put /boot on md0
and the rest of the system on LVs.

The mdadm.conf d-i generates for us in the target,
with these settings, have “spares=1” for md0 and
“spares=2” for md1 for some unknown reason, which
makes the mdadm cronjob (rightfully) warn about
missing spares. Changing it to “spares=1” for md1
too using a text editor makes it succeed.

I think the mdadm.conf here is generated by d-i
somehow, as it’s put into the target, but feel
free to reassign this around.

This happens both with d-i from April 2012 and from
April 2013 (though I built the images I used myself
on a sid system from sid sources), so I thought I’d
better report this, in case there’s some mishandling
of systems with more than one md device (TTBOMK grub
doesn’t yet boot from RAID-10, does it?).

tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Sebastian Mancke

Reply to: