I have a ReadyNAS 104 FW 6.6.1. I have 4x 3TB drives in RAID 5 with about 6TB of data. I recently did a full reset and restored all my data. This is the first scrub after that.
I started the scrub over 8 days ago and it is only at 15.5%!!! It is not dead, it is very slowly progressing. Luckily, the NAS is functional during this but this is rediculous. I have checksums on, no virus scanner, and the only thing running is stock DLNA.
The top command shows:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15673 root 20 0 0 0 0 R 28.8 0.0 89:22.51 kworker/u2:1 23180 root 20 0 0 0 0 R 28.8 0.0 26:03.81 kworker/u2:5 26359 root 20 0 0 0 0 R 28.1 0.0 1:54.39 kworker/u2:7 1042 root 20 0 0 0 0 S 3.2 0.0 472:55.50 md127_raid5 2403 root 19 -1 218312 37916 8984 S 1.6 7.5 174:43.55 readynasd 6093 root 19 -1 19736 1368 1200 S 1.6 0.3 228:23.57 btrfs 972 root 0 -20 0 0 0 S 1.0 0.0 107:51.50 kworker/0:1H 2893 root 20 0 16736 6352 3484 S 0.6 1.2 0:10.47 apache2 4773 admin 20 0 17044 7236 4148 S 0.6 1.4 0:00.62 apache2 25892 root 20 0 5680 2568 2136 R 0.6 0.5 0:06.95 top 2257 root 20 0 1888 1360 1264 S 0.3 0.3 0:06.78 wsdd2 2891 root 20 0 1752 1220 1148 S 0.3 0.2 0:00.09 apache_log 6090 root 39 19 0 0 0 R 0.3 0.0 66:21.05 md127_resync
Any ideas why this is so bad? In the past scrubs have taken 3-6 days which is also horrible but this is much worse.
The RN104 as a lowend nas is just lacking enough resources to conduct bitrot protection. If you have enabled that you might want to consider to switch this to disabled. With bitrot protection status "disabled" scrubbing is meaningless to my understanding and you should stop conducting it. It is just putting lots of stress on the disks and you are not getting any benefit of it.
Defrag and balance are ok, though.
Netgear moderators please correct me, in case I'm wrong on this.
With bitrot protection status "disabled" scrubbing is meaningless to my understanding and you should stop conducting it.
Bitrot protection works with RAID scrubbing to recover files when there is silent corruption. But RAID scrubbing has value even if bitrot protection is off. So I think your recommendation is incorrect.
No, I do not have disk spindown enabled. Today, things are finally progressing at a resonable rate. It is finally up to 63% and will hopefully be done some time tomorrow, but still, that will be about 10 days!
Then be so kind to share the advantage(s) of doing scrub with bitrot protection off, please.
You are going off topic, but I will answer anyway.
The scrub maintenance task includes both a btrfs scrub and a raid scrub. Note that the raid scrub is available on older OS 4.2.x readynas as it's own maintenance function (even though OS4.2 has no bitrot protection).
The btrfs scrub provides some verification of the file system integrity, even if there are no checksums. The raid scrub also verifies that all the parity blocks in the RAID system are consistent with the data blocks. If a bad disk block is encountered during either scrub, the block should be re-allocated and it's contents reconstucted from the remaining data+parity blocks. And of course, the SMART logs will track the reallocated and pending sectors that are uncovered.
There are some posts about scrubs not being useful with jbod volumes (and checksums turned off). But that's a different setup than what we have here. Even then, I suspect that scrubs in those cases might still have some diagnostic value.
