HP Superdome 2 Demo

Understanding HP's Intelligent Management Center

Get your own valid XHTML YouTube embed code

SAS and SATA Hard Drive - LED Combinations/behavior Explained

The table below shows the different status of the LEDs being steadily On, Off or flashing including in different colors to show the status of the SAS or SATA HardDrive.

Details

Online/Activity LED (green)	Fault/UID LED (amber/blue)	Interpretation
On, off, or flashing	Alternating amber and blue	The drive has failed, or a predictive failure alert has been received for this drive; it also has been selected by a management application.
On, off, or flashing	Steadily blue	The drive has failed, or a predictive failure alert has been received for this drive; it also has been selected by a management application.
On	Amber, flashing regularly (1 Hz)	A predictive failure alert has been received for this drive. Replace the drive as soon as possible.
On	Off	The drive is online, but it is not currently active
Flashing regularly (1 Hz)	Amber, flashing regularly (1 Hz)	Do not remove the drive. Removing a drive may terminate the current operation and cause data loss. The drive is part of an array that is undergoing capacity expansion or stripe migration, but a predictive failure alert has been received for this drive. To minimize the risk of data loss, do not replace the drive until the expansion or migration is complete.
Flashing regularly (1 Hz)	Off	Do not remove the drive. Removing a drive may terminate the current operation and cause data loss. The drive is rebuilding, or it is part of an array that is undergoing capacity expansion or stripe migration.
Flashing irregularly	Amber, flashing regularly (1 Hz)	The drive is active, but a predictive failure alert has been received for this drive. Replace the drive as soon as possible.
Flashing irregularly	Off	The drive is active, and it is operating normally.
Off	Steadily amber	Steadily amber A critical fault condition has been identified for this drive, and the controller has placed it offline. Replace the drive as soon as possible.
Off	Amber, flashing regularly (1 Hz)	A predictive failure alert has been received for this drive. Replace the drive as soon as possible
Off	Off	The drive is offline, a spare, or not configured as part of an array

The Execute Disable/No Execute CPU feature is not enabled for this machine.

After VMware ESX installation, you might get bellow warning on your screen.

The Execute Disable/No Execute CPU feature is not enabled for this machine.

There is No-Execute Memory Protection parameter, which is disabled, under the Processor Options (under Advanced Options) in the BIOS.

Go to the BIOS set up and enable it.

Recommended BIOS Settings on HP ProLiant DL580 G7 for VMware vSphere

The HP Proliant DL580 G7 has several important BIOS Settings which need to be set.

The default options are in Italic while the non-default (recommended) options are in Bold.

Options which are not relevant are left out.

You might need to change options if you have a specific configuration or specific needs.  This list is only a general guideline for most of the settings tuned for vSphere.

