photodyer

No errors spawning. Rebooted, server came back up clean. Attaching diagnostics, but looks like back on stable ground. Now, I just need to devote some serious time to upgrading, reconfiguring, and in general learning to better manage this beast. Jorge...Thanks aren't enough. You rock and this community rocks. I'm sure I will be back as I start the journey in earnest! Best to you, Jerry Trapp tower-diagnostics-20260608-0902.zip

I reset the pool stats after the clear scrub, about the time of my last post. No new errors, at least up until I left for work 10 hours ago.

Found the source of this particular problem...again my error. I reinstalled the wrong Plex. Realized that when I saw the last action on the offending app was years ago, went back and found the correct one and it installed and worked right away. The uncorrectable error was .db file in the wrong install. Uninstalled the wrong Plex, deleted the uncorrectable file. Scrub is now clean. Sorry...Flipping back and forth on nights I missed that until now.

Memtest ran all night on one pair, all passes. Booted up without issue. But then here things go sideways again. Ran scrub on pool...which comes back with 1 uncorrectable error.

Took the server down, dusted it out again, checked all cable connections, pull all ram sticks and reseated them in reverse order to get all sticks in new positions and channels. Went into BIOS and noted that under "DRAM Performance Control", "Performance Enhance" was set to "Turbo" by default; changed setting to "Standard" just to rule out another variable. Saved BIOS config and went back into memtest, was running better but still eventually started throwing errors. Stopped system, pulled and numbered DIMMS. 1 and 3 are now running in slots 0 & 2 and have PASSED first pool cycle and running still. Will stop this before I leave for work and start DIMMS 2 and 4 in the same slots, expect fail. So assuming server can run on single pair for now, should be able to move forward.

Crap...it's throwing errors. I assume stop and try reseating/checking connections as a first step then run again?

Memtest v6.2 running as directed. Is it a finite test or do I need to stop it at some point?

Not at all sure what's going on, but the CPU cores are redlining back forth working on something. Cache errors up to 3861. Plex still unable to open, same migration statement coming up. These are notifications from morning and evening:

New diag attached tower-diagnostics-20260604-1224.zip

Plex migration still running, Cache is showing errors. And the number of errors is increasing.

Followed first article. Had a little hiccup as there were multiple installs of "official" Plex listed and the last was evidently not the latest. Saw in log that it failed, and indeed that docker wasn't reinstalled. Went back in and did reinstall on the other Plex and it installed immediately. Can't check Plex yet as trying to open the WebUI gives "running data migration" code.

Command ran fine! Rebooted, Disk1 "wrong" as expected. New config, preserve ALL, apply. On main, all devices in proper assignments, blue dots present. Check "parity is already valid", Start array. Done. New diagnostics attached. tower-diagnostics-20260604-0714.zip

Rebooted, ran diagnostics, attached tower-diagnostics-20260603-2126.zip

Ack, came back and found my error, typed -p not p Will now reboot and run diag.

Ran the command as directed, but it states it failed (see snip). Did not reboot yet given the fail message.