HP Proliant DL380 G6 – 207 Memory Initialization Error


After a number of memory upgrades on our G6 servers I experienced an issue during the boot process whereby a number of DIMM slots were being reported as having 207 memory initialization errors.

I re-seated all the memory modules thinking that perhaps a module was not pushed in enough and after further research ensured that the BIOS was up to date.

Finally, I used different memory replacing the 3 new modules with a different set of 3 modules. This worked.

By process of elimination it turned out to be a faulty new module that was failing a bank of 3 modules. Even new HP memory can be faulty and is worth checking!

Advertisements

You receive the error ‘An error occurred while trying to save the file. Please check your media and try again’ when you try to save a report to an external device when using HP Insight Diagnostics


This was with the latest version of HP SmartStart 8.60 on a HP Proliant G6 server.

I started with a USB stick and also used an external USB floppy drive but kept getting the error each time I tried to save a diagnostics report. I could choose the drive and see that it was being accessed but still received an error. In the end I created a file on the floppy called survey.html (the file name that was supposed to be being created).

Bizarrely the software saw the file and asked to overwrite! Thereafter I could save any report to the disk.

Unable to delete a logical drive from an array on a HP SAN


Came across this recently when I wanted to delete a logical drive from one of the arrays on the SAN.

Unfortunately, unless it is the last Logical Drive that was created on the array then you do not get the option to delete it.

The only way to be able to delete a Logical Drive that was not created last on the array is to delete the Logical Drives in order of creation which is not always a viable option.

How to enable the Intel VT virtualisation feature on a supported HP Proliant server running ESX 3.5 so that 64-bit guest VM’s can run


When you try to create or import a 64-bit host VM in your Virtual Infrastructure you may receive an error in the VI client along the lines of

Attempting to load an x64 operating system, however this CPU is not compatible with x64 mode

If you have a HP Proliant server that has processors that are 64-bit compatible then it is likely that you just need to enable the Intel VT feature in the BIOS.

To enable the Intel VT feature in the BIOS

Restart the HP Proliant server and press F9

image001

Select ‘Advanced Options’

image002

Select ‘Processor Options’

image003

Select ‘Intel Virtualization Technology’

image004

Select ‘Enabled’ and press the enter key to enable Intel VT

image005

Press the Esc key to exit and then press the F10 key to save the configurations when prompted. The server automatically restarts but I also powered down the server to ensure a cold boot to confirm that the Intel VT option was correctly detected by ESX.

You receive the error message ‘Only one instance of the Array Configuration Utility can be running’ when opening the ACU utility on a HP Server


You receive the error message ‘Only one instance of the Array Configuration Utility can be running’ when opening the ACU utility on a HP Server.

ACU error message

This occurs when no other instance of the ACU utility is actually running.

It would seem that this effects, rather infuriatingly, Windows 2003 and 2008 servers with Internet Explorer 8 installed and ACU Version 8.25 (or earlier) for Windows 2003 and ACU Version 8.20 for Windows 2008.

To resolve this the version of the ACU utility needs upgrading to version 8.28 for Windows 2003 and 8.25 for Windows 2008.

Alternatively, you could uninstall Internet Explorer 8 and roll back to an earlier release.

HP have released an advisory here http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01763057