starred/Ventoy-ventoy

Fork 0

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

[issue]: SLES via GRUB needs ptoptions=+rdinit #2436

New issue

Open

opened 2026-02-20 22:00:38 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 22:00:38 -05:00

Owner

Originally created by @jirib on GitHub (Feb 20, 2025).

Official FAQ

I have checked the official FAQ.

Ventoy Version

1.1.02

What about latest release

No. I didn't try the latest release.

Try alternative boot mode

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

BIOS Mode

Legacy BIOS Mode

Partition Style

MBR

Disk Capacity

32GB

Disk Manufacturer

No response

Image file checksum (if applicable)

None

Image file download link (if applicable)

No response

What happened?

GRUB's rdinit=/vtoy/vtoy impacts SLES (OpenSUSE most likely as well, but untested) final bootloader boot parameters and after the installation completed, SLES does not boot with kernel panic pointing to Unable to mount root fs.

Resolution

The problem is the presence of kernel parameter rdinit,
one can exclude those kernel parameters to be available to the
installer via linuxrc ptoptions.

An example:

ptoptions=+rdinit

Cause

The installer reads Cmdline value from linuxrc options, which
"inherits" most of boot parameters, and adopt its value as boot
parameters to be added into the final bootloader configuration.
clearly, some kernel boot parameters might have an impact
(eg. rdinit).

Additional information

linuxrc ptoptions (boot) parameter causes removal of its value
from Cmdline option in /etc/install.inf in the installer
environment; this file is later read by the installer and would
exclude this value to appear in the bootloader boot parameters.

Ventoy adds boot parameter rdinit (here: rdinit=/vtoy/vtoy).

One might use linuxrc startshell=1 boot parameter to inspect the
content of /etc/install.inf before the installer itself is started.

Examples:

default

# grep rdinit /etc/install.inf
Cmdline: splash=silent rdinit=/vtoy/vtoy

customized boot with ptoptions=+rdinit

# grep rdinit /etc/install.inf
rdinit: /vtoy/vtoy

Not really a bug but maybe add it to FAQ?

Originally created by @jirib on GitHub (Feb 20, 2025). ### Official FAQ - [x] I have checked the official FAQ. ### Ventoy Version 1.1.02 ### What about latest release No. I didn't try the latest release. ### Try alternative boot mode No. I didn't try these alternative boot modes. ### BIOS Mode Legacy BIOS Mode ### Partition Style MBR ### Disk Capacity 32GB ### Disk Manufacturer _No response_ ### Image file checksum (if applicable) None ### Image file download link (if applicable) _No response_ ### What happened? GRUB's `rdinit=/vtoy/vtoy` impacts SLES (OpenSUSE most likely as well, but untested) final bootloader boot parameters and after the installation completed, SLES does not boot with kernel panic pointing to `Unable to mount root fs`. Resolution ---------- The problem is the presence of kernel parameter `rdinit`, one can exclude those kernel parameters to be available to the installer via _linuxrc_ `ptoptions`. An example: ``` ptoptions=+rdinit ``` Cause ----- The installer reads `Cmdline` value from _linuxrc_ options, which "inherits" most of boot parameters, and adopt its value as boot parameters to be added into the final bootloader configuration. clearly, some kernel boot parameters might have an impact (eg. `rdinit`). Additional information ---------------------- _linuxrc_ `ptoptions` (boot) parameter causes removal of its value from `Cmdline` option in `/etc/install.inf` in the installer environment; this file is later read by the installer and would exclude this value to appear in the bootloader boot parameters. Ventoy adds boot parameter `rdinit` (here: `rdinit=/vtoy/vtoy`). One might use _linuxrc_ `startshell=1` boot parameter to inspect the content of `/etc/install.inf` before the installer itself is started. Examples: - default ``` # grep rdinit /etc/install.inf Cmdline: splash=silent rdinit=/vtoy/vtoy ``` - customized boot with `ptoptions=+rdinit` ``` # grep rdinit /etc/install.inf rdinit: /vtoy/vtoy ``` Not really a bug but maybe add it to FAQ?

deekerman added the

Fixed

label

2026-02-20 22:00:38 -05:00

deekerman commented

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

Author

Owner

@ventoy commented on GitHub (Feb 20, 2025):

You boot SLE iso file in normal mode or grub2 mode?

@ventoy commented on GitHub (Feb 20, 2025): You boot SLE iso file in normal mode or grub2 mode?

deekerman commented

2026-02-20 22:00:41 -05:00

Author

Owner

@jirib commented on GitHub (Feb 20, 2025):

You boot SLE iso file in normal mode or grub2 mode?

grub mode; only there I saw rdinit=/vtoy/vtoy in /proc/cmdline.

@jirib commented on GitHub (Feb 20, 2025): > You boot SLE iso file in normal mode or grub2 mode? grub mode; only there I saw `rdinit=/vtoy/vtoy` in `/proc/cmdline`.

deekerman commented

2026-02-20 22:00:41 -05:00

Author

Owner

@ventoy commented on GitHub (Feb 20, 2025):

Please try this CI release:
https://github.com/ventoy/Ventoy/actions/runs/13437130548
https://ventoy.net/en/doc_github_ci.html

@ventoy commented on GitHub (Feb 20, 2025): Please try this CI release: https://github.com/ventoy/Ventoy/actions/runs/13437130548 https://ventoy.net/en/doc_github_ci.html

deekerman commented

2026-02-20 22:00:41 -05:00

Author

Owner

@ventoy commented on GitHub (Feb 21, 2025):

It should be fixed in the latest 1.1.03 release, please test.

@ventoy commented on GitHub (Feb 21, 2025): It should be fixed in the latest 1.1.03 release, please test.