× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: Cannot access the NAS 516 via network after update to 6.5.1 - have to force-reboot

gksolutions
Aspirant

Cannot access the NAS 516 via network after update to 6.5.1 - have to force-reboot

I am also experiencing similar issues with my NAS RN 516 over the past few weeks.  

 

Model:  Readynas 516

Serial:  3c82350N01C41

 

Model: Readynas Pro 6

Serial:  2H051CRM00033

 

No matter what I do, or if I setup SMB/NFS the computers on my local network can no longer see the NAS RN 516.  Constantly having to force-boot the machine in order to access my files which work for a few minutes, but then I lose all connections to it, including Frontview. Failed attempts to shutdown/restart/reboot via Frontview, RAIDar, or by double-pressing the front button.  Can only force-boot the machine by holding down the front button until powered-off and then re-pressing button or by disconnecting-reconecting power cable and pressing front button.

 

I have another NAS (Pro 6) on the same local network, workgroup and subnet and it works fine.  Both machines have been updated to firmware 6.5.2, though I was experiencing this issue about 2/3 weeks prior to updating.  Both machines are running Anti-Virus Plus and Transmission for Readynas and the RN516 also is running Plex.  Have disabled ReadyCloud and Replicate on both machines to see if this resolves the issue.

 

All shares have:

  • SMB set to allow Read/Write to everyone and to allow anonymous access and DFS Root disabled
  • SMB is enabled an all machines on local network (NASes, desktops) are set with 'NL' workgroup name
  • NFS set to allow Read/Write to AnyHost with Root Access to IP Address 192.168.0.0/24 and async disabled
  • NFS Settings have NFS enabled with 12 threads and NFSv4 disabled (enabling or disabling NFSv4 did not resolve issue)
  • AFP, FTP, iTunes and SNMP is disabled
  • HTTP access to specific user groups and webdav enabled
  • No snapshots are being taken on any share
  • File Access has Folder Owner and Folder Group set to guest with rename and delete privileges to non-owners enabled
  • File Access has Read/Write enabled for Everyone, Folder Owner and Folder Group
  • Home Folders are disabled and Not Shared
  • UPnP is On
  • Anti-Virus is enabled
  • SSH is enabled with password authentication (SSH key has been downloaded then added to adminand to my 'local username')
  • HTTPS is enabled with additiona ports (RN516: port 8082  |  Pro 6: port 8083) and port forwarding setup on router
  • SSL Key Host is set (RN516: 192.168.0.2  |  Pro 6: 192.168.0.3)
  • RSync Setting is enabled
  • and finally both NASes including two local desktops have their ethernet Cat-6 cables plugged into a TP-Link (TL-SG1016 V10) Gigabit Switch and the switch is connected directly to the router.  (hard reset of entire network and router/switch did not resolve issue)
  • Both have HTTP Admin disabled (enabling or disabling this setting did not resolve issue)
  • Both have WOL enabled and no UPS
  • Both machines have a single RAID-0 volume at approx. 75% capacity
  • RN516 has a redirect default web access folder set
  • RN516 has DLNA  and Auto Scan enabled but with TiVo disabled
  • RN516 has Disk Spin-Down enabled after 5 minutes - Pro 6 displays red warning that fan is not working if this is enabled even though the fans sound like they are running as normal
  • ...and most shares have RSync with Read/Write default access and password protection enabled
  • ...and a few shares have DLNA enabled for videos

Both machine have static IPv4 addresses (RN516: 192.168.0.2  |  Pro 6: 192.168.0.3) / Subnet: 255.255.255.0:

  • with both network ports on each bonded and in Adaptive Load Balancing Mode
  • both are set at 1500 MTU (have disabled Jumbo Packets which was previously on until experiencing this issue)
  • both are configured to Using DHCP for IPv6

 

Ran Diagnostics from RAIDar which also constantly shows the RN 516 as still being in Remote Support even though I turned this off a couple of days ago.  Results of diagnostics as follows:

 

Successfully completed diagnostics System

  • Disk 6 has 19 Command Timeouts

Logs

  • 2016-09-24 19:19:31: readynasd[8951]: segfault at 0 ip 00007f7cb23f987b sp 00007f7c897f8b30 error 4 in libc-2.19.so[7f7cb2303000+1a2000]

 

