DM-Crypt does not accept passphrase
up vote
0
down vote
favorite
The partition table is:
sda1 - /boot
sda2 - dmcrypt with LVM, containing root, home and swap volumes
Cryptsetup does not accept passphrase, that have been used for a long time and can not have any mistakes.
I tried to mount it using PXE Live Ubuntu:
root@ubuntu:~# cryptsetup luksOpen /dev/sda2 vgroot
Enter passphrase for /dev/sda2:
No key available with this passphrase.
On the live image US keyboard layot is only one by default. Copying and pasting of passphrase does not help too.
A month ago I have successfully mounted the dm-crypt on the same live image to chroot.
I have Ubuntu 14.04 installed and 13.10 live image on PXE boot.
encryption lvm dmcrypt
asked Jan 23 '15 at 9:34
Dinarx
111
add a comment |
up vote
0
down vote
favorite
The partition table is:
sda1 - /boot
sda2 - dmcrypt with LVM, containing root, home and swap volumes
Cryptsetup does not accept passphrase, that have been used for a long time and can not have any mistakes.
I tried to mount it using PXE Live Ubuntu:
root@ubuntu:~# cryptsetup luksOpen /dev/sda2 vgroot
Enter passphrase for /dev/sda2:
No key available with this passphrase.
On the live image US keyboard layot is only one by default. Copying and pasting of passphrase does not help too.
A month ago I have successfully mounted the dm-crypt on the same live image to chroot.
I have Ubuntu 14.04 installed and 13.10 live image on PXE boot.
encryption lvm dmcrypt
asked Jan 23 '15 at 9:34
Dinarx
111
And did anything happen last month when you "mounted the dm-crypt on the same live image to chroot"? Something changed/overwritten?
– Xen2050
Jan 25 '15 at 8:16
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
The partition table is:
sda1 - /boot
sda2 - dmcrypt with LVM, containing root, home and swap volumes
Cryptsetup does not accept passphrase, that have been used for a long time and can not have any mistakes.
I tried to mount it using PXE Live Ubuntu:
root@ubuntu:~# cryptsetup luksOpen /dev/sda2 vgroot
Enter passphrase for /dev/sda2:
No key available with this passphrase.
On the live image US keyboard layot is only one by default. Copying and pasting of passphrase does not help too.
A month ago I have successfully mounted the dm-crypt on the same live image to chroot.
I have Ubuntu 14.04 installed and 13.10 live image on PXE boot.
encryption lvm dmcrypt
asked Jan 23 '15 at 9:34
Dinarx
111
The partition table is:
sda1 - /boot
sda2 - dmcrypt with LVM, containing root, home and swap volumes
Cryptsetup does not accept passphrase, that have been used for a long time and can not have any mistakes.
I tried to mount it using PXE Live Ubuntu:
root@ubuntu:~# cryptsetup luksOpen /dev/sda2 vgroot
Enter passphrase for /dev/sda2:
No key available with this passphrase.
On the live image US keyboard layot is only one by default. Copying and pasting of passphrase does not help too.
A month ago I have successfully mounted the dm-crypt on the same live image to chroot.
I have Ubuntu 14.04 installed and 13.10 live image on PXE boot.
encryption lvm dmcrypt
encryption lvm dmcrypt
asked Jan 23 '15 at 9:34
Dinarx
111
asked Jan 23 '15 at 9:34
Dinarx
111
asked Jan 23 '15 at 9:34
Dinarx
111
asked Jan 23 '15 at 9:34
Dinarx
111
asked Jan 23 '15 at 9:34
Dinarx
111
111
And did anything happen last month when you "mounted the dm-crypt on the same live image to chroot"? Something changed/overwritten?
– Xen2050
Jan 25 '15 at 8:16
add a comment |
And did anything happen last month when you "mounted the dm-crypt on the same live image to chroot"? Something changed/overwritten?
– Xen2050
Jan 25 '15 at 8:16
And did anything happen last month when you "mounted the dm-crypt on the same live image to chroot"? Something changed/overwritten?
– Xen2050
Jan 25 '15 at 8:16
And did anything happen last month when you "mounted the dm-crypt on the same live image to chroot"? Something changed/overwritten?
– Xen2050
Jan 25 '15 at 8:16
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Well, the error "No key available with this passphrase" sounds like the key you're looking for is not in the LUKS header anymore. Could be the wrong passphrase, or could be something happened to that key, or the whole LUKS header. If you have a backup of the LUKS header you can try using it with the cryptsetup option --header
And try the --verbose & --debug options too, maybe there'll be more info revealed. The action isLuks -v <device> might be helpful to see if it's still a recognizable LUKS device.
And like the man cryptsetup page describes below, a LUKS header backup is important, (and look into the luksHeaderBackup and luksHeaderRestore actions too):
LUKS header: If the header of a LUKS volume gets damaged, all data is permanently lost unless
you have a header-backup. If a key-slot is damaged, it can only be restored from a header-
backup or if another active key-slot with known passphrase is undamaged. Damaging the LUKS
header is something people manage to do with surprising frequency. This risk is the result of
a trade-off between security and safety, as LUKS is designed for fast and secure wiping by
just overwriting header and key-slot area.
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Well, the error "No key available with this passphrase" sounds like the key you're looking for is not in the LUKS header anymore. Could be the wrong passphrase, or could be something happened to that key, or the whole LUKS header. If you have a backup of the LUKS header you can try using it with the cryptsetup option --header
And try the --verbose & --debug options too, maybe there'll be more info revealed. The action isLuks -v <device> might be helpful to see if it's still a recognizable LUKS device.
And like the man cryptsetup page describes below, a LUKS header backup is important, (and look into the luksHeaderBackup and luksHeaderRestore actions too):
LUKS header: If the header of a LUKS volume gets damaged, all data is permanently lost unless
you have a header-backup. If a key-slot is damaged, it can only be restored from a header-
backup or if another active key-slot with known passphrase is undamaged. Damaging the LUKS
header is something people manage to do with surprising frequency. This risk is the result of
a trade-off between security and safety, as LUKS is designed for fast and secure wiping by
just overwriting header and key-slot area.
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
add a comment |
up vote
0
down vote
Well, the error "No key available with this passphrase" sounds like the key you're looking for is not in the LUKS header anymore. Could be the wrong passphrase, or could be something happened to that key, or the whole LUKS header. If you have a backup of the LUKS header you can try using it with the cryptsetup option --header
And try the --verbose & --debug options too, maybe there'll be more info revealed. The action isLuks -v <device> might be helpful to see if it's still a recognizable LUKS device.
And like the man cryptsetup page describes below, a LUKS header backup is important, (and look into the luksHeaderBackup and luksHeaderRestore actions too):
LUKS header: If the header of a LUKS volume gets damaged, all data is permanently lost unless
you have a header-backup. If a key-slot is damaged, it can only be restored from a header-
backup or if another active key-slot with known passphrase is undamaged. Damaging the LUKS
header is something people manage to do with surprising frequency. This risk is the result of
a trade-off between security and safety, as LUKS is designed for fast and secure wiping by
just overwriting header and key-slot area.
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
add a comment |
up vote
0
down vote
up vote
0
down vote
Well, the error "No key available with this passphrase" sounds like the key you're looking for is not in the LUKS header anymore. Could be the wrong passphrase, or could be something happened to that key, or the whole LUKS header. If you have a backup of the LUKS header you can try using it with the cryptsetup option --header
And try the --verbose & --debug options too, maybe there'll be more info revealed. The action isLuks -v <device> might be helpful to see if it's still a recognizable LUKS device.
And like the man cryptsetup page describes below, a LUKS header backup is important, (and look into the luksHeaderBackup and luksHeaderRestore actions too):
LUKS header: If the header of a LUKS volume gets damaged, all data is permanently lost unless
you have a header-backup. If a key-slot is damaged, it can only be restored from a header-
backup or if another active key-slot with known passphrase is undamaged. Damaging the LUKS
header is something people manage to do with surprising frequency. This risk is the result of
a trade-off between security and safety, as LUKS is designed for fast and secure wiping by
just overwriting header and key-slot area.
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
Well, the error "No key available with this passphrase" sounds like the key you're looking for is not in the LUKS header anymore. Could be the wrong passphrase, or could be something happened to that key, or the whole LUKS header. If you have a backup of the LUKS header you can try using it with the cryptsetup option --header
And try the --verbose & --debug options too, maybe there'll be more info revealed. The action isLuks -v <device> might be helpful to see if it's still a recognizable LUKS device.
And like the man cryptsetup page describes below, a LUKS header backup is important, (and look into the luksHeaderBackup and luksHeaderRestore actions too):
LUKS header: If the header of a LUKS volume gets damaged, all data is permanently lost unless
you have a header-backup. If a key-slot is damaged, it can only be restored from a header-
backup or if another active key-slot with known passphrase is undamaged. Damaging the LUKS
header is something people manage to do with surprising frequency. This risk is the result of
a trade-off between security and safety, as LUKS is designed for fast and secure wiping by
just overwriting header and key-slot area.
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
answered Jan 25 '15 at 8:16
Xen2050
6,64212142
6,64212142
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f576848%2fdm-crypt-does-not-accept-passphrase%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
And did anything happen last month when you "mounted the dm-crypt on the same live image to chroot"? Something changed/overwritten?
– Xen2050
Jan 25 '15 at 8:16