Skip to content
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

Archinstall crashing when trying to create LUKS Encrypted Btrfs installation #2735

Closed
0xDezzy opened this issue Oct 17, 2024 · 3 comments · Fixed by #2745
Closed

Archinstall crashing when trying to create LUKS Encrypted Btrfs installation #2735

0xDezzy opened this issue Oct 17, 2024 · 3 comments · Fixed by #2745

Comments

@0xDezzy
Copy link

0xDezzy commented Oct 17, 2024

Which ISO version are you using?

2024.10.01

The installation log

https://0x0.st/XIum.log

describe the problem

Description of the issue

I was installing using a VMWare workstation VM with my second physical disk passed through to it

Then it failed when trying to actually install arch while trying to partition the disks.

@0xDezzy 0xDezzy closed this as completed Oct 17, 2024
@0xDezzy 0xDezzy reopened this Oct 17, 2024
@svartkanin
Copy link
Collaborator

Hmm I run an installation with your config and everything installed just fine, the encryption worked as expected. Looking at the config I also can't see anything that might cause the issue as your using the default layouts.
Best answer I have atm is to run it again?

@0xDezzy
Copy link
Author

0xDezzy commented Oct 18, 2024

I took a deeper look and it was due to a residual LUKS header on one of the partitions. I overwrote the first gig of each partition to be sure and it worked after that, but then I encountered a different issue with the keyring sync. I noticed a separate issue about that but I'll focus on this issue here.

Is there a way we can make sure that the archinstall script formats the disk to prevent this issue when trying to install over an existing LUKS partition? I tested a few things to make sure that it was the existing LUKS partition with a key and sure enough that was the issue. I had an install of Endeavour OS that I was trying to install over and then this issue popped up. To fix it I ran dd if=/dev/zero of=/dev/nvme0n1px bs=1M count=1024 status=progress where x was the partition and it worked after that.

@svartkanin
Copy link
Collaborator

I wasn't able to reproduce this, but I've raised a fix that should hopefully fix the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants