JebusJones

Yes, with the docker version if you stop your array, then docker stops and so does your Tailscale docker, so you lose remote access - this caught me out a few times when I wasn't thinking and doing some remote management. With the plugin, Tailscale is up even if the array is stopped. I finally just got it all working so that when I use the Tailscale app on my phone I can access all my dockers via local IP wherever I am plus my NZB360 app that I use to manage my arrs also works with no need to add or change IP details of my docker containers. I ran into many issues like other people have on this thread and found that I: 1. Had to ensure my Tailscale docker wasn't set to autostart (obvious but I accidentally forgot this bit and I want to keep it around while I make sure Tailscale plugin all works, so I've just disabled it and set it not to auto start with the array, I'll remove it soonish). 2. I advertised my subnets and set exit node but local IP still didn't work from my phone - Tailscale IP did work as expected. I found I needed to reboot my Unraid machine to ensure this worked. Did this in the CLI of Unraid with this command: tailscale up --advertise-exit-node --accept-routes --advertise-routes=192.168.1.0/24 (replacing the IP with my own so it could be 192.168.100.0 if that was my internal network IP) - when I did that it said it needed to add some extra flags and gave me that full command which I then copy and pasted, something about disallowing DNS advertising I think? Then you log in to the Tailscale web admin console at login.tailscale.com and approve the route settings against the machine in the menu accessed via the three dots on the right hand side of the machine listing in the Machines tab (and I also turned off key expiry). 3. In the Unraid GUI I had to go to Settings -> Network Settings -> Interface Extra -> Include Listening Interfaces and ensure that tailscale1 was applied in that. 4. Under Settings -> Docker I had to ensure Host access to custom networks: was Enabled (I have all my dockers on a custom network). 5. I could then access my dockers but a lot of them thought I was outside the network and required logins. In the pinned comment on this thread it states that you should have the "Use Tailscale Subnets" feature turned off if you're experiencing issues with access, but once I turned that to ON I found that all local IP access worked and the Tailscale plugin now thinks my phone is on the local network and everything works as expected. That's found in Settings -> Network Services -> Tailscale -> Settings NOTE: this is what worked for me, it may be different for others and what they need it to do. Shout out to the great community on here.

Couldn't seem to find one anywhere, so I think I'm OK. Weirdly Plex and Sonarr seemed to not know about files that were clearly present, but refreshing shows that siad they had missing episodes seems to have fixed that. I'm also getting network drop offs but can see there is a fix for Realtek drivers so will try that now. I've also just ordered 3 new 18TB drives to complement the current 5 x 8TB. Have been meaning to upgrade the drives for a while so I guess this is the kick in the butt I needed to get that process started. Hopefully by the time they've arrived things have settled down so the parity drive move (8TB to 18TB) and adding in two new 18TB drives goes well. Thanks for the help everyone.

OK, that was a lot faster than I thought. That seems to have fixed it. Really appreciate the help guys, apologies for my grumpiness, ambiguity in tech writing is a personal bugbear of mine.

Yeah I'm doing the -L option now. Fingers crossed.

*sigh* My grumpiness has once again gotten in the way of me receiving any sort of help hasn't it? You'd think I'd have learnt to keep my mouth shut by now.

Thanks for the fast reply, it really is greatly appreciated despite my hungover comments below, I'm doing that now. As I've found with some of the Unraid documentatrion, what you linked to appears tyo have been written by or collated by someone who assumes previous knowledge. As someone who writes complex tech instructions for laymen on the regular, this irks the hell out of me: Make sure that you have the array started in the correct mode. If necessary stop the array and restart in the correct mode by clicking/unclicking the Maintenance Mode checkbox next to the Start button. That says a whole lot of nothing right there. Oh God, then I kept reading and it got worse. I paid for this product but I'm pretty sure that page was written by a teenager. I shouldn't complain, I should be grateful that you replied and that there is documentation at all. Sorry, just being a grmpy old man. OK I guess my whining took long enough to type that the check finished, results below:... nope, copy and paste removed formatting. Attached as an image instead. The salient point seems to be: invalid start block 3638442754 in record 232 of cnt btree block 3/6

I've been having some weird issues lately. Files not transferring from Deluge to the array, Deluge container saying it wasn't connected (thought it was a dead .conf file but it wasn't) Plex "recently added" Movies showing what was added weeks ago (but the films added since still being present), whole server being on but unreachable and had to hard reboot, and now an unmountable drive. I thought maybe the docker image was corrupt so wiped that and rebuilt my containers, but after that I got the unmountablke drive message. I've had a dead drive before, but not this message. I've searched through the forums and tried some fixes (xfs repair) but before I go wiping or replacing drives, I was hoping someone here could point out the actual fault? Maybe with all the odd things going on my USB or cache drive is actually dying? Recent changes to the system: added a SAS/SATA card (which worked perfectly), and updated to 6.12.6. jebus-nas-diagnostics-20231230-1043.zip