Discussion stats
  • 12 replies
  • 2207 views
  • 0 kudos
  • 3 in conversation
Announcements

Top Contributors
Reply
Highlighted
Tutor

6.x Reboots during Resync --Pro Pioneer

Problem: I'm incurring intermittent reboots when performing a RAID6 resync on an out-of-warranty Pro Pioneer running both OS 6.2.2 or 6.3.3-T115 (Beta 3). Upon installing four brand new drives (WD30EFRX w/ NASware 3.0 firmware), a new RAID6 volume cannot be successfully created because the resync process is always interrupted by reboots.

How to Reproduce:
    1. Perform Factory Default via web gui
    3. Log in and ignore the initial setup wizard by pressing cancel
    4. Destroy the RAID5 volume that was just created during the Factory Default and create a new RAID6 volume as follows:
      a) Navigate to System > Volumes
      b) Disable X-RAID (cannot destroy volume unless X-RAID is first disabled)
      c) Click the Gear icon in the blue box on the left and then Destroy the volume
      d) Click all drives in the graphical depiction of the nas and select New Volume
      e) Name the NAS and select RAID6 (no encryption selected)

    5. Wait for nas to reboot (doesn't seem to be predictable --could occur at 10% resync or several hours later around 70% resync)


Expected behavior: NAS should reach 100% resync completion.

Troubleshooting & Logs: The following is a list of the troubleshooting steps taken (in order) with accommodating logs being posted chronologically


    -Reinstalled original 1GB dimm included w/ pro pioneer
    -Unplugged usb backup-drive and usb connection to UPS
    -Removed side panels, cleaned heat sinks w/ airgun (barely any dust buildup), connected an auxiliary 80mm fan and positioned it over the south bridge heat sink which seemed rather hot.
    -Cleared BIOS (used dipswitch and removed battery).
    -Entered BIOS and set default settings.
    -Performed a "Factory Default" (6.2.2) via web gui
    -Logged in and skipped initial setup Wizard by pressing cancel

    -After a Factory Default, the Readynas automatically syncs a RAID5 array. I did not intervene with this default behavior and the RAID5 volume resynced to 100%.
    -After resync completed, web gui was unresponsive. Rebooted nas via front panel.

    -Since I want a RAID6 setup, I destroyed the default RAID5 volume and create a new RAID6 volume as described in step 4 of "How to Reproduce" at the top of this post.
    -Within a few seconds of confirming the creation of the new RAID6 volume, I received the following gui error:


    *images may appear clipped if you do not maximize your browser or zoom out.


    -Upon clicking ignore in the above error, the resync still seems to be making progress as shown below:

    *images may appear clipped if you do not maximize your browser or zoom out.

    -Readynas rebooted about 7% into the above resync.

    -Destroyed the RAID6 volume according to step 4 of "How to Reproduce". However, about 10-seconds after confirming the 'DESTROY', the web gui crashed and so I physically rebooted the device via the front panel. Upon rebooting, web gui seems to confirm that volume was deleted.

    -Reattempted to create a new RAID6 volume. Did not receive a gui error w/ red colored drives like last time.

    *images may appear clipped if you do not maximize your browser or zoom out.


    -About 12 hours have passed since the last log entry where I reattempted to create the RAID6 volume. Since then, the nas has rebooted six times. The shortest amount of time between reboots being 30-minutes and the longest being 4-hours. NAS resynced a RAID5 volume earlier but seems to be having trouble w/ RAID6.


    -Deleted RAID6 volume and rebooted nas.


    -Recreated RAID6 volume (no encryption) and immediately enabled X-RAID by clicking the icon circled in red:

    *images may appear clipped if you do not maximize your browser or zoom out.


    -About 12 hours have passed since the last log entry where I recreate the RAID6 volume and immediately enabled X-RAID. Since then, the nas has rebooted seven times. The shortest amount of time between reboots being 1-minute and the longest being 2-hours. NAS continues to have trouble syncing a RAID6 volume despite successfully syncing a RAID5 volume.


    -Deleted RAID6 volume, disabled all services (except http and https which cannot be disabled from web gui) and rebooted nas.

    -Created new RAID6 volume (no encryption) with all services disabled except http and https
    -About 12 hours have passed since the last log entry where I created the RAID6 volume while all readynas services were disabled except http/https. Since then, the nas has rebooted six times. The shortest amount of time between reboots being 7-minutes and the longest being 4-hours. NAS continues to have trouble syncing a RAID6 volume despite successfully syncing a RAID5 volume.
      Click to download logs: "Forum Error: Your message contains too many URLs. The maximum number of URLs allowed is 10"

    -Flashed early access OS 6.3.3-T115 (Beta 3)
    -Performed a Factory Default
    -After a Factory Default, the Readynas automatically syncs a RAID5 volume. Deleted the default RAID5 volume.
    -Shutdown nas and installed an working 850W power supply.
    -Created new RAID6 volume (no encryption).
    -About 24-hours have passed since the last log entry where I created a new RAID6 volume. Since then, the nas has rebooted 33 times. The shortest ellapsed time between reboots being 1-minute and the longest being 2-hours.


    -Removed OS 6 and reinstalled RAIDiator 4.2.27
    -Created a " RAID Level X-RAID2, 4 disks (with dual redundancy) " volume (I believe this may be RAIDiator's terminology for "RAID6").

Considerations for future troubleshooting attempts:

    -Disable all services (except http and https which of course cannot be disabled via web gui)
    -Perform a Factory Default via physical reset button and front display on readynas
    -Perform an OS Reinstall via physical reset button and front display on readynas
    -Remove nas from network (unplug ethernet cables)
    -Change physical order of drives. e.g. Drives originally installed in slots 1,2,3,4. Reinserted drives into slots 1,2,5,6. (silly, but desperate)


Notes: searching through the forums. I found one user whose issue was similar issue was resolved via a complete replacement. I've had this issue w/ this same device (different hard drives) in the past running the old radiator OS. In the past, it would eventually complete a 100% resync --hopefully that occur here.
NAS: Pro Pioneer RAID10 OS6.4.0-T147 ::: CPU: E7600 DDR2: 2 x 2GB AD2U800B2G5-DRH ::: HDDs: 4 x 3TB WD30EFRX NASware 3.0_82.00A82 ::: LAN: GS108T-200 ::: UPS: Cyberpower 1500-AVR
Message 1 of 13
Highlighted
Guru

Re: 6.2.2 Reboots during Resync --Pro Pioneer

What do the SMART stats look like? Anything in the logs around the time it reboots?
Message 2 of 13
Highlighted
Tutor

Re: 6.2.2 Reboots during Resync --Pro Pioneer

StephenB, would you please advise where to look for this info?

I did " grep -ri "smart" ./ " in the directory containing all of the log files and did not see anything that looks explicitly like an error. See below for details.
Also, for your reference, I am posting links to each set of logs in the "Troubleshooting & Logs" section of the original post.

$ grep -ri "smart" ./
./systemd-journal.log:Jan 23 08:47:50 nas-EA-68-69 readynasd[3013]: adding: smart_history.log (deflated 79%)
./systemd-journal.log:Jan 23 19:53:03 nas-EA-68-69 readynasd[1967]: adding: smart_history.log (deflated 79%)
./systemd-journal.log:Jan 23 20:02:00 nas-EA-68-69 readynasd[1967]: Disabling smartnetwork ...
./systemd-journal.log:Jan 23 20:10:02 nas-EA-68-69 readynasd[1967]: adding: smart_history.log (deflated 79%)
./db.dump:CREATE TABLE `service_smartnetwork` ( `enabled` INT NULL);
./db.dump:INSERT INTO "service_smartnetwork" VALUES(0);
./readynasd.log:Jan 23 20:02:00 nas-EA-68-69 readynasd[1967]: Disabling smartnetwork ...
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:
./volume.log: SMART Data:


I also did a search for a "error" as shown:
$ grep -ri "error" ./
./network_settings.log: RX packets:5012 errors:0 dropped:6 overruns:0 frame:0
./network_settings.log: TX packets:6582 errors:0 dropped:0 overruns:0 carrier:0
./network_settings.log: RX packets:0 errors:0 dropped:0 overruns:0 frame:0
./network_settings.log: TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
./network_settings.log: RX packets:163 errors:0 dropped:0 overruns:0 frame:0
./network_settings.log: TX packets:163 errors:0 dropped:0 overruns:0 carrier:0
./network_settings.log: RX packets:0 errors:0 dropped:0 overruns:0 frame:0
./network_settings.log: TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: syslog+console
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: syslog+console
./systemctl-dump.log: StandardError: syslog+console
./systemctl-dump.log: StandardError: syslog+console
./systemctl-dump.log: Unit Load State: error
./systemctl-dump.log: Load Error Code: No such file or directory
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./systemctl-dump.log: StandardError: inherit
./smart_history.log:model serial realloc_sect realloc_evnt spin_retry_cnt ioedc cmd_timeouts pending_sect uncorrectable_err ata_errors timestamp time
./systemd-journal.log:Jan 23 08:38:20 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:20 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:23 nas-EA-68-69 apache2[3009]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:23 nas-EA-68-69 apache2[3009]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:23 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit netatalk.service is not loaded.
./systemd-journal.log:Jan 23 08:38:25 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit minidlna.service is not loaded.
./systemd-journal.log:Jan 23 08:38:25 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit rcbrokerd.service is not loaded.
./systemd-journal.log:Jan 23 08:38:25 nas-EA-68-69 apache2[3010]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:25 nas-EA-68-69 apache2[3010]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:26 nas-EA-68-69 apache2[3011]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:26 nas-EA-68-69 apache2[3011]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:27 nas-EA-68-69 apache2[3012]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:27 nas-EA-68-69 apache2[3012]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:28 nas-EA-68-69 readynasd[3013]: Can't read last fan setting or setting error -22.
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: soap error
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: "org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object"
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error registering user -1
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error configuring peer network
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error configuring network -1
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error logging in
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error starting application -6
./systemd-journal.log:Jan 23 08:38:29 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./systemd-journal.log:Jan 23 08:38:30 nas-EA-68-69 rcbrokerd[3204]: registration.cpp:150 [Registration::RegisterTmpOwner] Error: invalid config files. unable to read fetch_url, nas_name, nas_pass
./systemd-journal.log:Jan 23 08:38:30 nas-EA-68-69 apache2[3009]: [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
./systemd-journal.log:Jan 23 08:38:37 nas-EA-68-69 leafp2p[3106]: soap error
./systemd-journal.log:Jan 23 08:38:37 nas-EA-68-69 leafp2p[3106]: "org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object"
./systemd-journal.log:Jan 23 08:38:37 nas-EA-68-69 leafp2p[3106]: Error registering user -1
./systemd-journal.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error configuring peer network
./systemd-journal.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error configuring network -1
./systemd-journal.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error logging in
./systemd-journal.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error starting application -6
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:748: error: sendto(udp_shutdown=9): Network is unreachable
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:748: error: sendto(udp_shutdown=9): Network is unreachable
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./systemd-journal.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./systemd-journal.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1965]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1965]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:25 nas-EA-68-69 apache2[1967]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/wizard.html
./systemd-journal.log:Jan 23 09:30:25 nas-EA-68-69 apache2[1967]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/wizard.html
./systemd-journal.log:Jan 23 09:30:28 nas-EA-68-69 apache2[1969]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/wizard.html
./systemd-journal.log:Jan 23 09:30:28 nas-EA-68-69 apache2[1969]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/wizard.html
./systemd-journal.log:Jan 23 09:30:28 nas-EA-68-69 apache2[2036]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:28 nas-EA-68-69 apache2[2036]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:30 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:30 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 09:30:30 nas-EA-68-69 smbd[1970]: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./systemd-journal.log:Jan 23 09:30:31 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/wizard.html
./systemd-journal.log:Jan 23 09:30:31 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/wizard.html
./systemd-journal.log:Jan 23 09:30:31 nas-EA-68-69 readynasd[1971]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./systemd-journal.log:Jan 23 09:30:31 nas-EA-68-69 apache2[1965]: [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
./systemd-journal.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1994]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1994]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1995]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1995]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./systemd-journal.log:Jan 23 12:19:22 nas-EA-68-69 readynasd[2000]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./systemd-journal.log:Jan 23 12:36:46 nas-EA-68-69 readynasd[2000]: ERROR: Radar: Maximum iteration exceeded
./systemd-journal.log:Jan 23 19:50:13 nas-EA-68-69 smbd[1999]: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./systemd-journal.log:Jan 23 19:51:12 nas-EA-68-69 readynasd[1967]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./systemd-journal.log:Jan 23 20:00:57 nas-EA-68-69 apache2[2117]: [error] [client 192.168.1.3] File does not exist: /frontview/dashboard/images, referer: http://192.168.1.6/admin/css/frontview_1.0.2.754_base64.css
./systemd-journal.log:Jan 23 20:01:15 nas-EA-68-69 smbd[1966]: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./systemd-journal.log:Jan 23 20:01:19 nas-EA-68-69 readynasd[1967]: ERROR: cannot delete '/data/home' - Device or resource busy
./systemd-journal.log:Jan 23 20:01:58 nas-EA-68-69 readynasd[1967]: ERROR: cannot create subvolume - Inappropriate ioctl for device
./systemd-journal.log:Jan 23 20:01:58 nas-EA-68-69 readynasd[1967]: Error in chown for user: ReadyNAS, path: /run/.timemachine
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:748: error: sendto(udp_shutdown=9): Network is unreachable
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:748: error: sendto(udp_shutdown=9): Network is unreachable
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./upnp-av.log:Jan 23 08:38:45 nas-EA-68-69 minidlnad[3105]: minissdp.c:304: error: sendto(udp_notify=9, 5.214.24.29): Network is unreachable
./readynasd.log:Jan 23 08:38:23 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit netatalk.service is not loaded.
./readynasd.log:Jan 23 08:38:25 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit minidlna.service is not loaded.
./readynasd.log:Jan 23 08:38:25 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit rcbrokerd.service is not loaded.
./readynasd.log:Jan 23 08:38:28 nas-EA-68-69 readynasd[3013]: Can't read last fan setting or setting error -22.
./readynasd.log:Jan 23 08:38:29 nas-EA-68-69 readynasd[3013]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./readynasd.log:Jan 23 09:30:31 nas-EA-68-69 readynasd[1971]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./readynasd.log:Jan 23 12:19:22 nas-EA-68-69 readynasd[2000]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./readynasd.log:Jan 23 12:36:46 nas-EA-68-69 readynasd[2000]: ERROR: Radar: Maximum iteration exceeded
./readynasd.log:Jan 23 19:51:12 nas-EA-68-69 readynasd[1967]: Error proxy call. GDBus.ErrorSmiley Surprisedrg.freedesktop.systemd1.NoSuchUnit: Unit radar.timer is not loaded.
./readycloud.log:Jan 23 08:38:30 nas-EA-68-69 rcbrokerd[3204]: registration.cpp:150 [Registration::RegisterTmpOwner] Error: invalid config files. unable to read fetch_url, nas_name, nas_pass
./etc-ls.log:-rw-r--r-- 1 root root 3296 Aug 2 2012 localized-error-pages
./leafp2p.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: soap error
./leafp2p.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: "org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object"
./leafp2p.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error registering user -1
./leafp2p.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error configuring peer network
./leafp2p.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error configuring network -1
./leafp2p.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error logging in
./leafp2p.log:Jan 23 08:38:29 nas-EA-68-69 leafp2p[3106]: Error starting application -6
./leafp2p.log:Jan 23 08:38:37 nas-EA-68-69 leafp2p[3106]: soap error
./leafp2p.log:Jan 23 08:38:37 nas-EA-68-69 leafp2p[3106]: "org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object"
./leafp2p.log:Jan 23 08:38:37 nas-EA-68-69 leafp2p[3106]: Error registering user -1
./leafp2p.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error configuring peer network
./leafp2p.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error configuring network -1
./leafp2p.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error logging in
./leafp2p.log:Jan 23 08:38:38 nas-EA-68-69 leafp2p[3106]: Error starting application -6
./smbd.log: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./smbd.log: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./smbd.log: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./system.log:Jan 23 08:38:20 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:20 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:23 nas-EA-68-69 apache2[3009]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:23 nas-EA-68-69 apache2[3009]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:25 nas-EA-68-69 apache2[3010]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:25 nas-EA-68-69 apache2[3010]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:26 nas-EA-68-69 apache2[3011]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:26 nas-EA-68-69 apache2[3011]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:27 nas-EA-68-69 apache2[3012]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:27 nas-EA-68-69 apache2[3012]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:29 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:29 nas-EA-68-69 apache2[3008]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 08:38:30 nas-EA-68-69 apache2[3009]: [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
./system.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1965]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1965]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:23 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:25 nas-EA-68-69 apache2[1967]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/wizard.html
./system.log:Jan 23 09:30:25 nas-EA-68-69 apache2[1967]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/wizard.html
./system.log:Jan 23 09:30:28 nas-EA-68-69 apache2[1969]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/wizard.html
./system.log:Jan 23 09:30:28 nas-EA-68-69 apache2[1969]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/wizard.html
./system.log:Jan 23 09:30:28 nas-EA-68-69 apache2[2036]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:28 nas-EA-68-69 apache2[2036]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:30 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:30 nas-EA-68-69 apache2[1968]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 09:30:30 nas-EA-68-69 smbd[1970]: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./system.log:Jan 23 09:30:31 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.7] Connect rddclient failed, referer: http://192.168.1.6/admin/wizard.html
./system.log:Jan 23 09:30:31 nas-EA-68-69 apache2[1966]: [error] [client 192.168.1.7] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/wizard.html
./system.log:Jan 23 09:30:31 nas-EA-68-69 apache2[1965]: [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
./system.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1994]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1994]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1995]: [error] [client 192.168.1.3] Connect rddclient failed, referer: http://192.168.1.6/admin/
./system.log:Jan 23 12:19:17 nas-EA-68-69 apache2[1995]: [error] [client 192.168.1.3] Premature end of script headers: dbbroker.cgi, referer: http://192.168.1.6/admin/
./system.log:Jan 23 19:50:13 nas-EA-68-69 smbd[1999]: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./system.log:Jan 23 20:00:57 nas-EA-68-69 apache2[2117]: [error] [client 192.168.1.3] File does not exist: /frontview/dashboard/images, referer: http://192.168.1.6/admin/css/frontview_1.0.2.754_base64.css
./system.log:Jan 23 20:01:15 nas-EA-68-69 smbd[1966]: Failed to delete pidfile /var/run/smbd.pid. Error was No such file or directory
./disk_info.log: ATA Error Count: 0
./disk_info.log: ATA Error Count: 0
./disk_info.log: ATA Error Count: 0
./disk_info.log: ATA Error Count: 0
NAS: Pro Pioneer RAID10 OS6.4.0-T147 ::: CPU: E7600 DDR2: 2 x 2GB AD2U800B2G5-DRH ::: HDDs: 4 x 3TB WD30EFRX NASware 3.0_82.00A82 ::: LAN: GS108T-200 ::: UPS: Cyberpower 1500-AVR
Message 3 of 13
Highlighted
Guru

