borange

thanks @JorgeB That was an easy fix. The Array is back up. Think I panicked and overreacted a little.

Is it as simple as rebuilding the pools? Adding the drives back into the pools? (not sure how they got bad)

Label: none uuid: b6795987-af71-4d92-b324-d156a0d356db Total devices 1 FS bytes used 293.21GiB devid 1 size 953.87GiB used 349.02GiB path /dev/nvme0n1p1 Label: none uuid: 6fa7e030-f531-4670-83df-200d1634b831 Total devices 2 FS bytes used 348.88GiB devid 1 size 931.51GiB used 283.03GiB path /dev/sdb1 devid 2 size 931.51GiB used 283.03GiB path /dev/sdc1

root@dump:~# btrfs check /dev/sdc1 Opening filesystem to check... Checking filesystem on /dev/sdc1 UUID: 6fa7e030-f531-4670-83df-200d1634b831 [1/8] checking log skipped (none written) [2/8] checking root items [3/8] checking extents [4/8] checking free space tree [5/8] checking fs roots [6/8] checking only csums items (without verifying data) [7/8] checking root refs [8/8] checking quota groups skipped (not enabled on this FS) found 374607560704 bytes used, no error found total csum bytes: 255225452 total tree bytes: 430784512 total fs tree bytes: 92405760 total extent tree bytes: 56934400 btree space waste bytes: 55895081 file data blocks allocated: 430681206784 referenced 358848393216 root@dump:~# btrfs check /dev/sdb1 Opening filesystem to check... Checking filesystem on /dev/sdb1 UUID: 6fa7e030-f531-4670-83df-200d1634b831 [1/8] checking log skipped (none written) [2/8] checking root items [3/8] checking extents [4/8] checking free space tree [5/8] checking fs roots [6/8] checking only csums items (without verifying data) [7/8] checking root refs [8/8] checking quota groups skipped (not enabled on this FS) found 374607560704 bytes used, no error found total csum bytes: 255225452 total tree bytes: 430784512 total fs tree bytes: 92405760 total extent tree bytes: 56934400 btree space waste bytes: 55895081 file data blocks allocated: 430681206784 referenced 358848393216

Btrfs detects metadata inconsistency, often caused by unsafe shutdowns (power loss) or improper write caching. looks like i might need to do a better job of btrfs check

found this in dmesg, unsure of its meaning though [ 59.238592] BTRFS: device fsid 6fa7e030-f531-4670-83df-200d1634b831 devid 2 transid 4426877 /dev/sdc1 (8:33) scanned by udevd (2179) [ 59.239050] BTRFS: device fsid 6fa7e030-f531-4670-83df-200d1634b831 devid 1 transid 4426877 /dev/sdb1 (8:17) scanned by udevd (2177) sdb & sdc are the SSD cache drives. I ran a BTRFS check on them aswell.

Hi All, Having some trouble starting the Array. Wrong Pool State - (cache - missing devices, nvme_cache - missing devices) I ran a xfs_repair on the nvme drives. I believe they might be bad? Sorry, could not find valid secondary superblock - Would love to be wrong here. I removed one of my nvme cache pools all ready while i was messing around trying to fix. Nvme_cache - nvme0n1 cache - sdb + sdc pcinvme cache - nvme1n1 (the pool i removed) Unsure what is wrong with my SSD cache pool. Whats the best way to go about getting my array back up? Thanks! dump-diagnostics-20260331-2115.zip

Started a new config and running a parity-sync atm. Thanks for your help! I need to follow instructions better

Hmmm.... Bugger. I'm not able to tell which disk that would be. So, what would be my next step? Is it new config time? Is it possible to do a new config and keep the data I have?

The old disk 7 or 10 is currently installed.

What do you mean by what disks do I have? I had 3 bad disks. Currently two of the older ones are in the system (old Parity + another old 10TB) I have replacements for these drives.

Attempted to put one of the failed disks back in with no luck. Not able to start the array. I tried different combinations of where the drive was assigned. Popped in the old Parity disk as well to try something else. Same deal. Am I out of luck? Think I've molest it too much to get it back to a good state? dump-diagnostics-20240116-1610.zip

Correct, cannot replace any disks. Disk7 & 10 did not finish any rebuild. I believe i still have the old parity disk around and maybe one of the others disks (7 or 10).

I have 3 unassigned disks I've been trying to add to the array. 12tb to replace the dead parity disk (bringing me back to 2x parity disks) 2x10tb to replace the other to disks

Disk7 and 10 got disabled so I replaced them. The original disks are no longer connected. Yea, not a fan - but not alot I can do about it.