Re: Problem with md: Not rebuilding rai5

[Nico Schottelius <nico-kernel20060829@schottelius.org>]

[-- Attachment #1: Type: text/plain, Size: 2475 bytes --]

Neil Brown [Tue, Aug 29, 2006 at 07:26:52PM +1000]:
> On Tuesday August 29, nico-kernel20060829@schottelius.org wrote:
> > Hello!
> > 
> > I created a degrated raid5 on top of md1 and hde1. Then moved the data
> > from /dev/hdk to the mounted raid5, and then added hdk1 (repartitoned)
> > to the array. The sync began, but after that hde1 was faulty.
> 
> So you created a raid5 containing one drive that was already faulty.
> That is unfortunate!

And reported in the manpage of mdadm to be usable (simply specify "missing"
as keyword).

> > I removed it, readded it, but now I've a raid5 with only one active
> > disk (which should not be possible imho, a raid5 always needs 2 disks)
> > AND what's even stranger for me, I've two spare disks.
> 
> If you have a raid5 with 2 working drives and one fails, how many
> working drives do you expect to be left?  1.  So the raid is no longer
> fully functional.

That is what I also thought. But there are some points that make me
wonder:
   a) why is hdk1 marked as spare? I added it this morning and the
   rebuilt began. Though something happened (I do not know what)
   and made hdk1 not beeing in the array. (dmesg output
   is now available at
   http://home.schottelius.org/~nico/linux/debug/raid/raid5.strange.dmesg)

   b) what's the reason, linux does not mark md2 as faulty?

> You might be able to read some data, but you want
> able to write.
> What did you expect to happen when hde1 failed?

I expected hdk1 and md1 to work.

> > Is there a way to force rebuilding the array?
> 
> Well, you can create the array over md1 and hde1 again, and your data
> should still be there, but it will just  fail again whenever it tries
> to access the block on hde1 which is bad.

That's clear.

> I suggest you:
>   - recreate the array over md1 and hde1
>   - copy the data back to hdk
>   - stop the array
>   - replace hde1
>   - make the array.
>   - read the entire array (dd > /dev/null) to make sure it is safe
>   - copy data back from hdk

Will linux detect, that md1 and hde1 are from the same array
and will it see which harddisk is xored with which one?

Perhaps this is the only way to go. I hope I did not loose too much
data with my 'moving to raid5'-experiement.

Thanks for the suggestions so far!

Nico

-- 
``...if there's one thing about Linux users, they're do-ers, not whiners.''
(A quotation of Andy Patrizio I completely agree with)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]