Hi,
I just thought I'd report the problems I encountered attempting to install the Proxmox 2 series ISO available for download with new HP ProLiant DL360 G7 servers.
Out of the box, performed RAID 0+1 setup on 2x 300Gb disks. HP related drivers etc for this server model is available here:
http://h20566.www2.hp.com/portal/si...let.endCacheTok=com.vignette.cachetoken#12212
Had to install basic CentOS 6.1 server so could update the 5.14 storage controller firmware (the HP Firmware CD is old and contains older drivers). Also update iLO3 to 1.28 (available from the "Windows" HP driver downloads page even though it was a Linux bundle).
Once all that was done, ran up the server and ISO, installed Proxmox VE off the ISO.
Upon boot, got the BIOS/firmware bug problem in the first snapshot, then the second snapshot complaining about the inability to run fsck aka the inability to boot into Proxmox.A red herring. By "accident" I came across the solution.
I went into the BIOS of the server and changed the "HP Power Management Profile" which manages the power of the CPU's / cores from the "balanced" setting to "maximum performance", after all, the point of a VM host is to have high performance. Saved, rebooted, Proxmox went past that fsck error.
Performed on another new "out of the box" HP ProLiant DL360 G7 (same CPU's, memory, etc as the first one), performed the same thing (firmware, BIOS change to HP Power Profile, etc), fresh Proxmox install, went through fine no errors.
Rebuilt first G7 server with Proxmox ISO again, all went through fine and booted into Proxmox, no fsck error.
The firmware error still exists on both servers, but Proxmox boots without fsck issues.
Checked this BIOS firmware bug problem on the net, it's known and prevalent everywhere from Debian/Ubuntu to Red Hat. CentOS 6.2 seems to have it "fixed" with the latest release and kernel updates, didn't look too much into Debian/Ubuntu to see if kernel releases "fix" that problem.
HP most probably have to fix it with a later BIOS, as 2011/05/05 isn't exactly recent but it's the latest they've made available for download and coming pre-installed on the servers they ship.
These DL360 G7's are well spec'ed with 2x E5675 6 core CPU's with 12Gb RAM and 2x 300GB SAS drives.
It should be noted that booting a CentOS 6.1 ISO, even with the balanced HP Power Profile in the BIOS, went past any BIOS firmware errors and allowed no problems on boot. Only Proxmox had the "fsck" issue stopping the boot into the Proxmox OS.
I just thought I'd report the problems I encountered attempting to install the Proxmox 2 series ISO available for download with new HP ProLiant DL360 G7 servers.
Out of the box, performed RAID 0+1 setup on 2x 300Gb disks. HP related drivers etc for this server model is available here:
http://h20566.www2.hp.com/portal/si...let.endCacheTok=com.vignette.cachetoken#12212
Had to install basic CentOS 6.1 server so could update the 5.14 storage controller firmware (the HP Firmware CD is old and contains older drivers). Also update iLO3 to 1.28 (available from the "Windows" HP driver downloads page even though it was a Linux bundle).
Once all that was done, ran up the server and ISO, installed Proxmox VE off the ISO.
Upon boot, got the BIOS/firmware bug problem in the first snapshot, then the second snapshot complaining about the inability to run fsck aka the inability to boot into Proxmox.A red herring. By "accident" I came across the solution.
I went into the BIOS of the server and changed the "HP Power Management Profile" which manages the power of the CPU's / cores from the "balanced" setting to "maximum performance", after all, the point of a VM host is to have high performance. Saved, rebooted, Proxmox went past that fsck error.
Performed on another new "out of the box" HP ProLiant DL360 G7 (same CPU's, memory, etc as the first one), performed the same thing (firmware, BIOS change to HP Power Profile, etc), fresh Proxmox install, went through fine no errors.
Rebuilt first G7 server with Proxmox ISO again, all went through fine and booted into Proxmox, no fsck error.
The firmware error still exists on both servers, but Proxmox boots without fsck issues.
Checked this BIOS firmware bug problem on the net, it's known and prevalent everywhere from Debian/Ubuntu to Red Hat. CentOS 6.2 seems to have it "fixed" with the latest release and kernel updates, didn't look too much into Debian/Ubuntu to see if kernel releases "fix" that problem.
HP most probably have to fix it with a later BIOS, as 2011/05/05 isn't exactly recent but it's the latest they've made available for download and coming pre-installed on the servers they ship.
These DL360 G7's are well spec'ed with 2x E5675 6 core CPU's with 12Gb RAM and 2x 300GB SAS drives.
It should be noted that booting a CentOS 6.1 ISO, even with the balanced HP Power Profile in the BIOS, went past any BIOS firmware errors and allowed no problems on boot. Only Proxmox had the "fsck" issue stopping the boot into the Proxmox OS.
