wall1s

Well I was able to solve my previous problem. But I still am unable to access plex media at all when I have tailscale set up how I am led to believe it should be.

Hmm well this might explain some things. Is there something you need to predefine in the policy file that I might have missed?

Hey everyone I'm trying to get Plex to go over tailscale via a digital ocean exit node so that my users can access it without having to get the tailscale app. I feel like I have things set up correctly with my exit node. Or at least the tailscale dashboard makes me think so. and I have things set up in the unraid plugin dashboard. But when I try to tell it which exit node to use everything falls apart and I cant access unraid without removing it directly on the unraid server. (no more over network). I've attached a few screengrabs showing that tailscale does see the exit node. And what my "this device" page in the plugin says. I feel like I'm supposed to be able to choose my exit node there. But maybe not? Thanks

minor update I am able to get a static ip.. but it looks like I'm limited to 100 mbits and its $13 a month. which... considering I have fiber isnt great. I am digging more into this. But I would really like a alternative solution.

Hello everyone, I recently moved around the world and my new ISP utilizes CGNAT. This has causes my Plex (docker) to think its in relay mode and limits speeds to 2 mbps for my users. I was hoping to find a way to solve this problem? I've seen people mention tailscale or zerotier before but those require my users (some of whom are 90) to use their respective app along side plex and I just dont think that is going to happen. Especially for those who use the plex app on a TV. So I was hoping to find a solution entirely on my side of things. I have reached out to my ISP for getting a static IP but German customer service is legendary for how... well sometimes it exists. So any ideas?

Ok! was dumb and didnt notice. And it failed again after like 37%. The error I get without -n is: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

Sorry for the long wait. This time the parity sync made it to ~35% before the shares disappeared. Adding the new diag file also. tower-diagnostics-20240501-1903.zip

disk 1 .txt Here is the output from it.

Hello all! I'm in the middle of upgrading my parity drives so that I can pare down my total number of drives and get off a USB based JBOD. But for some reason after a few hours of parity sync my shares disappear. A reboot solves this problem but I only make it 14-16% of the way through a sync so it never finishes. Any idea what could be causing it? tower-diagnostics-20240430-2347.zip

Ok, I built a new config, kept the parity drive in my jbod (going to work on moving off asap), and I'm currently doing a no-write parity check. Everything SEEMS to be functioning. Even the data in disk7 seems to be there. And accessible. So take aways get the fuck off jbod usb is bad. and replace drive 1 asap.

Well I have moved one disk out, specifically the 14tb parity disk. However now the system isnt seeing it at all. And currently I am unable to move the other 4 disks out. Gonna have to buy a new sata expansion card. and trays. *edit* Ok moved the parity drive back into the JBOD and I can see it again. It still is listed as disabled but at least I can see it again.

Well... so what do you think my option is at this point? It sounds like you're saying I'm boned.

I dont think I have anything irreplaceable on them. Its like 75% plex. And everything should be covered by parity.

Just reran diag! tower-diagnostics-20240325-1054.zip

Well that is a lot of corruptions for a disk that SMART is telling me is healthy.