Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Solved]LUKS missing key/no key file available with this passphrase

Featured Replies

Hello,

 

So, after ending last year on an unRaid high (Converted all drives to encrypted XFS and added a second parity drive!), I seem to be starting off the year on a low. Last night, one of my fans started to make a loud noise. I decided to shut the system down and take a look at which fan was problematic later. I powered the system back up and found the faulty fan. I then log into web interface and enter my passphase to start the array.

 

I didn't quite pay attention, looked at something else for a few minutes, came back to unRaid and I saw the array had not started. Odd! I'm sure I entered the passphase. and hit "Start". Did I enter the right one?! After multiple attempts and reboots, no go!?!

 

No problem I thought. Let me pull out a drive from the array and see if I can mount it on my workstation (Arch Linux w/ Plasma Desktop). I did that and the drive is shown as encrypted in Dolphin. I clicked on it and entered the passphrase. Unfortunately, it errored with "Incorrect passphrase". 

 

While I'm not new to Linux, I'm new to using LUKS. Did some googling and attempted to use cryptsetup to see if I could get any more information. luksDump works and outputs relevant information but unfortunately, any attempt to manually mount the partition, results in "No key available with this passphrase.".

 

Prior to posting, I search and some a few similar threads but they either had no solution or the thread couldn't be open. 

 

Has anyone come across this issue? Any known solution?

 

Thanks and Happy New Year,

 

cesman

Edited by cesman
Resolved

  • Author

Well, I came across this post that indicated this issue was resolved with a workaround of using the keyfile. Unfortunately, the keyfile doesn't work for me. 

 

Here is log output:

Quote

Jan 3 21:09:53 usul emhttpd: shcmd (116): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --allow-discards --key-file=/root/keyfile
Jan 3 21:09:55 usul root: No key available with this passphrase.
Jan 3 21:09:55 usul emhttpd: shcmd (116): exit status: 2
Jan 3 21:09:55 usul emhttpd: shcmd (118): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --allow-discards --key-file=/root/keyfile
Jan 3 21:09:57 usul root: No key available with this passphrase.
Jan 3 21:09:57 usul emhttpd: shcmd (118): exit status: 2
Jan 3 21:09:57 usul emhttpd: shcmd (120): /usr/sbin/cryptsetup luksOpen /dev/md4 md4 --allow-discards --key-file=/root/keyfile
Jan 3 21:09:58 usul root: No key available with this passphrase.
Jan 3 21:09:58 usul emhttpd: shcmd (120): exit status: 2
Jan 3 21:09:58 usul emhttpd: shcmd (122): /usr/sbin/cryptsetup luksOpen /dev/md5 md5 --allow-discards --key-file=/root/keyfile
Jan 3 21:10:00 usul root: No key available with this passphrase.
Jan 3 21:10:00 usul emhttpd: shcmd (122): exit status: 2
Jan 3 21:10:00 usul emhttpd: shcmd (124): /usr/sbin/cryptsetup luksOpen /dev/md6 md6 --allow-discards --key-file=/root/keyfile
Jan 3 21:10:02 usul root: No key available with this passphrase.
Jan 3 21:10:02 usul emhttpd: shcmd (124): exit status: 2
Jan 3 21:10:02 usul emhttpd: shcmd (126): /usr/sbin/cryptsetup luksOpen /dev/md7 md7 --allow-discards --key-file=/root/keyfile
Jan 3 21:10:03 usul root: No key available with this passphrase.
Jan 3 21:10:03 usul emhttpd: shcmd (126): exit status: 2
Jan 3 21:10:03 usul emhttpd: shcmd (128): /usr/sbin/cryptsetup luksOpen /dev/md8 md8 --allow-discards --key-file=/root/keyfile
Jan 3 21:10:05 usul root: No key available with this passphrase.
Jan 3 21:10:05 usul emhttpd: shcmd (128): exit status: 2
Jan 3 21:10:05 usul emhttpd: shcmd (130): /usr/sbin/cryptsetup luksOpen /dev/md9 md9 --allow-discards --key-file=/root/keyfile
Jan 3 21:10:07 usul root: No key available with this passphrase.
Jan 3 21:10:07 usul emhttpd: shcmd (130): exit status: 2
Jan 3 21:10:07 usul emhttpd: shcmd (132): /usr/sbin/cryptsetup luksOpen /dev/md10 md10 --allow-discards --key-file=/root/keyfile
Jan 3 21:10:09 usul root: No key available with this passphrase.
Jan 3 21:10:09 usul emhttpd: shcmd (132): exit status: 2
Jan 3 21:10:09 usul emhttpd: Wrong encryption key

If I attempt to run one of the commands manually, I get:

Quote

root@usul:~# /usr/sbin/cryptsetup luksOpen /dev/md4 md4 --allow-discards --key-file=/root/keyfile
Device /dev/md4 does not exist or access denied.

Any help would be appreciated.

  • Author

Operator head space and timing...

1 hour ago, cesman said:

Operator head space and timing...

I guess, you solved it, can you share what was wrong and how you fixed it ?

This could help others in the future. :) 

  • 2 years later...

Could you share what you did, I restarted my server and unraid will no longer unencrypt. The keyfile thats worked for ages now fails.

 

No key available with this passphrase.

  • 11 months later...

Sorry for necro'ing this, but I have this exact problem. Could you share your solution?

Be sure the keyfile does not have a new line at the end.  The keyfile is one line of text with nothing else like a new line or carriage return.

The keyfile present in /root is identical to the one stored on my desktop. Loading from /root/ it fails, but when given the file from my desktop it starts.

 

I have copied the contents from my desktop file and echo'ed into the keyfile - still the same.

  • 4 months later...

bumping this thread as im facing the same issue but looks like i shouldn't expect any solutions.  

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.