_0m0t3ur

Happy Birthday! Cheers!

thank you for offering your input. i appreciate this. i always update all sas controllers to the latest (20.00.07.00) firmware before running in my server. the cables are new. still problems with this disk as an UD. but i am currently preclearing this disk. did a full read of the disk and now at 20% zeroing without any hardware change. update: the disk pre-cleared without issues. but i did double check the firmware on my two LSI SAS HBA's. the 8i was updated to the latest (20.00.07.00) but the 16e was not (20.00.06.00). my bad. not sure how i missed that. but thank you again to @JorgeB for their post.

test copied 50 gigs to this disk. errored out.

changed the UUID in UD. and did a little bit of reading up on this. post if more issues. thank you.

how can i figure out what is causing the mount points to duplicate? i just deleted the mount point and reformatted the disk. the same mount point returns.

the drive is running off a 9201-16e via sas-to-sata breakout cables. prior to this issue never had a problem. a bunch of drives running off this controller now without any problems. for some reason this drive in UD is a problem. drive itself passes smart tests.

this disk continues to be a problem in UD. ever since this issue, i cannot use this disk in UD. it appears fine, then i copy files to it. the disk then drops out, in, out, in, out, etc. then some kind of error. here is one i got today.

no, i did not enter a "?" mark in the mount point. a physical disk. so, the "?unassigned_disk4" mount point does not show up in the UD. it is the one i changed. new is in circled in red above. but i can see old one when navigating (/mnt/disks/) Krusader or MC. but cannot delete it due to permissions. was going to change permissions, then delete but wanted to get your input first.

i changed the mount point of an unassigned disk. noticed that the old mount point with a "?" mark in front of it is showing when browsing MC and when browsing Krusader. how to get rid of this? thanks.

testing privoxy in this docker was getting dns different than endpoint using wireguard. found these pia nextgen gen custom dns here. edited container, adding 10.0.0.242 as first dns. now dns leak test shows dns matching endpoint.

need to add a host path to this container. here's an example: otherwise everything else as default. works just fine. thanks to the linuxserver.io team for another excellent container.

try googling that error.

Steps 1-3 in this post should do it. (double check in the edit menu of SAB container that "privileged" is toggled "on.") binhex also explains here in Q21.

1. click on SABnzbdvpn edit. 2. double check pia user name/pasword used. must be the same credentials you use to login to pia web account. 3. double check that the lan network is correct: xx.xx.xx.0/24. (saw your logs show /24 lan. just make sure you are using the right local ip.) 4. strict port forwarding: yes 5. privoxy: yes (some have reported issues with privoxy off and no access. this should be fixed but worth trying, since yours is off.) 6. click apply. Lastly, consider switching from OVPN to Wireguard. I started having problems with OVPN on PIA. switched to Wireguard, all resolved. If you want to try, here's a post showing how:

try nzbhydra2. indexers go inside nzbhydra2. then *arrs only see one indexer, namely nzbhydra2. lots of graphs, etc. in nzbhydra2.

it's all i've ever run and never have had any issues. like the idea of obfuscated the indexer side.

i would go over all your container variables, including the network variable. comb the logs.

seems like SAB should be running. in mine after this is indication that privoxy is running. are you running privoxy? also have you cleared your browser cache? and then restarted your entire *arr's stack?

you're looking at your "edit" screen in advanced mode, that's why you're seeing the "default value" field. it doesn't matter. are you seeing "AUTH FAILED" in your logs? also, are you using your main username and password in SAB that you would use to login to the PIA website? that's the one you want to use.

try switching to wireguard. 1. Right click "Edit" the SABnzbdvpn container. 2. Add "variable" with the following information. 3. Click apply to pulldown the container change. The default PIA endpoint for this container is the Netherlands. You can also pick any other end point from here. 4. When changing endpoints, shutdown SAB. 5. Navigate to your /appdata/binhex-sabnzbdvpn/wireguard/wg0.conf . 6. Open "wg0.conf" in a text editor, like Atom, the open source text editor. 7. Change underlined part below to the appropriate endpoint from the link above based on country/location. 8. Click "Save" in your text editor. 9. Restart SAB.

have you switched to using the PIA Nextgen? look here starting with #19.

thanks mate.

excellent. glad you got it working.

i believe you need a leading / . so "/Downloads/incomplete" not "Downloads/incomplete". also, "/Downloads/complete".

posting the solution might help someone else.