ryoko227

Thanks, that fixed it! Now when I open the Plugin tab, it checks the status.

Updated the office server from 6.8.3 -> 6.10.2, seems like no issues so far! UPDATE- Couldn't get the VM to reboot without black screening the system, ended up bonding the GPU and USB Controller via the VFIO-PCI option in System Devices. This fixed that issue. Also was finally able to remove the "Docker - Case Insensitive" fix from the go file. UPDATE 2- In the Plugin tab, they show as status unknown everytime, until I click check for updates. Solved by this .... Final issue being, Nerdpack is showing "kbd-1.15.3-x86_64-2.txz" and "mcelog-161-x86_64-1.txz" as being "update ready" even though neither of those exist on my flash device under the 6.10 nerdpack plugin folder.

Stop and edit the docker. Change Repository: to this... linuxserver/openvpn-as:2.8.8-cbf850a0-Ubuntu18-ls122 Click Apply and it will rebuild the image You should be good to go after that once it finishes loading up o/

Unfortunately I tried that as well as connecting from differing machines that normally do not have access. No joy. I ended up reverting back to 6.8.3 due to other issues, but won't be able to mess with the docker till next Tuesday. UPDATE (solved) - Seems to have been a corrupted image. Moved the appdata to another share, removed the image, reinstalled via template, copied the appdata back over, used the controller's autoback file from the beginning of the month to restore everything. 100% back up and running.

Updated unRAID 6.8.3 -> 6.9.2 and now get a "ERR_CONNECTION_REFUSED" when trying to access my unifi 5.14.23 docker webui. The docker log shows no errors messages. So I tried: removing and redownloading the docker, completing deleting the docker image, reverting to 6.8.3, etc. Tried playing with the webui ports in the docker, but it just spits out the same error. The tunnels I have to offsite USGs are still up and according to their webui's, "The UniFi Controller is currently unreachable." TBH, not sure if this is a 6.9.2 issue, or an underlying issue that happened to pop off when I tried the update. Has anyone else run into this or has a suggestion on where/what I can try?

Out of curiosity, which video did you find? What was the exact solution for your problem? I am also having a similar issue, worked fine in 6.8.3, but not with 6.9.2 @awediohead

Unfortunately, based on your described symptoms, coincidental failure at the same time you happened to be updating/rebooting your unRAID. If you are not getting POST of any kind, then this points to your hardware/bios. At minimum when you start a PC you should get a post screen. If you are getting nothing on a confirmed working monitor, then you need to dig deeper. Firstly, pull your unRAID USB out and set it off to the side, you won’t need it right now. Your goal is to get the PC to properly boot, then worry about whether your unRAID works. There are many things that could be wrong when you get a solid black screen/no signal. If your MB displays post codes, check your manual to see what they mean and follow the troubleshooting steps. If the MB is older and doesn’t have this feature (nor a pc speaker), you might want to look into the following…. BIOS – may have gotten corrupted (pull all power, hit bios/cmos reset button (if your MB has this) or hold in the power button) plug it back in and see if it will boot. GPU – may have died, or gotten unseated while you have been working on this (try pulling it out and reseating, additionally, you could try it in a different slot). If you have another PC nearby, verify the GPU works by tossing it into the other machine to see if you can get a post screen. Memory – reseat all, still nothing? pull all out, try each dimm one at a time in different slots (try to see if you have a bad dimm). This is a process of elimination to try and find the fault in your PC. I think the above is enough for now, if none of the above solves it, let us know and we will try to go from there. PS – Truth be told, I had a CMOS battery die on me once, and after a simple reboot it borked my bios and I had to reset like I mentioned above. With constant power, that shouldn’t be possible, but meh, tech stuff so…. Best of luck.

64GB 3200 non-ecc

Japanese would be greatly appreciated as well.

Smooth update on the Home server from 6.8.2->6.8.3. The new kernel fixed my nvme IO_PAGE_FAULT issue, which is awesome!! I was also able to easily get the AMD cache thing running on my VMs with a simple Edit->Update to each of them. Awesome work as always Limetech! EDIT/UPDATE: Work server also updated from 6.8.2->6.8.3 with no issues.

Sorry I haven't gotten back to you on this!!! I agree with you on the kernel patching (way outside my bredth), www. I haven't had a chance to update unRAID to 6.8.3 yet, but the kernel for that is ... Linux kernel: version 4.19.108 (CVE-2020-2732) kernel-firmware: version 20200207_6f89735 oot: wireguard: version 0.0.20200215 I hopped back over to bugzilla, and according to Comment 111 , it's been commited. Here's a quote for brievity... So, I would think that (haven't tested yet) it *should* be fixed with an unRAID update. When I get around to updating the system with the issue, I'll edit/post the results! EDIT/UPDATE - No more errors with the 6.8.3 update on mine 🥰

Thank you for this!! I can confirm this works and got Manjaro 18.1.5 KDE Plasma running using binhex's method.

Updated from 6.7.2 to 6.8.2 on 2 servers and seem to have no issues. Dockers are up and running and VMs with passthrough all seem good too. *cheers*

※Related to the "unexpected GSO type" issue on unRAID 6.8※ Yes, related to unRAID's specific workload, hence the reason I worded it the way I did and linked what Tom wrote on that topic. For clarification, Tom in his own words... "This implies the bug was introduced with some code change in the initial 5.0 kernel. The problem is that we are not certain where to report the bug; it could be a kernel issue or a docker issue. Of course, it could also be something we are doing wrong, since this issue is not reported in any other distro AFAIK." That link is related to passthrough of an NVME device and was a seperate issue that has been resolved to my knowledge. The problem that we are discussing is related to IO_PAGE_FAULT being thrown when a NVME is trimmed, specifically to users who need to have IOMMU enabled. The current kernel patch information is located here https://bugzilla.kernel.org/show_bug.cgi?id=202665#c105 Awesome! It looks like from the latest update on https://bugzilla.kernel.org/show_bug.cgi?id=202665#c107 that you need to build a custom kernel with the patch applied to it. I've never attempted that, but to be completely honest, I don't know how one would apply that into unRAID, www.

I actually never got around to trying it TBH. The newer versions of unRAID were slated to jump into the 5.x kernels, so I was just holding off hoping that it would just come down the pipe, www. Unfortunately 6.8, with the 5.x kernels are having some new, weird, unRAID only error that was mentioned in this post "UNRAID OS VERSION 6.8 RELEASE PLAN"... so... I will have to look into this patching again when I get some free time.