[SOLVED] Error: bad shim signature on 6.8.12-5-pve kernel

R

rtorres

Member
Apr 3, 2024
47
10
8
33
Stockton, CA
Hello all,

Seems like the issue I was having where I couldn't install Proxmox with UEFI enabled because I was getting a SHIM error is coming up with the lates 6.8.12-5-pve kernel.

Code: 
Loading Linux 6.8.12-5-pve ...
error: bad shim signature.
Loading initial ramdisk ...
error: you need to load the kernel first.

Press any key to continue...

The issue was fixed in the previous Proxmox 8.2-2 iso revision, but seems like it's popped up again. [Related thread]

After the error message and selecting 6.8.12-4-pve, the system boots up normally - no error message.

Any way to get the latest kernel fixed? I still have 6.8.12-5-pve install but reverted (pinned) back to 6.8.12-4-pve. I wanted to see if anyone new of a way to make sure any future kernel updates are installed without this issue popping up.

This is a fresh Proxmox Version 8.3 install. Installed with secure boot enabled with no issues, just when I upgraded to the latest kernel is when this issue popped up.

Thanks!
 
Last edited:
that's a very different error though.. it seems like the -5 kernel got moved to the public test repo without its signed counter part. should hopefully be corrected soon, I'll update this thread once it's done. thanks for the heads-up in any case!
 
  • Like
Reactions: rtorres
fabian said:
that's a very different error though.. it seems like the -5 kernel got moved to the public test repo without its signed counter part. should hopefully be corrected soon, I'll update this thread once it's done. thanks for the heads-up in any case!
Click to expand...
Thank you for replying, Fabian! I know we've been bugging you about the shim issues, just know your help is greatly appreciated!

Another thing I'd like to add that I didn't add to the error message is, it'll say it tried use default and the fallback but failed and will boot into the grub menu.

Nonetheless, thank you!
 
the signed package is now available in pmg/pve/pbstest, switching over should work.
 
  • Like
Reactions: rtorres
you need to install "proxmox-kernel-6.8.12-5-pve-signed"
 
  • Like
Reactions: rtorres
did you run `apt update` before trying?
 
fabian said:
did you run `apt update` before trying?
Click to expand...
Yessir! did apt update, didn't see anything new so I rebooted and tried again but same results.

I also went the extra and did 'apt clean' and 'rm -rf /var/lib/apt/lists/*' , ran 'apt update'. 0 updates, couldn't run 'apt install proxmox-kernel-6.8.12-5-pve-signed' (same error as above) nor was I able to find by checking 'apt-cache search x'
 
Last edited:
could you try once more?
 
thanks for the quick report and follow-ups :) we'll add additional checks to our infra so that it doesn't happen again.
 
Hello, I had same issue, as @rtorres. Yes, update "you need to install "proxmox-kernel-6.8.12-5-pve-signed" worked to mee too, BUT, now I have another issue:

- proxmox is starting correctly and all VMS/LXC are up und running, but

the system console, is "Stuck On Loading Initial Ramdisk"....

Non of the solutions which I found on the net helped?
- I deactivated TPM
- no ventoy ... ?
 
you mean the physical console of the PVE host? or the virtual one available over the UI?

if it's the former, which GPU does your system have?
 
Thank you for your question: I mean the physical console (HDMI) to a old HP Elite Desk 800 G3. I guess it is a Intel HD Graphics 530.

I had this same PC in an Proxmox-Cluster for at leas 1 Year without any problems.

UPDATE: Sorry, it is a HD Graphics 530.
 
Last edited:
I'd double check the boot log, maybe something can be found there (missing module, warning, firmware, ..)
 
fabian said:
I'd double check the boot log, maybe something can be found there (missing module, warning, firmware, ..)
Click to expand...
Hello, I was running: journalctl -b --priority=err

root@pve1:/var/log# journalctl -b --priority=err
Dec 05 13:14:24 pve1 kernel: x86/cpu: SGX disabled by BIOS.
Dec 05 13:14:24 pve1 systemd-modules-load[371]: Failed to find module 'vfio_virqfd'
Dec 05 13:14:24 pve1 kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000dd0945ec (20230628/exre>
Dec 05 13:14:24 pve1 kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20230628/dswexec-433)
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:24 pve1 kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000eca918c8 (20230628/exre>
Dec 05 13:14:24 pve1 kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20230628/dswexec-433)
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:24 pve1 kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000555a6311 (20230628/exre>
Dec 05 13:14:24 pve1 kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20230628/dswexec-433)
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:24 pve1 kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000a89ac587 (20230628/exre>
Dec 05 13:14:24 pve1 kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20230628/dswexec-433)
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:24 pve1 kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (202>
Dec 05 13:14:29 pve1 pmxcfs[1250]: [quorum] crit: quorum_initialize failed: 2
Dec 05 13:14:29 pve1 pmxcfs[1250]: [quorum] crit: can't initialize service
Dec 05 13:14:29 pve1 pmxcfs[1250]: [confdb] crit: cmap_initialize failed: 2
Dec 05 13:14:29 pve1 pmxcfs[1250]: [confdb] crit: can't initialize service
Dec 05 13:14:29 pve1 pmxcfs[1250]: [dcdb] crit: cpg_initialize failed: 2
Dec 05 13:14:29 pve1 pmxcfs[1250]: [dcdb] crit: can't initialize service
Dec 05 13:14:29 pve1 pmxcfs[1250]: [status] crit: cpg_initialize failed: 2
Dec 05 13:14:29 pve1 pmxcfs[1250]: [status] crit: can't initialize service
Dec 05 13:23:56 pve1 pveproxy[1943]: detected empty handle
Dec 05 13:24:00 pve1 pveproxy[1943]: detected empty handle
Dec 05 14:03:50 pve1 pveproxy[27511]: got inotify poll request in wrong process - disabling inotify


as far as I understand, there are no errors critical, or related to my problem of stuck "initial ramdisk loading.."?

What are your findings? Regards
 
the full journal is probably more interesting, such things often just get logged as warning or info message..
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom