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

Forum Discussion

k4heines's avatar
Jan 15, 2017

RN104 crashing more frequently

Hello.

 

Here's the problem -- in the last week, my ReadnyNAS 104 has crashed twice.  By crash I mean the front panel is unrepsonsive (but the power button is lit), and it's not reachable via SMB, a web browser, or ReadyCLOUD.  It appears to crash while running rsync on my Mac to backup to a mounted SMB share from the ReadyNAS. Also, When ReadyCLOUD v1.0 on my Mac tries to connect to the crashed RN104, ReadyCLOUD actually quits unexpectedly -- just dispappears from the menu bar! This is new behavior for me.  

 

I upgraded from 6.6.0 to 6.6.1 this last week, in the hopes of fixing it. It crashed once before the upgrade, and once after. 

 

For the last 5 upgrades or so (potentially more), the device has required a power cycle after installation. Then after it has started up, it has the new version. Not sure if this is a problem.

 

More information:

My backup process prior to the last week has not been problem free.  While running rsync on a 2-3 TB set of data from my local Mac to a SMB share on the ReadyNAS, I have come to expect it to stop somehwere between 1-3 days. I suspect that the crashing is not due to the rsynd backups; rather that the error lies on the side of the ReadyNAS since I used to get SMB and AFP shares dropped frequently while copying files, before I started using rysnc.

 

Here's  a sampling of the errors I get while runnig an rsync command in Terminal:


when the SMB share is still connected on my Mac I get these errors:

  • Operation timed out (60)
    rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(992) [sender=2.6.9]
  •  

    Pictures/backup Ap Libraries prior to LR prep/ApLib_early collection.aplibrary/Database/Versions/2010/10/11/20101011-213853/d5LS%4mRTdqShDRqj%RRPA/Version-1.apversion
    rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
    WARNING: Pictures/backup Ap Libraries prior to LR prep/ApLib_early collection.aplibrary/Database/Versions/2010/10/11/20101011-213853/9NpafhJZR1uhopG9%uwq5A/Version-1.apversion failed verification -- update retained (will try again).
    rsync: connection unexpectedly closed (5391480 bytes received so far) [sender]
    rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-45/rsync/io.c(453) [sender=2.6.9]

 

when the SMB share has lost connection with my Mac I get there errors:

 

rsync: recv_generator: mkdir "/Volumes/drive-name/folder-name/Mac-HD-Home/." failed: Socket is not connected (57)
*** Skipping everything below this failed directory ***

and this is the very latest error, right after a successbul reboot:

 

Computer-Name:~ User$ sudo rsync -ah --progress -delete -e ssh --exclude="Creative Cloud Files" --exclude="ReadyCLOUD" --exclude=/Library/Caches/ --exclude=/Library/Application\ Support/MobileSync/ ~/  /Volumes/volume-name/folder-name/Mac-HD-Home/
Password:
building file list ...
2181346 files to consider
rsync: mkdir "/Volumes/volume-name/folder-name/Mac-HD-Home" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at /SourceCache/rsync/rsync-45/rsync/main.c(544) [receiver=2.6.9]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-45/rsync/io.c(453) [sender=2.6.9]

 

 

7 Replies

Replies have been turned off for this discussion
  • Now my RN104 won't come online at all.

     

    I power cycled it (3rd, maybe 4th, time in last week) because it was unrepsonsive on front panel and by all other means. After restarting, it never came online.

     

    Help - Now what? How can I get this to boot and stay operational? Should I load OS 6.6.0 or some utility on a USB thumb drive and connect it to the front of the ReadyNAS? I'm not sure how resolve this.

     

    (BTW, I looked at the logs the last time it booted, and it was all normal stuff -- antivirus updates, snapshots, the fact that the system rebooted. No db corruption listed.)

    • mdgm-ntgr's avatar
      mdgm-ntgr
      NETGEAR Employee Retired

      Can you send in your logs (see the Sending Logs link in my sig)?

      • k4heines's avatar
        k4heines
        Guide

        I'm afraid I can't send in the logs. I power cycled twice tonight, both times by unplugging the power cable (last resort, I know). On the first new startup, the front panel showed "Retry Startup 86%". It stayed there for a long time, so I power cycled. The second new startup got to "Fail to startup 98%"

         

        Is there some way I can repair it by starting up off a USB hard drive or thumb drive?

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