Dell™ PowerEdge™ Expandable RAID Controller 4/SC and 4/DC User's Guide
- Perc Scsi & Raid Devices Driver Download For Windows 10 Download
- Perc Scsi & Raid Devices Driver Download For Windows 10 64-bit
- Perc SCSI & RAID Devices Driver Download For Windows 10
Type: RAID Controller Card Model: PERC H710 Card Type: Serial Attached SCSI Integrated Raid Controller Card Data Transfer Rate: 6Gb/s Cache: 512MB Non Volatile Interface: SAS 6.0 Gps Series 7: PERC H710 Compatible Port/Slot: PCI Express 2.0 RAID Level: RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, RAID 50, RAID 60 SAS controller: LSI SAS 2208 dual. The newest type of SCSI, called Serial Attached SCSI (SAS), uses SCSI commands but transmits data serially. SAS uses a point-to-point serial connection to move data at 3.0 gigabits per second, and each SAS port can support up to 128 devices or expanders. All the different SCSI varieties use controllers and cables to interface with devices. Disk space is never enough. On an on-going basis system administrators will be getting request to increase the disk space on a server. In this article, let us review how to add new physical disks and create a virtual disk with a RAID configuration on an DELL PowerEdge Server using PERC 6/i Integrated BIOS Configuration Utility.
The Dell PERC 3 RAID (SCSI chip) Controller is designed to enhance the analog TV signal and transform it to a digital version compatible with the digital peripheral devices. A DVB-T Silicon tuner is an integrated chip in the controller that processes and translates the signals accordingly.
Requirements
This section describes the procedures for installing the PERC 4/SC/DC controllers. You must have the following items to install the RAID controller:
- A PERC 4/SC or 4/DC controller
- A host system with an available 32- or 64-bit, 3.3V PCI extension slot
- The Dell™ OpenManage™ Server Assistant® CD
- The necessary internal and/or external SCSI cables
- Ultra, Ultra2, Ultra3, Ultra160, or Ultra320 SCSI hard drives
(SCSI is backward compatible, but it slows to the slowest device).
Quick Installation Procedure
Perform the following steps for quick installation of the controller if you are an experienced computer user/installer. All others should follow the steps under the heading Installation Steps in this section.
- Turn off all power to the server and all hard drives, enclosures, and system components.
- Open the cabinet of the host system by following the instructions in the host system technical documentation.
- Determine the SCSI ID and SCSI termination requirements.
- Install the PERC 4 controller in the server and attach the SCSI cables and terminators.
- Make sure pin 1 on the cable matches pin 1 on the connector.
- Make sure that the SCSI cables you use conform to all SCSI specifications.
- Make sure pin 1 on the cable matches pin 1 on the connector.
- Perform a safety check.
- Make sure all cables are properly attached.
- Make sure the PERC 4 controller is properly installed.
- Close the cabinet of the host system.
- Turn power on after completing the safety check.
- Make sure all cables are properly attached.
- Format the hard drives as needed.
- Configure logical drives using the BIOS Configuration Utility, Dell Manager, or the WebBIOS Configuration Utility.
- Initialize the logical drives.
- Install the network operating system drivers as needed.
Installation Steps
This section provides instructions for installing the PERC 4 RAID controllers.
Step 1 Unpack the Controller
NOTICE: See the safety instructions in your system documentation for information about protecting against electrostatic discharge. |
Unpack and remove the controller and inspect it for damage. If the controller appears damaged, or if any items listed below are missing, contact your Dell support representative. The PERC 4 controller is shipped with:
- The PERC 4 RAID Controller User's Guide (on CD)
- The PERC 4 RAID Controller Operating System Driver Installation Guide (on CD)
NOTE: You can order a hard copy of the documentation for the controller. |
- A license agreement
- The PERC 4 Configuration Utilities diskette
Step 2 Power Down the System
Turn off the system and remove the AC power cord. Disconnect the system from any networks before installing the controller. Remove the system's cover. Please consult the system documentation for instructions.
Step 3 Set Jumpers
Make sure the jumper settings on the PERC 4/SC or PERC 4/DC controller are correct. Following are diagrams of the controllers showing their jumpers and connectors, and tables describing them. Select your controller from the ones shown on the following pages.
PERC 4/SC Jumpers and Connectors
Figure 3-1. PERC 4/SC Controller Layout
Connector | Description | Type | Default Setting |
---|---|---|---|
J1 | Internal SCSI connector | 68-pin connector | Internal high-density SCSI bus connector. |
J2 | NVRAM Clear | 2-pin header | To CLEAR the configuration data, install a jumper. |
J3 | Serial EPROM | 2-pin header | To CLEAR the configuration data, install a jumper. |
J4 | Onboard BIOS Enable | 2-pin header | No jumper = Enabled (Default is Enabled) |
J5 | SCSI Activity LED | 2-pin header | Connector for enclosure LED to indicate data transfers. Connection is optional. |
J6 | Serial Port | 3-pin header | Connector is for diagnostic purposes. |
J7 | External SCSI connector | 68-pin connector | External very-high density SCSI bus connector. |
J8 | BBU daughter card connector | 40-pin connector | Connector for optional backup battery unit (BBU) located on a daughter card. |
J9 | SCSI bus TERMPWR Enable | 2-pin header | Install jumper to enable onboard termination power. Default is installed. |
J10 | SCSI bus Termination Enable | 3-pin header | Jumper pins 1-2 to enable software control of SCSI termination through drive detection. Jumper pins 2-3 to disable onboard SCSI termination. Having no jumper installed enables onboard SCSI termination. |
PERC 4/DC Jumpers and Connectors
Figure 3-2. PERC 4/DC Controller Layout
Connector | Description | Type | Default Setting |
---|---|---|---|
J1 | I2C Header | 4-pin header | Reserved. |
J2 | SCSI Activity | 4-pin header | Connector for LED on enclosure to indicate data transfers. Optional. |
J3 | Write Pending Indicator | 2-pin header | Connector for enclosure LED to indicate when data in the cache has yet to be written to the device. Optional. |
J4 | SCSI Termination Enable Channel 1 | 3-pin header | Jumper pins 1-2 to enable software control of SCSI termination via drive detection. Jumper pins 2-3 to disable onboard SCSI termination. No Jumper installed enables onboard SCSI termination. (See J17 and J18). |
J5 | SCSI Termination Enable Channel 0 | 3-pin header | |
J6 | DIMM socket | DIMM socket | Socket that hold the memory module |
J7 | Internal SCSI Channel 0 connector | 68-pin connector | Internal high-density SCSI bus connector. Connection is optional. |
J8 | Internal SCSI Channel 1 connector | 68-pin connector | |
J9 | External SCSI Channel 0 connector | 68-pin connector | External very-high density SCSI bus connector. Connection is optional. |
J10 | Battery connector | 3-pin header | Connector for an optional battery pack. |
J11 | NVRAM clear | 2-pin header | To CLEAR the configuration data, install a jumper. |
J12 | NMI jumper | 2-pin header | Reserved for factory. |
J13 | 32-bit SPCI Enable | 3-pin header | Reserved for factory. |
J14 | Mode Select jumper | 2-pin header | |
J15 | Serial Port | 3-pin header | Connector is for diagnostic purposes. |
J16 | Onboard BIOS Enable | 2-pin header | No jumper = Enabled (Default setting) |
J17 | TERMPWR Enable Channel 0 | 2-pin header | Jumper installed enables TERMPWR from the PCI bus. Default setting. No jumper installed enables TERMPWR from the SCSI bus. (See J4 and J5) |
J18 | TERMPWR Enable Channel 1 | 2-pin header | |
J19 | External SCSI Channel 1 connector | 68-pin connector | External very-high density SCSI bus connector. Connection is optional. |
J23 | Serial EEPROM | 2-pin header | To CLEAR the configuration data, install a jumper. |
Step 4 Install the PERC 4 Controller
Select a 3.3V PCI slot and align the controller PCI bus connector to the slot. Press down gently but firmly to make sure that the controller is properly seated in the slot, as shown in Figure 3-3. Screw the bracket to the system chassis.
Figure 3-3. Inserting the PERC 4 Controller into a PCI Slot
Step 5 Connect SCSI Cables and SCSI Devices
Connect the SCSI cables to the SCSI connectors and SCSI devices.
Connect SCSI Devices
Perform the following steps to connect SCSI devices.
- Disable termination on any SCSI device that does not sit at the end of the SCSI bus.
- Configure all SCSI devices to supply TermPWR.
- Set proper target IDs (TIDs) for all SCSI devices.
The host controller has a SCSI ID of 7.
- Connect the cable to the devices.
The maximum cable length for Fast SCSI (10 MB/s) devices or single ended (SE) is 3 meters. For Ultra SCSI devices, it is 1.5 meters. The cable length can be up to 12 meters for LVD devices.
Cable Suggestions
System throughput problems can occur if SCSI cable are not the correct. You should:
- Use cables up to 12 meters for Ultra3, Ultra160, and Ultra320 devices.
- For single-ended SCSI devices, use the shortest SCSI cables (no more than 3 meters for Fast SCSI, no more than 1.5 meters for an 8-drive Ultra SCSI system and no more than 3 meters for a 6-drive Ultra SCSI system).
- Use active termination.
- Avoid clustering the cable nodes.
- Note that cable stub length should be no more than 0.1 meter (4 inches).
- Route SCSI cables carefully.
- Use high impedance cables.
- Do not mix cable types (choose either flat or rounded and shielded or non-shielded).
- Note that ribbon cables have fairly good cross-talk rejection characteristics.
Step 6 Set Target IDs
Set target identifiers (TIDs) on the SCSI devices. Each device in a channel must have a unique TID. Non-disk devices should have unique SCSI IDs regardless of the channel where they are connected. See the documentation for each SCSI device to set the TIDs. The PERC 4 controller automatically occupies TID 7 which is the highest priority. The arbitration priority for a SCSI device depends on its TID. Table 3-3 lists the target IDs.
Priority | Highest Lowest | |||||||||||
TID | 7 | 6 | 5 | ... | 2 | 1 | 0 | 15 | 14 | ... | 9 | 8 |
Step 7 Set SCSI Termination
The SCSI bus is an electrical transmission line and must be terminated properly to minimize reflections and losses. Termination should be set at each end of the SCSI cable(s).
For a disk array, set SCSI bus termination so that removing or adding a SCSI device does not disturb termination. An easy way to do this is to connect the controller to one end of the SCSI cable and to connect an external terminator module at the other end of the cable. The connectors between the two ends can connect SCSI devices. Disable termination on the SCSI devices. See the manual for each SCSI device to disable termination.
Set the termination so that SCSI termination and TermPWR are intact when any hard drive is removed from a SCSI channel, as shown in Figure 3-4.
Figure 3-4. Terminating Internal SCSI Disk Array
Step 8 Start the System
Replace the system cover and reconnect the AC power cords. Turn power on to the host system. Set up the power supplies so that the SCSI devices are powered up at the same time as or before the host system. If the system is powered up before a SCSI device, the device might not be recognized.
During boot, the PERC 4 BIOS message appears:
PowerEdge Expandable RAID Controller BIOS Version x.xx date
Copyright (c) Dell Computer Corporation
Firmware Initializing... [ Scanning SCSI Device ...(etc.)... ]
The firmware takes several seconds to initialize. During this time the adapter scans the SCSI channel. When ready, the following appears:
HA –0 (Bus 1 Dev 6) Type: PERC 4/xx Standard FW x.xx SDRAM=xxxMB
0 Logical Drives found on the Host Adapter
0 Logical Drive(s) handled by BIOS
Press <Ctrl><M> to run PERC 4 BIOS Configuration Utility
Or press <Ctrl><H> to run WebBIOS
The PERC 4 BIOS Configuration Utility prompt times out after several seconds.
The PERC 4 host controller number, firmware version, and cache SDRAM size display in the second portion of the BIOS message. The numbering of the controllers follows the PCI slot scanning order used by the host motherboard.
Light-emitting Diode (LED) Description
When you start the system, the boot block and firmware perform a number of steps that load the operating system and allow the computer to function properly. The boot block contains the operating system loader and other basic information needed during startup.
As the system boots, the LEDs indicate the status of the boot block and firmware initialization and whether the system performed the steps correctly. If there is an error during startup, you can use the LED display to identify it.
Table 3-4 displays the LEDs and execution states for the boot block. Table 3-5 displays the LEDs and execution states during firmware initialization. The LEDs display in hexadecimal format so that you can determine the number and the corresponding execution state from the LEDs that display.
LED | Execution State |
---|---|
0x01 | Setup 8-bit Bus for access to Flash and 8 Bit devices successful |
0x03 | Serial port initialization successful |
0x04 | Spd (cache memory) read successful |
0x05 | SDRAM refresh initialization sequence successful |
0x07 | Start ECC initialization and memory scrub |
0x08 | End ECC initialization and memory scrub |
0x10 | SCRAM is present and properly configured. About to program ATU. |
0x11 | CRC check on the firmware image successful. Continue to load firmware. |
0x12 | Initialization of SCSI chips successful. |
0x13 | BIOS protocols ports initialized. About to load firmware. |
0x17 | Firmware is either corrupt or BIOS disabled. Firmware was not loaded. |
0x19 | Error ATU ID programmed. |
0x55 | System Halt: Battery Backup Failure |
LED | Execution State |
---|---|
0x1 | Begin Hardware Initialization |
0x3 | Begin Initialize ATU |
0x7 | Begin Initialize Debug Console |
0xF | Set if Serial Loopback Test is successful |
Step 9 Run the PERC 4 BIOS Configuration Utility, WebBIOS Utility, or Dell Manager
Press <Ctrl><M> when prompted during the boot process to run the BIOS Configuration Utility or <Ctrl><H> to run the WebBIOS Configuration Utility. You can also run Dell Manager in Novell NetWare and Red Hat Linux to perform the same functions, such as configuring arrays and logical drives.
See PERC 4 BIOS Configuration Utility for additional information about running the PERC 4 BIOS Configuration Utility. WebBIOS is an HTML-based configuration utility. See WebBIOS Configuration Utility, for additional information about running the WebBIOS Configuration Utility and Dell Manager, for additional information about running Dell Manager.
Step 10 Install an Operating System
Install one of the following operating systems: Microsoft® Windows NT®, Windows® 2000, Windows XP, Windows Server 2003, Novell® NetWare®, and Red Hat Linux.
Step 11 Install the Operating System Driver
Operating system drivers are provided on the Dell OpenManage Server Assistant CD that accompanies your PERC controller. See the PERC 4 RAID Controller Operating System Driver Installation Guide for additional information about installing the drivers for the operating systems.
[RM note: This e-mail has been re-edited to update it.]
Perc Scsi & Raid Devices Driver Download For Windows 10 Download
Date: Thu, 17 Apr 2003 11:45:29 -0700
To: ilug (ilug@linux.ie)
Subject: Re: [ILUG] Which RedHat for Dell Perc
From: Rick Moen (rick@linuxmafia.com)
Quoting Ken Guest (kguest@stockbyte.com):
> Anybody using Dell PERC RAID controllers with Red Hat? (specifically a
> PERC 3/QC)
>
> I'm wondering what exact version/release of Red Hat 8.0 to spring for,
> considering all the options at http://www.redhat.com/apps/commerce/ ...
The problem with the term 'Dell PERC' is that it misleads one into thinking it refers to a single thing. In fact, Dell uses the term 'PERC', as they do several other such names, as a house brand for relabeled hardware from elsewhere. There are PERC PCI cards as well as motherboard-integrated chipsets.
PERC implementations divide into those using relabelled LSI Logic (formerly AMI) Megaraid chipsets requiring Linux's megaraid or megaraid_2002 driver, ones using relabelled LSI Logic (formerly Symbios, formerly NCR) MPT Fusion chipsets using Linux's mptbase/mptscsih drivers, and ones using relabelled Adaptec chipsets using Linux's aacraid driver. Here's a field guide:
LSI Logic / AMI chipsets (megaraid or megaraid_2002 driver):
- CERC (Cost Effective RAID Controller) ATA100/4CH — ATA100quad-channel PCI card (not branded as 'PERC', but same chipset)
- PERC card (original) — not known to me, but I'm guessing it's in this category, and was almost certainly just a relabelled AMI MegaRAID PCI card of some description.
- PERC II — dual-channel PCI card, Ultra SCSI. This was a plain AMI MegaRAID 428 card with a different sticker.
- PERC2/SC — single-channel PCI card, Ultra2 SCSI (rebranded AMI MegaRAID 466 card)
- PERC2/DC — dual-channel PCI card, Ultra2 SCSI (rebranded AMI MegaRAID 467 card)
- PERC3/SC — single-channel PCI card, U160 SCSI
- PERC3/DCL — dual-channel PCI card, U160 SCSI w/no battery-backed cache
- PERC3/DC — dual-channel PCI card, U160 SCSI w/ battery-backed cache
- PERC3/DCP — same as PERC3/DC, but bundled w/Dell Precision workstations
- PERC3/QC — quad-channel PCI card, U160 SCSI w/ battery-backed cache (rebranded LSI or AMI MegaRAID 471 card)
- PERC4/SC — single-channel PCI card U320 w/ battery-backed cache
- PERC4/Di — dual-channel U320 SCSI w/ battery-backed cache, found in PowerEdge 1750, 2600, 2750
LSI Logic MPT Fusion chipsets (mptbase/mptscsih drivers):
- PERC4/iM &mdash single-channel, U320 SCSI, serves two mirrored RAID0 or 1 drives, found in Dell PowerEdge 1655MC blade systems
Adaptec chipsets (aacraid driver):
- PERC2 — quad-channel PCI RAID card, Ultra2 SCSI
- PERC2/Si — single channel, Ultra2 SCSI, found in Dell PowerEdge 2400
- PERC3/Si — single channel, U160 SCSI, found in Dell PowerEdge 2450
- PERC3/Di — dual channels, U160 SCSI, found in Dell PowerEdige models 1650, 2650, 4400, 4600
- PERC 320/DC &mdash dual-channel PCI RAID card, U320 SCSI
Note that PERC2 and PERC2/Si use a completely different chipset (and thus driver) from the PERC2/SC, PERC2/DC and PERC2. Similarly, PERC3/Si and PERC3/Di use a completely different chipset (and thus driver) from the PERC3/SC, PERC3/DC, PERC3/DCL, PERC3/DCP, and PERC3/QC. Similarly, PERC4/iM uses a completely different chipset (and thus drivers) from the PERC4/SC and PERC4/Di.
Perc Scsi & Raid Devices Driver Download For Windows 10 64-bit
The megaraid_2002 driver is probably a RedHat-ism, not found in standard kernels. On Red Hat, it's required for the PERC4/SC and PERC4/Di chipsets.
Perc SCSI & RAID Devices Driver Download For Windows 10
See further information on this page: http://linux.dell.com/raid.shtml