February 8, 20242 yr Hello Unraid Community, I'm encountering an issue and could really use some help. Here's the situation: I have a pool consisting of 2 SSDs, each 240GB, set up in encrypted btrfs mode for redundancy. Today, I added 2 NVMe drives to this pool, bringing the total to 4 drives. After starting the array, the new drives were all built, and I was able to use the pool as before. However, when I attempted to remove one disk, I couldn't start the array because too many drives were missing (despite having the box checked next to the start button). After trying to troubleshoot with the Unassigned Devices plugin, following a forum post, I ended up breaking the pool. Now, all 4 drives need to be formatted. This is problematic because all my Docker files are stored in this pool. I'm at a loss for what to do next. Any advice from my fellow Unraiders would be greatly appreciated. hermes-diagnostics-20240208-1340.zip Edited February 8, 20242 yr by Hermis
February 8, 20242 yr Community Expert Try this: Unassign all pool devices, start array, stop array, reassign all 4 pool devices, start array and post new diags.
February 8, 20242 yr Author 18 minutes ago, JorgeB said: Try this: Unassign all pool devices, start array, stop array, reassign all 4 pool devices, start array and post new diags. Thank you for your guidance. Because i am not 100% familiar with the Unassigned all pool devices, please helm me to ensure I understand correctly without causing further issues: 1) I Stop Array 2) I go to the pool and i set each of the 4 drivers to No Device from the drop down menu (1 option is to set the SSD and the other option to set to No Device) 3) I check that all 4 drivers then appear in unassigned devised in the Plugin. 4) i Start array Checking the box (Start will remove the missing cache disk and then bring the array on-line.) *** Isn't this going to delete all my files on that pool?? *** 5)I stop Array and i set back the 4 SSDs in the pool as there where before? Could you please confirm if this procedure aligns with the initial advice provided? If not, could you kindly advise on any additional steps or adjustments necessary? Thank you for your assistance. Edited February 8, 20242 yr by Hermis
February 8, 20242 yr Community Expert 53 minutes ago, Hermis said: 4) i Start array Checking the box (Start will remove the missing cache disk and then bring the array on-line.) *** Isn't this going to delete all my files on that pool?? *** No, it won't delete anything, just leave the devices unassigned, don't do anything else with them. Steps are correct.
February 8, 20242 yr Author 40 minutes ago, JorgeB said: No, it won't delete anything, just leave the devices unassigned, don't do anything else with them. Steps are correct. Problem is still here, Unmountable disk present: in all 4 drives. New Diagnostics: 2hermes-diagnostics-20240208-1629.zip
February 8, 20242 yr Community Expert The NVMe devices are not being decrypted, but I don't see why not, post the output of: blkid
February 8, 20242 yr Author 11 minutes ago, JorgeB said: The NVMe devices are not being decrypted, but I don't see why not, post the output of: blkid Spoiler /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/sdf1: UUID="0ee117f6-eb11-4fe9-a8db-d6bb23df776b" TYPE="crypto_LUKS" PARTUUID="5631157c-a87f-4582-95f7-ec7c046d70aa" /dev/sdb1: UUID="17a5eea1-3c85-4728-b320-e471198ee4c9" TYPE="crypto_LUKS" /dev/sdi1: UUID="1d8fc7dd-dc1f-4718-91a8-3f678f0b3235" TYPE="crypto_LUKS" PARTUUID="15ebdf26-4a5d-44c2-b37b-600bd69aa737" /dev/sdg1: UUID="9cd99fad-19be-4150-a215-ff3d908f2340" TYPE="crypto_LUKS" PARTUUID="3be9b4e8-d531-4b93-bf0a-8280c8deb4ba" /dev/loop0: TYPE="squashfs" /dev/sde1: UUID="4481e308-b594-497a-84c0-74f5872c1a2c" TYPE="crypto_LUKS" /dev/sdc1: UUID="4e49bbca-a598-4cc6-8172-7f8c3a17ff0a" TYPE="crypto_LUKS" /dev/sdj1: UUID="72a62fea-f5f8-4822-91e8-6acb25aaacff" TYPE="crypto_LUKS" PARTUUID="4c34b1d9-3f4f-413b-a8cb-9b416a98a331" /dev/sdh1: UUID="75f60159-a0a6-4de3-9141-44010d7550a3" TYPE="crypto_LUKS" PARTUUID="8c9ab20a-16d9-4dbc-b3e0-4db2a91c1d8e" /dev/mapper/md2p1: UUID="291d5519-d418-446e-880f-7aa1db61a613" BLOCK_SIZE="512" TYPE="xfs" /dev/md2p1: UUID="75f60159-a0a6-4de3-9141-44010d7550a3" TYPE="crypto_LUKS" /dev/md5p1: UUID="0ee117f6-eb11-4fe9-a8db-d6bb23df776b" TYPE="crypto_LUKS" /dev/mapper/sde1: UUID="83d9f94b-4c22-48cf-bafd-d42aeeaa692c" UUID_SUB="b98ecb86-761f-4d74-a7ff-71b30d11a688" BLOCK_SIZE="4096" TYPE="btrfs" /dev/mapper/md5p1: UUID="955f7c60-0636-48a2-8b91-46b08e80359d" BLOCK_SIZE="512" TYPE="xfs" /dev/md1p1: UUID="9cd99fad-19be-4150-a215-ff3d908f2340" TYPE="crypto_LUKS" /dev/mapper/md3p1: UUID="a1231a09-0494-47bd-9b98-1dfb9b17f447" BLOCK_SIZE="512" TYPE="xfs" /dev/md4p1: UUID="72a62fea-f5f8-4822-91e8-6acb25aaacff" TYPE="crypto_LUKS" /dev/mapper/md1p1: UUID="1218bd1e-0436-4cd3-9027-f6e0af52c185" BLOCK_SIZE="512" TYPE="xfs" /dev/mapper/sdc1: UUID="83d9f94b-4c22-48cf-bafd-d42aeeaa692c" UUID_SUB="239867fe-5d43-4dae-bfae-2c41975e2c28" BLOCK_SIZE="4096" TYPE="btrfs" /dev/mapper/sdb1: UUID="3a152c80-3ff8-437a-a299-76c63dd10d47" BLOCK_SIZE="512" TYPE="xfs" /dev/md3p1: UUID="1d8fc7dd-dc1f-4718-91a8-3f678f0b3235" TYPE="crypto_LUKS" /dev/mapper/md4p1: UUID="b240d468-586c-4b15-8787-915f2edfce88" BLOCK_SIZE="512" TYPE="xfs" /dev/nvme0n1: PTUUID="75370908" PTTYPE="dos" /dev/sdd1: UUID="8e>ni13n-7=e<-4<60-9;ef-3c4b14:6be62" TYPE="crypto_LUKS" PARTUUID="f87b8b53-9469-4917-b2e9-f2937618cf78" /dev/loop2: UUID="2e463f51-c23c-45f6-b8ad-624cc511e499" UUID_SUB="61d37617-d947-4c2a-993f-6c0ae81c1f6c" BLOCK_SIZE="4096" TYPE="btrfs" /dev/nvme1n1: PTUUID="784f3595" PTTYPE="dos"
February 8, 20242 yr Author Btw I just saw that the File System is set to auto. i didn't change that. its was btrfs encrypted if i remember correctly. shall I do something?
February 8, 20242 yr Community Expert 39 minutes ago, Hermis said: /dev/nvme0n1: PTUUID="75370908" PTTYPE="dos" /dev/nvme1n1: PTUUID="784f3595" PTTYPE="dos" Now I see why the NVMe devices are not being decrypted, they don't have a LUKS signature, they should look like this: 40 minutes ago, Hermis said: /dev/sdj1: UUID="72a62fea-f5f8-4822-91e8-6acb25aaacff" TYPE="crypto_LUKS" PARTUUID="4c34b1d9-3f4f-413b-a8cb-9b416a98a331" /dev/sdh1: UUID="75f60159-a0a6-4de3-9141-44010d7550a3" TYPE="crypto_LUKS" PARTUUID="8c9ab20a-16d9-4dbc-b3e0-4db2a91c1d8e" I don't see why the LUKS signature is gone, as far as I can see it's nothing you or Unraid did, the devices were formatted and opened encrypted initially: Feb 8 03:14:59 Hermes emhttpd: shcmd (17519): /usr/sbin/cryptsetup luksFormat /dev/nvme0n1p1 Feb 8 03:15:06 Hermes emhttpd: shcmd (17522): /usr/sbin/cryptsetup luksOpen /dev/nvme0n1p1 nvme0n1p1 --allow-discards Feb 8 03:15:08 Hermes emhttpd: shcmd (17523): /sbin/btrfs device add -f /dev/mapper/nvme0n1p1 /mnt/cache_ssd ... Feb 8 03:15:11 Hermes emhttpd: shcmd (17528): /usr/sbin/cryptsetup luksFormat /dev/nvme1n1p1 Feb 8 03:15:18 Hermes emhttpd: shcmd (17531): /usr/sbin/cryptsetup luksOpen /dev/nvme1n1p1 nvme1n1p1 --allow-discards Feb 8 03:15:20 Hermes emhttpd: shcmd (17532): /sbin/btrfs device add -f /dev/mapper/nvme1n1p1 /mnt/cache_ssd The pool mounted and when you stopped the array LUKS was closed for all devices, including the NVMe devices: Feb 8 12:27:54 Hermes emhttpd: shcmd (17676): /usr/sbin/cryptsetup luksClose md1p1 Feb 8 12:27:54 Hermes emhttpd: shcmd (17677): /usr/sbin/cryptsetup luksClose md2p1 Feb 8 12:27:54 Hermes emhttpd: shcmd (17678): /usr/sbin/cryptsetup luksClose md3p1 Feb 8 12:27:54 Hermes emhttpd: shcmd (17679): /usr/sbin/cryptsetup luksClose md4p1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17680): /usr/sbin/cryptsetup luksClose md5p1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17681): /usr/sbin/cryptsetup luksClose sdb1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17682): /usr/sbin/cryptsetup luksClose sde1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17683): /usr/sbin/cryptsetup luksClose sdc1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17684): /usr/sbin/cryptsetup luksClose nvme0n1p1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17685): /usr/sbin/cryptsetup luksClose nvme1n1p1 Then you tried to start the array without one of the pool devices, BTW this failed because the pool was using the single profile, not raid1, so it wasn't redundant, devices can only be removed from redundant pools, still, this does not explain why the next time the array was started, with all pool devices in their correct positions, the NVMe devices lost the LUKS signature, they were no longer decrypted: Feb 8 13:14:22 Hermes emhttpd: shcmd (21226): /usr/sbin/cryptsetup luksOpen /dev/md1p1 md1p1 Feb 8 13:14:23 Hermes emhttpd: shcmd (21229): /usr/sbin/cryptsetup luksOpen /dev/md2p1 md2p1 Feb 8 13:14:23 Hermes emhttpd: shcmd (21232): /usr/sbin/cryptsetup luksOpen /dev/md3p1 md3p1 Feb 8 13:14:25 Hermes emhttpd: shcmd (21235): /usr/sbin/cryptsetup luksOpen /dev/md4p1 md4p1 Feb 8 13:14:27 Hermes emhttpd: shcmd (21238): /usr/sbin/cryptsetup luksOpen /dev/md5p1 md5p1 Feb 8 13:14:29 Hermes emhttpd: shcmd (21241): /usr/sbin/cryptsetup luksOpen /dev/sdb1 sdb1 --allow-discards Feb 8 13:14:31 Hermes emhttpd: shcmd (21244): /usr/sbin/cryptsetup luksOpen /dev/sde1 sde1 --allow-discards Feb 8 13:14:32 Hermes emhttpd: shcmd (21247): /usr/sbin/cryptsetup luksOpen /dev/sdc1 sdc1 --allow-discards As you can see, the NVMe devices are not on the list, and I'm afraid that because of the encryption recovery will likely be impossible, why I recommend only using encryption if you really need to, or it's just complicates things if any kind of recovery is needed. I can only try to see if the partitions are correct, and if not, see if they can be recovered, post the output of: fdisk -l /dev/nvme0n1
February 8, 20242 yr Author 6 hours ago, JorgeB said: Now I see why the NVMe devices are not being decrypted, they don't have a LUKS signature, they should look like this: I don't see why the LUKS signature is gone, as far as I can see it's nothing you or Unraid did, the devices were formatted and opened encrypted initially: Feb 8 03:14:59 Hermes emhttpd: shcmd (17519): /usr/sbin/cryptsetup luksFormat /dev/nvme0n1p1 Feb 8 03:15:06 Hermes emhttpd: shcmd (17522): /usr/sbin/cryptsetup luksOpen /dev/nvme0n1p1 nvme0n1p1 --allow-discards Feb 8 03:15:08 Hermes emhttpd: shcmd (17523): /sbin/btrfs device add -f /dev/mapper/nvme0n1p1 /mnt/cache_ssd ... Feb 8 03:15:11 Hermes emhttpd: shcmd (17528): /usr/sbin/cryptsetup luksFormat /dev/nvme1n1p1 Feb 8 03:15:18 Hermes emhttpd: shcmd (17531): /usr/sbin/cryptsetup luksOpen /dev/nvme1n1p1 nvme1n1p1 --allow-discards Feb 8 03:15:20 Hermes emhttpd: shcmd (17532): /sbin/btrfs device add -f /dev/mapper/nvme1n1p1 /mnt/cache_ssd The pool mounted and when you stopped the array LUKS was closed for all devices, including the NVMe devices: Feb 8 12:27:54 Hermes emhttpd: shcmd (17676): /usr/sbin/cryptsetup luksClose md1p1 Feb 8 12:27:54 Hermes emhttpd: shcmd (17677): /usr/sbin/cryptsetup luksClose md2p1 Feb 8 12:27:54 Hermes emhttpd: shcmd (17678): /usr/sbin/cryptsetup luksClose md3p1 Feb 8 12:27:54 Hermes emhttpd: shcmd (17679): /usr/sbin/cryptsetup luksClose md4p1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17680): /usr/sbin/cryptsetup luksClose md5p1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17681): /usr/sbin/cryptsetup luksClose sdb1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17682): /usr/sbin/cryptsetup luksClose sde1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17683): /usr/sbin/cryptsetup luksClose sdc1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17684): /usr/sbin/cryptsetup luksClose nvme0n1p1 Feb 8 12:27:55 Hermes emhttpd: shcmd (17685): /usr/sbin/cryptsetup luksClose nvme1n1p1 Then you tried to start the array without one of the pool devices, BTW this failed because the pool was using the single profile, not raid1, so it wasn't redundant, devices can only be removed from redundant pools, still, this does not explain why the next time the array was started, with all pool devices in their correct positions, the NVMe devices lost the LUKS signature, they were no longer decrypted: Feb 8 13:14:22 Hermes emhttpd: shcmd (21226): /usr/sbin/cryptsetup luksOpen /dev/md1p1 md1p1 Feb 8 13:14:23 Hermes emhttpd: shcmd (21229): /usr/sbin/cryptsetup luksOpen /dev/md2p1 md2p1 Feb 8 13:14:23 Hermes emhttpd: shcmd (21232): /usr/sbin/cryptsetup luksOpen /dev/md3p1 md3p1 Feb 8 13:14:25 Hermes emhttpd: shcmd (21235): /usr/sbin/cryptsetup luksOpen /dev/md4p1 md4p1 Feb 8 13:14:27 Hermes emhttpd: shcmd (21238): /usr/sbin/cryptsetup luksOpen /dev/md5p1 md5p1 Feb 8 13:14:29 Hermes emhttpd: shcmd (21241): /usr/sbin/cryptsetup luksOpen /dev/sdb1 sdb1 --allow-discards Feb 8 13:14:31 Hermes emhttpd: shcmd (21244): /usr/sbin/cryptsetup luksOpen /dev/sde1 sde1 --allow-discards Feb 8 13:14:32 Hermes emhttpd: shcmd (21247): /usr/sbin/cryptsetup luksOpen /dev/sdc1 sdc1 --allow-discards As you can see, the NVMe devices are not on the list, and I'm afraid that because of the encryption recovery will likely be impossible, why I recommend only using encryption if you really need to, or it's just complicates things if any kind of recovery is needed. I can only try to see if the partitions are correct, and if not, see if they can be recovered, post the output of: fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: KINGSTON SNV2S1000G 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: 0x75370908
February 9, 20242 yr Community Expert The partition is missing, type: sfdisk /dev/nvme0n1 then type 2048 and hit return, post the results after doing that, don't type anything else.
February 9, 20242 yr Author 2 hours ago, JorgeB said: The partition is missing, type: sfdisk /dev/nvme0n1 then type 2048 and hit return, post the results after doing that, don't type anything else. root@Hermes:~# sfdisk /dev/nvme0n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: KINGSTON SNV2S1000G 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: 0x75370908 Old situation: Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0x5004c4b3. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. Partition #1 contains a crypto_LUKS signature. Do you want to remove the signature? [Y]es/[N]o:
February 9, 20242 yr Community Expert Solution Type N plus return to keep the signature, then type: write and hit return again. Repeat the same for the other nvme device (nvme1n1), if a LUKS signature is also found keep it, then post new diags to see the current pool status.
February 9, 20242 yr Author 5 hours ago, JorgeB said: Type N plus return to keep the signature, then type: write and hit return again. Repeat the same for the other nvme device (nvme1n1), if a LUKS signature is also found keep it, then post new diags to see the current pool status. root@Hermes:~# sfdisk /dev/nvme0n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: KINGSTON SNV2S1000G 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: 0x75370908 Old situation: Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0x5004c4b3. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. Partition #1 contains a crypto_LUKS signature. Do you want to remove the signature? [Y]es/[N]o: N /dev/nvme0n1p1 : 2048 1953525167 (931.5G) Linux /dev/nvme0n1p2: write New situation: Disklabel type: dos Disk identifier: 0x5004c4b3 Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 2048 1953525167 1953523120 931.5G 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. root@Hermes:~# sfdisk /dev/nvme1n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme1n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: KINGSTON SNV2S1000G 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: 0x784f3595 Old situation: Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0x3e68e19f. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. Partition #1 contains a crypto_LUKS signature. Do you want to remove the signature? [Y]es/[N]o: N /dev/nvme1n1p1 : 2048 1953525167 (931.5G) Linux /dev/nvme1n1p2: write New situation: Disklabel type: dos Disk identifier: 0x3e68e19f Device Boot Start End Sectors Size Id Type /dev/nvme1n1p1 2048 1953525167 1953523120 931.5G 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. root@Hermes:~# ------------------------------ Just to clarify again, Return you mean the button Enter in keyboard OR shift+Enter ?? done it with shift+ enter hope its good. 3hermes-diagnostics-20240209-1930.zip
February 9, 20242 yr Community Expert 13 minutes ago, Hermis said: Return you mean the button Enter This. Output above looks good, according to diags the 4 pools devices are assigned correctly, the pool is still unmountable of course, so just stop the array, start the array again, post new diags.
February 9, 20242 yr Author 6 hours ago, JorgeB said: This. Output above looks good, according to diags the 4 pools devices are assigned correctly, the pool is still unmountable of course, so just stop the array, start the array again, post new diags. Everything works fine!!! Thanks a lot!! I really appreciate your help, if I had lost my files i would be in pieces.... Now, can you explain me how can I remove the 2 old SSDs I have (240gb) and put the Nvme ones? I read at the forums that i have to take out one by one the Drivers in the pool. So the procedure is that i have to take the NVMEs first out (both of them), make my pool 2 disks from 4, and then change SSD with M.2, start array let rebuild, and after change the second driver. Is that correct? Because now when I take one Nvme out of the pool (by selecting no device in the dropdown menu), i tick the box (Start will remove the missing cache disk and then bring the array on-line. Yes, I want to do this) but i cant start array because **Wrong Pool State cache_ssd - too many missing/wrong devices** I see the driver in the unnassigned Devices, but i dont do anything else. why is that? 4hermes-diagnostics-20240210-0124.zip Edited February 10, 20242 yr by Hermis
February 10, 20242 yr Community Expert 9 hours ago, Hermis said: Because now when I take one Nvme out of the pool (by selecting no device in the dropdown menu), i tick the box (Start will remove the missing cache disk and then bring the array on-line. Yes, I want to do this) but i cant start array because **Wrong Pool State cache_ssd - too many missing/wrong devices** I see the driver in the unnassigned Devices, but i dont do anything else. why is that? I did mention before: On 2/8/2024 at 4:21 PM, JorgeB said: BTW this failed because the pool was using the single profile, not raid1, so it wasn't redundant, devices can only be removed from redundant pools Now that the pool is mounting again you first need to convert it to raid1, only after doing that will you be able to remove the other two devices, one at a time. To convert the pool click on it, scroll down to the balance sections and select "convert to raid1", then click balance.
February 11, 20242 yr Author On 2/10/2024 at 11:08 AM, JorgeB said: I did mention before: Now that the pool is mounting again you first need to convert it to raid1, only after doing that will you be able to remove the other two devices, one at a time. To convert the pool click on it, scroll down to the balance sections and select "convert to raid1", then click balance. I Follow your steps but i Can't remove the ssd..... also look in forums but maybe i am bigger noob than i thought. Steps: 1)I start Array 2) i Click Cache_SSD in main tab, i go to Settings tab 3) In balance dropdown Menu i select Conver to raid1 and i Hit Balance now button 4) I wait balance to stop and i stop array 5)i go to Pool, remove the last SSD (nvme of 1tb) and I try to start array with the "remove this device from pool" ticked (but not the Maintance mode) 6) I Get Error...... (Wrong Pool State...) BTW while the array is running, It tells me Its raid1 , When i stop array its says in BTRFs Single mode...... 5hermes-diagnostics-20240211-1237.zip Edited February 11, 20242 yr by Hermis
February 11, 20242 yr Community Expert Possibly the profile is not being correctly updated after the conversion, edit /boot/config/pools/cache_ssd.cfg and change diskFsProfile="single" to diskFsProfile="raid1", then try again, a reboot before may be needed.
February 13, 20242 yr Author I encouted another problem again Sifu Jorge, please On 2/11/2024 at 1:33 PM, JorgeB said: Possibly the profile is not being correctly updated after the conversion, edit /boot/config/pools/cache_ssd.cfg and change diskFsProfile="single" to diskFsProfile="raid1", then try again, a reboot before may be needed. I did that. pool work ok with files intact. I hadd all 4 ssd conected and i starting by removing the 2nd in order (240gb), i let rebuild, all worked fine. After i remove the 1st in order ssd (240gb), since i want to keep the 2 nvmes of 1Tb in the pool. And all the files were gone as there weren't copied to the other 2 drives from the pool... Now if i put back the ssd to pool is says it will delete all its content when aray starts, that we dont want. At that point I would like just to get the setup as it was if possible, copy the files in a completly new pool without encryption, and delete this one once and for all. 7hermes-diagnostics-20240213-2207.zip
February 13, 20242 yr Community Expert Diags are after rebooting, but post new ones after array start with just the two NVMe devices assigned to the pool.
February 13, 20242 yr Author 8 minutes ago, JorgeB said: Diags are after rebooting, but post new ones after array start with just the two NVMe devices assigned to the pool. 8hermes-diagnostics-20240213-2244.zip EDIT: After the reboot and the start array again its working!! the pool is showing the files its suposed. i dont know if i missed something or worked after. Thanks! Edited February 13, 20242 yr by Hermis
February 13, 20242 yr Community Expert Great, not sure what the problem was before but pool looks normal now.
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.