Michael_P

Yes - set shares living on your cache drive to 'Yes', disable docker and the VM manager so their files can be moved too, then run mover to move everything to the array. When it's empty, remove the drives from the cache slots, start the array, stop again and add your new drive to the cache slot. The online manual is pretty detailed, you should check it for anything I've missed - but I just upgraded my cache drive this morning and that's pretty much the gist of it.

Everything is in RAM which is why it's lost on reboot. You can set up the syslog server in Settings to mirror to flash if you need to

try writing 30 gigs to it

Let me know when the 11 branch reaches stable

When is your Plex media scan set to kick off?

Also, eliminate any splitters and don't hang all the drives off of one line back to the power supply

If they're blocking it at DNS, Plex still does the authentication so there's that

First- don't piss off the work IT guy Second- I hope you don't have Unraid exposed to the internet As for the service ports, just use a port that's accessible and have your router/firewall re-direct it to your service's port

Plex transcoding to RAM?

My beef with them is for how they handled the pivot from Media Browser to Emby. For the uninitiated, Media Browser was a plugin for Windows Media Center that was a front end for any content you had locally (or on the LAN), I used it for accessing my Music Video and Concert content along with My Movies for movies and TV. Media Browser had theme support, and I found 1 that suited my need to browse my content perfectly - it was literally the ONLY ONE that showed it the way I wanted. Worked great until one day the devs decided they were moving to a monetized model and re-named it Emby, Media Browser updated automatically, without asking, and boom, now the 1 theme I used was now behind a paywall.... I'm not a cheapskate, if it was a paid theme from the get-go I would have paid for it (their "store" offered paid themes, too). But to pull the rug out from under me, well I'm petty and don't forget these kinds of things.

I should have been clearer about them both being pretty much the same as far as self-hosting. Still wouldn't touch Emby with a 20' pole

Jellyfin is really just "free" Emby, so there's that. Security practices don't change, it's still a self-hosted server after all (Plex is too...) FWIW, I block all of Emby's sites at my firewall for the way they pivoted Media Browser to monitize Emby, still salty about that

https://trueconf.com/blog/knowledge-base/how-to-run-trueconf-server-in-a-docker-container.html

Unless your drives are parked next to a magnetron or nestled up on the space station, I'd check all of your connections and if the controller has gone wonky. Pop the drives into another PC and run a SMART test to see if it's really the drives

Not Plex then, prolly crashplan

Split-tunnel VPN is your huckleberry

When is your Plex scheduled tasks set to kick off?

Yeah, that's not a probably, that's a definitely. You're operating those drives at close to their Tmax and they really don't like that. It can operate at up to 60c, but that's not the optimal range for performance and, most importantly, longevity. Not surprised it just keeled over out of the blue rather than gracefully.

Yep

You don't have to, you can mount a remote share any way you like

Change your CMOS battery on the mobo

Are you running a pihole or pfblockerng on your network?

I think "high stakes risk" is a little overblown, but if you're hosting your own services you should be fairly familiar with those services and the ports you're exposing - having Cloudflare pointing at your IP doesn't change that. You need to add a CNAME, or A record in your DNS in your godaddy panel if your domain isn't already pointed at your server. I created a sub domain pointed at my home server (the A record), and then use CNAMEs that point to that subdomain for any services I want to self host, and my domain and websites remain pointed at my webhost.

This, you'll need to image the drive