Option	Value	Description
System Options
–Serial Port Options
—-Embedded Serial Port	COM 1; IRQ4; IO: 3F8h-3FFh	The onboard Serial Port is left enabled in case Serial-Line logging at the server is needed.
—-Virtual Serial Port	COM 2; IRQ3; IO: 2F8h-2FFh	The Virtual Serial Port is needed to do Serial-Line logging through iLO 3.
–Embedded NICs
—-Embedded NIC Boot Options	Disabled	If you don't PXE boot the server, set it to disabled.  Otherwise, leave it enabled.  Setting it to disabled saves you 2 seconds when booting the server
–Advanced Memory Protection	Advanced ECC Support	Depending on your needs, you might want to select improved Memory Protection
–USB Options
—-USB Control	USB Enabled	Allows the use of Keyboard and Mouse during vSphere setup.
—-USB 2.0 Controller	Enabled	Allows USB 2.0 high speed transfers.
—-Removable Flash Media Boot Sequence	External DriveKeys First	Allows the host to boot from external USB keys (and iLO). Necessary for firmware updates, …
–Processor Options
—-No-Execute Memory Protection	Enabled	Needed for vSphere
—-Intel® Virtualization Technology	Enabled	Needed for vSphere
—-Intel® Hyperthreading Options	Enabled	Divides each core in 2 logical CPU's, improving the vSphere CPU schedulers possibilities.
—-Processor Core Disable	All Cores Enabled	No reason to disable cores.
—-Intel® Turbo Boost Technology	Enabled	When not all cores are used, ESX will park those cores and over clock the other ones. When an ESX host is not using all its cores, the active cores will run faster resulting in faster VM speeds.
—-Intel® VT-d	Enabled	Needed for vSphere (VMDirectIO, …)
–NUMLOCK Power-On State	Disabled	In most server rooms or when using a laptop to access the server console, a numeric keypad is not available.
Power Management Options
–HP Power Profile	Custom	Allows to enable custom Power settings specific for vSphere
–HP Power Regulator	OS Control Mode	Hands over the Power Management to vSphere. The other options give this control to the server itself.
–Redundant Power Supply Mode	High Efficiency Mode (Auto)	By default (Balanced Mode), the server uses all installed PSU's. This might look like the most efficient use, but the more power is drawn from a PSU, the more efficient it operates. The less power you draw from a PSU, the more gets lost to keep the PSU working. Thus, it is best to use the minimum amount of PSU's so they deliver the highest possible output. The remaining PSU's are placed in standby. This settings does not affect redundancy as the standby PSU's jump in as soon as an active one fails. By using the 'Auto' mode, the active PSU's are chosen based on the server's serial number (odd or even number = odd or even PSU numbers). This makes sure that all power circuits in the racks are evenly used.
–Advanced Power Management Options
—-Minimum Processor Idle Power State	C3 State	Needed for vSphere DPM. Allows vSphere to halt unneeded cores.
—-Maximum Memory Bus Frequency	Auto	Memory only runs at 1 speed in these servers -> 800 MHz
—-PCI Express Generation 2.0 Support	Auto	Server will detect PCIe Generation itself. Forcing it to PCIe 2.0 will make all PCIe 1.0 cards unusable.
—-Dynamic Power Savings Mode Response	Fast	Switch faster between processor states.
—-Collaborative Power Control	Enabled	Allows vSphere to control the PCC Interface
—-DIMM Idle Power Saving Mode	Enabled	DIMMs can put themselves into Low Power mode when not used. This will save some power if not all memory is used on the host.
Server Availability
–ASR Status	Disabled	ASR monitors an agent running in the Service Console. When this does not respond within 10 minutes, the host is rebooted. However, if the agent fails or the Service Console becomes sluggish (even though the VM's are perfectly fine), ASR will detect this as a system hang and will reboot the server. Furthermore, in case of a PSOD, ASR will reboot the server as well. This reboot might cause a loss of some logfiles.
–ASR Timeout	10 Minutes	This has no effect since ASR is disabled.
–Thermal Shutdown	Enabled	To protect your server, it will be shutdown in case it gets too hot.
–Wake-On LAN	Enabled	vSphere DPM uses Wake-On LAN to power on servers (it uses iLO first, but falls back on Wake-On LAN)
–POST F1 Prompt	Disabled	The system boots if critical components fail.
–Power Button	Enabled	Power Button behaves like it should
–Automatic Power-On	Disabled	If set to enabled, the server will power-on as soon as AC Power is available. When set to disabled, power is restored to its previous state when AC Power is available.
–Power-On Delay	No Delay	When AC Power is restored, all systems will come online at the same time causing a power spike. If the power system is unable to handle this, a random delay will solve this problem.
BIOS Serial Console & EMS
–BIOS Serial Console Port	Auto
–BIOS Serial Console Baud Rate	9600
–EMS Console	Disabled
–BIOS Interface Mode	Auto
Advanced Options
–Advanced System ROM Options
—-Option ROM Loading Sequence	Load Embedded Devices First	Embedded devices should be loaded first so PXE boot from onboard NICs is always possible.
—-MPS Table Mode	Full Table APIC	vSphere needs this set to Full Table APIC
—-ROM Selection	Use Current ROM	Backup ROM is only needed when a firmware flash was unsuccessful.
—-NMI Debug Button	Enabled	Can be used to generate a NMI through the button on the system board.
—-Virtual Install Disk	Disabled	This Virtual Install Disk only contains drivers for Microsoft Windows Operating system.
—-PCI Bus Padding Options	Enabled	Disabling this option is only necessary for certain older expansion cards.
—-Power-On Logo	Enabled	Disabling has no improvements on boot-times.
–Video Options	Optional Video Primary, Embedded Video Disabled	Default setting.
–Power Supply Requirements Override	Default Power Supply Requirements	PSU requirements will be calculated depending on server power requirements.
–Thermal Configuration	Optimal Cooling	Fans will run at their minimum speed for adequate cooling.  Saves some power since they don't run at full speed (less noise as well)
–Advanced Performance Tuning Options
—-HW Prefetcher	Enabled	In previous CPU generations, disabling this options gave better performance. With the Nahalem architecture, it does provide benefits (better caching)
—-Adjacent Sector Prefetch	Enabled	Similar to HW Prefetcher.
—-Hemisphere Mode	Auto	Hemisphere will be enabled if your memory configuration allows it (see HP QuickSpecs for optimal Hemisphere modes)
—-Node Interleaving	Disabled	Since vSphere utilizes NUMA nodes, there is no need to disable NUMA (= enable Node Interleaving)
–Drive Write Cache	Disabled	Only the DVD-ROM drive is attached to the onboard SATA controller. Writes are not possible to this device thus it can be left disabled. This setting has NO effect on the Smart Array Controller settings.
–Asset Tag Protection	Unlocked

Ref: http://boerlowie.wordpress.com/2010/09/03/recommended-bios-setting-on-hp-proliant-dl580-g7-for-vsphere

Remote monitoring Sun Systems using ipmitool

The open-source tools ipmitool can be used to help manage and monitor Sun via the IPMI.

 

 

Chasis Status

# ipmitool -I lan -U root -H 192.168.1.5chassis status

 

Change Password

# ipmitool -I lanplus -H <IP Address> -U root -P <oldpassword> user set password 2 <newpassword>

 

Managing the System Event Log

Use ipmitool's sel elist command to print out the contents of the System Event Log

# ipmitool -I lan -H 192.168.1.5-U root sel elist

 

If the System Event Log contains a large number of entries, the last modifier can be used with the sel elist subcommand to show only a specific number of the most recent events.

# ipmitool -I lan -H 192.168.1.5-U root sel elist last 2

 

Clear the System Event Log

# ipmitool -I lan -H 192.168.1.5-U root sel clear

 

Use the led get command to display the state of the LED lights on a system

# ipmitool -I lan -H 192.168.1.5-U root sunoem led get

 

Use the sdr command to display sensor values

# ipmitool -I lan -H 192.168.1.5-U root sdr type voltage

 

Display the Service Processor's network configuration

# ipmitool -I lan -H 192.168.1.5-U root lan print 1

 

Print a list of all Field Replaceable Unit (FRU) inventory data

# ipmitool -I lan _H 192.168.1.5-U root fru print

 

Use the restart_cause command to display the cause of the last system restart

# ipmitool -I lan -H 192.168.1.5-U root chassis restart_cause

 

Perform a hard reset of a remote system

# ipmitool -I lan -H 192.168.1.5-U root chassis power reset

 

Request a PXE boot on the next reboot

# ipmitool -I lan -H 192.168.1.5-U root chassis bootdev pxe

 

Some more….

 

Run the following against the Ilom:

ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> bmc info
ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> sel elist
ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> fru
ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> sensor
ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> sunoem led get all

ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> sunoem sbled get all

ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> sdr elist
ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> sdr elist full
ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> sdr elist all
ipmitool -I lan -H <ILOM IP address> -U <ILOM Username> chassis status

 

 

 

 

HP Hard drive LED alert combinations

Hot-plug SCSI hard drive LED combinations

 

 

 

SAS and SATA hard drive LED combinations

 

Sun 6000 Modular System - Identify the IP and MAC Addresses

You must know the CMM IP address to log into the CMM through the NET MGT port. You also must know the IP address of the service processor (SP) of any server module that you want to log into through the network.

Perform this task to identify the CMM IP addresses, such as when you want to log into the CMM through your network and the DHCP server assigned the IP address.

1. Use one of the following methods to identify the CMM IP address:

   • Access the CMM ILOM though the SER MGT port.

   1. Connect a terminal device to the CMM SER MGT port.

   2. Log into the CMM though the CMM SER MGT port.

   3. View the CMM IP address and MAC address information:

      -> show /CMM/network    /CMM/network     Targets:         test       Properties:         commitpending = (Cannot show property)         dhcp_server_ip = none         ipaddress = 10.7.95.153         ipdiscovery = static         ipgateway = 10.7.95.254         ipnetmask = 255.255.255.0         macaddress = 00:21:28:3E:2B:B6         pendingipaddress = 10.7.95.153         pendingipdiscovery = static         pendingipgateway = 10.7.95.254         pendingipnetmask = 255.255.255.0         state = enabled         switchconf = port0

   4. View the IP addresses or MAC address of server modules, using the ILOM show command with the path of each server module.

      Replace the x in BLx with the number of the server module.

      -> show /CH/BLx/SP/network    /CH/BL0/SP/network     Targets:       Properties:         type = Network Configuration         commitpending = (Cannot show property)         ipaddress = 10.7.95.155         ipdiscovery = static         ipgateway = 10.7.95.254         ipnetmask = 255.255.255.0         macaddress = 00:21:28:14:F6:5B         pendingipaddress = 10.7.95.155         pendingipdiscovery = static         pendingipgateway = 10.7.95.254         pendingipnetmask = 255.255.255.0         state = enabled

   • On your DHCP server, review the IP address assignment information.

     Sometimes you can obtain the IP address assignments by viewing the DHCP log files on the server. If you know the MAC address of the CMM or server module, you can locate the IP address assigned to it.

     The CMM and server module MAC addresses are also listed on the Customer Information sheets that are included in a pouch on the outside of the shipping container.

How to inject SATA drivers (AHCI) after XP installation.

After installing XP Pro with BIOS Native IDE mode, you can add SATA drivers and switch back to AHCI mode with bellow steps

1) Copy bellow text to a notepad and change the file extension as ".reg" . Run it to change the registry entries.

