Hi,
I may have done something stupid. A few days ago, my OMV NAS was unresponsive (no Web UI, no ssh, no Samba), and so I rebooted it after a few minutes (later I found some mails about exceeded resource limits, so that probably was the reason).
Now I did the first "snapraid sync" since the reboot, and I get lots of errors:
Code
Data error in file '/srv/dev-disk-by-label-Data4/file1.mkv' at position '1064', diff bits 73/128
Data error in file '/srv/dev-disk-by-label-Data3/file2.mkv' at position '232', diff bits 69/128
Data error in parity 'parity' at position '7632915', diff bits 1/2097152
Data error in parity 'parity' at position '7634385', diff bits 1/2097152
Data error in parity 'parity' at position '7635226', diff bits 1/2097152
Data error in parity 'parity' at position '7635622', diff bits 2/2097152
Data error in parity 'parity' at position '7638365', diff bits 1/2097152and even
Code
Verifying /srv/dev-disk-by-label-Data1/snapraid.content...
Verifying /srv/dev-disk-by-label-Data2/snapraid.content...
Verifying /srv/dev-disk-by-label-Data3/snapraid.content...
Verifying /srv/dev-disk-by-label-Data4/snapraid.content...
DANGER! Wrong file CRC in '/srv/dev-disk-by-label-Data3/snapraid.content.tmp'
Verified /srv/dev-disk-by-label-Data4/snapraid.content in 10 seconds
Verified /srv/dev-disk-by-label-Data1/snapraid.content in 10 seconds
Verified /srv/dev-disk-by-label-Data2/snapraid.content in 17 secondsSince the errors are on different disks and the disks are all healthy according to the SMART info, my guess is the problem is with the snapraid data (maybe I intererrupted the "snapraid sync"?).
fsck also looks good:
Code
root@orion:~# fsck -nA
fsck from util-linux 2.33.1
e2fsck 1.44.5 (15-Dec-2018)
Warning! /dev/sda1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda1: clean, 359178/1638400 files, 4789554/6553600 blocks
e2fsck 1.44.5 (15-Dec-2018)
e2fsck 1.44.5 (15-Dec-2018)
Warning! /dev/sdf1 is mounted.
Warning! /dev/sdb1 is mounted.
e2fsck 1.44.5 (15-Dec-2018)
e2fsck 1.44.5 (15-Dec-2018)
Warning! /dev/sde1 is mounted.
Warning! /dev/sdc1 is mounted.
e2fsck 1.44.5 (15-Dec-2018)
Warning! /dev/sdd1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Data2: clean, 559654/244191232 files, 1333942335/1953506385 blocks
Warning: skipping journal recovery because doing a read-only filesystem check.
Data3: clean, 93789/244191232 files, 1383491839/1953506385 blocks
Warning: skipping journal recovery because doing a read-only filesystem check.
Parity: clean, 14/244191232 files, 1479855674/1953506385 blocks
Warning: skipping journal recovery because doing a read-only filesystem check.
Data1: clean, 1984/244191232 files, 1476011393/1953506385 blocks
Warning: skipping journal recovery because doing a read-only filesystem check.
Data4: clean, 62591/244191232 files, 1386865878/1953506385 blocksNow my questions are: Am I right in thinking the data is OK, it's just the parity that's fucked up? If so, how do I fix it?