Proxmox VE 3.0 Installation Stuck on Intel E3-1240 V3 Supermicro System

[LEckley]

Hi Guys,

I am trying to get Proxmox VE 3.0 installed onto the below hardware configuration to performance testing, however so far the ISO installer is failing to get past the initial install screen (Once you choose enter it notes it be booting). It will sit at the boot screen indefinitely and so far I have been unable to get the diagnostic output either.

Any ideas?

System information:

Supermicro X10SLM-F
Bios Date: 05/08/2013 Ver: 04.06.05

Intel Xeon E3-1240 V3
16GB RAM
500GB Western Digital RE4 (SATA in ACHI Mode)

I am mounting the proxmos ISO via Supermicro IPMI to perform the OS installation.

Thanks!

 

[Raymond Burns]

Can you try this http://forum.proxmox.com/threads/14...-1225v3-X10SLM-F-Supermicro?p=77925#post77925
I am looking into purchasing one of these in the very near future. Was going for the 1230v2 to get great idle TDP, but it seems that the idle power is negligible between the 1230v2 and 1230v3.

Will be using mine for HA quorum and a firewall appliance.
Please report back if this works

 

[LEckley]

Can you try this http://forum.proxmox.com/threads/14...-1225v3-X10SLM-F-Supermicro?p=77925#post77925
I am looking into purchasing one of these in the very near future. Was going for the 1230v2 to get great idle TDP, but it seems that the idle power is negligible between the 1230v2 and 1230v3.

Will be using mine for HA quorum and a firewall appliance.
Please report back if this works

I read that thread before posting mine, honestly I am not sure how I am to use a different kernel without first having the system installed...maybe I am missing something (lack of knowledge/experience)?

I was able to finally get Proxmox up and running on the system, though very ass backwards.

1) Installed Debian Jessie (Debian 7.x does not the "newer" Intel NIC drivers and I did not feel like trying to compile my own.)
2) Downgraded Jessie to Wheezy - http://ispire.me/downgrade-from-debian-sid-to-stable-from-jessie-to-wheezy/
3) Installed Proxmox on Wheezy - http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy

All in all, prior to this experience I never really used Debian personally so there could be a much easier way to do it, but as it stands right now, even looking back, I have no better solution.

If you can explain how to use the solution in http://forum.proxmox.com/threads/14...-1225v3-X10SLM-F-Supermicro?p=77925#post77925 I will happily take a crack at it.

 

[Raymond Burns]

Tom says to utilize the new kernel "pve-kernel-2.6.32-22-pve: 2.6.32-107"
The announcement sticky, http://forum.proxmox.com/threads/14694-New-Kernel-for-Proxmox-VE-3-0, says that the new stable kernel is .... wait for it .... pve-kernel-2.6.32 (2.6.32-107)

You may have to create a new ISO disk if it was created before the kernel was released, but my understanding is the kernel you are looking for is now the standard. Also, you may have to do the "nousb" kernel option. Whatever that means.

 

[Raymond Burns]

Also, I have decided to go with a dual "AMD Opteron Quad Core 2346HE" board to replace my failed board.
Ideally, all I wanted to do was replace my failed dual 2212HE setup with something that is low power.
Now I can get a new Proxmox v3.0 on 8 cores, and a new chassis for my Napp-IT+OmniOS NAS using the e3-1230v2 (or something similar).
http://www.ebay.com/itm/Supermicro-...773991?pt=COMP_EN_Servers&hash=item27d516ece7
I hope the solution I posted works for you!!

 

[LEckley]

Tom says to utilize the new kernel "pve-kernel-2.6.32-22-pve: 2.6.32-107"
The announcement sticky, http://forum.proxmox.com/threads/14694-New-Kernel-for-Proxmox-VE-3-0, says that the new stable kernel is .... wait for it .... pve-kernel-2.6.32 (2.6.32-107)

You may have to create a new ISO disk if it was created before the kernel was released, but my understanding is the kernel you are looking for is now the standard. Also, you may have to do the "nousb" kernel option. Whatever that means.

I was using the latest ISO downloaded last week.

Also, I have decided to go with a dual "AMD Opteron Quad Core 2346HE" board to replace my failed board.
Ideally, all I wanted to do was replace my failed dual 2212HE setup with something that is low power.
Now I can get a new Proxmox v3.0 on 8 cores, and a new chassis for my Napp-IT+OmniOS NAS using the e3-1230v2 (or something similar).
http://www.ebay.com/itm/Supermicro-...773991?pt=COMP_EN_Servers&hash=item27d516ece7
I hope the solution I posted works for you!!

Honestly, going out and buying brand new equipment is not a valid solution...not too mention that the AMD CPU's have horrible performance & are power hungry compared to almost any of the new Intel chips.

 

[Raymond Burns]

Honestly, going out and buying brand new equipment is not a valid solution...not too mention that the AMD CPU's have horrible performance & are power hungry compared to almost any of the new Intel chips.

I wasn't suggesting getting new equipment. I was saying, you persuaded me to go another route, and I hope the new kernel with nousb option works for you.

Just to confirm, you did the "nousb" option? I'm assuming from the suggestion, there are some factors that drivers are not presently compatible, but the chipset itself should take.
Also, I had this happen before on another UNIX install, not Proxmox, but try different ACPI Versions in your BIOS. Normally, when I used to get a system I felt was above the average, I would enable mostly everything that resembled upgrade or better usage. Which included ACPI Version Options 1.0 - 2.0 - 3.0. I normally have always selected 3.0, but during my OmniOS, it was the option to cause my boot to hang. That and the ECC Memory Scrubbing. If that doesn't work, set your BIOS to "Default", not Optimal Default.

What I tend to do now is print out the bios selection from the online manual. Write the values I have present in my BIOS now, and then reload the defaults or whatever allows me to Boot without hanging. Then you can compare and narrow down what caused the HANG. To me, this would give you optimal values from the BIOS standpoint

 

[LEckley]

Tom says to utilize the new kernel "pve-kernel-2.6.32-22-pve: 2.6.32-107"
The announcement sticky, http://forum.proxmox.com/threads/14694-New-Kernel-for-Proxmox-VE-3-0, says that the new stable kernel is .... wait for it .... pve-kernel-2.6.32 (2.6.32-107)

You may have to create a new ISO disk if it was created before the kernel was released, but my understanding is the kernel you are looking for is now the standard. Also, you may have to do the "nousb" kernel option. Whatever that means.

Gotcha!

Unfortunately I cannot do it without USB as I am using IPMI to load the OS.

 

[Raymond Burns]

The IPMI needs USB to run the OS install? I thought the IPMI would Virtually attach your local media via ether or /media and not necessarily usb.
I wouldn't know though. I've never used IPMI

 

[LEckley]

Tom says to utilize the new kernel "pve-kernel-2.6.32-22-pve: 2.6.32-107"
The announcement sticky, http://forum.proxmox.com/threads/14694-New-Kernel-for-Proxmox-VE-3-0, says that the new stable kernel is .... wait for it .... pve-kernel-2.6.32 (2.6.32-107)

You may have to create a new ISO disk if it was created before the kernel was released, but my understanding is the kernel you are looking for is now the standard. Also, you may have to do the "nousb" kernel option. Whatever that means.

The IPMI needs USB to run the OS install? I thought the IPMI would Virtually attach your local media via ether or /media and not necessarily usb.
I wouldn't know though. I've never used IPMI

Correct, it mounts as a USB device.