USB / CD boot - Perc 4e DC Controller

Booting from Knoppix? What do you want to do? Backup you data at system with not starting os?

Not sure want you want to do,

BartPE

http://www.nu2.nu/pebuilder/

 

 

Do you have your Dell OpenManage Server Assistant CD? If not you need to download perc-cerc-w2k3-6.41.2.32-A04.exe, this of course is dependant upon your NOS! If you are using Windows Server 2003, the one listed would be the one you need. Below are instructions from the above exe file.


Dell PowerEdge RAID Controller Device Driver for Windows 2003.

Version 6.41.2.32


TABLE OF CONTENTS

1.0 Introduction
2.0 Compatibility / Minimum Requirements
3.0 Install Instructions
3.0.1 Installing on a new driver on a Windows Server 2003 system
3.0.2 Adding the PERC/CERC Driver to an Existing Windows Server 2003.
3.0.3 Updating the PERC/CERC Driver on an Existing Windows Server 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 4e/Di, 4e/Si, 4e/DC
PERC 4/Di, 4/DC, 4/SC
PERC 3/QC, 3/DC, 3/DCL, 3/SC
CERC ATA100/4CH


2.0 Compatibility / Minimum Requirements

This Device Driver is compatible with the following firmware versions:

Controller Minimum firmware level Description

PERC 3/QC 1.92 PERC 3 Quad Channel
PERC 3/DC 1.92 PERC 3 Dual Channel
PERC 3/DCL 1.92 PERC 3 Dual Channel Lite
PERC 3/SC 1.92 PERC 3 Single Channel
PERC 4/Di 4.04 PERC 4 Integrated on PE 1750
PERC 4/Di 2.37 PERC 4 Integrated on PE 2600
PERC 4/SC 3.28 PERC 4 Single Channel
PERC 4/DC 3.28 PERC 4 Dual Channel
PERC 4e/Di 512i PERC 4e Integrated on PE 2800, 2850
PERC 4e/Si 512i PERC 4e Integrated on PE 1850
PERC 4e/DC 512i PERC 4e Dual Channel
PERC 4e/SC 512i PERC 4e Single Channel
CERC ATA100/4CH 6.62 CERC Quad Channel IDE


3.0 Install Instructions

This package is a self-extracting package of the Windows 2003 device driver
installation diskette for PERC 4/DC, 4/SC, 3/QC, 3/DC, 3/DCL, 3/SC, 2/DC, 2/SC,
CERC ATA100/4CH, PERC 4/Di, PERC 4e/Di, PERC 4e/Si, and PERC 4e/DC.

XXXX.EXE - Self-extracting package to create Windows 2003 device driver
installation diskette

To build the installation diskette, execute the package, directing it's output
to an empty formatted diskette.


3.0.1 Installing on a new driver on a Windows Server 2003 system

1. Boot the system using the Windows Server 2003 CD. As the message

"Press F6 if you need to install a third party SCSI or RAID driver."

appears, press F6 immediately.

2. Within a few minutes, a screen appears that asks for additional adapters in
the system. Choose 'S'.
3. You are prompted for the driver diskette. Insert the PERC/CERC Windows Server
2003 driver diskette in the floppy drive and press Enter.
4. A list of drivers for PERC/CERC controllers appears. Select the right driver
for your installed controller and press Enter to load the driver.
5. A statement is presented saying the driver that you provided is older/newer
then the Windows driver.

Press 'S' to use the driver on the floppy.

6. Press Enter again to continue installation process as usual.


3.0.2 Adding the PERC/CERC Driver to an Existing Windows Server 2003.

1. Boot the system to Windows 2003. The Found New Hardware Wizard displays.

2. If you are installing the PERC 3/SC, PERC 4/DC PERC 4/SC, PERC 4/DI or
CERC ATA100/4CH, click on Next and skip to step 5. Otherwise, click Cancel
on all the new devices.
3. Restart the system from the shutdown menu.
4. The Found New Hardware Wizard displays again when the system boots to Windows
Server 2003. Click on Next.
5. Select Search for a suitable driver and click Next to continue.
6. Select Floppy disk drive, insert the PERC/CERC Windows 2003 driver diskette
created above and click Next to continue.
7. Continue to click on Next and finish the installation.
8. The Found New Hardware Wizard screen appears one time for each PERC 3/SC,
PERC 4/SC, PERC 4/DC controller, three times for each PERC 3/DC or PERC
3/DCL controller and four times for each PERC 3/QC. Repeat steps 5 - 7 for
each time the wizard displays to complete installation of the card.
9. To confirm driver installation, right click on My Computer and select Manage.
Click on Device Manager, then click on SCSI and RAID controllers to see the
newly added PERC 3 controller(s) in the list.
10. Restart the computer for the changes to take effect.


3.0.3 Updating the PERC/CERC Driver on an Existing Windows Server 2003.

If your server is already running Windows Server 2003, use the following steps
to update the PERC Windows Server 2003 driver.

NOTE: If your driver supports multiple RAID controllers, make sure to upgrade
all the RAID controllers in your system that your driver supports.

