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

Proxmox v8.1.2: stuck at "Loading initial ramdisk" after fresh install #2782

Open
1 task done
pjotrek-b opened this issue Mar 20, 2024 · 4 comments
Open
1 task done

Comments

@pjotrek-b
Copy link

Official FAQ

  • I have checked the official FAQ.

Ventoy Version

1.0.97

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

64 GB

Disk Manufacturer

Transcend

Image file checksum (if applicable)

Yes.

Image file download link (if applicable)

No response

What happened?

After successfully installing Proxmox v8.1-2 (2024-02-07) using Ventoy, Proxmox-boot gets stucks at: "Loading initial ramdisk"

The issue was that Ventoy left the string rdinit=/vtoy/vtoy as kernel option in /etc/default/grub.d/installer.cfg.

Workaround:
After booting the Proxmox ISO (using Ventoy) in recovery mode, then removing this rdinit parameter completely and running "update-grub" afterwards, the Proxmox system boots fine. 😄

See:
https://forum.proxmox.com/threads/ventoy-install-of-proxmox-8-1-halts-at-loading-initial-ramdisk.143196/

@bryzgalovkv
Copy link

Thank you, smart man!

@Ikariusrb
Copy link

Ikariusrb commented Apr 28, 2024

Confirming I encountered the same problem both with proxmox 8.1-2 and with the latest 8.2-1. The documented fix works, but had to track down this bug after trying a number of options. If it's useful, the problem did not occur on a Beelink SER5 box, but did occur on a GMKTek nucbox M5 pro.

The GMTek M5 also required setting the Advanced CPU -> NX mode to "enabled" in order for proxmox to install (otherwise it fails to mount the efivars FS and halts the install), but that appears to be all on proxmox and unrelated to ventoy. Mentioning it here in hopes it helps out some other hapless googler.

@aldosr
Copy link

aldosr commented May 12, 2024

Confirming the same issue on an Hp EliteDesk 800 g4 using Proxmox 8.2 and Ventoy 1.0.97. Anyway, can confirm that the steps suggested above solved the problem!

@WhyDoWeLiveWithoutMeaning

😭😭😭😭😭😭

all my problems were immediately solved when I read this thread. After spending 12 hours trying to figure out what was wrong with my server. TURNS OUT THERE WAS NOTHING, this cancerous bug has caused me great mental turmoil, festering distrust in myself and my systems. But it was one little itty bitty installation medium all along.
I switched to rufus just to install it and it worked first try with 0 errors whatsoever.

Tl;dr please fix this

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

5 participants