mirror of
https://github.com/ventoy/Ventoy.git
synced 2026-03-03 00:07:49 -05:00
Fedora 37 Cannot Boot with Ventoy 1.0.81 #1583
Labels
No labels
Denied Feature Request
File Corrupted
Fixed
Good practice
Not an issue
Not planed
USB 2.0/3.0
USB Hardware Issue
Wait Upstream Fix
bug
documentation
duplicate
enhancement
help wanted
question
wontfix
【Tested Image Report】
【Tested Image Report】
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Ventoy-ventoy#1583
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @linuxtopia on GitHub (Nov 16, 2022).
Official FAQ
Ventoy Version
1.0.81
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
16GB
Disk Manufacturer
SanDisk
Image file checksum (if applicable)
Yes.
Image file download link (if applicable)
https://download.fedoraproject.org/pub/fedora/linux/releases/37/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-37-1.7.iso
What happened?
Ventoy's latest release is not compatible with new released Fedora 37 isos. I have downloaded KDE, LXQT etc. all those working with virtualbox but cannot boot with Ventoy even with GRUB2 mode.
I cannot get bug log bur roughly message is kinda that:
dracut fatal failed to find a root filesystemdracut-initqueue wrong fs typeI hope you'll find a solution and update Ventoy.
Thanks
@ventoy commented on GitHub (Nov 16, 2022):
Checksum the ISO file as follows:
https://www.ventoy.net/static/img/filechecksum.gif
@linuxtopia commented on GitHub (Nov 16, 2022):
very weird, original file on my sdd matches checksum but copied version on usb does not. how to solve this?
edit:
I think the issue was related to my usb port then changed it and iso copied to the usb with exact sha256 value. so my issue solved.
thanks
@ventoy commented on GitHub (Nov 16, 2022):
If you use Linux, you can run
synccommand in the terminal after you copy the ISO file to the USB.