Re: How to recover a multiple raid5 disk failure with mdadm?

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

 



--Am Montag, 8. August 2005 09:18 +0200 Claas Hilbrecht <claas+maillinglists.linux-raid@xxxxxxxxxxxxxxxxx> schrieb:

The output below is from mdadm-2.0-devel-2 examine. What I don't
understand is that there is difference in the "Spare Devices".

Today I thought I could give the broken raid another try and use mdadm-2.0-devel-3. After looking again on the output of mdadm -E /dev/hde1 I think I had to repair this by hand. The

     Number   Major   Minor   RaidDevice State
this     3      33        1        3      active sync   /dev/hde1

  0     0       0        0    524288      spare
  1 3670016   65536    65536    393216      spare
  2     0       0    131072    589824      spare
  3 2162688   65536    196608    393216      spare
  4 3735552   65536    262144        0      spare

is totaly wrong. I think this is caused due to the bad checksum message in the mdadm -E output. Is there any way to fix this information with a disk editor or mdadm itself?

--
Claas Hilbrecht
http://www.jucs-kramkiste.de

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux