RE: Incorrect array member slot assignment during assemble

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

 



David Lethe (david@xxxxxxxxxxxx) wrote on 21 April 2008 22:54:
 >No, just assemble with --force.
 >
 > >The other idea I have in mind is to - after a backup - recreate the  
 > >array using the initial configuration (raid-level 5, num-devices 3,  
 > >etc), and hope that the array can pick itself up again.
 > >
 > >Any thoughts much appreciated - thanks for helping out :)
 >
 >This is the last alternative, when you're sure the 2 disks are fine.
 >Then just re-create the array replacing the /dev/3rd-drive by the
 >word "missing". This won't change the data, it'll just re-write the
 >superblocks. Then do read-only fsck

 >=======
 >
 >I would go pick up a few extra  disks, boot to a CDROM
 >LINUX  image, and make raw block copies of the disks on the RAID and

Yes, that's what I said in the first msg.

 >then try to reconstruct with the copies of the data.

Of course, if the originals have problems reconstruction will probably
abort again...
--
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