IpDo

Ok, I've just removed the 3 unused VMs. removed the bad zigbee stick as well. restarted the logs - seems to be fine now. Any one got an idea about the 2nd issue (missing dockers in the manager)? after stopping the docker, this is what I see in the log: ... e":"can not get logs from container which is dead or marked for removal"} e":"No such container: eb3bc92ef7d0"} e":"No such container: eb3bc92ef7d0"}

Before removeing the log files i wanted to check the sizes. it led me to this: root@Tower:/var/log# ls -l total 3872 -rw------- 1 root root 0 Apr 7 2021 btmp -rw-r--r-- 1 root root 0 Apr 10 2020 cron -rw-r--r-- 1 root root 0 Apr 10 2020 debug -rw-rw-rw- 1 root root 518 Sep 16 15:42 diskinfo.log -rw-rw-rw- 1 root root 66415 Sep 16 15:40 dmesg -rw-rw-rw- 1 root root 12288 Oct 26 19:05 docker.log -rw-r--r-- 1 root root 0 Jun 16 2020 faillog -rw-r--r-- 1 root root 0 Apr 8 2000 lastlog drwxr-xr-x 3 root root 140 Oct 24 04:40 libvirt/ -rw-r--r-- 1 root root 0 Apr 10 2020 maillog -rw-r--r-- 1 root root 0 Apr 10 2020 messages drwxr-xr-x 2 root root 40 May 16 2001 nfsd/ drwxr-x--- 2 nobody root 60 Sep 16 15:42 nginx/ lrwxrwxrwx 1 root root 24 Apr 7 2021 packages -> ../lib/pkgtools/packages/ drwxr-xr-x 5 root root 100 Sep 16 15:41 pkgtools/ drwxr-xr-x 2 root root 300 Oct 26 19:47 plugins/ -rw-rw-rw- 1 root root 0 Sep 16 15:41 preclear.disk.log drwxr-xr-x 2 root root 40 Sep 16 15:44 pwfail/ lrwxrwxrwx 1 root root 25 Apr 7 2021 removed_packages -> pkgtools/removed_packages/ lrwxrwxrwx 1 root root 24 Apr 7 2021 removed_scripts -> pkgtools/removed_scripts/ lrwxrwxrwx 1 root root 34 Sep 16 15:41 removed_uninstall_scripts -> pkgtools/removed_uninstall_scripts/ drwxr-xr-x 3 root root 180 Sep 16 15:51 samba/ lrwxrwxrwx 1 root root 23 Apr 7 2021 scripts -> ../lib/pkgtools/scripts/ -rw-r--r-- 1 root root 0 Apr 10 2020 secure lrwxrwxrwx 1 root root 21 Apr 7 2021 setup -> ../lib/pkgtools/setup/ -rw-r--r-- 1 root root 0 Apr 10 2020 spooler drwxr-xr-x 3 root root 60 Jul 16 2020 swtpm/ -rw-r--r-- 1 root root 917504 Oct 26 21:28 syslog -rw-r--r-- 1 root root 1491281 Sep 28 04:39 syslog.1 -rw-r--r-- 1 root root 1457028 Sep 26 04:39 syslog.2 -rw-rw-rw- 1 root root 0 Sep 16 15:40 vfio-pci -rw-rw-r-- 1 root utmp 6912 Sep 16 15:41 wtmp root@Tower:/var/log/libvirt# ls -l total 127192 -rw------- 1 root root 129273720 Oct 26 21:34 libvirtd.log -rw------- 1 root root 967863 Sep 19 04:40 libvirtd.log.5.gz drwxr-xr-x 2 root root 60 Sep 16 15:42 qemu/ -rw------- 1 root root 0 Sep 16 15:42 virtlockd.log -rw------- 1 root root 0 Sep 16 15:42 virtlogd.log the "libvirtd.log" seems to be the one the clogs the logs if i'm not mistaken. I've attached it compressed is it 123mb raw. the log seems to be this (below) on repeat: 2021-09-19 01:40:03.722+0000: 11980: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/pfSenseVM/vdisk1.img: No such file or directory 2021-09-19 01:40:03.722+0000: 11980: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/pfSenseVM/vdisk1.img': No such file or directory 2021-09-19 01:40:03.750+0000: 11982: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/pfSenseVM/vdisk1.img: No such file or directory 2021-09-19 01:40:03.750+0000: 11982: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/pfSenseVM/vdisk1.img': No such file or directory 2021-09-19 01:40:03.753+0000: 11980: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/pfSenseVM/vdisk1.img: No such file or directory 2021-09-19 01:40:03.753+0000: 11980: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/pfSenseVM/vdisk1.img': No such file or directory 2021-09-19 01:40:03.758+0000: 11981: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/pfSenseVM/vdisk1.img: No such file or directory 2021-09-19 01:40:03.758+0000: 11981: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/pfSenseVM/vdisk1.img': No such file or directory 2021-09-19 01:40:03.764+0000: 11983: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/pfSenseVM/vdisk1.img: No such file or directory 2021-09-19 01:40:03.764+0000: 11983: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/pfSenseVM/vdisk1.img': No such file or directory 2021-09-19 01:40:03.861+0000: 11983: error : qemuOpenFileAs:3175 : Failed to open file '/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J9BB442595': No such file or directory 2021-09-19 01:40:03.882+0000: 11984: error : qemuOpenFileAs:3175 : Failed to open file '/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J9BB442595': No such file or directory 2021-09-19 01:40:03.886+0000: 11983: error : qemuOpenFileAs:3175 : Failed to open file '/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J9BB442595': No such file or directory 2021-09-19 01:40:03.889+0000: 11982: error : qemuOpenFileAs:3175 : Failed to open file '/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J9BB442595': No such file or directory 2021-09-19 01:40:03.894+0000: 11983: error : qemuOpenFileAs:3175 : Failed to open file '/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J9BB442595': No such file or directory 2021-09-19 01:40:04.814+0000: 11980: error : virFileIsSharedFixFUSE:3384 : unable to canonicalize /mnt/user/domains/pfSenseVM/vdisk1.img: No such file or directory 2021-09-19 01:40:04.814+0000: 11980: error : qemuOpenFileAs:3175 : Failed to open file '/mnt/user/domains/pfSenseVM/vdisk1.img': No such file or directory 2021-09-19 01:40:05.605+0000: 11982: error : qemuOpenFileAs:3175 : Failed to open file '/dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J9BB442595': No such file or directory I only one one VM that I use. the rest are relics that are no longer working and I only keep there in case I'll need to get something from the VM image. Any ideas what's going on? should I just removed the old VMs from the manager? libvirtd.7z

