I've just spent two days beating our company's new ML110 G5 with a stick in order to force it to accept an installation of Microsoft Windows Server 2008 Standard (x64). Having finally got it working I thought I'd share what I did in case anyone else has the same issues I came across.
This is a long-winded post but hopefully the gory details will make a difference somewhere.
This is a "works for me" post. Your milage may vary. Discussion is welcome, but my server is now commissioned and in use, so I am unable to carry out any further tests.
My hardware:
HP ML110 G5 server
3 GB RAM
2 x 250 GB SATA HDDs (which I want to run as a RAID-1 mirror)
These instructions assume you are performing an installation from scratch, and that the disks hold no data that you wish to keep. FOLLOWING THESE INSTRUCTIONS WILL ERASE THE HARD DISKS! Back up any data you want to keep before starting.
1. Boot the machine and hit F10 to enter the BIOS configuration utility.
2. Press F9 and confirm the dialog to reset the BIOS to its factory default settings.
3. Under the "Main" menu, under "Boot Features", change "Virtual Install Disk" option to "Disabled".
4. Under the "Advanced" menu, select "Advanced Chipset Control" and set "SATA RAID Enable" to "Enabled".
THIS NEXT STEP IS CRITICAL. The Windows 2008 Server installer won't recognise the RAID array unless you do this.
5. Under the "Boot" menu, highlight "+ Hard Drive" and press <+> twice to move it to the top of the list.
6. Save and exit from the BIOS. The machine will reboot.
7. Press F8 when prompted to enter the RAID controller configuration utility.
8. Configure your RAID array according to taste.
IMPORTANT: If a RAID array is already configured DELETE IT and reconfigure, even if the existing configuration is the same as the one you want. The act of deleting the array clears the disk partition tables. If this isn't done, the currently installed operating system will boot instead of the install CD. This is an artifact of the requirement for the Hard Drive to be set first in the BIOS boot order, and is also the reason why it's not possible to perform an installation using these instructions without erasing the disks.
9. Go back into the BIOS and check the boot order again. I have found that sometimes the "removable device" entry gets moved to the top of the list after the RAID array has been configured. If this has happened, move "Hard Disk" back to the top of the list, save and exit.
10. Insert the installation media (I used the Windows Server 2008 Standard x64 DVD from the Microsoft Action Pack).
11. Follow the installation wizard steps up to the point at which you have to choose where to install Windows.
There are *two* drivers that you have to install:
* cp008698 - Install this first (this seems to be the 64bit driver that windows uses when it boots from disk).
12. Insert a USB stick with these drivers on it, and click "load driver".
13. Click "Browse" and navigate to the "CP008698" folder on the USB stick.
14. Select "Adaptec Serial ATA HostRAID (c:\path\to\cp008698\aarachi.inf) - this should be the only entry if you have checked "Hide drivers that are not compatible with hardware on this computer".
15. Click next, and "OK" on the subsequent "load driver" dialog.
When you return to the "Where do you want to install windows" screen, it will look exactly as it did the first time (the disks will not appear in the list). However the driver will have been loaded into memory and will get copied to the system directory when the OS installs.
16. Now repeat the above steps, substituting cp008697 for cp008698. This will load the 32bit driver.
17. Back at the "where do you want to install windows" screen, you should now have a new disk entry: "Disk 1 Unallocated Space". Select this entry and click Next.
All being well, Windows should now install. The installer will use the 32bit disk drivers to install Windows, but will also copy the 64bit drivers to the system drive.
The machine will reboot automatically when installation is complete. Remove your USB stick when this happens. If you don't remove the USB stick in time you may need to press CTRL-ALT-DEL to reset the machine after it reboots.
With any luck, when the operating system loads from disk, it will use the 64bit disk drivers and you will be presented with the first-run configuration wizard. w00t!
Theories on a postcard, please, as to why both the 32- and 64-bit drivers are required. Also, sharp-eyed readers will note that the drivers I've linked to here are the Windows Server 2003 versions, not the Server 2008 ones. I did try the latter using this process, but they didn't work (GPF on reboot). I guess only HP can tell us why that might be.
I hope this information helps save someone some time and effort :o)
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
On my new Proliant ML150 G5 , i need only to insert the SBS2008x64 boot cd, select the 64bit drivers for the embedded sata raid (cp009516) and all work fine.
Maybe there is a better bios or firmware on board.
This is the solution which I was looking for for months. I had the same problem (the RAID driver being 'not signed') but loading the 2 drivers after each other has left me with a correct installed RAID controller and WIndows Server 2008.
Ok, the procedure I took was some what different than the procedure Richard took. I didn't alter any settings in the BIOS (which I previously had done, so I didn't have the default settings) I just first loaded the 64-bit driver when being asked by the install procedure of Windows Server 2008 (because Richard assumed that the drivers which are loaded stay in available in memory). After loading these drivers I got an error (and no visible partitions). After closing the error I just loaded the 32-bit driver (for links seer RIchards' post) after which I got another error. But after closing the error message I simply had all my partitions visible and available for installing Windows Server 2008 in one of them.
Once downloaded, the exe file needs to be run and extracted preferably into a new folder on a USB stick. You do not have to purchase this from HP - any USB stick will do.
12. Insert the USB stick with this driver on it, and click "load driver".
13. Click "Browse" and navigate to the folder on the USB stick where you extracted the driver to.
14. For 32bit, select "Adaptec Serial ATA HostRAID (c:\path\to\cp009517\aarachi.inf) - this should be the only entry if you have checked "Hide drivers that are not compatible with hardware on this computer".
For 64bit, select "Adaptec Serial ATA HostRAID (c:\path\to\cp009516\aarachi.inf) - this should be the only entry if you have checked "Hide drivers that are not compatible with hardware on this computer".
15. Click next, and "OK" on the subsequent "load driver" dialog.
When you return to the "Where do you want to install windows" screen, it will look exactly as it did the first time (the disks will not appear in the list). However the driver will have been loaded into memory and will get copied to the system directory when the OS installs.
Continue with 17...
That's it.
As this is marketed as an entry level server, lots of newbies (like me) may purchase this machine so this detailed guide is very useful.
I wanted to thank you all. It took me a day and a half of frustration trying every driver from HP. I could only install SBS 2008 on IDE and not raid. Could not figure out why. Damn. 2000 am an I found your post and the others that updated it and solved the damn thing.
Also a vote of thanks from me. I spent two days on this. HP site is misleading - sp008698 and sp008697 did not show up in my Windows Server 2008 FOUNDATION install. However SP009516 did and worked! Special thanks to Anthony O'Brien for pointing me in the right direction. regards Steve
Hi, I did install Win2008 server on the HP M110 G5 using the same routine as described by Richard P.King. Win2008 is running fine fot he moment. Now I want to ad a second HDisk, same type and size as disk#0 for a RAID-1 (mirror) volume. HP-support suggest to reinstall the OS after finishing the virtual Volume and that's not mine idea. I like to have the OS intact and put the second disk to the running system, because what to do when a emergency will happen and a disk has to be removed for a better one? But when the Volume is made (takes a copy time of 3 hours!)then the OS will not boot because there is no HD anywhere!
Printable version