2)Download Intel Matrix Storage Manager-Package for your make and model and extract its files by running using the following switches "-a –a"

3) Copy "iastor.sys " from freshly extracted folder to %Windows%\System32\Drivers\

4) Rrestart your computer, enter the BIOS and switch back to Advanced, AHCI-mode.

5) Save, exit and load Windows XP from your HD (it should now start properly).

6) When XP goes for the SATA driver-installation procedure, stop it and run Matrix Storage Manage setup from the previously extracted folder to complete the SATA installation

7) Restart your system.

Done

======================================================

Windows Registry Editor Version 5.00

; --
; traegt einige Betriebsmodi der SATA-AHCI-Hostadapter
; der I/O Controller Hubs
; ICH7R, ICH7-DH, ICH7M-DH
; ICH8R, ICH8-DH, ICH8-DO, ICH8-M, ICH8-ME
; ICH9, ICH9R, ICH9-DH, ICH9-DO
; ICH9-M, ICH9-ME (experimentell)
: ICH10, ICH10R
; der Intel-Chipsaetze
; 955X, 945P, 945G, P965, G965, Q965, Q963
; 945GM, 945PM, 965GM, 965PM
; G31, G33, G35, P31, P35, X38, X48
; G43, G45, P43, P45
; GM45, GM47, PM45
; Q45, P55 (experimentell)
; in die Registry einer Windows-XP-Installation ein
; (XP Home, Professional, x64 Professional Edition).
; --
; Der Treiber IaStor.sys muss man manuell kopieren
; in das Verzeichnis
; %SYSTEMROOT%\system32\drivers\iaStor.sys
; Weitere Tipps: c't 23/05, S. 210
; und
; SATA-AHCI-Treiber nachrüsten:
;
; Weitere Informationen:
; ICH7R: www.intel.com/design/chipsets/datashts/307013.htm
; IaStor.sys:
; Enthalten in Intel Matrix Storage Manager (IMSM), 32- und 64-Bit:
; http://support.intel.com/support/chipsets/imsm/
; Trademarks: Intel (www.intel.com), Microsoft (www.microsoft.com)

