Hi, I was reading this one https://raid.wiki.kernel.org/index.php/RAID_Recovery I don't have any spare bays on that server...I'd have to make a trip to my datacenter and bring the drives back to my house. The bad thing is the 2 drives I replaced, failed a while ago, so they were behind. I was hoping I could still use the 4 drives I had before I did a grow on them. Do they need to be up-to-date or do I just need the config from them to recover the 3 drives that were still good? Oh, I originally started with 7, 2 failed a few moths back and the 3rd one just recently. FML Cheers, Curt On Wed, Oct 4, 2017 at 1:51 PM, Anthony Youngman <antlists@xxxxxxxxxxxxxxx> wrote: > On 04/10/17 18:18, Curt wrote: >> >> Is my raid completely fucked or can I still recover some data with >> doing the create assume clean? > > > PLEASE PLEASE PLEASE DON'T !!!!!! > > I take it you haven't read the raid wiki? > > https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn > > The bad news is your array is well borked. The good news is I don't think > you have - YET - managed to bork it irretrievably. A create will almost > certainly trash it beyond recovery!!! > > I think we can stop/revert the grow, and get the array back to a usable > state, where we can force an assemble. If a bit of data gets lost, sorry. > > Do you have spare SATA ports? So you have the bad drives you replaced (can > you ddrescue them on to new drives?). What was the original configuration of > the raid - you say you lost three drives, but how many did you have to start > with? > > I'll let the experts talk you through the actual recovery, but the steps > need to be to revert the grow, ddrescue the best of your failed drives, > force an assembly, and then replace the other two failed drives. No > guarantees as to how much data will be left at the end, although hopefully > we'll save most of it. > > Cheers, > Wol -- 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
