sunbear

Hello, I have been trying every Unriad OS update since 6.10.3, and every single one of them has lasted about 12 hours with docker running, before several of my cores seem to lock up with 100% usage & I start having lockup issues with different docker apps. When I visit the unraid webGUI through browser, it is still usually responsive (if a little slow), until I visit the DOCKER gui page and the page hangs halfway through loading and the rest of the gui becomes unresponsive. At this point, I can usually still access the terminal, although no docker commands work and no apps are responsive (nor can I kill them through docker daemon). The only thing I am left with is a hard reboot and the entire process starts again 12-24 hours later. Would love some help figuring out what the issue is. Like I said, I'm currently on 6.10.3 which works fine, I've tried every update since and I always end up having to revert back to 6.10.3. I have attached my latest diagnostics after reverting but I'm not sure how long these go back. I know my latest lock-up was when I just recently tried updating to 6.11.5 and believe it locked up around 2022-11-20 ~07:00AM. Edit: I'm guessing my logs don't back far enough to show what's happening. Do I need to try to update again to try to get logs of my system hanging? I really don't like having to keep hard resetting.

Yes.

I get the following error at the bottom of my dashboard whenever docker is turned off. Is this normal? Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [2] No such file or directory

Ahh, okay. Well at least it's doing something. Okay, so there's not specific a setting for unassiged disk spin down? In an unrelated note, I'm getting what seems like crazy read counts for one of my unassiged devices being passthrough to a VM. Does this seem abnormal to you? Over a day or so, It's collected 18,446,744,073,709,551,616 reads as compared to the ~1,641,683,107 or so for my array drives. Meanwhile, it has only 2 writes?

I get these notification every hour (my smart poll time) in my logs. Sep 4 11:01:03 SERV-X370 emhttpd: spinning down /dev/sdb Sep 4 11:07:21 SERV-X370 emhttpd: spinning down /dev/sda Sep 4 11:07:22 SERV-X370 emhttpd: read SMART /dev/sda Both of these drives are SSDs that do not spin up. Is there anyway I can turn spin up/spin down delay or even the smart polling time for Unassigned device SSDs? These settings exist for regular array devices but not for Unassiged Devices as far as I can tell.

I've had this issue happen twice in two days now. Something with docker is hanging and I can't get the gui back without a reboot through ssh terminal.

