NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Roman304
May 27, 2021Aspirant
С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...
- Jun 04, 2021
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.
mdgm
May 27, 2021Virtuoso
Did you have bit-rot protection turned on or disabled on the share?
The checksum of the test file changing would seem to suggest bad RAM (memory) or a loose RAM module as a possibility. Have you run the memory test boot menu option?
- Roman304May 27, 2021Aspirant
Bit-rot Protection was disabled for all share. RAM (Memory) was tested by MemTest86 - No error (7 laps).
I create file under ReadyNAS os directly on mountpoint /RAID-5- StephenBMay 27, 2021Guru - Experienced User
Roman304 wrote:
Bit-rot Protection was disabled for all share.
I create file under ReadyNAS os directly on mountpoint /RAID-5I understood that from your commands.
Not sure what happened, as of course md5sum should have generated the same result the second time. Of course the volume is degraded, so any other disk errors can't be corrected by RAID parity.
So a read error or file system error could account for it - which is why I suggested looking in the log zip for any errors that occured while the commands were being executed. You could substitute journalctl if you prefer to use ssh.
You might also try rebooting the NAS and see if you can reproduce the error.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!