Dell PowerEdge RAID Controller Device Driver for Windows 2000 and 2003. Windows 2000 Version 5.

48 Windows 2003 Version 6.46.2.32 TABLE OF CONTENTS 1.0 Introduction 2.0 Compatibility / Minimum Requirements 3.0 Install Instructions 3.1 Installing the Driver during Operating System Installation 3.2 Installing a Windows 2000 or 2003 Driver for a New RAID Controller 3.3 Updating an Existing Windows 2000 or 2003 Driver 3.4 Installing PERC 4/DC, 4/SC or PERC 4e/DC Controllers in Windows 2000 an d Windows 2003 Operating Systems with PERC 3/SC, 3/DCL or PERC 3/DC Contr ollers 3.5 Migrating from a PERC 3/DC, 3/DCL, 3/SC Controller to a PERC 4e/DC, 4/D C or PERC 4/SC Controller in Windows 2000 or 2003 4.0 Fixes or Enhancements in this Release 5.0 Additional Information 6.0 Revision History 1.0 Introduction ================ This is the driver for following PowerEdge Expandable RAID Controllers: PERC PERC PERC CERC 4e/Di, 4e/Si, 4e/DC 4/Di, 4/DC, 4/SC 3/QC, 3/DC, 3/DCL, 3/SC ATA100/4CH

2.0 Compatibility / Minimum Requirements ======================================== This Device Driver is compatible with the following firmware versions: Controller PERC 3/QC PERC 3/DC PERC 3/DCL PERC 3/SC PERC 4/Di PERC 4/Di PERC 4/SC PERC 4/DC PERC 4e/Di , 6800, 6850 PERC 4e/Si PERC 4e/DC CERC ATA100/4CH Minimum Recommended Firmware Level 198Q 198Q 198Q 198Q 421Q 251Q 351Q 351Q 521Q 521Q 521Q 6.62 Description PERC PERC PERC PERC PERC PERC PERC PERC PERC 3 Quad Channel 3 Dual Channel 3 Dual Channel Lite 3 Single Channel 4 Integrated on PE 1750 4 Integrated on PE 2600 4 Single Channel 4 Dual Channel 4e Integrated on PE 2800, 2850

PERC 4e Integrated on PE 1850 PERC 4e Dual Channel CERC Quad Channel IDE

Select the right driver for the installed controller and press the <Enter> key to load the driver. 11. Power down the system. 3. On the Locate device driver screen. Boot the system using the Microsoft Windows Server 2000/2003 CD. 3/SC. A list of PERC controllers appears. The Windows operating system should detect the new controller and display a message to inform the user. 3/DCL. directing its output to an empty. Install the new RAID controller in the system. 1. 3. When the message Press F6 if you need to install a third party SCSI or RAID driver appears. 3/QC. Within a few minutes. 3. 5. . Insert the driver diskette in the floppy drive and press the <Enter> key. 5. Press the <S> key to use the driver that is on the floppy diskette. 2. a message appears that states that the driver that you provided is older/newer then the Windows driver. PERC 4/Di. 2. Insert the appropriate driver diskette and select Floppy disk drives on the Locate Driver Files screen. 3/DC. To build the installation diskette. The wizard detects and installs the appropriate device drivers for the new RAID controller. select Search for a suitable driver for my device and click Next. Press the <S> key.0 Install Instructions ======================== This is a self-extracting package of the Windows 2000 and 2003 device driver installation diskette for PERC 4/DC. press the <F6> key immediately.1 Installing the Driver during Operating System Installation -------------------------------------------------------------1. Click Next. PERC4e/Si and PERC 4e/DC.3. 7.2 Installing a Windows 2000 or 2003 Driver for a New RAID Controller ---------------------------------------------------------------------Perform the following steps to configure the driver when you add the RAID controller to a system that already has Windows installed. CERC ATA100/4CH. formatted diskette. 4. NOTE: For Windows 2003. 9. Power on the system. Click Next. 8. 3. 6. Reboot the server. The Found New Hardware Wizard screen pops up and displays the detected hardware device. 4. a screen appears that asks for additional controllers in the system. execute the package. PERC 4e/Di. 6. 10. 4/SC. The system prompts for the driver diskette to be inserted. Refer to Hardware Installation for detailed instructions on installing and cabling the RAID controller in the system. Click Finish to complete the installation. Press the <Enter> key again to continue the installation process as usual.

