[[Plugin] Realtek R8125 R8168 and R8152\6 drivers]

Is the problem only when using PCI or USB with RTL8125?
Im runnning z790-p with onboard ethernet RTL8125. Can I still get problems?

[[6.12.6] accessing log via android chrome/brave question]

I have the exact same problem. I thought I did something wrong. 

It's working fine with my other server still running 6.11.5. 

 

It works if I use FF. So I guess brave on phone and 6.12.6 doesn't like each other... 

[Windows 10 VM does not boot anymore after upgrade of motherboard + cpu]

On 5/16/2023 at 9:52 PM, gvh said:

Found out it was because WSL2 was enabled and nested virtualization is not supported on Raptor Lake. AM4 did support nested virtualization but 13th gen Intel does not.

 

I was able to boot and run the system with the following changes to the config:

  <cpu mode='custom' match='exact' check='full'>
    <model fallback='forbid'>Broadwell-noTSX</model>
    <feature policy='disable' name='hypervisor'/>
    <feature policy='require' name='vmx'/>
    <feature policy='disable' name='svm'/>
    <feature policy='require' name='vme'/>
    <feature policy='require' name='f16c'/>
    <feature policy='require' name='rdrand'/>
    <feature policy='require' name='arat'/>
    <feature policy='require' name='xsaveopt'/>
    <feature policy='require' name='abm'/>
  </cpu>

 

I could start and use my VM without an issue but it was really slow and capped at 4 cores (broadwell architecture?)

All of the other cpu models I tried to emulate resulted in a message that the host cpu didn't support some of the features.

 

After a lot of googling found out that this might be an issue in the current Linux kernel and we'll have to wait for a fix.

 

At least I was able to save my VM, after booting I could disable WSL and set my CPU settings to the default settings.

I'm now using an Ubuntu VM with remote-ssh in vscode instead of WSL.

 

More info on emulating a CPU to get Hyper-V / WSL2 running: https://www.redpill-linpro.com/techblog/2021/04/07/nested-virtualization-hyper-v-in-qemu-kvm.html

I tried uninstalling and disabling everything bound to WSL/wsl2, and then pasted my original xml for my win10, but it still wont start...
Any ideas?

[VT-X nested virtualisation 6.12]

So this is not fixed in latest unraid version?

[Windows 10 VM does not boot anymore after upgrade of motherboard + cpu]

Thanks for the advice.
Same happened to me with my new 13500. Ran 8700k before, and it was working just fine.

Is this fixed in latest unraid version??

[[Support] binhex - qBittorrentVPN]

Is there still problems with qbittorrent after 4.3.9 that makes unraid crash? 

[[SOLVED] Cannot access dockers using custom:br0]

Same thing happened now after reboot. Cannot access dockers on br0 from NPM on my custom docker network. 

[[Support] binhex - qBittorrentVPN]

2 hours ago, jcarre said:

 

I am having exactly the same problem. Qbitorrent crashes with a:

 

 

 

When this happens web ui becomes unresponsive, docker kill makes the ui work again, but qbitorrent won't restart correctly. 
The only fix is to restart docker, which will not start again for me until I fully restart.
I also have the umount error while turning off the array.

 

The problem seemed to go away after last update, I got a couple days uptime. But it happened twice yesterday.

I've rolled back qbit to 4.3.9 now. Hope that helps. 

[[Support] binhex - qBittorrentVPN]

I'm courious if anyone else got the same problem with this docker.
I've been using it for a couple of years now and it happens from time to time.

The docker seems to crash and the unraid webui becomes unresponsive.
I've tried a couple of different methods to kill the docker, but it always  ends with rebooting the server.

I've been using it with Nordvpn before and now Im using mullvad vpn. Earlier I did not use privoxy, but now my prowlarr docker is connecting via the privoxy.
Cannot see anything obvious in the logs what is causing the "crash".

 

When this happened like two hours ago, I tried stopping docker service via ssh. It says something like "cannot stop docker qbit".

But the service stops. And the webui gets responsive again. But then i cannot start the docker service bacause "docker.img is in use".

So i tried to stop the array. But then the log said it "cannot unmount /mnt/cache because its busy".
So I tried a command I read in another thread on the forums "lsof /mnt/cache". And it listed a few .lock-files in the qbit-appdata folder.
My appdata is stored on the cache only.

Then i tried reboot, but I guess that was not a clean one, because it started a parity sync on startup.

Where to look for a solution?

 

Is this what's causing me problem? 

 

[[SOLVED] Cannot access dockers using custom:br0]

Just ran into this. Running 6.11.5.
But it took me like 2 hours before I found this thread and tested it.
Was checking all docker logs to find out what was wrong.
Then I saw that the problem was NPM could not route to dockers on br0. And after hours of googling, i found this thread. Thanks!

But would be nice to get this fixed.

I thought i broke something last night when I was fixing nextcloud php problem.

[[Support] binhex - qBittorrentVPN]

On 1/19/2023 at 2:48 AM, ChadwickTheCrab said:

Anyone else having an issue with privoxy at the moment? My *arrs work fine if I disable proxy. I made no config changes, just noticed I couldn't add a movie today unless I disabled the proxy in Radar.

Edit: Deleted privoxy folder and changed NAME_SERVERS to just google and cloudflare IPs. Not sure which fixed it but all is good now.

Yes, I noticed my prowlarr indexer not working.
But I've already removed the privoxy folder and changed the DNS in qbit docker. It worked like a couple of days, and now it's the same again...