Re: 6.2.2 Reboots during Resync --Pro Pioneer

look in disk_info.log
Message 4 of 13
Highlighted
Tutor

Re: 6.2.2 Reboots during Resync --Pro Pioneer

StephenB wrote:
look in disk_info.log


I don't see anything suspicious. Would you have a look?

Click to download logs: System_log-nas-EA-68-69-20150124-191511.zip

$ pwd
/home/dk0r/Downloads/System_log-nas-EA-68-69-20150124-191511

$ cat disk_info.log
Device: sda
Controller: 0
Channel: 0
Model: WDC WD30EFRX-68EUZN0
Serial: <REMOVED BY MODERATOR>
Firmware: 82.00A82
Class: SATA
RPM: 5400
Sectors: 5860533168
Pool: data
PoolType: RAID 6
PoolState: 1
PoolHostId: 33ea6869
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 33
Start/Stop Count: 13
Power-On Hours: 81
Power Cycle Count: 13
Load Cycle Count: 8

Device: sdb
Controller: 0
Channel: 2
Model: WDC WD30EFRX-68EUZN0
Serial: <REMOVED BY MODERATOR>
Firmware: 82.00A82
Class: SATA
RPM: 5400
Sectors: 5860533168
Pool: data
PoolType: RAID 6
PoolState: 1
PoolHostId: 33ea6869
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 32
Start/Stop Count: 11
Power-On Hours: 80
Power Cycle Count: 11
Load Cycle Count: 5