1. Insert the appropriate driver diskette. 10. 3. Double-click SCSI and RAID Controller. press Start > Control Panel > System. The screen for the Upgrade Device Driver Wizard displays. . 3/DCL. A list of all currently installed SCSI drivers appears. Click Next and continue the installation steps in the Wizard. 2. NOTE: In Windows 2003. 3. 3. . 3/DCL and PERC 3/DC controllers. Click SCSI and RAID Controllers. Click Finish to exit the wizard and reboot the system for the changes to tak e place.3 Updating an Existing Windows 2000 or 2003 Driver ---------------------------------------------------Perform the following steps to update the windows driver for the RAID controller already installed on your system. Click on the Hardware tab. 5. not the INF file. Left-click Manage. Follow the steps in the Wizard to search the diskette for the driver. Double-click the RAID controller for which you want to update the driver. Click the Driver tab and click on Update Driver. Click Device Manager. Select the Driver tab. 6. 7. 9. 6. Double-click the appropriate RAID controller (such as PERC 3/DC RAID Controller). NOTE: The PERC 4/DC. 2. Click Next. 7. 4/SC and PERC 4e/DC drivers for Windows 2000 and Windows 2003 operating systems are compatible with PERC 3/SC.Install PERC 4/DC or 4/SC controllers in Windows 2000 or Windows 2003 operating systems . 8. 4. 4.3. NOTE: It is important that you idle your system before you update the driver. Select the INF file from the diskette. 5. select the name of the driver. 11. 4/SC or PERC 4e/DC Controllers in Windows 2000 and Windows 2003 Operating Systems with PERC 3/SC.4 Installing PERC 4/DC. Click the Device Manager and the Device Manager screen displays. Press Start > Settings > Control Panel > System. From the desktop.Update the PERC 3/DC. Select Update Driver.Install the PERC 4/DC or 4/SC drivers for the newly installed controllers NOTE: You must be logged on as Administrator to perform these steps. 12. right-click on the My Computer icon. NOTE: In Windows 2003. or 3/SC drivers to PERC 4 drivers. 3/DCL or PERC 3/DC Controller s -------------------------------------------------------------------------------The following steps should be performed in the following order: . The System Properties screen displays. 1.

17. 20. Select the appropriate driver for Windows 2000 or Windows 2003. the Completing the Found Ne w Hardware Wizard window appears. During boot up. Refer to the Hardware Installation section for detailed instructions on installing and cabling the RAID controller in the system. 26. Click OK. if not already selected. The Install Hardware Device Drivers window appears. 9. 11. The Driver Files Search Results window appears. The Select a Device Driver Wizard appears. 24. If it does not. and click Next. Shut down and remove power from the system. 25. 22. the PERC 4/DC or 4/SC BIOS banner should display indicating the presence of the new controllers in the system. 16. 19. Make sure that only the Floppy disk drive option is selected. Click Next. A driver warning dialog box appears. 4/SC or PERC 4e/DC controller into your system s diskette drive and click Next. 15. Locate the driver diskette for Windows 2000 or Windows 2003 provided with your PERC 4/DC or PERC 4/SC controller kit and insert it in the diskette dri ve. Click Finish to complete the installation and exit the wizard. 14. The Start Device Driver Installation dialog box appears. Select the Search for a suitable driver for my device (recommended) option. Power on the system. Click Finish. Click Yes to continue. Click Display a list of known drivers for this device so I can choose a specific driver. When Windows has finished installing the driver. Click Next. 8.The Update Device Driver Wizard displays. Install the new PERC 4/DC or 4/SC controller(s) and connect the internal SCS I cables appropriately. Windows 2000 or Windows 2003 starts. and starts the Found New Hardware Wizard. 23. Insert the driver diskette that came with your PERC 4/DC. displaying the driver found on the diskette that matches the device you are installing. 18. Click Next. NOTE: You can also create a diskette with the latest version of the driver b y accessing support. . The Locate Driver Files dialog box appears. displays a message that new hardware ha s been detected.com and downloading the latest version available onli ne. A list of PERC 4/DC and 4/SC drivers available on the diskette appears.dell. Log on as an administrator. Click Next. 10. power the sys tem down and refer to the Troubleshooting section. 12. Click Next. Click Have Disk. 21. 13. The Install from Disk dialog box appears.

