SOLVED Rsync error question

[onekanoobie]

I apologize for posting this here, but I am hoping someone may know the answer. I have tried searching and cannot find a very clear answer. I run several rsync tasks nightly to back up file from my Freenas server to my local windows server to then be stored offsite through Carbonite. Probably not the most elegant but it works. About a week or so ago I was notified of a critical error (Smart short test failure) on one of my drives. I have arraigned for the RMA already, however the same day I started getting the following error in my rsync log files:

Code:

2017/11/20 02:00:02 [47845] rsync: safe_read failed to read 1 bytes [sender]: Connection reset by peer (54)
2017/11/20 02:00:02 [47845] rsync error: error in rsync protocol data stream (code 12) at io.c(276) [sender=3.1.2]
or
2017/11/20 04:00:02 [55595] building file list
2017/11/20 04:00:06 [55595] rsync: fork failed in do_recv: Resource temporarily unavailable (11)
2017/11/20 04:00:06 [55595] rsync error: error in IPC code (code 14) at /home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/main.c(759) [receiver=3.0.4]
2017/11/20 04:00:06 [55595] rsync: connection unexpectedly closed (201 bytes received so far) [sender]
2017/11/20 04:00:06 [55595] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]

I have 4 tasks that run nightly and over the past 10 days maybe 2 or 3 have been successful. Most of the time the logs reflect the first error above. I believe that this issue is tied to the bad hard drive but have not been able to confirm that based on searching the errors codes. Can anyone confirm that is the issue? I am not having any other issues accessing data or files and the bad hard drive is still in place while I wait for the replacement.

I appreciate any help. Thanks

 

[dlavigne]

Were you able to resolve this with the new hardware?

 

[onekanoobie]

I just received the new drive and am planning to replace it today. I will let you know.

 

[onekanoobie]

For anyone interested, replacing the hard drive has resolved the issue. Seems like the read failure on the drive was causing the issue. Still don't really understand why but I am glad it is resolved.