IBM P/N: 46C8103 Version 1.0
First Edition (July 2008)
© Copyright International Business Machines Corporation 2008.
All rights reserved.
®
US Government Users Restricted Rights – Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.
LSI, the LSI logo design, and MyStorage are trademarks or registered trademarks
of LSI Corporation. All other brand and product names may be trademarks of their
respective companies.
Connect the cables between the controller and
the supported SAS devices or SATA II devices.
Refer to the device documentation to view
connector locations.
Note
:
Refer to the
ServeRAID-MR10is SAS/SATA
Controller User’s Guide
for information about the
cables and the connectors.
Step 7
Turn on the Power to the Computer
Replace the computer cover, and reconnect the
power cords. Turn on the power to the computer.
During boot, a MegaRAID BIOS message similar
to the following is displayed:
LSI MEGARAID BIOS VERSION xxxx [date]
Copyright(c) 2007, LSI Corporation
HA-1 (Bus x Dev y) MegaRAID 8708E
PCI-Express RAID Controller
Standard FW xxxx DRAM=xxx MB(SDRAM)
The firmware takes several seconds to initialize.
During this time the controller scans the bus(es).
Step 8
Run the WebBIOS Configuration Utility
Run the WebBIOS Configuration Utility to
configure the physical arrays and the logical
drives. When the message
Press
<Ctrl><H> for
WebBIOS
displays on the screen, immediately
press CTRL+H to run the utility.
Note
:
Refer to the
ServeRAID-MR Software User’s
Guide
on the
ServeRAID-MR Support
CD for
detailed steps on configuring the physical arrays
and the logical drives.
Step 9
Install the Operating System Driver
The controller can operate under various
operating systems. To operate under these
operating systems, you must install software
drivers.
The
ServeRAID-MR Support
CD includes drivers
for the supported operating systems. You can
view the supported operating systems and
download the latest drivers for the controller at
http://www.ibm.com/systems/support/
.
Refer to the
ServeRAID-MR Device Driver
Installation User’s Guide
on the CD for details on
installing the driver. Be sure to use the latest
Service Packs provided by the operating system
manufacturer and review the
readme
file that
accompanies the driver.
S U P P O R T E D R A I D L E V E L S
The ServeRAID-MR10is SAS/SATA Controller supports disk
arrays using the following RAID levels:
•
RAID 0 (Data striping):
Data is striped across all disks
in the array, enabling fast data throughput. There is no
data redundancy. All data is lost if any disk fails.
•
RAID 1 (Disk mirroring):
Data is written simultaneously
to two disks, providing complete data redundancy if one
disk fails. The maximum array capacity is equal to the
available size of the smaller of the two hard drives.
•
RAID 5 (Disk striping with distributed parity):
Data is
striped across all disks in the array. Part of the capacity
of each disk stores parity information that reconstructs
data if a disk fails. Provides good data throughput for
applications with high read request rates.
•
RAID 6
(Disk striping with distributed parity across
two disks):
Data is striped across all disks in the array
and two parity disks are used to provide protection
against the failure of up to two physical disks. In each row
of data blocks, two sets of parity data are stored.
•
RAID 10 (RAID 1 and RAID 0 in spanned arrays):
Uses
mirrored pairs of disks to provide complete data
redundancy. Provides high data throughput rates.
•
RAID 50 (RAID 5 and RAID 0 in spanned arrays):
Uses
both parity and disk striping across multiple disks to
provide complete data redundancy. Provides high data
throughput rates.
•
RAID 60 (RAID 6 and RAID 0 in spanned arrays):
RAID
60 uses both distributed parity across two parity disks and
disk striping across multiple disks to provide complete
data redundancy. RAID 60 provides high fault tolerance.
T E C H N I C A L S U P P O R T
Refer to the
Warranty and Support Information
document for
information about the technical support available for this
product.
Attention:
The battery in the iBBU must charge for at least
six hours under normal operating conditions. To
protect your data, the firmware changes the Write
Policy to
write-through
until the battery unit is
sufficiently charged. When the battery unit is
charged, the controller firmware changes the
Write Policy to
write-back
to take advantage of
the performance benefits of data caching.
