So we have had a few power outage and even with a UPS seems like i got a issue sadly.

And noticed after i started unraid up again that docker containers started and suddenly stopped and was gone. and appdata was also gone. so took a restart and then when booted back up the cache drive was "Unmountable: wrong or no file system"

So would love some assistance if this is fixable ?

have added the diagnostics file.

thor-diagnostics-20260220-1236.zip

Edited February 20Feb 20 by CrazyLordy

There's a problem with the log, type

btrfs rescue zero-log /dev/nvme0n1p1

Then restart the array and post new diags.

Here is the new diags after doing what you requested.

thor-diagnostics-20260220-1401.zip

42 minutes ago, CrazyLordy said:

So we have had a few power outage and even with a UPS seems like i got a issue sadly.

have you made sure that your UPS settings are such that Unraid tries to attempt a tidy shutdown after a few minutes without power? You do not want the UPS to ever have insufficient stored power left to allow for a tidy shutdown.

Just now, itimpi said:

have you made sure that your UPS settings are such that Unraid tries to attempt a tidy shutdown after a few minutes without power? You do not want the UPS to ever have insufficient stored power left to allow for a tidy shutdown.

i have tried to do so. but maybe i havnt done a good enough job ? i saw a doc file just now about etch container should atleast have 10-20 sec to do a clean shutdown or something ?

8 minutes ago, JorgeB said:

There's a problem with the log, type

btrfs rescue zero-log /dev/nvme0n1p1

Then restart the array and post new diags.

after that command i could also see the appdata content . but still no dockers.

1 minute ago, CrazyLordy said:

i have tried to do so. but maybe i havnt done a good enough job ? i saw a doc file just now about etch container should atleast have 10-20 sec to do a clean shutdown or something ?

Two things— First, determine the time required to stop the Array using the button on the MAIN tab. Then make sure that this setting is long enough to allow for the array to be stopped.

Second. Think about your UPS for a minute. Realize that it has enough energy stored to run your server fro twenty minutes to, perhaps, an hour. It will take a minimum of eight hours to recharge that battery if you run it to almost fully discharge. Now, think about your power interruptions. In my area, we have two kinds of interruptions. One is the power company maintenance ones. They last less than ten seconds. Then there are all the other types. They last for a couple of hours at a minimum. I have set my UPS to only run thirty seconds on battery before requesting that the server be shut down.

Remember that the "Time on battery before shutdown (seconds):" parameter only starts the shutdown. It can take several minutes after that you actually get your server shutdown cleanly. (Part of this time is flushing all the cached writes from RAM onto the physical media where it is safe.) I f you are like most of us, after power restoration, you want to get the server back on-line ASAP. Remember that the battery is now partially discharged and it will be several hours before recovery to a fully charged state. You want it to have enough reserve to be able to handle a second outage.

Edited February 20Feb 20 by Frank1940
Removed extra screen capture...

23 minutes ago, CrazyLordy said:

i have tried to do so. but maybe i havnt done a good enough job ? i saw a doc file just now about etch container should atleast have 10-20 sec to do a clean shutdown or something ?

You time how long it takes to stop the array tidily by pressing the Stop button in the webGUI and then provide for a margin above that. There ae separate timer settings available for closing VMs, all docker containers, and then stopping the array. so make sure they are all large enough.

Thank You guys. That's some great tips. i will give does a test. now that i can see my appdata content again after the command from JorgeB . is it safe to just reinstall the dockers ?

Did check system docker / docker.img and it looks like this

Edited February 20Feb 20 by CrazyLordy

The Docker image is new, so possibly there are two now. You can delete the new one, or just uninstall the apps from CA.

Btrfs is detecting some data corruption on the pool, that's unrelated to the unclean shutdown, Ryzen with overclocked RAM like you have is known to cause that, so I recommend correcting it.

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