NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
"Scrub" killed my NAS :( #27023882
I used to have scrubs running monthly... (recently changed to every 3 months, but now I'll have to disable completely.)
I started a scrub on Jun 16th, at 17:00. By 11pm on the 17th, it was only at around 33%. By 1am, it was spitting out warnings that it failed to make snapshops. Around the same time, my windows machine lost it's iSCSI connection to the NAS.
By 10am the same morning, the entire NAS was locked up. None of the blue activity LED's were flashing, I could ping it, but the web interface wouldn't respond, I couldn't ssh into it, none of the shares worked, The front display didn't work (and even tapping the power button didn't work!!!)
I ended up having to hard reset the NAS (press/hold the power button.)
I see there have been previous threads about scrub's starting to take a VERY LONG time or other scrub issues, but those threads don't ever seem to be properly resolved. They just either fade away or the poor victim ends up factory reseting their NAS. (On the other hand, I didn't see any other threads where the person let it run until the entire thing was locked up.)
Obviously, I've hard reset the NAS so it's no longer locked up, but I did download the logs in case someone from netgear perhaps wants to, perhaps, postmortem the issue.
Please let me know who to send them it...
(Edit: it's running 6.5.0)
Gary
16 Replies
Replies have been turned off for this discussion
jak0lantash wrote:
Let's wait and see what NETGEAR says about it.Yeah.. umm.. that's why I posted the thread.. (to hopefully get someone from netgear to help with the issue.) The case number was only created so that I could send/attach the logs.
I'm going to try (Again - for the 3rd time) to do a scrub. This time, unlike other times, I've uninstalled PLEX and turned off transmission. I got the impression from various other threads that sometimes having PLEX running can tie up resources (and in one case, a person had mysql active even when PLEX was installed but turned off.) While those things shouldn't completely mess up a scrub, I'm willing to try it...
The logs are not attached to your case. Email them in (see the Sending Logs link in my sig) with the case number mentioned in the email subject and someone should be able to attach them.
Support cases are the official way to contact support.
Whilst there is some NETGEAR monitoring of the community it's mainly here for engaging with your fellow users.
Plex doesn't use MySQL. Perhaps you are thinking of another app. Scrubbing does put the disks under heavy use, but if there is a disk problem or perhaps something (other than the scrub) is using a lot of resources then things could take quite a while longer than usual or the scrub may even fail to complete.
In the "kernel.log" from that log download, there are hundreds of log entries like these during the scrub. No idea if it's related, though:
Jun 17 02:06:21 Nas516 kernel: [394512.602748] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:06:56 Nas516 kernel: [394547.636456] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:07:46 Nas516 kernel: [394597.750539] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:08:11 Nas516 kernel: [394623.114471] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:08:56 Nas516 kernel: [394668.100414] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:09:05 Nas516 kernel: [394676.732246] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:10:22 Nas516 kernel: [394753.454576] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:10:23 Nas516 kernel: [394754.347364] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units) Jun 17 02:10:23 Nas516 kernel: [394754.746430] md: delaying requested-resync of md126 until md127 has finished (they share one or more physical units)
case number is 27023882 (logs are uploaded to that case)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
