trurl

That all looks reasonable so far and only using 15% of docker.img Post docker run for plex

Attach Diagnostics ZIP to your NEXT post in this thread.

Constant RPM, shorter tracks, less data per revolution. And as I always say, each additional drive is an additional point of failure.

Most of what I have said about your configuration has been that way since the earliest days of Unraid. You have been on the forum several years longer than I have. It has always worked just like that.

I don't recommend sharing drives or pools on the network. If you mix user shares and drives/pools when moving/copying, you can lose data. If you really need to, you can work directly with files and folders on drives/pools using the builtin File Manager. It won't let you make the mistake of mixing user shares and drives/pools.

When Unraid boots from flash (or from boot partition on 7.3+ if you have that setup), it unpacks the OS fresh from archives, into RAM, and the OS runs complettely in RAM. Think of it as firmware. When the OS has finished loading, it gets ALL settings made in your webUI from that config folder and reapplies them to that fresh OS. That is your configuration. Any setting made in the webUI is saved there so it can be reapplied at boot. If it is in the webUI, it is in your configuration in the config folder. Your disk assignments, your plugins, your docker templates, the settings you have made for each of your user shares, things on the Settings page, etc. If it is something you have configured in the webUI, it is in the config folder. Most of the files in config are simple text files and if you examine them, you can get some idea how they correspond to settings in the webUI. If you lose some or all of your configuration from that config folder, Unraid does not remember it. Simple as that.

Sorry, the backups in your screenshot are the appdata backups. Those are intended to restore your appdata using the plugin. Not clear if you also have appdata backup plugin saving flash backups, and if so, where you told it to save them.

That looks like you were relying on Appdata Backup plugin to store the backup of your configuration. Keeping a backup needed for starting your system on that same system isn't the best plan. Unraid Connect will keep a backup of your configuration on Unraid Cloud. You can use the config folder from that backup to overwrite the config folder on flash and you will have a configuration as current as that backup. When I say "configuration" I mean all settings from the webUI. None of your storage has your configuration (unless you go to Internal Boot with a boot partition on your storage). Your storage just has your data. Some of that data is your appdata, but the docker templates needed to work with your dockers in the webUI are part of your configuration in the config folder on flash.

Assuming you haven't made any changes to disk assignments since those diagnostics. Unmount them in UD or you won't be able to assign them. Parity should be valid after you assign the disks, you can check the Parity Valid box before starting the array and it won't rebuild parity. Probably a good idea to do a correcting parity check anyway.

Diagnostics you posted in January had these drive assignments (disk0 is parity): Jan 11 16:12:21 TerraFirma kernel: md: import disk0: (sdi) WDC_WD120EFBX-68B0EN0_D7HEJ0JN size: 11718885324 Jan 11 16:12:21 TerraFirma kernel: md: import disk1: (sdh) ST12000NT001-3MD101_ZZ007GMK size: 11718885324 Jan 11 16:12:21 TerraFirma kernel: md: import disk2: (sdg) WDC_WD60EFAX-68SHWN0_WD-WX62D30RDFXX size: 5860522532 Jan 11 16:12:21 TerraFirma kernel: md: import disk3: (sdf) ST12000NT001-3MD101_ZZ3079WK size: 11718885324 Jan 11 16:12:21 TerraFirma kernel: md: import disk4: (sdc) WDC_WD120EFBX-68B0EN0_D7HEVYVN size: 11718885324 Jan 11 16:12:21 TerraFirma kernel: md: import disk5: (sde) WDC_WD40EFZX-68AWUN0_WD-WX72D221Y1N9 size: 3907018532 Jan 11 16:12:21 TerraFirma emhttpd: import 30 pool device: (nvme0n1) T-FORCE_TM8FP7001T_TPBF2308150010101219

We still don't know that. Why are those replaced drives attached?

Actually, UD seems to be saying it has recognized the filesystem on all disks except the one that has the greyed out MOUNT button.

Click on the gears icon under Settings for each drive. You really only need to check if the 12TB are mountable since the smaller drives cannot have been parity.

Can you mount the other drives (read-only)?

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/array-health-and-maintenance/#reset-the-array-configuration

Don't assume. Unraid only knows what your old backup said. It hasn't recognized anything. It won't even try to recognize anything until you start the array. If your old backup had a drive assigned as parity, and you later assigned a different disk as parity then reused that (former parity) disk as a data drive, then Unraid will have assigned that data disk as parity if that is what your old backup had.

Since you didn't have a current backup with your current disk assignments, you will have to New Config and assign your disks. Then it will rebuild parity instead of clearing any data disks. You must be very certain of your parity assignments. If you accidentally assign any data disk to any parity slot, it will be overwritten with parity. If you aren't absolutely certain of your parity disks

If it is a current backup, just copy the config folder from it to your new flash drive, then you will have all of your configuration including your disk assignments and the license (which will need to be transferred to the new flash as mentioned).

On the Docker page, click Container Size button at bottom and post the results, along with new diagnostics.

The webUI and Previous Apps relies on templates for your containers, and those are saved on flash. If you have flash problems that make these templates unavailable, the webUI and Previous Apps has nothing to work with. Installed plugins are also on flash, along with all settings from the webUI, such as your drive assignments. Server name reverting to default "tower" is often a sign of flash problems. Internal boot from a partition on one of your storage pools instead of flash drive is also an option in Unraid 7.3 and above. In that case, your templates and other settings would be kept on that boot partition. Still a good idea to have a current backup of course.

Is plex the only container you have reinstalled so far?

Probably a misunderstanding about the difference between dockers and plugins.

If you can't get the db repaired you will have to replace plex appdata with a backup or delete plex appdata and start over.