CyrusD

Turns out it was tailscale that broke it. I've been running tailscale since unraid introduced it and never had a problem so I had no reason to suspect this was the issue. I had to add the tailscale network to the LAN_NETWORK. Holy crap I'm so happy this is fixed. Took me 2 weeks to track this down lol. Anyway, thanks for your help.

Unraid is version 7.2.0

OK I corrected that, using Austria now. The UI now loads. HOWEVER! I'm still having issues loading up my other docker containers that use the qBittorrent container VPN. 3 of the 4 do not load. For some reason my 4k instance of radarr will load and seems to work fine. It is using ghcr.io/hotio/radarr repository. My 1080p radarr instance that is not working is using ghcr.io/linuxserver/radarr:latest. Also sonarr and firefox are using linuxserver repositories. Not sure if any of that matters but that's the only difference I can find. I didn't change any configuration other than drop in new PIA cert for Austria and updated the qbittorent docker image to the latest.supervisord.log New supervisord.log file attached. Thank you for the help so far! Side note: I did test the 1080p radarr docker by removing the extra parameter "--net=container:qBittorentVPN" and setting the network to bridge, this worked. I was able to load the UI. So this makes me believe something isn't right with the VPN still.

Howdy, After an update I'm having some issues getting the web UI to load and none of my other docker containers that use the VPN are loading. It seems there's a problem with a table value ID of some sort in the logs. I did run the commands on Q1 of the github documentation to force ip table mangle at it says and rebooted the entire server but I'm still having issues. Thank you for the help. Docker run supervisord.log

I just wanted to update this thread in case anyone came across it when searching. I ran into way more problems than I originally reported on. After a reboot the server wouldn't even make it past POST. I thought maybe the memory had went bad. Went through troubleshooting all 8 sticks with not much success. It did boot once and I found roughly 4 drives were not showing up. BAD HBA! LSI 9210-8i wasn't even warm. Tried different pci slots, still nothing. Removed the card, moved drives to second LSI card and attempted booting, still no POST after many attempts. Eventually just transferred all hard drives (12 of them total) and the second LSI card to my old desktop hardware/tower. Works fine now. I ended up losing at least a LSI 9210-8i, one hard drive, a S2600CP motherboard, not sure on memory sticks or other hardware. Power is provided by a UPS and we didn't have any power events recently so I'm not really sure what happened. So far I have not lost any data, currently in a data rebuild process. Moving to new hardware was painless as I learned unraid is hardware agnostic. I did have one hard drive go disabled along with the one that failed, luckily I have two parity drives. Hopefully nothing else fails while the data rebuild is happening. New LSI 9305-16i with cables is on order along with a few new 18tb drives.

Hi there, hoping to get some direction on an issue I'm having. I've had the server unexpectedly reboot twice in the last 5 days. I checked the logs and I am seeing a constant message; Dec 17 17:31:14 Tower kernel: ata1: SATA link down (SStatus 0 SControl 310) Dec 17 17:31:15 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps I guess I don't know what to make of this. I assume there's a bad sata cable or something? None of my drives are showing CRC errors or any other smart errors according to the dashboard or scrutiny. Any help would be appreciated, thanks. tower-diagnostics-20241217-1721.zip

tower-diagnostics-20230924-1352.zip Hi there, So one of the SSDs in my cache pool has been throwing CRC errors for a couple of weeks. I ordered two brand new 1TB SSDs to replace my current 250gb setup. The same day the new drives arrived the cache pool went "Unmountable: unsupported or no file system". So now I don't know if I can salvage the data off the non-failing cache drive or if I have to resort to a backup. I do have backups of the whole app data folder and the docker.img which are only a couple of days old. Not entirely sure of the steps to proceed either way. Not sure which way to proceed. Attached is the diagnositcs. Thank you for the help. [EDIT] I did find another similar thread and found the command btrfs rescue zero-log /dev/sdj1 Which did run and I was allowed to mount my remaining cache drive. It seems there still might be some errors though. End goal is to upgrade to 2x 1tb ssd and remove both old drives from service.