Error - Proxmox VE 6.3 - Firmware Bug: TSC_DEADLINE - ASUS - First installation

[RSMAN]

Hello,

I am trying to install Proxmox VE 6.3-1 for the first time on my ASUS motherboard (Z97) and I get the following error message.
I updated the BIOS for the last version, but the problem is the same!
Do you have any idea how to fix this problem?

 

[leesteken]

The firmware bug is not an issue. Your problem is that the installer does not recognize the installation medium (no cdrom found even though the USB-drive was detected as /dev/sdc). Are you sure the ISO was written to the USB-stick correctly?

 

[RSMAN]

Hello avw, thanks for your help!
I think so, I used "balenaEtcher-Portable-1.5.114" to make the key, I also tried with "rufus-3.13p" in different modes, same problem.
What method do you use to create the key?

 

[leesteken]

What method do you use to create the key?

Maybe thiss post can help? Or this or this one maybe? It would appear that using dd from Linux works best.

 

[t.lamprecht]

Use one of our officialy documented ways: https://pve.proxmox.com/pve-docs/chapter-pve-installation.html#installation_prepare_media

 

[RSMAN]

Same problem with Rufus in DD mode!

 

[RSMAN]

Use one of our officialy documented ways: https://pve.proxmox.com/pve-docs/chapter-pve-installation.html#installation_prepare_media

Thank you!
I only have a Windows computer, I also tried with Rufus and Etcher, I spent the day on it, I am stuck :/

 

[t.lamprecht]

We only heard positive feedback for using either etcher or rufus, at least if used in DD mode, so this is a bit weird..

Are you sure that the downloaded ISO is OK and the USB pen drive has no issues?

If that is all well, please post the output of the following commands from inside the initial installation environment's shell:

cat skipped-devs.txt
blkid
ls -l /sys/block/

and post a screenshot here?

 

[HonzaIT]

Today I decided to test Proxmox on an HP Proliant 360e gen8 server and the same problem, boot a USB key created on Rufus.

 

[RSMAN]

I will try with another USB stick tonight and alose with Proxmox 6.2 !

 

[t.lamprecht]

Today I decided to test Proxmox on an HP Proliant 360e gen8 server and the same problem, boot a USB key created on Rufus.

Then what's your output on the commands I asked? That may help to actually solve this...

cat skipped-devs.txt
blkid
ls -l /sys/block/

 

[RSMAN]

Hello, I solved the problem with another USB stick !!!
The first USB stick is USB3 with M.2
The second USB stick is a normal USB2 stick

 

[t.lamprecht]

Hello, I solved the problem with another USB stick !!!

great to hear!

The first USB stick is USB3 with M.2
The second USB stick is a normal USB2 stick

OK, this seems like something we could improve; I now this is extra work but could you boot the ISO another time with the problematic USB3 with M.2 stick in debug mode and then execute those commands in the first shell you get?

After that just do a reboot or even reboot -f to get out of the installer again (nothing will be overwritten at this point)

 

[HonzaIT]

OK, I'll try, version 6.2 doesn't work either, but I'll try another USB flash drive.

 

[RSMAN]

great to hear!



OK, this seems like something we could improve; I now this is extra work but could you boot the ISO another time with the problematic USB3 with M.2 stick in debug mode and then execute those commands in the first shell you get?

After that just do a reboot or even reboot -f to get out of the installer again (nothing will be overwritten at this point)

Yes and I take a picture of the result?
But I remember I had the same problem while installing a Linux distro 1 or 2 years ago!

 

[t.lamprecht]

Yes and I take a picture of the result?

That'd work for me, thanks a lot! FYI: I'm taking an educated guess that the usb3 stick shows up with a device apth like /dev/nvmeXnY, and I'd just like to confirm that guess to be certain when implementing a solution for this issue.

 

[RSMAN]

That'd work for me, thanks a lot! FYI: I'm taking an educated guess that the usb3 stick shows up with a device apth like /dev/nvmeXnY, and I'd just like to confirm that guess to be certain when implementing a solution for this issue.

Hello, here are the pictures, are they good for you?

 

[t.lamprecht]

Yes thanks!

 

[RSMAN]

Yes thanks!

Does that help you?