Ok, I'm pretty confident it's not the cable but the plug on this drive (I've had issues with it before). I've cleaned and re-seated the plug. I'm starting the system back up and was going to run a filesystem check for that drive if that's possible for a disabled drive. Do y'all have any recommendations for testing this drive to make sure I've got a good connection?

Uggh. I've had so many damn cable/connection issues. Thanks. I will try swapping around once I can get everything shutdown. Just FYI, I've attached the latest SMART report for the drive that was having issues. This was after recent repeating read errors but prior to it going offline today. WDC_WD60EFRX-68L0BN1_WD-WX21D583NR7P-20220824-1237[1].txt

Possibly related: I have also been having some issues with an SSD passed-through to a VM which I am pretty sure is a bad drive that I plan on replacing. Is it possible for potential corruption issues with that drive somehow spilling over to my array drives? I did notice that my file integrity scans found some corruptions on the bad array disk around the same time as the errors (see system log diagnostics). These aren't totally unusual though, I get them every once in a while on certain files being shared w/ multiple dockers/smb.

About every other day for about a week now, I have been getting a handful of read errors on one drive that correct themselves. I've run several short smart tests and one extended smart test with no errors. Then today something finally bit the dust, I ended up with 3974 errors (both read & write) some errors like "blk_update_request: I/O error, op 0x1:(WRITE) flags 0x4000 prio class 0" and "Synchronize Cache(10) failed" and the drive gets disabled. This drive is actually one of my newer ones and unfortunately also my good CMR 6GB drive (instead of my screwed-over-by-WD secretly-SMR 6GB drive) so I'm hoping I don't have to replace it. Would someone smarter than me mind taking a look at my diagnostics and let me know if I just need to replace the drive? Is there anything I can do besides more smart tests to see what the issue is? Should I do a preclear? Diagnostics attached. Thanks. serv-x370-diagnostics-20220829-1135.zip

I have no idea how the docker networking stuff works but it seems to be filling up my logs. Can anyone tell me what's going on here? ug 21 21:20:30 SERV-X370 kernel: br-1765d9199c3f: port 3(vethd757812) entered disabled state Aug 21 21:20:30 SERV-X370 kernel: vethc13a47d: renamed from eth0 Aug 21 21:20:31 SERV-X370 kernel: br-1765d9199c3f: port 3(vethd757812) entered disabled state Aug 21 21:20:31 SERV-X370 kernel: device vethd757812 left promiscuous mode Aug 21 21:20:31 SERV-X370 kernel: br-1765d9199c3f: port 3(vethd757812) entered disabled state Aug 21 21:20:31 SERV-X370 kernel: br-1765d9199c3f: port 3(veth13ef075) entered blocking state Aug 21 21:20:31 SERV-X370 kernel: br-1765d9199c3f: port 3(veth13ef075) entered disabled state Aug 21 21:20:31 SERV-X370 kernel: device veth13ef075 entered promiscuous mode Aug 21 21:20:31 SERV-X370 kernel: br-1765d9199c3f: port 3(veth13ef075) entered blocking state Aug 21 21:20:31 SERV-X370 kernel: br-1765d9199c3f: port 3(veth13ef075) entered forwarding state Aug 21 21:20:31 SERV-X370 kernel: eth0: renamed from veth21635b3 Aug 21 21:20:31 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth13ef075: link becomes ready Aug 21 21:29:57 SERV-X370 kernel: br-1765d9199c3f: port 3(veth13ef075) entered disabled state Aug 21 21:29:57 SERV-X370 kernel: veth21635b3: renamed from eth0 Aug 21 21:29:57 SERV-X370 kernel: br-1765d9199c3f: port 3(veth13ef075) entered disabled state Aug 21 21:29:57 SERV-X370 kernel: device veth13ef075 left promiscuous mode Aug 21 21:29:57 SERV-X370 kernel: br-1765d9199c3f: port 3(veth13ef075) entered disabled state Aug 21 21:29:57 SERV-X370 kernel: br-1765d9199c3f: port 3(veth41ee04e) entered blocking state Aug 21 21:29:57 SERV-X370 kernel: br-1765d9199c3f: port 3(veth41ee04e) entered disabled state Aug 21 21:29:57 SERV-X370 kernel: device veth41ee04e entered promiscuous mode Aug 21 21:29:57 SERV-X370 kernel: br-1765d9199c3f: port 3(veth41ee04e) entered blocking state Aug 21 21:29:57 SERV-X370 kernel: br-1765d9199c3f: port 3(veth41ee04e) entered forwarding state Aug 21 21:29:57 SERV-X370 kernel: eth0: renamed from veth7544713 Aug 21 21:29:57 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth41ee04e: link becomes ready Aug 21 21:30:29 SERV-X370 emhttpd: spinning down /dev/sda Aug 21 21:30:32 SERV-X370 emhttpd: read SMART /dev/sda Aug 21 21:40:19 SERV-X370 kernel: vethc9bcd80: renamed from eth0 Aug 21 21:40:19 SERV-X370 kernel: br-1765d9199c3f: port 1(veth962f53d) entered disabled state Aug 21 21:40:19 SERV-X370 kernel: br-1765d9199c3f: port 1(veth962f53d) entered disabled state Aug 21 21:40:19 SERV-X370 kernel: device veth962f53d left promiscuous mode Aug 21 21:40:19 SERV-X370 kernel: br-1765d9199c3f: port 1(veth962f53d) entered disabled state Aug 21 21:40:20 SERV-X370 kernel: br-1765d9199c3f: port 1(veth06b5e0e) entered blocking state Aug 21 21:40:20 SERV-X370 kernel: br-1765d9199c3f: port 1(veth06b5e0e) entered disabled state Aug 21 21:40:20 SERV-X370 kernel: device veth06b5e0e entered promiscuous mode Aug 21 21:40:20 SERV-X370 kernel: br-1765d9199c3f: port 1(veth06b5e0e) entered blocking state Aug 21 21:40:20 SERV-X370 kernel: br-1765d9199c3f: port 1(veth06b5e0e) entered forwarding state Aug 21 21:40:20 SERV-X370 kernel: eth0: renamed from vethce5d689 Aug 21 21:40:20 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth06b5e0e: link becomes ready Aug 21 21:41:05 SERV-X370 kernel: veth7544713: renamed from eth0 Aug 21 21:41:05 SERV-X370 kernel: br-1765d9199c3f: port 3(veth41ee04e) entered disabled state Aug 21 21:41:05 SERV-X370 kernel: br-1765d9199c3f: port 3(veth41ee04e) entered disabled state Aug 21 21:41:05 SERV-X370 kernel: device veth41ee04e left promiscuous mode Aug 21 21:41:05 SERV-X370 kernel: br-1765d9199c3f: port 3(veth41ee04e) entered disabled state Aug 21 21:41:25 SERV-X370 emhttpd: spinning down /dev/sdb Aug 21 22:03:12 SERV-X370 kernel: br-1765d9199c3f: port 3(vethefc623e) entered blocking state Aug 21 22:03:12 SERV-X370 kernel: br-1765d9199c3f: port 3(vethefc623e) entered disabled state Aug 21 22:03:12 SERV-X370 kernel: device vethefc623e entered promiscuous mode Aug 21 22:03:12 SERV-X370 kernel: br-1765d9199c3f: port 3(vethefc623e) entered blocking state Aug 21 22:03:12 SERV-X370 kernel: br-1765d9199c3f: port 3(vethefc623e) entered forwarding state Aug 21 22:03:12 SERV-X370 kernel: br-1765d9199c3f: port 3(vethefc623e) entered disabled state Aug 21 22:03:12 SERV-X370 kernel: eth0: renamed from veth01c0c6a Aug 21 22:03:12 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethefc623e: link becomes ready Aug 21 22:03:12 SERV-X370 kernel: br-1765d9199c3f: port 3(vethefc623e) entered blocking state Aug 21 22:03:12 SERV-X370 kernel: br-1765d9199c3f: port 3(vethefc623e) entered forwarding state Aug 21 22:07:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf76c6d9) entered disabled state Aug 21 22:07:19 SERV-X370 kernel: vethb708293: renamed from eth0 Aug 21 22:07:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf76c6d9) entered disabled state Aug 21 22:07:19 SERV-X370 kernel: device vethf76c6d9 left promiscuous mode Aug 21 22:07:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf76c6d9) entered disabled state Aug 21 22:11:03 SERV-X370 kernel: br-1765d9199c3f: port 2(vetha87c9f4) entered blocking state Aug 21 22:11:03 SERV-X370 kernel: br-1765d9199c3f: port 2(vetha87c9f4) entered disabled state Aug 21 22:11:03 SERV-X370 kernel: device vetha87c9f4 entered promiscuous mode Aug 21 22:11:03 SERV-X370 kernel: eth0: renamed from veth9c47bdb Aug 21 22:11:03 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha87c9f4: link becomes ready Aug 21 22:11:03 SERV-X370 kernel: br-1765d9199c3f: port 2(vetha87c9f4) entered blocking state Aug 21 22:11:03 SERV-X370 kernel: br-1765d9199c3f: port 2(vetha87c9f4) entered forwarding state Aug 21 22:11:03 SERV-X370 kernel: br-1765d9199c3f: port 2(vetha87c9f4) entered disabled state Aug 21 22:11:03 SERV-X370 kernel: veth9c47bdb: renamed from eth0 Aug 21 22:11:03 SERV-X370 kernel: br-1765d9199c3f: port 2(vetha87c9f4) entered disabled state Aug 21 22:11:03 SERV-X370 kernel: device vetha87c9f4 left promiscuous mode Aug 21 22:11:03 SERV-X370 kernel: br-1765d9199c3f: port 2(vetha87c9f4) entered disabled state Aug 21 22:11:05 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1caee3c) entered blocking state Aug 21 22:11:05 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1caee3c) entered disabled state Aug 21 22:11:05 SERV-X370 kernel: device veth1caee3c entered promiscuous mode Aug 21 22:11:05 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1caee3c) entered blocking state Aug 21 22:11:05 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1caee3c) entered forwarding state Aug 21 22:11:05 SERV-X370 kernel: eth0: renamed from vetha4f92f6 Aug 21 22:11:05 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1caee3c: link becomes ready Aug 21 22:11:05 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1caee3c) entered disabled state Aug 21 22:11:05 SERV-X370 kernel: vetha4f92f6: renamed from eth0 Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1caee3c) entered disabled state Aug 21 22:11:06 SERV-X370 kernel: device veth1caee3c left promiscuous mode Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1caee3c) entered disabled state Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(vethbbe4c1f) entered blocking state Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(vethbbe4c1f) entered disabled state Aug 21 22:11:06 SERV-X370 kernel: device vethbbe4c1f entered promiscuous mode Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(vethbbe4c1f) entered blocking state Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(vethbbe4c1f) entered forwarding state Aug 21 22:11:06 SERV-X370 kernel: eth0: renamed from veth67c349b Aug 21 22:11:06 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbbe4c1f: link becomes ready Aug 21 22:11:06 SERV-X370 kernel: veth67c349b: renamed from eth0 Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(vethbbe4c1f) entered disabled state Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(vethbbe4c1f) entered disabled state Aug 21 22:11:06 SERV-X370 kernel: device vethbbe4c1f left promiscuous mode Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(vethbbe4c1f) entered disabled state Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(veth3494bdd) entered blocking state Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(veth3494bdd) entered disabled state Aug 21 22:11:06 SERV-X370 kernel: device veth3494bdd entered promiscuous mode Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(veth3494bdd) entered blocking state Aug 21 22:11:06 SERV-X370 kernel: br-1765d9199c3f: port 2(veth3494bdd) entered forwarding state Aug 21 22:11:07 SERV-X370 kernel: eth0: renamed from vethe9b5270 Aug 21 22:11:07 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3494bdd: link becomes ready Aug 21 22:11:07 SERV-X370 kernel: vethe9b5270: renamed from eth0 Aug 21 22:11:07 SERV-X370 kernel: br-1765d9199c3f: port 2(veth3494bdd) entered disabled state Aug 21 22:11:07 SERV-X370 kernel: br-1765d9199c3f: port 2(veth3494bdd) entered disabled state Aug 21 22:11:07 SERV-X370 kernel: device veth3494bdd left promiscuous mode Aug 21 22:11:07 SERV-X370 kernel: br-1765d9199c3f: port 2(veth3494bdd) entered disabled state Aug 21 22:11:08 SERV-X370 kernel: br-1765d9199c3f: port 2(veth4b2d23b) entered blocking state Aug 21 22:11:08 SERV-X370 kernel: br-1765d9199c3f: port 2(veth4b2d23b) entered disabled state Aug 21 22:11:08 SERV-X370 kernel: device veth4b2d23b entered promiscuous mode Aug 21 22:11:08 SERV-X370 kernel: br-1765d9199c3f: port 2(veth4b2d23b) entered blocking state Aug 21 22:11:08 SERV-X370 kernel: br-1765d9199c3f: port 2(veth4b2d23b) entered forwarding state Aug 21 22:11:08 SERV-X370 kernel: eth0: renamed from veth60ad635 Aug 21 22:11:08 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4b2d23b: link becomes ready Aug 21 22:11:08 SERV-X370 kernel: br-1765d9199c3f: port 2(veth4b2d23b) entered disabled state Aug 21 22:11:08 SERV-X370 kernel: veth60ad635: renamed from eth0 Aug 21 22:11:08 SERV-X370 kernel: br-1765d9199c3f: port 2(veth4b2d23b) entered disabled state Aug 21 22:11:08 SERV-X370 kernel: device veth4b2d23b left promiscuous mode Aug 21 22:11:08 SERV-X370 kernel: br-1765d9199c3f: port 2(veth4b2d23b) entered disabled state Aug 21 22:11:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth6d9ce90) entered blocking state Aug 21 22:11:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth6d9ce90) entered disabled state Aug 21 22:11:10 SERV-X370 kernel: device veth6d9ce90 entered promiscuous mode Aug 21 22:11:10 SERV-X370 kernel: eth0: renamed from vethd591442 Aug 21 22:11:10 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6d9ce90: link becomes ready Aug 21 22:11:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth6d9ce90) entered blocking state Aug 21 22:11:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth6d9ce90) entered forwarding state Aug 21 22:11:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth6d9ce90) entered disabled state Aug 21 22:11:10 SERV-X370 kernel: vethd591442: renamed from eth0 Aug 21 22:11:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth6d9ce90) entered disabled state Aug 21 22:11:10 SERV-X370 kernel: device veth6d9ce90 left promiscuous mode Aug 21 22:11:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth6d9ce90) entered disabled state Aug 21 22:11:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth20c69ef) entered blocking state Aug 21 22:11:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth20c69ef) entered disabled state Aug 21 22:11:13 SERV-X370 kernel: device veth20c69ef entered promiscuous mode Aug 21 22:11:14 SERV-X370 kernel: eth0: renamed from vethee81ac2 Aug 21 22:11:14 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth20c69ef: link becomes ready Aug 21 22:11:14 SERV-X370 kernel: br-1765d9199c3f: port 2(veth20c69ef) entered blocking state Aug 21 22:11:14 SERV-X370 kernel: br-1765d9199c3f: port 2(veth20c69ef) entered forwarding state Aug 21 22:11:14 SERV-X370 kernel: br-1765d9199c3f: port 2(veth20c69ef) entered disabled state Aug 21 22:11:14 SERV-X370 kernel: vethee81ac2: renamed from eth0 Aug 21 22:11:14 SERV-X370 kernel: br-1765d9199c3f: port 2(veth20c69ef) entered disabled state Aug 21 22:11:14 SERV-X370 kernel: device veth20c69ef left promiscuous mode Aug 21 22:11:14 SERV-X370 kernel: br-1765d9199c3f: port 2(veth20c69ef) entered disabled state Aug 21 22:12:41 SERV-X370 kernel: br-1765d9199c3f: port 2(vethac6b02a) entered blocking state Aug 21 22:12:41 SERV-X370 kernel: br-1765d9199c3f: port 2(vethac6b02a) entered disabled state Aug 21 22:12:41 SERV-X370 kernel: device vethac6b02a entered promiscuous mode Aug 21 22:12:42 SERV-X370 kernel: eth0: renamed from veth7c5bc89 Aug 21 22:12:43 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethac6b02a: link becomes ready Aug 21 22:12:43 SERV-X370 kernel: br-1765d9199c3f: port 2(vethac6b02a) entered blocking state Aug 21 22:12:43 SERV-X370 kernel: br-1765d9199c3f: port 2(vethac6b02a) entered forwarding state Aug 21 22:18:19 SERV-X370 kernel: veth7c5bc89: renamed from eth0 Aug 21 22:18:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethac6b02a) entered disabled state Aug 21 22:18:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethac6b02a) entered disabled state Aug 21 22:18:19 SERV-X370 kernel: device vethac6b02a left promiscuous mode Aug 21 22:18:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethac6b02a) entered disabled state Aug 21 22:18:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf46fb64) entered blocking state Aug 21 22:18:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf46fb64) entered disabled state Aug 21 22:18:19 SERV-X370 kernel: device vethf46fb64 entered promiscuous mode Aug 21 22:18:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf46fb64) entered blocking state Aug 21 22:18:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf46fb64) entered forwarding state Aug 21 22:18:20 SERV-X370 kernel: eth0: renamed from veth5a60b45 Aug 21 22:18:20 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf46fb64: link becomes ready Aug 21 22:22:07 SERV-X370 kernel: br-1765d9199c3f: port 4(veth500f42c) entered disabled state Aug 21 22:22:07 SERV-X370 kernel: veth75a8372: renamed from eth0 Aug 21 22:22:07 SERV-X370 kernel: br-1765d9199c3f: port 4(veth500f42c) entered disabled state Aug 21 22:22:07 SERV-X370 kernel: device veth500f42c left promiscuous mode Aug 21 22:22:07 SERV-X370 kernel: br-1765d9199c3f: port 4(veth500f42c) entered disabled state Aug 21 22:22:07 SERV-X370 kernel: br-1765d9199c3f: port 4(vethd62741b) entered blocking state Aug 21 22:22:07 SERV-X370 kernel: br-1765d9199c3f: port 4(vethd62741b) entered disabled state Aug 21 22:22:07 SERV-X370 kernel: device vethd62741b entered promiscuous mode Aug 21 22:22:07 SERV-X370 kernel: br-1765d9199c3f: port 4(vethd62741b) entered blocking state Aug 21 22:22:07 SERV-X370 kernel: br-1765d9199c3f: port 4(vethd62741b) entered forwarding state Aug 21 22:22:07 SERV-X370 kernel: eth0: renamed from veth148fb9a Aug 21 22:22:07 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd62741b: link becomes ready Aug 21 22:29:10 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf46fb64) entered disabled state Aug 21 22:29:10 SERV-X370 kernel: veth5a60b45: renamed from eth0 Aug 21 22:29:10 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf46fb64) entered disabled state Aug 21 22:29:10 SERV-X370 kernel: device vethf46fb64 left promiscuous mode Aug 21 22:29:10 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf46fb64) entered disabled state Aug 21 22:29:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth57214eb) entered blocking state Aug 21 22:29:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth57214eb) entered disabled state Aug 21 22:29:10 SERV-X370 kernel: device veth57214eb entered promiscuous mode Aug 21 22:29:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth57214eb) entered blocking state Aug 21 22:29:10 SERV-X370 kernel: br-1765d9199c3f: port 2(veth57214eb) entered forwarding state Aug 21 22:29:10 SERV-X370 kernel: eth0: renamed from veth4f80d47 Aug 21 22:29:10 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth57214eb: link becomes ready Aug 21 22:30:33 SERV-X370 emhttpd: spinning down /dev/sda Aug 21 22:30:35 SERV-X370 emhttpd: read SMART /dev/sda Aug 21 22:38:35 SERV-X370 kernel: br-1765d9199c3f: port 1(veth06b5e0e) entered disabled state Aug 21 22:38:35 SERV-X370 kernel: vethce5d689: renamed from eth0 Aug 21 22:38:35 SERV-X370 kernel: br-1765d9199c3f: port 1(veth06b5e0e) entered disabled state Aug 21 22:38:35 SERV-X370 kernel: device veth06b5e0e left promiscuous mode Aug 21 22:38:35 SERV-X370 kernel: br-1765d9199c3f: port 1(veth06b5e0e) entered disabled state Aug 21 22:38:35 SERV-X370 kernel: br-1765d9199c3f: port 1(vethf95d07f) entered blocking state Aug 21 22:38:35 SERV-X370 kernel: br-1765d9199c3f: port 1(vethf95d07f) entered disabled state Aug 21 22:38:35 SERV-X370 kernel: device vethf95d07f entered promiscuous mode Aug 21 22:38:35 SERV-X370 kernel: br-1765d9199c3f: port 1(vethf95d07f) entered blocking state Aug 21 22:38:35 SERV-X370 kernel: br-1765d9199c3f: port 1(vethf95d07f) entered forwarding state Aug 21 22:38:36 SERV-X370 kernel: eth0: renamed from veth2e28fd6 Aug 21 22:38:36 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf95d07f: link becomes ready Aug 21 22:41:26 SERV-X370 emhttpd: spinning down /dev/sdb Aug 21 22:43:44 SERV-X370 kernel: br-1765d9199c3f: port 1(vethf95d07f) entered disabled state Aug 21 22:43:44 SERV-X370 kernel: veth2e28fd6: renamed from eth0 Aug 21 22:43:44 SERV-X370 kernel: br-1765d9199c3f: port 1(vethf95d07f) entered disabled state Aug 21 22:43:44 SERV-X370 kernel: device vethf95d07f left promiscuous mode Aug 21 22:43:44 SERV-X370 kernel: br-1765d9199c3f: port 1(vethf95d07f) entered disabled state Aug 21 22:43:45 SERV-X370 kernel: br-1765d9199c3f: port 1(veth1594204) entered blocking state Aug 21 22:43:45 SERV-X370 kernel: br-1765d9199c3f: port 1(veth1594204) entered disabled state Aug 21 22:43:45 SERV-X370 kernel: device veth1594204 entered promiscuous mode Aug 21 22:43:45 SERV-X370 kernel: br-1765d9199c3f: port 1(veth1594204) entered blocking state Aug 21 22:43:45 SERV-X370 kernel: br-1765d9199c3f: port 1(veth1594204) entered forwarding state Aug 21 22:43:45 SERV-X370 kernel: eth0: renamed from vethb4fe4a0 Aug 21 22:43:45 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1594204: link becomes ready Aug 21 22:44:17 SERV-X370 kernel: veth148fb9a: renamed from eth0 Aug 21 22:44:17 SERV-X370 kernel: br-1765d9199c3f: port 4(vethd62741b) entered disabled state Aug 21 22:44:17 SERV-X370 kernel: br-1765d9199c3f: port 4(vethd62741b) entered disabled state Aug 21 22:44:17 SERV-X370 kernel: device vethd62741b left promiscuous mode Aug 21 22:44:17 SERV-X370 kernel: br-1765d9199c3f: port 4(vethd62741b) entered disabled state Aug 21 22:44:17 SERV-X370 kernel: br-1765d9199c3f: port 4(vethfb7dd33) entered blocking state Aug 21 22:44:17 SERV-X370 kernel: br-1765d9199c3f: port 4(vethfb7dd33) entered disabled state Aug 21 22:44:17 SERV-X370 kernel: device vethfb7dd33 entered promiscuous mode Aug 21 22:44:17 SERV-X370 kernel: br-1765d9199c3f: port 4(vethfb7dd33) entered blocking state Aug 21 22:44:17 SERV-X370 kernel: br-1765d9199c3f: port 4(vethfb7dd33) entered forwarding state Aug 21 22:44:18 SERV-X370 kernel: eth0: renamed from veth4d214fd Aug 21 22:44:18 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfb7dd33: link becomes ready Aug 21 22:58:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth57214eb) entered disabled state Aug 21 22:58:13 SERV-X370 kernel: veth4f80d47: renamed from eth0 Aug 21 22:58:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth57214eb) entered disabled state Aug 21 22:58:13 SERV-X370 kernel: device veth57214eb left promiscuous mode Aug 21 22:58:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth57214eb) entered disabled state Aug 21 22:58:14 SERV-X370 kernel: br-1765d9199c3f: port 2(vethe9fd87c) entered blocking state Aug 21 22:58:14 SERV-X370 kernel: br-1765d9199c3f: port 2(vethe9fd87c) entered disabled state Aug 21 22:58:14 SERV-X370 kernel: device vethe9fd87c entered promiscuous mode Aug 21 22:58:14 SERV-X370 kernel: br-1765d9199c3f: port 2(vethe9fd87c) entered blocking state Aug 21 22:58:14 SERV-X370 kernel: br-1765d9199c3f: port 2(vethe9fd87c) entered forwarding state Aug 21 22:58:14 SERV-X370 kernel: eth0: renamed from veth7181e82 Aug 21 22:58:14 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe9fd87c: link becomes ready Aug 21 22:58:16 SERV-X370 kernel: veth7181e82: renamed from eth0 Aug 21 22:58:16 SERV-X370 kernel: br-1765d9199c3f: port 2(vethe9fd87c) entered disabled state Aug 21 22:58:16 SERV-X370 kernel: br-1765d9199c3f: port 2(vethe9fd87c) entered disabled state Aug 21 22:58:16 SERV-X370 kernel: device vethe9fd87c left promiscuous mode Aug 21 22:58:16 SERV-X370 kernel: br-1765d9199c3f: port 2(vethe9fd87c) entered disabled state Aug 21 22:58:16 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf0bc706) entered blocking state Aug 21 22:58:16 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf0bc706) entered disabled state Aug 21 22:58:16 SERV-X370 kernel: device vethf0bc706 entered promiscuous mode Aug 21 22:58:16 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf0bc706) entered blocking state Aug 21 22:58:16 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf0bc706) entered forwarding state Aug 21 22:58:17 SERV-X370 kernel: eth0: renamed from vethbe6fef6 Aug 21 22:58:17 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf0bc706: link becomes ready Aug 21 22:58:19 SERV-X370 kernel: vethbe6fef6: renamed from eth0 Aug 21 22:58:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf0bc706) entered disabled state Aug 21 22:58:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf0bc706) entered disabled state Aug 21 22:58:19 SERV-X370 kernel: device vethf0bc706 left promiscuous mode Aug 21 22:58:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethf0bc706) entered disabled state Aug 21 22:58:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethd2f8588) entered blocking state Aug 21 22:58:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethd2f8588) entered disabled state Aug 21 22:58:19 SERV-X370 kernel: device vethd2f8588 entered promiscuous mode Aug 21 22:58:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethd2f8588) entered blocking state Aug 21 22:58:19 SERV-X370 kernel: br-1765d9199c3f: port 2(vethd2f8588) entered forwarding state Aug 21 22:58:20 SERV-X370 kernel: eth0: renamed from veth3a21eac Aug 21 22:58:20 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd2f8588: link becomes ready Aug 21 22:58:22 SERV-X370 kernel: br-1765d9199c3f: port 2(vethd2f8588) entered disabled state Aug 21 22:58:22 SERV-X370 kernel: veth3a21eac: renamed from eth0 Aug 21 22:58:22 SERV-X370 kernel: br-1765d9199c3f: port 2(vethd2f8588) entered disabled state Aug 21 22:58:22 SERV-X370 kernel: device vethd2f8588 left promiscuous mode Aug 21 22:58:22 SERV-X370 kernel: br-1765d9199c3f: port 2(vethd2f8588) entered disabled state Aug 21 22:58:23 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1506aaf) entered blocking state Aug 21 22:58:23 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1506aaf) entered disabled state Aug 21 22:58:23 SERV-X370 kernel: device veth1506aaf entered promiscuous mode Aug 21 22:58:23 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1506aaf) entered blocking state Aug 21 22:58:23 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1506aaf) entered forwarding state Aug 21 22:58:23 SERV-X370 kernel: eth0: renamed from vethf14caa4 Aug 21 22:58:23 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1506aaf: link becomes ready Aug 21 22:58:24 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1506aaf) entered disabled state Aug 21 22:58:24 SERV-X370 kernel: vethf14caa4: renamed from eth0 Aug 21 22:58:24 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1506aaf) entered disabled state Aug 21 22:58:24 SERV-X370 kernel: device veth1506aaf left promiscuous mode Aug 21 22:58:24 SERV-X370 kernel: br-1765d9199c3f: port 2(veth1506aaf) entered disabled state Aug 21 22:58:25 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered blocking state Aug 21 22:58:25 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered disabled state Aug 21 22:58:25 SERV-X370 kernel: device vethb09f32c entered promiscuous mode Aug 21 22:58:25 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered blocking state Aug 21 22:58:25 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered forwarding state Aug 21 22:58:26 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered disabled state Aug 21 22:58:26 SERV-X370 kernel: eth0: renamed from vetha5fe0e5 Aug 21 22:58:26 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb09f32c: link becomes ready Aug 21 22:58:26 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered blocking state Aug 21 22:58:26 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered forwarding state Aug 21 22:58:37 SERV-X370 kernel: vetha5fe0e5: renamed from eth0 Aug 21 22:58:37 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered disabled state Aug 21 22:58:37 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered disabled state Aug 21 22:58:37 SERV-X370 kernel: device vethb09f32c left promiscuous mode Aug 21 22:58:37 SERV-X370 kernel: br-1765d9199c3f: port 2(vethb09f32c) entered disabled state Aug 21 22:58:37 SERV-X370 kernel: br-1765d9199c3f: port 2(veth795792e) entered blocking state Aug 21 22:58:37 SERV-X370 kernel: br-1765d9199c3f: port 2(veth795792e) entered disabled state Aug 21 22:58:37 SERV-X370 kernel: device veth795792e entered promiscuous mode Aug 21 22:58:37 SERV-X370 kernel: br-1765d9199c3f: port 2(veth795792e) entered blocking state Aug 21 22:58:37 SERV-X370 kernel: br-1765d9199c3f: port 2(veth795792e) entered forwarding state Aug 21 22:58:37 SERV-X370 kernel: eth0: renamed from vethd81909c Aug 21 22:58:37 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth795792e: link becomes ready Aug 21 22:58:40 SERV-X370 kernel: vethd81909c: renamed from eth0 Aug 21 22:58:40 SERV-X370 kernel: br-1765d9199c3f: port 2(veth795792e) entered disabled state Aug 21 22:58:40 SERV-X370 kernel: br-1765d9199c3f: port 2(veth795792e) entered disabled state Aug 21 22:58:40 SERV-X370 kernel: device veth795792e left promiscuous mode Aug 21 22:58:40 SERV-X370 kernel: br-1765d9199c3f: port 2(veth795792e) entered disabled state Aug 21 22:58:40 SERV-X370 kernel: br-1765d9199c3f: port 2(veth69a7817) entered blocking state Aug 21 22:58:40 SERV-X370 kernel: br-1765d9199c3f: port 2(veth69a7817) entered disabled state Aug 21 22:58:40 SERV-X370 kernel: device veth69a7817 entered promiscuous mode Aug 21 22:58:40 SERV-X370 kernel: br-1765d9199c3f: port 2(veth69a7817) entered blocking state Aug 21 22:58:40 SERV-X370 kernel: br-1765d9199c3f: port 2(veth69a7817) entered forwarding state Aug 21 22:58:41 SERV-X370 kernel: eth0: renamed from vethe1c1808 Aug 21 22:58:41 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth69a7817: link becomes ready Aug 21 22:58:41 SERV-X370 kernel: br-1765d9199c3f: port 2(veth69a7817) entered disabled state Aug 21 22:58:41 SERV-X370 kernel: vethe1c1808: renamed from eth0 Aug 21 22:58:41 SERV-X370 kernel: br-1765d9199c3f: port 2(veth69a7817) entered disabled state Aug 21 22:58:41 SERV-X370 kernel: device veth69a7817 left promiscuous mode Aug 21 22:58:41 SERV-X370 kernel: br-1765d9199c3f: port 2(veth69a7817) entered disabled state Aug 21 23:00:05 SERV-X370 kernel: vethb4fe4a0: renamed from eth0 Aug 21 23:00:05 SERV-X370 kernel: br-1765d9199c3f: port 1(veth1594204) entered disabled state Aug 21 23:00:05 SERV-X370 kernel: br-1765d9199c3f: port 1(veth1594204) entered disabled state Aug 21 23:00:05 SERV-X370 kernel: device veth1594204 left promiscuous mode Aug 21 23:00:05 SERV-X370 kernel: br-1765d9199c3f: port 1(veth1594204) entered disabled state Aug 21 23:00:06 SERV-X370 kernel: br-1765d9199c3f: port 1(veth962e4a8) entered blocking state Aug 21 23:00:06 SERV-X370 kernel: br-1765d9199c3f: port 1(veth962e4a8) entered disabled state Aug 21 23:00:06 SERV-X370 kernel: device veth962e4a8 entered promiscuous mode Aug 21 23:00:06 SERV-X370 kernel: br-1765d9199c3f: port 1(veth962e4a8) entered blocking state Aug 21 23:00:06 SERV-X370 kernel: br-1765d9199c3f: port 1(veth962e4a8) entered forwarding state Aug 21 23:00:06 SERV-X370 kernel: eth0: renamed from veth8be7821 Aug 21 23:00:06 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth962e4a8: link becomes ready Aug 21 23:13:11 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4c63e1f) entered disabled state Aug 21 23:13:11 SERV-X370 kernel: veth515d926: renamed from eth0 Aug 21 23:13:11 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4c63e1f) entered disabled state Aug 21 23:13:11 SERV-X370 kernel: device veth4c63e1f left promiscuous mode Aug 21 23:13:11 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4c63e1f) entered disabled state Aug 21 23:13:11 SERV-X370 kernel: br-1765d9199c3f: port 2(veth8c5060a) entered blocking state Aug 21 23:13:11 SERV-X370 kernel: br-1765d9199c3f: port 2(veth8c5060a) entered disabled state Aug 21 23:13:11 SERV-X370 kernel: device veth8c5060a entered promiscuous mode Aug 21 23:13:11 SERV-X370 kernel: br-1765d9199c3f: port 2(veth8c5060a) entered blocking state Aug 21 23:13:11 SERV-X370 kernel: br-1765d9199c3f: port 2(veth8c5060a) entered forwarding state Aug 21 23:13:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth8c5060a) entered disabled state Aug 21 23:13:13 SERV-X370 kernel: eth0: renamed from vethdac93bc Aug 21 23:13:13 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8c5060a: link becomes ready Aug 21 23:13:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth8c5060a) entered blocking state Aug 21 23:13:13 SERV-X370 kernel: br-1765d9199c3f: port 2(veth8c5060a) entered forwarding state Aug 21 23:13:44 SERV-X370 kernel: veth4d214fd: renamed from eth0 Aug 21 23:13:44 SERV-X370 kernel: br-1765d9199c3f: port 4(vethfb7dd33) entered disabled state Aug 21 23:13:44 SERV-X370 kernel: br-1765d9199c3f: port 4(vethfb7dd33) entered disabled state Aug 21 23:13:44 SERV-X370 kernel: device vethfb7dd33 left promiscuous mode Aug 21 23:13:44 SERV-X370 kernel: br-1765d9199c3f: port 4(vethfb7dd33) entered disabled state Aug 21 23:13:44 SERV-X370 kernel: br-1765d9199c3f: port 4(veth70ed143) entered blocking state Aug 21 23:13:44 SERV-X370 kernel: br-1765d9199c3f: port 4(veth70ed143) entered disabled state Aug 21 23:13:44 SERV-X370 kernel: device veth70ed143 entered promiscuous mode Aug 21 23:13:44 SERV-X370 kernel: br-1765d9199c3f: port 4(veth70ed143) entered blocking state Aug 21 23:13:44 SERV-X370 kernel: br-1765d9199c3f: port 4(veth70ed143) entered forwarding state Aug 21 23:13:45 SERV-X370 kernel: eth0: renamed from vethd408a54 Aug 21 23:13:45 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth70ed143: link becomes ready Aug 21 23:14:56 SERV-X370 kernel: br-1765d9199c3f: port 6(veth7c2e70d) entered blocking state Aug 21 23:14:56 SERV-X370 kernel: br-1765d9199c3f: port 6(veth7c2e70d) entered disabled state Aug 21 23:14:56 SERV-X370 kernel: device veth7c2e70d entered promiscuous mode Aug 21 23:14:56 SERV-X370 kernel: eth0: renamed from vethcf5f6c6 Aug 21 23:14:56 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7c2e70d: link becomes ready Aug 21 23:14:56 SERV-X370 kernel: br-1765d9199c3f: port 6(veth7c2e70d) entered blocking state Aug 21 23:14:56 SERV-X370 kernel: br-1765d9199c3f: port 6(veth7c2e70d) entered forwarding state Aug 21 23:21:50 SERV-X370 kernel: br-1765d9199c3f: port 6(veth7c2e70d) entered disabled state Aug 21 23:21:50 SERV-X370 kernel: vethcf5f6c6: renamed from eth0 Aug 21 23:21:50 SERV-X370 kernel: br-1765d9199c3f: port 6(veth7c2e70d) entered disabled state Aug 21 23:21:50 SERV-X370 kernel: device veth7c2e70d left promiscuous mode Aug 21 23:21:50 SERV-X370 kernel: br-1765d9199c3f: port 6(veth7c2e70d) entered disabled state Aug 21 23:21:50 SERV-X370 kernel: br-1765d9199c3f: port 6(veth01f9d64) entered blocking state Aug 21 23:21:50 SERV-X370 kernel: br-1765d9199c3f: port 6(veth01f9d64) entered disabled state Aug 21 23:21:50 SERV-X370 kernel: device veth01f9d64 entered promiscuous mode Aug 21 23:21:50 SERV-X370 kernel: br-1765d9199c3f: port 6(veth01f9d64) entered blocking state Aug 21 23:21:50 SERV-X370 kernel: br-1765d9199c3f: port 6(veth01f9d64) entered forwarding state Aug 21 23:21:50 SERV-X370 kernel: eth0: renamed from vethd27e290 Aug 21 23:21:50 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth01f9d64: link becomes ready Aug 21 23:22:17 SERV-X370 kernel: vethd27e290: renamed from eth0 Aug 21 23:22:17 SERV-X370 kernel: br-1765d9199c3f: port 6(veth01f9d64) entered disabled state Aug 21 23:22:18 SERV-X370 kernel: br-1765d9199c3f: port 6(veth01f9d64) entered disabled state Aug 21 23:22:18 SERV-X370 kernel: device veth01f9d64 left promiscuous mode Aug 21 23:22:18 SERV-X370 kernel: br-1765d9199c3f: port 6(veth01f9d64) entered disabled state Aug 21 23:22:23 SERV-X370 kernel: br-1765d9199c3f: port 6(veth9bab8f9) entered blocking state Aug 21 23:22:23 SERV-X370 kernel: br-1765d9199c3f: port 6(veth9bab8f9) entered disabled state Aug 21 23:22:23 SERV-X370 kernel: device veth9bab8f9 entered promiscuous mode Aug 21 23:22:23 SERV-X370 kernel: eth0: renamed from vetha79fad6 Aug 21 23:22:23 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9bab8f9: link becomes ready Aug 21 23:22:23 SERV-X370 kernel: br-1765d9199c3f: port 6(veth9bab8f9) entered blocking state Aug 21 23:22:23 SERV-X370 kernel: br-1765d9199c3f: port 6(veth9bab8f9) entered forwarding state Aug 21 23:29:04 SERV-X370 kernel: br-1765d9199c3f: port 6(veth9bab8f9) entered disabled state Aug 21 23:29:04 SERV-X370 kernel: vetha79fad6: renamed from eth0 Aug 21 23:29:04 SERV-X370 kernel: br-1765d9199c3f: port 6(veth9bab8f9) entered disabled state Aug 21 23:29:04 SERV-X370 kernel: device veth9bab8f9 left promiscuous mode Aug 21 23:29:04 SERV-X370 kernel: br-1765d9199c3f: port 6(veth9bab8f9) entered disabled state Aug 21 23:29:05 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4056f35) entered blocking state Aug 21 23:29:05 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4056f35) entered disabled state Aug 21 23:29:05 SERV-X370 kernel: device veth4056f35 entered promiscuous mode Aug 21 23:29:05 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4056f35) entered blocking state Aug 21 23:29:05 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4056f35) entered forwarding state Aug 21 23:29:05 SERV-X370 kernel: eth0: renamed from veth7735fab Aug 21 23:29:05 SERV-X370 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4056f35: link becomes ready Aug 21 23:30:36 SERV-X370 emhttpd: spinning down /dev/sda Aug 21 23:30:37 SERV-X370 emhttpd: read SMART /dev/sda Aug 21 23:33:22 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4056f35) entered disabled state Aug 21 23:33:22 SERV-X370 kernel: veth7735fab: renamed from eth0 Aug 21 23:33:22 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4056f35) entered disabled state Aug 21 23:33:22 SERV-X370 kernel: device veth4056f35 left promiscuous mode Aug 21 23:33:22 SERV-X370 kernel: br-1765d9199c3f: port 6(veth4056f35) entered disabled state Aug 21 23:33:22 SERV-X370 kernel: br-1765d9199c3f: port 6(vethfdf6815) entered blocking state Aug 21 23:33:22 SERV-X370 kernel: br-1765d9199c3f: port 6(vethfdf6815) entered disabled state Aug 21 23:33:22 SERV-X370 kernel: device vethfdf6815 entered promiscuous mode Aug 21 23:33:22 SERV-X370 kernel: br-1765d9199c3f: port 6(vethfdf6815) entered blocking state Aug 21 23:33:22 SERV-X370 kernel: br-1765d9199c3f: port 6(vethfdf6815) entered forwarding state Aug 21 23:33:22 SERV-X370 kernel: eth0: renamed from veth332bc05

I'm starting with the recommendations in that thread.

Would be nice to have the Fix Common Problems plugin somehow how check for this if it is a problem. Any advice on how to start investigating what is writing the the flash?

Can someone please tell me if the below usage for the My Servers flash backup is intended behavior? Is there anyway to get this to stop other than uninstalling? Aug 21 05:00:56 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:02:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:03:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:06:00 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:07:00 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:13:02 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:14:02 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:15:03 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:20:05 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:21:06 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:22:07 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:29:37 SERV-X370 emhttpd: spinning down /dev/sda Aug 21 05:29:38 SERV-X370 emhttpd: read SMART /dev/sda Aug 21 05:30:13 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:35:31 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:36:40 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:38:41 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:39:41 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:40:42 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:41:09 SERV-X370 emhttpd: spinning down /dev/sdb Aug 21 05:41:42 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:42:42 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:51:54 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:53:55 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:54:56 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:55:56 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:57:57 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:58:57 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 05:59:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:00:01 SERV-X370 root: Starting Mover Aug 21 06:00:01 SERV-X370 root: Forcing turbo write on Aug 21 06:00:01 SERV-X370 kernel: mdcmd (59): set md_write_method 1 Aug 21 06:00:01 SERV-X370 kernel: Aug 21 06:00:01 SERV-X370 root: ionice -c 3 nice -n 5 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 15 0 0 '' '' '' '' no 80 '' '' Aug 21 06:00:18 SERV-X370 root: Restoring original turbo write mode Aug 21 06:00:19 SERV-X370 kernel: mdcmd (60): set md_write_method auto Aug 21 06:00:19 SERV-X370 kernel: Aug 21 06:00:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:05:59 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:06:59 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:10:00 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:11:00 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:17:02 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:18:02 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:19:02 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:20:02 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:21:03 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:26:05 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:27:06 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:29:39 SERV-X370 emhttpd: spinning down /dev/sda Aug 21 06:29:41 SERV-X370 emhttpd: read SMART /dev/sda Aug 21 06:30:07 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:40:13 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:41:10 SERV-X370 emhttpd: spinning down /dev/sdb Aug 21 06:50:16 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 06:59:41 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:00:50 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:01:54 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:03:54 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:07:56 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:10:57 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:11:57 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:12:57 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:13:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:14:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:15:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:16:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:17:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:18:59 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:19:59 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:20:59 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:23:00 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:24:00 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:25:00 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:29:42 SERV-X370 emhttpd: spinning down /dev/sda Aug 21 07:29:44 SERV-X370 emhttpd: read SMART /dev/sda Aug 21 07:30:03 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:31:04 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:32:05 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:34:07 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:40:20 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:41:11 SERV-X370 emhttpd: spinning down /dev/sdb Aug 21 07:41:21 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:42:22 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:43:24 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:44:24 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:47:36 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:49:41 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:50:49 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:51:57 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 07:53:58 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:10:02 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:14:03 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:15:03 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:16:04 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:20:05 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:23:13 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:24:13 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:25:15 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:29:45 SERV-X370 emhttpd: spinning down /dev/sda Aug 21 08:29:46 SERV-X370 emhttpd: read SMART /dev/sda Aug 21 08:34:22 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:40:31 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:41:12 SERV-X370 emhttpd: spinning down /dev/sdb Aug 21 08:50:37 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 21 08:54:37 SERV-X370 flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update

I don't have the ability to shut everything down for the amount of time required to verify at the moment but I would hazard to guess that you are correct as typically the errors occur whenever I'm doing some kind of activity in another docker. But it has happened with multiple different docker applications and doesn't seem to be consistent. It seems as if any sort of RAM-heavy activity in another docker seems to trigger an OOM error that very often (but not always) crashes my VM (in addition to whatever process the OOM process kills of course). Just to restate, the VM often crashes even though the OOM finds and kills only a docker process. I just need to find out WHY OOM is being triggered at all when I have 32GB of RAM. WTF IS GOING ON. This is not okay for a server to be constantly killing random processes and crashing VMS. Who knows what essential files have already been corrupted.

Nothing? Do I need to post in a different section?

Something is causing authelia to spike RAM but I still don't understand why that should cause OOM errors that crash my VM. It's not even always authelia that causes it. HOW DO I GET THIS TO STOP???

Literally just happened again while trying to access backuppc. serv-x370-diagnostics-20220702-2027.zip

Here is my VM XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='13'> <name>DESK-X370</name> <uuid>53c1ad51-0912-f7c2-ba7e-d08b992d4cf2</uuid> <description>WIN10PRO (UEFI|GPT) - Q35-6.2</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='7'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='8'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='9'/> <vcpupin vcpu='7' cpuset='21'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='22'/> <vcpupin vcpu='10' cpuset='11'/> <vcpupin vcpu='11' cpuset='23'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/53c1ad51-0912-f7c2-ba7e-d08b992d4cf2_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='6' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/_bin/_vm/images/bob.ombs.modified.win10pex64.v4.8.iso' index='3'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/_bin/_vm/images/virtio-win-0.1.217-2.iso' index='2'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/sda' index='1'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='usb' index='0' model='nec-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:7b:84:29'/> <source bridge='br0'/> <target dev='vnet12'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/30'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/30'> <source path='/dev/pts/30'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-13-DESK-X370/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2c' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2c' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52b'/> <address bus='1' device='6'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

I'm at my wits end here, I have wasted so much time trying to get this damn windows VM to work. I literally spent half a year trying to get VM passthrough to work and I finally get it to work and now I'm having constant OOM errors. It's outrageous how much time I've sunk into this. Can someone please help me figure out why my Windows 10 VM ALWAYS crashes with Out of Memory errors. Sometimes the OOM error will cite the VM as the source, sometimes it will cite a seemingly random docker as the source. I have more than a sufficient amount of memory for anything I could want to do with this server, it's insane that I'm having OO memory issues on a modern server. I have run the VM with less and more memory to no avail. I have reduced the niceness of all of my dockers. I have switched to isolated threads, solely to try to get this damn VM to work. Can someone please take a look at my diagnostics and try to help me figure out what is going on? serv-x370-diagnostics-20220702-2013.zip

Hi, was something changed about a month ago that effected the parsing of variables, specifically the RCLONE_USER_FLAGS variable? I used to use the below string as one of my user flags in order to BACKUP files from the SYNC into the correct folder based on the current rclone_media_shares_item share being run e.g. BACKUPS/PERSONAL, BACKUPS/PROFESSIONAL, etc.. This was running correctly up until about a month ago when it then created a new folder at "BACKUPS/${rclone_media_shares_item}" where it then started comining all my backup files from all shares into that same folder. RCLONE_USER_FLAGS="other flags... --backup-dir BACKUPS/${rclone_media_shares_item}" I've looked at your repository and can't seem to be able to find what the hell changed. Would appreciated any help.

I just wanted to add a follow up for this in case anyone is in my same scenario. I was confused when you made this comment specifically when you said "the plugin still operates as is with its default settings" because the only thing that was working for me was the separation into folders. None of the context menu items were working for my on any of the icons. It turns out the actual source of the problem is in the "Preview advanced context menu" option for the docker folders. It turns out this is the feature where the main bug is. After turning this off (I had it on for all folders because it's pretty useful), the typical context menu features started working again. This brings back the major useful functionality of the plugin and I can again navigate my dockers without pulling my hair out. Thanks.

Nooooo! I love this app. Guess I might finally have to switch over to portainer.

I'm having the same issue as @kjames2001 here. The latest update had quite a few updates to the docker system. Would be great to get a fix!

Can someone please tell me what these Errors are about? I've been regularly getting them for a few months now. Diagnostics attached. serv-x370-diagnostics-20220208-1402.zip