Diagnostics on Pro 6 shows a number of faults:

  • 2016-09-20 00:39:02: [607121.383468] general protection fault: 0000 [#15] SMP
  • 2016-09-20 00:39:02: [607121.383515] RIP [] do_dup2+0x2c/0xa0
  • 2016-09-20 00:39:02: [607121.383564] general protection fault: 0000 [#16] SMP
  • 2016-09-20 00:22:44: [606143.452039] general protection fault: 0000 [#13] SMP
  • 2016-09-20 00:22:44: [606143.452124] RIP [] filp_close+0x17/0x80
  • 2016-09-20 00:22:44: [606143.452231] general protection fault: 0000 [#14] SMP
  • 2016-09-20 00:17:56: [605855.619282] general protection fault: 0000 [#11] SMP
  • 2016-09-20 00:17:56: [605855.619405] RIP [] __fget_light+0x5c/0x70
  • 2016-09-20 00:17:56: [605855.619547] general protection fault: 0000 [#12] SMP
  • 2016-09-19 23:12:01: [601900.995239] general protection fault: 0000 [#9] SMP
  • 2016-09-19 23:12:01: [601900.995290] RIP [] dup_fd+0x130/0x2e0
  • 2016-09-19 23:12:01: [601900.995399] general protection fault: 0000 [#10] SMP
  • 2016-09-19 22:17:01: [598600.935221] general protection fault: 0000 [#8] SMP
  • 2016-09-19 22:17:01: [598600.935272] RIP [] filp_close+0x17/0x80
  • 2016-09-19 20:50:01: [593380.660384] general protection fault: 0000 [#7] SMP
  • 2016-09-19 20:50:01: [593380.660434] RIP [] filp_close+0x17/0x80
  • 2016-09-19 19:48:01: [589661.339470] general protection fault: 0000 [#6] SMP
  • 2016-09-19 19:48:01: [589661.339520] RIP [] filp_close+0x17/0x80
  • 2016-09-19 15:05:01: [572680.568779] general protection fault: 0000 [#5] SMP
  • 2016-09-19 15:05:01: [572680.568829] RIP [] filp_close+0x17/0x80
  • 2016-09-19 07:42:34: [546133.422057] general protection fault: 0000 [#3] SMP
  • 2016-09-19 07:42:34: [546133.422143] RIP [] filp_close+0x17/0x80
  • 2016-09-19 07:42:34: [546133.422252] general protection fault: 0000 [#4] SMP
  • 2016-09-19 06:55:01: [543280.654212] general protection fault: 0000 [#1] SMP
  • 2016-09-19 06:55:01: [543280.655194] RIP [] __fget_light+0x5c/0x70
  • 2016-09-19 06:55:01: [543280.855397] general protection fault: 0000 [#2] SMP

 

Tried clearing out all references to NASes within User/Certificates, used NET USE to delete all network connections and created new connections.

 

gksolutions
Graham-King Solutions
ReadyNas 516 -
Model: RN51600|ReadyNAS 516 6-Bay
Message 1 of 4

Accepted Solutions
gksolutions
Aspirant

Re: Cannot access the NAS 516 via network after update to 6.5.1 - have to force-reboot

Have replaced all disks with 5TB ones and have done a Factory Reset.  Everything seems to be back in proper working order.

View solution in original post

Model: RN51600|ReadyNAS 516 6-Bay
Message 4 of 4

All Replies
mdgm-ntgr
NETGEAR Employee Retired

Re: Cannot access the NAS 516 via network after update to 6.5.1 - have to force-reboot

Check for a full root volume and if that has plenty of space then download the logs and send those in (see the Sending Logs link in my sig).

 

As for the GPF on the Pro 6, is your Pro 6 connected to a 100Mbit Ethernet port on a router rather than a Gigabit (1000Mbit) one?

Message 2 of 4
gksolutions
Aspirant

Re: Cannot access the NAS 516 via network after update to 6.5.1 - have to force-reboot

I have just ordered new 5TB HGST 128MB disk drives which I will use to replace my existing 4TB Red drives as I am currently running at approx. 80% volume capacity.  Once they arrive, I will perform a full default-reset before restoring my data which is backed-up to the Pro 6.  Will observe how it behaves from there and post any observations/issues.

 

So far, since I disabled ReadyCloud and Replicate and disabled SMB 1.0/CIFS File Support and enabled SMB Direct I have been able to map both NASes and retain connected.

Model: RN51600|ReadyNAS 516 6-Bay
Message 3 of 4
gksolutions
Aspirant

Re: Cannot access the NAS 516 via network after update to 6.5.1 - have to force-reboot

Have replaced all disks with 5TB ones and have done a Factory Reset.  Everything seems to be back in proper working order.

Model: RN51600|ReadyNAS 516 6-Bay
Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 3227 views
  • 0 kudos
  • 2 in conversation
Announcements