Hi Roland.
I want to upgrade a drive from 250GB to 1TB, if I copy all data with the same folder structure and I assing the same drive letter to the new drive, my parity data will be still valid?
Hi Roland.
I want to upgrade a drive from 250GB to 1TB, if I copy all data with the same folder structure and I assing the same drive letter to the new drive, my parity data will be still valid?
Yes. Just swap the drives, and copy all your files over to the new drive. You don't even have to maintain the drive letter, if you update the entry in config.txt for that drive to point at the new drive letter. Or keep the old letter and you don't have to change config.txt.
Sorry for the delay in responding, I've been on the road for the last couple of days.
No problem, thanks!
One more thing: the act of copying all the files from one drive to another will probably reset the file creation timestamps for every file. This will cause disParity to notice that the files may have changed on the next update, and recalculate the hash code on each file to see whether it changed or not. This will cause the update to take a while, but I think that in the end if all goes well it won't actually add or remove anything.
Hey Roland,
Would it be possible to just 'recover' to the new, bigger drive, having replaced the smaller drive with the bigger one first?
I figure it skips having to mount both drives for the copy, and maybe no need for hash recalcs since it's a restore?
I'll probably have to try/do something like this when I swap out a 500GB for a 1TB.
That's an interesting idea, and off the top of my head I can't think of any reason why it wouldn't work. Only issue I guess is that "copying" the files via the recover command would be a whole lot slower than a straight disk-to-disk copy.
As for the hash check, that wouldn't be avoided by doing this, since the file creation timestamps would still have changed since the last update (the "restore" command doesn't update the file meta data.)
You must log in to post.