Rapid updating of drivers
I am by no means an Intel expert, but based on my significant experience with Intel chipsets, I believe this method will work for IRST managment with free Hyper-V Server 2008 R2 (and Windows Server 2008 R2 Core) using the following chipsets: - Intel(R) ESB2 SATA RAID Controller - Intel(R) ICH7R/DH SATA RAID Controller - Intel(R) ICH7MDH SATA RAID Controller - Intel(R) ICH8R/ICH9R/ICH10R/DO/5 Series/3400 Series SATA RAID Controller - Intel(R) ICH8M-E/ICH9M-E/5 Series SATA RAID Controller - Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller - Intel(R) Mobile Express Chipset SATA RAID Controller The system I did this testing with is a 3420 Chipset (Super Micro X8SIL-F).Testing hard drive failure Since there was little time invested in setting up this particular server, we decided testing for and managing a failed hard drive would be a wise excercise. Here are the series of commands and screens we encountered during the test.To make administration from the command window easier, from the remote workstation I copied the files in the \Intel Util\AHCI_Intel_10.0.0.1046_W7x64\RAIDCFG32 directory up to the top level \Intel Util directory.You will probably want to open the Raid Cfg32file on the remote workstation for easier reading of the help on command switches.Sequence of events Note: the server remained booted to the Hyper-V Server 2008 R2 Operating System during this entire excercise.We made no real effort to test throughput during this test, but I suspect that we would have found performance degraded but acceptable like we experience with the normal full GUI OS install.Selecting a single disk with the /DS option will delete the metadata from all volume members." So which is it?
And while the style is old school, its 2K, single-stage paint technology is completely modern.
Before drive removal, our standard RAID1 Hot Spare configuration.
Disks 0 and 2 are the mirror set, Disk 4 is the Hot Spare. We only wanted to monitor the line with the Rebuild information, so we piped the results to the find command.
(If you find a newer version of the utility, please let me know! Note: this write-up is based on a free Hyper-V Server 2008 R2 SP1 install, your experience may vary depending on OS version.
On the Hyper-V server, I shared the root of the C: drive, then using another workstation, I browsed to the Hyper-V server, created a directory named pnputil -i -a ia Microsoft Pn P Utility Processing inf : ia Successfully installed the driver on a device on the system. Published name : oem0Total attempted: 1 Number successfully imported: 1 (you may get a pop-up box to confirm you trust software from Intel) You will need to reboot the server to load the new driver.
I was able to find a V10.0.0.1046 copy of the driver and utility, I believe this to be the most current version available of the utility.