Picha

nostromo-diagnostics-20210102-2300.zip Sure, thank you

Thanks for the reply I cant see any error or even an attempt from UD trying to mount the NFS (if it was the right logfile) This is the only thing regarding i found, but this should be from the manual mounting: Jan 2 20:42:11 Nostromo unassigned.devices: Mount NFS command: /sbin/mount -t nfs -o rw,hard,timeo=600,retrans=10 '192.168.3.110:/volume1/Backup' '/mnt/remotes/synology' Jan 2 20:42:11 Nostromo rpcbind[27728]: connect from 127.0.0.1 to getport/addr(status) Jan 2 20:42:11 Nostromo kernel: RPC: Registered named UNIX socket transport module. Jan 2 20:42:11 Nostromo kernel: RPC: Registered udp transport module. Jan 2 20:42:11 Nostromo kernel: RPC: Registered tcp transport module. Jan 2 20:42:11 Nostromo kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Jan 2 20:42:12 Nostromo unassigned.devices: Successfully mounted '192.168.3.110:/volume1/Backup' on '/mnt/remotes/synology'. Jan 2 20:42:12 Nostromo unassigned.devices: Running common script: 'SanDisk_Ultra.sh' Jan 2 20:42:12 Nostromo unassigned.devices: Running device script: 'synology.sh' with action 'ADD'. As sad, the Status is online but it wont automount. Or do you mean its online but not fully started and UD cant mount it, discards it and doesnt try again ?

Hello, i have a NFS Share (Synology NAS) in UD but it doesnt auto-mount it. (auto mount is on) The NAS is only running on mondays (or at least thats the plan). When the NAS starts up, the status lamp (of the share) goes green and the button goes to orange "mount" Everything else is running fine. Except that i always have to mount it manually. Running on Unraid Version: 6.9.0-rc2 and UD Version 2021.01.01 Any ideas ? Thanks

Sure, sorry for also being late CPU: Intel Core i5 10500 Mainboard: MSI B460M-A Pro mATX, So.1200 with latest bios

Need some help with that. For curious reasons i added just the vbios to see what happens. What should i say, i got a display output ! yeaah Sadly went only well for just a few seconds, till my logfiles filled up with "vfio_region_write failed: Device or resource busy igpu" But i am happy to know, it should work somehow. Sooo... i made everything like you sad there. Except the "VFIO-PCI Config to stub 00:02.0". What do you mean with that ? I passed through the IGPU in the System Devices if its that. Long story short with your setting i cant even start my VM and get an Error message instead: "internal error: process exited while connecting to monitor: 2020-11-26T21:08:05.232046Z qemu-system-x86_64: -device vfio-pci,host=0000:00:02.0,id=hostdev0,bus=pci.0,addr=0x2,romfile=/mnt/disk3/isos/vbios_gvt_uefi.rom: Failed to mmap 0000:00:02.0 BAR 2. Performance may be slow 2020-11-26T21:08:05.237102Z qemu-system-x86_64: -device vfio-pci,host=0000:00:1f.3,id=hostdev1,bus=pci.0,addr=0x8: vfio 0000:00:1f.3: group 8 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver." Anything i overlooked ? Thanks you so far for your post, really helped me along. Edit: Just saw that the last error "....group 8 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver." is related to my passthroughed audio device. I will have a look at the kernel settings again. Edit Edit: Kernel settings were indeed wrong. everthing is working now.