NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN628X V6.10.4 Unresponsive both with usage of SMB Shares as the admin webconsole
Since a couple of days my RN628X is becoming slower and slower and had reached the point that I can't use it any longer. Everything seems to function correctly and I don't see any erorrs, but opening...
Yes I did serval times. I don'have a clue what is causing the non responsiveness. It is really painfull and makes it that I can't use my NAS any longer. I have removed the scheduled maintenance jobs on my volume as they were taking an extreme long periode (more than 5 days) and during this period the performance was bad, but even then the performance was way better than it is now. Is there a maintenance task I should perform now that could help?
Have you looked in system.log and kernel.log for errors?
What are you seeing in loadavg.log?
How full is the data volume?
Hi StephenB I am certainly not an expert on how to read the logs, but in the kernel.log I see these entries:
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319872 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319880 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319888 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319896 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319904 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319912 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319920 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319928 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798322560 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798322568 on sdc3)I guess this is Disk 3 that has the blue light not shining blue constantly whereas the other disks do shine blue almost all the time. Could it be a disk failure that occupies the NAS heavily? I don't see any error and also the health of the disk seems to be oke.
loadavg.log -> here is an example (not sure how to read this):
01:46:37 up 27 days, 5:03, 0 users, load average: 2.22, 2.60, 2.63
The data volume has a free size of 17.76TB of the total of 36.36TB.
If it is an eminent disk failure I would expect an error message, but I can't see any. All signs are green. Is there a test I can perform or something?
ronaldvr2132 wrote:
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319872 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319880 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319888 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319896 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319904 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319912 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319920 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798319928 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798322560 on sdc3)
Jan 24 14:02:08 RN628X-1 kernel: md/raid:md127: read error corrected (8 sectors at 6798322568 on sdc3)I guess this is Disk 3 that has the blue light not shining blue constantly whereas the other disks do shine blue almost all the time. Could it be a disk failure that occupies the NAS heavily? I don't see any error and also the health of the disk seems to be oke.
FYI, all these are saying there are disk errors on disk 3. Definitely test it, but I think you'll end up replacing it.
If you enable SSH and connect to the NAS via it, top can help you determine if there is a runaway process eating all the assets. But you might also get similar results if you are experiencing a lot of retries on the network. Have you tried another cable and connection on your router/switch?
I have reclaced hard disk 3 with a spare that I had, the volume was resynced and is reducndant again and now the led is the same blue as the other disks and the performance seems to be the same as before. So it seems to have something to do with the hard disk, but there has been no message whatsover that the disk has an issue. The health data did not show any error either. I would expect that an disk error would be showing up in the logs and I also would expect an alert to be send via e-mail. Has anyone an idea why I was not informed and furthermore the disk itself has still warranty, but if it will be tested I am afraid it will show up as fully functional. Any advice?
ronaldvr2132 wrote:
the disk itself has still warranty, but if it will be tested I am afraid it will show up as fully functional. Any advice?
I think you should just test it in a Windows PC with vendor tools - Lifeguard for WDC, Seatools for Seagate.
Run both the long generic (non-destructive) test and the full erase test.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
