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

Forum Discussion

ausea's avatar
ausea
Aspirant
Feb 16, 2017

ReadyNAS 212 (FW 6.6.1) Host not visible, shares not visible and can't start SMB

 

 

I'm having a very odd combination of issues with my ReadyNAS 212 which all occurred together and therefore I'm pretty sure are related.  The issues are:

  1. The NAS hostname is not visible on my (windows workgroup) LAN.  I can ping the IP address directly, and I have checked that the hostname is listed in the DHCP table on the router (which is providing the DHCP server).  However, the hostname is not accesible from any other host on the network (e.g. ping NAShostname gives "Ping request could not find host massaya."  To put this another way, arp -a lists the IP address, but net view doesn't list the host name.  Note that all other hosts on the network are listed in both.
  2. When browsing the NAS using the admin page, I cannot see any of the shares that exist on the NAS except for the Home folders (which contain only two subfolders, one for admin and one for the only user account created on the system).  These are empty.  However, I know the rest of the data is there somewhere, because the disk storage shows it half the storage being used.
  3. In investigating these problems I noticed that the SMB service was off.  I tried to turn it on but it doesn't turn on - no error messages, no log messages, nothing.  Other services seem to be working (e.g. FTP, HTTP).

To be honest, I'm not a hundred percent sure how the problem started.  Here are the steps I think led to the issues:

  • While renaming one of the shares, the admin console started taking a long time to respond, then came back with a error page along the lines of "cannot accces the host".  At this time, I found I couldn't access the shares anymore - I think this is when the hostname stopped being accessible.
  • As part of trying to fix this based on info from other posts in this forum, I figured it was a problem with space running out on the OS partition - my log files showed the "Volume: Less than 5% of volume media's capacity is free." warnings.  To try to resolve, I deleted the logs, disabled anti-virus and uninstalled Plex (which was the only app on the NAS at the time, although it was not running).  (Unfortunately, I neglected to save those logs before deleting).
  • At this point I noticed that the host name was not accessible.  I eliminated any issues with the router, then rebooted the router and the NAS to try to resolve.  I then did an OS reboot on the NAS.

Only other point worth mentioning is that ReadyCloud was enabled - I don't think it contributed but it's the only other which was turned on at the time.

 

I'm now at my wits end trying to solve this - I'm not a networks guy, and this is just a home network so I'm struggling with what to look at next.  Any suggestions for solutions or avenues of investigation would be much appreciated.

 

3 Replies

Replies have been turned off for this discussion
  • Did these issues coincide with your upgrading to FW 6.6.1? They sound familiar to a lot of the issues we had when I upgraded the FW on our ReadyNAS 312 from 6.6.0 to 6.6.1 right before I enabled ReadyCloud capability. 

     

    If you search this forum it seems like there are a lot of ongoing 6.6.1 issues, especially w/ the built-in antivirus; NG did just release a 6.7.0 beta FW this week.

     

    Things are generally working for my users now (still on FW 6.6.1, disabled the built-in antivirus on the ReadyNAS and re-mapped network drives on client PCs) so it's possible you can work your way towards a solution on 6.6.1.  Ultimately I plan to either factory restore to 6.6.0 or try out the beta.

     

     

    • ausea's avatar
      ausea
      Aspirant

      Thanks drw538.  I've actually had 6.6.1 working for quite a while without a problem (at least a month I think) so I didn't associate it with that, but I did read about the various problems.

       

      I realised after posting this that I was within my 90 day support warranty (just - it was my last day of free support!), so I logged a case and they seem to have fixed it all.  In summary:

      • Problems 1 and 3 were an oversight on my behalf.  After doing an ios rebuild (via the boot menu), the settings got cleared, and I forgot to reset the workgroup name in the authentication settings.
      • I'm told that problem 2 was caused by some corruption in the boot partition, but I haven't got the speicifc details.  My suspicion is that the boot sector entirely filled up (because I didn't notice the warnings) - probably associated with the AV issue - and this somehow corrupted it.  Luckily, they've been able to clean this up and I'm back to normal.

       

      So I'm leaving AV off and waiting with baited breath for the 6.7.0 to come out of beta; and I need to set up the email alerts (which I had neglected to do) so that I can act immediately when the boot sector starts filling up.

       

       

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