I had a power outage on July 2nd and don't have my Unraid server connected to a UPS. The power came on for a few minutes, and shutdown again. My server was set to start up each time.

Looking at the logs, on July 4th, I see the following errors:

Jul 4 07:20:40 FBUNRAID kernel: pcieport 0000:00:1b.0: AER: Uncorrectable (Non-Fatal) error message received from 0000:02:00.0

Jul 4 07:20:40 FBUNRAID kernel: nvme 0000:02:00.0: PCIe Bus Error: severity=Uncorrectable (Non-Fatal), type=Transaction Layer, (Requester ID)

Jul 4 07:20:40 FBUNRAID kernel: nvme 0000:02:00.0: device [1179:011a] error status/mask=00004000/00000000

None of my docker containers came up and I've had to reinstall them from scratch. I found out that my NVME cache drive is unmountable. It's btrfs file system and it says "Unmountable: no file system". I've attached my diagnostics below. The errors are in the syslog-previous.txt.

What can I do to recover my containers or at least access the appdata on that drive?

fbunraid-diagnostics-20250704-1233.zip

No btrfs filesystem is being detected on the NVMe device, post the output from blkid

48 minutes ago, JorgeB said:

No btrfs filesystem is being detected on the NVMe device, post the output from blkid

root@FBUNRAID:~# blkid

/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2736-60C3" BLOCK_SIZE="512" TYPE="vfat"

/dev/md1p1: UUID="aca203d2-8a96-4dc8-ae8d-3223054725d0" BLOCK_SIZE="512" TYPE="xfs"

/dev/md2p1: UUID="1a50248f-0cc6-4052-ade3-0d33bda0b63a" BLOCK_SIZE="512" TYPE="xfs"

/dev/md3p1: UUID="6bca1659-d7ad-4ddc-bcf0-a18a8b9b19c6" BLOCK_SIZE="512" TYPE="xfs"

/dev/md4p1: UUID="342fe148-ba12-468b-8ac6-8e423d9d80ff" BLOCK_SIZE="512" TYPE="xfs"

/dev/md5p1: UUID="81972b1f-e366-4457-acac-87b48880fe08" BLOCK_SIZE="512" TYPE="xfs"

/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"

/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"

/dev/loop2: UUID="e1771ae2-0da4-4811-8ea1-bbde77a70dac" UUID_SUB="a2a8f406-43e2-4fd7-b356-22280ac7cdb0" BLOCK_SIZE="4096" TYPE="btrfs"

/dev/loop3: UUID="c2f3e91d-3493-4746-9881-2ec9568e5c6d" UUID_SUB="6f9f9a23-23a1-4166-9088-4c5832bb1481" BLOCK_SIZE="4096" TYPE="btrfs"

No btrfs or other filesystem detected, post output from:

wipefs /dev/nvme0n1p1

Despite the name, this command as written won't wipe anything.

Also

btrfs-select-super -s 1 /dev/nvme0n1p1

6 minutes ago, JorgeB said:

No btrfs or other filesystem detected, post output from:

wipefs /dev/nvme0n1p1

Despite the name, this command as written won't wipe anything.

Also

btrfs-select-super -s 1 /dev/nvme0n1p1

I ran both commands twice because the first wipefs command came up blank, but that could be due to me messing up copying and pasting:

root@FBUNRAID:~# wipefs /dev/nvme0n1p1
root@FBUNRAID:~# btrfs-select-super -s 1 /dev/nvme0n1p1
using SB copy 1, bytenr 67108864
root@FBUNRAID:~# wipefs /dev/nvme0n1p1
DEVICE    OFFSET  TYPE  UUID                                 LABEL
nvme0n1p1 0x10040 btrfs cd28e38f-d248-43ae-8ba0-b84fc7ff9e14 
root@FBUNRAID:~# btrfs-select-super -s 1 /dev/nvme0n1p1
using SB copy 1, bytenr 67108864

Looks like the backup superblock was successfully restored, try starting the array again, ifg it doesn't mount post new diags.

Thanks! The drive looks like it's mounted now and can read from it. I can grab any backups from there.

It doesn't have the docker containers I had installed before this came up. Do I just have to manually add each of the containers and it'll continue to use the app data located for that container? It looks like it's merged one of them (Plex) where the new database files have replaced the old ones, but the backups are still available. Diagnostics are attached if needed.

fbunraid-diagnostics-20250706-1729.zip

If you have the appdata, you should be able to re-add them from APPS:

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

Then:

https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

Also see below if you have any custom docker networks:

https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Thanks a lot for your help! I'm having an issue with my Plex database corrupted but that's another issue altogether.