H12SSL-i unable to install Proxmox

[BeastBurst]

I am trying to install latest Proxmox on my system with defaulted BIOS settings:

MB: Supermicro H12SSL-i
CPU: AMD Epyc 7742
GPU: NVIDIA RTX 3090
RAM: 512GB DDR4 RDIMM ECC

When I try to install the proxmox it always hangs on Loading initial ramdisk.. and the whole system freezes.

We already did a test of the ram for 12 hours and it passed without issues.

Any idea what can be causing this issue ?

 

[scline]

Are you installing via IPMI or USB/Disk? If IPMI, try to install via local media (had an odd issue like this on 7 with a board)

 

[BeastBurst]

I am installing with USB and it just freezes the whole system at "Loading initial ramdisk.." and I am wondering what can be the cause of this issues.

Any idea how can I resolve it ?

 

[Falk R.]

I have installed PVE on many Server with the same Board, but without dedicated GPU. Can you remove the RTX3090 during install?

 

[BeastBurst]

I have installed PVE on many Server with the same Board, but without dedicated GPU. Can you remove the RTX3090 during install?

Sir I was unable to run the integrated GPU.
How did you used it?

Also why you think "Loading initial ramdisk.." can be related to the GPU ?

 

[Falk R.]

Sir I was unable to run the integrated GPU.
How did you used it?

i have used the IPMI Remote Console

Also why you think "Loading initial ramdisk.." can be related to the GPU ?

"Loading initial ramdisk..." is unfortunately somewhat unspecific and can have many causes.
Since the board and the CPU usually do not cause any problems, one takes the most conspicuous component first when testing.
Try it possibly first with a BIOS reset (loading defaults).

 

[BeastBurst]

i have used the IPMI Remote Console

"Loading initial ramdisk..." is unfortunately somewhat unspecific and can have many causes.
Since the board and the CPU usually do not cause any problems, one takes the most conspicuous component first when testing.
Try it possibly first with a BIOS reset (loading defaults).

Already tried out with loading defaults. Did not helped at all. Also looks like my motherboard does not to obtain an IP for the IPMI so basically I can't use IPMI.

 

[Falk R.]

If the network cable is plugged in for IPMI, it should get an IP from DHCP.
However, you can also give the IPMI a static IP via the BIOS.

 

[BeastBurst]

If the network cable is plugged in for IPMI, it should get an IP from DHCP.
However, you can also give the IPMI a static IP via the BIOS.

Tried both cases and none seems to work. In the BIOS on the IPMI sections under IPMI Revision it says unknown. On your motherboards do you have a specific greenlight that indicates that the IPMI is enabled ?

Maybe you've set some jumpers?

 

[Falk R.]

You can enable and configure the IPMI over the BIOS. Per default is the IPMI always enabled and the network config have dhcp enabled.

 

[nardis555]

Was having the same issue. Probably went through 200+ forums. Long story short i fixed it by plugging in a dedicated GPU (arc a380), set preferred video on bios to offboard, and installation worked from there. Issue is something with onboard video freezing during initrd

h12ssl-nt
epyc 7313p

 

[alexskysilk]

I am installing with USB and it just freezes the whole system at "Loading initial ramdisk.." and I am wondering what can be the cause of this issues.

Any idea how can I resolve it ?

recreate the installation iso. use a different usb drive, and make sure you're using a direct burn tool like balena etcher (NOT rufus)

 

[Falk R.]

recreate the installation iso. use a different usb drive, and make sure you're using a direct burn tool like balena etcher (NOT rufus)

I agree with you that copying a fresh ISO to a stick can help, but why are you denigrating a good tool?
I have been using Rufus for well over 10 years and have never had any problems. Rufus also offers you the DD mode and it couldn't be more direct.
I've read a lot more bad things about Balena, but I'm not saying anything bad about it because I don't use this tool and it could be user error.
More than 100 well-functioning USB sticks speak in favor of Rufus.
It would be better to recommend using dd directly or the dd mode of your tool of choice.

 

[alexskysilk]

but why are you denigrating a good tool?

Apologies if you're personally invested; I dont have any preferences. I just know rufus defaults to a none raw-dd method; easier to tell people just not to use it.

It would be better to recommend using dd directly or the dd mode of your tool of choice.

oh sure. but people who usually need this advice are windows based.

 

[Falk R.]

Apologies if you're personally invested; I dont have any preferences. I just know rufus defaults to a none raw-dd method; easier to tell people just not to use it.

The Same Problem has any People with Balena Etcher. The Tool ist not the Problem. The Problem sit behind the Keyboard.

 

[TomiWebPro]

I am no experts here, maybe try using ventoy/a better usb, and for the installation part you may also remove some ram and other system hardwares unnessary for the installation, like downgrading to one stick/minimum of ram for example. If you have a vga/hdmi port on motherboard consider using that during installation and maybe meanwhile remove 3090 completely if the display part went there causing the fault?

 

[alexskysilk]

The Same Problem has any People with Balena Etcher.

no, not the same. etcher only works in dd mode. I agree with your conclusion.

 

[olk]

I've the same problem!

MB: Supermicro H12SSL-i
CPU: AMD Epyc 7713
GPU: NVIDIA RTX 3090 FE
RAM: 512GB DDR4 RDIMM ECC
BIOS vers: 2.9
VGA (BIOS option): external

PVE installer: 8.2-2

Installation option: terminal

During booting the kernel and displaying the kernel parameters the system freezes. Replacing the RTX3090 by a 1080Ti the boot process completes.

 

[Ghan]

I found the solution in this thread: https://forum.proxmox.com/threads/installation-stuck-after-grub.65029/
Had the same problem installing with an RTX 3080. Added

module_blacklist=nvidiafb

to the boot line and then it was able to proceed.