Cannot copy ... : The specified network name is not longer available

[Joe L.]

ok, one more question before I hit this tonight. Does the copy have to be done EVERYTIME the system is booted via the go script, or does it stay once put in? I'm assuming everytime you reboot, as the smdb is copied from the flash each time.

You are correct, The copy to "/usr/sbin" has to be done every time the system is re-booted.   That is because every time you reboot the "/usr/sbin" directory is created in RAM, and is initially populated with the version of smbd that is contained in the "bzroot" file.  (bzroot is a form of a compressed archive, somewhat similar to a zip file)

When unRaid is booted, the bzroot file is "unzipped" into the in-memory filesystem.  That puts the buggy version of smbd into place in /usr/sbin/smbd.  As part of its start-up, unRaid also starts "smbd" running.
   
When the "go" script executes, the extra lines we added stops the"smbd" process, copies the newer "smbd" file from the flash drive to /usr/sbin/smbd, and then re-starts "smbd"  (as part of samba)

Joe L.

[wanton]

Tested 3.0.26a and it's working without any problems.

[limetech]

Brilliant work people ! Im so glad I started this thread.

Agreed!  As you probably know, 4.2 was released today without this fix; however, I'll produce a 4.2.1 release A.S.A.P. that includes Samba 3.0.26a.

[Fountainhead]

I loaded 4.2.1 this morning and the performed three tasks that had a high probability of producing the error...cloning a DVD directly to a user share with Clone DVD, and compiling two DVD's directly to a user share with TMPGEnc DVD Author.  All three finished successfully after installing 4.2.1.

I wouldn't call it conclusive as the error rate was never 100% for these things, but three consecutive successful events in the first three tries seems like a pretty good indication that 4.2.1 may have rectified this problem.

[poopiepants]

I am seeing this issue with 4.5 beta 6.
When copying files I get the same error:

The specified network name is not longer available

My memory in unraid is completely gone and as soon as I cancel the error dialog it returns.


Sometimes copying one large file it will go through but not release the memory.
I will attach a screen shot.

[yelnatsch517]

Was there ever a resolution to this issue?  I'm getting the same problem when copying BluRay ISOs.  Every now and then, I will get this error.  Using unRaid 4.7 and Teracopy.

Nothing else is done on with the unRaid machine during the transfer.

[parkesjg]

I also am having the same problem and would be interested if there was any resolution to this.

I did notice that one of my WD Green drives did a spin down at 4:18 a.m. during one of the copies (was doing multiple copies at the time) and the problem then manifested itself about an hour later.


Mar 5 04:18:24 Tower kernel: mdcmd (44): spindown 2
Mar 5 05:32:46 Tower kernel: mdcmd (45): spindown 2
Mar 5 05:32:46 Tower kernel: mdcmd (46): spindown 3
Mar 5 06:12:40 Tower kernel: mdcmd (47): spindown 1
Mar 5 06:13:51 Tower kernel: mdcmd (48): spindown 4
Mar 5 06:33:40 Tower emhttp: Spinning up all drives...
Mar 5 06:33:40 Tower kernel: mdcmd (49): spinup 1
Mar 5 06:33:40 Tower kernel: mdcmd (50): spinup 2
Mar 5 06:33:40 Tower kernel: mdcmd (51): spinup 3
Mar 5 06:33:40 Tower kernel: mdcmd (52): spinup 4


And here is the log from TeraCopy:

5:12:23 AM Error writing JANE_EYRE.iso
5:12:23 AM [0/60] The specified network name is no longer available.

And here is the system log:

Mar  4 20:27:41 Tower emhttp_event: svcs_restarted
Mar  4 21:25:04 Tower kernel: mdcmd (35): spindown 4
Mar  4 21:30:56 Tower kernel: mdcmd (36): spindown 2
Mar  4 21:31:47 Tower kernel: mdcmd (37): spindown 1
Mar  4 23:28:59 Tower kernel: mdcmd (38): spindown 1
Mar  4 23:29:10 Tower kernel: mdcmd (39): spindown 4
Mar  5 00:11:00 Tower kernel: mdcmd (40): spindown 2
Mar  5 02:48:56 Tower kernel: mdcmd (41): spindown 2
Mar  5 03:10:21 Tower kernel: mdcmd (42): spindown 1
Mar  5 04:18:13 Tower kernel: mdcmd (43): spindown 1
Mar  5 04:18:24 Tower kernel: mdcmd (44): spindown 2
Mar  5 05:32:46 Tower kernel: mdcmd (45): spindown 2
Mar  5 05:32:46 Tower kernel: mdcmd (46): spindown 3
Mar  5 06:12:40 Tower kernel: mdcmd (47): spindown 1
Mar  5 06:13:51 Tower kernel: mdcmd (48): spindown 4
Mar  5 06:33:40 Tower emhttp: Spinning up all drives...
Mar  5 06:33:40 Tower kernel: mdcmd (49): spinup 1
Mar  5 06:33:40 Tower kernel: mdcmd (50): spinup 2
Mar  5 06:33:40 Tower kernel: mdcmd (51): spinup 3
Mar  5 06:33:40 Tower kernel: mdcmd (52): spinup 4


Jim

[RobJ]

I also am having the same problem and would be interested if there was any resolution to this.

The specific problem of this v4 thread was resolved, back a few posts.  That error message is somewhat generic, generally a timing problem, often a client issue - the client app timing out, unwilling to wait long enough.  It would be better to post again in the v5 General Support board, with your details.