Readynas Pro 6 rebooting during resync - after factory reset

[daminite]

Need help since I factory rest my Readynas it seems to reboot during the resyncing process

Here is what I see in logs from admin page:

Tue Dec 8 2015 10:51:56		Volume: Resyncing started for Volume data.
Tue Dec 8 2015 10:51:01		System: ReadyNASOS background service started.
Tue Dec 8 2015 10:50:59		System: ReadyNASOS service or process was restarted.
Tue Dec 8 2015 9:29:21		Volume: Resyncing started for Volume data.
Tue Dec 8 2015 9:28:26		System: ReadyNASOS background service started.
Tue Dec 8 2015 9:28:24		System: ReadyNASOS service or process was restarted.

Here are what I see in the readynasd logs:

Dec 08 08:22:49 Server readynasd[2295]: DEBUG: NAS_SEND_MSMTP_RUN: Fail. (status=77. error_buf=(null))
Dec 08 08:22:49 Server readynasd[2295]: Could not send email
Dec 08 08:22:51 Server readynasd[2295]: Exit main thread by SIGTERM.
Dec 08 08:23:33 Server readynasd[2295]: readynasd is halted.
Dec 08 08:28:38 Server readynasd[2294]: readynasd log started
Dec 08 08:28:38 Server readynasd[2294]: readynasd started. (restarted=0)
Dec 08 08:28:51 Server readynasd[2294]: ResetFailedUnit: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
Dec 08 08:28:51 Server readynasd[2294]: ReadyNASOS background service started.
Dec 08 08:29:46 Server readynasd[2294]: Resyncing started for Volume data.
Dec 08 08:29:48 Server readynasd[2294]: DEBUG: NAS_SEND_MSMTP_RUN: Fail. (status=77. error_buf=(null))
Dec 08 08:29:48 Server readynasd[2294]: Could not send email
Dec 08 09:28:14 Server readynasd[2301]: readynasd log started
Dec 08 09:28:14 Server readynasd[2301]: readynasd started. (restarted=0)
Dec 08 09:28:24 Server readynasd[2301]: Last run started at 1449592129 was aborted
Dec 08 09:28:24 Server readynasd[2301]: Detect abnormal shutdown of readynasd and child without core
Dec 08 09:28:24 Server readynasd[2301]: ReadyNASOS service or process was restarted.
Dec 08 09:28:26 Server readynasd[2301]: ResetFailedUnit: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
Dec 08 09:28:26 Server readynasd[2301]: ReadyNASOS background service started.
Dec 08 09:29:22 Server readynasd[2301]: Resyncing started for Volume data.
Dec 08 09:29:24 Server readynasd[2301]: DEBUG: NAS_SEND_MSMTP_RUN: Fail. (status=77. error_buf=(null))
Dec 08 09:29:24 Server readynasd[2301]: Could not send email
Dec 08 10:50:49 Server readynasd[2315]: readynasd log started
Dec 08 10:50:49 Server readynasd[2315]: readynasd started. (restarted=0)
Dec 08 10:50:59 Server readynasd[2315]: Last run started at 1449595704 was aborted
Dec 08 10:50:59 Server readynasd[2315]: Detect abnormal shutdown of readynasd and child without core
Dec 08 10:50:59 Server readynasd[2315]: ReadyNASOS service or process was restarted.
Dec 08 10:51:01 Server readynasd[2315]: ResetFailedUnit: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
Dec 08 10:51:01 Server readynasd[2315]: ReadyNASOS background service started.
Dec 08 10:51:56 Server readynasd[2315]: Resyncing started for Volume data.
Dec 08 10:51:58 Server readynasd[2315]: DEBUG: NAS_SEND_MSMTP_RUN: Fail. (status=77. error_buf=(null))
Dec 08 10:51:58 Server readynasd[2315]: Could not send email

I have tried to reseat the RAM, factory reset again through boot menu, reinstall OS from boot menu.

Running: 6.4.1

Anyone have any idea what might be the cause?

[mdgm-ntgr]

Have you checked the health of your disks?

[daminite]

I am running brand new WD 3TB drives

[StephenB]

---

@daminite wrote:

I am running brand new WD 3TB drives

---

Check the SMART stats anyway.

[daminite]

Here is the data I think you are requesting. Only thing I see abnormal is the command error on disk 6

	realloc_sect	realloc_evnt	spin_retry_cnt	ioedc	cmd_timeouts	pending_sect	uncorrectable_err	ata_errors	timestamp	time
--------------------	------------	------------	--------------	----------	------------	------------	-----------------	----------	----------	----------	---------
Disk1	0	0	0	0	0	0	0	0	1449531196	12/7/2015	23:33:16
Disk2	0	0	0	0	0	0	0	0	1449531196	12/7/2015	23:33:16
Disk3	0	0	0	0	0	0	0	0	1449531196	12/7/2015	23:33:16
Disk4	0	0	0	0	0	0	0	0	1449531197	12/7/2015	23:33:17
Disk5	0	0	0	0	0	0	0	0	1449531197	12/7/2015	23:33:17
Disk6	0	0	0	0	1	0	0	0	1449531197	12/7/2015	23:33:17

[daminite]

Here is the data I think you are requesting. Only thing I see abnormal is the command error on disk 6

	realloc_sect	realloc_evnt	spin_retry_cnt	ioedc	cmd_timeouts	pending_sect	uncorrectable_err	ata_errors	timestamp	time
--------------------	------------	------------	--------------	----------	------------	------------	-----------------	----------	----------	----------	---------
Disk1	0	0	0	0	0	0	0	0	1449531196	12/7/2015	23:33:16
Disk2	0	0	0	0	0	0	0	0	1449531196	12/7/2015	23:33:16
Disk3	0	0	0	0	0	0	0	0	1449531196	12/7/2015	23:33:16
Disk4	0	0	0	0	0	0	0	0	1449531197	12/7/2015	23:33:17
Disk5	0	0	0	0	0	0	0	0	1449531197	12/7/2015	23:33:17
Disk6	0	0	0	0	1	0	0	0	1449531197	12/7/2015	23:33:17

[StephenB]

Yes, that was it.

Since the pro is rebooting more than once, the single command timeout can't be the trigger.

[mdgm-ntgr]

Please send in the full set of logs (see the Sending Logs link in my sig).

[mdgm-ntgr]

It's unclear from your logs why this is happening.

You may wish to try ReadyNASOS 6.4.2 (RC1)

If that does not resolve it, perhaps try hooking the disks up to your PC and testing them using SeaTools and also run a few passes of the memory test boot menu option.