Proxmox VE 9.0-1 install via Ventoy - kernel panic

[andreworg]

Hi,
I'd like to share what happened to me today, hoping that it will save others some sweat.

I installed Proxmox VE from the latest ISO (currently 9.0-1) after booting it through Ventoy.
The installed system could not boot; I got a purple screen with the following message:

KERNEL PANIC!
Please reboot your computer.
VFS: unable to mount root fs on unknown-block(0,0)

I finally found the root issue: the installer carried over to the installed system a kernel parameter that was clearly injected by Ventoy working in GRUB mode:

linux /boot/vmlinuz-6.14.8-2-pve root=/dev/mapper/pve-root ro rdinit=/vtoy/vtoy quiet

the rdinit=/vtoy/vtoy parameter was clearly the culprit.

I actually found some reference to this issue, along with a resolution, on other threads. But I decided to post this anyway.
I'm not 100% sure, but if I got everything right, this may be an installer issue that may be addressed.

Happy hacking, -a

 

[johnw40223]

could you walk me through that a little better a am new to linux world having the same issue. not sure where to go to make that change. any help would be greatful thanks

 

[andreworg]

I haven't got the system available right now, just following my notes.

Boot into rescue mode, then remove any occurrence of rdinit=/vtoy/vtoy from /boot/grub/grub.cfg .

These commands might help you do that:

# Remove the problematic parameter
sed -i 's/ rdinit=\/vtoy\/vtoy//g' /boot/grub/grub.cfg

# Verify it's removed - should return nothing
grep rdinit /boot/grub/grub.cfg

Then of course reboot.

 

[johnw40223]

thanks so much for getting back so fast i going to try now,

 

[johnw40223]

it worked thanks so much, their was alot to remove like 8 or more line of vtoy in the code

 

[andreworg]

Glad I helped you and possibly others that will eventually fall into Ventoy's "GRUB mode" trap as I did.

Happy hacking, -a