Hi , I'm now selling some used ECC-RAM at 8GB each.
8 ECC RAM: HMT41GV7BMR4C-H9 - SK Hynix 1x 8GB DDR3-1333 RDIMM PC3-10600R --> PRICE 100 EUR
CPU Cooler for socket 2011 -- > Price 35 EUR
Byer pay for delivery cost.
The item is in Sweden and prefere to sell in Sweden.
//Peter
Have not time now to update... but some changes on githup page and to fix this you can for now try to update the script --> /usr/local/emhttp/plugins/openvpnserver/scripts/rc.openvpnserver
Line 349 change f16 to f14
Line 376 change f16 to f14
Solved the issue with adding the following to the boot parameters:
pcie_no_flr=1022:149c,1022:1487
source -- https://forum.level1techs.com/t/attention-flr-kernel-patch-fixes-usb-audio-passthrough-issues-on-agesa-1-0-0-4b/151877
//Peter
Solved the issue with adding the following to the boot parameters:
pcie_no_flr=1022:149c,1022:1487
source -- https://forum.level1techs.com/t/attention-flr-kernel-patch-fixes-usb-audio-passthrough-issues-on-agesa-1-0-0-4b/151877
//Peter
Looks stable with qemu 3.0 now I added "pcie_no_flr=1022:149c,1022:1487" to boot parameters and changed qemu to 4.2 on one of my w10 VM .......... so we will see after some day how it works.
My 2 VM:s have been OK since I lower the quemu to 3.0, so far no issues with shutdown (2 W10 and one OSX)
How did you patch unraid kernel @Leoyzen? and what is your qemu settings for the VM ?
//Peter
I have done a test to lower qemu settings to 3.0 and have not see any issue yet, I will let the VM's be on for a week or so before I do a new shutdown or reboot.
I have done a test to lower qemu settings to 3.0 and have not see any issue yet, I will let the VM's be on for a week or so before I do a new shutdown or reboot.
I have 2 VM running.
One VM have an AMD GPU and USB card pass trough and freezing unraid when shutting down.
When shutting down the other VM with NVIDIA GPU and NO USB card pass trough it still freezing the unraid server 😞 😞
And nothing in the log 😞 😞
//Peter
Thanks for the replay Jonp, I will look into this and disable the GPU and test. For me this issue have been here at least 1 year, perhaps longer.
So it's impossible to say when it was working, BUT definitely it has been working in the past.
//Peter