I have a failed disk (d5) and am attempting to restore the files on the failed disk to another disk in the array that has enough free space on it to store all the recovered files. I ran the below fix command after changing my config (see before and after disk failure configs below). However, it only recovered less than 1TB of the estimated 5.8TB worth of data on the disk. The fix.log (which I had to split into 18 different files because of their size) shows all kinds of error such as the following:
msg:error: Reading data from missing file '/mnt/data/disk18/media/tv/Series/Season/filename1.mkv' at offset 0.
error:0:d5:media/tv/Series/Season/filename1.mkv: Read error at position 0
msg:error: Missing file '/mnt/data/disk18/media/movies/Movie/filename2.mkv'.
error:0:d18:media/movies/Movie/filename2.mkv: Open error at position 0
entry:0:block:known:bad:d5:media/tv/Series/Season/filename1.mkv:0:
Hello :) You can't perform a restore to an existing disk in your array (meaning you can't name the same disk twice like /mnt/data/disk18 in this case). You will need to replace disk d05 with a new, formatted, and mounted disk to properly perform this restore. I'm honestly surprised it even let you do this in the first place without throwing an error (I guess it threw 18 files worth of errors).
I wish I had a cheaper answer (I hope you have an extra disk or two at home), but put in a new disk, and you'll be back in business.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm... Leifi really knows SnapRAID, so I wouldn't want to contradict previous advice that appears to have worked, because Andrea even contributed to the conversation. I've never done a restore like this, so I can't speak to it. I know that replacing the disk works as I've done that a few times over the years.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No doubt. The disk is under warranty so it will be replaced soon. All the spare drives I have are larger (14TB) then my parity drives (10TB). Any problem with using one to replace the failed disk (assuming I'd only be able to use 10TB of it until I upgrade parity) until I'm back up and running at which point I will upgrade the parity drives as well?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a failed disk (d5) and am attempting to restore the files on the failed disk to another disk in the array that has enough free space on it to store all the recovered files. I ran the below fix command after changing my config (see before and after disk failure configs below). However, it only recovered less than 1TB of the estimated 5.8TB worth of data on the disk. The fix.log (which I had to split into 18 different files because of their size) shows all kinds of error such as the following:
Fix Command
Before Disk Failure Config
After Disk Failure Config
Hello :) You can't perform a restore to an existing disk in your array (meaning you can't name the same disk twice like /mnt/data/disk18 in this case). You will need to replace disk d05 with a new, formatted, and mounted disk to properly perform this restore. I'm honestly surprised it even let you do this in the first place without throwing an error (I guess it threw 18 files worth of errors).
I wish I had a cheaper answer (I hope you have an extra disk or two at home), but put in a new disk, and you'll be back in business.
So this is not accurate then?
https://sourceforge.net/p/snapraid/discussion/1677233/thread/205b97b5/?limit=25#f527
Hmm... Leifi really knows SnapRAID, so I wouldn't want to contradict previous advice that appears to have worked, because Andrea even contributed to the conversation. I've never done a restore like this, so I can't speak to it. I know that replacing the disk works as I've done that a few times over the years.
No doubt. The disk is under warranty so it will be replaced soon. All the spare drives I have are larger (14TB) then my parity drives (10TB). Any problem with using one to replace the failed disk (assuming I'd only be able to use 10TB of it until I upgrade parity) until I'm back up and running at which point I will upgrade the parity drives as well?
No problem at all and you can use as much drive capacity as you want as long as you leave enough space for the parity file.
Last edit: David 2021-10-04
Do you mean the snapraid.content file?
EDIT: Nvmd, I realize now you meant the snapraid.parity file on the parity disk.
Last edit: IamSpartacus 2021-10-05
If I delete all files off a disk and then run a fix on that disk, it should restore all files that existed from the last run sync?
Yes