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

Re: ReadyNAS 316 - Error 0x8007003B: An unexpected network error occurred.

ItsPeter2
Guide

ReadyNAS 316 - Error 0x8007003B: An unexpected network error occurred.

Have had this unit for years without issue, since my last drive replacement I'm now getting this when moving files across to the device:

 

An unexpected error is keeping you from moving the file. If you continue to receive this error, you can use the error code to search for help with this problem.

 

Error 0x8007003B: An unexpected network error occurred.

 

It is intermittent, but frequent enough to be annoying. Usually the entire file looks like it has copied over, and the error comes up right at the end - it looks like the required acknowledgement doesn't come back to the source, and it thinks the file move hasn't worked (when moving a batch, the whole attempt then falls over). This is from Windows 7/10 & Mac devices, the Windows devices are connected locally via the same Netgear GS316 switch that everything is plugged into, Mac has also been tried locally (normally WiFi).

 

As far as I can determine, this only started happening after my last drive swap in the unit, the current drives are as follows:

Disk 1 - ST12000VN008

Disk 2 - ST16000NT001 (was ST8000VN0022)

Disk 3 - ST16000NT001

Disk 4 - ST8000VN0022

Disk 5 - ST12000VN008

Disk 6 - ST12000VN008

 

Firmware 6.10.10.

 

Overall the file system sometimes takes a while to respond / bring up a directory listing, it looks like it just churns away sometimes, and is probably causing a timeout on the sending system.

 

Any suggestions on anything else I might try or look at would be much appreciated.

Message 1 of 4
StephenB
Guru

Re: ReadyNAS 316 - Error 0x8007003B: An unexpected network error occurred.


@ItsPeter2 wrote:

 

Error 0x8007003B: An unexpected network error occurred.

 

It is intermittent, but frequent enough to be annoying. Usually the entire file looks like it has copied over, and the error comes up right at the end - it looks like the required acknowledgement doesn't come back to the source, and it thinks the file move hasn't worked (when moving a batch, the whole attempt then falls over). This is from Windows 7/10 & Mac devices, the Windows devices are connected locally via the same Netgear GS316 switch that everything is plugged into, Mac has also been tried locally (normally WiFi).

 

As far as I can determine, this only started happening after my last drive swap in the unit, the current drives are as follows:

 


If you have some familiarity with the linux command line interface, then I'd use that, and run top to see if anything is generating a lot of activity on the NAS.

 

You could also download the log zip file, and look in there for problems.  I am wondering if you are seeing any activity in readycloud.log or leafp2p.log.

 

If you have the AV service or the file search enabled on the NAS, you could try disabling both and see if it makes any difference.

Message 2 of 4
ItsPeter2
Guide

Re: ReadyNAS 316 - Error 0x8007003B: An unexpected network error occurred.

top isn't showing much, smdb at about 4% cpu, every so often md126_raid5 / md124_raid5 bounce up to about 20% cpu, but only briefly.

 

readycloud.log & leafp2p.log are both empty.

 

AntiVirus and File Search are disabled. ZeroTier is probably the only "non-standard" app I have running, although that's been on there a while with no issue. But I can try turning it off to see if any change.

 

The whole thing is singing along at the moment, browsing directories is bring them up pretty much instantly. I'll run top in the background when moving the next batch of files across, maybe if it starts churning it will hint at the issue.

Message 3 of 4
ItsPeter2
Guide

Re: ReadyNAS 316 - Error 0x8007003B: An unexpected network error occurred.

I managed to run top a few times when the issue was occurring, the only additional process that seemed to be running was btrfs-transacti - I wouldn't say it was using a lot of resources, just that it was running while the issue was happening.

 

For the past week now, the issue has simply stopped. When it was happening, it largely seemed like some problem trying to bring up / access / write to the directory structure. I've been rearranging a lot of files myself, perhaps that cleared something up or triggered a rebuild of some kind. A couple of the PCs here also received a Windows 10 update, although the issue had occurred from everything (Mac/Win7/XP), so unless the Win10 machines were doing something unfriendly, I doubt that was the issue. But who knows.

Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 826 views
  • 1 kudo
  • 2 in conversation
Announcements