March 31Mar 31 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 - nvme0n1cache - sdb + sdcpcinvme 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
March 31Mar 31 Author 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.
March 31Mar 31 Author 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
March 31Mar 31 Author root@dump:~# btrfs check /dev/sdc1Opening filesystem to check...Checking filesystem on /dev/sdc1UUID: 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 foundtotal csum bytes: 255225452total tree bytes: 430784512total fs tree bytes: 92405760total extent tree bytes: 56934400btree space waste bytes: 55895081file data blocks allocated: 430681206784 referenced 358848393216root@dump:~# btrfs check /dev/sdb1Opening filesystem to check...Checking filesystem on /dev/sdb1UUID: 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 foundtotal csum bytes: 255225452total tree bytes: 430784512total fs tree bytes: 92405760total extent tree bytes: 56934400btree space waste bytes: 55895081file data blocks allocated: 430681206784 referenced 358848393216
March 31Mar 31 Community Expert Both pools have no devices assigned. If the NVMe pool has been removed, you also need to remove it from the GUI. Click the first pool device and then "remove pool"For the other one, post the output from btrfs fi show
March 31Mar 31 Author 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/nvme0n1p1Label: 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
March 31Mar 31 Author Is it as simple as rebuilding the pools? Adding the drives back into the pools?(not sure how they got bad)
March 31Mar 31 Community Expert Solution Do this for both, assuming you want to keep both:on main click on the first device for that pool and then "remove pool"back on main, create a new pool with the same name and number of slotsassign the pool device(s), leave the filesystem set to autostart the array to import the pool
March 31Mar 31 Author thanks @JorgeB That was an easy fix. The Array is back up. Think I panicked and overreacted a little.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.