I have / had a few dockers for image processing that had a large container (frigate for example is about 1.5gb~). so i just changed it to 100gb to be on the safe side. it's not filling up as far as i can tell. ttyACM1 should be one of the zigbee sticks. i'll check it out. thanks! any way to clean the logs without rebooting to see it the problem keeps happening?

Hi, I have 2 issues for a long while now that I keep ignoring, but I would like to get fixed before upgrading to 5.10. 1. the log file is getting full fast. My current uptime is 40 days, but it's getting full in a few days tops according to the report of "Fix Common Problems" plugin. diagnostics attached. 2. my second issue is more annoying - when SOME containers stop - they disappear form the "docker" tab. I get get them running again by adding a new container with the same config file and everything will work fine as long as they are operational. the issue mostly bother me after a server restart (the dockers are missing and will not start automatically) or when I get some issue after updating the docker container (more annoying, as the logs will be missing as well). I can see the issue easily with 2 of my dockers: a. "frigate" - using "my-frigate.xml" b. "deepstack_gpux" using "my-deepstack_gpux.xml" I might created those two configs manually or changed them from the base version, as I don't thing they were available via the community addon when I started using them. not sure as too much time passed. I've attached the docker files for those two as well. Any help will be appreciated tower-diagnostics-20211026-1921.zip my-frigate.xml my-deepstack_gpux.xml

Hi @mathgoy, I've been using Frigate with an NVIDIA GPU. to set it up, go the the docker template and add: --rm --runtime=nvidia to the "Extra Parameters". You will also need to add two new Variables: "NVIDIA_VISIBLE_DEVICES" and "NVIDIA_DRIVER_CAPABILITIES": After that you should be able to run "nvidia-smi" in the docker console: Note that you won't get anything under processes here even after you'll get the GPU decoding to work. After that you should adjust you're config to use the HW decoding. see here: https://blakeblackshear.github.io/frigate/configuration/nvdec Those are my changes: (all my cameras are 1080P h264) When you're done you should be able to see the GPU being used by running "nvidia-smi" from the Unraid console: I have 8 cameras, so 8 processes (and another one is Deepstack). Hope it helps.

