June 4Jun 4 Community Expert 5 hours ago, photodyer said:Ack, came back and found my error, typed -p not pSorry about that, typo, corrcted it in case someone else finds this in thefuture.5 hours ago, photodyer said:Rebooted, ran diagnostics, attachedOK, disk1 is now showing the correct size; you can now recreate the partition again to use the full capacity.On 6/1/2026 at 3:20 PM, JorgeB said:sgdisk -o -a 8 -n 1:32K:0 /dev/sdbReboot the server. Disk1 should then show as "wrong." Go to Tools - New Config - Keep All - Apply.Back on main check that all disks are assigned as before but with a blue icon, check "parity is already valid", start the array and post new diags.
June 4Jun 4 Author 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
June 4Jun 4 Community Expert Disk1 mounted, and the issue should be resolved.As for Docker, it looks like the original image was on disk1, so when that disk stopped mounting, a new one was created in the pool , which is the better place for that. Assuming appdata is all there, and it should be, you should be able to just restore the apps:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applicationsAlso see below if you have any custom docker networks:https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networksIf all looks good, you can then delete the old docker image from disk1
June 4Jun 4 Author 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.
June 4Jun 4 Author Plex migration still running, Cache is showing errors. And the number of errors is increasing.
June 5Jun 5 Author 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:
June 5Jun 5 Author Memtest v6.2 running as directed. Is it a finite test or do I need to stop it at some point?
June 5Jun 5 Author Crap...it's throwing errors. I assume stop and try reseating/checking connections as a first step then run again?
June 5Jun 5 Author 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.
June 6Jun 6 Community Expert Scrub the pool and if there aren't any uncorrectable errors, reset the stats and keep monitoring; if more errors show up, there's still a problem.
June 6Jun 6 Author 7 hours ago, JorgeB said:Scrub the pool and if there aren't any uncorrectable errors, reset the stats and keep monitoring; if more errors show up, there's still a problem.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.
June 7Jun 7 Community Expert Look in the syslog for name of the corrupt file after the scrub, that file should be deleted, restore from a backup, then scrub again and confirm 0 errors.
June 7Jun 7 Author 6 hours ago, JorgeB said:Look in the syslog for name of the corrupt file after the scrub, that file should be deleted, restore from a backup, then scrub again and confirm 0 errors.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.
June 8Jun 8 Author 3 hours ago, JorgeB said:You can now reset the pool stats, then monitor for any new errors.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.
June 8Jun 8 Author 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
June 8Jun 8 Community Expert Diags look good so far, no issues that I can see, and thanks for the donation! Much appreciated.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.