Michael_P

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

both of these? raw.githubusercontent.com githubusercontent.com

Sure, you can spin up a Windows VM using your OS SSD, attach your SSD and RAID pool disks to the VM then transfer over the virtual network interface to Unraid's pool. Little fiddly but totally doable

I didn't say anything about using unraid to host it

Are you exceeding its capacity?

Just make sure it's less than the amount you have free

32GB, limited Plex to 4GB - can confirm that works and the scheduled task no longer runs the server OOM.

That's what's running you OOM. Mine started doing it after upgrading from 6.8.3 to 6.10.3, haven't figured out why yet, likely doesn't like a media file for some reason when it generates thumbs and runs away. Doesn't do it if you change all of these to never You can change it to whatever you want when you add media, just make sure to disable them again before the scheduled task. I set a memory limit based on @Squid's suggestion above, going to test tonight to see if it runs away again.

In HA, the modem should only see the virtual interface

What time is your Plex scheduled tasks set to run?

Hello, after upgrading from 6.8.3 to 6.10.3 I have been getting OOM errors every night around midnight and the system kills a random process, the first night it was my W10 VM and last night it was Plex. Can anyone shed some light as to why? Memory usage is only in the neighborhood of ~50%. I hate to be "That Guy", but it's been running fine for years under 6.8.3 so I can't imagine what would be causing it to go OOM now. It seems to happen right after sending the nightly status email. urserver-diagnostics-20220622-0505.zip

A good backup routine is a better use of resources. If you were to ever encounter one of these edge of edge case errors, just diff the backup against live data.

In such a scenario, where the parity does not match and produces an error, and you have checksums of your data that match, then there is no error in your data and a "bit flip" in an "empty" portion of the drive would not be an issue. You'd simply rebuild parity as you already know that your data is intact (via the checksum verification).

The drive showing signs of failure isn't new, it's got 44k power on hours, I'd replace it if I were you if it's still needed

Just do one at a time if uptime is your primary goal, "protection" would be just limited to 1 disk failure

Are you running a pihole or pfblockerng on your network for DNS?

If the system is sending corrupted data, the age of the SSDs is irrelevant

If bad memory is corrupting your data, changing file systems won't stop the corruption - it'll just stop telling you about it.