I added an older 3TB HDD to my SnapRaid and copied stuff there from my old RAID6. Then I made a sync which gave some I/O errors at the beginning but then ran fine for hours over the 3TB.
After this was done it did snapraid status which gave:
The oldest block was scrubbed 113 days ago, the median 113, the newest 0.
WARNING! The array is NOT fully synced.
You have a sync in progress at 1%.
The 2% of the array is not scrubbed.
You have 640547 files with zero sub-second timestamp.
Run the 'touch' command to set it to a not zero value.
No rehash is in progress or needed.
DANGER! In the array there are 51 errors!
They are from block 42264 to 50019, specifically at blocks: 42264 42265 42266 42267 42268 42295 42296 42297 42298 45004 45005 45006 45007 45008 45009 45010 45011 46764 46765 46766 46767 46768 46769 46770 46771 46772 49256 49257 49258 49259 49260 49261 49262 49263 49264 49265 49266 49267 49268 49269 49273 49274 49275 50012 50013 50014 50015 50016 50017 50018 50019
To fix them use the command 'snapraid -e fix'.
The errors will disappear from the 'status' at the next 'scrub' command.I now wonder what exactly an error means and how snapraid even discovered those. If there was an I/O error on the initial sync how can the parity be correct? Or did the I/O error simply result in an error beeing logged/synced instead of the real data.
I don't care so much about those blocks of data since it is from older stuff anyway but I would like to interpret the message.
On the other hand the drive I inserted seems unable to successfully run a SMART test (fatal error) so I will switch it out anyway. Should I snapraid -e fix the errors before? I am unsure if this would make anything better or worse since I am not sure if the fix will result in good data. Or would a fix try to re-read the faulty blocks again?
Thanks!
