Hi,

I think I did something really stupid :(

I had a dead drive. It had only some old backups so I thought about replacing it but without a rebuild. To start with an empty disk.

What I did:

- stop array

- tools -> new config

- same config as before but without the failed drive

***Stupid action incoming***
-> reboot

I think I have lost all my config in unraid. Thats not cool, but I can deal with it. 

The much more important thing is to get my data on the encrypted drives again.

After the reboot I can assign the drives again (no problem, I have documented the disk order in the array; also the cache and parity drives).
But the "Encryption Status" says "Enter new key". 

Any ideas how to mount the existing encrypted drives in a clean unraid config?

Thanks! :)

IIRC you shroud get "missing key", not "enter new key", are you on latest unRAID?

I am on 6.4.1

Update to 6.5.1 and try again, if you don't get a missing key warning post the diagsnotics.

I updated to 6.5.1 -> still the same.

I don't think the diagnostics would help because this is not an error or something.
The actual status is that I have to reassign all disks to the slots. After this I can restart the array. But only after entering a new encryption key.

-> I need an option or something to say unraid that the array is already there and encrypted. I want to enter the key and unraid starts the array.
Let me know if the diagnostics would really help you!

Edited May 10, 20188 yr by rootiam

Enter the key which you used before, it allows the array to start as before.

 

14 minutes ago, bonienl said:

Enter the key which you used before, it allows the array to start as before.

  

Yeah! Thanks a lot! Working perfectly and I have my data back

1 hour ago, rootiam said:

I don't think the diagnostics would help because this is not an error or something.

the diags would show something similar to this:

 

May 10 14:58:01 Tower9 kernel: md1: running, size: 244198552 blocks
May 10 14:58:01 Tower9 kernel: md2: running, size: 244198552 blocks
May 10 14:58:01 Tower9 kernel: md3: running, size: 244198552 blocks
May 10 14:58:01 Tower9 kernel: md4: running, size: 244198552 blocks
May 10 14:58:01 Tower9 emhttpd: shcmd (94): udevadm settle
May 10 14:58:01 Tower9 emhttpd: Opening encrypted volumes...
May 10 14:58:01 Tower9 emhttpd: shcmd (98): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --key-file /root/keyfile
May 10 14:58:01 Tower9 root: Failed to open key file.
May 10 14:58:01 Tower9 emhttpd: shcmd (98): exit status: 1
May 10 14:58:01 Tower9 emhttpd: shcmd (100): /usr/sbin/cryptsetup luksOpen /dev/md4 md4 --key-file /root/keyfile
May 10 14:58:01 Tower9 root: Failed to open key file.
May 10 14:58:01 Tower9 emhttpd: shcmd (100): exit status: 1
May 10 14:58:01 Tower9 emhttpd: Missing encryption key
May 10 14:58:01 Tower9 kernel: mdcmd (43): stop 
May 10 14:58:01 Tower9 kernel: md1: stopping
May 10 14:58:01 Tower9 kernel: md2: stopping
May 10 14:58:01 Tower9 kernel: md3: stopping
May 10 14:58:01 Tower9 kernel: md4: stopping

 

And I just tested after a new config and a reboot and I get "missing key", not "enter new key", that's why I wanted to see them, but glad it's sorted.