or 4/SC controllers the following broad tasks must be completed in order: 1. 3. Repeat step 8 through step 17 to install the correct driver for the SCSI controller. PERC 4/DC. 5. 3/DCL.5 Migrating from a PERC 3/DC. indicating that Windows 2000 or Windows 2003 found a device labeled SCSI Controller. 2. When you have installed a ll of the necessary drivers. 30. Click Close. including operating system and user data files before making this upgrade. Make sure you back up the entire system. A list of all currently installed SCSI drivers appears. perform the following steps: NOTE: You must be logged on as Administrator to perform these steps: 1. Click on Device Manager and the Device Manager screen displays. Click on Manage. From the desktop. 31. 29. 4/SC or PERC 4e/DC controller. Upgrading from PERC 3/SC. Update the device driver (use the procedure appropriate for your operating system).1 Updating the Device Driver in Windows 2000 or 2003 -------------------------------------------------------To remove the PERC 3/DC. 3. 3/DCL or PERC 3/SC controllers to the PERC 4/DC. The Found New Hardware Wizard appears.27. Do not roam drives during drive migration. Set the desired write-back or write-through policy using the PERC BIOS Configure Utility 3. 4/DC or PERC 4/SC Controller in Windows 2000 or 2003 ------------------------------------------------------------------------------This section provides details for upgrading from the PERC 3/DC. 2. Keep the controllers on the same ID. perform step 24 once to inst all one driver for the device labeled SCSI Controller.or PERC 4/SC controller. NOTE: If you are adding a PERC 4/DC controller. 3/SC Controller to a PERC 4e/DC. Double-click the appropriate RAID controller to be removed (such as . To upgrade to PERC 4e/DC. the Completing the Found New Hardware Wizard windo w appears. PERC 4/DC or 4/SC drivers to a system running the Microsoft Windows 2000 or Windows 2003 operating system. Restart your system. Click Finish. 32. Click Finish. 3/DC and 3/DCL is direct and easy. PERC 4/DC. 3/DCL. 3/DCL controller and install the PERC 4e/DC. 3/DC. 28. The Dell PERC 4/DC. 4.5. 3. right-click the My Computer icon. 4/SC or PERC 4e/DC RAID Controller Properties window app ears. NOTE: PERC controller cards cannot support drive roaming and drive migration at the same time. Double-click SCSI and RAID Controller. The Completing the Upgrade Device Driver Wizard window appears. 3/SC drivers and install the PERC 4e/DC. Remove the PERC 3/SC.

Shut down and remove power to the system and any attached external peripheral s. 12. 1. 4/DC or PERC 4/SC Controller on a Windows 2000 or 2003 System ------------------------------------------------------------------The following procedure applies to Windows 2000 and Windows 2003 operating systems. 4/DC or PERC 4/SC drivers available on the diskette ap pears.5. A list of PERC 4e/DC. Click OK. The Start Device Driver Installation dialog box appears. follow the procedure Removing the PERC 3/DC. Click Yes to continue. 8. Locate the driver diskette for Windows 2000 or Windows 2003 provided with your PERC 4e/DC. 3. Disconnect the connectors attached to the PERC 3/DC. 3. 17. 2. 3/DCL or PERC 3/SC Controller and Installing the PERC 4e/DC. Click Display a list of known drivers for this device so I can choose a specific driver. . 19. 3/DCL or PERC 3/SC Controller and Installing the PERC 4e/DC. 3/DCL. 11. 14. Click Have Disk.) 4. The Update Device Driver Wizard appears. 10. Click on Update Driver. 20. Click Next. CAUTION: If the SCSI connectors are not properly identified with their channel identification. Label the SCSI connectors that connect to the 3/DC. A driver warning dialog box appears.2 Removing the PERC 3/DC. perform the following steps: CAUTION: See the safety instructions in your System Information booklet before working inside your system. or 3/SC controller. 4/DC or PERC 4/SC Controller on a Windows 2000 or 2003 System. The Select a Device Driver Wizard appears. Click Next. 18. Select the Driver tab. Click Next. The Completing the Upgrade Device Driver windows appears. To remove the PERC 3/DC. Click Close. 7. 15. Click Finish. See the system Installation and Troubleshooting Guide for detailed instructio ns. 16.PERC 3/DC RAID Controller). Select the appropriate driver for Windows 2000 or Windows 2003. The Install from Disk dialog box appears. 4/DC or PERC 4/SC controller kit and insert it in the diske tte drive. Next. 3/DCL and 3/SC controlle r and remove them from the system. Click Next. Remove the system cabinet cover. the PERC 4 controller firmware may be unable to convert to the correct logical drive configuration (performed in the next procedure. 6. 3/DCL and 3/SC controller connectors. 9. 13.

This is an indication of normal background initialization being performed by the PERC 4 controllers. Performance should be back to normal after initialization is complete. 8.See the systems Installation and Troubleshooting Guide for instructions. 6.3 Changing the Write Policy ------------------------------If the new PERC 4e/DC. you should change the write policy from Write-Through to Write-Back for additional performance improvements. The configuration data on the hard drive is used automatically if there is a configuration mismatch (assuming the new controller has no configuration). This . 4. Reconnect the system and peripherals to their power sources. Otherwise. Background initialization could take hours to complete. If the new adapter does not include the battery backup unit. select WrBack. although I/O response may be slow. the disk activity LED blinks after the BIOS configuration is complete. 4/DC. During Bus Reset. 7. 4/DC or PERC 4/SC controllers have different battery backup settings than the previous controllers. 9. Reboot your system for the changes to take place. 3. change the write policy settings. PERC 3/SC and PERC 3/DCL controllers do not include a battery backup unit. Press <Esc> as many times as necessary to return to the Logical Drive Menu. you must change the write policy of the logical drive to obtain additional performance improvements or avoid data corruption in the event of power loss. 7. Select WrBack or WrThru according to the battery unit setting. If you are upgrading from a PERC 3/SC to a PERC 4/DC. To 1. 3. 9. If you are upgrading a PERC 3/DC to a PERC 4/DC with the same battery backup settings.0 Fixes or Enhancements in this Release ========================================= W2K 5. Close or replace the system cabinet cover. 2. Power on the system. while the PERC 4/DC and PERC 3/DC do have a battery backup unit. Repeat step 2 through step 6 for each logical drive. 4. select WrThru. depending on the size of the logical drives. 8. Select View/Update Parameters and press <Enter>. the driver issues a call to the F/W and returns without waiting for the call to finish and asks for the next request from OS. Select the logical drive and press <Enter>.5. NOTE: If you have configured a RAID 5 system with more than four physical drives . select the Object > Logical Drive menu. The server is usable. Refer to Hardware Installation for detailed instructions on installing and cabling the RAID controller in the system. 6. you do not need to change the write policy. or 4/SC controller and install the SCSI cables you removed in step 4. For example. 5. Select Write Policy and press <Enter>. perform the following steps: From the PERC BIOS Configure Utility.48 1. Install the PERC 4e/DC. 5.

5. PERC 4/SC. Where (y) is the logical drive id per controller. If the Adapter is set to DEAD. If there is more than 1 logical drive per controller then Id number will be incremented. 3. PERC 4/DC. (xxxxx)mb Disk 0 at Id (y) on bus (z) on mraid35x [MBR] (xxxxx)mb Disk 0 at Id (y) on bus (z) on mraid35x [MBR] The user must be careful to select the appropriate id when installing Windows Server 2000 or 2003. 6. Driver should have rejected all the commands issued to the Dummy Device except for the SCSIOP_INQUIRY and SCSIIO_READ_CAPACITY. Now the driver does not issue the next command until the reset call to the F/W completes. PERC 4e/DC. all the IOCTLs sent to the driver will be returned with a special signature 0xEE to identify that the adapter is DEAD and not responding. 2. Now the driver does not issue the next command until the reset call to the F/W completes. This was causing the system to blue screen when using utilities sending SCSI commands to the Dummy Device. When installing a PERC 3/DCL controller in a system. W2K3 6. This driver will show the PERC 3/DCL as a PERC 3/DC. or PERC 4e/Di together in a system you will see the following selection when choosing a logical drive to configure. During Bus Reset. PERC 3/SC. If there is more than 1 type of controller in a system then multiple selections will be displayed per controller. (xxxxx)mb Disk 0 at Id <y> on bus <z> on mraid35x [MBR] Where (xxxxx) is the size of the logical drive. When installing Windows Server 2000 or 2003 in a system and have a PERC 3/QC.0 Additional Information ========================== 1. SCSI commands issued to the Dummy Device exposed by the driver was not handled properly. You must upgrade the driver to the latest shipping leve l and after this upgrade the PERC 3/DCL will be displayed correctly.0 Revision History ==================== .2. This release driver handles all the SCSI commands issued to the driver gracefully.next request got issued to the F/W even before the reset call completed resulting in the reservation conflict.46. This next request got issued to the F/W even before the reset call completed resulting in the reservation conflict. PERC 3/DC. Where (z) is the bus number. Windows will automatically load a different PERC driver. 2. PERC 3/DCL.32 1. the driver issues a call to the F/W and returns without waiting for the call to finish and asks for the next request from OS.

this would prevent the driver from stalling the CPU and allow the cluster to failover instead of freezing. If more than 3 minutes elapse. This bug has been fixed in the driver by returning all the calls with lesser buffer si ze without copying any data successfully. 3. We have seen some utilities are requesting 40LD statistics but send buffer le ss than the required statistics size. 7. W2K Changes from 5. The fix is made in the driver to improve delay optimization for the mailbox busy condition. .35. 3. 4. System was hanging after it wakes up from Hibernation/Standby on PERC 3/QC and PERC 3/DC controllers.PERC 4e/Di.W2K Changes from 5.46 1. Minor change to the setup files. 2. During the Cluster HCT phase 5 test the driver and firmware used to wait for each other for a command completion. In order to avoid this dead lock conditi on the driver will poll the firmware for completion of a command before the OS times out the command. 6. Utilities are issuing driver calls for getting the logical drive statistics. Driver needs to reprogram these SCSI chips before waiting for the firmware to initialize. 5. The driver will now expose a failed logical drive to the OS and will complete the failed I/O request with the proper status information to prevent a logica l drive mismatch between the OS and the RAID management utilities. 3. the adapter will be marked as failed. 2. This is causing the system to crash.and PERC 4e/DC.39 to 5. A timer routine has been added to the driver's reset path which will periodically be invoked and will calculate the actual system time elapsed from the start of the issuing of reset. This led to dead lock condition and the HCT test fails with an IO timeout error. The driver will be using an individual commandID for each WriteConfig issued to the Firmware W2K Changes from 5. Change in the setup files. The driver will accept only one Reservation call at a time and would allow it to complete before issuing any more commands to the Firmware. File Version has been modified to reflect the product version from this release onwards. During Reset. 2. A timeout is implemented in the driver so that driver shouldn't wait infinitely for the Firmware to acknowledge the interrupt. In a cluster environment during heavy I/O. so that Scsiport driver should give correct Device Number and Function Number to the Miniport driver. When running heavy I/O's the miniport driver would often get a mailbox busy condition that would lead to an I/O hang. Support added for PERC 4e/Si.42 to 5. Driver was not clearing all the Pending Commands whenever the Firmware is not able to complete it. 5. Driver no longer filters out all other commands except SCSI READ and SCSI WRITE 4.42 1.39 1.2 to 5.

41. One can attach up to a maximum of 15 devices on a single physical channel. driver was not waiting for the Firmware to get initialized.and PERC 4e/DC. The driver addresses a potential system freeze during reset. If the commands are not completed in certain period of time. Driver completes al l the outstanding with error and returns. This bug has been fixed by accessing the PCI_CONFIG space from the ScsiSetRunningConfig entry point. This bug was caused by the driver. 3. 5. Driver was waiting infinitely for all the commands to complete.35. 5.32 1.32 to 5. This logic was removed since there is no need to check status of this device. W2K Changes from 5. the adapter will be marked as failed. Driver i s polling for the Firmware to get initialized before sending any commands to th e Firmware. 9.8.0 1.32 to 6. The capability pointer was changed in firmware for Fast READ/WRITE calls for hard drives connected to the SCSI Channels.PERC 4e/Di. The driver will now expose a failed logical drive to the OS and will complete the failed I/O request with the proper status information to prevent a logica l drive mismatch between the OS and the RAID management utilities. System was not waking up after a hibernation/standby operation. 3.2. The logical drive status checking was failing for Dummy Device inquiry. 2. If more than 3 minutes elapse. 2.35.2 1. Initial release of PERC 4/Di support on PE2755MC 11. W2K3 Changes from 6. All the requests coming for a physical channel with TargetID greater than 15 should be returned as Illegal request. The fix has been put in the driver. A timer routine has been added to the driver's reset path which will periodically be invoked and will calculate the actual system time elapsed from the start of the issuing of reset. In case of Standby.0. 10. 4. In case of cluster reset. resulting in the system crash/hang. this would prevent the driver from stalling the CPU and allow the cluster to failover instead of freezing. New command has been introduced to enhance the performance for SCSI I/O on non-raid SCSI channel. Initial release of PERC 4/SC. In a cluster environment during heavy I/O. Initial release of PERC 4/Di on PE2600. A single Tape drive was seen at TargetID 0 and TargetID 16 on the physical channel. This problem has been fixed by waiting for certain period of time for the outstanding commands to complete. Support added for PERC 4e/Si. The driver now returns the Bus interrupt level in the PCI information structu .32.2. W2K Version 5. Driver was trying to access PCI_CONFIG space from the ScsiRestartAdapter in the driver. 4. resulting in the driver sending commands to the firmware even wh en the Firmware is not initialized.

A new command has been introduced to enhance the performance for SCSI I/O on non-raid SCSI channel. Changes in the setup files. 7. This bug has been fixed by accessing th e PCI_CONFIG space from the ScsiSetRunningConfig entry point. This bug has been fixed by adding entries of all the supported controllers in the critical data base section of the registry through changes in the oemsetup. 2.32 1. 10. 4. The TimeOut Value in the Registry entry under Disk. A timeout is implemented in the driver so that driver shouldn't wait infinitely for the firmware to acknowledge the interrupt.txt file. The system gives a blue screen when one swaps the boot controller. W2K3 Changes from 6. Driver is allocating enough continuous memory for the FLASH_WRITE_BLOCK(0x2c) command.32 1. So we have to disable the Hal calls in the previous releases. The driver will return an error status for all the offline logical drives. 9. 5.sys has been increased to 60 secs from 40 secs to prevent Event ID 9. 12. 7. W2K3 Changes from 6. 3. 9. This bug has been fixed in the driver. Support for MegaRAID SCSI 320-0X support added to the registry. so that Scsiport driver should give the correct device number and function number to the miniport driver.32. This is causing the system to crash.2. om . The driver was trying to access PCI_CONFIG space fr the ScsiRestartAdapter in the driver. This was leading to reservation failures on some of the logical drives.re for use in the RAID utilities. This resulted in the driver sending commands to the firmware even when the firmware is not initialized. In case of standby. 6.inf file. Support has been added for the Intel(R) Storage RAID Controller SRCU42 to the driver and the setup files.25 to 6.35. A workaround has been done in the driver whereby all the Hal calls have been replaced by its assembly equivalent. The fix has been put in the driver. Utilities are issuing 0xc3 calls for getting the logical drive statistics. This bug was caused by the driver. During reset.2. The use of Hal functions were not allowing the driver to pass the HCT test. The PERC 3 Firmware was not able to handle multiple reserve commands for a logical drive. Minor change to Oemsetup. 2. Support has been added for the SATA(523) SAF-TE device from AMI. 8. Driver no longer filters out all other commands except SCSI READ and SCSI WRITE. A fix has been done in the driver where the driver would accept only one reservation call at a time and would allow it to complete 6.2. the driver was not clearing all the pending commands whenever the firmware is not able to complete it. the driver was not waiting for the firmware to get initialized. 11. The driver is using Hal functions to program hierarchy bridges and SCSI chips when system goes to D3 standby state.32 to 6. The system was not waking up after a hibernation/standby operation. The driver is polling for the Firmware to get initialized before sending any commands to the firmware.32. 8.

before issuing any more commands to the firmware. .

Sign up to vote on this title
UsefulNot useful