New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LUKSerror: luks device has no key/passphrase #1161

Open
Schopenberg opened this Issue Sep 3, 2015 · 8 comments

Comments

Projects
None yet
9 participants
@Schopenberg

This is my first issue submission, so please bear with me.

I'm attempting to install Qubes OS R3 (rc2) on a late 2008 Macbook Pro. None of the three kernels under "Troubleshooting" would work (graphics issues, it would seem), so I went into "basic graphics mode." I went through all the steps (time zone, installation source, yadda yadda yadda), and then ran into some errors. These errors popped up whether I chose LVM, BTRFS, or the other option whose name slips my mind (I mention this because I understand that LVM doesn't work well with Macs oftentimes, though I've managed to get it to work before).

I've included pictures of the output to save me the time of typing them all out (apologies if these are out of order).
img_1880
img_1881
img_1876
img_1873
img_1877
img_1878
img_1874
img_1875
img_1879

@marmarek marmarek added this to the Release 3.1 milestone Sep 5, 2015

@Piirtaa

This comment has been minimized.

Show comment
Hide comment
@Piirtaa

Piirtaa Nov 14, 2015

I get exactly the same error on a panasonic toughbook cf 19, mk 3. I've tried the same steps as well. Qubes 2 installed fine and didn't have this problem.

Piirtaa commented Nov 14, 2015

I get exactly the same error on a panasonic toughbook cf 19, mk 3. I've tried the same steps as well. Qubes 2 installed fine and didn't have this problem.

@SentinelX101

This comment has been minimized.

Show comment
Hide comment
@SentinelX101

SentinelX101 Nov 14, 2015

I also have the same problem when attempting to install Qubes OS Release 3.0 on a computer with an Nvidia graphics card that does not support anything other than basic graphics mode for installation.

Presumably the text only installer just forgets to ask for an encryption passphrase to set.

I also have the same problem when attempting to install Qubes OS Release 3.0 on a computer with an Nvidia graphics card that does not support anything other than basic graphics mode for installation.

Presumably the text only installer just forgets to ask for an encryption passphrase to set.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Nov 14, 2015

Member

Presumably the text only installer just forgets to ask for an encryption passphrase to set.

Yes. Even worse - text installed doesn't support password prompt.

The only way to feed LUKS password is to use kickstart file (unattended installation). Take a look at this thread: https://groups.google.com/d/msgid/qubes-users/54DA1BA0.6010305%40t-t-l.co.uk

Member

marmarek commented Nov 14, 2015

Presumably the text only installer just forgets to ask for an encryption passphrase to set.

Yes. Even worse - text installed doesn't support password prompt.

The only way to feed LUKS password is to use kickstart file (unattended installation). Take a look at this thread: https://groups.google.com/d/msgid/qubes-users/54DA1BA0.6010305%40t-t-l.co.uk

@egberts

This comment has been minimized.

Show comment
Hide comment
@egberts

egberts Sep 29, 2016

Looks like I got a VirtualBox video driver error, which prompted me to go into Anaconda text-mode.
qube

Would this be a new issue?

egberts commented Sep 29, 2016

Looks like I got a VirtualBox video driver error, which prompted me to go into Anaconda text-mode.
qube

Would this be a new issue?

@gjhami

This comment has been minimized.

Show comment
Hide comment
@gjhami

gjhami Feb 5, 2017

Excuse me if there's an obvious answer to this question, but why can't we just edit the code to use a hard coded password for encryption and then delete the password from that file later?

gjhami commented Feb 5, 2017

Excuse me if there's an obvious answer to this question, but why can't we just edit the code to use a hard coded password for encryption and then delete the password from that file later?

@g60ocR

This comment has been minimized.

Show comment
Hide comment
@g60ocR

g60ocR May 1, 2017

This is still an issue unfortunately.

g60ocR commented May 1, 2017

This is still an issue unfortunately.

@mikeshultz

This comment has been minimized.

Show comment
Hide comment
@mikeshultz

mikeshultz Oct 9, 2017

If the problem is indeed upstream, perhaps a maintainer could open a ticket, since the one submitted by a user was closed as Won't Fix.

If the problem is indeed upstream, perhaps a maintainer could open a ticket, since the one submitted by a user was closed as Won't Fix.

@santy2001

This comment has been minimized.

Show comment
Hide comment
@santy2001

santy2001 Jan 30, 2018

Same to me, installing on VmWare Qubes release 3.2 . I have to require the basic install method because the installation process doesn't start and stall in a black screen. So I switch to advanced install options and got this. :/

Same to me, installing on VmWare Qubes release 3.2 . I have to require the basic install method because the installation process doesn't start and stall in a black screen. So I switch to advanced install options and got this. :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment