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

Bug#338200: marked as done (root raid should use mdadm --config=partitions)

Your message dated Mon, 05 May 2008 10:23:24 +0200
with message-id <1209975804.535384.28665.nullmailer@xanadu.blop.info>
and subject line initrd-tools has been removed from Debian, closing #338200
has caused the Debian Bug report #338200,
regarding root raid should use mdadm --config=partitions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
338200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338200
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: initrd-tools
Version: 0.1.84

currently for a root on md raid mkinitrd does something like this:

mdadm -A /dev/md3 -R -u 2b3a5b77:c7b4ab81:a2b8322a:db5c4e88 /dev/sdb4 /dev/sda4

however this has the problem that it will require the root raid devices to 
always reside at /dev/sda4 and /dev/sdb4.  in practice it's way more 
desirable to let mdadm go find the root devices using the UUID -- so that 
if you have to shuffle drives/controllers around the system will still 
boot without problems.  the way to do this is:

mdadm -A /dev/md3 -R --config=partitions -u 2b3a5b77:c7b4ab81:a2b8322a:db5c4e88

note that the devices aren't specified at all -- mdadm will look at any 
and all partitions for raid superblocks with the specified UUID.

i'd suggest using --config=partitions by default and possibly providing a 
mkinitrd.conf option to revert to the explicit device name list.

-dean

--- End Message ---
--- Begin Message --- 
Version: 0.1.84.2+rm

The initrd-tools package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/393092 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.
-- 
Lucas

--- End Message ---
Reply to: