trurl

Yes

The docker templates on flash are at config/plugins/dockerMan/templates-user. These store the settings from the Unraid webUI for each container when it was created/edited. appdata stores the working data for each container, such as settings made within the application, and other things the application needs to know about. With the templates and appdata you can easily reinstall your dockers just as they were from Previous Apps on the Apps page.

Doesn't look like you have any assigned storage so no place for libvirt

Maybe UFS Explorer can recover something

Emulated disk8 is mounted but empty.

That certainly has not been the experience of many. Plenty of threads on this forum about these problems. That is why the programmers have provided another method.

Any changes in the webUI (configuration) are written to flash so they can be reapplied at boot, Seems that recent flash drives are hit-or-miss. A whole thread about that here:

After we figure this out I recommend you put logspace back to its normal size. 8G is not a fix.

What do you get from command line with this? ls -lah /var/log

Since you had bad RAM your data is somewhat suspect. You might consider check filesystem all around and a parity check. No parity?

https://docs.unraid.net/unraid-os/release-notes/7.3.0/#onboarding-and-internal-boot https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/deploy-and-configure-unraid-os/#onboarding https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/internal-boot-faq/ https://docs.unraid.net/unraid-os/troubleshooting/tpm-licensing-faq/

Empty the cache pool by moving everything off, so it can be repartitioned and reformatted. You would have a mirrored boot partition and another mirrored partition as cache.

This thread might as well belong to you since OP abandoned it.

Worth a try.

You can quit when it gets even a single error, or let it run overnight.

So you didn't actually follow the instructions.

Post a screenshot of your Syslog Server settings.

I wouldn't count on Mover Tuning for this. Either remove it or use File Manager.

You should never put off running memtest. You must do it immediately! You must never attempt to run any computer unless RAM is working perfectly. Everything goes through RAM. The OS and other executable code. Your DATA!. EVERYTHING! The CPU can't do anything with anything until it is loaded into RAM.

Now that we have that syslog, can you reboot and get us diagnostics while still able to access webUI?

Then... All 3 disks are mounted, disk3 is empty which I assume is expected. Might be a good idea to check filesystem on disk1 anyway. docker.img still showing the corruption it already had. Delete, recreate, reinstall Previous Apps. https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/ Might also be a good idea to do a parity check. Do you intend to have cache or other pool outside the parity array? It can have some benefits with docker even if you don't use it for caching.

Changing the flash device | Unraid DocsThe USB flash device is critical to your Unraid server as it stores the operating system, configuration files, and license. If this device fails or becomes unreliable, prompt replacement is essential

Fix Common Problems plugin puts warnings in syslog and also notifies of problems. It does not cause the problem it is warning about.

correct