Thanks for the reply, I've added a static route now on both configs - Some improvements, but I still having some issues. On the simple server - I can now connect to the Unraid UI and to the pfsense UI. but I still can't access anything else on the network. I've tried the firewall rules because of the firewall log: (first one 192.168.0.31:8123 is the source, the 10.253.0.2 is the destination) it looks like the remote device (the VPN peer) try to talk to the local service, but when the local service try to "take back" there's an issue. on the complex server, it's basically the same + but I can't access the main UI as it forward automatically to the local domain (unraid.privateFQDN.org) and it stops there. dockers on the unraid server (using the IP address) connect perfectly. Edit: Found the fix the the issue, not sure why my config is causing it - but the scenario here is Asymmetric Routing. The solution is to enable "Bypass firewall rules for traffic on the same interface" under System/Advanced/Firewall & NAT: That fix both of the issues described above.

Hi, Might be unrated - but maybe someone here can help. I've tried using this plugin on 2 different unraid servers located on 2 different networks. In both I get the same result - I can access the main unraid server, but nothing more (meaning, I can enter the IP on the unraid server and it works perfectly. nothing else in the network [such other servers] works). Both servers are behind dedicated pfsense firewalls. Both have the port forwarded as needed. I've tried the Advance setup on one (NAT to false, Docker Host access to custom networks "enabled" and firewall rule): Firewall rules I've tried, but seems to make no difference: And here is the second one, with the "basic" config: Port forwarding for both looks mostly the same: Any ideas? And thanks for the plugin! :)

Fantastic upgrade! I use to think that the 5 min startup for my VM's is a fact of life. now? it's up before I change the output in my monitor! Thanks a lot LimeTech team!

I'll try to exchange the "Interface Rules" in the Network Settings page so that eth0 will be realtek and eth1 is Intel. in a few hours and report back. Anyone have more ideas?

the Intel NIC is the build in one (in the MOBO) and is ETH0. maybe something else? it's only happened from the 6.4 -> 6.5 upgrade.

I guess so, one is Intel and the other is Realtek 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Diagnostics attached. tower-diagnostics-20180318-2203.zip

