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.
dmesg on boot nothing about RAID-5 /dev/md127
root@NAS-2:~# dmesg | grep md0 [ 31.068901] md: md0 stopped. [ 31.075222] md/raid1:md0: active with 6 out of 6 mirrors [ 31.075307] md0: detected capacity change from 0 to 4290772992 [ 31.602526] BTRFS: device label 33ea55f9:root devid 1 transid 467355 /dev/md0 [ 31.603155] BTRFS info (device md0): has skinny extents [ 33.369153] BTRFS warning (device md0): csum failed ino 117932 off 2420736 csum 3710567192 expected csum 4039208015 [ 33.378234] BTRFS warning (device md0): csum failed ino 117932 off 3203072 csum 2302637777 expected csum 2765412742 [ 39.711268] BTRFS warning (device md0): csum failed ino 26800 off 2105344 csum 3723732640 expected csum 4129019946 root@NAS-2:~# dmesg | grep md1 [ 31.100266] md: md1 stopped. [ 31.108850] md/raid10:md1: active with 6 out of 6 devices [ 31.108933] md1: detected capacity change from 0 to 1604321280 [ 34.218589] md: md127 stopped. [ 34.246979] md/raid:md127: device sda3 operational as raid disk 0 [ 34.246985] md/raid:md127: device sdf3 operational as raid disk 5 [ 34.246988] md/raid:md127: device sde3 operational as raid disk 4 [ 34.246990] md/raid:md127: device sdd3 operational as raid disk 3 [ 34.246993] md/raid:md127: device sdc3 operational as raid disk 2 [ 34.246996] md/raid:md127: device sdb3 operational as raid disk 1 [ 34.247777] md/raid:md127: allocated 6474kB [ 34.247926] md/raid:md127: raid level 5 active with 6 out of 6 devices, algorithm 2 [ 34.248112] md127: detected capacity change from 0 to 9977158696960 [ 34.658138] Adding 1566716k swap on /dev/md1. Priority:-1 extents:1 across:1566716k [ 34.670593] BTRFS: device label 33ea55f9:RAID-5 devid 1 transid 27093 /dev/md127 [ 34.980123] BTRFS info (device md127): has skinny extents root@NAS-2:~# dmesg | grep md127 [ 34.218589] md: md127 stopped. [ 34.246979] md/raid:md127: device sda3 operational as raid disk 0 [ 34.246985] md/raid:md127: device sdf3 operational as raid disk 5 [ 34.246988] md/raid:md127: device sde3 operational as raid disk 4 [ 34.246990] md/raid:md127: device sdd3 operational as raid disk 3 [ 34.246993] md/raid:md127: device sdc3 operational as raid disk 2 [ 34.246996] md/raid:md127: device sdb3 operational as raid disk 1 [ 34.247777] md/raid:md127: allocated 6474kB [ 34.247926] md/raid:md127: raid level 5 active with 6 out of 6 devices, algorithm 2 [ 34.248112] md127: detected capacity change from 0 to 9977158696960 [ 34.670593] BTRFS: device label 33ea55f9:RAID-5 devid 1 transid 27093 /dev/md127 [ 34.980123] BTRFS info (device md127): has skinny extents
What log file do you recommend watching?
There are a lot of them in zip.
Problem not solved after reboot.
root@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, 104.607 s, 10.3 MB/s root@NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 5c07ebd42dc2af232c0431d3b86cab7d Test.flie root@NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 5c07ebd42dc2af232c0431d3b86cab7d Test.flie root@NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 433c2099b00285f11ed88d0c7d580f32 Test.flie root@NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 38b511f0129c3ac888f19a430b3938c8 Test.flie root@NAS-2:/RAID-5/TEST-FILE# md5sum Test.flie 38b511f0129c3ac888f19a430b3938c8 Test.flie
Nothing errors in GUI after rebuild.
/dev/md127:
Version : 1.2
Creation Time : Mon Mar 16 21:27:21 2020
Raid Level : raid5
Array Size : 9743319040 (9291.95 GiB 9977.16 GB)
Used Dev Size : 1948663808 (1858.39 GiB 1995.43 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Update Time : Fri May 28 17:29:02 2021
State : clean
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Consistency Policy : unknown
Name : 33ea55f9:RAID-5-0 (local to host 33ea55f9)
UUID : 04d214c4:ee331e6a:74ca0a04:5e846481
Events : 977
Number Major Minor RaidDevice State
6 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
2 8 35 2 active sync /dev/sdc3
3 8 51 3 active sync /dev/sdd3
4 8 67 4 active sync /dev/sde3
5 8 83 5 active sync /dev/sdf3cat /sys/block/md127/md/mismatch_cnt 0
What other test can i do?
Roman304 wrote:
What log file do you recommend watching?
system.log, kernel.log, and system-journal.log
StephenB wrote:
Roman304 wrote:What log file do you recommend watching?
system.log, kernel.log, and system-journal.log
in kernel.log
May 30 14:35:29 NAS-2 kernel: mdcsrepair[13627]: segfault at 2325238 ip 00000000004048df sp 00007fff08ffa500 error 4 in mdcsrepair[400000+10000] May 30 14:35:29 NAS-2 kernel: sh (13626): drop_caches: 3 May 30 14:35:29 NAS-2 kernel: sh (13625): drop_caches: 3 May 30 14:35:29 NAS-2 kernel: mdcsrepair[13639]: segfault at 1cd6230 ip 00000000004048df sp 00007ffeba060c50 error 4 in mdcsrepair[400000+10000] May 30 14:35:29 NAS-2 kernel: mdcsrepair[13640]: segfault at bfe230 ip 00000000004048df sp 00007ffe6f442530 error 4 in mdcsrepair[400000+10000] May 30 14:35:30 NAS-2 kernel: sh (13647): drop_caches: 3 May 30 14:35:30 NAS-2 kernel: sh (13648): drop_caches: 3 May 30 17:47:16 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 6852608 csum 846329252 expected csum 429493038 May 30 17:47:16 NAS-2 kernel: sh (9521): drop_caches: 3 May 30 17:47:17 NAS-2 kernel: sh (9522): drop_caches: 3 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 2220032 csum 4138936066 expected csum 3680012373 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 5521408 csum 988873707 expected csum 286883169 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 5603328 csum 2031798327 expected csum 1425106784 May 30 20:41:32 NAS-2 kernel: sh (2563): drop_caches: 3 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 6266880 csum 1389706193 expected csum 2134807686 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 6754304 csum 1977957496 expected csum 1477350191 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 6754304 csum 1977957496 expected csum 1477350191 May 30 20:41:32 NAS-2 kernel: sh (2567): drop_caches: 3 May 30 20:41:32 NAS-2 kernel: sh (2569): drop_caches: 3 May 30 20:41:32 NAS-2 kernel: mdcsrepair[2571]: segfault at 1fd5230 ip 00000000004048df sp 00007ffe294f0c30 error 4 in mdcsrepair[400000+10000]
what is mean - mdcsrepair segfault ?
i found problems in logs on root device /dev/md0
in system-journal.log
May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 2220032 csum 4138936066 expected csum 3680012373 May 30 20:41:32 NAS-2 mdcsrepaird[2862]: mdcsrepaird: mdcsrepair /dev/md0 622764032 4096 fdd84c09 aa77a724 //var/readynasd/db.sq3 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 5521408 csum 988873707 expected csum 286883169 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 5603328 csum 2031798327 expected csum 1425106784 May 30 20:41:32 NAS-2 kernel: sh (2563): drop_caches: 3 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 6266880 csum 1389706193 expected csum 2134807686 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 6754304 csum 1977957496 expected csum 1477350191 May 30 20:41:32 NAS-2 kernel: BTRFS warning (device md0): csum failed ino 26800 off 6754304 csum 1977957496 expected csum 1477350191 May 30 20:41:32 NAS-2 kernel: sh (2567): drop_caches: 3 May 30 20:41:32 NAS-2 mdcsrepaird[2862]: mdcsrepair: repairing /dev/md0 @ 622764032 [//var/readynasd/db.sq3] succeeded. May 30 20:41:32 NAS-2 kernel: sh (2569): drop_caches: 3 May 30 20:41:32 NAS-2 kernel: mdcsrepair[2571]: segfault at 1fd5230 ip 00000000004048df sp 00007ffe294f0c30 error 4 in mdcsrepair[400000+10000] May 30 20:41:32 NAS-2 mdcsrepaird[2862]: mdcsrepaird: mdcsrepair /dev/md0 626065408 4096 14fc0ec5 9e82e6ee //var/readynasd/db.sq3 May 30 20:41:32 NAS-2 mdcsrepaird[2862]: mdcsrepaird: mdcsrepair /dev/md0 626147328 4096 c837e586 9f980eab //var/readynasd/db.sq3 May 30 20:41:32 NAS-2 mdcsrepaird[2862]: mdcsrepaird: mdcsrepair /dev/md0 626810880 4096 2ec42aad 796bc180 //var/readynasd/db.sq3 May 30 20:41:32 NAS-2 mdcsrepaird[2862]: mdcsrepaird: mdcsrepair /dev/md0 627298304 4096 87c31a8a d06cf1a7 //var/readynasd/db.sq3 May 30 20:41:33 NAS-2 kernel: sh (2616): drop_caches: 3 May 30 20:41:33 NAS-2 kernel: sh (2617): drop_caches: 3 May 30 20:41:33 NAS-2 mdcsrepaird[2862]: mdcsrepair: designated data mismatches bad checksum /dev/md0 @ 626065408 May 30 20:41:33 NAS-2 kernel: sh (2620): drop_caches: 3 May 30 20:41:33 NAS-2 kernel: sh (2619): drop_caches: 3 May 30 20:41:33 NAS-2 mdcsrepaird[2862]: mdcsrepair: designated data mismatches bad checksum /dev/md0 @ 627298304 May 30 20:41:33 NAS-2 kernel: sh (2618): drop_caches: 3 May 30 20:41:33 NAS-2 kernel: sh (2622): drop_caches: 3 May 30 20:41:33 NAS-2 mdcsrepaird[2862]: mdcsrepair: designated data mismatches bad checksum /dev/md0 @ 626147328 May 30 20:41:33 NAS-2 kernel: sh (2621): drop_caches: 3 May 30 20:41:33 NAS-2 kernel: sh (2623): drop_caches: 3 May 30 20:41:33 NAS-2 mdcsrepaird[2862]: mdcsrepair: designated data mismatches bad checksum /dev/md0 @ 626810880
Can we conclude that my device is completely defective and the operating system does not work correctly? What can I do about it?
Roman304 wrote: Can we conclude that my device is completely defective and the operating system does not work correctly? What can I do about it?It looks that way to me. The csum errors say that files are damaged in the OS partition, and the segmentation faults mean that the repair attempt was either reading or writing to an illegal memory location.
Failing memory is a possibility, and could explain the symptoms. You could try running the memory test from the boot menu. Note the test will keep running until it finds an error. I'd stop it at 3 passes (unless of course it finds an error).
How much memory do you have in the Pro-6?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
