gurulee

@guru69 brilliant! Tested and working on my side with dockers and vm's. Thank you! Sent from my SM-N960U using Tapatalk

I just upgraded from 6.7.2 to 6.8.1 successfully! Thank you!

I noticed as today that my pre-existing speed limits for uploads are no longer enforced. Is this a known issue from a recent update?

THANK YOU! Following these steps exactly got me passed the import of Wazuh VMDK "kernal panic fatal error'. It is now booting! :-) Now onto configuring it hopefully.

Good morning all! When I attempted to start this docker today, it would not start with this error in the logs: Removing docker/image and reinstalling it fixed it for now. But is this going to come back? I generally leave the docker stopped and only run it when I'm doing scans.

Thank you for making this available.

Greetings! I did a quick search and did not come across anything; I currently monitor unRAID using the Grafana/InfluxDB using this dashboard https://github.com/gilbN/theme.park#graforg. It does a very nice job for Docker CPU and RAM usage monitoring. Is there a similar solution for monitoring VM performance running on unRAID?

Upgraded from 6.7.0 with no noticeable issues. Thank you!

Greetings all! I am noticing that my Sonarr docker is averaging 60% cpu usage, but all other dockers average only 0-2%. I do not use any remote SMB paths in Sonarr and its also pinned at 1 cpu core like all my other related dockers. Any tips/tweaks to address this?

I just successfully upgraded from 6.6.7 to 6.7 with 3 vm's with multiple NIC's passed-through and approx 20 dockers. THANK YOU! Sent from my SM-N960U using Tapatalk

This works method works very well for me:

I am also seeing this error and I am on unraid 6.6.7 and just use Ombi site-conf file. All appears to be working though, but I am concerned about performance and security. nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

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.

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.

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.

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

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...