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]: install to disk - GPT warning does not allow to continue on Linux #2593

Open
1 task done
gerbrent opened this issue Oct 2, 2023 · 1 comment
Open
1 task done

Comments

@gerbrent
Copy link

gerbrent commented Oct 2, 2023

Official FAQ

  • I have checked the official FAQ.

Ventoy Version

1.0.95 x86_64

What about latest release

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

Try alternative boot mode

No. I didn't try these alternative boot modes.

BIOS Mode

Legacy BIOS Mode

Partition Style

GPT

Disk Capacity

32GB

Disk Manufacturer

SanDisk

Image file checksum (if applicable)

Yes.

Image file download link (if applicable)

https://sourceforge.net/projects/ventoy/files/v1.0.95

What happened?

On attempting to install to a previously used USB drive via Linux (openSUSE Tumbleweed), a GPT partition warning appeared. Issue is: the Ventoy install script does not offer a user-friendly method to continue through this situation. This appears to be a warning generated from within parted:

Warning: Not all of the space available to /dev/sdc appears to be used, you can fix the GPT to use all of the space (an extra 57730768 blocks) or continue with the current setting?

Once this warning appears, no obvious means to continue/make a choice are offered to the user.
Upon keyboard mashing and hitting enter, and a slight pause, it becomes obvious it is in fact asking for an internal parted command.

Peek 2023-10-02 14-19

Expected behaviour:

the correct option is presented to the user to rectify the disk formatting situation, which allows the user to proceed to install Ventoy once corrected.

@ventoy
Copy link
Owner

ventoy commented Oct 6, 2023

It should have been fixed in 1.0.96

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

2 participants