NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

tupholme's avatar
tupholme
Aspirant
Oct 05, 2018

RND4000 volume scan/RAID sync every day

Hi,

 

I have the ReadyNAS NV+ RND4000, up to date with the latest firmware. It's been running flawlessly for about ten years albeit with only light use. It powers down overnight and there are many days when I don't acually access it at all.

 

Just recently it's started performing a volume scan and RAID sync most days, of its own accord. I haven't changed anything myself. The log (short sample below) tells me that volume scan 'found and corrected errors', even though I may not have accessed any data since the last time. Yesterday I forced a volume scan and it found no errors, only for the device to do its own volume scan later on and find errors.

 

Looking at the SMART information for the disks, there doesn't seem to be anything anomalous (although I'm no expert) and no great difference between the stats for the three drives I have installed.

 

Any ideas what's going on, please?

 

 

Thanks,

 

Jeff

 

 

 

        Fri Oct 5 07:13:06 GMT 2018	System is up.
	Thu Oct 4 23:55:17 GMT 2018	System power-on scheduled for 10/05/2018 07:10
	Thu Oct 4 23:53:58 GMT 2018	RAID sync finished on volume C. The volume is now fully redundant.
	Thu Oct 4 19:40:40 GMT 2018	System is up.
	Thu Oct 4 19:36:48 GMT 2018	RAID sync started on volume C.
	Thu Oct 4 19:36:27 GMT 2018	Volume scan found and corrected errors.
	Thu Oct 4 10:44:25 GMT 2018	System is up.
	Thu Oct 4 10:41:37 GMT 2018	Volume scan found no errors.
	Thu Oct 4 08:52:57 GMT 2018	Rebooting device...
	Thu Oct 4 08:52:57 GMT 2018	Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
	Thu Oct 4 07:12:59 GMT 2018	System is up.
	Wed Oct 3 23:05:47 GMT 2018	System power-on scheduled for 10/04/2018 07:10
	Wed Oct 3 18:46:12 GMT 2018	RAID sync finished on volume C. The volume is now fully redundant.
	Wed Oct 3 18:44:11 GMT 2018	Disk on channel 2 reports a temperature of 55C / 131F.
	Wed Oct 3 18:35:08 GMT 2018	Disk on channel 2 reports a temperature of 55C / 131F.
	Wed Oct 3 18:26:08 GMT 2018	Disk on channel 2 reports a temperature of 55C / 131F.
	Wed Oct 3 14:32:59 GMT 2018	System is up.
	Wed Oct 3 14:28:59 GMT 2018	RAID sync started on volume C.
	Wed Oct 3 14:28:40 GMT 2018	Volume scan found and corrected errors.
	Wed Oct 3 07:12:53 GMT 2018	System is up.
	Wed Oct 3 01:40:24 GMT 2018	System power-on scheduled for 10/03/2018 07:10
	Wed Oct 3 01:38:29 GMT 2018	RAID sync finished on volume C. The volume is now fully redundant.
	Tue Oct 2 21:25:29 GMT 2018	System is up.
	Tue Oct 2 21:21:20 GMT 2018	RAID sync started on volume C.
	Tue Oct 2 21:21:00 GMT 2018	Volume scan found and corrected errors.
	Tue Oct 2 07:12:45 GMT 2018	System is up.
	Mon Oct 1 23:05:44 GMT 2018	System power-on scheduled for 10/02/2018 07:10
	Mon Oct 1 07:12:56 GMT 2018	System is up.

 

14 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User

    Have you looked in the log zip file for more details on the volume scans?

    • tupholme's avatar
      tupholme
      Aspirant

      Thanks, I'd overlooked that option. This is what I'm getting repeated in fs_check.log:

       

       

      ***** File system check performed at Thu Oct  4 17:41:50 GMT 2018 *****
      fsck 1.40.11 (17-June-2008)
      e2fsck 1.40.11 (17-June-2008)
      c was not cleanly unmounted, check forced.
      Pass 1: Checking inodes, blocks, and sizes
      Pass 2: Checking directory structure
      Pass 3: Checking directory connectivity
      Pass 4: Checking reference counts
      Pass 5: Checking group summary information
      c: 134393/178307072 files (5.6% non-contiguous), 319068372/356589568 blocks

       

       

      I note the "c was not cleanly unmounted, check forced." line! I'm slightly reassured that it's not something worse data-wise, but given that I'm not aware of any external reasons why there could be spontaneous outages, e.g., power cuts, it leads me to think that the ReadyNAS is fully rebooting itself. In other words, the volume scan is a symptom not the problem in itself.

       

      If I then look in the system.log I can see this (filtered):

       

      Oct  4 07:11:43 nas-01-B6-06 kernel: Boot type/reason: rtc/0/0
      Oct  4 10:43:25 nas-01-B6-06 kernel: Boot type/reason: normal/2/0
      Oct  4 19:39:41 nas-01-B6-06 kernel: Boot type/reason: normal/0/0

      The first of these events was when it woke up in the morning, the second was when I forced a reboot and the third was spontaneous. Thus we can see there is something non-routine going on, but I'm not sure where to go from here. Frontview always shows reasonable operating temperatures and I haven't had issues with any of my other equipment on the same circuit having crashes etc..

       

      Thanks for any advice offered!

       

       

      Jeff

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        I guess there could be something going on with the power, but I'm thinking it's more likely to be a failing PSU or maybe a system board component.

         

        Given the age of the NAS, replacing it might be the best option.  You could replace the PSU with some effort, but of course we don't really know if that's the cause or not.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More