Kudagra

Does anyone know if it's possible for a script to detect individual docker's "Autostart" setting? If so, you could create a script that only starts all dockers with the setting enabled.

Just to provide an update on this problem- it ended up being a faulty CPU as JorgeB suggested. I successfully RMA'd my 5950x a few weeks back (meaning it failed their testing), and I haven't seen the errors since installing the replacement CPU.

This issue seems to have began after installing GluetunVPN, and it only affects the dockers I have network traffic routed directly through it. Randomly (but more often than not it’s after the weekly automated AppData backup) my torrent’s stop seeding and I can’t access my Firefox docker webui. All I have to do to correct the problem is to open up the docker tab in Unraid, and refresh the webpage. I never get any errors in the log, but the only sign that something is wrong is the constant “loading” animation on the screen. I’ve attempted to add a longer Autostart delay to the dockers after Gluetun, and I rebuilt my entire docker file (swapped to a directory). Neither have solved the problem.

Unfortunately BIOS is already up to date, but I did have this error popup in my log. Think it's related?

Hey did you ever have any luck with solving this? I randomly started been getting the same warning with my 5950x a couple months back.

I disabled the RAM overclocking, but unfortunately I'm still receiving the 'Machine Check Events' error (most recent diag attache). Unfortunately I don't have a second CPU on hand to try, so you have any suggestions on how I can test the health of this CPU? As for the disk errors (for anyone else seeing this problem)- I resolved this with a new PSU. Apparently my previous PSU had one of it's rails failing. diagnostics-20230808-0941.zip

Thank you for the response. Would you suggest I test for CPU failure? I've attached a zip of the full diagnostics (which was downloaded at the same time as the previously attached syslog file). diagnostics-20230522-1711.zip

Any suggestions?

I'm not sure if these two items are correlated, but I just woke up to a MCE error in fix common problems, and also a disabled parity drive due to read errors. I was having read errors with multiple drives a couple weeks back, so I did extensive RAM testing, but it ended up being resolved (I think?) by moving my HDD sata power plugs to a different PSU rail. Now this single drive comes comes back with more errors (the system disabled it). May 20 08:07:38 Osgiliath kernel: mce: [Hardware Error]: Machine check events logged May 20 08:07:38 Osgiliath kernel: [Hardware Error]: Deferred error, no action required. May 20 08:07:38 Osgiliath kernel: [Hardware Error]: CPU:1 (19:21:0) MC12_STATUS[Over|-|-|AddrV|PCC|SyndV|UECC|Deferred|Poison|Scrub]: 0xc765ffc883007f37 May 20 08:07:38 Osgiliath kernel: [Hardware Error]: Error Addr: 0x0000000000000000 May 20 08:07:38 Osgiliath kernel: [Hardware Error]: IPID: 0x0000000000000000, Syndrome: 0x0000000000000000 May 20 08:07:38 Osgiliath kernel: [Hardware Error]: Bank 12 is reserved. May 20 08:07:38 Osgiliath kernel: [Hardware Error]: cache level: L3/GEN, tx: DATA Any ideas? syslog.txt

Just some feedback- This gave me 50-60 fps on average at 1440p with almost everything set to ultra in Windows 11. Unfortunately, enabling Hyper-V within windows broke display output to my second monitor. so it's not a feasible solution for me... but it did get the game going at least! Keeping the XML adjustments but DISABLING Hyper-V within windows does not allow the game to launch. My passed through VM hardware- 3950x (8 isolated cores), 6800xt, 32gb RAM, SSD (bare metal).

Changed Status to Solved I've resolved all issues listed in the OP. Tested successfully in both 6.9.2 and 6.10.0 rc-1. I'm not sure what exact setting did it, but after tinkering more and more in the network settings, I managed to strike gold after adjusting "Bonding" and "Interface Rules" enough times. Something to do with within those areas was fine prior to 6.8.3 and below, but wasn't 100% compatible with 6.9.x and above. command.center-diagnostics-20210916-1350.zip

Thanks for the tip. Randomly enough, it looks like my UPS (network port) is causing the recent issues with connectivity to github and whatnot. I tried a couple different cables, but the only way for me to get a stable connection now is by bypassing the UPS's Ethernet port all together? My mobo's Intel LAN port doesn't play well with my UPS port, but the Realtek LAN port works fine with it... Odd. I'm still having the same original issues listed in the OP, though (slow dockers, VM network connection issues, ect..). command.center-diagnostics-20210916-1350.zip

I manually updated my main server to 6.10.0 rc-1 by copying over the "bz" files (there was no option to upgrade in the UI), and then replaced the network.cfg with that from the fresh "6.10.0 rc-1 (UEFI + Static)" install. Now I can no longer access github (fix common problems scan) nor the community applications store. I've tried adjusting the DNS servers to no avail, and I'm seeing errors like- nginx: ..... [error] 12411#12411: *4229 upstream timed out (110: Connection timed out) while reading response header from upstream, client: .... Error: Unable to communicate with GitHub.com Download to appfeed failed command.center-diagnostics-20210915-1529.zip

I feel like I should have tested this long before your suggestion... I have both GUI access and network UI access with a fresh install of 6.10.0 rc-1. That eliminates any hardware incompatibilities! EDIT: I did some testing with various network settings on fresh installs (my main server uses UEFI + Static)- 6.10.0 rc-1 (UEFI + DHCP) = GUI and webUI success 6.10.0 rc-1 (UEFI + Static) = GUI and webUI success 6.9.2 (UEFI + DHCP) = NO GUI (black screen with blinking cursor) but webUI success 6.9.2 (UEFI + Static) = NO GUI (black screen with blinking cursor) but webUI success (sluggish)

Make any progress on getting this issue resolved on 6.9.x? Or you still running 6.8.3?