On Wed Feb 24, 2010 at 06:35:46PM +0100, Stefan G. Weichinger wrote:
> Am 24.02.2010 18:09, schrieb Robin Hill:
>
> > If these are the only disks with up-to-date data, and sda4 is still
> > failing, I can only suggest stopping the array and using dd/dd_rescue to
> > copy sda4 onto a working disk. You should then be able to reassemble
> > the array with sdb4 and the new disk, then add in a hot spare to
> > recover.
>
> Currently sdd isn't in use at all.
>
> So I could
>
>
> mdadm --stop /dev/md4
>
> ddrescue /dev/sda4 /dev/sdd4
>
> mdadm --assemble --force /dev/md4 /dev/sdb4 /dev/sdd4
>
> ??
>
Yes, that'd be what I'd recommend - the ddrescue will only need to make
a single pass across sda4 (except for failed blocks of course), so will
have the lowest risk of exacerbating the disk problems. Of course, the
practicality of doing the assemble will depend on the number of
unreadable blocks found by ddrescue.
Good luck!
Robin
--
___
( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
Attachment:
pgpXlmrZ6juIc.pgp
Description: PGP signature