Device: sdc
Controller: 0
Channel: 3
Model: WDC WD30EFRX-68EUZN0
Serial: <REMOVED BY MODERATOR>
Firmware: 82.00A82
Class: SATA
RPM: 5400
Sectors: 5860533168
Pool: data
PoolType: RAID 6
PoolState: 1
PoolHostId: 33ea6869
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 35
Start/Stop Count: 11
Power-On Hours: 80
Power Cycle Count: 11
Load Cycle Count: 5

Device: sdd
Controller: 0
Channel: 5
Model: WDC WD30EFRX-68EUZN0
Serial: <REMOVED BY MODERATOR>
Firmware: 82.00A82
Class: SATA
RPM: 5400
Sectors: 5860533168
Pool: data
PoolType: RAID 6
PoolState: 1
PoolHostId: 33ea6869
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 33
Start/Stop Count: 13
Power-On Hours: 80
Power Cycle Count: 13
Load Cycle Count: 5
NAS: Pro Pioneer RAID10 OS6.4.0-T147 ::: CPU: E7600 DDR2: 2 x 2GB AD2U800B2G5-DRH ::: HDDs: 4 x 3TB WD30EFRX NASware 3.0_82.00A82 ::: LAN: GS108T-200 ::: UPS: Cyberpower 1500-AVR
Message 5 of 13
Highlighted
Guru

