I was out of town for the weekend and we had a sustained poweroutage.  When I came back home I discovered the same issue as :

https://forums.unraid.net/topic/157633-cache-drive-pool-unmountable-after-restart/

 

where my cache drives are not recognized which I discovered when none of my dockers existed....:

 

results of btrfs fi show:

root@STORAGE:~# btrfs fi show
Label: none  uuid: 0df9477a-fee8-4858-80b3-1047512917af
        Total devices 1 FS bytes used 392.00KiB
        devid    1 size 20.00GiB used 536.00MiB path /dev/loop2

Label: none  uuid: f9c6b189-82c9-4a45-b942-064f08446bdf
        Total devices 2 FS bytes used 8.67GiB
        devid    1 size 476.94GiB used 45.03GiB path /dev/sdf1
        devid    2 size 476.94GiB used 45.03GiB path /dev/sdg1

 

And both results of fdisk -i:
 

root@STORAGE:~# fdisk -l /dev/sdf1
Disk /dev/sdf1: 476.94 GiB, 512109142016 bytes, 1000213168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@STORAGE:~# fdisk -l /dev/sdg1
Disk /dev/sdg1: 476.94 GiB, 512109142016 bytes, 1000213168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

At the sfdisk command I get a different expeience, so posting here...

 

Any suggestion on the next step?

 

Thanks in Advance...

 

 

storage-diagnostics-20240312-2110.zip

5 hours ago, ffaat said:

Any suggestion on the next step?

The partitions exist, you didn't use the correct command with fdisk, it should have been 

fdisk -l /dev/sdf

 

Abort sgdisk and type:

btrfs rescue zero-log /dev/sdf1

Then restart the array and post new diags

 

fdisk -l /dev/sdf returns:

Disk /dev/sdf: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SanDisk SDSSDH3 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdf1        2048 1000215215 1000213168 476.9G 83 Linux

 

and btrfs rescue zero-log /dev/sdf1 returns:
 

Clearing log on /dev/sdf1, previous log_root 2131132416, level 0

 

Diags atached.

 

Cache array is up but my dockers seem all borked:

 

Any suggestions on next steps?

storage-diagnostics-20240313-2103.zip

Mar 13 20:59:35 STORAGE kernel: BTRFS: error (device sdf1: state A) in __btrfs_free_extent:3072: errno=-2 No such entry
Mar 13 20:59:35 STORAGE kernel: BTRFS info (device sdf1: state EA): forced readonly

 

Pool has other issues and it's going read-only, suggest backing it up and reformatting.

I did that, and now have no dockers... Can I restore them from the backed up folders some how?

 

If you managed to copy the appdata folder, restore that, then recreate the docker image.

 

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

Also see below if you have any custom docker networks:

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

8 hours ago, JorgeB said:

Also see below if you have any custom docker networks:

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

Alas - I did, but hadn't noted them down... WIll I have to try and reconstruct from memory or can I find artifacts within the contrainers or old configuration to indicate what they were?

 

TIA-

21 minutes ago, ffaat said:

or can I find artifacts within the contrainers or old configuration to indicate what they were?

That I don't know, maybe someone else will.