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

[issue]: Ventoy2Disk creates LUKS encrypted first partition #2490

Open
1 task done
returnofblank opened this issue Jul 19, 2023 · 2 comments
Open
1 task done

[issue]: Ventoy2Disk creates LUKS encrypted first partition #2490

returnofblank opened this issue Jul 19, 2023 · 2 comments

Comments

@returnofblank
Copy link

returnofblank commented Jul 19, 2023

Official FAQ

  • I have checked the official FAQ.

Ventoy Version

1.0.93

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

Both

Partition Style

MBR

Disk Capacity

256GB

Disk Manufacturer

Samsung

Image file checksum (if applicable)

Yes.

Image file download link (if applicable)

No response

What happened?

When using any Ventoy installation method in Linux, the first partition where the ISOs are stored is encrypted with LUKS. I have tried both MBR and GPT, secure boot on and off, the CLI version and GUI version and the Web version.

No passphrase works, I have tried an empty string, the root password.

I am running this on Fedora 38.

Screenshot from 2023-07-19 15-52-57

@DaniilSkLi
Copy link

What worked for me was deleting all partitions and creating 1 fat32 partition on the flash drive, via gparted. After that I restarted the ventoy utility and installed again. Now I don't have a LUKS partition, but a regular exFat partition.

@tastytea
Copy link

i had the same problem and the workaround fixed it for me.

i did have an encrypted GPT-partition before, then created a new MBR partition layout before using Ventoy. since the partiion doesn't get actually deleted but just removed from the table, maybe that interfered somehow? 🤔

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

No branches or pull requests

3 participants