Re: 6.2.2 Reboots during Resync --Pro Pioneer

The disks look fine.

I am seeing the abnormal restarts in readynasd.log. I'm not seeing any shutdowns or evidence of errors there (or in kernel.log or system.log). Perhaps someone else can also take a look.

Perhaps there is a hardware issue (power perhaps since you've already swapped memory)???

RAID-6 does put a higher processing load on the CPU, so it might draw more power. Or perhaps the problem is simply getting worse, and the RAID-6 timing is coincidence?

Are you using a UPS?
Message 6 of 13
Highlighted
Tutor

Re: 6.2.2 Reboots during Resync --Pro Pioneer

Thanks for your reply, StephenB.

StephenB wrote:

Perhaps there is a hardware issue (power perhaps since you've already swapped memory)???
RAID-6 does put a higher processing load on the CPU, so it might draw more power.

It's been a couple years since I ran both memtest86 and the memory test from the physical front panel on both the original 1GB and aftermarket 4GB kit. Neither of them turned up any errors in the past but I'll rerun the tests and post if anything has changed.

Also, please forgive my misleading signature. I'm currently running the stock CPU and am awaiting delivery of the E7600 upgrade. For now, I've removed the E7600 reference from my signature.

StephenB wrote:

Or perhaps the problem is simply getting worse, and the RAID-6 timing is coincidence?

What do you mean by the problem is getting worse? From what I've experienced, there's no better or worse --I simply cannot sync a RAID6 volume.

Also, what do you mean by the RAID6 timing being coincidence? By "timing", are you referring to the amount of time between reboots that I posted in the Troubleshooting & Logs section? If so, what is coincidental about the time between reboots that I posted?

StephenB wrote:

Are you using a UPS?

Yes, the NAS is being powered using a battery-backed-up outlet on an UPS.
However, the NAS shouldn't know that since the usb cable connecting the NAS and the UPS is unplugged.
NAS: Pro Pioneer RAID10 OS6.4.0-T147 ::: CPU: E7600 DDR2: 2 x 2GB AD2U800B2G5-DRH ::: HDDs: 4 x 3TB WD30EFRX NASware 3.0_82.00A82 ::: LAN: GS108T-200 ::: UPS: Cyberpower 1500-AVR
Message 7 of 13
Highlighted
Guru

Re: 6.2.2 Reboots during Resync --Pro Pioneer

The resync issue is a symptom. The problem is whatever is making it do that.

Just to clarify - I am thinking that the real problem is that your power supply or UPS is starting to fail. As the raid resync continues, the continued power draw causes either the UPS or the power supply to glitch, resulting in a reboot.

I think RAID-6 might use more power during sync (certainly the sync takes longer). But if the supply (or UPS) were starting to fail anyway, it is possible that the issue has nothing directly to do with RAID-6.

I'd try plugging the NAS into the mains power instead of the UPS, and see if the symptoms change. (The power supply seems more likely than the UPS, but the UPS is easier to rule in/out).

The idea that it might be power is of course just a guess.
Message 8 of 13
Highlighted
Tutor

Re: 6.2.2 Reboots during Resync --Pro Pioneer

StephenB wrote:
...I am thinking that the real problem is that your power supply or UPS is starting to fail.


Thanks, StephenB. I've connected the Pro Pioneer (now running early access OS 6.3.3-T115 Beta 3) to a working 850W power supply. For others reference, I swapped the following connections from the old power supply to the new one: One 24-pin ATX power connector on the motherboard, one 4-pin cpu power connector on the motherboard and three molex power connectors on the sata interface board located behind the hard drive cage.

Unfortunately, I'm still getting reboots using RAID6. At this point the behavior seems indicative of an internal hardware defect. At this point, I'm uncertain whether there are any alternatives to just throwing parts at it Need to google whether replacement parts (motherboard, sata interface boards, etc) are even available/afforable. Perhaps I'll just use RAID5 instead.. sigh :: :cry:
NAS: Pro Pioneer RAID10 OS6.4.0-T147 ::: CPU: E7600 DDR2: 2 x 2GB AD2U800B2G5-DRH ::: HDDs: 4 x 3TB WD30EFRX NASware 3.0_82.00A82 ::: LAN: GS108T-200 ::: UPS: Cyberpower 1500-AVR
Message 9 of 13
Highlighted
NETGEAR Employee Retired

Re: 6.2.2 Reboots during Resync --Pro Pioneer

Do you still have this problem if you put 4.2.x back on it (note this requires a factory reset so backup your data first)?: http://www.readynas.com/forum/viewtopic.php?f=35&t=75198
Message 10 of 13
Highlighted
Guru

Re: 6.2.2 Reboots during Resync --Pro Pioneer

dk0r wrote:
StephenB wrote:
...I am thinking that the real problem is that your power supply or UPS is starting to fail.


Thanks, StephenB. I've connected the Pro Pioneer (now running early access OS 6.3.3-T115 Beta 3) to a working 850W power supply...Unfortunately, I'm still getting reboots using RAID6.
Definitely not the supply then :slap:

mdgm's suggestion is time-consuming but free, so maybe try that next.
Message 11 of 13
Highlighted
Tutor

Re: 6.2.2 Reboots during Resync --Pro Pioneer

mdgm wrote:
Do you still have this problem if you put 4.2.x back on it?

Good call, mdgm. This issue does not seem to be OS dependent as I reverted to RAIDiator 4.2.3 and had the same results as OS6.x.
That is, RAID5 volumes will sync to completion but resyncs on a RAID6 volume are constantlly interrupted by reboots with no apparent indication of the problem in the logs. So, what next? Hardware?
NAS: Pro Pioneer RAID10 OS6.4.0-T147 ::: CPU: E7600 DDR2: 2 x 2GB AD2U800B2G5-DRH ::: HDDs: 4 x 3TB WD30EFRX NASware 3.0_82.00A82 ::: LAN: GS108T-200 ::: UPS: Cyberpower 1500-AVR
Message 12 of 13
Highlighted
NETGEAR Employee Retired

Re: 6.x Reboots during Resync --Pro Pioneer

I assume you bought this more than 3 years ago?

Can you provide a set of logs from 4.2.x?

I guess you can update back to OS6 if you want that.

Can you make sure the RAM is still properly seated? Have you tried running a few passes of the memory test boot menu option?

Although your WD disks are not showing SMART errors you may also wish to hook them up to a PC and test them using WD Data LifeGuard Diagnostics.
Message 13 of 13