Hello again, I'm facing the original problem once again - eth1 is missing. the strange thing is that the network is connected, pinging network #2 from within the windows 10 VM works but from Unraid (the host) I get no ping. VM: C:\Users\Ido>ping 192.168.1.1 Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\Ido>ping 192.168.0.1 Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Reply from 192.168.0.1: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms UNRAID: root@Tower:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.337 ms ^C --- 192.168.1.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.337/0.337/0.337/0.000 ms root@Tower:~# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. ^C --- 192.168.0.1 ping statistics --- 28 packets transmitted, 0 received, 100% packet loss, time 27644ms here is some more info that might be helpful: root@Tower:~# lspci | egrep -i --color 'network|ethernet' 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V (rev 05) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) root@Tower:~# lshw -class network *-network description: Ethernet interface product: Ethernet Connection (2) I218-V vendor: Intel Corporation physical id: 19 bus info: pci@0000:00:19.0 logical name: eth0 version: 05 serial: 38:d5:47:23:80:64 size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k duplex=full firmware=0.1-4 latency=0 link=yes multicast=yes port=twisted pair promiscuous=yes speed=1Gbit/s resources: irq:46 memory:fb300000-fb31ffff memory:fb336000-fb336fff ioport:f000(size=32) *-network description: Ethernet controller product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:06:00.0 version: 06 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list configuration: driver=vfio-pci latency=0 resources: irq:19 ioport:c000(size=256) memory:d0004000-d0004fff memory:d0000000-d0003fff *-network:0 description: Ethernet interface physical id: 2 logical name: br0 serial: 38:d5:47:23:80:64 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=192.168.1.222 link=yes multicast=yes *-network:1 DISABLED description: Ethernet interface physical id: 3 logical name: virbr0-nic serial: 52:54:00:07:a8:97 size: 10Mbit/s capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=no multicast=yes port=twisted pair speed=10Mbit/s *-network:2 description: Ethernet interface physical id: 4 logical name: vnet1 serial: fe:54:00:36:e8:25 size: 10Mbit/s capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=yes multicast=yes port=twisted pair speed=10Mbit/s *-network:3 DISABLED description: Ethernet interface physical id: 5 logical name: gretap0 capabilities: ethernet physical configuration: broadcast=yes multicast=yes *-network:4 description: Ethernet interface physical id: 6 logical name: virbr0 serial: 52:54:00:07:a8:97 capabilities: ethernet physical configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A ip=192.168.122.1 link=no multicast=yes *-network:5 description: Ethernet interface physical id: 7 logical name: vnet0 serial: fe:54:00:e3:81:fa size: 10Mbit/s capabilities: ethernet physical configuration: autonegotiation=off broadcast=yes driver=tun driverversion=1.6 duplex=full link=yes multicast=yes port=twisted pair speed=10Mbit/s *-network:6 DISABLED description: Ethernet interface physical id: 8 logical name: erspan0 capabilities: ethernet physical configuration: broadcast=yes multicast=yes root@Tower:~# ifconfig -a br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.222 netmask 255.255.255.0 broadcast 0.0.0.0 inet6 fd4d:e7fb:46eb:0:3ad5:47ff:fe23:8064 prefixlen 64 scopeid 0x0<global> inet6 fe80::c06c:3cff:fefc:5156 prefixlen 64 scopeid 0x20<link> ether 38:d5:47:23:80:64 txqueuelen 1000 (Ethernet) RX packets 866448 bytes 187508409 (178.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 979578 bytes 1249128328 (1.1 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 erspan0: flags=4098<BROADCAST,MULTICAST> mtu 1450 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 inet6 fe80::3ad5:47ff:fe23:8064 prefixlen 64 scopeid 0x20<link> ether 38:d5:47:23:80:64 txqueuelen 1000 (Ethernet) RX packets 4893058 bytes 3662543084 (3.4 GiB) RX errors 0 dropped 83 overruns 0 frame 0 TX packets 3740252 bytes 1718171974 (1.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xfb300000-fb320000 gre0: flags=128<NOARP> mtu 1476 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 gretap0: flags=4098<BROADCAST,MULTICAST> mtu 1462 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ip_vti0: flags=128<NOARP> mtu 1364 tunnel txqueuelen 1000 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 443988 bytes 188297584 (179.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 443988 bytes 188297584 (179.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sit0: flags=128<NOARP> mtu 1480 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tunl0: flags=128<NOARP> mtu 1480 tunnel txqueuelen 1000 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255 ether 52:54:00:07:a8:97 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 52:54:00:07:a8:97 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::fc54:ff:fee3:81fa prefixlen 64 scopeid 0x20<link> ether fe:54:00:e3:81:fa txqueuelen 1000 (Ethernet) RX packets 843319 bytes 199018000 (189.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 751535 bytes 839056856 (800.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::fc54:ff:fe36:e825 prefixlen 64 scopeid 0x20<link> ether fe:54:00:36:e8:25 txqueuelen 1000 (Ethernet) RX packets 4313029 bytes 1900159552 (1.7 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5814744 bytes 4268662816 (3.9 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@Tower:~# ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1364 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 11: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff 12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff 13: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff 14: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff 15: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:e3:81:fa brd ff:ff:ff:ff:ff:ff 16: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:36:e8:25 brd ff:ff:ff:ff:ff:ff root@Tower:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1450 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1364 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 11: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff inet6 fe80::3ad5:47ff:fe23:8064/64 scope link valid_lft forever preferred_lft forever 12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 38:d5:47:23:80:64 brd ff:ff:ff:ff:ff:ff inet 192.168.1.222/24 scope global br0 valid_lft forever preferred_lft forever inet6 fd4d:e7fb:46eb:0:3ad5:47ff:fe23:8064/64 scope global dynamic mngtmpaddr valid_lft forever preferred_lft forever inet6 fe80::c06c:3cff:fefc:5156/64 scope link valid_lft forever preferred_lft forever 13: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 14: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:07:a8:97 brd ff:ff:ff:ff:ff:ff 15: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000 link/ether fe:54:00:e3:81:fa brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fee3:81fa/64 scope link valid_lft forever preferred_lft forever 16: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UNKNOWN group default qlen 1000 link/ether fe:54:00:36:e8:25 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc54:ff:fe36:e825/64 scope link valid_lft forever preferred_lft forever

