January 10, 20251 yr Like the title says, I have two new SSD drives and I want to add these to an existing RAID-0 btrfs pool that already contained two other SSD. All of these drives are 1TB SSD. While trying to find a free hdd slot in my server I disconnected the two existing SSD from the pool, plus other HDD from the main array. I connected all back again in the same slot and I found two free slots to insert my two new SSDs. At this point, all drives that I disconnected and the ones I added were in the unmounted section. I stopped the array, I changed the pool number of disks from 2 to 4, added the two new SSDs in that pool and I started the array back. Now the "fun" happens, one of my HDD from the array was emulated and currently while I'm writing this, the rebuild process is taking care of that issue. But the main issue that I don't know how to solve is that ALL my 4 SSDs from the pool have the "Unmountable: Unsupported or no file system" message: There's also the option of formatting these Unmountable drives, which I DID NOT click: I'm assuming the normal behaviour would be just for the two new drives to appear in this list and just only then I could format using this option. ---- In short now I'm stuck, I cannot go back from 4 to 2 drives in the pool like I used to have in a way to recover my data, nor I know how to proceeed to resolve this issue. I've attached the diagnostiscs file, keep in mind that I have a current rebuild running for one of the HDD drives in the array that I disconnected by mistake. kamogawa-srv-diagnostics-20250110-1731.zip Edited January 10, 20251 yr by IppoKun
January 10, 20251 yr Author Quote Label: none uuid: f9df4faf-795d-40ee-8f71-512ea45d0806 Total devices 1 FS bytes used 367.68GiB devid 1 size 1.82TiB used 375.04GiB path /dev/nvme0n1p1 Label: none uuid: d917ed2e-8b62-4bf9-8c2a-69b2feee95f9 Total devices 1 FS bytes used 22.90GiB devid 1 size 200.00GiB used 49.02GiB path /dev/loop2 Label: none uuid: 73623dc0-35f3-46dd-8ee3-99f0c56c46f1 Total devices 1 FS bytes used 712.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3 Label: none uuid: 22542a88-c113-450c-aec2-9d098fda2f9d Total devices 2 FS bytes used 1.56TiB devid 1 size 953.87GiB used 803.03GiB path /dev/sdr1 devid 2 size 953.87GiB used 803.03GiB path /dev/sdp1 Label: none uuid: f80f88d7-f66f-4e34-a383-3a01d15ac8bd Total devices 1 FS bytes used 144.00KiB devid 1 size 931.51GiB used 2.02GiB path /dev/sdu1 Label: none uuid: 5612211e-3efb-4eb6-ac47-6bf7ba3b8a07 Total devices 1 FS bytes used 144.00KiB devid 1 size 931.51GiB used 2.02GiB path /dev/sdq1
January 10, 20251 yr Community Expert Solution 30 minutes ago, IppoKun said: Label: none uuid: 22542a88-c113-450c-aec2-9d098fda2f9d Total devices 2 FS bytes used 1.56TiB devid 1 size 953.87GiB used 803.03GiB path /dev/sdr1 devid 2 size 953.87GiB used 803.03GiB path /dev/sdp1 Re-import the pool with just these two devices, to do that, stop the array unassign all pool devices start the array stop the array reassign only those two devices start the array, post new diags.
January 12, 20251 yr Author On 1/10/2025 at 7:06 PM, JorgeB said: Re-import the pool with just these two devices, to do that, stop the array unassign all pool devices start the array stop the array reassign only those two devices start the array, post new diags. Attaching the logs, same behaviour. kamogawa-srv-diagnostics-20250112-0103.zip
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.