I lost a hard drive, one partition had data protected by disparity, the other partition had windows, where the config file was at. I have no recent back up of the windows partition (sigh, stupid me), so is there any way to figure out the config based on the parity data?
disParity » General Discussion
Recover the config file?
(3 posts)-
Posted 4 years ago #
-
Possibly!
What you'll need to reconstruct yourself is that the roots were of all the data drives. The parity meta data deliberately does not store the root of the drive (this allows you to do some tricky things like move drives around in your array and avoid having to do any parity recalculation if you just update your config file correctly to represent the new arrangement.)
I assume that if you saw what the file names were on each of the data drives, you could figure out what the roots were again, either from inspecting your remaining data drives, or from memory in the case of the one lost partition?
You can open the meta data files (files0.dat, files1.dat, etc.) in a binary file editor, and you should be able to see text file names of the files on that drive.
So for example if you open files0.dat and you see some .mkv files in there that you know are on the G: drive, then you know data1 must be G:\. The only possibly confusing thing is you have to remember that "data1" in the config.txt corresponds to files0.dat, "data2" is files1.dat, etc.
-Roland
Posted 4 years ago # -
Thanks Roland!
I tried that and it mostly worked. I was able to recover 70% of the files, the rest failed the hash check ( I checked some text files, complete garbage ). I think part of the problem is all of a sudden a few files on other drives are being detected as changed. I presume somehow the file got corrupted. I run updates every night, so I'm not sure what happened.Regardless, awesome piece of software. This is now the second time it has saved me time and heartache! Now to find something to protect that pesky windows drive.
Posted 4 years ago #
Reply
You must log in to post.