I downloaded the Windows Server driver from HP and it installed without problem. After you have selected which Windows Server edition you want to install the setup process brings up a listing of available drives in your machine. Note that your submission may not appear immediately on our site. Your message has been reported and will be reviewed by our staff. The newly recreated array came up as free space and I selected it and hit next. Leave a Reply Cancel reply Your email address will not be published.
|Date Added:||20 May 2012|
|File Size:||43.10 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Installing Windows Server 2008 on a Compaq ProLiant ML310 G1 server
After the driver loaded, the number of items was down to 3, now showing 2 physical drives really the two logical RAID 1 drivers and 2 partitions one on each driveplus the unallocated space. Once comlaq, our staff will be notified and the comment will be reviewed.
Using this command we can get the clear text data from the error:. Your email address will not be published. So I knew what the problem was, just not how to fix it.
Enter the e-mail address of the recipient Add your own personal message: That produced another error. The posting of advertisements, profanity, or personal attacks is prohibited.
NC BaseTX (PCI-X) PCI Drivers – Download Device Drivers – –
In this driver package the MegaIDE. Circumstantial evidence to back up this conclusion is that the other array is accessible in Windows Server without problem.
Finally I installed Exchange and moved all the mailboxes to the virtual server. I did a lot of stuff to the partitions while trying to make the old HP driver work. Home Windows Drivers Network Drivers cp Note that your submission may not appear immediately on our site.
To make windows see the arrays I have to load a driver during OS setup. I have 4 drives in the server, distributed over two RAID 1 arrays.
I still think my theory about the original array becoming corrupted or having been modified in some way to be 20008. Things were looking good. For those who are interested here are the links to wndows software I have mentioned in this post: Using windowz command we can get the clear text data from the error: I hit Next and Windows Setup proceeded to try and create a new partition in this free space.
I figured it might be a bad floppy so I copied the driver files to a USB key instead and tried again. I proceeded to hit the Load Driver button and load the HP driver from floppy.
This time the driver loaded successfully but setup still displayed the same 6 items, so that driver was not RAID capable when used with Windows Server either. It always gives an error and then freezes when I try to start it. I quickly noticed that the server had no network connectivity due to a missing NIC driver.
I rebooted again and went back into the controller BIOS. On Windows Server this was done pressing F6 at the beginning of setup and popping in a floppy with the required driver.
Windows Server installed successfully and I started configuring the server. That was when the fun started. Sexually explicit or offensive language.
SPEXE Download | ZDNet
Then I could do a search for new hardware and install the Broadcom driver. This weekend I decided it was time to upgrade cmpaq to Windows Server It installed successfully and the Spy program, which sits in the system tray and monitors drive health, worked well. That was, however, the only unknown device.