; ICH7 AHCI
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c1]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH7-M AHCI
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c5]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH7 RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c3]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH7-M DH RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_27c6]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH8, ICH8R, ICH8-DO, ICH8-DH AHCI 6-Port
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2821]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH8, ICH8R, ICH8-DO, ICH8-DH AHCI 4-Port
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2824]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH8, ICH8R, ICH8-DO, ICH8-DH RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2822]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH8-M, ICH8-ME AHCI
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2829]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH8-M RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_282A]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH9, ICH9R, ICH9-DO, ICH9-DH AHCI Ports 0-5
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2922]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH9, ICH9R, ICH9-DO, ICH9-DH AHCI Ports 0, 1, 4, 5
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2923]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH9R RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2822]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH9R RAID Alternativ je nach Bit 7 im Register D21:F2:9Ch (siehe Datenblatt)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2925]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH9-M, ICH9-ME AHCI
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2929]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH9-M RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_282A]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH9-M RAID Alternativ je nach Bit 7 im Register D21:F2:9Ch (siehe Datenblatt)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_292C]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH10, ICH10R AHCI Ports 0-5
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3A22]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH10R RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3A25]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH10DO AHCI
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3A02]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; ICH10DO RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3A05]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; P55 AHCI Port 0-5
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3B22]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; P55 AHCI Port 0,1,4,5
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3B23]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; P55 RAID ist 3A25 wie ICH10R

