NAS

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

Recommended Posts

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.

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.