Hello all, After upgrading from 6.4 to 6.5 I've had many issues (with the VM engine mostly) but I've managed to fix all of them. the only problem that I can't seem to fully fix is the network issue. my setup is - network #1 ISP A [192.168.1.1] - connected as eth0 and is the main connection. network #2 ISP B [192.168.0.1] - connected as eth1 and is the backup connection and used to serv the media stored in the server to a different part of the house. before the upgrade everything worked fine. after the upgrade I've lost eth1 completely (only br1 showed with link down). after reading the change log (many network related updates) I've guessed that cleaning the config might help. I've removed: network.cfg & network-rules.cfg and rebooted. that seem to make eth0 and eth1 work. after some basic config both network are seeing the server and have access to the web UI. the problem is with network #2 and Samba - it can't seem to access it. with network #1 everything works fine. I've attached the old and new config files for the network. Any ideas? network.cfg network.cfg.bu network-rules.cfg network-rules.cfg.bu

WIN10 + GTX1070. the sound is from the onboard card

What to you mean by non-VM core?

I'm having the same problem.. Any solutions to this issue? maybe an external usb sound card?

Hmmm, Option number 1 sound like a solid choice Thanks anyways!

Everything works perfectly as far as I can tell.

anyone?

Got this error. Logs are attached. I've found this: Aug 25 20:27:18 Tower kernel: ------------[ cut here ]------------ Aug 25 20:27:18 Tower kernel: WARNING: CPU: 0 PID: 10502 at arch/x86/kvm/vmx.c:4773 vmx_deliver_posted_interrupt+0xec/0x128 [kvm_intel] Aug 25 20:27:18 Tower kernel: Modules linked in: vhost_net tun vhost macvtap macvlan kvm_intel kvm md_mod xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables bonding e1000e ptp pps_core r8169 mii hid_logitech_hidpp mxm_wmi x86_pkg_temp_thermal coretemp i2c_i801 i2c_smbus ahci i2c_core hid_logitech_dj libahci wmi [last unloaded: md_mod] Aug 25 20:27:18 Tower kernel: CPU: 0 PID: 10502 Comm: CPU 0/KVM Not tainted 4.9.30-unRAID #1 Aug 25 20:27:18 Tower kernel: Hardware name: ASUS All Series/X99-A II, BIOS 0601 05/18/2016 Aug 25 20:27:18 Tower kernel: ffffc9000d0b7b60 ffffffff813a4a1b 0000000000000000 ffffffffa00ab568 Aug 25 20:27:18 Tower kernel: ffffc9000d0b7ba0 ffffffff8104d0d9 000012a50d0b7a00 ffff8807fe620000 Aug 25 20:27:18 Tower kernel: 000000000000000a ffffc9000d0b7c80 ffff8802083d8000 ffff8807fe620000 Aug 25 20:27:18 Tower kernel: Call Trace: Aug 25 20:27:18 Tower kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e Aug 25 20:27:18 Tower kernel: [<ffffffff8104d0d9>] __warn+0xb8/0xd3 Aug 25 20:27:18 Tower kernel: [<ffffffff8104d1a1>] warn_slowpath_null+0x18/0x1a Aug 25 20:27:18 Tower kernel: [<ffffffffa008e3ee>] vmx_deliver_posted_interrupt+0xec/0x128 [kvm_intel] Aug 25 20:27:18 Tower kernel: [<ffffffffa0064e81>] __apic_accept_irq+0x173/0x19b [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa00660bc>] kvm_apic_set_irq+0x25/0x27 [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa0069506>] kvm_irq_delivery_to_apic+0x129/0x20f [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa0065bff>] kvm_lapic_reg_write+0x336/0x492 [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa0065d9e>] kvm_apic_write_nodecode+0x43/0x49 [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa008bf82>] handle_apic_write+0x19/0x20 [kvm_intel] Aug 25 20:27:18 Tower kernel: [<ffffffffa0096055>] vmx_handle_exit+0xf9d/0x1035 [kvm_intel] Aug 25 20:27:18 Tower kernel: [<ffffffffa00528a9>] kvm_arch_vcpu_ioctl_run+0x357/0x1165 [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa008df4c>] ? __vmx_load_host_state.part.27+0x120/0x127 [kvm_intel] Aug 25 20:27:18 Tower kernel: [<ffffffffa004d088>] ? kvm_arch_vcpu_load+0xea/0x1a0 [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa0042d71>] kvm_vcpu_ioctl+0x178/0x499 [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffffa00452f5>] ? kvm_vm_ioctl+0x40a/0x6d2 [kvm] Aug 25 20:27:18 Tower kernel: [<ffffffff810bd85b>] ? __perf_event_task_sched_in+0xd0/0x135 Aug 25 20:27:18 Tower kernel: [<ffffffff81130112>] vfs_ioctl+0x13/0x2f Aug 25 20:27:18 Tower kernel: [<ffffffff81130642>] do_vfs_ioctl+0x49c/0x50a Aug 25 20:27:18 Tower kernel: [<ffffffff8113921f>] ? __fget+0x72/0x7e Aug 25 20:27:18 Tower kernel: [<ffffffff811306ee>] SyS_ioctl+0x3e/0x5c Aug 25 20:27:18 Tower kernel: [<ffffffff8167f537>] entry_SYSCALL_64_fastpath+0x1a/0xa9 Aug 25 20:27:18 Tower kernel: ---[ end trace 4bddda485d1bdd7b ]--- Any ideas? Thanks! tower-diagnostics-20170901-0040.zip

