Re: Re-add not selecting drive for correct slot?

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

 



On Sat, 8 Aug 2015, Thomas Fjellstrom wrote:

I did try that :( It fails to assemble because it only sees sdc as a spare.
Maybe because I did things with the old mdadm first, and did a --remove? That
seems to have wiped out the "slot" information (it's -1) so the assemble force
magic can't figure things out? Just a guess on my part.

Unless someone else has a better idea, I'd say you're right. If you would have unplugged the failed drive (so it disappeared completely), it could probably have been re-added. So unless you have a copy of the old superblock, your only way to proceed now is to use --create --assume-clean and get all the parameters right (order, offsets etc). There are lots of examples in the mailing list archives of people trying this and some actually suceeding.

--
Mikael Abrahamsson    email: swmike@xxxxxxxxx
--
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