Re: Trying to rescue a RAID-1 array

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

 



On 01/04/2022 21:23, Bruce Korb wrote:
Because if it did your data is probably toast, but if it didn't we might
be home and dry.

If I can figure out how to mount it (read only), then I can see if a
new FS was installed.
If it wasn't, then I've got my data.

That looks promising then. It looks like your original array may have been v1.0 too ... a very good sign.

Read up on loopback devices - it's in the wiki somewhere on recovering your raid ...

What that does is you stick a file between between the file system and whatever's running on top, so linux caches all your writes into the file and doesn't touch the disk.

Let's hope xfs_recover didn't actually write anything or we could be in trouble.

The whole point about v1.0 is - hallelujah - the file system starts at the start of the partition!

So now you've got loopback sorted, FORGET ABOUT THE RAID. Put the loopback over sdc1, and mount it. If it needs xfs_recover, because you've got the loopback, you can let it run, and hopefully it will not do very much.

IFF the wind is blowing in the right direction (and there's at least a decent chance), you've got your data back!

If it all goes pear shaped, it may well still be recoverable, but I'll probably be out of ideas. But the loopback will have saved your data so you'll be able to try again.

Oh - and if it looks sort-of-okay but xfs_recover has trashed sdc1, at least try the same thing with sde1. You stand a chance that xfs_recover only trashed one drive and, the other being an exact copy, it could have survived and be okay.

Cheers,
Wol



[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