NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Сhecksum errors in files on RAID5 Netgear ReadyNAS Pro 6 RNDP6000
Netgear ReadyNAS Pro 6 RNDP6000 RAID-5 (of 6 disks) 2TB FW 6.10.2 I got a checksum error message in the backup software. I was check disks and found on one many bad sectors. (using HDAT2 softw...
Roman304 wrote:
I have partitioned jbod raid drives into each drive. RAID number 4 checksum error.
That's a clear indication that your issue is either linked to that disk or to that slot. The next step is to figure out which.
I suggest destroying RAID 1,2,5,6, and removing those disks. Then power down the NAS, and swap RAID 3 and RAID 4. Power up and re-run the test on both volumes. That will let you know if the problem is linked to the disk or the slot.
If the problem disappears on both disks, then it could be power-related. You can confirm that by adding the removed disks back one at a time, and see when the problem starts happening again.
It seems incredibly strange that BTRFS would have a file get corrupted like this and not throw BTRFS errors all over the place.. What's in the journal would not match what's on the disk!
Are you absolutely sure there's not some application out there touching/modifying the files? Can you also track the modify date of the file ($ stat <file>)? Perhaps even turn on Auditing? It's a pretty major thing for a file to get changed like that silently, BTRFS should detect and report corruption as soon as you try to access the file.. Unless.... maybe you have turned off checksumming on your data volume?
DEADDEADBEEF wrote:
Are you absolutely sure there's not some application out there touching/modifying the files? Can you also track the modify date of the file ($ stat <file>)? Perhaps even turn on Auditing?
i am not sure... But i use default all services and nothing install outhere.
about $ stat <file> , file not modified, but checksum changed.
root@HQ-NAS-2:/RAID-5/TEST-FILE# dd if=/dev/urandom of=Test.flie bs=64M count=32 dd: warning: partial read (33554431 bytes); suggest iflag=fullblock 0+32 records in 0+32 records out 1073741792 bytes (1.1 GB, 1.0 GiB) copied, 103.885 s, 10.3 MB/s root@HQ-NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 0542952ac3e7e9d494a26a37c41a6c9e Test.flie root@HQ-NAS-2:/RAID-5/TEST-FILE# stat Test.flie File: 'Test.flie' Size: 1073741792 Blocks: 2097160 IO Block: 4096 regular file Device: 35h/53d Inode: 1049 Links: 1 Access: (0660/-rw-rw----) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2021-05-31 10:54:16.835309473 +0300 Modify: 2021-05-31 10:56:00.681735098 +0300 Change: 2021-05-31 10:56:00.681735098 +0300 Birth: - root@HQ-NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 0542952ac3e7e9d494a26a37c41a6c9e Test.flie root@HQ-NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 0efe119d6aba0648ba32fc722fd72095 Test.flie root@HQ-NAS-2:/RAID-5/TEST-FILE# stat Test.flie File: 'Test.flie' Size: 1073741792 Blocks: 2097152 IO Block: 4096 regular file Device: 35h/53d Inode: 1049 Links: 1 Access: (0660/-rw-rw----) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2021-05-31 10:54:16.835309473 +0300 Modify: 2021-05-31 10:56:00.681735098 +0300 Change: 2021-05-31 10:56:00.681735098 +0300 Birth: - root@HQ-NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie d289a229916a49bede053b9cdc778ec6 Test.flie root@HQ-NAS-2:/RAID-5/TEST-FILE# stat Test.flie File: 'Test.flie' Size: 1073741792 Blocks: 2097152 IO Block: 4096 regular file Device: 35h/53d Inode: 1049 Links: 1 Access: (0660/-rw-rw----) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2021-05-31 10:54:16.835309473 +0300 Modify: 2021-05-31 10:56:00.681735098 +0300 Change: 2021-05-31 10:56:00.681735098 +0300 Birth: -
DEADDEADBEEF wrote:Unless.... maybe you have turned off checksumming on your data volume?
where i can have turned off or turned on checksumming on data volume?
checksum was turned on only this box.
Checksum
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
