Hollandex

Well, don't I feel dumb. I looked to see if qbittorrent had a way to change the port but failed to turn on the advanced view. Anyway, this worked perfectly. Thanks!!

I'm having issues running this and binhex-qbittorrentvpn together. I have binhex-qbittorrentvpn running on port 8080 (default). I have binhex-sabnzbd set to use the binhex-qbittorrentvpn container's network. I tried changing the binhex-sabnzbd Ports 1 and 2 to 9090 and 9091, respectively. I also turned on advanced settings and switched the webgui URL to [PORT:9090]. However, when I go to http://<myip>:9090, I get nothing. I have ports 9090 and 9091 routed through binhex-qbittorrenvpn the same as Prowlarr, Sonarr, Radarr, and Flaresolverr (which all work fine) but I just can't access binhex-sabnzbd no matter what I do. Is there something fancy I need to do to move binhex-sabnzbd to a different port? Or is there a better way to run both binhex-qbittorrent and binhex-sabnzbd through a VPN? Thanks in advance for any help.

Is there a way to make the Palworld server NOT a community server? I just want to host it on my LAN for my family. I don't have 8211 forwarded, obviously, but I'm curious if that's enough to keep my server off the community list.

I switched to a single drive using xfs, with an aggressive backup schedule. I haven't a single corruption issues since I switched. I'd like to move to zfs at some point, but I don't see a reason to yet. If it ain't broke...

My thread history will tell the tale. haha Long story short, I've never had much luck with it. Always getting file corruption errors, to the point of having to format the entire cache pool. Which sort of negates the redundancy of BTRFS if I'm having to format the whole thing anyway. RAM seems to be the culprit, even though 12 hours of memtest show the RAM is working just fine. So yeah, BTRFS seems neat and apparently works great for 99% of the people that use it. But not me.

Yeah, I'm running Mover now to get everything off the cache so I can format it again. I might abandon BTRFS and go to XFS with an aggressive backup schedule or something. At the very least, I'm curious if I run in to any data corruption issues outside of BTRFS. I appreciate all your help. I believe you've been the one replying to every help thread I've started. Thank you.

Yeah, I ran memtest for about 12 hours a while back without any errors at all. This really seems to be a BTRF issue. Obviously, my hardware is playing some part in it but this RAM works fine in every other application. But when it comes to BTRFS, something isn't right. I'm sort of at a point where I don't care about redundancy on my cache drive. It hasn't helped anyway. I've had my entire cache drives go corrupt and become unrecoverable, leading me to lose everything on them. So I'm tempted to just use XFS and have an aggressive backup schedule or something.

Correct. At the moment, all the cache has on it is domains, system, and appdata. No other directories.

sanctuary-diagnostics-20230110-1228.zip

Not really sure where this type of topic should live. Hopefully, this is the correct spot. I'm curious why our only option for redundant cache pools is BTRFS. For instance, why couldn't we use XFS and let it handle the parity like it does with the array? Not against BTRFS. Just curious why that's the only option provided for cache pools.

Sorry, I realize what you're saying now. I ran a scrub and get 6 errors that it can't fix. The files are odd. Things like usr/lib/freerdp2/libparallel-client.so etc/ssl/certs/ca-certificates.crt I'm not sure those files are even on the cache drives, are they?

I swapped the RAM sticks, again, just to make sure I wasn't crazy. Corruption Errors started almost immediately after starting Unraid. This is how it happens every time. It's fine for a while, then they slowly start happening. And they get faster and more frequent until something gets really corrupt like my docker image. Then I have to format the drives completely and start the process all over. Another interesting thing I've noticed is that the errors seem to double on one of the drives. For instance, here's my current dev stats output. It shows 4 errors on nvme0 and 8 on nvme1. It's not always double but it often is, or close to it. [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 8 [/dev/nvme1n1p1].generation_errs 0 [/dev/nvme0n1p1].write_io_errs 0 [/dev/nvme0n1p1].read_io_errs 0 [/dev/nvme0n1p1].flush_io_errs 0 [/dev/nvme0n1p1].corruption_errs 4 [/dev/nvme0n1p1].generation_errs 0

Yup, I did that. I pass the -z flag every time I run it.

Yup. As the text you quoted says, "I've disabled all overclocks".

Okay, ran with one DIMM for a while without any issue. Switched to the other DIMM, no issue for about 2 weeks. Then, tonight, I started getting corruption errors again. So I figured the DIMM was bad, swapped back to the "good" DIMM, and I'm still getting errors. So now I'm not sure what's going on. Bad mobo?