Proxmox 9.1.5 stuck at initial ramdisk

[jboard]

I started using Proxmox at 9.1, everything was running fine for months, and doing the version upgrades have all worked.
Last update from 9.1.4 and it restarted and looked to be okay.
Maybe 48 hours later I noticed my truenas VM was down and I tried to log into Proxmox and it was not running.
No power issues and its on a PSU.

Being its headless I plunged in my 7" pi lcd to it and saw it was stuck at loading initial ramdisk.
I did try the BIOS setting from reading other forms and nothing worked.

When it boots and I don't see any advance options, it just starts Loading linux 6.17.9-1-pve.
ESC or Arrows won't stop it from starting either.

From the 9.1 ISO I down loaded today 4/16/26 I can boot into recovery and everything starts.
I'm just not sure what to do to fix my settings on the Boot disk?

I don't think its from the update, but I haven't done anything since. no new VM's no config changes..
Just boot and it runs.

any help would be great, I have no idea what logs to look at or what commands might fix this.
Linux is a leaning curve I've been enjoying.
Thanks Jason

 

[Impact]

Can you try to boot with the debug kernel arg? WHile you're there, can you show the kernel args you use? Do you use PCI(e) passthrough? How is that configured?

 

[jboard]

Can you try to boot with the debug kernel arg? WHile you're there, can you show the kernel args you use? Do you use PCI(e) passthrough? How is that configured?

That's the thing, Once the PC boots past the BIOS, I don't get any options. Right into booting Proxmox.
If I've booted from USB recovery. Can I edit the Boot of the OS drive somehow?

 

[jboard]

If you mean from the USB Boot, Yes. cat /proc/cmdline
BOOT_IMAGE=/boot/linux26 ro ramdisk_size=16777216 rw splash=verbose proxdebug proxtui

 

[Impact]

Once booted via rescue you can add it to the relevant config file, sure. Depends on bootloader.
Maybe updating the initramfs and grub (if used) already fixes your issue.

 

[jboard]

I have no idea how I would do that or what files I'd need to edit.
thanks for the pointers thus far. I'm not that good with Linux stuff.
I will search google and ask my AI, But AI has been making crap up and breaking things for me lately..

 

[Impact]

Figure out your bootloader, then edit the kernel args to include debug. Please don't quote every message you reply to.

 

[jboard]

Booting USB recovery then from Shell: running this command proxmox-boot-tool status.

Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.
(Not sure why it shows E: for the drive)

nano /etc/default/grub:

Looking at Grub, only stuff not commented below, plus added one for the line I replaced to try:
GRUB_DEFAULT=0
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`( . /etc/os-release && echo ${NAME} )`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt video=vesafbff video=efifbff initcall_blacklist=sysfb_init"
GRUB_CMDLINE_LINUX_DEFAULT="debug ignore_loglevel loglevel=7"
GRUB_CMDLINE_LINUX=""

After doing the Grub edit and running: update-grub, I see this.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.17.9-1-pve
Found initrd image: /boot/initrd.img-6.17.9-1-pve
Found linux image: /boot/vmlinuz-6.17.2-1-pve
Found initrd image: /boot/initrd.img-6.17.2-1-pve
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Adding boot menu entry for UEFI Firmware Settings ...

It did boot after, and I am seeing output errors now or general information.
going to try adding back in my other commands to see what breaks it again.

 

[Impact]

I you use code blocks these smiley go away and it looks nice. You seem to be using settings specific for GPU passthrough so it's kind of expected for the output to be stuck/black.

 

[jboard]

Impact, thank you for helping with this.
after everything was tried in grub I ended up swapped back to my normal settings.
I must have had a corrupt file not letting it boot and by running the update-grub command must have fixed it.
I wasn't able to login or ping my proxmox before and now it's back going.
For the passthrough it was for EMBY, not that its working so I should remove it.

I am going to run these and look though things more.
journalctl -b -1 > /home/prev_boot.log
dmesg > /home/dmesg.log

 

[Impact]

Maybe updating the initramfs and grub (if used) already fixes your issue.

I didn't fully expect it but glad that worked. I recommend using CTs when possible as they can share the GPU with the node and other CTs.