Hi
So I needed to pull the power for my NAS the day before yesterday and thought i waited long enough for a graceful shutdown but apparently not because I'm assuming that's what has messed up the file system.
I have two pools, one with two mirrored 1tb sata ssd:s and one much less important with just a single 2tb nvme. After starting back up it just says "Unmountable: Unsupported or no file system" on the single 2tb nvme.
I've tried searching around online a bit and looking around the system options and logs, also restarting the array but haven't really figured out what I should do next. I can't even seem to figure out which logs i should share that could be useful for troubleshooting?
It wouldn't be the end of the world to loose the data on it but I'd of course prefer not to.
Any ideas?

Best Regards Matt

Attach Diagnostics ZIP to your NEXT post in this thread.

Thanks, here is the diagnostics zip

bender-diagnostics-20260122-0022.zip

Start the array in normal (not maintenance) mode, then

Attach Diagnostics ZIP to your NEXT post in this thread.

Sorry, here it is

bender-diagnostics-20260122-0036.zip

your pool named 'ssd' is unmountable.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/data-recovery/

20 minutes ago, trurl said:

your pool named 'ssd' is unmountable.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/data-recovery/

"btrfs scrub" doesn't work since it isn't mounted.

"No valid Btrfs" when running "brtfs check /dev/nvme0n1p1".
"btrfs check --repair /dev/nvme0n1p1" didn't work either. I'm assuming that's the right name? I can't see any other it would be as it's the only nvme i have installed.

So is that all I can try other then the "ddrescue" method?
Because if that is the case then I guess I'll have to just wipe the drive.
I'm pretty certain it only contained media that ~should~ (hopefully) be pretty easily replaceable.

Please post the output from btrfs fi show

Please post the output from btrfs fi show

Doesn't seem to show the 2tb nvme, only my two mirrored 1tb drives?

I won't have access to a computer until later so here's a screenshot from my phone, I can't seem to be able to copy paste from the terminal on it.

Yep, no valid btrfs filesystem being detected on that device. When you can, post output from:

fdisk -l /dev/nvme0n1

and

blkid /dev/nvme0n1p1

Yep, no valid btrfs filesystem being detected on that device. When you can, post output from:

fdisk -l /dev/nvme0n1

and

blkid /dev/nvme0n1p1

"fdisk -l /dev/nvme0n1" showed

Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors

Disk model: WD_BLACK SN7100 2TB

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 32768 bytes / 262144 bytes

Disklabel type: dos

Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type

/dev/nvme0n1p1 64 3907029167 3907029104 1.8T 0 Empty

"blkid /dev/nvme0n1p1" Didn't show anything but "blkid /dev/nvme0n1p1" showed
/dev/nvme0n1: PTTYPE="dos"

16 minutes ago, MONK3Y said:

"blkid /dev/nvme0n1p1" Didn't show anything but "blkid /dev/nvme0n1p1" showed
/dev/nvme0n1: PTTYPE="dos"

Weird, blkid /dev/nvme0n1p1 should have output something like UUID="xxxxxxxx" UUID_SUB="xxxxxxxx" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="xxxxxxxx"

Weird, blkid /dev/nvme0n1p1 should have output something like UUID="xxxxxxxx" UUID_SUB="xxxxxxxx" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="xxxxxxxx"

nope i get nothing from it

The btrfs signature is missing, assuming the filesystem was btrfs for sure, and since the partition is still there, see if it can recover from a superblock backup. Post the output from

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

The btrfs signature is missing, assuming the filesystem was btrfs for sure, and since the partition is still there, see if it can recover from a superblock backup. Post the output from

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

Yes it should be btrfs, it says so as well in the drive settings

Running "btrfs-select-super -s 1 /dev/nvme0n1p1" gave:
"No valid Btrfs found on /dev/nvme0n1p1

ERROR: open ctree failed"

That suggests the filesystem was wiped or it wasn't Btrfs, type dd if=/dev/nvme0n1 bs=16M status=progress 2>/dev/null | hexdump -C | grep '_BHRfS_M'

Let it run for a couple of minutes and post if there's any output, you can abort anytime with CTRL + C

That suggests the filesystem was wiped or it wasn't Btrfs, type dd if=/dev/nvme0n1 bs=16M status=progress 2>/dev/null | hexdump -C | grep '_BHRfS_M'

Let it run for a couple of minutes and post if there's any output, you can abort anytime with CTRL + C

"dd if=/dev/nvme0n1 bs=16M status=progress 2>/dev/null | hexdump -C | grep '_BHRfS_M'"
Gave this pretty much straight away.

00110040 5f 42 48 52 66 53 5f 4d d9 00 00 00 00 00 00 00 |_BHRfS_M........|

04100040 5f 42 48 52 66 53 5f 4d d9 00 00 00 00 00 00 00 |_BHRfS_M........|

Those look like the normal places to have the btrsf superblock, but for a partition that starts on sector 2048, not 64 as the current partition you have.

type:

mkdir /x

losetup -f --show -o 1048576 /dev/nvme0n1

then using the loop device you get from the command above, e.g., loop2

mount -v /dev/loop2 /x

If that doesn't give an error, then

btrfs fi usage -T /x

Those look like the normal places to have the btrsf superblock, but for a partition that starts on sector 2048, not 64 as the current partition you have.

type:

mkdir /x

losetup -f --show -o 1048576 /dev/nvme0n1

then using the loop device you get from the command above, e.g., loop2

mount -v /dev/loop2 /x

If that doesn't give an error, then

btrfs fi usage -T /x

It gave me loop4. After running "mount -v /dev/loop4 /x" it gave me this:
"mount: /x: wrong fs type, bad option, bad superblock on /dev/loop4, missing codepage or helper program, or other error.

dmesg(1) may have more information after failed mount system call."

Not good, and does btrfs-select-super -s 1 /dev/loop4 find a filesystem?

Also post new diags or syslog just in case there's more info on why the mount failed.

Not good, and does btrfs-select-super -s 1 /dev/loop4 find a filesystem?

Nope?

"checksum verify failed on 30539776 wanted 0x00000000 found 0xb6bde3e4

checksum verify failed on 30539776 wanted 0x00000000 found 0xb6bde3e4

using SB copy 1, bytenr 67108864"

Maybe it's time to give up and just reformat the drive?
Like I mentioned earlier in the thread I don't think there's anything of real value on it. I got it about a month ago to specifically keep media that I watch regularly so that my HDD wouldn't have to spin up and that should be easily reacquired. I just hope that i actually followed that principle and didn't keep anything else on it because I can't quite remember😅
Is there any way so see the filesystem/folders in Unraid even if the drive is unavailable? Through the dynamix cache plugin or something else?

I attached a new diagnostic zip

bender-diagnostics-20260123-1549.zip

You can try and download UFS Explorer which is a data recovery software tool.

Not sure if the trial lets you mount btrfs disk/pools but it doesn't cost anything to try. You'd need to purchase the software to actually recover the files.

1 hour ago, MONK3Y said:

using SB copy 1, bytenr 67108864"

Try mounting it again, if it stil fails, I'm afraid it may not be recoverable with btrfs tools,

like mentioend UFS Exlorer can help, and ther free trial should show if/what it can recover, and you can then decide if it's important or not

Try mounting it again, if it stil fails, I'm afraid it may not be recoverable with btrfs tools,

like mentioend UFS Exlorer can help, and ther free trial should show if/what it can recover, and you can then decide if it's important or not

What do you mean by mounting? Just restarting the array? I tried a reboot and it still won't mount. I also tired to stop the array, remove the disk from it and mount it with unassigned devices but "mount" is grayed out.