[6.10.3] Multiple Errors (maybe connected?) - NFS timeout, Mover runs infinitely...

[Helmut]

Hey everyone,

 

I have a couple of problems that may be connected to each other. Sadly, I have no idea how to fix this. So maybe someone can help an amateur.

 

1. A couple of weeks ago I messed around with NFS shares in a VM. In that scenario the VM was the server and I wanted to connect Unraid as a client via unassigned devices. However, I could get it to work somehow and stupidly ended up with trying to connect to the share via terminal (which worked). I unmounted everything and did no other changes. Nevertheless the Unraid syslog is showing the following 24/7:

   Quote

   Aug 29 05:00:45 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:03:42 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:03:45 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:06:45 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:06:47 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:09:47 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:09:52 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:12:47 Tower kernel: nfs: server 192.168.178.75 not responding, timed out
   Aug 29 05:12:58 Tower kernel: nfs: server 192.168.178.75 not responding, timed out

   I have no idea why and how to stop that. I checked /etc/fstab but no changes or entries there. 
   
   I also used "ps -ef | grep mount" and it shows this:
    

   root      8344     1  0 Aug06 ?        00:00:00 /usr/sbin/rpc.mountd
   root     13133     1 99 07:19 ?        00:04:25 /usr/bin/qemu-system-x86_64 -name guest=Lubuntu_VPN,debug-threads=on -S -object {"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-8-Lubuntu_VPN/master-key.aes"} -blockdev {"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"} -blockdev {"driver":"file","filename":"/etc/libvirt/qemu/nvram/933ef657-8ddc-4609-91e1-1630bb83a213_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"} -machine pc-q35-6.2,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram -accel kvm -cpu host,migratable=on,host-cache-info=on,l3-cache=off -m 2048 -object {"qom-type":"memory-backend-ram","id":"pc.ram","size":2147483648} -overcommit mem-lock=off -smp 2,sockets=1,dies=1,cores=1,threads=2 -uuid 933ef657-8ddc-4609-91e1-1630bb83a213 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=39,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -boot strict=on -device pcie-root-port,port=16,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=17,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=18,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=19,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=20,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device pcie-root-port,port=21,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,multifunction=on,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -blockdev {"driver":"file","filename":"/mnt/cache/domains/Lubuntu_VPN/vdisk1.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"} -device virtio-blk-pci,bus=pci.4,addr=0x0,drive=libvirt-1-format,id=virtio-disk2,bootindex=1,write-cache=on -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/mnt/user/media/ -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=media,bus=pci.1,addr=0x0 -netdev tap,fd=40,id=hostnet0 -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:52:1f:b4,bus=pci.2,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0,index=0 -chardev socket,id=charchannel0,fd=38,server=on,wait=off -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -audiodev {"id":"audio1","driver":"none"} -vnc 0.0.0.0:1,websocket=5701,audiodev=audio1 -k de -device qxl-vga,id=video0,max_outputs=1,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
   root     16804 16720  0 07:21 pts/0    00:00:00 grep mount

   So some process seems to look for the VM and I don't know why.

2. The Mover is running infinitely. Nothigh happens (so no files are moved) but the GUI is showing this:
   
   Enabling Mover logging didn't change anything. The syslog is not showing a thing. I'm suspecting that this has something to do with problem #1.

 

Thank you for your help

 

Edited August 29, 2022 by Helmut
copypaste error

[JorgeB]

Type

mover stop

and reboot, should fix the NFS issue.

[Helmut]

Uhhh this is interesting. After the whole NFS ordeal I already rebooted everything. This is why I thought it make no difference.

 

However, stopping the mover and rebooting again as you said solved all of my problems (including that memory utilization was not shown in the dashboard??).

 

Thank you very much!