Either way we ended up with a Critical error on the OS’s RAID 1 array.

The BIOS for the “RAID” at the motherboard level holds no clues to how to rebuild the array once we re-seated the drive.

We booted the server since our experience with software based on board RAID chipset failures require the driver to be loaded and available before a rebuild could be initiated (some Intel on board RAID chipsets are an exception to this rule).

Once into the OS we found the AMD RAIDXpert “console” link:

What came up was a Web based console that asked for a username and password. Fortunately the default username and password was right there on the logon page.

Once in we were able to initiate a rebuild of the RAID 1 array:

The rebuild time for a pair of 750GB Seagate ES series drives took quite a few hours on this particular box even though there was not a lot of disk action going on via the network.

The Performance tab in the Task Manager during the rebuild process looked like this:

Philip Elder 
MPECS Inc. 
Microsoft Small Business Specialists 
Co-Author: SBS 2008 Blueprint Book

Fuente: http://blog.mpecsinc.ca/2011/04/hp-proliant-microserver-rebuilding.html