I just recently upgraded from v5 rc12 or so to v5.0.5, installed some new v5 plugins, replaced my parity drive with a larger (4TB) drive, and put the old parity drive into use as a data drive.

 

Now when I try to transfer a group of files to the server I get a network transfer error 0x8007003B.  I think it is something to do with SMB restarting but otherwise I don't really know what is happening. 

 

I have tried to remove all the plugins except unmenu in case it was a memory issue but it hasn't helped. 

 

I saw another topic that had that error code but it didn't appear to offer a solution. 

Unraid_Error_Log.txt

Searching Google on the error code brings up the suggestion to disable antivirus and firewall on your Windows box and test the transfer. Since you did all that work on your unRAID system, it wouldn't hurt to double-check network cabling. Router firmware up to date? Reviewing your unRAID syslog may reveal errors on the unRAID side; posting a copy of it covering the period when the error happens is helpful.

Did I get the wrong error log portion posted?  It's should be there above the screenshot.

 

I also replaced the sata cable with another and moved the hard drive power to another cable coming out of the power supply instead of the same cable run, so hopefully they are different rails now.

 

Nothing changed on the network/switch/router setup from before the upgrades.  The section of the network between my PC and the Unraid server shouldn't go to the router anyway.  Should just be a couple of gigabit switches. 

Oops, sorry I missed it earlier. You have about an 11 minute span of your log. At what point (time) do you encounter a transfer error?

 

Another way to approach this is to bring up the log window during normal operation. That would mean clicking on the "Log" button way over on the far right on the main page of the GUI. That's a constantly refreshing window. At this point start the file transfer at the point where it fails you can copy/paste any entries into a text file. Or at least you'll have a time stamp to go back into the log later.

 

I see the entries where files have changed and SMB is restarting, but I don't think that's what's causing your problems.