the specified network name is no longer available

[cyberjock]

The IBM M1015.. but that's PCIe. I'm highly doubtful you're going to find a controller for a system that old. Most of the PCI/PCI-X stuff has 2TB disk size limits.

As old as that is, you're probably looking at a whole new system if you want to reliably use FreeNAS.

 

[PeterB]

I gave up on it - using a Gen8 HP MicroServer. It wasn't ready for me with SMB sharing from a Windows-based VM. That same MicroServer ran WinSvr 2012R2 perfectly, even had a higher throughput than the FreeNas did when it was set up (before it choked).

On another note, I have an old Dell PE 2970 w/Perc 5 that is running FreeNas fine in a similar role. Who knows.

 

[benji791]

Hello,

I'm experimenting the same problem with Freenas 9.2.1.6.
I'm running Freenas on top of ESXi serving other VMs on NFS datastore.
The VM is set up with PCI-Pass Through
This is a brand new installation with the following specifications.
BuildFreeNAS-9.2.1.6-RELEASE-x64 (ddd1e39)
PlatformIntel(R) Core(TM) i5-2400S CPU @ 2.50GHz
Memory8170MB
I'm using vmxnet3 with jumbo enabled (because i use the 10G link with my VMs). I've successfully tested jumbo and iperf is showing pretty good results.
I activated Active Directory and CIFS. I successfully joined my AD and started sharing with authorizations set to Windows standard on the dataset. The owner is my domain admin. I've been able after to apply my ACL from Windows.
After that I started running my windows backup towards freenas. They start to run but they fail after a very long time and gigs of data transferred. Here is the same error.

"The backup was not successful. The error is: The network name cannot be found. (0x80070043)."

So I started to investigate in the smb logs and I found this (after putting log level to full in freenas) in

[2014/07/30 18:10:10.031613, 3] ../source3/smbd/trans2.c:3092(smbd_do_qfsinfo)
smbd_do_qfsinfo: level = 1001
[2014/07/30 18:10:10.040965, 3] ../source3/smbd/trans2.c:3092(smbd_do_qfsinfo)
smbd_do_qfsinfo: level = 1005
[2014/07/30 18:10:10.041388, 3] ../source3/smbd/trans2.c:3092(smbd_do_qfsinfo)
smbd_do_qfsinfo: level = 1007
[2014/07/30 18:10:10.041695, 3] ../source3/lib/sysquotas.c:433(sys_get_quota)
sys_get_vfs_quota() failed for mntpath[Computers/BigbrainIII] bdev[(null)] qtype[2] id[20500]: Operation not supported
[2014/07/30 18:10:10.041752, 3] ../source3/lib/sysquotas.c:433(sys_get_quota)
sys_get_vfs_quota() failed for mntpath[Computers/BigbrainIII] bdev[(null)] qtype[4] id[20513]: Operation not supported
[2014/07/30 18:10:23.627940, 1] ../source3/smbd/service.c:1130(close_cnum)
192.168.1.122 (ipv4:192.168.1.122:3443) closed connection to service sauvegardes
[2014/07/30 18:10:23.748203, 3] ../source3/smbd/server_exit.c:221(exit_server_common)
Server exit (NT_STATUS_CONNECTION_RESET)

I see this each time before getting the windows error. It seems to be related to quota but I haven't set any. Also the null value passed in parameter is pretty strange.

Do you have any idea? Any way to disable this? I looked around at samba resources but didn't find anything relevant.

Benji

 

[benji791]

Hello again,
I forgot two precisions :
- I'm using smb2
- the client OS is a physical desktop on the lan with 1GB connection
Also, I have tested the bandwidth beetween freenas and the client and I can saturate my 1GB link. But I my samba transfers only go up to 30-35MB/s with freenas. On the same pool/dataset, I easily saturated it with Openindiana which is the OS I come from (my pool also :) )
The dataset I was testing with had dedup (because several Win OS image backup dedup easily). Right now, I'm trying the same test on another dataset with no comp/dedup enabled and it does not seem to be better regarding speed. :) Wait and see if I have the same error before the end.

Benji

 

[benji791]

Hello,

Let me give feedback even if nobody answered me :( . Maybe this will help someone else.
The issue was absolutely not related to freenas. I'm using windows backup to backup my Win7 clients. I hadn't noticed that in my library's I had a reference to a network path that was not shared yet (this is a trick I use to have my documents on the nas included in the library). So in fact windows was just not able to backup this specific folder. The way around will be to backup not library but selected folders.

Hope this will help someone else.

Benji.

 

[greebles]

I'm also experiencing this issue on FreeNAS-9.2.1.6-RELEASE-x64 (as well as a couple previous releases). This used to work fine, but now on large transfers using a Windows machine, FreeNAS will just disappear from the network. I can then no longer access any shares, nor the web interfaces for the Web Admin or anything I'm running in jails (e.g. sabnzbd). However, I can still access the server with a directly connected keyboard and monitor.

Sometimes, after a period of time, I can again see the shares. Sometimes I just reboot, which fixes it...until I do another large transfer.

This is a very frustrating situation. I'm running an ASRock C2750D4I board with 16gigs of ECC RAM. I have 6 3TB WD Red drives in RAIDZ2.

 

[NickSA]

I am having the exact same problem as greebles. I have tried everything from SMB2 all the way up to SMB3_00 and it happens with each mode. I have tried different SATA cables for the drives and different network cables and it doesn't make any difference. Sometimes I can transfer as much as 100GB before it will fail, other times I can only manage around 10GB before it fails.

At this point I am just trying to get my DATA off the box so if anybody has any pointers it would be greatly appreciated (I have tried to use NFS but I have Windows 8.1 Pro so this is not an option for me).