Finished running. Found only one issue. Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 30 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Checking Semantic tree: finished 1 found corruptions can be fixed when running with --fix-fixable ########### reiserfsck finished at Sat Aug 19 17:43:32 2017 ########### root@Tower:~# reiserfsck --fix-fixable /dev/md2 reiserfsck 3.6.24 Will check consistency of the filesystem on /dev/md2 and will fix what can be fixed without --rebuild-tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --fix-fixable started at Sat Aug 19 17:44:09 2017 ########### Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later. Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 64040 Internal nodes 388 Directories 43 Other files 348 Data block pointers 64706572 (257234 of them are zero) Safe links 0 ########### reiserfsck finished at Sat Aug 19 17:53:22 2017 ###########

Hi all, I'm having an issue with my unraid setup. Last week I've noticed that I can't write to the shares thru SMB - i've restarted the server and it's fixed the issue. Today I've faced the same issue again so i begun invastigating. Only Disk2 is having an issue, it's not an old drive and it's shown as OK in the dashboard. I've installed the fix common issues plugin and i see there: Unable to write to disk2 Drive mounted read-only or completely full. The disk is not full. Diagnostic data is here: https://www.dropbox.com/s/88meeqb7ddf0lrq/tower-diagnostics-20170818-2318.zip?dl=0 Any ideas?

I thought about doing it the other way around. first make sure that the unraid VM setup is able to give me the necessary solution for gaming. so again, is it needed to add another GPU for the use of UNRAID? or can it run without one (main [and only] GPU passthru)

Hey all, This seems to be related to the HW forum and the KVM forum, so i'll post in general. I've get myself a new system with unraid in mind. spec are: PCPartPicker part list / Price breakdown by merchant CPU: Intel Core i7-6850K 3.6GHz 6-Core Processor ($609.99 @ Amazon) CPU Cooler: Corsair H100i v2 70.7 CFM Liquid CPU Cooler ($104.20 @ Amazon) Motherboard: Asus X99-A II ATX LGA2011-3 Motherboard ($225.99 @ SuperBiiz) Memory: Crucial Ballistix Elite 32GB (4 x 8GB) DDR4-2666 Memory ($169.00 @ B&H) Storage: Samsung 850 Pro Series 512GB 2.5" Solid State Drive ($219.99 @ Amazon) Storage: Mushkin Reactor 1TB 2.5" Solid State Drive ($229.49 @ Amazon) Video Card: Asus GeForce GTX 1070 8GB Dual Series Video Card ($429.89 @ OutletPC) Case: Fractal Design Define R4 w/Window (Black Pearl) ATX Mid Tower Case ($109.99 @ SuperBiiz) Total: $2098.54 Prices include shipping, taxes, and discounts when available Generated by PCPartPicker 2016-09-22 02:26 EDT-0400 I would like to move my old unraid server (6 years old, core 2 duo) - now with unraid 5.1 - to the new server. for that i would move my 7 HDDs excluding the old cache drive. I would also like to install 2 VM on the server - one will be my main "PC" that will run WIN10 gameing machine (with the 1070 passthru) and another VM for old softwares (win7). do I need another GPU for that? any advice on how to accomplish that? thank you!

I use unraid already (on an old server). the idea here is to get a system that will stay as-is for a few good years. I thought that for the VM windows i should get the fastest drive to reduce the "lazyness" that I know we can get from normal HDs in VMs. I've also decided to swap the motherboard for one with more SATA ports: GIGABYTE GA-Z170X-UD5. maybe i'll get a different one. i need to decide on a configuration for the drives so i will not disable some of the ports (cuz of the M2 drive). Aswell as a USB3 PCIe card for easy attach and detach usb drives to the VM system: http://www.amazon.com/Anker%C2%AE-Express-Connector-Desktops-Chipset/dp/B005ARQV6U