1. Insert the PERC/CERC Windows Server 2003 driver diskette.
2. Position the mouse pointer to the my computer icon in the Start menu and
right click and select Manage.
3. Position the mouse pointer on Device Manager and click the left mouse button.
4. Position the mouse pointer on SCSI and RAID controllers and double click.
5. Select the PERC controller and double click.
6. Select the Driver tab.
7. Select Update Driver.

The Upgrade Device Driver Wizard displays.

8. Select Install from a list or specific location and click Next to continue.
9. Select Search for the best driver in these locations.
10. Make sure that Search removable media is checked and click Next to continue.
11. When you see the Completing the hardware Update Wizard window click on
Finish.
12. When prompted to restart your computer, click on No.
13. Close the SCSI and RAID controller by clicking the + box and position the
mouse pointer on System Devices and double click.
14. Repeat steps 6 -11 for each of the following devices under System Devices:

RAID Controller Component Device
RAID Virtual Device

15. Restart the computer.

After finishing the driver update, YOU MUST REBOOT YOUR SERVER.


4.0 Fixes or Enhancements in this Release

1. A timer routine has been added to the driver's reset path which will be periodically be invoked and will calculate the actual system time elapsed from the start of the issuing of reset. If more than 3 minutes elapse, the adapter will be marked as failed.
In a cluster environment during heavy I/O, this would prevent the driver from stalling the CPU and allow the cluster to failover instead of freezing.

2. 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 logical drive mismatch between the OS and the RAID management utilities.

3. Support added for PERC 4e/Si,PERC 4e/Di,PERC 4e/DC, PERC 4e/SC.

4. The driver addresses a potential system freeze during reset.

5. The driver now returns the Bus interrupt level in the PCI information structure
for use in the RAID utilities.

6. The TimeOut Value in the Registry entry under Disk.sys has been increased to 60 secs from 40 secs to prevent Event ID 9.

7. Support for MegaRAID SCSI 320-0X support added to the registry.

8. Support has been added for the SATA(523) SAF-TE device from AMI.

9. Support has been added for the Intel(R) Storage RAID Controller SRCU42 to the driver and the setup files.


5.0 Additional Information

1. When installing a PERC 3/DCL controller in a system, Windows will
automatically load a different PERC driver. This driver will show the PERC
3/DCL as a PERC 3/DC. You must upgrade the driver to the latest shipping level
and after this upgrade the PERC 3/DCL will be displayed correctly.

2. When installing Windows Server 2003 in a system and have a PERC 3/QC, PERC
3/DC, PERC 3/DCL, PERC 3/SC, PERC 4/DC or PERC 4/SC together in a system you
will see the following selection when choosing a logical drive to configure.

(xxxxx)mb Disk 0 at Id on bus on mraid35x [MBR]

Where (xxxxx) is the size of the logical drive.
Where (y) is the logical drive id per controller.
Where (z) is the bus number.
z=2 PERC 3/SC or PERC 4/SC
z=3 PERC 3/DC,PERC 3/DCL or PERC 4/DC
z=5 PERC 3/QC

If there is more than 1 logical drive per controller then id number will be
incremented.

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]

(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 2003.


6.0 Revision History

Changes from 6.32.2.32 to 6.35.2.32

1. Minor change to Oemsetup.txt file.
2. Driver no longer filters out all other commands except SCSI READ and SCSI
WRITE


Changes from 6.25 to 6.32.2.32

1. Changes in the setup files, so that Scsiport driver should give the correct
device number and function number to the miniport driver.
2. A timeout is implemented in the driver so that driver shouldn't wait
infinitely for the firmware to acknowledge the interrupt.
3. The driver will return an error status for all the offline logical drives.
4. Utilities are issuing 0xc3 calls for getting the logical drive statistics.
This is causing the system to crash. This bug has been fixed in the driver.
5. The driver is using Hal functions to program hierarchy bridges and SCSI
chips when system goes to D3 standby state.

The use of Hal functions were not allowing the driver to pass the HCT test.
So we have to disable the Hal calls in the previous releases. A workaround
has been done in the driver whereby all the Hal calls have been replaced by
its assembly equivalent.
6. During reset, the driver was not clearing all the pending commands whenever
the firmware is not able to complete it.
7. Driver is allocating enough continuous memory for the
FLASH_WRITE_BLOCK(0x2c) command.
8. The system gives a blue screen when one swaps the boot controller. 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.inf file.
9. The system was not waking up after a hibernation/standby operation. This bug
was caused by the driver. The driver was trying to access PCI_CONFIG space from
the ScsiRestartAdapter in the driver. This bug has been fixed by accessing the
PCI_CONFIG space from the ScsiSetRunningConfig entry point.
10. A new command has been introduced to enhance the performance for SCSI I/O on
non-raid SCSI channel.
11. In case of standby, the driver was not waiting for the firmware to get
initialized. This resulted in the driver sending commands to the firmware
even when the firmware is not initialized. The fix has been put in the
driver. The driver is polling for the Firmware to get initialized before
sending any commands to the firmware.
12. The PERC 3 Firmware was not able to handle multiple reserve commands for a
logical drive. This was leading to reservation failures on some of the
logical drives. 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
before issuing any more commands to the firmware.

Message Edited by AlaskaNetMgr on 07-18-200604:41 PM