So I've recently been having trouble with my plex server. For context it works for maybe a few hours then it refuses to load any content, along with docker has become more or less unresponsive and has started to give me "Execution Errors" when starting and stopping containers. Because of these issues, I have started to look at the syslogs, and I've noticed an alarming amount of red in the syslogs. I don't know if this is anything to worry about or if I need to run to microcenter and grab a new cache drive. For the people who will ask, I will attach the Diagnostics file.

unraid-diagnostics-20260805-2317.zip

Also I should note, for what its worth I have also asked the wizards of reddit, from the r/unRAID subreddit to help me in my time of stupidity, and clueless-ness. Here is the link to that post.

btrfs is detecting a lot of data corruption. Start by correcting the RAM speeds, since they are currently running overclocked; also, good to run memtest

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

As far as I'm aware I haven't overclocked the ram at all. I just set them at the XMP speeds. If thats bad then sure I can revert it, just seems like a silly issue.

16 minutes ago, bungle said:

I just set them at the XMP speeds

XMP Is an over clock.

I have possibly a stupid question, if you peeps don't mind me asking, why would having the ram be faster, be an issue here. I will revert it, if that's believed to be the issue along with running a memtest, but I'm just a bit lost on why the ram being faster is causing my cache drive to error out.

3 hours ago, bungle said:

I have possibly a stupid question, if you peeps don't mind me asking, why would having the ram be faster, be an issue here. I will revert it, if that's believed to be the issue along with running a memtest, but I'm just a bit lost on why the ram being faster is causing my cache drive to error out.

Instability basically - unstable ram

Fair enough, I'll run a memtest here soon and let you guys know what the result is.

8 hours ago, bungle said:

That's highly unfortunate. RAM no good.

If you have multiple sticks, test each stick (can do it in a different machine) and continue to use the good stick if one is still viable.

I might get around to testing the sticks one by one, but I have a question. So does the ram is bad cause the cache drive to start to error out, or do I have two device(s) to fix?

7 minutes ago, bungle said:

So does the ram is bad cause the cache drive to start to error out

There's nothing so far suggesting a device problem so far, btrfs was detecting data corruption, that's it, and of course, Docker, etc., would also be affected since the filesystem went read-only and the Docker image is there.

Okay, just to make sure I'm understanding. The ram is more or less causing my issue so if that gets fixed the rest of the issues should vanish or at least self correct? Sorry to sound incompetent but I'm trying to understand and not have to spend facebook marketplace shitbox Honda civic money to fix a issue.

36 minutes ago, bungle said:

Okay, just to make sure I'm understanding. The ram is more or less causing my issue so if that gets fixed the rest of the issues should vanish or at least self correct? Sorry to sound incompetent but I'm trying to understand and not have to spend facebook marketplace shitbox Honda civic money to fix a issue.

Considering everything including the OS is running from RAM, yes.

Everything from crashes to data corruption happens because of bad RAM.

Edited August 7Aug 7 by MowMdown

After resolving the RAM issue, you should scrub the pool to see if any errors are found, and then reset the stats, if there are uncorrectable errors, any listed files should be deleted/restored from a backup; probably also a good idea to recreate the docker image. There can also have other corrupted data in the array, but XFS can't detect that, so not much you can do unless there are preexisting checksums for all the files.

Appreciate the help, Sorry for asking tons of questions, just wanted to make sure I know what to fix and where it went wrong.