wgstarks

This looks like your problem- 2026-05-29 10:05:35,372 DEBG 'start-script' stdout output: [info] PIA endpoint 'mexico.privacy.network' is NOT in the list of endpoints that support port forwarding shown below:- 2026-05-29 10:05:35,601 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- 2026-05-29 10:05:35,601 DEBG 'start-script' stdout output: [info] nl-amsterdam.privacy.network [info] np-nepal-pf.privacy.network [info] pe-peru-pf.privacy.network [info] yerevan.privacy.network [info] monaco.privacy.network [info] in.privacy.network [info] gt-guatemala-pf.privacy.network [info] uy-uruguay-pf.privacy.network [info] hk.privacy.network [info] mongolia.privacy.network [info] ca-toronto.privacy.network [info] ca-vancouver.privacy.network [info] morocco.privacy.network [info] lu.privacy.network [info] de-germany-so.privacy.network [info] kazakhstan.privacy.network [info] ca-ontario.privacy.network [info] venezuela.privacy.network [info] ua.privacy.network [info] bo-bolivia-pf.privacy.network [info] cyprus.privacy.network [info] ec-ecuador-pf.privacy.network [info] uk-2.privacy.network [info] srilanka.privacy.network [info] cambodia.privacy.network [info] ca-ontario-so.privacy.network [info] kr-south-korea-pf.privacy.network [info] liechtenstein.privacy.network [info] sanjose.privacy.network [info] austria.privacy.network [info] nl-netherlands-so.privacy.network [info] ca-montreal.privacy.network [info] malta.privacy.network [info] man.privacy.network [info] bangladesh.privacy.network [info] montenegro.privacy.network [info] ba.privacy.network [info] macau.privacy.network [info] panama.privacy.network [info] vietnam.privacy.network [info] bahamas.privacy.network [info] albania.pvt.site [info] algeria.pvt.site [info] andorra.pvt.site [info] argentina.pvt.site [info] au-adelaide.pvt.site [info] au-brisbane.pvt.site [info] au-melbourne.pvt.site [info] au-perth.pvt.site [info] au-sydney.pvt.site [info] belgium.pvt.site [info] brazil.pvt.site [info] bulgaria.pvt.site [info] chile.pvt.site [info] china.pvt.site [info] colombia.pvt.site [info] croatia.pvt.site [info] czech-republic.pvt.site [info] de-berlin.pvt.site [info] de-frankfurt.pvt.site [info] denmark.pvt.site [info] egypt.pvt.site [info] es-madrid.pvt.site [info] es-valencia.pvt.site [info] estonia.pvt.site [info] fi-helsinki.pvt.site [info] france.pvt.site [info] georgia.pvt.site [info] greece.pvt.site [info] greenland.pvt.site [info] hungary.pvt.site [info] iceland.pvt.site 2026-05-29 10:05:35,602 DEBG 'start-script' stdout output: [info] indonesia.pvt.site [info] ireland.pvt.site [info] israel.pvt.site [info] it-milano.pvt.site [info] jp-tokyo.pvt.site [info] latvia.pvt.site [info] lithuania.pvt.site [info] malaysia.pvt.site [info] mexico.pvt.site [info] moldova.pvt.site [info] new-zealand.pvt.site [info] nigeria.pvt.site [info] north-macedonia.pvt.site [info] norway.pvt.site [info] philippines.pvt.site [info] poland.pvt.site [info] portugal.pvt.site [info] qatar.pvt.site [info] romania.pvt.site [info] saudi-arabia.pvt.site [info] se-stockholm.pvt.site [info] serbia.pvt.site [info] singapore.pvt.site [info] slovakia.pvt.site [info] slovenia.pvt.site [info] south-africa.pvt.site [info] switzerland.pvt.site [info] taiwan.pvt.site [info] turkey.pvt.site [info] uk-london.pvt.site [info] uk-manchester.pvt.site [info] uk-southampton.pvt.site [info] united-arab-emirates.pvt.site PIA has made some recent changes to their server host names. You’ll need to correct it in your OVPN (or WireGuard) file.

The documentation linked in the first post includes instructions how to setup WireGuard using PIA. https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Scroll down to Q21.

PIA has also recently changed the host names for some of their servers so you may be using an invalid host name.

IIRC you’ll need to download it from PIA.

No. The supervisord log is only for this container. Also, your docker run command isn’t in diagnostics.

Try it with the default password.

Your supervisord log is in the appdata folder and you can click on the words docker run (it’s a link) to get info on how to generate the command so you can post it.

Tiny log snippets aren’t really useful. You need to attach the entire supervisord log as well as your docker run command to your next post. Be sure to redact any users/passwords.

It’s a little hard to get into the x4 slot though. Had to loosen the push button (boot) switch and slide it out of the hole for a little extra space.

I have done this to mine without any problems.

I did a bunch of googling last night and it appears that using macvlan for the docker network can possibly cause this sort of problem so I have switched to ipvlan. Will give it a couple of days and see what happens. 🤞 If the crashes continue I’ll try your suggestion but I haven’t added any dockers recently and VMs are disabled. Thanks for your help.

If you can’t connect attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords.

Yes. Not sure it’ll work with WireGuard though. The log snippet you posted shows a successful start. You should be able to connect to the webUI from your local network.

These are the last entries before the freeze/hard reset- Jun 9 16:00:03 BrunnhildeTwo root: /var/lib/docker: 14.8 GiB (15930499072 bytes) trimmed on /dev/loop2 Jun 9 16:00:05 BrunnhildeTwo root: /var/lib/docker/btrfs: 14.8 GiB (15930925056 bytes) trimmed on /dev/loop2[/btrfs] Jun 9 16:00:24 BrunnhildeTwo root: /mnt/cache: 135 GiB (144437903360 bytes) trimmed on /dev/nvme1n1p1, /dev/nvme0n1p1 Jun 9 16:00:24 BrunnhildeTwo root: /mnt/flash: 2.00 GiB (2142236672 bytes) trimmed on /dev/nvme2n1p3 Not sure if they have any bearing?

Server locked up again. syslog attached. syslog-10.0.1.20.log

It doesn't actually say that your server won't start a parity rebuild. I've never used 2 parity disks so can't be sure but I would expect it to start a rebuild when you start the array.

I misread your first post but the basic steps would still be the same. I would change the parity drives first using “new config” and rebuild parity. After the rebuild is finished make your changes to the array.

Personally I would add your second parity drive first and rebuild parity. Remember that both these drives must be larger than any other drive. After the rebuild is complete add the large array drive. If it’s new and you want to test it you can preclear it. If it’s not new and under warranty you can just let the system clear the drive as part of the “add” process. After adding the large drive you can move data as required to empty the small drives and remove them. If you have a large amount of empty space on your array you might possibly combine the removing of the small drives and adding the large one.

Deleted the syslog file and rebooted. Will post back here if the issue recurs.

I used the switch and here are the current settings for my boot mode- menuentry "Unraid OS" { echo "Loading..." linux /boot@/bzimage pcie_aspm=off linux /bzimage pcie_aspm=off initrd /boot@/bzroot }Please confirm this is correct before I reboot.

Or maybe this?

Like this???

Maybe I found it? Is this correct???

Not sure I understand how to do this. Tried googling and got this- Not sure this is correct though since I don’t see a Syslinux Configuration tab anywhere.

Seeing lots of kernel errors. I don't pretend to understand the entries though.