cen

ok but should I then take out the "old" disc which already has data on it since the other one is going to be encrypted or does it not matter because parity check will be done on both discs once the parity drives are set? and should I first start the encryption of the new drive or first start the parity and then format the new drive?

Just wondering: if I now have two data drives (the old one and the new encrypted one) how will Unraid then know which drive to do the parity check on. Won't both be added to the array? Sorry for being so new to Unraid.

hmm, ok. I'll try that. Thank you for the advice.

sorry but of which settings? "main"?

No the disc has not been touched yet (same xfs fs) except for hooking it to a other SATA port. The drive letter is also still the same (sdb). There is a green circle next to the drive.

sorry, that was misstated. I was using one drive but with data on it and the drive was the array. It was assigned as normal data drive not with parity protection since I only had one drive in the tower.

Hello, until now I was only using Unraid with one single unassigned drive for testing. Now I wanted to upgrade my setup with 3 more drives of the very same type (same producer, same series, same capacity) so that 2 would be parity drives and one would become my initial encrypted data-drive. the contents of the one year "old" drive would then be copied to the array and then afterwards the drive would be added to the array later on. I powered down clean and took out the "old" drive since I wanted to place it to another SATA port. One of the new drives (for parity) is now sitting where the old "drive" used to be. When starting Unraid I cannot start the array. It says to the left side: "Stopped. Invalid expansion." and to the right side I see: "You may not add new disk(s) and also remove existing disk(s).". The "old"disc has a green circle in front and the other three drives have blue squares. Can anybody help me to proceed? How can I install the two drives as parity? Greetings

Hi there, and thank you for this docker! I am really thrilled with the possibilities zero tier brings along and was searching for an option like this last year. The docker is running and I joined my private network without problems. In the networks section I see the IPs and that my tower is online but I somehow cannot get a connection from other places outside of home. I see the connected devices as ZT-leafs even from my tower via CLI-listpeers but when trying to go to the webadmin via the browser I don't get through. I also cannot mount SMB-share over ZT. Pinging works. I am guessing there could be something not set right at my tower? Do I need to allow any forwarding (via the docker?) on the tower so that traffic received by ZT in the docker then routes to the webgui or samba?