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

Forum Discussion

IX's avatar
IX
Aspirant
Jul 03, 2018

ReadyDR unreliable / random failures (Error 255)

Hello Community,

I have problems with ReadyDR-Jobs failing randomly with error 255.

Here's the setup:

Two RN3138 with identical disk setup, FW 6.9.3.

The first (storage02) ist the active NAS and provides usershares and a data-share for the company( about 46 shares in total). The second one (storage03) is only a readydr target.

On storage02 snapshots are taken every hour with smart-setting enabled..

Storage02 is connected to the company network via eth0. Storage02 and storage03 have a dedicted connection via eth3 and dedicated switch for the readydr-jobs. All connections are LAN, no internet/vpn involved.

Readydr-jobs are configured as push-jobs from storage02 to storage03 every hour.

 

At least once a day one ore more readydr-jobs fail with

"ReadyDR-Auftrag fehlgeschlagen: Unbekannter Fehler 255 [<job-name>]"

(roughly translated: ReadyDR-Job failed: Unkown error 255[<job-name>])

 

Last two days it were sometimes more than half the jobs which failed

 

Any help is highly appreciated.

Sven

3 Replies

  • StephenB's avatar
    StephenB
    Guru - Experienced User

    Look at the ethernet statistics on both NAS (which are in network_settings.log in the log zip file).  Perhaps also look at the ethernet stats on the switches on the path.

    • IX's avatar
      IX
      Aspirant

      Thank you,

      I followed your advice and this is the result:

      ethernet statistics storage02:

      eth3      Link encap:Ethernet  HWaddr e8:fc:af:e6:e7:a3  
                inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
                inet6 addr: fe80::eafc:afff:fee6:e7a3/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:4953775625 errors:0 dropped:0 overruns:0 frame:0
                TX packets:10754960373 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000 
                RX bytes:578561054079 (538.8 GiB)  TX bytes:15379770239021 (13.9 TiB)
                Memory:dfe00000-dfe1ffff 

      storage03:

      eth3      Link encap:Ethernet  HWaddr b0:b9:8a:43:c3:23  
                inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
                inet6 addr: fe80::b2b9:8aff:fe43:c323/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:31759593 errors:0 dropped:0 overruns:0 frame:0
                TX packets:3936203 errors:0 dropped:0 overruns:0 carrier:0
                collisions:0 txqueuelen:1000 
                RX bytes:46351098088 (43.1 GiB)  TX bytes:375613535 (358.2 MiB)
                Memory:dfe00000-dfe1ffff 

      I can not see any errors. Network looks fine to me.

      Switch is unmanaged, no logs available.

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        IX wrote:

        I can not see any errors. Network looks fine to me.


        It looks fine to me too.  I suggested checking this because there was a recent poster with the same error, and in his case the network connection was dropping.

         

        I think you'll need Netgear's help to diagnose this.  Perhaps PM mdgm-ntgr or another mod here, and ask them if they are willing to analyze your logs.

         

        If you are using the NAS hostname in the ReadyDR job(s), then perhaps you could try switching to the IP address.

         

        BTW, if you aren't using ipv6 on your network, I suggest disabling the protocol in the two NAS.  Sometimes Windows 10 will use the ipv6 local links, and performance can suffer if that happens. 

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