; P55 Mobile AHCI Port 0-5
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3B2F]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; P55 Mobile AHCI Port 0,1,4,5
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3B29]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

; P55 Mobile RAID
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_3B2C]
"Service"="iaStor"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor]
"Type"=dword:00000001
"Start"=dword:00000000
"Group"="SCSI miniport"
"ErrorControl"=dword:00000001
"ImagePath"="system32\\drivers\\iaStor.sys"
"tag"=dword:00000019
"DisplayName"="Intel AHCI Controller"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Parameters]
"AtapiOnPrimary"=dword:ffffffff
"AtapiOnSecondary"=dword:ffffffff

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor\Enum]

=====================================================================

Intel Matrix Storage driver Windows XP and STOP: 0x0000007B - SCCM OSD

Drop down box on the Apply Driver Package TS action only allows you to select drivers where Class=SCSIAdapter. The AHCI drivers you're talking about in this thread have Class=hdc by default.

 Follow the bellow steps to get the AHCI drivers to work:

1. Delete the nonfunctional Intel AHCI & RAID Controller drivers from my Drivers list in SCCM

2. Extract the downloaded mass storage drivers to a temp directory

3. Edit the iaahci.inf file by changing the line that says Class=hdc to instead say Class=SCSIAdapter

4. Import the driver into SCCM, add to the appropriate driver package and update my DP

5. Edit my Apply Driver Package TS to select the appropriate AHCI driver

 

Unknown Device Identifier

Unknown Device Identifier enables you to identify the yellow question mark labeled Unknown Devices in Device Manager. And reports you a detailed summary for the manufacturer name, OEM name, device type, device model and even the exact name of the unknown devices. With the collected information, you might contact your hardware manufacturer for support or search the Internet for the corresponding driver with a simple click. With this utility, you might immediately convert your unidentified unknown devices into identified known devices and find proper driver on the Internet and contact the hardware device manufacturer or vender. Known devices recognized by Microsoft Windows will also be analyzed independent of the operating system.

Download Page: http://www.zhangduo.com/udi.html

How to clear an unknown BIOS password.

If you have mistakenly forgot or lost your BIOS password or you receive a password at boot that you do not know, you will need to clear the BIOS password by one of the below methods

On the computer motherboard locate the BIOS clear / password jumper or dipswitch and change its position. Once this jumper has been changed, turn on the computer and the password should be cleared. Once cleared, turn the computer off and return the jumper or dipswitch to its original position

For more reference click here