NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN104 Resync Speed on 3rd Drive Replacement Very Slow
I am updating my RN104 from 4 8Tb drives to 4 10Tb drives. After replacing the first drive, the resync took a couple of days to complete. After replacing the second drive, about the same length of time. Now, I have replaced the third drive and the resync is going very, very slowly. After two days it is only at 53.7% and the estimate says it has 1240 hours to go. Is this normal? When I have updated drives in the past, each drive took about the same time to resync. This is the first time I can remember one drive taking so much longer than others.
Thanks.
I rebooted the NAS and the resync speed increased to about 14 Mb/sec. I don't know what was causing the slow down before.
I do have backup jobs running Rsync. This particular NAS does not have any backups configured on it, but it is the NAS that recieves backups from another NAS.
19 Replies
Replies have been turned off for this discussion
Ken6432-1 wrote:
After two days it is only at 53.7% and the estimate says it has 1240 hours to go. Is this normal?
That is unusually slow. Is the NAS doing something else (backup jobs, scheduled maintenance activities, or under a heavier usage then other times)? Resync is a lower priority task than other things, so it will run slower when there is more going on.
I suggest downloading the log zip file, and looking for disk errors in system.log and kernel.log
If ssh is enabled, you can get a better sense of the progress with cat /proc/mdstat and query the smart stats interactively with smartctl.
No backups running at this time although there were some running during the sync so maybe that was slowing things some.
In the kernel.log I see a large number of ethernet errors:
May 13 00:36:55 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512
May 13 00:36:55 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896
May 13 00:39:03 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:39:04 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:39:04 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:09 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896
May 13 00:39:10 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:39:10 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:11 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:39:12 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:12 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:39:12 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=768
May 13 00:39:13 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:39:13 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
May 13 00:39:14 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:14 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:15 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=144
May 13 00:39:17 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:39:25 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:32 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:37 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=144
May 13 00:39:37 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:38 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=504
May 13 00:39:39 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:40 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
May 13 00:39:40 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1280
May 13 00:39:40 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=768
May 13 00:39:42 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0d830000 (overrun error), size=16
May 13 00:39:43 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:39:48 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896
May 13 00:39:48 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=768
May 13 00:39:54 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=272
May 13 00:39:57 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:40:07 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=400
May 13 00:40:10 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:40:18 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:40:20 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0d830000 (overrun error), size=16
May 13 00:40:32 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:40:34 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1152
May 13 00:40:37 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=272
May 13 00:40:47 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896
May 13 00:40:57 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:40:57 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=440
May 13 00:40:58 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
May 13 00:41:04 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=768
May 13 00:41:17 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:41:20 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:41:20 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=640
May 13 00:41:21 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896
May 13 00:41:26 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
May 13 00:41:28 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
May 13 00:41:29 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=448
May 13 00:41:29 Media-Backup kernel: mvneta d0070000.ethernet eth0: bad rx status 0f830000 (overrun error), size=896
May 13 11:43:56 Media-Backup kernel: nr_pdflush_threads exported in /proc is scheduled for removalI wouldn't think this would impact the sync speed, though.
In the system.log I see a number of failed log in attempts which is strange. Some of them say the attempt is coming from 192.168.1.1 which would be the gateway server, correct?
May 12 21:46:38 Media-Backup sshd[3419]: Invalid user Retford from 192.168.1.1
May 12 21:46:38 Media-Backup sshd[3419]: input_userauth_request: invalid user Retford [preauth]
May 12 21:46:38 Media-Backup sshd[3419]: pam_unix(sshd:auth): check pass; user unknown
May 12 21:46:38 Media-Backup sshd[3419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=gateway
May 12 21:46:38 Media-Backup sshd[3420]: SSH: Server;Ltype: Authname;Remote: 192.168.1.1-59610;Name: root [preauth]
May 12 21:46:38 Media-Backup sshd[3420]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=gateway user=root
May 12 21:46:39 Media-Backup sshd[3421]: SSH: Server;Ltype: Authname;Remote: 192.168.1.1-59611;Name: [preauth]
May 12 21:46:39 Media-Backup sshd[3421]: Invalid user from 192.168.1.1
May 12 21:46:39 Media-Backup sshd[3421]: input_userauth_request: invalid user [preauth]
May 12 21:46:39 Media-Backup sshd[3421]: Failed none for invalid user from 192.168.1.1 port 59611 ssh2
May 12 21:46:39 Media-Backup sshd[3421]: Connection closed by 192.168.1.1 [preauth]Does this tell you anything?
The cat command gives:
Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md1 : active raid10 sdd2[3] sdc2[2] sdb2[1] sda2[0]
1044480 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]md125 : active raid1 sdd5[0] sdc5[1]
1952278144 blocks super 1.2 [2/2] [UU]md126 : active raid5 sdb4[6] sdd4[4] sda4[3] sdc4[5]
11720633664 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [UU_U]
resync=DELAYEDmd127 : active raid5 sdb3[6] sda3[7] sdd3[4] sdc3[5]
11706500352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/3] [U_UU]
[================>....] recovery = 84.3% (3290015080/3902166784) finish=7 593.8min speed=1343K/sec
bitmap: 0/30 pages [0KB], 65536KB chunkmd0 : active raid1 sdb1[6] sda1[7] sdd1[4] sdc1[5]
4190208 blocks super 1.2 [4/4] [UUUU]unused devices: <none>
The resync=DELAYED is interesting. What does this mean?
Thanks again for you help.
You have a multi-layer volume due to incremental drive size upgrades. Each layer is it's own RAID, and it can only sync one at a time. So the delayed one is waiting for the another to complete. The multiple layers may be contributing to the slower speed.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
