guruleenyc

You can use the simple option and fire up WinSCP and get properties of file and give it 777. Or do it by cmd line using chmod.

This resolved my issue NIC detection too! My problem was I was going with the default machine type after changing it to: i440fx-3.0. Also I changed VM settings interface model type: <model type='e1000-82545em'/> Now the Sophos UTM 9.5 is seeing at least one network card during installation. At least now I can complete the install and then figure out what I want to use as my second NIC. Thanks!!! BUT, now I get an RPM error 3/4 through the installation and it aborts. To get past this error, I re-ran the installer as 32bit kernel and opting out of the Enterprise tools option. Not out of the woods yet! Now that install finished, it boots to Grub prompt.... 😞

Thanks for the quick reply! My VM interface settings are: <interface type='bridge'> <mac address='52:54:00:c2:66:6d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> Not sure how to get the virtio drivers loaded into the VM, there's no option for driver ISO under vm settings.

Trying to boot off install ISO with br0 as interface in VM settings, but installer states "no network card was found". Any help would be appreciated.

I am migrating my SophosUTM from ESXi vmdk to Unraid VM. I followed these steps: ESXi VMDK to Unraid KVM VM 1) Stop the VM in ESXI 2) Export the VM as an OVF template 3) Make a folder on your unraid box called /mnt/user/domains/<NameOfVM> 4) Copy the VMDK file from the export folder to the folder you created in step 3 5) Run the following command: "qemu-img convert -p -f vmdk -O raw <vmdkfile> <vmdkfilename>.img". This will convert the file to the KVM/OVirt format. 6) Create a new VM, change the bios to "SeaBIOS", and choose the .img file created in step #5 for the first hard drive. At this point, if it's a linux machine, you can boot it and it pretty much Just Works (tm). If it's a windows box, you've got a couple more steps. I'm using the aforementioned Linux VM settings. BUT during boot it hangs at "could not find /dev/disk/by-label/root", please see screenshot. The disk type is SATA which points to my .img file. Can someone help me get past this?

Thank you for this thread. I eagerly await unraid 6.7.x for this plugin again.

Allow me to clarify... Unraid mgmt: br0/eth0 - on 172.16.1.0/24 pfsense LAN interface: eth2 - on 172.16.1.0/24 (passed-thru NIC) pfsense WAN interface: eth3 - on 192.168.1.0/24 (passed-thru NIC) ***NIC for pfsense is not blacklisted in syslinux config, rather just allowing unsafe interrupts and specifying NIC in VM XML That being said, pfsense LAN interface is seeing traffic for docker0 (172.17.1.0/24) in firewall logs and being denied. Should this be expected?

Sorry about that; so unraid is on br0 (eth0) and pfsense LAN is on same subnet as bri0 using pass-thru NIC port (eth2). The pfsense WAN interface (eth3) is not on br0 or the same subnet as unraid mgmt network. Eth3 connects to an upstream switch. I only have one bridge (br0) in unraid. Any ideas why pfsense is seeing docker0 subnet traffic coming in on the LAN interface?

My br0 is 172.16.0.0/24 My docker0 is 172.17.0.0 Pfsense VM LAN is 172.16.1.x on a passed-through NIC Why is pfsense see traffic src from 172.17.0.0 (docker0) and of course its being denied by FW rules, should the docker0 subnet be bridged with br0 and all traffic src from 172.16.1.0/24 ?

Currently I have a dual onboard NIC and a dual Intel Pro/1000 PCIe NIC. I pass-through the Intel dual NIC and use both dedicated ports in pfsense for max performance. I had to add the add the allow unsafe interrupts in my syslinux config though.

This was a helpful post! Thank you.

I set this up per tutorial, but the banner script runs with no output in script window and empty subfolders in download path on array. Is this working for anyone else currently? Getting this when running icon sync script: rsync: link_stat "/mnt/user/icons/icons/store/*" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1189) [sender=3.1.3] UPDATE: Reset permissions recursively on /mnt/icons share, now it is working! THANK YOU! (guess I need more coffee)

AWESOME! This resolved the same error for me as well on an IBM x3200 M3 Thank you!

The nic is in separate groups already without override. Would I still need to move my card?

I followed the steps in @SpaceInvaderOneto passthrough my NIC to a pfsense vm, but I'm getting an error at vm start. Please see my post here: Does anyone have any ideas to help me get past this? UPDATE: this fixed my issue: https://forums.unraid.net/topic/37959-guide-passing-through-network-controllers-to-unraid-6-virtual-machines/?do=findComment&comment=592661 Brb dinner

I followed this guide to install pfsense as vm on unraid and the required steps to passthrough the NIC (Intel Pro/1000 dual port), but when I try to boot the pfsense VM I get this error: "internal error: process exited while connecting to monitor: 2019-04-20T15:41:25.512263Z qemu-system-x86_64: -device vfio-pci,host=10:00.0,id=hostdev0,bus=pci.3,addr=0x0: vfio error: 0000:10:00.0: failed to setup container for group 17: failed to set iommu for container: Operation not permitted" I also tried the 'enable pcie acs override" option which did not seem to help. Group 17, 18 is my card in 'system devices': "IOMMU group 16:[8086:10d3] 0b:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection IOMMU group 17:[8086:105e] 10:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06) IOMMU group 18:[8086:105e] 10:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06) IOMMU group 19:[8086:10d3] 15:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection" Can someone help me get this working? UPDATE: this fixed my issue: https://forums.unraid.net/topic/37959-guide-passing-through-network-controllers-to-unraid-6-virtual-machines/?do=findComment&comment=592661

Anyone have a pfsense icon already made? This might work...also PIA VPN logo

I think he is trying to use 1 of the ports on a NIC for a VM. This is my issue too. Is it possible to split a dual NIC so one port is used by unraid and the other port can be available for an unraid vm?

Update: I am trying to migrate a SophosUTM from VMware ESXi (vmdk) to Unraid as a VM. I following these above settings and it still not seeing the disk. It boots to "waiting for device /dev/disk/by-label/root to appear", then it results in "could not find /dev/disk/by-label/root" Any ideas?

Thank you also for sharing and confirming!

Yeah I am seeing this on a couple drives as well, especially when in high utilization. I have changed the SATA breakout cables as well and it did not resolve it. Perhaps the drives are going...

Just installed this to possibly replace Headphones. However, I'm on the Artist import process after pointing it to my large music collection. It is taking forever to allow import and resolve artists... Also if my browser closes or time-out, the import process seems to start from the beginning again. I am seeing this in the Lidarr logs: Error|AddArtistService|The operation has timed out.: 'https://api.lidarr.audio/api/v0.3/artist/fa6521a7-56b5-4e56-b946-fda469becba9?primTypes=Album&secTypes=Studio&releaseStatuses=Official' Any workaround on this? UPDATE: Fixed my issue, which was adjusting my pfsense fw rule to redirect traffic for api.lidarr.audio out wangw instead of pia vpn.

Bump; anyone have similar problems with openVMTools_auto.plg-10.2.5? I'm not totally convinced its the openvmtools....

UPDATE: I uninstalled openVMTools_auto.plg-10.2.5 on my unRAID 6.5.2 and my Docker updating seems back to normal. But my plugin update check appears to hang indefinitely. The only issue I am seeing that may be related is the Fix Problems plugin reports this: But at the CLI I can ping by DNS and resolve DNS addresses. Moreover, Docker updates succeed. Any ideas?

UPDATE: I uninstalled openVMTools_auto.plg-10.2.5 on my unRAID 6.5.2 and my Docker updating seems back to normal. But my plugin update check appears to hang indefinitely.