RN428 - Waiting for encryption key but no encrypted volumes available

[r00b]

Hi together,

some time ago I had an issue with my encrypted drives (encryption key wasn't found although it was on the pen drive). As a result I deleted all volumes and created new ones without encription. Since then I get the message "Waiting for encryption key" when booting the NAS and I have to wait until the timeout of 10 minutes is over.

Any idea how to remove the encryption process from the start up?

Thank you!

Regards,

Robert

[r00b · Accepted solution]

Hi together,

I could fix the issue by doing the following steps:

- check systemd-journal.log to see which volume is causing the problem

- delete volume

- create new volume with the same name and encryption enabled

- delete new volume

- create new volume with the same name without encryption

(probably it's not necessary but I've done a reboot between each step)

Now the system boots up without asking for an ecryption key.

BR,

Robert

[Marc_V]

@r00b

Welcome to the Community!

It would be best if you can contact Support so they can access it thru backend and fix it or if it's still possible, doing a Factory reset is another option. Doing OS-Reinstall might not work

HTH

[Sandshark]

@Marc_V, has it at least been logged as a bug, assuming it's a common problem when an encrypted volume has been deleted?

[Marc_V]

@Sandshark

I checked with Support yesterday if there has been any logged issues on this matter but nothing came out that is why I encouraged @r00b to contact Support so they can properly check on this. 

[mdgm]

This could be as simple as the fstab entry for the deleted volume still being present, so the system looks for the encryption key so it can attempt to mount the volume.

[r00b]

Thank you for your replies. My new volume has the same name as the old one. Looking at fstab I can see all current volumes only once. Any further advice? Any chance to see which volumes are marked es encrypted?

Thank you!

//edit: here you can see what I've found in the logs:

Started udev Wait for Complete Device Initialization.
systemd-cryptsetup@<volumeName>\x2d0.service: Job systemd-cryptsetup@<volumeName>\x2d0.service/start timed out.
Timed out starting Cryptography Setup for <volumeName>-0.
Dependency failed for dev-mapper-<volumeName>\x2d0.device.
dev-mapper-<volumeName>\x2d0.device: Job dev-mapper-<volumeName>\x2d0.device/start failed with result 'dependency'.
Dependency failed for Encrypted Volumes.
cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
systemd-cryptsetup@<volumeName>\x2d0.service: Job systemd-cryptsetup@<volumeName>\x2d0.service/start failed with result 'timeout'.
<volumeName>-key.service: Main process exited, code=exited, status=1/FAILURE
Failed to start Cryptography Key Search for <volumeName>.
<volumeName>-key.service: Unit entered failed state.
<volumeName>-key.service: Failed with result 'exit-code'.
Reached target Local File Systems (Pre).

[StephenB]

Since there is no data on the NAS, it's probably fastest to do a factory reset (clicking the "Perform Factory Default" control on system->settings->update ).  Then just set up the NAS again.

[r00b · Accepted solution]

Hi together,

I could fix the issue by doing the following steps:

- check systemd-journal.log to see which volume is causing the problem

- delete volume

- create new volume with the same name and encryption enabled

- delete new volume

- create new volume with the same name without encryption

(probably it's not necessary but I've done a reboot between each step)

Now the system boots up without asking for an ecryption key.

BR,

Robert

[Sandshark]

For the benetit of others, and Netwear if they find this is a bug, was there anything different in the way you deleted the re-created encrypted volume than the way you originally did it other than the fact that the encryption key for it was now available?

[r00b]

No, there was nothing special/different now. 

Looking at the log also only one of the 6 volumes I had before seemed not to be deleted completly and was waiting for the encryption key. All other 5 volumes have been deleted correctly.