Hermis

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!

I encouted another problem again Sifu Jorge, please 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

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

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

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

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:

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

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?

Problem is still here, Unmountable disk present: in all 4 drives. New Diagnostics: 2hermes-diagnostics-20240208-1629.zip

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.

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

I only used root user to do everything. Install docker apps, shares and I didn't create any users-groups and I didn't modify any write/read restriction to anything. All left with their "vanilla" settings on install. Which if I had understand correctly is bad for security reasons...

Hey Unraid community! I've been using Unraid for 1.5 years now and have been running popular dockers and the Sonarr-Radarr suite. However, I made a few mistakes during the initial setup as a newbie, one of which was not properly setting up Docker users. As a result, I want to start fresh and ensure that all the necessary users are set up properly. My question is whether I can create a new server on a trial USB and transfer my key once the setup is complete. I want to make sure I don't lose any data during the transition. Any advice or guidance on this process would be much appreciated. Thank you! Edited just now by Hermis

Hey Unraid community! I've been using Unraid for 1.5 years now and have been running popular dockers and the Sonarr-Radarr suite. However, I made a few mistakes during the initial setup as a newbie, one of which was not properly setting up Docker users. As a result, I want to start fresh and ensure that all the necessary users are set up properly. My question is whether I can create a new server on a trial USB and transfer my key once the setup is complete. I want to make sure I don't lose any data during the transition. Any advice or guidance on this process would be much appreciated. Thank you!