NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN428 - Waiting for encryption key but no encrypted volumes available
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 e...
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
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.
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).
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.
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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
