Matthias Urlichs wrote:
Hi,
Michael Tokarev:
$ mdadm -A /dev/md7 /dev/hd[bceij]1
This worked.
Matthias, please provide your /etc/mdadm/mdadm.conf
entries for the array in question (/dev/md7). From
the description of your problem it seems it is due
to incorrect content of the array entry in there --
not all and wrong devides are listed. If I'm right,
please try booting with correct mdadm.conf contents.
No, that's not it.
The mdadm.conf is rather simple:
DEVICE partitions
[ other arrays ]
ARRAY /dev/md7 uuid=8303b89b:70284d24:1f751455:b2e2c40d
I can boot correctly *now*, but of course
I have no missing disks any more...
Aha. I mis-read your initial bugreport - i didn't notice
you where starting your array manually.
Anyway. Looks like more info is needed.
You said your array didn't come up during boot, but provided
a command line which you executed which failed:
$ mdadm -A /dev/md7 /dev/hd[bceijkl]1
mdadm: failed to add /dev/hdk1 to /dev/md7: Invalid argument
mdadm: failed to add /dev/hdl1 to /dev/md7: Invalid argument
mdadm: /dev/md7 assembled from 3 drives - not enough to start the array.
At this point, the situation should be something like:
mdadm have choosen to use 5 drives out of 7 - only 3 of
hd[bceij]1 (first 5) and hd[kl]1. Why it did so is impossible
to say - as there's no additional error messages, it means
mdadm tried to open all 7 devices in turn, found everything
is ok, but descided not to touch 2 of them. Or, another
possible cause, there wasn't all of the nodes in question
present in /dev, so shell wildcard expanded to less than 7
entries.
for some reason, kernel didn't like the 2 last devices
(hd[kl]1) and complained. dmesg should contain more info
(incl. exact reason why kernel didn't like the two) --
and the dmesg from that time still *may* be in your logs.
So finally, the thing tried to start 7-drive array out of
3 drives, which obviously didn't work.
If you still have dmesg from that time, showing failed attempt
to assemble the array, it may be possible to understand what's
going on. If not, I guess we will never know...
/mjt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
