Jump to content

Network name is no longer available


Recommended Posts

Posted (edited)

I am in the process of copying the contents of a whole drive to my Unraid array. Since the drive is encrypted with BitLocker I have to do this through a Windows virtual machine.

 

The problem I am facing is that the network share seems to become unavailable intermittently. After about 10 to 115 seconds it comes back. This does not seem to occur if I am not copying files in the VM. During the outage of the network share the share becomes unavailable for all clients, not just the VM.

 

In the screenshot below you can see that the backup software I am using (Bvckup 2 Pro) is giving me errors that the network name is no longer available. However, the problem persists even if I am just copying files using Windows Explorer.

 

I don't know if this is a common issue, but I was hoping anyone could point me in the right direction, as I have no idea how to troubleshoot this.

 

2024-06-06_15-08-25.thumb.png.dea3520800613224df2d45dcd5956c9c.png

 

Here is what I have tried:

 

  • Restarting Unraid
  • Stopping all docker containers
  • Assigning more RAM to the VM (now 16 GB)
Edited by Bob-omb
Link to comment
1 hour ago, Bob-omb said:

 

The link you provided is for resetting the password. I am not sure how to get diagnostics.

The link is meant to be auto-generated so it looks like Limetech have something messed up at their end.  Try this instead.  The online documentation is accessible via the Manual link at the bottom of the Unraid GUI and in addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

Link to comment
Posted (edited)

 

 

OK, so I managed to take a diagnostic dump right after I noticed a freeze in the SMB. The freeze happened around 11:33.

In this case, I copied a bunch of large video files to the share called backup on the array.

 

<------log removed------>

Edited by Bob-omb
Link to comment
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_id' in directory 'ep02' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_context_array' in directory 'ep02' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_id' in directory 'ep03' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_context_array' in directory 'ep03' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_id' in directory 'ep06' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_context_array' in directory 'ep06' already present!

 

Do you know where these debugfs lines comes from? I don't believe this is stock, at least not used to seeing them.

Link to comment
Just now, JorgeB said:
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_id' in directory 'ep02' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_context_array' in directory 'ep02' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_id' in directory 'ep03' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_context_array' in directory 'ep03' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_id' in directory 'ep06' already present!
Jun  7 11:26:25 nova kernel: debugfs: File 'stream_context_array' in directory 'ep06' already present!

 

Do you know where these debugfs lines comes from? I don't believe this is stock, at least not used to seeing them.

 

Uhm, I don't know what debugfs is.

Link to comment

Sure. Here it is.

 

image.thumb.png.8212fa7431164fba6c7db12697dbc1e4.png

 

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='1'>
  <name>W10 IoT ENT LTSC 2021 x64 en-US</name>
  <uuid>560f1466-c2db-571b-f1ea-453ec93e1b20</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>16777216</memory>
  <currentMemory unit='KiB'>16777216</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <source type='memfd'/>
    <access mode='shared'/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='3'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='5'/>
    <vcpupin vcpu='6' cpuset='6'/>
    <vcpupin vcpu='7' cpuset='7'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-7.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/560f1466-c2db-571b-f1ea-453ec93e1b20_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv mode='custom'>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='4' threads='2'/>
    <cache mode='passthrough'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/cache/vms/W10 IoT ENT LTSC 2021 x64 en-US/vdisk1.img' index='2'/>
      <backingStore/>
      <target dev='hdc' bus='virtio'/>
      <serial>os</serial>
      <boot order='1'/>
      <alias name='virtio-disk2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.248-1.iso' index='1'/>
      <backingStore/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <alias name='ide0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='qemu-xhci' ports='15'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </controller>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:62:44:4b'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-W10 IoT ENT LTSC 202/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <channel type='qemu-vdagent'>
      <source>
        <clipboard copypaste='yes'/>
        <mouse mode='client'/>
      </source>
      <target type='virtio' name='com.redhat.spice.0' state='disconnected'/>
      <alias name='channel1'/>
      <address type='virtio-serial' controller='0' bus='0' port='2'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='no'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <audio id='1' type='none'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x174c'/>
        <product id='0x55aa'/>
        <address bus='2' device='3'/>
      </source>
      <alias name='hostdev0'/>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

 

Link to comment

Googling that debugfs error it appears to be mostly harmless, though can't rule out if it's related, especially since the timing is around when the issue occurred.

 

Regarding the VM config, it looks good to me, but try changing the virtual NIC to virtio-net, and see if it's any better.

 

 

Link to comment

 

 

Here is a video recording showing what is happening. It shows that the copy times out for no apparent reason. On the right side, I am continually pinging my Unraid server, which always responds. On the left, I am using ping.canbeuseful.com/ to continually check for WAN dropouts in case there are problems with my router.

 

Everything seems normal. However, I should mention that I had a bunch of PCIe warnings in the log previously. I don't know if that is the problem.

 

I am honestly getting really frustrated with Unraid. "Switch to Unraid," they said. "It's great," they said.... 😂 I have had almost nothing but problems since I started some weeks ago. I am super close to giving up and going back to Windows.

 

I really appreciate getting some help, though. I really, really don't want to start over, and I don't even know if that will solve the problem.

Link to comment

Without anything logged can't guess what the problem is, don't remember anyone else with a similar issue, if you are doing this because of Bitlocker, I would suggest using the Windows VM to decrypt the disks instead, and them mount them directly with the UD plugin to copy the data.

Link to comment

Thanks for the suggestion. However, decrypting the drive will take forever, and I will have to wipe it afterward to stay secure, so it's not really a practical option. I also have multiple drives with TBs of data.

 

Did you look at the other thread I linked? Do you think it could be the culprit here?

 

In the meantime, I am going to try another VM; perhaps the latest Windows 11 will work better...

Link to comment

Ok. So here is what I have tried:

  • Changed the line to just pcie_aspm=off
  • Shut down Unraid. Restarted.
  • Installed a new Windows 11 VM with the same settings as the previous VM with Windows 10 LTSC. I am trying the consumer version now.

It's the same issue. The speed goes down to 0, and then, after a minute or two, it's back again.

 

I am out of ideas and it is getting late. Maybe tomorrow I will try:

  • Copy files from a drive without BitLocker
  • Copy files to a cache drive
  • Copy files to another share but on the array

 

But I am really shooting in the dark over here. 😢

2024-06-07T22-53-35.png

2024-06-07T22-55-26.png

Link to comment

I am still having this issue.

 

What I have tried:

  • Copy using Robocopy (same issue)
  • Copy from a different disk (same issue)
  • Copy from a different computer (tried a physical computer instead of the VM in Unraid (same issue)
  • Tried different Windows versions (10 and 11). (same issue)
  • Connected the source disk directly to the SATA port on my motherboard instead of using a docking station. (same issue)
  • Made a new share on another disk on the array, just in case there is something wrong with that particular disk. (same issue)
  • Reinstalled Unraid (but with the same array and shares). (same issue)
  • Connected computers with quality LAN cables.

I am kind of out of ideas. Any help would be much appreciated. It's already taking forever to transfer terabytes of data to the array. Having the SMB freeze for minutes at a time surely does not help. 😥

 

Link to comment

I will do that later today if I have time.

 

I forgot to say I also got rid of the LSI HBA card. So now the array is connected directly to the motherboard.

 

Do you, by any chance, know where in the logs I should look to troubleshoot SMB issues? I mean, there is probably not much help digging into the logs if none of this is actually logged.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...