So I was repurposing my HP ML 370 G4 from it’s old job of being a SBS 2003 to another operating system.  And I threw on Windows 2008 64 bit to see if it would load.  While the box won’t support HyperV (sniff) it may have a few years left to be a spare server duty out of it.  My first interesting factoid is that since it’s been turned off for two weeks the controller card battery was low (this is why I plan for hardware change outs after five years).  The next thing I noted was exactly what is documented in this thread:

Install using the smart start media and after you log into the OS the jet engines (better known as the fans on that sucker) turn on and do not turn off.

Do not use smart start. Set up the array without smart start and install the OS without smart start. Then install HP tools after OS installed

If you let it install ALL of the drivers, the jet engine sound will turn you deaf.

As that thread indicates, run 2003 on it, and it won’t sound like a jet engine.  Put 2008 with the smart smart and wear ear plugs. 

So the moral of this story is…. sometimes you don’t want to use that HP smart start media especially when you are putting server operating systems that are not the same “vintage” as the server is. 

As I always explain… sometimes you have to make sure you match the kids on the playground to ensure they are the same age to get them to play the nicest together.  That’s why the vintage G4 + smart start + Windows 2003 plays nice and a G6 (my current model) and smart start and Windows 2008 works the best. 


2 Responses to Using the HP Smart Start turns your Server into a Boeing 747

  1. Chris Knight says:

    Any idea which driver is causing the problem?

    Personally I prefer Win2008 and then ProLiant Support Pack (firmware + drivers + Allows me to be selective with drivers and firmware.
    Handy for Hyper-V Core Installs as this allows the video driver to not be installed, though not so much of an issue with Hyper-V R2 and SLAT-enabled hardware.
    There’s a good reason why Microsoft only included the SVGA driver with Windows Server 2008 – avoidance of expensive vTLB Flush calls inside the hypervisor, caused by graphics drivers.

  2. bradley says:

    Not sure what driver. I may experiment a bit and see if I can tell.