cryptsetup disc encryption âÂÂno key available with this passphraseâ - but password known 100% [closed]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
5
down vote
favorite
I try to decrypt my harddrive using the password that I 100% know. The password knowledge is not the problem.
Last thing I remember doing is: installing texlive. Not having enough disk space. Removing texlive again. followed by
apt update
apt upgrade
apt dist-upgrade
I remember the update had an error due to missing internet connection (wifi switch was off) After I switched on wifi, update, upgrade and dist-upgrade went (I don't remember otherwise) smoothly.
Starting my machine this morning brings me to the current state of affairs:
No key available with this passphrase
cryptsetup failed. bad password or option?
The password contains special characters - can I somehow test which
symbols are created by a keypress? Maybe the keyboard layout switched or somithing similar.
This problem is on Debian Jessie.
Except for header backups, what else can help me investigate?
debian luks
closed as unclear what you're asking by Rui F Ribeiro, schily, Jesse_b, slm⦠Jul 30 at 3:22
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |Â
up vote
5
down vote
favorite
I try to decrypt my harddrive using the password that I 100% know. The password knowledge is not the problem.
Last thing I remember doing is: installing texlive. Not having enough disk space. Removing texlive again. followed by
apt update
apt upgrade
apt dist-upgrade
I remember the update had an error due to missing internet connection (wifi switch was off) After I switched on wifi, update, upgrade and dist-upgrade went (I don't remember otherwise) smoothly.
Starting my machine this morning brings me to the current state of affairs:
No key available with this passphrase
cryptsetup failed. bad password or option?
The password contains special characters - can I somehow test which
symbols are created by a keypress? Maybe the keyboard layout switched or somithing similar.
This problem is on Debian Jessie.
Except for header backups, what else can help me investigate?
debian luks
closed as unclear what you're asking by Rui F Ribeiro, schily, Jesse_b, slm⦠Jul 30 at 3:22
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
Did your keyboard layout change for whatever reason, causing you to mistype the passphrase?
â Kusalananda
Jul 29 at 10:13
First thing I'd have tried from the GRUB menu would be to if using an older kernel changed anything. I also would have avoided special characters in the password, but that's of course not a lot of help after the fact.
â kasperd
Jul 29 at 16:57
add a comment |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I try to decrypt my harddrive using the password that I 100% know. The password knowledge is not the problem.
Last thing I remember doing is: installing texlive. Not having enough disk space. Removing texlive again. followed by
apt update
apt upgrade
apt dist-upgrade
I remember the update had an error due to missing internet connection (wifi switch was off) After I switched on wifi, update, upgrade and dist-upgrade went (I don't remember otherwise) smoothly.
Starting my machine this morning brings me to the current state of affairs:
No key available with this passphrase
cryptsetup failed. bad password or option?
The password contains special characters - can I somehow test which
symbols are created by a keypress? Maybe the keyboard layout switched or somithing similar.
This problem is on Debian Jessie.
Except for header backups, what else can help me investigate?
debian luks
I try to decrypt my harddrive using the password that I 100% know. The password knowledge is not the problem.
Last thing I remember doing is: installing texlive. Not having enough disk space. Removing texlive again. followed by
apt update
apt upgrade
apt dist-upgrade
I remember the update had an error due to missing internet connection (wifi switch was off) After I switched on wifi, update, upgrade and dist-upgrade went (I don't remember otherwise) smoothly.
Starting my machine this morning brings me to the current state of affairs:
No key available with this passphrase
cryptsetup failed. bad password or option?
The password contains special characters - can I somehow test which
symbols are created by a keypress? Maybe the keyboard layout switched or somithing similar.
This problem is on Debian Jessie.
Except for header backups, what else can help me investigate?
debian luks
edited Jul 29 at 13:18
Jeff Schaller
30.7k846104
30.7k846104
asked Jul 29 at 10:02
Ok Letsdothis
283
283
closed as unclear what you're asking by Rui F Ribeiro, schily, Jesse_b, slm⦠Jul 30 at 3:22
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by Rui F Ribeiro, schily, Jesse_b, slm⦠Jul 30 at 3:22
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, itâÂÂs hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
Did your keyboard layout change for whatever reason, causing you to mistype the passphrase?
â Kusalananda
Jul 29 at 10:13
First thing I'd have tried from the GRUB menu would be to if using an older kernel changed anything. I also would have avoided special characters in the password, but that's of course not a lot of help after the fact.
â kasperd
Jul 29 at 16:57
add a comment |Â
1
Did your keyboard layout change for whatever reason, causing you to mistype the passphrase?
â Kusalananda
Jul 29 at 10:13
First thing I'd have tried from the GRUB menu would be to if using an older kernel changed anything. I also would have avoided special characters in the password, but that's of course not a lot of help after the fact.
â kasperd
Jul 29 at 16:57
1
1
Did your keyboard layout change for whatever reason, causing you to mistype the passphrase?
â Kusalananda
Jul 29 at 10:13
Did your keyboard layout change for whatever reason, causing you to mistype the passphrase?
â Kusalananda
Jul 29 at 10:13
First thing I'd have tried from the GRUB menu would be to if using an older kernel changed anything. I also would have avoided special characters in the password, but that's of course not a lot of help after the fact.
â kasperd
Jul 29 at 16:57
First thing I'd have tried from the GRUB menu would be to if using an older kernel changed anything. I also would have avoided special characters in the password, but that's of course not a lot of help after the fact.
â kasperd
Jul 29 at 16:57
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
11
down vote
accepted
In GRUB (or whatever you're using as your bootloader), add this boot option to your kernel command line: break=premount
. It should give you a shell prompt while the system is still running on initramfs and the system has not yet made any attempts to mount the real root filesystem.
You can use this shell prompt to check your keyboard layout.
2
It was the special Characters. Keybiardlayout changed. Thank you!
â Ok Letsdothis
Jul 29 at 11:20
By the way: actually just pressing 'c' brought me to a commandline from Grub2
â Ok Letsdothis
Jul 29 at 11:22
2
Pressing 'c' brings you to the GRUB command prompt, which typically always uses the US English keyboard layout unless you customize your GRUB configuration specifically for that. This may or may not be the same keyboard layout thecryptsetup
password prompt uses. (However, if a keyboard layout gets changed on update, the most likely change is a fallback to factory default US English.)
â telcoM
Jul 29 at 11:28
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
11
down vote
accepted
In GRUB (or whatever you're using as your bootloader), add this boot option to your kernel command line: break=premount
. It should give you a shell prompt while the system is still running on initramfs and the system has not yet made any attempts to mount the real root filesystem.
You can use this shell prompt to check your keyboard layout.
2
It was the special Characters. Keybiardlayout changed. Thank you!
â Ok Letsdothis
Jul 29 at 11:20
By the way: actually just pressing 'c' brought me to a commandline from Grub2
â Ok Letsdothis
Jul 29 at 11:22
2
Pressing 'c' brings you to the GRUB command prompt, which typically always uses the US English keyboard layout unless you customize your GRUB configuration specifically for that. This may or may not be the same keyboard layout thecryptsetup
password prompt uses. (However, if a keyboard layout gets changed on update, the most likely change is a fallback to factory default US English.)
â telcoM
Jul 29 at 11:28
add a comment |Â
up vote
11
down vote
accepted
In GRUB (or whatever you're using as your bootloader), add this boot option to your kernel command line: break=premount
. It should give you a shell prompt while the system is still running on initramfs and the system has not yet made any attempts to mount the real root filesystem.
You can use this shell prompt to check your keyboard layout.
2
It was the special Characters. Keybiardlayout changed. Thank you!
â Ok Letsdothis
Jul 29 at 11:20
By the way: actually just pressing 'c' brought me to a commandline from Grub2
â Ok Letsdothis
Jul 29 at 11:22
2
Pressing 'c' brings you to the GRUB command prompt, which typically always uses the US English keyboard layout unless you customize your GRUB configuration specifically for that. This may or may not be the same keyboard layout thecryptsetup
password prompt uses. (However, if a keyboard layout gets changed on update, the most likely change is a fallback to factory default US English.)
â telcoM
Jul 29 at 11:28
add a comment |Â
up vote
11
down vote
accepted
up vote
11
down vote
accepted
In GRUB (or whatever you're using as your bootloader), add this boot option to your kernel command line: break=premount
. It should give you a shell prompt while the system is still running on initramfs and the system has not yet made any attempts to mount the real root filesystem.
You can use this shell prompt to check your keyboard layout.
In GRUB (or whatever you're using as your bootloader), add this boot option to your kernel command line: break=premount
. It should give you a shell prompt while the system is still running on initramfs and the system has not yet made any attempts to mount the real root filesystem.
You can use this shell prompt to check your keyboard layout.
answered Jul 29 at 11:08
telcoM
9,82111032
9,82111032
2
It was the special Characters. Keybiardlayout changed. Thank you!
â Ok Letsdothis
Jul 29 at 11:20
By the way: actually just pressing 'c' brought me to a commandline from Grub2
â Ok Letsdothis
Jul 29 at 11:22
2
Pressing 'c' brings you to the GRUB command prompt, which typically always uses the US English keyboard layout unless you customize your GRUB configuration specifically for that. This may or may not be the same keyboard layout thecryptsetup
password prompt uses. (However, if a keyboard layout gets changed on update, the most likely change is a fallback to factory default US English.)
â telcoM
Jul 29 at 11:28
add a comment |Â
2
It was the special Characters. Keybiardlayout changed. Thank you!
â Ok Letsdothis
Jul 29 at 11:20
By the way: actually just pressing 'c' brought me to a commandline from Grub2
â Ok Letsdothis
Jul 29 at 11:22
2
Pressing 'c' brings you to the GRUB command prompt, which typically always uses the US English keyboard layout unless you customize your GRUB configuration specifically for that. This may or may not be the same keyboard layout thecryptsetup
password prompt uses. (However, if a keyboard layout gets changed on update, the most likely change is a fallback to factory default US English.)
â telcoM
Jul 29 at 11:28
2
2
It was the special Characters. Keybiardlayout changed. Thank you!
â Ok Letsdothis
Jul 29 at 11:20
It was the special Characters. Keybiardlayout changed. Thank you!
â Ok Letsdothis
Jul 29 at 11:20
By the way: actually just pressing 'c' brought me to a commandline from Grub2
â Ok Letsdothis
Jul 29 at 11:22
By the way: actually just pressing 'c' brought me to a commandline from Grub2
â Ok Letsdothis
Jul 29 at 11:22
2
2
Pressing 'c' brings you to the GRUB command prompt, which typically always uses the US English keyboard layout unless you customize your GRUB configuration specifically for that. This may or may not be the same keyboard layout the
cryptsetup
password prompt uses. (However, if a keyboard layout gets changed on update, the most likely change is a fallback to factory default US English.)â telcoM
Jul 29 at 11:28
Pressing 'c' brings you to the GRUB command prompt, which typically always uses the US English keyboard layout unless you customize your GRUB configuration specifically for that. This may or may not be the same keyboard layout the
cryptsetup
password prompt uses. (However, if a keyboard layout gets changed on update, the most likely change is a fallback to factory default US English.)â telcoM
Jul 29 at 11:28
add a comment |Â
1
Did your keyboard layout change for whatever reason, causing you to mistype the passphrase?
â Kusalananda
Jul 29 at 10:13
First thing I'd have tried from the GRUB menu would be to if using an older kernel changed anything. I also would have avoided special characters in the password, but that's of course not a lot of help after the fact.
â kasperd
Jul 29 at 16:57