starred/Ventoy-ventoy

Fork 0

mirror of https://github.com/ventoy/Ventoy.git synced 2026-03-03 00:07:49 -05:00

[issue]: CachyOS with systemd-boot as image bootloader does not find disk #2183

New issue

Open

opened 2026-02-20 21:20:36 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 21:20:36 -05:00

Owner

Originally created by @ptr1337 on GitHub (May 1, 2024).

Official FAQ

I have checked the official FAQ.

Ventoy Version

1.0.96

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

UEFI Mode

Partition Style

GPT

Disk Capacity

128GB

Disk Manufacturer

SanDISK

Image file checksum (if applicable)

No.

Image file download link (if applicable)

https://mirror.cachyos.org/ISO/testing/cachyos-kde-linux-240428.iso

What happened?

Hi,

On CachyOS we wanted to switch the bootloader to systemd-boot for the ISO due following archlinux upstream (https://gitlab.archlinux.org/archlinux/archiso/-/merge_requests/374).

Ventoy is not able to boot from the ISO and does not find the disk e.G:
Waiting 30 seconds for device /dev/disk/by-label/....

after that it fails.

We have tried multiple ways to detect the Image when systemd-boot is used:

Label
archisosearchuuid (https://gitlab.archlinux.org/archlinux/archiso/-/merge_requests/372)
archisodevice

Using GRUB 2 mode does fix the issues, but this is actually not a solution.

Second Issue, when Grub as ISO Bootloader is used

Additionally archlinux introduced recently including the ucode into the initramfs. When this mkinitcpio hook is used, it results also into a not bootable ISO with the grub bootloader.

Edit:
archiso 77 was used to build the ISO

Originally created by @ptr1337 on GitHub (May 1, 2024). ### Official FAQ - [X] I have checked the official FAQ. ### Ventoy Version 1.0.96 ### 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 UEFI Mode ### Partition Style GPT ### Disk Capacity 128GB ### Disk Manufacturer SanDISK ### Image file checksum (if applicable) No. ### Image file download link (if applicable) https://mirror.cachyos.org/ISO/testing/cachyos-kde-linux-240428.iso ### What happened? Hi, On CachyOS we wanted to switch the bootloader to systemd-boot for the ISO due following archlinux upstream (https://gitlab.archlinux.org/archlinux/archiso/-/merge_requests/374). Ventoy is not able to boot from the ISO and does not find the disk e.G: `Waiting 30 seconds for device /dev/disk/by-label/.... ` after that it fails. We have tried multiple ways to detect the Image when systemd-boot is used: - Label - archisosearchuuid (https://gitlab.archlinux.org/archlinux/archiso/-/merge_requests/372) - archisodevice Using GRUB 2 mode does fix the issues, but this is actually not a solution. Second Issue, when Grub as ISO Bootloader is used Additionally archlinux introduced recently including the ucode into the initramfs. When this mkinitcpio hook is used, it results also into a not bootable ISO with the grub bootloader. Edit: archiso 77 was used to build the ISO

deekerman added the

Fixed

label

2026-02-20 21:20:36 -05:00

deekerman commented

2026-02-20 21:20:39 -05:00

Author

Owner

@ventoy commented on GitHub (May 12, 2024):

This CI release should have fixed this issue.
https://github.com/ventoy/Ventoy/actions/runs/9048876467
https://www.ventoy.net/en/doc_github_ci.html

@ventoy commented on GitHub (May 12, 2024): This CI release should have fixed this issue. https://github.com/ventoy/Ventoy/actions/runs/9048876467 https://www.ventoy.net/en/doc_github_ci.html

deekerman commented

2026-02-20 21:20:39 -05:00

Author

Owner

@ptr1337 commented on GitHub (May 19, 2024):

This CI release should have fixed this issue. https://github.com/ventoy/Ventoy/actions/runs/9048876467 https://www.ventoy.net/en/doc_github_ci.html

Hi @ventoy, thanks this did resolve microcode issues.

Actually we are facing another, that mkinitcpio-archiso can not find the UUID, when using systemd-boot as bootloader on the ISO.
Grub as bootloader works. Also booting the ISO from etcher, rufus or QEMU does also work without problems. Only Ventoy provides problems.

This issue is not present on the archlinux ISO, im not sure, if there are any expections on archlinux set, so that is not happening on archlinux.

Weve set the same parameter for the bootflags as archlinux.
You can find the issue of the attached image:

I have also uploaded the failing ISO here , weve also increased the root wait to 10s, not that it would be to slow to find it.

https://archive.cachyos.org/iso/

Here the branch of the systemd-boot changes:
https://github.com/CachyOS/CachyOS-Live-ISO/tree/systemd-boot

@ptr1337 commented on GitHub (May 19, 2024): > This CI release should have fixed this issue. https://github.com/ventoy/Ventoy/actions/runs/9048876467 https://www.ventoy.net/en/doc_github_ci.html Hi @ventoy, thanks this did resolve microcode issues. Actually we are facing another, that mkinitcpio-archiso can not find the UUID, when using systemd-boot as bootloader on the ISO. Grub as bootloader works. Also booting the ISO from etcher, rufus or QEMU does also work without problems. Only Ventoy provides problems. This issue is not present on the archlinux ISO, im not sure, if there are any expections on archlinux set, so that is not happening on archlinux. Weve set the same parameter for the bootflags as archlinux. You can find the issue of the attached image: ![image](https://github.com/ventoy/Ventoy/assets/70081076/5fae242e-21a1-41d5-8aed-07150d49d994) I have also uploaded the failing ISO here , weve also increased the root wait to 10s, not that it would be to slow to find it. https://archive.cachyos.org/iso/ Here the branch of the systemd-boot changes: https://github.com/CachyOS/CachyOS-Live-ISO/tree/systemd-boot

deekerman commented

2026-02-20 21:20:40 -05:00

Author

Owner

@ptr1337 commented on GitHub (Jul 19, 2024):

This is not related. Update your ventoy to latst version

@ptr1337 commented on GitHub (Jul 19, 2024): This is not related. Update your ventoy to latst version