NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN528X drives constantly spinning even after a reboot, what is causing this?!
RN528X drives are being accessed, or are doing self-maintenance, or something, 24/7 and it's driving my wife nuts. I've tried looking at "Logging" - nothing there. How can I diagnose what the drives ...
StephenB wrote:The scheduled maintenance tasks (defrag, balance, disk test, scrub) would show up in the logs.
Do you use the file search feature or have antivirus enabled? Is the volume status saying it is degraded?
Have you downloaded the log zip file, and looked in there (particularly at the disk health info in disk-info.log)? There's a lot of info in the log zip that isn't shown in the web ui.
Hi StephenB ,
- File search is enabled, as is anti-virus. Are you suggesting one or both be disabled?
- Downloaded logs, dozens of files... where to look and what to look for?
- Under System--> Volumes the little pie chart and text don't indicate "degraded"... opened Settings (small wheel in the box containing pie chart), don't see anything in there that indicates "degraded". Where to look otherwise?
jimk1963 wrote:
- Under System--> Volumes the little pie chart and text don't indicate "degraded"... opened Settings (small wheel in the box containing pie chart), don't see anything in there that indicates "degraded". Where to look otherwise?
Those are the right places. If the volume isn't degraded, then it isn't resyncing (which would explain the disk activity).
jimk1963 wrote:
- File search is enabled, as is anti-virus. Are you suggesting one or both be disabled?
Both will generate disk activity when you aren't connected to the NAS. Perhaps try disabling file search first, and see if that helps.
StephenB wrote:
jimk1963 wrote:- Under System--> Volumes the little pie chart and text don't indicate "degraded"... opened Settings (small wheel in the box containing pie chart), don't see anything in there that indicates "degraded". Where to look otherwise?
Those are the right places. If the volume isn't degraded, then it isn't resyncing (which would explain the disk activity).
jimk1963 wrote:- File search is enabled, as is anti-virus. Are you suggesting one or both be disabled?
Both will generate disk activity when you aren't connected to the NAS. Perhaps try disabling file search first, and see if that helps.
Disabled File Search and Anti-Virus, no change. Opened every log file, found a few errors but unclear if they are the issue:
Under "systemd" logfile:
Jan 25 14:41:23 <ReadyNAS Name> tracker-miner-fs[4854]: (tracker-miner-fs:4854): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed
Jan 25 14:41:23 <ReadyNAS Name> tracker-miner-fs[4854]: (tracker-miner-fs:4854): GLib-GObject-CRITICAL **: g_object_notify_queue_thaw: assertion 'g_atomic_int_get(&object->ref_count) > 0' failed
Jan 25 14:41:23 <ReadyNAS Name> tracker-miner-fs[4854]: (tracker-miner-fs:4854): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failedUnder "kernel" logfile:
Jan 25 14:38:48 <ReadyNAS Name> kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -71
Jan 25 14:39:22 <ReadyNAS Name> kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 3 ret -71
Jan 25 14:41:40 <ReadyNAS Name> kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -71Under "tracker-miner-fs service" logfile:
Jan 25 14:01:47 <ReadyNAS Name> systemd[1]: Started tracker-miner-fs system service.
Jan 25 14:40:58 <ReadyNAS Name> tracker-miner-fs[4854]: Received signal:15->'Terminated'
Jan 25 14:40:59 <ReadyNAS Name> systemd[1]: Stopping tracker-miner-fs system service...
Jan 25 14:41:23 <ReadyNAS Name> tracker-miner-fs[4854]: (tracker-miner-fs:4854): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed
Jan 25 14:41:23 <ReadyNAS Name> tracker-miner-fs[4854]: (tracker-miner-fs:4854): GLib-GObject-CRITICAL **: g_object_notify_queue_thaw: assertion 'g_atomic_int_get(&object->ref_count) > 0' failed
Jan 25 14:41:23 <ReadyNAS Name> tracker-miner-fs[4854]: (tracker-miner-fs:4854): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed
Jan 25 14:41:23 <ReadyNAS Name> tracker-miner-fs[4854]: OK
Jan 25 14:41:23 <ReadyNAS Name> systemd[1]: Stopped tracker-miner-fs system service.Churning sound can be heard on this file.
https://drive.google.com/file/d/1XKNWAIVxT5_O5TNOh7JIjCEXy8fL4PkG/view?usp=sharing
The tracker stuff is file search, so if you turned that off you shouldn't be seeing these now.
USBDEVFS_CONTROL is coming from your UPS. Not sure on the specific cause, but it isn't uncommon - I see these with my own UPS too. However, the UPS is still working ok, and the NAS does shut down when the power drains.
Try disconnecting your NAS from the network for a while, and see if the disk activity stops.
If disconnecting from the network stops it, then check to see if you have the virus checker on a PC set to check or network drives or Windows to index them.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
