MegaRAID SAS User`s Guide
MegaRAID SAS User's Guide
Areas Covered
Before Reading This Manual
This section explains the notes for your safety and conventions used in this manual.
Chapter 1
Overview
This chapter provides an overview and configuration precautions for the disk array, and an
explanation of the array configuration flow.
Chapter 2
Array Configuration and Management [WebBIOS]
This chapter explains the WebBIOS setup procedures. WebBIOS is a basic utility to set up and
manage array controllers.
Chapter 3
Preparations
This chapter explains how to update the device drivers and how to apply a hotfix.
Chapter 4
Array Configuration and Management [ServerView RAID]
This chapter contains an overview of and product requirements for ServerView RAID Manager,
and describes how to install and use the program.
Chapter 5
Array Configuration and Management [GAM]
This chapter contains an overview of and product requirements for GAM, and describes how to
install and use the program.
Chapter 6
Replacing Hard Disk
This chapter explains maintenance related issues, such as hard disk replacement.
Appendix
This section explains ServerView RAID event log and GAM event log.
1
Before Reading This Manual
This manual is a guide for using the following array controllers:
• MegaRAID SAS 300-8E ROMB
• MegaRAID SAS 8300XLP
• MegaRAID SAS 8408E
• MegaRAID SAS 8344ELP
• RAID 5/6 SAS based on LSI MegaRAID
Checking the Contents
When you purchased any of the products listed below, check if the package contains all the items come
with. If any items are missing, contact an office listed in the "Contact Information" of "Start Guide".
• PG-140F / PG-140FL / PG-140F1L / PG-140G (MegaRAID SAS 8300XLP)
• PG-244C / PG-244C1 / PG-244CL (MegaRAID SAS 8344ELP)
• PG-248B / PG-248BC / PG-248C / PG-248C1 / PG-248CL (RAID 5/6 SAS based on LSI
MegaRAID)
` There is no appended item for the following products because they are installed on the baseboard of
the server.
• An onboard array controller (MegaRAID SAS 300-8E ROMB)
• An array controller installed by default (MegaRAID SAS 8408E)
• An array controller installed by default (RAID 5/6 SAS based on LSI MegaRAID without a model
name)
` Array Controller Document & Tool CD is supplied with the server.
„ PG-140F / PG-140FL / PG-140F1L / PG-140G (MegaRAID SAS
8300XLP)
• Array controller card (this product)
• Array Controller Document & Tools CD
• PCI Slot Adapter
` Some servers require a PCI Slot Adapter.
„ PG-244C (MegaRAID SAS 8344ELP)
• Array controller card (this product)
„ PG-244C1 / PG-244CL (MegaRAID SAS 8344ELP)
• Array controller card (this product)
• Battery backup unit (BBU)
• BBU cable
2
MegaRAID SAS User's Guide
„ PG-248B (RAID 5/6 SAS based on LSI MegaRAID)
• Array controller card (this product)
„ PG-248BC (RAID 5/6 SAS based on LSI MegaRAID)
• Array controller card (this product)
• Cable to connect hard disks
„ PG-248C / PG-248C1 / PG-248CL (RAID 5/6 SAS based on LSI
MegaRAID)
• Array controller card (this product)
• Battery backup unit (BBU)
• BBU cable
Remarks
„ Symbols
Symbols used in this manual have the following meanings:
These sections explain prohibited actions and points to note when using this software. Make
sure to read these sections.
These sections explain information needed to operate the hardware and software properly.
Make sure to read these sections.
→
This mark indicates reference pages or manuals.
„ Key descriptions / operations
Keys are represented throughout this manual in the following manner:
E.g.: [Ctrl] key, [Enter] key, [–] key, etc.
The following indicate the pressing of several keys at once:
E.g.: [Ctrl] + [F3] key, [Shift] + [↑] key, etc.
„ CD/DVD drive descriptions
In this manual, both CD-ROM and DVD-ROM drives are described as CD/DVD drives. Select a proper
drive depending on your environment.
„ Entering commands (keys)
Command entries are written in the following way:
• In the spaces indicated with the "↑" mark, press the [Space] key once.
• In the example above, the command entry is written in lower case, but upper case is also allowed.
3
• CD/DVD drive names are shown as [CD/DVD drive]. Enter your drive name according to your
environment.
[CD/DVD drive]:\setup.exe
„ Screen shots and figures
Screen shots and figures are used as visual aids throughout this manual. Windows, screens, and file
names may vary depending on the OS, software, or configuration of the server used. Figures in this
manual may not show cables that are actually connected for convenience of explanation.
„ Consecutive operations
Consecutive operations are described by connecting them with a dash (–).
Example: For the operation to click the [Start] button, point to [Programs], and click [Accessories]
↓
Click the [Start] button – [Programs] – [Accessories].
„ Abbreviations
The following expressions and abbreviations are used throughout this manual.
table: Abbreviation of product name
Product name
Expression and abbreviation
MegaRAID SAS 300-8E ROMB
MegaRAID SAS 8408E
MegaRAID SAS 8300XLP
MegaRAID SAS 8344ELP
RAID 5/6 SAS based on LSI MegaRAID
the array controller, this array controller
Microsoft® Windows Server® 2003, Standard Edition
Windows Server 2003
Microsoft® Windows Server® 2003, Enterprise Edition
Microsoft® Windows Server® 2003 R2, Standard Edition
Microsoft® Windows Server® 2003 R2, Enterprise Edition
Microsoft® Windows Server® 2003, Standard x64 Edition
®
®
Microsoft Windows Server 2003, Enterprise x64 Edition
Windows Server
2003 x64[*1]
Microsoft® Windows Server® 2003 R2, Standard x64 Edition
Microsoft® Windows Server® 2003 R2, Enterprise x64 Edition
Microsoft® Windows® 2000 Server
®
Windows 2000 Server
®
Microsoft Windows 2000 Advanced Server
4
Microsoft® Windows® 2000 Professional
Windows 2000 Professional
Microsoft® Windows® XP Professional
Windows XP
Windows
MegaRAID SAS User's Guide
table: Abbreviation of product name
Product name
Red Hat Enterprise Linux 5(for x86)
Expression and abbreviation
Red Hat Linux
Linux
RHEL5(x86)
Red Hat Enterprise Linux 5(for Intel64)
RHEL5(Intel64)
Red Hat Enterprise Linux AS(v.4 for x86)
RHEL-AS4(x86)
Red Hat Enterprise Linux ES(v.4 for x86)
RHEL-ES4(x86)
Red Hat Enterprise Linux AS(v.4 for EM64T)
RHEL-AS4(EM64T)
Red Hat Enterprise Linux ES(v.4 for EM64T)
RHEL-ES4(EM64T)
Red Hat Enterprise Linux AS(v.3 for x86)
RHEL-AS3(x86)
Red Hat Enterprise Linux ES(v.3 for x86)
RHEL-ES3(x86)
SUSE™ Linux® Enterprise Server 9
SUSE Linux
*1: Unless otherwise noted, Windows Server 2003 can also mean Windows Server 2003 x64.
„ Information for PRIMERGY
For the latest information on PRIMERGY, update modules, drivers and the software, refer to the Fujitsu
PRIMERGY website.
http://www.fujitsu.com/global/services/computing/server/ia/driver/
Regarding BIOS and FW, contact to Fujitsu Support Office.
Refer to the website (http://www.fujitsu.com/global/contact/computing/PRMRGY_index.html).
„ PRIMERGY Startup Disc
"PRIMERGY Startup Disc" referred in this manual is supplied with a PRIMERGY server. Depending
on your PRIMERGY type, "PRIMERGY Document & Tool CD" may be supplied instead . Then
"PRIMERGY Startup Disc" also means "PRIMERGY Document & Tool CD" in this manual.
„ RAID 1+0(10) description
In this manual, RAID 1+0(10) is referred to as RAID 10.
„ Trademarks
Microsoft, Windows, and Windows Server are trademarks or registered trademarks of Microsoft Corporation in the USA
and other countries.
Linux is a trademark or registered trademark of Linus Torvalds in the USA and other countries.
Red Hat and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the
USA and other countries.
SUSE is a trademark of Novell, Inc. in the United States and other countries.
LSI, Global Array Manager (GAM), and MegaRAID are trademarks or registered trademarks of LSI Corp.
All other hardware and software names used are trademarks or registered trademarks of their respective manufacturers.
Other product names are copyrights of their respective manufacturers.
All Rights Reserved, Copyright© FUJITSU LIMITED 2008
Screen shot(s) reprinted with permission from Microsoft Corporation.
5
6
MegaRAID SAS User's Guide
Contents
Chapter 1 Overview
1.1 Array Controller Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2 Overview of Disk Array Configuration . . . . . . . . . . . . . . . . . . . . 16
1.2.1 Array controller specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.2.2 What is Disk Array? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.2.3 RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.2.4 Disk Group and Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
1.2.5 Checking Hard Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
1.3 Disk Array Configuration Features . . . . . . . . . . . . . . . . . . . . . . . 26
1.3.1 Write Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
1.3.2 Logical Drive Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
1.3.3 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
1.3.4 Make Data Consistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
1.3.5 Capacity Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
1.3.6 Hard Disk Failure Prediction Function (PFA / S.M.A.R.T.) . . . . . . . . . . . . .35
1.3.7 HDD Check Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
1.3.8 Battery Backup Unit (BBU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
1.4 Notes before Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.4.1 Notes on Installation to Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
1.4.2 Notes on Hard Disk to Be Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
1.4.3 Cautions for OS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
1.5 Notes on Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
1.5.1 Notes for Using Array Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
1.5.2 Message during POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
1.5.3 When the Server Is Not Shut Down Properly . . . . . . . . . . . . . . . . . . . . . .41
1.5.4 Using ServerView RAID under the Windows 2000 Server Environment .42
1.5.5 Notes on WebBIOS Startup When Installing Multiple MegaRAID SAS
Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
1.5.6 Hard Disk Failure LED during Operation . . . . . . . . . . . . . . . . . . . . . . . . . .44
Chapter 2 Array Configuration and Management [WebBIOS]
2.1 Starting and Exiting WebBIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.1.1 Starting Up WebBIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
2.1.2 Exiting WebBIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
2.2 Checking Each Status [WebBIOS] . . . . . . . . . . . . . . . . . . . . . . . 51
2.2.1 Checking Hard Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
2.2.2 Checking Logical Drive Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
2.2.3 Checking Progress of Background Task . . . . . . . . . . . . . . . . . . . . . . . . . .58
2.2.4 Confirming Array Controller Information . . . . . . . . . . . . . . . . . . . . . . . . . .60
7
2.3 Creating/Deleting Disk Array Configuration . . . . . . . . . . . . . . . 63
2.3.1 Creating Disk Array Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.3.2 Deleting Disk Array Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
2.4 Setting/Releasing Spare Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
2.4.1 Setting Spare Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
2.4.2 Releasing Spare Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
2.5 Operations on Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.5.1 Initializing Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
2.5.2 Fast Initialization of Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
2.5.3 Make Data Consistent of Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
2.5.4 Expanding the Capacity of Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . 89
2.5.5 Deleting Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2.6 Rebuilding Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2.7 Reusing Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
2.7.1 Cautions When Reusing Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
2.7.2 Clearing Information from Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Chapter 3 Preparations
3.1 Updating Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.1 Creating Driver Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.1.2 Updating Driver (Windows Server 2003) . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.1.3 Updating Driver (Windows 2000 Server) . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.2 Applying Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Chapter 4 Array Configuration and Management
[ServerView RAID]
4.1 Overview of and Requirements for ServerView RAID . . . . . . . 108
4.1.1 ServerView RAID Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
4.1.2 Requirements for ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4.1.3 Access Privileges to ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4.1.4 Using ServerView RAID in Linux Environment . . . . . . . . . . . . . . . . . . . . 111
4.1.5 Operations via Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.1.6 When Using Both ServerView RAID and GAM . . . . . . . . . . . . . . . . . . . . 113
4.2 Installing ServerView RAID [Windows] . . . . . . . . . . . . . . . . . . 114
4.2.1 How to Install ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4.2.2 How to Uninstall ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.3 Installing HDD Check Scheduler [Windows] . . . . . . . . . . . . . . 117
4.3.1 Installation of HDD Check Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4.3.2 Modifying HDD Check Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.3.3 Uninstallation of HDD Check Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . 120
4.4 Installing Battery Recalibration Scheduler [Windows] . . . . . 121
4.4.1 Installation of Battery Recalibration Scheduler . . . . . . . . . . . . . . . . . . . . 121
8
MegaRAID SAS User's Guide
4.4.2 Changing Battery Recalibration Start Date and Time . . . . . . . . . . . . . . .122
4.4.3 Uninstallation of Battery Recalibration Scheduler . . . . . . . . . . . . . . . . . .124
4.5 Starting and Exiting ServerView RAID Manager . . . . . . . . . . . 125
4.5.1 Preparations and Precautions for using ServerView RAID Manager . . .125
4.5.2 Starting and Logging in ServerView RAID Manager . . . . . . . . . . . . . . . .126
4.5.3 Exiting ServerView RAID Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
4.6 ServerView RAID Manager Window Layout . . . . . . . . . . . . . . . 129
4.6.1 Startup Window Layout and Functions . . . . . . . . . . . . . . . . . . . . . . . . . .129
4.6.2 Menu Layout and Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
4.6.3 Layout of the Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
4.7 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
4.7.1 Changing Array Controller Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
4.7.2 Configuring Battery Backup Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
4.7.3 Setting Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
4.7.4 Setting ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
4.8 Operating RAID Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 149
4.8.1 Creating Disk Array Configuration (Create Logical Drive) . . . . . . . . . . . .149
4.8.2 Expanding Capacity of Logical Drive (Migrate Logical Drive) . . . . . . . . .153
4.8.3 Deleting Existing Logical Drive (Delete Last Logical Drive) . . . . . . . . . . .156
4.8.4 Setting and Releasing Spare Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
4.8.5 Changing the Write Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
4.8.6 Deleting Disk Array Configuration Information . . . . . . . . . . . . . . . . . . . . .160
4.8.7 Make Data Consistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
4.8.8 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
4.8.9 Recalibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
4.9 Checking Each Status [ServerView RAID Manager] . . . . . . . . 164
4.9.1 Checking the Server Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
4.9.2 Checking Array Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
4.9.3 Checking Hard Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
4.9.4 Checking Logical Drive Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
4.9.5 Checking Progress of Background Task . . . . . . . . . . . . . . . . . . . . . . . . .171
Chapter 5 Array Configuration and Management [GAM]
5.1 Overview of and Requirements for GAM . . . . . . . . . . . . . . . . . 176
5.1.1 GAM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
5.1.2 Requirements for GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
5.1.3 Access Privileges to GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
5.1.4 Using GAM in Linux Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
5.1.5 Using GAM in a Network Environment . . . . . . . . . . . . . . . . . . . . . . . . . .180
5.1.6 When Using Both ServerView RAID and GAM . . . . . . . . . . . . . . . . . . . .182
5.2 Installing GAM[Windows] . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5.2.1 How to Install GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
5.2.2 Uninstalling GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
5.3 Installing HDD Check Scheduler[Windows]. . . . . . . . . . . . . 188
9
5.3.1 Installation Procedure for HDD Check Scheduler . . . . . . . . . . . . . . . . . . 188
5.3.2 Modifying HDD Check Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
5.3.3 Uninstallation Procedure for HDD Check Scheduler . . . . . . . . . . . . . . . 191
5.4 Installing Battery Recalibration Scheduler [Windows] . . . . . 192
5.4.1 Installation Procedure for Battery Recalibration Scheduler . . . . . . . . . . 192
5.4.2 Modifying HDD Check Start Date and Time . . . . . . . . . . . . . . . . . . . . . . 193
5.4.3 Uninstallation Procedure for Battery Recalibration Scheduler . . . . . . . . 195
5.5 Starting and Exiting GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5.5.1 Starting GAM and Signing On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5.5.2 Exiting GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
5.6 GAM Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5.6.1 Startup Window Layout and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 198
5.6.2 Menu Layout and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5.6.3 Toolbar Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
5.6.4 Starting Controller View and the Window Layout . . . . . . . . . . . . . . . . . . 204
5.7 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
5.7.1 Server group and server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
5.7.2 Setting and Changing Controller Options . . . . . . . . . . . . . . . . . . . . . . . . 208
5.7.3 Configuring Battery Backup Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
5.8 Operating RAID Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 212
5.8.1 Starting RAID Assist Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
5.8.2 Creating New Disk Array Configuration (New Configuration) . . . . . . . . . 214
5.8.3 Adding Logical Drive to Existing Disk Array Configuration (Add Logical Drive)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
5.8.4 Expanding Capacity of Logical Drive (Expand Array) . . . . . . . . . . . . . . . 219
5.8.5 Deleting Existing Logical Drive (Edit Configuration) . . . . . . . . . . . . . . . . 222
5.8.6 Setting and Releasing Spare Disk (Edit Configuration) . . . . . . . . . . . . . 223
5.8.7 Changing the Write Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
5.8.8 Saving and Deleting Disk Array Configuration Information . . . . . . . . . . . 226
5.9 Viewing Information [GAM] . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
5.9.1 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
5.9.2 Viewing Array Controller Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
5.9.3 Viewing Hard Disk Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
5.9.4 Viewing Logical Drive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
5.9.5 Checking Progress of Background Tasks . . . . . . . . . . . . . . . . . . . . . . . . 236
5.10 Maintenance Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
5.10.1 Make Data Consistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
5.10.2 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
5.10.3 Recalibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Chapter 6 Replacing Hard Disk
6.1 How to Replace Hard Disk [ServerView RAID] . . . . . . . . . . . . 244
6.1.1 Checking Hard Disk to be Replaced [ServerView RAID] . . . . . . . . . . . . 244
10
MegaRAID SAS User's Guide
6.1.2 Replacing Failed Hard Disk [ServerView RAID] (With Hot Swap Support)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
6.1.3 Replacing Failed Hard Disk [ServerView RAID] (No Hot Swap Support)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
6.1.4 Preventive Replacement of Hard Disk [ServerView RAID] . . . . . . . . . . .249
6.2 How to Replace Hard Disk [GAM] . . . . . . . . . . . . . . . . . . . . . . . 260
6.2.1 Checking Hard Disk to Replace [GAM] . . . . . . . . . . . . . . . . . . . . . . . . . .260
6.2.2 Replacing Failed Hard Disk [GAM] . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
6.2.3 Preventive Replacement of hard disk [GAM] . . . . . . . . . . . . . . . . . . . . . .263
Appendix
A List of ServerView RAID Event Log . . . . . . . . . . . . . . . . . . . . . 270
B List of GAM Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
C Replacing Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
11
12
Chapter 1
Overview
This chapter provides an overview and
configuration precautions for the disk array, and
an explanation of the array configuration flow.
1.1
1.2
1.3
1.4
1.5
Array Controller Work Flow . . . . . . . . . . . . . . . . . . . . . . .
Overview of Disk Array Configuration . . . . . . . . . . . . . . . .
Disk Array Configuration Features . . . . . . . . . . . . . . . . . .
Notes before Operation . . . . . . . . . . . . . . . . . . . . . . . . . .
Notes on Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
16
26
39
41
13
Chapter 1 Overview
1.1 Array Controller Work Flow
The work flow when using a disk array controller is as follows.
„ For Windows
1. Designing the Disk Array
Set the operation pattern of the disk array
configuration. Design the RAID level and
the logical drive configuration.
㸢1.2 Overview of the Disk Array Configuration
㸢1.3 Disk Array Configuration Features
2. Installing the Hardware
Install the array controller card on the server
when using the card as an option.
Also, install the hard disk drive on the bay.
㸢䇭1.4䇭Notes before the Operation
㸢䇭"User's Guide" provided with the server
3. Configuring the Disk Array
Configure the disk array using WebBIOS before installing the OS.
㸢䇭Chapter 2 Array Configuration and Management [WebBIOS]
ServerStart will help
you set up Steps
4. Installing the OS
from
3
to
5.
㸢䇭1.4.3 Cautions for OS Installation
㸢䇭"User's Guide" provided with the server
㸢㩷㩷3.2 Applying the Hotfix
5. Installing the Management Tools
Install the following management tools.
䇭䇭䊶ServerView RAID [Note 1]
䇭䇭䊶Global Array Manager(GAM) [Note 1]
䇭䇭䊶HDD check scheduler [Note 2]
䊶Battery recalibration scheduler [Note 3]
(only when the battery backup unit is installed
㩷Chapter 4 Array Configuration and
Management [ServerView RAID]
Chapter 5 Array Configuration and
Management [GAM]
㸢 1.3.8 Battery Backup Unit (BBU)
[Note 1]: Either one tool can be installed. For details, see ReadmeEN.html on the "Array Controller Document & Tool CD".
[Note 2]: HDD check is set to start at noon every day by default. For details, see "1.3.7 HDD scheduler".
Change the time to start as necessary.
[Note 3]: Battery Recalibration is set to start at 11 on the first day every month by defarult. For details, see "‫ع‬Battery
‫ޓޓޓޓ‬recalibration scheduler" in "1.3.8 Battery Backup Unit (BBU)". Change the time to start as necessary.
6. Updating the Device Drivers
㸢㩷3.1 㩷㪬㫇㪻㪸㫋㫀㫅㪾㩷㫋㪿㪼㩷㪛㪼㫍㫀㪺㪼㩷㪛㫉㫀㫍㪼㫉㫊
Update the device drivers to the latest version
stored on the "Array Controller Document & Tool CD".
7. Preparing the Environment for the Management Tools
䊶Register the user account with the OS to use
the management tools. (This is not required if it
is set at the installation of the management tools.)
㩷Chapter 4 Array Configuration and
Management [ServerView RAID]
Chapter 5 Array Configuration and
Management [GAM]
䊶Set the start time for the HDD check scheduler.
䊶Set the start time for the Battery recalibration scheduler.
14
MegaRAID SAS User's Guide
„ For Linux
1. Designing the Disk Array
Set the operation pattern of the disk array
configuration. Design the RAID level and
the logical drive configuration.
㸢1.2 Overview of the Disk Array Configuration
㸢1.3 Disk Array Configuration Features
2. Installing the Hardware
Install the array controller card on the server
when using the card as an option.
Also, install the hard disk drive on the bay.
㸢㩷1.4䇭Notes before the Operation
㸢㩷"User's Guide" provided with the server
3. Configuring the Disk Array
Configure the disk array using WebBIOS before 㸢䇭Chapter 2 Array Configuration and
installing the OS.
Management [WebBIOS]
4. Installing the OS
㸢䇭 "Installation Guide"
5. Installing the Management Tools
Install the following management tools.
䇭䇭䊶ServerView RAID䇭*
䇭䇭䊶Global Array Manager(GAM)䇭*
䇭䇭䊶HDD check scheduler
䊶Battery recalibration scheduler
㸢䇭 "Installation Guide"
(only when the battery backup unit is installed
* Either one tool can be installed. For details, see ReadmeEN.html on the "Array Controller Document & Tool CD".
6. Preparing the Environment for the Management Tools
䊶Register the user account with the OS to use
㸢䇭 "Installation Guide"
the management tools. (This is not required if it
is set at the installation of the management tools.)
䊶Set the start time for the HDD check scheduler.
䊶Set the start time for the Battery recalibration scheduler.
For using Linux, see the PRIMERGY page on the Fujitsu website (http://primergy.fujitsu.com) and refer
to information about Linux.
15
Chapter 1 Overview
1.2 Overview of Disk Array
Configuration
This section contains an overview (RAID levels, disk groups, and logical drives) and
a functional description of the disk array.
1.2.1 Array controller specifications
The specifications of the array controller described in this manual are as follows:
table: Specifications
Item
Product name
Product model
name
Contents
MegaRAID SAS
8408E
No model name
MegaRAID SAS
300-8E ROMB
No model name
MegaRAID
SAS 8300XLP
PG-140F
PG-140FL
PG-140F1L
PG-140G
MegaRAID SAS
8344ELP
PG-244C
PG-244C1
PG-244CL
RAID 5/6 SAS
based on LSI
MegaRAID
PG-248B
PG-248BC
PG-248C
PG-248C1
PG-248CL
One without a
model name
[Note 1]
Whether
installed in the
server
Installed by
default
[Note 2]
Onboard [Note 3]
Interface
The number of
SAS ports
PCI-X Slot
installable card
PCI-Express Slot
installable card
card [Note 1]
SAS (Serial Attached SCSI)
8 ports (for internal device
connection)
0
ports [Note 4]
4 ports (for
optional and
internal device
connection)[Note 5]
RAID level to
be supported
Cache
memory and
capacity
PCI-Express
Slot installable
RAID 0, 1, 5, 6,
and 10
RAID 0, 1, 5, and 10
Available
(256MB)
Available [Note 6]
Available
(128MB)
8 ports (for
internal device
connection)
Available
(256MB)
PG-248B / PG248BC:
256MB
PG-248C / PG248C1 / PG248CL:
512MB[Note 1]
Cache
memory
battery
16
Available
Not available/
Available [Note 6]
PG-140F/
PG-140FL/
PG-140F1L:
Not available
PG-140G:
Available
Available
PG-248B / PG248BC: Not
available
PG-248C / PG248C1 / PG248CL:
Available[Note 1]
MegaRAID SAS User's Guide
table: Specifications
Item
Supported OS
[Note 7]
Contents
OS supported by the server
•
•
•
•
•
Windows Server 2003 x64
Windows Server 2003
Windows 2000 Server
Red Hat Linux
SUSE Linux
OS supported
by the server
There are two types of tools: (1) WebBIOS which configures disk arrays before installing the
OS and (2) ServerView RAID or GAM which monitors or manages array controllers on the OS.
Make sure to install the management tools before using the array controllers.
You must install either ServerView RAID or GAM, but not both. For information about which
to use, see ReadmeEN.html on the Array Controller Document & Tool CD.
Management
Tools
• WebBIOS
BIOS utility in the array controller.
J"Chapter 2 Array Configuration and Management [WebBIOS]" (pg.45)
• ServerView RAID
J"Chapter 4 Array Configuration and Management [ServerView RAID]" (pg.107)
• Global Array Manager (GAM)
J"Chapter 5 Array Configuration and Management [GAM]" (pg.175)
[Note 1]: If there is no model name, an array controller is installed in your server by default. In this case, refer to
the specification of the server.
[Note 2]: It is pre-installed on the server.
[Note 3]: It is directly installed on the baseboard of the server.
[Note 4]: Since this array controller itself does not have any ports, use a port from the SAS controller installed on
the server.
[Note 5]: Connection ports for internal devices are not supported.
[Note 6]: See the specification of the server.
[Note 7]: See the supported OS of the server that the array controller is operating.
` When you start the server with this product installed in, you may hear the buzzer sound a few times.
This is not a warning and you can go on with your operation.
1.2.2 What is Disk Array?
A disk array or RAID (Redundant Array of Independent Disks) is a system that uses an array controller
and multiple hard disk unit to achieve better performance and higher reliability than when using a single
hard disk unit. An array controller controls the access to each hard disk. There are different types of
control methods that are defined as a RAID level.
By using a redundant RAID level, system operation can be continued without data loss in the event that
one or even two, for some RAID levels, of the hard disk unit fail.
17
Chapter 1 Overview
1.2.3 RAID Levels
There are several types of RAID level, with different characteristics. Depending on the RAID level, the
number of installable hard disks, available capacity and applicability of redundancy are different. The
RAID levels supported by this array controller vary depending on the product mode. For details, see
"1.2.1 Array controller specifications" (Jpg.16).
table: Characteristics of each RAID Level
Number of
hard disks [Note1]
RAID Level
Available total capacity
Redundancy
RAID 0
1 to 32
Capacity of one hard disk × the number of hard disks
RAID 1
2
Capacity of one hard disk
Yes
RAID 5
3 to 32
Capacity of one hard disk × (the number of hard disks -1)
Yes
RAID 6
3 to 32
Capacity of one hard disk × (the number of hard disks -2)
Yes
RAID 10
4 to 32
(Even number)
Capacity of one hard disk × (the number of hard disks / 2)
Yes
No
[Note 1]: The maximum number of hard disks indicates the specifications for an array controller. The actual
configurable number of hard disks depends on the specifications and configuration of the server.
` You should backup the data as frequently as possible just in case even with redundancy.
` When using RAID 6, you can continue the operation even when two hard disks fail. Leaving them in
the failed status, however, may increase the possibility of losing data if more hard disks fail.
` In a RAID configuration with four or more hard disks, use RAID 5 if capacity is important, RAID 10 if
performance is important, or RAID 6 if redundancy is important.
„ Reliability and performance comparison between RAID levels
When choosing RAID level, compare reliability and performance between RAID levels to determine the
right level. The recommended RAID level is RAID 1. RAID 1 is superior to other RAID levels in data
recoverability. RAID 1 can only be configured with two hard disks and the available capacity will be
equal to the capacity of a single hard disk. If the logical drive capacity is insufficient, you can increase
the capacity by configuring multiple RAID 1 logical drives.
table: Characteristics of each RAID Level
Data Reliability
RAID Level
Redundancy
[Note 1]
18
Recoverability
[Note 2]
Performance
Write
Read
Capacity
Remarks
RAID 0
×
×
○
○
◎
This is not
recommended,
because no data
redundancy is
provided.
RAID 1
○
△
○
○
△
Highly recommended
for its excellent data
recoverability.
RAID 5
○
×
△
○
○
The write performance
is poorer than other
RAID levels.
MegaRAID SAS User's Guide
table: Characteristics of each RAID Level
Data Reliability
RAID Level
Redundancy
[Note 1]
RAID 6
◎
RAID 10
○
Recoverability
[Note 2]
×
×
Performance
Write
×
○
Read
○
○
Capacity
Remarks
△
The write performance
is poorer than RAID 5.
Data is safe with
failure of up to two
hard disks.
△
Available capacity is
smaller than RAID 5,
yet the write
performance is usually
higher than RAID 5.
[Note 1]: Data redundancy when hard disks fail or get disconnected.
[Note 2]: Data recoverability when two or more hard disks are disconnected due to a failure other than a hard
disk failure. For RAID 1, in which data is not striped, other systems may read one of the constituent
hard disks in the RAID 1 configuration. However, even for RAID 1, data cannot always be recovered.
„ RAID 0 (Striping)
Striping refers to the function of dividing data and writing them on multiple hard disks. For example,
when writing nine blocks of data (D1 to D9), if three hard disks are involved, data is written evenly on
each hard disk as shown in the figure below. Performance is improved by writing data on three different
hard disks rather than writing all nine data blocks on a single hard disk.
Data
D-1
D-1
D-2
D-3
D-4
D-5
D-6
D-7
D-8
D-9
D-4
D-7
Hard Disk 1
Array Controller
D-2
D-5
D-8
Hard Disk 2
D-3
D-6
D-9
Hard Disk 3
` RAID 0 has no redundancy and all data may be lost in the case of even one hard disk failure. System
operation will also be interrupted.
„ RAID 1 (mirroring)
Mirroring is a function in which identical data is written in two hard disks in duplicate. When operating
in RAID 1 disk array configuration, the system always writes the same data in two hard disks, using the
redundancy feature. Operation continues even if one of the hard disks should fail and lose redundancy
(Critical). RAID 1 always consists of two hard disks and the actual available capacity is equal to the
capacity of one hard disk.
19
Chapter 1 Overview
Data
D-1
D-2
D-3
Hard Disk 1
D-1
Array Controller
D-2
D-1
D-3
D-2
D-3
Hard Disk 1
` With RAID 1, operation continues even if one of the hard disks fail (Critical). However, data may be lost
if both hard disks fail. If the status of a logical drive becomes "Critical", replace the failed hard disk as
immediately as possible and recover the redundancy.
See "Chapter 6 Replacing Hard Disk" (Jpg.243) for how to replace a hard disk.
„ RAID 5 (striping + parity)
In addition to striping, which divides the data and distributes them over multiple hard disks, RAID 5
generates parity data to provide redundancy. Parity data is data obtained through calculations on the
data.
For example, when three hard disks compose a RAID 5, data is evenly written to two of the hard disks.
The parity data that is obtained through calculations of the data written to those two hard disks is then
written to the remaining one hard disk. The hard disk where parity data is written to is not fixed, but it is
used per block in turn by three hard disks.
In a RAID 5 configuration, the size of a single disk drive is used for parity data in order to provide
redundancy by parity data.
D-1
Data
D-4
Parity
D-5
D-6
Hard Disk 1
D-1
D-2
Array Controller
D-2
Parity
D-3
D-4
D-3
D-4
Hard Disk 2
D-5
D-6
Parity
D-1
D-2
D-3
D-5
D-6
Hard Disk 3
` With RAID 5, operation continues even if one of the hard disks fail and lose redundancy (Critical).
However, data may be lost if two or more hard disks fail. If the status of a logical drive becomes
"Critical", replace the failed hard disk as immediately as possible and recover the redundancy.
See "Chapter 6 Replacing Hard Disk" (Jpg.243) for information on how to replace a hard disk.
20
MegaRAID SAS User's Guide
„ RAID 10 (mirroring + striping)
In addition to striping, which divides the data and distributes them over multiple hard disks, RAID 10
provides redundancy by mirroring while using four or more (even numbers only) hard disks. For
example, when writing six blocks of data (D-1 to D-6), if four hard disks are involved, each section of
data and redundant data are written evenly on each hard disk as shown in the figure below. Performance
is improved by distributing data over two disk drives and redundancy is provided by the redundant data.
Actually available disk size is half of the total hard disk size.
` When RAID is configured using the same number of hard disks, the available disk size is reduced
compared to RAID 5, yet performance while writing the data is increased.
D-1
D-3
D-5
Hard Disk 1
Data
D-1
D-1
D-2
D-3
D-4
D-3
D-5
Hard Disk 1
Array Controller
D-2
D-5
D-6
D-4
D-6
Hard Disk 1
D-2
D-4
D-6
Hard Disk 1
` With RAID 10, operation continues even if one of the hard disks fail and lose redundancy (Critical).
However, data may be lost if two or more hard disks fail. If the status of a logical drive becomes
"Critical", replace the failed hard disk as immediately as possible and recover the redundancy.
See "Chapter 6 Replacing Hard Disk" (Jpg.243) for information on how to replace a hard disk.
` The capacity of a RAID 10 logical drive cannot be expanded.
J"1.3.5 Capacity Expansion" (pg.33)
` In a disk group of RAID 10, multiple logical drives cannot be defined. Only a single logical drive can be
created in a single RAID 10 disk group with the maximum capacity of the group.
21
Chapter 1 Overview
„ RAID 6 (striping + dual parity)
RAID 6, in addition to the striping + parity of RAID 5, improved its redundancy by doubling parity data.
Take a case with RAID 6 configured with five hard disks for instance. The data is written into 3 hard
disks, and the remaining two have the parity data [P] which was calculated based on the data written to
the three drives, and the parity data [Q] which was calculated in a different way from the [P]. Parity data
is not written into specific disks but into all disks by the block in turn.
In RAID 6, for the better redundancy, two hard disks store the parity data.
D-1
D-9
D-5
Hard Disk 1
Parity-P
Data
D-2
D-6
D-7,D-8
D-9
Hard Disk 2
D-1
D-2
D-3
Parity-P
D-4
D-5
D-6
D-7
D-8
D-9
Array Controller
Parity-Q
D-4,D-5 D-7,D-8
D-9
D-3
D-6
Hard Disk 3
Parity-P
Parity-Q
D-1,D-2 D-4,D-5 D-7
D-3
D-6
Hard Disk 4
Parity-Q
D-1,D-2
D-3
D-4
D-8
Hard Disk 5
` RAID 6 keeps redundancy (partially critical) even when a hard disk fails. Furthermore, even when
another hard disk fails resulting in redundancy free status, the operation will continue. The chance,
however, of losing data increases since the first hard disk failure. It gets higher at the second hard disk
failure. The third and the subsequent hard disk unit failures result in the data loss. Exchange a failed
hard disk unit soon after its failure while still partially critical, and restore its redundancy.
When two hard disks fail( logical drives are in the critical status), their data is almost lost. Exchange the
failed drives at once to restore its redundancy.
For how to change hard disks, see "Chapter 6 Replacing Hard Disk" (Jpg.243).
22
MegaRAID SAS User's Guide
1.2.4 Disk Group and Logical Drive
The management unit that collectively groups the number of hard disks required for forming RAID is
referred to as a disk group and the logical units configured within a disk group are called logical drives.
Logical
Drive 0
Logical
Drive 1
Hard Disk 1
Logical
Drive 2
Logical
Drive 3
Logical
Drive 4
Hard Disk 2
Hard Disk 4
Hard Disk 3
Hard Disk 5
Disk group A
Disk group B
Logical
Drive 5
z Disk group
A disk group is a group of physical hard disks that form a disk array. It is not recognized by the OS.
` A disk group can consist of 1 to 32 hard disks.
` Hard disks in a single disk group should be of the same model (with the same capacity and the rotation
speed).
` Up to eight disk groups can be configured within a single array controller.
z Logical drive
A logical drive is a logical hard disk space within a disk group. It is recognized as a single hard disk by
the OS.
` Up to eight logical drives can be configured within a single array controller.
` In a disk group of RAID 10, multiple logical drives cannot be defined. Only a single logical drive can be
created in a single RAID 10 disk group with the maximum capacity of the group.
` Only one type of RAID level can be configured for the logical drives within a disk group.
23
Chapter 1 Overview
„ Example of disk group and logical drive configuration
Assume that two disk groups A and B are created using five hard disks and six logical drives are created
on those groups. In this case, the OS will assume that six hard disks are connected.
The OS assumes that six hard disk drives are connected.
Logical
Drive 0
Logical
Drive 1
Logical
Drive 2
Hard Disk 1
Logical
Drive 3
Logical
Drive 4
Hard Disk 2
Hard Disk 4
Hard Disk 3
Hard Disk 5
Disk group A
Disk group B
Logical
Drive 5
Configuring conditions
`
`
`
`
Disk group A (drives 1 to 3) must consist of hard disks of the same type and capacity.
Disk group B (drives 4 and 5) must consist of hard disks of the same type and capacity.
One type of RAID level can be configured for logical drives 0 to 2 of disk group A.
One type of RAID level can be configured for logical drives 3 to 5 of disk group B.
„ Status during hard disk failure
In the example above, if hard disk 1 fails, the status of all the logical drives from 0 to 2 in the same disk
group becomes "Critical" (without redundancy). If another drive (e.g. drive 2 or 3) also fails, the status
of the logical drives from 0 to 2 becomes "Offline" (unavailable). However, the logical drives from 3 to
5 of disk group B will remain online (normal operation) because a hard disk problem is not present.
1.2.5 Checking Hard Disk Status
Hard disks and logical drives in the disk group should be constantly monitored, and be replaced if there
is a failure or indication of a failure.
` The status differs depending on each management tool. For information about the status, see the
appropriate description in your management tool's documents.
• Web BIOS
J"2.2.2 Checking Logical Drive Status" (pg.54),
J"2.2.1 Checking Hard Disk Status" (pg.51)
• ServerView RAID
J"4.6.3 Layout of the Tree View" (pg.134)
24
MegaRAID SAS User's Guide
• GAM
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
` When ServerView RAID or GAM operates properly, information is logged as an event if an error occurs
in the logical drive or hard disk.
J"Appendix A List of ServerView RAID Event Log" (pg.270)
J"Appendix B List of GAM Event Log" (pg.304)
„ Logical drive status
A logical drive can be in the following states:
table: Logical drive status
Status
Description
Online
Operating normally.
Critical
Operating without redundancy. A hard disk for RAID 1, RAID 5, or RAID 10 logical
drives, or two hard disks for RAID 6 logical drive have been failed. Replace the failed
hard disks as soon as possible and rebuild to restore the online status. See "Chapter 6
Replacing Hard Disk" (Jpg.243) for how to replace and rebuild hard disks.
Partially critical
Operating with redundancy. But a hard disk of RAID 6 logical drives has been failed.
Replace the failed hard disk as soon as possible and rebuild to restore the “Online" status.
See "Chapter 6 Replacing Hard Disk" (Jpg.243) for how to replace and rebuild hard
disks.
Offline
Not operating. Two or more hard disks in a disk group have been failed. The data in the
logical drive has also been lost.
„ Hard disk status
A hard disk may be in any of the following states.
table: Hard disk status
Status
Description
Online
Operating normally. It is included in the disk array.
Unused
Operating normally. It is unused because it is not included in the disk array.
Failed
Unable to read/write data. The hard disk has been failed. Replace and rebuild it. See
"Chapter 6 Replacing Hard Disk" (Jpg.243) for how to replace hard disks.
Offline
Data read/write is disabled by the array controller. You need to rebuild the hard disk for
the further usage.
Hotspare
The hard disk is configured as a spare disk.
Rebuild
The hard disk is currently being rebuilt.
Failure Predicted
Currently operating normally. But it may fail in the near future (failure predicted status).
See "Chapter 6 Replacing Hard Disk" (Jpg.243) and replace the hard disk as soon as
possible.
` If there is a hard disk with failure status, there may be a hard disk failure and the hard disks may be
operating without redundancy. The hard disk must be replaced as soon as possible. See "Chapter 6
Replacing Hard Disk" (Jpg.243) for how to replace a hard disk.
25
Chapter 1 Overview
1.3 Disk Array Configuration
Features
This section explains the features in disk array configuration.
1.3.1 Write Policy
The Write Policy is the setting of the mode for data writing to the logical drive on the array controller
and can be configured for each logical drive.
There are three Write Policy modes: Write Through, Write Back, and Bad BBU.
Changing your Write policy from Write Through to Write Back (or bad BBU) improves many software
applications in writing performance. If efficiency is essential in your operation, review your Write
Policy. However there are things you should keep in mind when using Write Back (or bad BBU). Before
setting up, be sure to read the following contents and know the gist of Write Policy operation.
` When installing the OS on the logical drive connected to this array controller, set the Write Policy of the
logical drive to Write Through before the OS installation. If you want to set the Write Policy to Write
Back (or Bad BBU), change it after the OS installation is completed.
„ Summary of Write Policy operation
z Write Through
When writing data from the OS and application to hard disk (disk array) is issued, the completion of
writing is only recognized after the writing to hard disk is finished.
Array controller receives
data, and reports on the
writing completion to the
host after the data writing in
the disk is completed.
㽳 Writing of
data
㽲 Write command
Array Controller
Data
㽵 Completion report
26
Hard disk
Data
㽴 Completion report
Logical drive
MegaRAID SAS User's Guide
z Write Back/Bad BBU
When writing data from the OS and application to hard disk (disk array) is issued, writing is completed
after finishing the writing data to cache memory on the array controller. Writing into hard disk is
actually carried out by the array controller after the operation of the OS or application, not at the same
time.
Array controller receives data and
reports on the writing completion
to the host simultaneously. The
multiple data will be written in the
disk later.
Hard disk
㽲 Write command
Array Controller
Data
㽳 Completion report
㽴 Writing of
data
Data
Logical drive
Writing to hard disk is performed mechanically, but writing to cache memory is performed electrically.
Consequently, drastic improvement in efficiency can be expected by the OS or application finalizing the
control with cache memory, not by directly accessing to hard disk. Write Back (or Bad BBU) mode is an
efficient means of bringing a full capacity of high speed cache memory when writing.
„ Notes on Write Back (or Bad BBU)
In setting up Write Back (Bad BBU) mode, time lug exists between the time when the OS and software
application acknowledge the completion of writing and the time of actual writing into hard disk.
Consequently, if power problem to server occurs before writing into a hard disk, data to be written which
is left on cache memory may be destroyed, and there may be a gap in data between the one that OS or
software application acknowledges and the one that is actually written on hard disk.
z When using Write Back mode
When you use Write Back, make sure to install battery backup unit (BBU) for cache memory to
minimize the risk described above. Make sure to either utilize array controller which supports battery
backup unit, or install battery backup unit option. See "1.3.8 Battery Backup Unit (BBU)" (Jpg.36) for
the details of battery backup unit.
` If you use Write Back with battery backup unit for cache memory, the data on the cache memory is
protected by the battery at the time of unexpected blackout, and the writing of data from the cache
memory to the hard disk is carried on when the system restarts (when the next server is on), reducing
the risk of the data loss.
` If the battery is not fully charged, or when a recalibration is in progress, the data may not be kept on
cache memory. To avoid such data loss, the logical drive set on Write Back is automatically changed to
Write Through mode. It returns to Write Back automatically when the battery is fully charged or the
recalibration is completed.
` If the server's power-off state continues for a long time, the logical drive with Write Back setting will
operate as Write Through compulsorily at the next startup due to the discharged battery. The logical
drive whose setting is compulsorily changed will automatically return to the Write Back after the battery
is charged enough.
` It is recommended that you connect UPS to the server, as well as the battery backup unit to avoid
accidents caused by blackout.
27
Chapter 1 Overview
z When using Bad BBU mode
When you set up Bad BBU, Write Back mode is maintained whether a battery is in or if battery is
charged. Therefore, when no battery units are installed or battery backup unit is not fully charged, Write
Policy is not automatically changed to Write Through mode, and data on cache memory is not saved.
Risks to lose data in case of unexpected accidents are higher compared to Write Back.
` Do not use Bad BBU if the power supply to the server is not secured by UPS or other devices.
Otherwise, there is a risk of data loss in case of unexpected blackout.
` If the battery is fully charged, the data on the cache memory is protected by the battery at the time of
unexpected blackout, and the writing of data from the cache memory to the hard disk is carried on
when the system restarts (when the next server is on).
1.3.2 Logical Drive Initialization
After creating a logical drive, it must be initialized in order to use it properly. There are three methods to
initialize a logical drive as described below.
„ Foreground initialization
With this method, "0 (zero)" is written in all areas of a logical drive to maintain consistency between the
hard disks and to initialize them. This requires a certain amount of time because write operations are
performed for the entire space of the hard disks.
` Foreground initialization is performed from WebBIOS.
J"2.5.1 Initializing Logical Drives" (pg.86)
` When the server restarts during foreground initialization, the initialization is stopped and the logical
drive is not initialized. Perform the initialization again. If foreground initialization is not performed,
background initialization is performed automatically.
z Time estimated for foreground initialization
The following table shows the estimated initialization time per 10GB of logical drive space.
table: Estimated Time for Foreground Initialization per 10GB
RAID Level
Number of hard
disks
Time per 10GB
RAID 1
2
approx. 3 min.
RAID 5
3
approx. 2 min.
6
approx. 2 min.
3
approx. 2 min.
6
approx. 2 min.
4
approx. 3 min.
RAID 6
RAID 10
28
MegaRAID SAS User's Guide
For example, the capacity of a RAID 5 logical drive consisting of three 73GB hard disks is 146GB (=
73GB × (3 - 1)), which requires approximately 30 minutes (= approx. 2 min./10GB × 146GB) to
initialize. However, the time may differ from the value in the above table depending on the configuration
and the hard disk type.
„ Background initialization
With this method, initialization of the logical drive is performed in parallel with normal I/O access
operations from the host. You can use the logical drive immediately after creating the logical drive
without waiting for completion of the initialization process. This can save the time of a foreground
initialization, but the following points must be noted.
• During background initialization, access to the hard disks may occur regardless of normal I/O access.
Therefore, I/O processing performance may decrease during background initialization.
• Do not perform background initialization on hard disks that may contain partition information. If you
need to perform background initialization on hard disks that contain data, see "2.7 Reusing Hard
Disk" (Jpg.95) and erase the data from the hard disks before configuring the array.
` Background initialization starts automatically when the array controller checks redundant logical drives
(RAID 1, RAID 5, RAID 10, and RAID 6) and detects a drive that is not completely initialized. The array
controller checks for logical drives that are not completely initialized every 5 minutes.
` If the server is reset or turned off before completing the background initialization, the background
initialization is interrupted. Background initialization is resumed from where it was stopped the next
time.
` During background initialization, the access lamps of the hard disks that make up the target logical
drive remain lit.
` The execution time of this function can be reduced by changing the BGI Rate and giving priority to this
function over server I/O, but I/O performance will be reduced accordingly. Normally, use the default
settings.
` If foreground initialization is not performed, background initialization is performed automatically.
` Even when RAID 6 logical drives are partially critical, background initialization can be done. When you
replace the failed hard disks and the rebuild starts, background initialization is canceled and the rebuild
starts. In that case, background initialization starts after the rebuild.
z Time estimated for background initialization
The following table shows the estimated execution time per 10GB of logical drive space when there is
no server I/O.
table: Estimated time for background initialization per 10GB
RAID Level
Number of hard
disks
Execution time per 10GB
RAID 1
2
approx. 20 min.
RAID 5
3
approx. 15 min.
6
approx. 24 min.
3
approx. 15 min.
6
approx. 24 min.
4
approx. 24 min.
RAID 6
RAID 10
29
Chapter 1 Overview
For example, the capacity of a RAID 5 logical drive consisting of three 73GB hard disks is 146GB (=
73GB × (3 - 1)), the execution time is approximately 220 minutes (= approx. 15 min./10GB × 146GB)
to initialize. However, the time may differ from the value in the above table depending on the
configuration and the hard disk type.
` The above execution time is an estimate for when the BGI Rate is the default value.
„ Fast initialization
With this method, "0 (zero)" is written to only the first 50KB of the logical drive and the remaining area
of the logical drive is initialized with the subsequent background initialization which starts
automatically.
If partition information remains in the first section of the logical drive, performing fast initialization
rather than background initialization deletes the partition information. Therefore, background
initialization can be performed without performing initialization on the hard disk in advance.
Fast initialization can be performed with WebBIOS. See "2.5.1 Initializing Logical Drives" (Jpg.86) for
the detailed procedure.
` This fast initialization completes in few seconds, but the subsequent background initialization may take
some time.
For notes about background initialization, see "„ Background initialization" (Jpg.29).
1.3.3 Rebuild
Even when a hard disk fails in logical drives with redundancy such as RAID 1, RAID 5, or RAID 10, or
two hard disks fail in RAID 6 which has double redundancy, the logical drives continue to operate in
"Critical" status. If, however, another hard disk in the same logical drive fails, the logical drive becomes
"Offline" (unavailable). Rebuild is an operation to recover a logical drive from "Critical" status to
"Normal" (Online) status.
The rebuild process is performed in the background in parallel with normal I/O access. During rebuild, if
a logical drive becomes "Critical", the redundancy of the logical drive remains lost. Once the rebuild is
completed, it is restored to "Online".
There are two methods for rebuilding as described below.
„ Hot spare rebuild
Hot spare rebuild is rebuild that is performed automatically in the event of a hard disk failure, by having
a pre-installed spare hard disk. The pre-installed spare hard disk is called a spare disk. When a hard disk
failure occurs, rebuild is immediately performed on the spare disk, to improve the reliability of the disk
array.
30
MegaRAID SAS User's Guide
` You need to have a spare hard disk set as a spare disk in advance. Setting up the spare disk can be
performed from the WebBIOS or management tool.
` A spare disk is used as a substitute for a failed hard disk. Therefore, use a hard disk with the same
capacity and speed as the hard disks connected in the disk group.
` When a failed hard disk is replaced after starting a hot spare rebuild, the newly installed hard disk is
automatically configured as the spare disk.
When a hot spare rebuild is performed, the bay where the disk group and the spare disk are installed is
changed.
` A hot spare rebuild is not performed for the hard disk with a failure prediction sign. Once preventive
replacement is done, the rebuild is started.
J"1.3.6 Hard Disk Failure Prediction Function (PFA / S.M.A.R.T.)" (pg.35)
` When configuring spare disks in an environment with multiple disk groups using different types of hard
disks, for each disk group, configure at least one spare disk with the same capacity and speed as the
hard disk used in each disk group.
Spare Disk
73GB
73GB
Hard Disk 1
Hard Disk A
147GB
Hard Disk 1
73GB
Hard Disk 2
147GB
Hard Disk B
Disk group A
147GB
Hard Disk 2
Disk group B
„ Manual rebuild
Manual rebuild is rebuild that is performed by replacing a failed hard disk with a new hard disk. When
no spare disk is available, the disk array needs to be repaired through manual rebuild.
„ Estimated time for rebuild
The following table shows the estimated execution time per 10GB of logical drive space when there is
no server I/O.
table: Estimated Time for manual rebuild per 10GB
RAID Level
Number of hard
disks
Execution time per 10GB
RAID 1
2
approx. 4 min.
RAID 5
3
approx. 3 min.
6
approx. 3 min.
3
approx. 3 min.
6
approx. 3 min.
4
approx. 2 min.
RAID 6
RAID 10
For example, the capacity of a RAID 5 logical drive consisting of three 73GB hard disks is 146GB (=
73GB × (3 - 1)), which requires approximately 44 minutes (= approx. 3 min./10GB × 146GB) to rebuild.
However, the time may differ from the value in the above table depending on the configuration and the
hard disk type.
31
Chapter 1 Overview
` The above execution time is an estimate when the Rebuild Rate is the default value.
` The rebuild process is performed in parallel with normal I/O access, therefore I/O performance for the
logical drives can be decreased during rebuild. With this array controller and the default settings, the
I/O performance decreases about 30% at maximum.
` The rebuild time can be reduced by setting the [Rebuild Rate] to "100" which will give itself priority over
I/O. However, I/O performance can be lower than that of the default configuration. Normally, use the
default settings. [Rebuild Rate] can be set with each management tool.
• WebBIOS
J"2.2.4 Confirming Array Controller Information" (pg.60)
• ServerView RAID
J"4.7.1 Changing Array Controller Setting" (pg.139)
• GAM
J"5.7.2 Setting and Changing Controller Options" (pg.208)
` If the system restarts or shuts down during rebuild, the rebuild is resumed from where it was stopped
the next time.
` Replacing two failed hard disks from RAID 6 logical drives at the same time will keep both in rebuilding
states. The actual rebuild, however, is done each at a time. While a hard disk is rebuilding, another
rebuild progress is 0%.
1.3.4 Make Data Consistent
Make Data Consistent is a function to maintain consistency between data on redundant logical drives
(RAID 1, RAID 5, RAID 6, or RAID 10) and mirrored data or parity data.
` If the server is not shut down properly, the data consistency among hard disks may be lost. In such
cases, use this function to make the data consistent.
Data sent to the server is never changed by performing Make Data Consistent because correction of
mirrored data and parity data is performed as necessary.
` The Make Data Consistent function is also used to recover from hard disk media errors (different from
inconsistency) because it reads the data on the hard disk.
` If rebuild is performed for RAID 10, Make Data Consistent is automatically performed after the rebuild
is completed.
` The I/O performance will decrease during Make Data Consistent. The execution time of Make Data
Consistent can be reduced by changing the CC Rate (MDC Rate for ServerView RAID) and giving
priority to this function over system I/O, but then I/O performance is reduced accordingly. Normally, use
the default settings.
` Even when RAID 6 logical drives are partially critical, Make Data Consistent can be done. When you
replace the failed hard disks and rebuild starts, Make Data Consistent is canceled and rebuild starts.
32
MegaRAID SAS User's Guide
z Time estimated for Make Data Consistent
The following table shows the estimated execution time per 10GB of logical drive space when there is
no server I/O.
table: Estimated time for Make Data Consistent per 10GB
RAID Level
Number of hard
disks
Execution time per 10GB
RAID 1
2
approx. 20 min.
RAID 5
3
approx. 15 min.
6
approx. 24 min.
3
approx. 15 min.
6
approx. 24 min.
4
approx. 24 min.
RAID 6
RAID 10
For example, the capacity of a RAID 5 logical drive consisting of three 73GB hard disks is 146GB (=
73GB × (3 - 1)), which requires approximately 220 minutes (= approx. 15 min./10GB × 146GB) for
Make Data Consistent. However, the time may differ from the value in the above table depending on the
configuration and the hard disk type.
` The execution time above is an estimate when the CC Rate is the default value.
1.3.5 Capacity Expansion
Using capacity expansion, you can expand the capacity of the logical drive or change the RAID level by
adding a new hard disk to the logical drive while leaving the existing data. The following figure shows
an example of adding two hard disks to disk group A, which consists of three hard disks.
Reconfiguring the RAID of five hard disks will keep the data of the logical drive, and the capacity
amount of the new drives will be added to that of the logical drive.
Logical Drive 0
(after expanding the capacity)
Logical Drive 0
Hard Disk 1
Hard Disk 2
Hard Disk 3
Disk group
Hard Disk 1
Hard Disk 2
Hard Disk 4
Hard Disk 5
Additional Disk
Hard Disk 3
Hard Disk 4
Hard Disk 5
Disk group
33
Chapter 1 Overview
After performing capacity expansion, the RAID level may change as follow.
table: RAID level after capacity expansion
RAID level
before capacity
expansion
RAID level after capacity expansion
Migration only
Migration with addition
RAID 0
N/A
RAID 0, RAID 1, RAID 5, or RAID 6
RAID 1
RAID 0
RAID 0, RAID 5, or RAID 6
RAID 5
RAID 0
RAID 0, RAID 5, or RAID 6
RAID 6
RAID 0, RAID 5
RAID 0, RAID 5, or RAID 6
RAID 10
Unable to expand the capacity
Unable to expand the capacity
` Only the capacity of logical drives is expanded by capacity expansion. The capacity of OS partitions is
not expanded.
` The execution time of capacity expansion can be reduced by changing the Reconstruction Rate (More
Rate for GAM, and Migration Rate for ServerView RAID) and giving priority to this function over system
I/O, but I/O performance is reduced accordingly. Normally, use the default settings.
` If logical drives after capacity expansion have RAID level with redundancy (RAID 1, RAID 5, or RAID
6), background initialization will be performed.
` If the capacity is expanded without adding a hard disk, the RAID level of the logical drive is converted
to RAID 0 with only few exceptions, and the logical drive loses its redundancy. We recommend that
you add a hard disk when expanding the capacity.
` During capacity expansion, logical drives with their Write Policy set to Write Back or Bad BBU will
temporarily be set to Write Through.
` Capacity expansion is only available when the logical drive is used in a Windows environment and the
partition style for the logical drive has been initialized in MBR format. Do not perform capacity
expansion if the partition style is in GUID Partition Table (GPT) format under Windows, or if using
Linux. The GPT partition style may be available for Windows Server 2003 SP1 or later, or Windows
Server 2003 x64.
` The capacity of RAID 10 logical drive cannot be expanded.
` If there are multiple logical drives within a disk group, capacity expansion cannot be performed for the
logical drives in that disk group.
` Capacity expansion cannot be interrupted during execution. Also, if the server restarts during
execution, the data within the logical drive is lost. Make sure to back up data before executing capacity
expansion.
` The I/O load when performing capacity expansion is very high and operation will slow down. It is
recommended that you perform the capacity expansion during non-business hours, or low-business
hours.
In addition, since the logical drive loses its redundancy during capacity expansion, all the data on the
logical drive will be lost if a hard disk failure occurs.
34
MegaRAID SAS User's Guide
z Time estimated for capacity expansion
The following table shows the estimated execution time per 10GB of logical drive space when there is
no server I/O.
table: Estimated time of capacity expansion per 10GB
RAID level
before capacity
expansion
Number of hard disks
RAID level after
capacity
expansion
Execution time per 10GB
When adding 1
drive
When adding 3
drives
RAID 0
1
RAID 0
approx. 6 min.
approx. 3 min.
RAID 0
1
RAID 1
approx. 7 min.
N/A
RAID 0
1
RAID 5
N/A
approx. 4 min.
RAID 0
1
RAID 6
N/A
approx. 4 min.
RAID 1
2
RAID 0
approx. 3 min.
approx. 2 min.
RAID 1
2
RAID 5
approx. 4 min.
approx. 2 min.
RAID 1
2
RAID 6
approx. 6 min.
approx. 4 min.
RAID 5
3
RAID 0
approx. 4 min.
approx. 3 min.
RAID 5
3
RAID 5
approx. 3 min.
approx. 3 min.
RAID 5
3
RAID 6
approx. 5 min.
approx. 5 min.
RAID 6
3
RAID 0
approx. 5 min.
approx. 3 min.
RAID 6
3
RAID 5
approx. 4 min.
approx. 4 min.
RAID 6
3
RAID 6
approx. 4 min.
approx. 4 min.
For example, when expanding capacity of a RAID 5 logical drive consisting of three 73GB hard disks is
146GB (= 73GB × (3 - 1)), the execution time is approximately 44 minutes (= approx. 3 min./10GB ×
146GB) by adding one hard disk. However, the time may differ from the value in the above table
depending on the configuration, the hard disk type and the number of added hard disks. Use the table
only as a guide.
` The above execution time is an estimate when the Reconstruction Rate is the default value.
1.3.6 Hard Disk Failure Prediction Function (PFA /
S.M.A.R.T.)
The PFA/S.M.A.R.T. function is a failure prediction function for the hard disks that determines the risk
of a failure in advance and issues a warning when the risk is high.
Although a hard disk will still operate normally even when a risk of a failure is predicted, that hard disk
may fail in the near future and should be replaced as soon as possible. See "6.1.4 Preventive
Replacement of Hard Disk [ServerView RAID]" (Jpg.249) or "6.2.3 Preventive Replacement of hard
disk [GAM]" (Jpg.263) for the replacement procedure. The hard disk for which failure is predicted can
be identified by management tools or event logs.
35
Chapter 1 Overview
1.3.7 HDD Check Scheduler
HDD Check Scheduler is a program to detect or recover media errors on hard disks. HDD Check
Scheduler performs media checks to all logical drive areas including drive areas that are not accessed in
everyday operation by performing Make Data Consistent periodically.
z Overview
Media errors may occur accidentally on a hard disk, in particular if the drive is exposed to a severe shock
during operation. In that case, since this kind of event is not a hard disk failure, the media errors will not
be detected until reading the data in the erroneous sector. If the drive is configured in a RAID level with
redundancy, this array controller's usual functions will recover the data using the data on other hard
disks. However, if a medium error occurs in a file that is rarely accessed, the error will remain
unrecovered, and if an additional hard disk should also fail, the data will be lost.
Use HDD Check Scheduler properly to perform media checks periodically.
` Make sure to install HDD Check Scheduler. If you install the OS with ServerStart, HDD Check
Scheduler will be automatically installed with a RAID management tool.
` Manual installation of the OS requires you to install HDD Check Scheduler after RAID management
tool installation. For how to install it, see the following.
• When using ServerView RAID
J"4.2 Installing ServerView RAID [Windows]" (pg.114)
J"4.3 Installing HDD Check Scheduler [Windows]" (pg.117)
• When using GAM
J"5.2 Installing GAM [Windows]" (pg.183)
J"5.3 Installing HDD Check Scheduler [Windows]" (pg.188)
` HDD Check Scheduler periodically executes Make Data Consistent using a standard OS taskscheduling function. When you install HDD Check Scheduler, Make Data Consistent is set to start at
12:00 every day by default. For how to change the settings, see the following.
• When using ServerView RAID
J"4.3.2 Modifying HDD Check Start Time" (pg.118)
• When using GAM
J"5.3.2 Modifying HDD Check Start Time" (pg.189)
` The HDD checks using HDD Check Scheduler can only be performed on logical drives with
redundancy (RAID 1, RAID 5, RAID 6, or RAID 10). The checks cannot be performed on RAID 0
logical drives or spare disks.
1.3.8 Battery Backup Unit (BBU)
For a model with a battery backup unit, incomplete write data can be maintained in the cache memory of
the array controller even if shutdown occurs due to unintentional damage, power failure, or power
interruption. When Write Back or Bad BBU is used, if the power is accidentally not supplied while
leaving incomplete write data to the hard disk in the cache memory, the battery backup unit maintains
the data by supplying the power to the cache memory. In such cases, data can be maintained for the
following time period since the time of power-off when the battery is fully charged.
36
MegaRAID SAS User's Guide
• Up to 72 hours for MegaRAID SAS 300-8E ROMB, MegaRAID SAS 8408E, MegaRAID SAS
8344ELP, RAID 5/6 SAS based on LSI MegaRAID
• Up to 37 hours for MegaRAID SAS 8300XLP.
` Battery is a lifetime component that degrades over time, so you must replace it periodically. For details,
see "Appendix C Replacing Battery" (Jpg.327).
` The length of the data holding time is an approximate value. The length of the data holding time varies
depending on the temperature of the operation environment, the age and cache memory size of the
server, and other factors.
` The battery backup unit maintains data in the cache memory of this product and does not ensure the
data in the system memory of the server.
` The battery backup unit must be used solely for unintentional power failure, so do not use it for any
operations (such as power interruption during access) other than its intended purpose. In normal
operation, power must not be supplied to the cache memory from the battery.
` The battery is automatically charged while server is on.
` When the server is off for long periods of time, the remaining battery capacity may be reduced by
discharging naturally even if data does not exist in the cache memory. In such cases, battery
recalibration may automatically be performed when the server is turned on.
` The reconditioning of the battery requires 12 hours with the power on. The reconditioning of the battery
is performed from the beginning if the server is accidentally turned off or on during the battery
recalibration.
` When you replace array controller cards, battery backup units, or the battery, the reconditioning of the
battery may automatically be started.
` While the remaining battery capacity is reduced and recalibration is performed, a logical drive that is
set to Write Back is automatically changed to Write Through for safety. When the battery recalibration
is completed, Write policy is automatically restored to Write Back.
` For a logical drive that is set to Bad BBU, write cache is always enabled even during battery
recalibration.
„ Battery Recalibration Scheduler
The battery backup unit on MegaRAID SAS 300-8E ROMB, MegaRAID SAS 8408E, MegaRAID
8344ELP, or RAID 5/6 SAS based on LSI MegaRAID has a battery capacity management function.
Periodical recalibration is necessary for MegaRAID SAS 300-8E ROMB, MegaRAID SAS 8408E,
MegaRAID 8344ELP, or RAID 5/6 SAS based on LSI MegaRAID, since long-time operation causes a
margin of error in the battery capacity managed by the battery backup unit.
This array controller can perform periodical recalibration by installing Battery Recalibration Scheduler.
` When using MegaRAID SAS 300-8E ROMB, MegaRAID SAS 8408E, MegaRAID 8344ELP, or RAID 5/
6 SAS based on LSI MegaRAID with a battery backup unit, make sure to install Battery Recalibration
Scheduler. If you install the OS with ServerStart, Battery Recalibration Scheduler will be automatically
installed with a RAID management tool.
` Manual installation of the OS requires you to install Battery Recalibration Scheduler after RAID
management tool. For how to install it, see the following.
• When using ServerView RAID
J"4.2 Installing ServerView RAID [Windows]" (pg.114)
J"4.4 Installing Battery Recalibration Scheduler [Windows]" (pg.121)
37
Chapter 1 Overview
• When using GAM
J"5.2 Installing GAM [Windows]" (pg.183)
J"5.4 Installing Battery Recalibration Scheduler [Windows]" (pg.192)
` Battery Recalibration Scheduler periodically executes recalibration using a standard OS taskscheduling function. When you install Battery Recalibration Scheduler, recalibration is set to start at
11:00 on the 1st day of each month by default. For how to change the settings, see the following.
• When using ServerView RAID
J"4.4.2 Changing Battery Recalibration Start Date and Time" (pg.122)
• When using GAM
J"5.4.2 Modifying HDD Check Start Date and Time" (pg.193)
` Battery Recalibration Scheduler is not necessary for MegaRAID SAS 8300XLP. Periodical
recalibration will not be performed even if Battery Recalibration Scheduler is installed.
38
MegaRAID SAS User's Guide
1.4 Notes before Operation
Check the following before starting the operation.
1.4.1 Notes on Installation to Server
This section explains notes when installing the array controller of a PCI card type on the server.
• When you install this product on the server, turn off the server, all peripheral
devices, and any other connected devices. Also unplug all power cables from
the outlet. If you install or remove this product when the power is turned on, it
may cause device failure, fire, or electric shock.
• This product reaches very high temperatures while the server is in operation.
To remove this product, first turn off the server, wait until it is cool, and then
remove the product from the server.
z Notes
• When you install the array controller in a PCI slot, see "User’s Guide" located on "PRIMERGY
Startup Disc bundled with the server, and properly follow the procedure described in the document to
install them on the server.
Installable PCI slot location is specified by the target server. Make sure the location of the installable
PCI slot is correct before installing.
• Usage may be limited depending on the target server.
1.4.2 Notes on Hard Disk to Be Used
The following notes apply to the hard disks to be used. Please check in advance.
z Usable hard disk
All the hard disks in a single disk group use the same model (with the same capacity and speed) as a
rule. Check that the installed hard disks have the same capacity and speed. Also, be sure to check that the
hard disks are installable on the server.
z Reusing hard disk
Hard disks containing data may have partition information or array configuration information. Using
such hard disk units without taking the proper measures may cause unexpected problems. When using a
previously used hard disk, erase the data by performing low level format on the system that was using
the hard disk, before connecting the drive to this array controller. The same caution applies when using
hard disks used by this array controller on another system. See "2.7.2 Clearing Information from Hard
Disk" (Jpg.95) and completely erase the information on the hard disk before using it on another system.
39
Chapter 1 Overview
z Removing hard disk
When the server is turned on, do not remove the hard disks except for the following situations:
• When replacing a failed hard disk
• When replacing a hard disk as a preventive measure
z Notes on connecting device
Do not connect any devices other than Fujitsu-supported hard disks to this array controller.
1.4.3 Cautions for OS Installation
When you install an OS on the hard disk under the array controller, there are the following cautions.
Please check in advance.
„ About Write Policy
When you install an OS, set the write policy of the logical drive to Write Through.
When you use Write Back or Bad BBU, change the write policy from the management tool or WebBIOS
after the OS installation and hotfix application are completed.
For details about applying the hotfix, see "3.2 Applying Hotfix" (Jpg.106).
40
MegaRAID SAS User's Guide
1.5 Notes on Operation
This section contains notes concerning system operation when using this array
controller.
1.5.1 Notes for Using Array Controller
When using Windows in a disk array configuration, the following event may be entered in the Event
Viewer's system log:
Source
:
Type
:
Event ID
:
Description:
msas2k3
Warning
129
The description for Event ID (129) in Source (msas2k3) cannot
be found.
(The rest is omitted.)
This log entry means that an internal reset has been issued in the device driver, but since the event has
been restored by an OS retry, you can continue with the operation. However, if this event occurs
repeatedly (about twice in every 10 minutes), there is a possibility of hardware failure. Contact an office
listed in the "Contact Information" of "Start Guide" and check the array controller and hard disks.
1.5.2 Message during POST
If the following message appears, the hard disk may have a failure.
Foreign configuration(s) found on adapter
Some configured disks have been removed from your system, or are no longer
accessible. Please check your cables and also ensure all disks are
present.
In that case, see "Chapter 6 Replacing Hard Disk" (Jpg.243) to check the hard disk condition, replace
the hard disk, and perform rebuild.
1.5.3 When the Server Is Not Shut Down Properly
If the server is turned off without performing a proper shutdown due to power interruption, the
consistency of the logical drive may be lost. In such cases, perform Make Data Consistent.
Please refer to the following for details.
J"1.3.4 Make Data Consistent" (pg.32)
J"2.5.3 Make Data Consistent of Logical Drive" (pg.88)
J"4.8.7 Make Data Consistent" (pg.161) (When using ServerView RAID)
J"5.10.1 Make Data Consistent" (pg.239) (When using GAM)
41
Chapter 1 Overview
1.5.4 Using ServerView RAID under the Windows 2000
Server Environment
Under the conditions below, at the restart of Windows 2000 Server, events reporting abnormalities of
hard disks or logical drives may be recorded.
• When restarting Windows 2000 Server after installing Windows 2000 Server and ServerView RAID
using ServerStart.
• When restarting Windows 2000 Server after applying the hotfix KB904374 of Windows 2000 Server
with ServerView RAID installed in it.
The details of the recorded events are as follows.
Note that the [Array Controller Name], Logical drive [%s], Disk [%s], and [Server Name] in the
messages are different according to the types of array controller that are installed, the number of created
logical drives, the number of installed hard disks, and the setting values of the server name.
z For events via ServerView
Source
42
Fujitsu ServerView Services
ID
3
Message
ServerView received the following alarm from server [Server Name]:
Adapter [Array Controller Name]: Disk [%s] missing after reboot
(Server [Server Name])
Description
Unable to find the hard disk at the restart of the server.
Example
ServerView received the following alarm from server PRIMERGY03:
Adapter LSI MegaRAID SAS 8408E (0): Disk (0) missing after reboot
(Server PRIMERGY03)
Source
Fujitsu ServerView Services
ID
3
Message
ServerView received the following alarm from server [Server Name]:
Adapter [Array Controller Name]:Logical drive [%s] missing after reboot
(Server [Server Name])
Description
Unable to find the logical drive at the restart of the server.
Example
ServerView received the following alarm from server PRIMERGY03:
Adapter LSI MegaRAID SAS 8408E (0): Logical drive (0) missing after reboot
(Server PRIMERGY03)
MegaRAID SAS User's Guide
z Source: For ServerView RAID events, or ServerView RAID Manager event
window
Source
ServerView RAID
ID
10476
Message
Adapter %s: Disk (%s) missing after reboot
Description
Unable to find the hard disk at the restart of the server.
Example
Adapter LSI MegaRAID SAS 8408E (0): Disk (0) missing after reboot
Source
ServerView RAID
ID
10477
Message
Adapter %s: Logical drive %s missing after reboot
Description
Unable to find the logical drive at the restart of the server.
Example
Adapter LSI MegaRAID SAS 8408E (0): Logical drive (0) missing after reboot
When the above events are recorded, check the states of the array using ServerView RAID Manager. If
the array is recognized as the normal state, ignore the events.
` Information that Windows SCSI mini port driver outputs will be changed by applying the hotfix. So, the
information is different from what ServerView RAID memorized until then. That is why these events
occur. These events may be recorded at the first restarting after applying the hotfix.
` These events will not occur if the state of the array is normal after the next startups.
` These events are recorded when restarting the server after installing Windows 2000 Server since the
hotfix is automatically applied if it is installed using ServerStart.
1.5.5 Notes on WebBIOS Startup When Installing Multiple
MegaRAID SAS Controllers
When you have multiple MegaRAID SAS controllers in your system (for example, RAID5/6 SAS based
on LSI MegaRAID for internal hard disk connection, and MegaRAID SAS 8344ELP for external
hard disk connection) a POST screen appears for each MegaRAID SAS during POST.
The following message to start WebBIOS appears as many times as the number of MegaRAID SAS
installed in your system.
Press <Ctrl><H> for WebBIOS.
The WebBIOS you are using is that of RAID 5/6 SAS based on LSI MegaRAID. And even just one of
the following two actions will display only MegaRAID SAS 8344ELP, not RAID 5/6 SAS based on LSI
MegaRAID, on the [Adapter Selection] window appeared right after the WebBIOS startup.
• When pressing the [Ctrl] + [H] keys twice or more on the POST window.
• When pressing the [Ctrl] + [H] keys once on the POST window of RAID 5/6 SAS based on LSI
MegaRAID, then pressing the [Ctrl] + [H] keys on the POST window of MegaRAID SAS 8344ELP
that is optionally installed.
43
Chapter 1 Overview
If you keep accessing to MegaRAID SAS 8344ELP when you want to access WebBIOS of RAID 5/6
SAS based on LSI MegaRAID and configure an array, press the [Alt] + [Ctrl] + [Del] keys to restart the
system. Then, while the POST window of RAID 5/6 SAS based on LSI MegaRAID is appearing, press
the [Ctrl] + [H] keys only once to start WebBIOS.
Here are some examples of actual WebBIOS windows:
z When both RAID 5/6 SAS based on LSI MegaRAID and MegaRAID SAS
8344ELP which is optionally installed appear on the same screen
Select array controller that you want to operate and click [Start]. Then you can operate any array
controllers for such functions as array configuration.
z When only MegaRAID SAS 8344ELP which is optionally installed appears,
but not RAID 5/6 SAS based on LSI MegaRAID
With MegaRAID SAS 8344ELP, clicking [Start] will allow you such operation as configuring an array.
To operatae RAID 5/6 SAS based on LSI MegaRAID, restart the system since you cannot operate it at
this point.
1.5.6 Hard Disk Failure LED during Operation
When using RAID 5/6 SAS based on LSI MegaRAID, during the few minutes between the OS monitor
closure and POST screen appearance at OS restart, failure LEDs of some hard disks may be lit.
If the LEDs go off after POST screen appearance, there is no problem. If not, even with a successful
POST operation, the hard disks may actually be failed. Check the status of the array with a management
tool.
44
Chapter 2
Array Configuration and
Management [WebBIOS]
This chapter explains the WebBIOS setup
procedures. WebBIOS is a basic utility to set up
and manage the array controller.
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Starting and Exiting WebBIOS . . . . . . . . . . . . . . . . . . . . .
Checking Each Status [WebBIOS] . . . . . . . . . . . . . . . . . .
Creating/Deleting Disk Array Configuration . . . . . . . . . . .
Setting/Releasing Spare Disk . . . . . . . . . . . . . . . . . . . . .
Operations on Logical Drives . . . . . . . . . . . . . . . . . . . . . .
Rebuilding Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reusing Hard Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
51
63
84
86
94
95
45
Chapter 2 Array Configuration and Management [WebBIOS]
2.1 Starting and Exiting WebBIOS
This section explains how to start up and exit WebBIOS. WebBIOS can be set to start
from the BIOS at system startup, regardless of whether the OS has been installed or
not on the computer to be used.
` To use WebBIOS, a mouse needs to be connected. Before starting WebBIOS, make sure that the
mouse is connected to the server.
` If both this array controller and the SCSI array controller (MegaRAID SCSI) are installed in the system,
the connected USB mouse may not work when WebBIOS for the SCSI array controller starts up.
In this case, start up WebBIOS for this array controller to operate the SCSI array controller. While the
POST screen of this array controller appears, press the [Ctrl]+[H] keys to start up WebBIOS.
2.1.1 Starting Up WebBIOS
1
Turn on the server, and press the [Ctrl]+[H] keys while the following messages
are displayed on the screen.
Press the [Ctrl]+[H] keys while the message
"Press <CTRL> <H> for WebBIOS" is displayed.
` When your server has a number of this array controllers installed in it, only press the [Ctrl] +[H]
keys once while a message of the array controller to operate WebBIOS is shown.
The following message appears and WebBIOS starts up after the system BIOS operations are
complete.
WebBIOS will be executed after POST completes
46
MegaRAID SAS User's Guide
When WebBIOS starts, the [Adapter Selection] window of WebBIOS appears.
If other array cards are also installed, more than one array controllers are displayed.
` When the system has multiple controllers, the array controller that you wish to operate may not
appear on the [Adapter Selection] window. In this case, follow the procedure at "1.5.5 Notes on
WebBIOS Startup When Installing Multiple MegaRAID SAS Controllers" (Jpg.43).
` For this array controller, the [Type] in the window shown above is one of the following controllers.
• MegaRAID SAS PCI Express(TM) ROMB
• MegaRAID SAS 8300XLP
• MegaRAID SAS 8408E
• MegaRAID SAS 8344ELP
• RAID 5/6 SAS based on LSI MegaRAID
2
Select the array controller to be operated, and click [Start].
The main window of WebBIOS will appear.
47
Chapter 2 Array Configuration and Management [WebBIOS]
` The following screen appears when abnormal hard disk is detected. Click [Cancel] and continue. Check the status of the hard disk and replace it if it is defective, referring to "Chapter 6
Replacing Hard Disk" (Jpg.243).
Do not click [GuidPreview] or [ClearForeighCfg].
„ WebBIOS main window
The main window of WebBIOS consists of three areas.
Physical Drives view
Main menu
48
Virtual Drives view / Configured Drives view
MegaRAID SAS User's Guide
z Main menu
WebBIOS has the following menus:
table: WebBIOS main menu
Menu name
Description
Adapter Properties
Allows you to view/change the properties settings of the array controller.
Scan Devices
Redetects the hard disks connected.
Virtual Disks
Displays a list of the logical drives.
Physical Drives
Displays a list of the hard disks. You can also check the status of connected
hard disks. J"2.2.1 Checking Hard Disk Status" (pg.51)
Configuration Wizard
Creates and adds/deletes a disk array configuration.
Adapter Selection
Switches array controllers.
Physical View
Displays the [Configured Drives] view, where the disk group can be browsed
and operated.
The menu name switches to the Logical View.
Logical View
Displays the [Virtual Drives] view, where the logical drive can be browsed
and manipulated.
The menu name switches to the Physical View.
Events
Displays the event log on the array controller.
This function is not supported. Do not use it.
Exit
Exits WebBIOS.
` You can switch between the [Virtual Drives] and [Configured Drives] views by selecting [Logical View]
or [Physical View] in the main menu.
z [Physical Drives] view
Displays a list of the hard disks. The status and the capacity of each hard disk are also displayed. For
details about the status of hard disks, see "2.2.1 Checking Hard Disk Status" (Jpg.51).
z [Virtual Drives] view
The [Virtual Drives] view displays the relationship between disk groups and logical drives. The RAID
level, capacity and status of logical drives are also displayed. For details about the logical drive status,
see "2.2.2 Checking Logical Drive Status" (Jpg.54).
z [Configured Drives] view
Selecting [Physical View] in the main menu switches the [Virtual Drives] view to the [Configured
Drives] view. The [Configured Drives] view allows you to check the relationship between disk groups
and the hard disks that make up the disk groups. The status and the capacity of each hard disk are also
displayed.
49
Chapter 2 Array Configuration and Management [WebBIOS]
2.1.2 Exiting WebBIOS
1
Click [Exit] in the main menu.
2
When the message "Exit Application" appears, select [Yes].
WebBIOS exits.
3
50
When the message "Please Reboot your System" appears, turn off the server
or press the [Ctrl]+[Alt]+[Delete] keys to restart the server.
MegaRAID SAS User's Guide
2.2 Checking Each Status [WebBIOS]
This section explains how to check each status, such as the hard disk status, the
logical drive status, and the background task status.
• Checking Hard Disk Status (Jpg.51)
• Checking Logical Drive Status (Jpg.54)
• Checking Progress of Background Task (Jpg.58)
• Confirming Array Controller Information (Jpg.60)
2.2.1 Checking Hard Disk Status
Checks the hard disk status.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
In the [Physical Drives] view, a list of connected hard disks and their status are displayed.
a
b
d
c
e
f
Status of hard disk drives (icons)
table: Hard disk information
Meaning of Item
Example
a
Hard disk ID. This is a number to specify each hard disk, not to
indicate actual storage bay number. To see slot numbers and
addresses, refer to the detailed information in the step 2.
PD0
b
The number of the disk group to which the hard disk belongs. Only
appears when included in a disk group.
DG0
c
Hard disk status.
ONLINE
d
Hard disk capacity.
69472MB
e
Hard disk vendor name, or interface form.
• For SAS hard disks:
FUJITSU
• For SATA hard disks:
ATA
f
Hard disk model name.
MAX3147RC
51
Chapter 2 Array Configuration and Management [WebBIOS]
Hard disk Icons
The hard disk status is indicated with an icon, as follows.
table: Indications for each hard disk status
Color
Green
Message
ONLINE
Status
Online
Description
Array is configured and functions normally
Blue
UNCONF GOOD
Unused
Array is not in use but functions normally
Red
OFFLINE
Offline
Read and write protect
Red
FAILED
Failed
Failure
Black
UNCONF BAD
Failed
Array is not configured and has a failure
Brown
REBUILD
Rebuilding
Rebuild in progress
Pink
HOTSPARE
or
GL HOTSPARE
Spare disk
Spare disk
` For hard disks displayed in yellow, PFA (S.M.A.R.T.) is detected. Hard disks, for which PFA
(S.M.A.R.T.) is detected may fail in the near future, and should be replaced as soon as possible. For how to replace hard disks, see "Chapter 6 Replacing Hard Disk" (Jpg.243).
` Depending on the failure condition of the hard disk, a "PD Missing from DG x:Slot y" entry may
be added and displayed. This entry means that the hard disk with ID y in the disk group × is in
failure condition. See "Chapter 6 Replacing Hard Disk" (Jpg.243) to replace the hard disk with
the displayed ID and perform rebuild.
2
Click the icon for the hard disk for which you want to check detailed information
or that you want to manipulate.
The status and the settings of the selected hard disk are displayed.
Detailed
information
Functions
52
MegaRAID SAS User's Guide
Detailed information
table: The meaning of the Detailed Information for each item
Item
Revision
Description
Displays the firmware version.
Enclosure ID
Displays the connected enclosure number.
Slot Number
Displays the installed slot number.
Device Type
Displays the device type.
Connected Port
Displays the connected port number.
Media Errors
Displays the number of media errors.
This function is not supported. Even if counted, no problem occurs because the
error is restored by the firmware.
Pred Fail Count
If PFA (S.M.A.R.T.) is detected, other than zero appears. Hard disks, for which
PFA (S.M.A.R.T.) is detected may fail in the near future, and should be replaced as
soon as possible. See "Chapter 6 Replacing Hard Disk" (Jpg.243) for the
replacement procedure.
SAS Address
Displays the SAS address of the hard disks.
Physical Drive State
Displays the current status of the hard disks. For details about the status of a
hard disk, see " Hard disk Icons" (Jpg.52).
Coerced Size
Displays the hard disk capacity recognized by the array controller.
Functions
This window allows you to execute functions on the hard disks. The executable functions may
vary according to the hard disk status.
table: Functions in the function executing area
Item
Description
Executable Status
Locate
Makes the failure LED of the hard disk flash for ten
seconds to tell the location.
All
Make Global HSP
Sets a spare disk.
J"2.4.1 Setting Spare Disk" (pg.84)
UNCONF GOOD
Make Dedicated HSP
Creates a special spare disk.
Disabled. Do not use this.
UNCONF GOOD
Make Unconf Bad
Forcibly puts the hard disk into UNCONF BAD status.
Disabled. Do not use this.
UNCONF GOOD
Prepare for Removal
Stops the motor rotation.
Disabled. Do not use this.
UNCONF GOOD
Undo Prepare for
Removal
Re-starts the stopped motor.
Disabled. Do not use this.
UNCONF GOOD
Replace Missing PD
Allocates a new hard disk instead of the failed disk. Do not
execute this function without instructions from our engineer.
The data may be lost.
UNCONF GOOD
Make Drive Offline
Forcibly puts the hard disk in OFFLINE status.
Do not execute this function without instructions from our
engineer, as the data may be lost.
ONLINE
Make Online
Forcibly puts the hard disk in ONLINE status.
Do not execute this function without instructions from our
engineer. The data may be lost.
OFFLINE
Rebuild Drive
Starts rebuild.
J"2.6 Rebuilding Hard Disk" (pg.94)
OFFLINE
53
Chapter 2 Array Configuration and Management [WebBIOS]
table: Functions in the function executing area
Item
3
Description
Executable Status
Mark as Missing
Forcibly releases the target hard disk from the disk array
configuration.
Do not execute this function without instructions from our
engineer. The data may be lost.
OFFLINE
Make Unconf Good
Forcibly puts the hard disk in UNCONF GOOD status.
Disabled. Do not use this.
UNCONF BAD
Remove HOTSPARE
Releases a spare disk.
J"2.4.2 Releasing Spare Disk" (pg.85)
HOTSPARE
When the check or operation is finished, click [HOME] or
to return to the
main window.
2.2.2 Checking Logical Drive Status
Checks the logical drive status.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
In the [Virtual Drives] view, the logical drive status appears.
` If the [Configured Drives] view is shown, select [Virtual View] in the main menu to display the
[Virtual Drives] view.
a
c
b
d
Status of the logical drive (icon)
table: Logical drive information
Meaning of Item
54
Example
a
Logical drive number.
VD0
b
RAID level of the logical drive.
RAID1
c
Logical drive capacity.
139488MB
d
Logical drive status.
Optimal
MegaRAID SAS User's Guide
` When a logical drive is configured for RAID 10, as shown below, the same logical drive number
(VD y) is allocated to a group of disk groups with successive numbers (DG x).
Logical Drive Icon
The logical drive icon appears in the following color according to the logical drive status.
table: Color of each logical drive status
Color
2
Display
Status
Description
Green
Optimal
Online
Normal
Yellow
Partially
Degraded
Partially
critical
Operating with redundancy. But a
hard disk has been failed.
Blue
Degraded
Critical
Operation with non-redundancy
Red
Offline
Offline
Unavailable
Click the logical drive which you want to check details or operate.
The status and settings of the selected logical drive are displayed.
RAID 5/6 SAS based on LSI MegaRAID
Properties
area
Policies
area
Operations
area
Capacity Expansion
Setting area
55
Chapter 2 Array Configuration and Management [WebBIOS]
For MegaRAID SAS 300-8E ROMB / MegaRAID SAS 8300XLP / MegaRAID SAS
8408E / MegaRAID SAS 8344ELP
Properties
area
Policies
area
Operations
area
Capacity Expansion
Setting area
Properties
table: Properties information
Item
56
Description
RAID Level
RAID level of the logical drive.
State
Logical drive status. For details about the logical drive status, see " Logical Drive Icon"
(Jpg.55).
Size
Displays the total capacity of the logical drive.
Stripe Size
Displays the configurable stripe sizes of the logical drive.
MegaRAID SAS User's Guide
Policies
table: Policies information
Item
Description
Access
Sets the I/O access. Do not change this.
Read
Sets the read policy. Do not change this.
Disk Cache
Sets the write cache of the hard disk. Do not change this.
Write
Displays and sets Write Policy.
For RAID 5/6 SAS based on LSI MegaRAID, WTru (Write Through) or WBack (Write
Back) is shown. And below that is "Use wrthru for failure or missing battery" where
you can change or display the settings of Write Policy. With a check at "Use wrthru for
failure or missing battery", the Write Policy will be set to WTru (Write Through) when
a battery is not installed or failed. Without a check, the Write Policy will be BadBBU
that will operate a controller with WBack (Write Back) even when a battery is not
installed or failed.
It displays WThru (Write Through), WBack (Write Back), or BadBBU for a controller
other than RAID 5/6 SAS based on LSI MegaRAID. Click [Change] after changing the
settings to reflect the new settings.
J"1.3.1 Write Policy" (pg.26).
Disable BGI
Sets BGI. Do not change this.
I/O
Sets DMA transmission mode. Do not change this.
` If a background task is in operation, the [Policies] items are only displayed, and cannot be
modified.
Operations
Operations can be executed on the logical drives. To execute, select the target function and click
[Go].
table: Information about the operations area
Item
Description
Del
Deletes the logical drive.
J"2.5.5 Deleting Logical Drive" (pg.92).
Locate
Makes the failure LED of the hard disk installed in the logical drive blink for ten
seconds to indicate the location.
Fast or FastInit
Performs fast initialization for a logical drive.
J"2.5.2 Fast Initialization of Logical Drive" (pg.87).
Slow or
SlowInit
Performs foreground initialization for a logical drive.
J"2.5.1 Initializing Logical Drives" (pg.86).
CC
Performs Make Data Consistent for a logical drive.
J"2.5.3 Make Data Consistent of Logical Drive" (pg.88).
Capacity Expansion Setting
The capacity of a logical drive can be expanded. For more details, see "2.5.4 Expanding the
Capacity of Logical Drives" (Jpg.89).
3
When the operation is finished, click [HOME] or
to return to the main
window.
57
Chapter 2 Array Configuration and Management [WebBIOS]
2.2.3 Checking Progress of Background Task
Displays the status of a task currently running in the background. This enables to check the progress of
various kinds of initialization, Make Data Consistent, rebuild, and capacity expansion for logical drives.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Click the button for the task in progress shown at the bottom of the main window.
` The buttons to be appeared and background tasks appeared by pressing buttons are as follows:
• [Rebuild Progress] Rebuild
• [Initialization Progress] Foreground Initialization
• [Background Initialization Progress] Background Initialization
• [Check Consistency Progress] Make Data Consistent
• [Reconstruction Progress] Capacity Expansion
• [VD Progress Info] Foreground Initialization, Background Initialization, Check Consistency
Progress, and all of the Capacity Expansion
• [PD Progress Info] Rebuild
` If the button for a task which is supposed to be running in the background is not shown, click
[Scan Devices] in the main menu.
58
MegaRAID SAS User's Guide
The names and status of running tasks are shown in the left area of the window.
` If you select [Abort] for a target background task and click [Go] in the lower right of the window,
that background task will be aborted. Normally, do not abort.
` Although the options [Fast Initialize], [Check Consistency], [Properties], and [Set Boot Drive]
are shown in the right area of the window, these functions are not supported in this window. Do
not use them.
3
Check the information, then click [HOME] or
to return to the main window.
59
Chapter 2 Array Configuration and Management [WebBIOS]
2.2.4 Confirming Array Controller Information
This window displays array controller information. The settings can be changed. Before creating an
array configuration, make sure to check the array controller settings.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Click [Adapter Properties] from the main menu.
The [Adapter Information] window appears.
table: Array controller information
Item
Firmware Version
60
Description
Displays the firmware version of the array controller.
WebBIOS Version
Displays the WebBIOS version.
SubVendorID
Displays the Sub Vendor ID.
SubDeviceID
Displays the Sub Device ID.
HostInterface
Displays the interface type between the server and the array controller.
PortCount
Displays the number of SAS ports.
NVRAM Size
Displays the NVRAM size.
Memory Size
Displays the cache memory size.
Firmware Time
Displays the time stamp of the firmware.
Serial Number
Displays array controller serial number. However, the value displayed here is
invalid for the onboard array controllers.
Min Stripe Size
Displays the minimum configurable stripe size of logical drives.
Max Stripe Size
Displays the maximum configurable stripe size of logical drives.
Virtual Disk Count
Displays the number of created logical drives.
Physical Disk Count
Displays the number of hard disks connected.
FW Package Version
Displays the total version that includes the array controller’s firmware and the
BIOS, etc.
MegaRAID SAS User's Guide
3
Click [Next].
The [Adapter Properties] window appears.
To Change Properties
To change the property settings of the array controller, edit or select the item to change, and then
click [Submit] to confirm the change.
` Before changing the properties, check the changeable and fixed items in "„ Array controller
settings" (Jpg.61).
4
Confirm the description, then click [HOME] or
to return to the main window.
„ Array controller settings
The initial value for each property item of the array controller is as follows:
table: Array controller property initial values
Item
Value
Description
Battery Backup
Present
or None
Displays whether a battery is installed or not. "Present" (detected) or
"None" (not detected) will appear depending on whether a battery is
detected or not.
Set Factory Defaults
No
Selecting [Yes] and saving the settings allows you to reset each setting
of the array controller to the initial value.
Cluster Mode
Disabled (Do
not change)
This is an optional setting for supporting multi-initiator environments.
This item is set to "Disabled" and must not be changed.
Rebuild Rate
[Note 1]
Sets the priority when performing rebuild. The higher this value, the
higher the priority of rebuild over I/Os from the server.
BGI Rate
[Note 1]
Sets the priority when running background initialization. The higher
this value, the higher the priority of background initialization over I/
Os from the server.
CC Rate
[Note 1]
Sets the priority when performing Make Data Consistent. The higher
this value, the higher the priority of Make Data Consistent over I/Os
from the server.
61
Chapter 2 Array Configuration and Management [WebBIOS]
table: Array controller property initial values
Item
Value
Description
Reconstruction Rate
[Note 1]
Sets the priority when performing capacity expansion. The higher this
value, the higher the priority of capacity expansion over I/Os from the
server.
Adapter BIOS
Enabled
(Do not
change)
Enables or disables the array controller BIOS.
This item is set to "Enabled" and must not be changed.
Coercion Mode
None
(Do not
change)
Sets a capacity rounding function to make varying hard disk capacities
equal to each other.
This item is set to "None" and must not be changed.
PDF Interval
300
(Do not
change)
Sets the PFA (=S.M.A.R.T.) tracking interval for the hard disk.
This item is set to "300" and must not be changed.
Alarm Control
Disabled
(Do not
changer)
If a buzzer for notifying errors is installed in the array controller, this
enables or disables the buzzer.
This item is set to "Disabled" and must not be changed.
Patrol Read Rate
20
Sets the priority when running Patrol Read. The higher this value, the
higher priority the Patrol Read has over I/Os from the server. This
setting is not supported.
Cache Flush Interval
4
(Do not
change)
Sets the data write interval from the cache memory to the hard disk
when running in write back mode.
This item is set to "4" and must not be changed.
Spinup Drive Count
2
(Do not
change)
Sets the number of hard disks that start rotating at the same time.
This item is set to "2" and must not be changed.
Spinup Delay
6
(Do not
change)
Sets the interval to the next start after starting the hard disk rotation for
the first time.
This item is set to "6" and must not be changed.
StopOnError
Disabled
(Do not
change)
During POST, sets whether to stop the POST as soon as a specific
message appears.
This item is set to "Disabled" and must not be changed.
[Note 1]: 80 for: MegaRAID SAS 300-8E ROMB, MegaRAID SAS 8300XLP, MegaRAID SAS 8408E,
MegaRAID SAS 8344ELP
30 for: RAID 5/6 SAS based on LSI MegaRAID
62
MegaRAID SAS User's Guide
2.3 Creating/Deleting Disk Array
Configuration
This section explains how to configure a new disk array.
2.3.1 Creating Disk Array Configuration
„ Overview of array configuration procedure
Follow the procedure below to configure disk arrays. The operation on an array configuration screen of
WebBIOS differs whether you have RAID 5/6 SAS based on LSI MegaRAID, or something else. Make
sure to follow the procedure for your controller.
` Before starting the disk array configuration, see "2.2.4 Confirming Array Controller Information"
(Jpg.60) and check the array controller properties.
Select whether to create a new disk array configuration or to add a logical drive to the
current disk array configuration.
Create a disk group.
Only for RAID 5/6 SAS based on LSI MegaRAID, create a disk group (span) to be
included in a logical drive.
Create the logical drive
Select the RAID level
Set the Write Policy
Set the capacity of the logical drive
Initialize the logical drive.
COMPLETION
63
Chapter 2 Array Configuration and Management [WebBIOS]
„ How to create disk array configuration
z For RAID 5/6 SAS based on LSI MegaRAID
` When the disk array is configured with RAID 10, note that two or more logical drives cannot be defined
in a RAID 10 disk group.
Follow the procedure below to configure a disk array.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Click [Configuration Wizard] on the main menu.
The [Configuration Wizard] window appears.
3
Select [New Configuration] to delete all the current disk array configuration and
create a new disk array configuration, or [Add Configuration] to add a logical
drive to the current disk array configuration. Then click [Next].
` If you select [New Configuration] when a disk array configuration already exists, a warning
appears because the existing configuration will be all deleted.
If you want to delete the current configuration, click [Yes] to proceed.
To add a new logical drive while keeping the existing logical drive, click [No] to select [Add
Configuration].
64
MegaRAID SAS User's Guide
The following window appears.
` [Auto Configuration: With Redundancy (Recommended)] and [Auto Configuration: Without
Redundancy] are not supported. Do not select them.
4
Select [Custom Configuration] and click [Next].
The [DG Definition] window appears.
5
Create a disk group.
The procedure to create a disk group is different depending on the RAID level.
` Do not configure the disk group of RAID 10 and other RAID levels at the same time when RAID
10 exists with other RAID levels (RAID 0 / RAID 1 / RAID 5). After configuring a disk group, add
another disk group by clicking [Configuration Wizard] – [Add Configuration] again.
65
Chapter 2 Array Configuration and Management [WebBIOS]
Configuring RAID 0 / RAID 1 / RAID 5 / RAID 6
Follow the procedure below:
1. While pressing the [Ctrl] key, click all the hard disks to be added to a disk group on
the "Physical Drives" area.
Seleclable hard disks are indicated as "UNCONF GOOD" in blue.
table: Number of hard disks needed for each RAID level
RAID level
Necessary number of hard disks
RAID 0
1 or more
RAID 1
2
RAID 5
3 or more
RAID 6
3 or more
2. Click [AddtoArray].
The hard disks to be included in a disk group are confirmed and displayed in the [Disk
Groups] area.
66
MegaRAID SAS User's Guide
3. Click [Accept DG].
The disk group to be included in the [Disk Groups] area will be confirmed and the disk
capacity in the disk group will be displayed.
4. Repeat the procedure above to set as many disk groups as needed.
Add as many hard disks for the array configuration as needed.
` Hard disks in a single disk group should be of the same model (with the same capacity and the
rotation speed).
` Hard disks that are already included in a disk group are displayed as "Online" in green.
` If an incorrect disk group is set by mistake, click [Back] and redo the procedure from the step 3
(Jpg.64).
5. Click [Next].
The [Span Definition] window appears.
67
Chapter 2 Array Configuration and Management [WebBIOS]
6. Check that the disk group has been selected in the [Array With Free Space] area,
then click [Add to SPAN].
Now the disk group has been confirmed and added to the [Span] area.
7. Click [Next].
The [VD Definition] window appears.
Configuring RAID 10
Follow the procedure below:
1. While pressing the [Ctrl] key, click two hard disks to be in the disk group on the
"Physical Drives" area.
The two drives will configure a mirror.
Selectable hard disks are indicated as "UNCONF GOOD" in blue.
68
MegaRAID SAS User's Guide
2. Click [AddtoArray].
Now the disk group has been confirmed and added to the [Disk Groups] area.
3. Click [Accept DG].
Now the disk group to be added has been confirmed and the capacity in the Disk Group
appears.
69
Chapter 2 Array Configuration and Management [WebBIOS]
4. Repeat the procedure above until you arrange all the hard disks to configure RAID
10 into disk groups.
Add as many hard disks as needed to configure an array. To configure RAID 10, you need
to create disk groups here. Here is an example four hard disks create two disk groups.
` Hard disks in a single disk group should be of the same model (with the same capacity and the
rotation speed).
` Hard disks that are already included in a disk group appears as "Online" in green.
` If an incorrect disk group is set by mistake, click [Back] and redo the procedure from the step 3
(Jpg.64).
5. Click [Next].
The [Span Definition] window appears.
70
MegaRAID SAS User's Guide
6. Check that disk groups have been selected in the [Array With Free Space] area,
click [Add to SPAN].
Now the disk group has been confirmed and added to the [Span] area.
Repeat the procedure until all the disk groups in the [Array With Free Space] are moved to
the [Span] area.
` To configure RAID 10, you need to create disk groups in advance.
7. Click [Next].
The [VD Definition] window appears.
71
Chapter 2 Array Configuration and Management [WebBIOS]
6
Create a logical drive.
Enter the settings for the logical drive.
The setting items and their defaults for a logical drive are as follows:
table: Logical drive settings
Item
Default value
Remarks
RAID Level
Depends on the
number of hard
disks in a disk group
Sets a RAID level.
Stripe Size
64KB
Do not change.
Access Policy
RW
Do not change.
Read Policy
Normal
Do not change.
Write Policy
WThru
Set the Write Policy. Select WThru (Write Through), or
WBack (Write Back).
For the OS installation, make sure to set WThru. You can
change the Write Policy after the installation.
Wrthru for BAD
BBU
Checked
With a check, when there is no battery or at a time of a
failure, the Write Policy is switched from WBack to
WThru. Without a check, it remains BadBBU which works
as WThru even when there is no battery or at a time of a
failure.
IO Policy
Direct
Do not change.
Disk Cache Policy
Disable
Do not change.
Disable BGI
No
Do not change.
Select Size
The maximum
capacity of the
logical drive
Sets the capacity of the logical drive in MB.
` Only one RAID level can be configured in a disk group.
` Always refer to "1.3.1 Write Policy" (Jpg.26) before changing the Write Policy default setting.
72
MegaRAID SAS User's Guide
Configuring RAID 0 / RAID 1 / RAID 5 / RAID 6
• The default [Select Size] value is the maximum capacity of a RAID level that was selected
when moved from the [VD Definition] window.
When you wish to manually change a RAID level or create it by dividing logical drives in a
disk group, select a RAID level and type the appropriate number for its capacity. You can refer
to the [Next LD, Possible RAID Levels] on the right side of the window.
For instance, as in the image below, when the number shows "R0:277888 R5:208416
R6:138944", the maximum RAID capacity is 277888MB, 208416MB, and 138944MB for
RAID 0, RAID 5, RAID 6 respectively.
• Putting a number smaller than the maximum value for a logical drive capacity will allow you
to create logical drives.
Configuring RAID 10
• Set [RAID Level] to "RAID 10".
• Only one logical drive with maximum capacity of the disk group can be created.
Do not change the [Select Size].
7
Click [Accept].
The logical drive is confirmed and added to the area in the right side of the window.
` When there is available logical drive capacity left in a disk group, click [Back] to show the [Span
Definition] window. Then create as many logical drives as needed until using up all the available areas.
8
Click [Next].
The [Preview] window appears.
The [Preview] Window example (For RAID 0 / RAID 1 / RAID 5 / RAID 6)
73
Chapter 2 Array Configuration and Management [WebBIOS]
The [Preview] Window Example (For RAID 10)
` If you create an incorrect logical drive by mistake, click [Back] and start again from the [DG
Definition] window.
` When RAID 10 already exists, the same logical drive number appears straddling disk groups in
the logical drive.
9
Click [Accept].
The message "Save this Configuration?" appears.
10
Click [Yes].
All the settings up to here are saved and the [Confirm Page] window appears.
11
To perform fast initialization of the logical drive here, click [Yes]. To perform
other initialization or fast initialization later, click [No].
` Clicking [Yes] at this point will start fast initialization. After the fast initialization which finishes
soon, background initialization will automatically be started.
To perform foreground initialization, click [No] to return to the main window, and then perform
foreground initialization by following "2.5.1 Initializing Logical Drives" (Jpg.86).
74
MegaRAID SAS User's Guide
z For MegaRAID SAS 300-8E ROMB / MegaRAID SAS 8300XLP / MegaRAID
SAS 8408E / MegaRAID SAS 8344ELP
` When RAID 10 configures a disk array, note that two or more logical drives cannot be defined in the
RAID 10 disk group.
Follow the procedure below to configure a disk array.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Click [Configuration Wizard] on the main menu.
The [Configuration Wizard] window appears.
3
Select [New Configuration] to delete all the current disk array configurations
and create a new disk array configuration, or [Add Configuration] to add a
logical drive to the current disk array configuration. Then click [Next].
` When you select [New Configuration] when a disk array configuration already exists, a warning
message appears telling that the existing configuration will be all deleted.
If you want to delete the current configuration, click [Yes] to proceed.
To add a new logical drive while keeping the existing logical drive, click [No] to select [Add
Configuration].
75
Chapter 2 Array Configuration and Management [WebBIOS]
The following window appears.
` [Auto Configuration: With Redundancy (Recommended)] and [Auto Configuration: Without
Redundancy] are not supported. Do not select them.
4
Select [Custom Configuration] and click [Next].
The [DG Definition] window appears.
76
MegaRAID SAS User's Guide
5
Create a disk group.
` Do not configure the disk group of RAID 10 and other RAID levels at the same time when RAID
10 exists with other RAID levels (RAID 0 / RAID 1 / RAID 5). After configuring a disk group, add
another disk group by clicking [Configuration Wizard] – [Add Configuration] again.
Configuring RAID 0 / RAID 1 / RAID 5
Follow the procedure below:
1. While pressing the [Ctrl] key, click all the hard disks to be added to a disk group on
the "Physical Drives" area.
The available hard disks are indicated as "UNCONF GOOD" in blue.
table: Number of hard disks needed for each RAID level
RAID level
Necessary number of hard disk
RAID 0
1 or more
RAID 1
2
RAID 5
3 or more
2. Click [Accept DG].
The disk group is confirmed and displayed in the [Disk Groups] area.
3. Repeat the procedure above to set as many disk groups as needed.
Add as many hard disks for the array configuration as needed.
` Hard disks in a single disk group should be of the same model (with the same capacity and
rotation speed).
` Hard disks that are already included in a disk group are displayed as "Online" in green.
` If an incorrect disk group is set by mistake, click [Back] and redo the procedure from the step 3
(Jpg.75).
Configuring RAID 10
Follow the procedure below:
1. While pressing the [Ctrl] key, select two hard disks to set to the disk group from the
"Physical Drives" area.
The mirror system is configured with the selected two hard disks.
The available hard disks are indicated as "UNCONF GOOD" in blue.
2. Click [Accept DG].
The disk group is confirmed and displayed in the [Disk Groups] area.
3. Repeat the procedure above to set all the hard disks which configure RAID 10 to
the disk groups.
` Hard disks in a single disk group should be of the same model (with the same capacity and the
rotation speed).
77
Chapter 2 Array Configuration and Management [WebBIOS]
` Hard disks that are already included in a disk group appears as "Online" in green.
` If an incorrect disk group is set by mistake, click [Back] and redo the procedure from the step 3
(Jpg.75).
6
Click [Next].
The [VD Definition] window appears.
7
Create a logical drive.
1. Select disk groups for a logical drive from the area in the right.
78
MegaRAID SAS User's Guide
` To create a logical drive, begin from the disk group with the smallest number. For example, if
there are disk groups named "DG 0" and "DG 1", start creating a logical drive from the disk
group "DG 0".
` Do not create a logical drive for a new disk group while free space remains in the old disk
group. Wait until no free space remains in the old disk group to create a logical drive for a new
disk group.
` To configure RAID 10, select all the disk groups created in step 5 while pressing the [Ctrl] key.
2. Enter settings for a logical drive.
The setting items and their defaults for the logical drive are as follows:
table: Logical drive settings
Item
RAID Level
Default value
RAID 0
Remarks
Sets the RAID level.
Stripe Size
64KB
Do not change this.
Access Policy
RW
Do not change this.
Read Policy
Normal
Do not change this.
Write Policy
WThru
Sets WThru (Write Through), WBack (Write Back), or
BadBBU.
When installing the OS, make sure to set the Write Policy
to WThru. You can change it after the OS installation.
IO Policy
Direct
Do not change this.
Disk Cache Policy
Disable
Do not change this.
Disable BGI
No
Do not change this.
Select Size
(Blank)
Sets the capacity of a logical drive in MB.
Configuring RAID 0 / RAID 1 / RAID 5
` Only one RAID level can be configured in a disk group.
` Always refer to "1.3.1 Write Policy" (Jpg.26) before changing the Write Policy default setting.
79
Chapter 2 Array Configuration and Management [WebBIOS]
` The capacity of the logical drive appears in the "RAID level = maximum value" format above
the disk groups to the right. Do not set a higher value than the maximum value. For example, in
the figure below, if "DG 0:R0=138944MB, R1=69472MB" appears, the maximum configurable
RAID 0 capacity for disk group 0 is 138,944MB, and 69,472MB for RAID 1.
` Setting the logical drive capacity to a lower value than the maximum capacity allows you to create multiple logical drives.
Configuring RAID 10
• Set [RAID Level] to "RAID 1".
• Only one logical drive with maximum capacity of the disk group can be created.
Specify the total capacity of the selected disk groups in [Select Size].
For instance, when "DG 0:R0=138944MB,R1=69472MB" appears on the disk group in the
area in the right, capacity of one disk group is 69472MB. When RAID 10 is configured with
three disk groups (six hard disks), the capacity specified for [Select Size] is 208416MB.
69472MB × 3 = 208416MB
` Always refer to "1.3.1 Write Policy" (Jpg.26) before changing the Write Policy default setting.
8
Click [Accept].
The logical drive is added under the disk groups in the [Configuration] area.
` If there is free space left to set other logical drives, or if there is a disk group for which no logical drive has been set, the [VD Definition] window appears again. Return to the step 7, and
create logical drives until no free space remains in the disk group.
` When there is no more free space in the disk group, the [Preview] window appears.
When the disk group settings are finished, the [Preview] window appears.
80
MegaRAID SAS User's Guide
The [Preview] Window Example (For Combination of RAID 1 and RAID 5)
The [Preview] Window Example (For RAID 10)
` If you create an incorrect logical drive by mistake, click [Back] and start again from the [DG
Definition] window.
` If RAID 10 is configured, the first RAID 1 disk group appears as "RAID 10" and the other disk
groups are displayed as "(Contd)".
9
After confirming that the [Preview] window is correct, click [Accept].
The message "Save this Configuration?" appears.
81
Chapter 2 Array Configuration and Management [WebBIOS]
10
Click [Yes].
The modified settings are written, and the [Confirm Page] window appears.
11
To perform fast initialization of the logical drive here, click [Yes]. To perform
other initialization or fast initialization later, click [No].
` Clicking [Yes] at this point will start fast initialization. After a short while, background initialization will automatically be started. To perform foreground initialization, click [No] to return to the
main window, and then perform foreground initialization, referring to "2.5.1 Initializing Logical
Drives" (Jpg.86).
When neither fast initialization nor foreground initialization is performed, background initialization will be performed.
12
Click [HOME] or
to return to the main window.
2.3.2 Deleting Disk Array Configuration
To delete the entire current disk array configuration, use the [Clear Configuration] function in the
[Configuration Wizard].
When the disk array configuration is deleted, the data on the hard disk can no longer be accessed. The
configuration information for the disk array is completely deleted, and all hard disks are restored to the
"Unused" state.
` Normally, this function should not be used. If this function is used, the current settings on the array
controller are deleted and all the data on the hard disks connected to the array controller is also
deleted. If using this function, make a plan beforehand and proceed carefully.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
` When multiple array controllers are installed, select the controller for which the disk array is to
be deleted in the controller selection window.
82
MegaRAID SAS User's Guide
2
Click [Configuration Wizard] from the main menu.
The [Configuration Wizard] window appears.
3
Select [Clear Configuration] and click [Next].
When the following warning message appears, click [Yes].
4
If the [Configuration Preview] window appears, click [Accept].
When the message "Save this Configuration?" appears, click [Yes]. Allocation of all logical
drives is deleted, and the status of all hard disks connected to the array controller becomes
"Unused (UNCONF GOOD)".
` If a hard disk is in the "UNCONF BAD" state after clicking [Yes], it means that the hard disk is
defective. That hard disk cannot be used. See "Chapter 6 Replacing Hard Disk" (Jpg.243) to
replace the defective hard disk.
5
Click [HOME] or
to return to the main window.
83
Chapter 2 Array Configuration and Management [WebBIOS]
2.4 Setting/Releasing Spare Disk
This section explains how to set a hard disk in "Unused" state as a spare disk and
how to release an existing spare disk.
2.4.1 Setting Spare Disk
Sets a hard disk in "Unused (UNCONF GOOD)" state as a spare disk.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Select a hard disk in "Unused (UNCONF GOOD)" state to set as a spare disk
from the [Physical Drives] view in the main window.
3
Select [Make Global HSP] at the bottom of the window, and click [Go].
1. Click here to
select
2. Click
Make sure that the hard disk has been set as a spare disk and that the "Physical Drive State" is
indicated as "HOTSPARE" or "GL HOTSPARE".
4
84
Confirm the settings and click [HOME] or
to return to the main window.
MegaRAID SAS User's Guide
2.4.2 Releasing Spare Disk
Restores a hard disk that has been set as a spare disk to "Unused (UNCONF GOOD)" state.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Select the spare disk to restore to "Unused (UNCONF GOOD)" state from the
[Physical Drives] view of the main window.
3
Select [Remove HOTSPARE] at the bottom of the window, and click [Go].
1. Click here to
select
2. Click
Make sure that the spare disk has been released and that the "Physical Drive State" is indicated as
"UNCONF GOOD".
4
Confirm the settings and click [HOME] or
to return to the main window.
85
Chapter 2 Array Configuration and Management [WebBIOS]
2.5 Operations on Logical Drives
This section explains the following operations on logical drives:
• Initializing Logical DrivesJpg.86
• Fast Initialization of Logical DrivesJpg.87
• Make Data Consistent for Logical DrivesJpg.88
• Expanding Capacity of Logical DrivesJpg.89
2.5.1 Initializing Logical Drives
To initialize a logical drive in the foreground, perform the following procedure.
` Note that initialization of a logical drive will delete all the data on the target logical drive.
` For an overview of the initialization functions, see "1.3.2 Logical Drive Initialization" (Jpg.28).
` This array controller supports background initialization. If you do not want to initialize the logical drive
in the background, perform this function beforehand to initialize the logical drive.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Click the logical drive to initialize in the [Virtual Drives] view in the main window.
3
Select "Slow" or "SlowInit" in "Operations" and click [Go].
A confirmation window appears.
4
Click [Yes].
The initialization of the logical drive starts.
` Clicking [No] allows you to return to the previous window.
` During initialization, you can check the progress by clicking [Initialization Progress] or [VD
Progress Info] in the lower part of the window. For more details, see "2.2.3 Checking Progress
of Background Task" (Jpg.58).
5
When the initialization is finished, click [HOME] or
window.
86
to return to the main
MegaRAID SAS User's Guide
2.5.2 Fast Initialization of Logical Drive
To fast initialize logical drives, perform the following procedure:
` For an overview of the fast initialization function, see "„ Fast initialization" (Jpg.30).
` When background initialization is in progress, fast initialization cannot be performed.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Click the logical drive to fast initialize in the [Virtual Drives] view in the main
window.
3
Select "Fast" or "FastInit" in "Operations" and click [Go].
A final confirmation window appears.
4
Click [Yes].
The fast initialization of the logical drive starts.
` Clicking [No] allows you to return to the previous window.
5
When the initialization is finished, click [HOME] or
to return to the main
window.
87
Chapter 2 Array Configuration and Management [WebBIOS]
2.5.3 Make Data Consistent of Logical Drive
To make data consistency of a logical drive, perform the following procedure:
` For an overview of the Make Data Consistent function, see "1.3.4 Make Data Consistent" (Jpg.32).
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Make sure that the [Virtual Drives] view is shown.
If the [Configured Drives] view is shown, select [Virtual View] in the main menu to switch to the
[Virtual Drives] view.
3
Click the logical drive whose consistency is to be checked in the [Virtual Drives]
view.
4
Select "CC" in "Operations" and click [Go].
The Make Data Consistent for the logical drive starts.
` During the Make Data Consistent, you to check the progress by clicking [Check Consistency
Progress] or [VD Progress Info] in the lower part of the window. For more details, see "2.2.3
Checking Progress of Background Task" (Jpg.58).
5
When the Make Data Consistent is finished, click [HOME] or
the main window.
88
to return to
MegaRAID SAS User's Guide
2.5.4 Expanding the Capacity of Logical Drives
Perform this procedure to expand the capacity and change the RAID level for an existing logical drive.
` There are certain conditions to note and precautions to take for capacity expansion. Read "1.3.5
Capacity Expansion" (Jpg.33) carefully before expanding the capacity.
„ Operations before capacity expansion
Before expanding the capacity, perform the following preparatory procedures:
1
Back up the data to prepare for unexpected problems.
2
Perform a Make Data Consistent (Jpg.88) on the logical drive where the
capacity is to be expanded and make sure that the check terminates normally.
` If the Make Data Consistent is not completed successfully, do not expand the capacity of the
logical drive.
3
Install the hard disk to be added to the server.
Install it as a hard disk under this array controller.
„ Procedures to expand capacity
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Make sure that the [Virtual Drives] view is shown.
If the [Configured Drives] view is shown, select [Virtual View] in the main menu to switch to the
[Virtual Drives] view.
89
Chapter 2 Array Configuration and Management [WebBIOS]
3
Click the logical drive whose capacity is to be expanded in the [Virtual Drives]
view.
The logical drive details window appears.
4
Configure the settings for capacity expansion:
1. Select an option for
capacity expansion.
2. Select the RAID level.
3. Select the hard disk to be
added.
4. Confirm the above settings
and click here.
1. Select the options for capacity expansion.
To change the RAID level only, select [Migration only]. To expand capacity by changing
the RAID level and adding a hard disk, select [Migration with addition].
` Do not select [Remove physical drive].
2. Select the RAID level after capacity expansion.
90
MegaRAID SAS User's Guide
3. Select the hard disk to add for capacity expansion.
If [Migration only] is selected for the capacity expansion option, this operation is not
needed.
` Multiple hard disks can be selected at a time by holding down the [Ctrl] key.
` Depending on the number of additional hard disks and the RAID level after capacity expansion,
only the RAID level may be changed without expanding the capacity. For example, when converting a RAID 0 logical drive into a RAID 5 logical drive by adding a hard disk, the capacity will
not be expanded, because the added capacity of one drive is used for the RAID 5 parity data
capacity.
5
Click [Go].
A confirmation window appears.
6
Click [Yes].
[Reconstruction Progress] or [VD Progress Info] appears and the capacity expansion process
starts.
Wait for a while until the process is finished.
` During capacity expansion, you can check the progress by clicking [Reconstruction Progress]
or [VD Progress Info] in the lower part of the window. For details, see "2.2.3 Checking
Progress of Background Task" (Jpg.58).
` If the message "Unacceptable Reconstruction parameter" appears, the combination of the
RAID level after capacity expansion and the added hard disk may be inappropriate.
` If the message "Failed to start operation on Logical Drive" appears, a background task may be
under execution. Wait until the background task operations are finished before performing the
capacity expansion.
` If the RAID level of the logical drive after the expansion has data redundancy (that is RAID 1,
RAID 5 or RAID 6), background initialization will be performed after the capacity expansion is
completed.
` While capacity expansion is in progress, do not turn off, reset or restart the server. Doing so
may cause loss of data on the target logical drive.
` If the server is turned off during the capacity expansion process, access to the hard disk is
resumed automatically after the server restarts. In this case, wait until the access lamp on the
hard disk turns off, ensure that no access is made to the hard disk, create an array configuration again and then restore the data backed up before the task.
7
When completed, click [HOME] or
to return to the main window.
91
Chapter 2 Array Configuration and Management [WebBIOS]
2.5.5 Deleting Logical Drive
When all the logical drives in a disk group are deleted, the hard disks in that disk group are restored to
unused state.
` Delete logical drives in descending order logical drive ID.
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Make sure that the [Virtual Drives] view is shown.
If the [Configured Drives] view appears, select [Logical View] in the main menu to switch to the
[Virtual Drives] view.
3
92
Click the last logical drive (at the bottom) in the [Virtual Drives] view.
MegaRAID SAS User's Guide
4
Select "Del" in "Operations" and click [Go].
1. Click here to
select
2. Click
A confirmation window appears.
5
Click [Yes].
The logical drive is deleted.
6
Click [HOME] or
to return to the main window.
` When all the logical drives in a disk group are deleted, the hard disks in that disk group are restored to
"UNCONF GOOD" state.
93
Chapter 2 Array Configuration and Management [WebBIOS]
2.6 Rebuilding Hard Disk
To execute a manual rebuild, follow the procedure below.
` Usually, rebuild is executed automatically after replacing a hard disk. For details on hard disk
replacement and automatic rebuild, see "Chapter 6 Replacing Hard Disk" (Jpg.243).
1
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
2
Select the hard disk to rebuild (in "FAILED" or "OFFLINE" status) in the
[Physical Drives] view of the main window.
The detailed information window for the selected hard disk appears. Regarding the detailed
information window for hard disks, see "2.2.1 Checking Hard Disk Status" (Jpg.51).
3
Select [Rebuild Drive] in the function area at the bottom of the window, and click
[Go].
The hard disk status changes to "REBUILD" and the rebuild starts. Wait for a while until the
rebuild is completed.
` The rebuild is completed when the progress bar for the rebuild reaches its end and the hard
disk status changes to "ONLINE".
` If the server restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next.
4
When the rebuild is completed, click [HOME] or
window.
94
to return to the main
MegaRAID SAS User's Guide
2.7 Reusing Hard Disk
This section explains how to reuse a hard disk that has been connected to this array
controller in another system.
2.7.1 Cautions When Reusing Hard Disk
Before you can reuse a hard disk that has been connected to this array controller in another system, the
following information must be deleted from the hard disk.
• Disk Array Configuration Information
• OS Partition Table
If a hard disk with this information remaining is used in another system, it may cause unexpected
behavior in the system and problems such as loss of existing data. Delete the configuration information,
etc. completely from the hard disk before reusing the hard disk.
2.7.2 Clearing Information from Hard Disk
To reuse a hard disk, perform the following procedure to delete all the information from the hard disk.
` This procedure should be performed in the old system before connecting the hard disk to the new
system.
` This procedure deletes the entire disk array configuration in the actual array controller.
1
If there is a disk array configuration on the hard disk, delete the disk array
configuration, referring to "2.3.2 Deleting Disk Array Configuration" (Jpg.82).
After the disk array configuration is deleted, all the hard disks are displayed as being in
"UNCONF GOOD" state. If there is a hard disk in "UNCONF BAD" state, it means that that hard
disk is defective and cannot be used.
2
Initialize each hard disk by creating RAID 0.
The procedures are different between RAID 5/6 SAS based on LSI MegaRAID and the other
controllers.
For RAID 5/6 SAS based on LSI MegaRAID
1. Click [Configuration Wizard] on the main menu.
The [Configuration Wizard] window appears.
2. Select [New Configuration] and click [Next].
3. Select [Custom Configuration] and click [Next].
The [DG Definition] window appears.
95
Chapter 2 Array Configuration and Management [WebBIOS]
4. From the [Physical Drives] area, select a single hard disk and click [AddtoArray]
and [Accept DG].
Repeat this for each hard disk in "UNCONF GOOD" state.
5. When the hard disk becomes "Online", click [Next].
The [Span Definition] window appears.
96
MegaRAID SAS User's Guide
6. From the disk group shown in [Array With Free Space], select one and click [Add to
SPAN] and then [Next].
The [VD Definition] window appears.
7. With the logical drive setting default, click [Accept].
Logical drives will be created.
8. Click [Back] to return to the [Span Definition] window. Repeat the step 6 and 7 to
every disk group created.
9. After creating a logical drive to every disk group created, click [Next] on the [VD
Definition] window.
The "Save this Configuration?" message appears.
10. Click [Yes].
The "All data on the new Virtual Disks will be lost. Want to Initialize?" message appears.
11. Click [No].
` Be sure to click [No] to delete all the data here. Clicking [Yes] will start fast initialization.
12. Click [HOME] to return to the main window.
For MegaRAID SAS 300-8E ROMB / MegaRAID SAS 8300XLP / MegaRAID SAS
8408E / MegaRAID SAS 8344ELP
1. Click [Configuration Wizard] on the main menu.
The [Configuration Wizard] window appears.
2. Select [New Configuration] and click [Next].
3. Select [Custom Configuration] and click [Next].
The [DG Definition] window appears.
97
Chapter 2 Array Configuration and Management [WebBIOS]
4. From the [Physical Drives] area, select a single hard disk and click [Accept DG].
Repeat this for each hard disk in "UNCONF GOOD" state.
5. When the hard disk becomes "ONLINE", click [Next].
The [VD Definition] window appears.
98
MegaRAID SAS User's Guide
6. Select a disk group from the [Configuration] area, and create a logical drive with the
following settings:
table: Logical drive settings when deleting a hard disk
Item
RAID Level
Default value
RAID 0
Remarks
Same as the default value
Stripe Size
64KB
Same as the default value
Access Policy
RW
Same as the default value
Read Policy
Normal
Same as the default value
Write Policy
WThru
Same as the default value
IO Policy
Direct
Same as the default value
Disk Cache Policy
Disable
Same as the default value
Disable BGI
No
Same as the default value
Select Size
Maximum
Specifies the maximum capacity of the logical drive.
7. Perform the step 6 for each disk group.
When the settings for all the logical drives are complete, the [Preview] window appears.
8. Click [Accept].
The "Save this Configuration?" message appears.
9. Click [Yes].
The "All data on the new Virtual Disks will be lost. Want to Initialize?" message appears.
10. Click [No].
` Be sure to click [No] to delete all the data here. Clicking [Yes] will start fast initialization.
11. Click [HOME] or
to return to the main window.
99
Chapter 2 Array Configuration and Management [WebBIOS]
3
Initialize all the logical drives created.
1. Select [Virtual Disks] in the main window.
The [Virtual Disks] window appears.
2. Select all the displayed logical drives while pressing the [Ctrl] key.
3. Select [Slow Initialize] and click [Go].
4. When the following confirmation window appears, click [Yes].
The initialization of the logical drive starts. Wait for a while.
5. When the initialization is finished, click [HOME] or
to return to the main
window.
4
Delete the disk array configuration created in step 2.
J"2.3.2 Deleting Disk Array Configuration" (pg.82)
This completes the procedure for wiping the data from the hard disk. The hard disk can now be reused in
other systems.
100
Chapter 3
Preparations
This chapter explains how to update the device
drivers and apply hotfix.
3.1 Updating Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.2 Applying Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
101
Chapter 3 Preparations
3.1 Updating Device Driver
This section explains how to update device drivers installed in the server.
The driver update operation varies depending on the OS.
Before the update, create driver disks by using the "Array Controller Document &
Tool CD".
` Even when the OS is newly installed in the server, the drivers need to be updated when those included
on the "Array Controller Document & Tool CD" are the latest.
For the latest information on the software supplied with the array controller such as "Array Controller
Document & Tool CD", refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).
3.1.1 Creating Driver Disk
Before updating the device drivers, create driver disks from the "Array Controller Document &
Tool CD" by following procedure below.
1
Prepare formatted floppy disks.
2
Insert the "Array Controller Document & Tool CD" into a CD/DVD drive.
3
Copy the necessary drivers for the OS from the following folder on the CDROM to the floppy disks.
Label the floppy disks with the floppy disk names in the following table.
table: Driver disks
OS
Folder name
Floppy disk name
Windows 2000 Server
\Drivers\Mega-SAS\W2K
MegaRAID SAS Windows 2000
Drivers Disk
Windows Server 2003
\Drivers\Mega-SAS\W2K3
MegaRAID SAS Windows Server
2003 Drivers Disk
Windows Server 2003 x64
\Drivers\Mega-SAS\W2K3x64
MegaRAID SAS Windows Server
2003 for x64 Edition Drivers Disk
` For the version of the device drivers, see ReadmeEN.html on the "Array Controller Document & Tool
CD".
102
MegaRAID SAS User's Guide
3.1.2 Updating Driver (Windows Server 2003)
1
Log on to Windows with Administrator privileges.
2
Exit all the software before updating.
3
Execute [System] from the [Control Panel].
4
Select the [Hardware] tab and click [Device Manager].
5
Double-click [SCSI and RAID Controller].
The SCSI adapter list appears.
6
Double-click your controller from the following list:
• LSI Logic MegaRAID SAS PCI Express ROMB
• LSI Logic MegaRAID SAS 8300XLP RAID Controller
• LSI Logic MegaRAID SAS 8408E RAID Controller
• LSI Logic MegaRAID SAS 8344ELP RAID Controller
• RAID 5/6 SAS based on LSI MegaRAID
The [Properties] window appears.
7
Select the [Driver] tab and click [Update Driver].
The "Hardware Update Wizard" window appears.
8
Select [No, not this time] and click [Next].
9
Select [Install from a list or specific location] and click [Next].
10
Select [Don't search. I will choose the driver to install.] and click [Next].
11
Insert the following floppy disk in the floppy disk drive and click [Have Disk].
• For Windows Server 2003
"MegaRAID SAS Windows Server 2003 Drivers Disk"
• For Windows Server 2003 x64
"MegaRAID SAS Windows Server 2003 for x64 Edition Drivers Disk"
12
Type "A:\" in [Copy manufacturer's file from] and click [OK].
13
Select the same model as what you specified in the step 6 from the model field
and click [Next].
The files are copied.
14
When file copying is finished, click [Done] and close the [Hardware Update
Wizard] window.
103
Chapter 3 Preparations
15
Click [Close] to close the [Properties] window.
` If the [Change System Settings] window appears, click [No].
16
If more than one array controllers are installed, update all the device drivers.
Repeat the steps 6 to 15 until all device drivers are updated.
17
Restart the system when all the device drivers are updated.
` To confirm all the device drivers are correctly read, check that a controller from the following list
appears in [SCSI and RAID controller] of the Device Manager. (One of the controllers below appears
depending on the type of your controller.)
• LSI Logic MegaRAID SAS PCI Express ROMB
• LSI Logic MegaRAID SAS 8300XLP RAID Controller
• LSI Logic MegaRAID SAS 8408E RAID Controller
• LSI Logic MegaRAID SAS 8344ELP RAID Controller
• RAID 5/6 SAS based on LSI MegaRAID
Also, to check the version of the device driver currently read, double-click a controller above, select the
[Driver] tab and see the version information.
3.1.3 Updating Driver (Windows 2000 Server)
1
Log on to Windows with Administrator privileges.
2
Exit all the software before updating.
3
Select [System] from the [Control Panel].
4
Select the [Hardware] tab and click [Device Manager].
5
Double-click [SCSI and RAID Controller].
The SCSI adapter list appears.
6
Double-click your controller from the following list.
• LSI Logic MegaRAID SAS PCI Express ROMB
• LSI Logic MegaRAID SAS 8300XLP RAID Controller
• LSI Logic MegaRAID SAS 8408E RAID Controller
The [Properties] window appears.
7
Select the [Driver] tab and click [Update Driver].
The [Device Driver Upgrade Wizard] window appears.
8
104
Click [Next].
MegaRAID SAS User's Guide
9
Select [Display known drivers for this device and select a driver from the list.]
and click [Next].
10
Click [Have Disk] and insert the "MegaRAID SAS Windows 2000 Drivers Disk"
in the floppy disk drive.
11
Type "A:\" in [Copy manufacturer's file from] and click [OK].
12
Select the same model name as what you specified in the step 6 from the
model field and click [Next].
The device driver installation starts.
13
When the installation is finished, click [Done] and close the [Device Driver
Update Wizard] window.
14
Click [Close] to close the [Properties] window.
` If the [Change System Settings] window appears, click [No].
15
If more than one array controllers are installed, update all the device drivers.
Repeat the steps 6 to 14 until all device drivers are updated.
16
Restart the system when all device drivers are updated.
` To confirm all the device drivers are correctly read, check that a controller from the following list
appears in [SCSI and RAID controller] of the Device Manager. (One of the following controllers
appears as the controller name depending on your array controller.)
• LSI Logic MegaRAID SAS PCI Express ROMB
• LSI Logic MegaRAID SAS 8300XLP RAID Controller
• LSI Logic MegaRAID SAS 8408E RAID Controller
Also, to check the version of the device driver that is being read, double-click a controller name above,
select the [Driver] tab and see the version information.
105
Chapter 3 Preparations
3.2 Applying Hotfix
In order to use this array controller in a Windows environment, hotfix needs to be
applied.
` For hotfix, use "PRIMERGY Startup Disc" ( or "ServerStart Disc1 CD-ROM" depending on the server)
supplied with the server. Make sure to apply hotfix when using this array controller with a newly
installed OS in a Windows environment.
„ Application procedure
1
Log on to Windows with Administrator privileges.
2
Close all the software applications.
3
Insert "PRIMERGY Startup Disc" ( or ServerStart Disc1 CD-ROM depending on
the server) into the CD/DVD drive.
4
Run the following program to apply hotfix.
• For Windows 2000 Server
[CD/DVD drive]:\HOTFIX\W2K\ENU\Windows2000-KB904374-x86-ENU.EXE
• For Windows Server 2003 Service Pack 1
[CD/DVD drive]:\HOTFIX\W2K3\WindowsServer2003-KB916048-x86-ENU.exe
• For Windows Server 2003 ×64 Service Pack 1
[CD/DVD drive]:\HOTFIX\W2K3x64\WindowsServer2003.WindowsXP-KB916048x64-ENU.exe
106
Chapter 4
Array Configuration and
Management
[ServerView RAID]
This chapter contains an overview of and
product requirements for ServerView RAID
Manager, and describes how to install and use
the program.
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
Overview of and Requirements for ServerView RAID . . . .
Installing ServerView RAID [Windows] . . . . . . . . . . . . . . .
Installing HDD Check Scheduler [Windows] . . . . . . . . . . .
Installing Battery Recalibration Scheduler [Windows] . . . .
Starting and Exiting ServerView RAID Manager . . . . . . . .
ServerView RAID Manager Window Layout . . . . . . . . . . .
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating RAID Configuration . . . . . . . . . . . . . . . . . . . . .
Checking Each Status [ServerView RAID Manager] . . . . .
108
114
117
121
125
129
139
149
164
107
Chapter 4 Array Configuration and Management [ServerView RAID]
4.1 Overview of and Requirements
for ServerView RAID
This section explains ServerView RAID.
ServerView RAID is used to monitor, manage, maintain, and configure array
controllers and the hard disks and logical drives that are connected to the array
controllers.
4.1.1 ServerView RAID Overview
This application software runs on the OS to monitor and manage the array controller.
ServerView RAID is an application software that allows you to manage a disk array system connected to
the array controllers (RAID controllers).
Using ServerView RAID, which is a client-server application, you can manage array controllers via a
network as well as in a standalone environment.
ServerView RAID includes the ServerView RAID service and ServerView RAID Manager.
The ServerView RAID service and ServerView RAID Manager use HTTPS to communicate with each
other.
z ServerView RAID Service
Installed on the server, this program operates as an OS service and monitors the operation of the array
controllers.
z ServerView RAID Manager
A graphical user interface that uses a Web browser and Java. You manage and configure array
controllers with ServerView RAID Manager.
ServerView RAID Manager㧔GUI㧕
ServerView RAID Service
(Service)
Array Controller
108
MegaRAID SAS User's Guide
` To ensure stable operation of PRIMERGY, install ServerView RAID (or GAM) when using the array
controller. If ServerView RAID (or GAM) is not installed, failures will not be detected. You will also be
unable to perform maintenance correctly. Make sure to install ServerView RAID (or GAM).
` Install either ServerView RAID or GAM, but do not install both. For information about which to use, see
ReadmeEN.html on the Array Controller Document & Tool CD. If by mistake you have installed GAM
rather than ServerView RAID, you must uninstall GAM and HDD Check Scheduler, and then install
ServerView RAID and HDD Check Scheduler. Do not operate the server with both ServerView RAID
and GAM installed.
` Only start ServerView RAID Manager when management or maintenance of arrays is necessary. From
a security point of view, it is not recommended to run ServerView RAID Manager continuously. If the
accessed server shuts down while you are logged in to ServerView RAID Manager, ServerView RAID
Manager cannot communicate with the ServerView RAID service and cannot respond, making it
impossible to operate ServerView RAID Manager. In this case, close the Web browser in which
ServerView RAID Manager is running.
` ServerView RAID uses SSL to encrypt communication. Since server certification is not supported, you
are responsible for ensuring the reliability of the network server itself.
4.1.2 Requirements for ServerView RAID
An appropriate server environment is required for using ServerView RAID properly.
Make sure that the following requirements are met.
„ ServerView RAID (server requirements)
You must have the following environment to use ServerView RAID.
table: Requirements for ServerView RAID
Category
Description
For Windows
For Linux
Hard disk
150MB or more free space in the
installation partition of the OS
150MB or more free space under /opt
Application
TCP/IP, SNMP service, and ServerView must be installed.
OS
OS supporting servers with this array controller installed
Web browser
Internet Explorer 6 or later
Java
Java™ 2 Runtime Environment Standard Edition V1.5.0_06 or later
Mozilla Firefox 1.0.4 or later
SeaMonkey 1.0.3 or later
` Make sure to install the device drivers and ServerView RAID specified by Fujitsu.
` Make sure to configure the network settings properly. If there is a problem with the network
configuration, you may be unable to monitor the status of arrays by ServerView or events may not be
notified.
` To monitor the array controllers, see the OS event log notified by ServerView (Source: Fujitsu
ServerView Services) or by ServerView RAID, or /var/log/messages (Source: ServerView RAID).
Refer to the events by ServerView instead of ServerView RAID when events are notified from both. For
the list of logs notified by ServerView, see "Appendix A List of ServerView RAID Event Log"
(Jpg.270).
109
Chapter 4 Array Configuration and Management [ServerView RAID]
„ ServerView RAID Manager (when managed from a client PC)
When ServerView RAID Manager is used on a client PC different from the server, the following
environment is required for the client PC.
table: Requirements for ServerView RAID Manager
Category
Description
Network
Network connection with TCP/IP available
Input device
A mouse or other pointing device
Processor
Pentium® 500MHz or higher (1GHz or higher recommended)
Memory
512MB or more (1GB or more recommended)
Monitor
800 × 600 or better resolution (1024 × 768 or more recommended), 256 or more
colors
OS
Windows Server 2003 SP1 or later
Windows XP
Windows 2000 Service Pack 4 or later
Windows 2000 Professional Service Pack 4 or later
Web browser
Internet Explorer 6 or later
Java
Java™ 2 Runtime Environment Standard Edition V1.5.0_06 or later
4.1.3 Access Privileges to ServerView RAID
To use the ServerView RAID functions, you must log in to ServerView RAID Manager.
When you log in, user authentication is performed against your user account registered with the OS. The
available functions depend on the user account. There are two levels of access privileges as shown
below:
„ User privileges
The User privileges are mainly used to see the status of the array controllers, hard disks, and logical
drives. To use the User privileges, log in to ServerView RAID Manager with any of the user names and
passwords registered with the OS. With User privileges, you can see the detailed information, settings,
and status of the RAID subsystems such as the array controllers, hard disks, and logical drives.
However, you cannot change the disk array configuration, rebuild hard disks, or modify the parameters
for the array controllers and ServerView RAID.
` The array cannot be configured with User privileges. We recommend that you log in with User
privileges unless you need to operate the array or modify the settings.
„ Administrator privileges
These privileges are used for management, maintenance, and configuration of the array controllers, hard
disks, and logical drives. To use the Administrator privileges, log in to ServerView RAID Manager as a
user belonging to the "raid-adm" group, the "Administrators" group (for Windows), or "root" group (for
Linux). In addition to the functions available with User privileges, it is possible to use all other functions
including creating/changing disk array configurations, rebuilding hard disks, making data consistency of
logical drives, and changing the hard disk status.
110
MegaRAID SAS User's Guide
` When using ServerView RAID with Administrator privileges, certain operations may cause loss of data
in the array controller. Read this chapter and use ServerView RAID carefully.
` You must create the "raid-adm" group. Make sure to create the group with the name "raid-adm".
4.1.4 Using ServerView RAID in Linux Environment
To use ServerView RAID in a Linux environment, you need to install device drivers for Linux and
ServerView RAID.
For using Linux, see the PRIMERGY page on the Fujitsu website (http://primergy.fujitsu.com/) and
refer to information about Linux.
When using the software in an RHEL5(Intel64), RHEL-AS4(EM64T), or RHEL-ES4(EM64T)
environment
` The Java plug-ins do not work on the servers with the RHEL5(Intel64), RHEL-AS4(EM64T), or RHELES4(EM64T) system. You cannot manage the array controllers with ServerView RAID Manager
running directly on these servers.
If you want to manage the array controllers on servers with the RHEL5(Intel64), RHEL-AS4(EM64T),
or RHEL-ES4(EM64T) system, run ServerView RAID Manager on a Windows server or client PC, and
manage the array controllers remotely.
For the remote management configuration, see "4.1.5 Operations via Network" (Jpg.111).
4.1.5 Operations via Network
In a network environment, arrays on the servers can be monitored and managed from a server or a
Windows client PC connected to the network.
When you manage the disk array on the server with ServerView RAID installed from ServerView RAID
Manager on another server or a client PC, the configuration is as follows:
Windows Server
or
Client PC
Monitoring and setting
the disk array
Notifying
ServerView RAID Event
Server
ServerView RAID
Service
ServerView RAID Manager
Array Controller
111
Chapter 4 Array Configuration and Management [ServerView RAID]
` Each ServerView RAID Manager program can manage only one server. When you manage disk
arrays on multiple servers from a single client PC or server, start one ServerView RAID Manager
program for each server.
` If there is an intervening firewall in the environment, you need to configure the network settings so that
the port used by the ServerView RAID is not blocked.
ServerView RAID uses the TCP port 3173.
„ Interaction with ServerView AlarmService
ServerView RAID can log the events of an array controller in the OS event log on the server using
ServerView AlarmService. When you monitor the disk array remotely, you can also log the events of the
array controllers in the OS event log on the client PC by installing ServerView Console or ServerView
AlarmService on the client PC. When you install ServerView AlarmService on the client PC as well, the
configuration is as follows:
Windows Server
or
Client PC
Windows Server or Linux Server
Monitoring and setting
the disk array
ServerView
AlarmService
ServerView RAID
Manager
OS Event Log
Notifying
ServerView RAID
Event (SNMP Trap)
SNMP Service
Notifying
ServerView RAID
Event (SNMP Trap)
ServerView
AlarmService
OS Event Log
` Make sure to install ServerView on the server.
112
ServerView RAID
Service
Array Controller
MegaRAID SAS User's Guide
4.1.6 When Using Both ServerView RAID and GAM
When using both ServerView RAID and GAM on a network, you can use ServerView RAID Manager
and GAM Client simultaneously on the management client PC or Windows server.
You can use the following configuration:
Server
Management Client PC
or
Windows Server
ServerView RAID
Service
Notifying
㪪㪼㫉㫍㪼㫉㪭㫀㪼㫎㩷㪩㪘㪠㪛
Event
Monitoring and
setting the disk array
GAM Client
Monitoring and
setting the disk array
ServerView RAID Manager
Array Controller
Server
GAM Server
Notifying
GAM Event
Array Controller
If ServerView is installed on the management client PC or Windows server, you can start the
ServerView RAID Manager or GAM Client program for a server managed by ServerView by making
use of ServerView's interaction with the RAID Manager. For details about the RAID Manager
interaction, see "RAID Manager Linking" in the "ServerView User's Guide".
` When you install GAM Client on a Windows server where ServerView RAID is already installed, install
only GAM Client. Do not install GAM Server.
` One GAM Client can manage up to a maximum of 100 GAM Servers.
When managing more than 100 servers at the same time, one Windows server or one client PC to be
used as GAM Client is necessary per 100 servers.
` If multiple versions of the GAM Server coexist, use the version of GAM Client that corresponds to the
latest version of GAM Server, or a later version.
113
Chapter 4 Array Configuration and Management [ServerView RAID]
4.2 Installing ServerView RAID
[Windows]
This section explains how to install ServerView RAID on a Windows server.
` You may or may not overwrite installation on ServerView RAID depending on the version.
• With the version v2.0.x or v2.1.x, overwriting installation cannot be done. Uninstall ServerView RAID
and install the version of ServerView RAID you want to install.
• With the version v2.3.x or later, you can overwrite installation. Just go on installing the later version.
• With all the versions, you can not overwrite installation with the older version. If you need to do that
for some reasons, uninstall ServerView RAID first and then install the version of ServerView RAID
you want to install.
` To record events that occur in the array controllers in the OS event log, make sure to install
ServerView and configure the event log settings. For details, see the "ServerView User's Guide".
4.2.1 How to Install ServerView RAID
Follow the procedure below to install ServerView RAID.
1
Log on to Windows with Administrator privileges.
2
Before installing ServerView RAID, complete the following preparations:
• Make sure that ServerView is installed and working properly.
• Insert the "Array Controller Document & Tool CD" provided with this product into the CD/
DVD drive.
• Exit all application software.
` Exit all application software before starting the installation. In particular, if you install the software while Event Viewer, Services, or Computer Management is running, the installation may
fail.
3
Click [Start] button – [Run...]. Type the following path and click [OK].
[CD/DVD drive]:\RAIDTOOL\SVRAID\Windows\install.bat
The message "Installation of ServerView RAID has started." appears at the command prompt,
and the installation of ServerView RAID begins.
4
When the message "Installation of ServerView RAID has finished." appears at
the command prompt, press the [Enter] key.
The command prompt window closes.
114
MegaRAID SAS User's Guide
5
6
Restart the system.
Once the system is up and running, create and configure a Windows user
account.
User Account for Administrator Privileges
1. Create a user account for the Administrator privileges of ServerView RAID.
2. Create the "raid-adm" group.
3. Configure the user account for the Administrator privileges so that it belongs to the
"raid-adm" group or the Administrators group.
User Account for User Privileges
1. Create a user account for the User privileges of ServerView RAID.
Do not include the user account for the User privileges in the "raid-adm" group.
` When creating the account for ServerView RAID, uncheck the [User must change password at
next logon] checkbox.
Normally, the [Password never expires] checkbox should be checked. Unless the account is
configured as above, you may be unable to log in to ServerView RAID Manager properly,
because the program will consider the user account invalid if the password of the account has
expired or has not been set, without displaying any warning message.
` Create each user account as an OS user account.
` You must create the "raid-adm" group. Make sure to create the group with the name "raidadm".
115
Chapter 4 Array Configuration and Management [ServerView RAID]
4.2.2 How to Uninstall ServerView RAID
Follow the procedure below to uninstall ServerView RAID.
` In general, do not uninstall ServerView RAID except for certain cases such as when you need to
update ServerView RAID.
1
Log on to Windows with Administrator privileges.
` Exit all programs before starting the uninstallation.
If you uninstall the software while Event Viewer, Services, or Computer Management is running, the uninstallation will fail. Make sure to exit all programs.
2
Click [Start] button – [Settings] – [Control Panel].
3
Double-click [Add or Remove Applications] (or [Add or Remove Programs]
depending on the OS).
4
Select [ServerView RAID] from the application list and click [Delete] (or
[Change/Remove] depending on the environment).
The message "Are you sure you want to remove ServerView RAID from the computer?" appears.
5
Click [Yes].
The uninstallation process starts.
6
When the following message appears after the uninstallation, click [Yes].
You must restart your system for the configuration changes made to
ServerView RAID to take effect...
The system restarts.
116
MegaRAID SAS User's Guide
4.3 Installing HDD Check Scheduler
[Windows]
HDD Check Scheduler is a tool to detect or recover media errors on hard disks, by
periodically performing Make Data Consistent of the media. This section explains
how to install HDD Check Scheduler on a Windows server.
` Make sure to install HDD Check Scheduler. Also, make sure to install ServerView RAID before
installing HDD Check Scheduler.
` During the HDD check, the I/O performance for the logical drives decreases to some extent (up to
about 30%). After the installation, set the start time so that the check is performed during non-business
hours, or low-business hours, referring to "4.3.2 Modifying HDD Check Start Time" (Jpg.118).
When you install HDD Check Scheduler, the check is set to start every day at 12:00 by default.
` For an overview of the HDD Scheduler functions, see "1.3.7 HDD Check Scheduler" (Jpg.36).
` HDD Check Scheduler performs Make Data Consistent periodically using the standard OS scheduling
function ("AT" command for Windows, or Cron for Linux).
` We recommend that you perform the HDD check, at least once a week.
` If the server restarts or shuts down during HDD check, the HDD check is resumed from where it was
stopped the next time.
4.3.1 Installation of HDD Check Scheduler
Follow the procedure below to install HDD Check Scheduler.
1
Log on to Windows with Administrator privileges.
2
Before installing HDD Check Scheduler, complete the following preparations:
• Check that ServerView RAID is installed.
• Make sure that ServerView is installed and working properly.
• Insert the "Array Controller Document & Tool CD" provided with this product into the CD/
DVD drive.
• Exit all application software.
` Exit all application software before starting the installation. In particular, if you install the software while Event Viewer, Services, or Computer Management is running, the installation may
fail.
117
Chapter 4 Array Configuration and Management [ServerView RAID]
3
Click [Start] button – [Run...]. Type the following file name and click [OK].
[CD/DVD drive]:\RAIDTOOL\HDDCS\Windows\install.bat
The message "Installing HDD Check Scheduler." appears at the command prompt.
4
When the message "Installation of HDD Check Scheduler has finished."
appears, press the [Enter] key.
The command prompt window closes.
` When you install HDD Check Scheduler for the first time, the HDD check is set to start every day at
12:00 by default.
` If you reinstall and overwrite HDD Check Scheduler, the previously set start time setting will be kept.
4.3.2 Modifying HDD Check Start Time
The start time for the HDD check can be modified using the "AT" command of the OS. To modify the
start time, perform the following procedure.
` We recommend that you perform the HDD check regularly, at least once a week.
1
Log on to Windows with Administrator privileges.
2
Click [Start] button – [All Programs] – [Accessories] – [Command Prompt] to
open the command prompt.
3
Type "AT" and press the [Enter] key.
4
Write down the [ID] value for the row with the following value in the [Command
Line] column:
For Windows Server 2003 x64
C:\Program Files (x86)\Fujitsu Siemens\RAID\FJutils\HDDchk.bat
For Windows Server 2003/Windows 2000 Server
C:\Program Files\Fujitsu Siemens\RAID\FJutils\HDDchk.bat
Example: If the "AT" command output is as follows, the ID is 13.
C:\Documents and Settings\Administrator>at
Status ID Day
Time
Command Line
---------------------------------------------------------------------1 Each M F
10:00 AM
"C:\Program Files (x86)\Fujitsu
\F5FBFE01\ServerView Services\WebServer\ClearMyLogs.exe"
13 Each M T
12:00 PM
"C:\Program Files (x86)\Fujitsu
Siemens\RAID\FJutils\HDDchk.bat"
118
MegaRAID SAS User's Guide
5
Delete the currently registered HDD check schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 13 /delete
6
Register a new schedule. Using the "AT" command, register the following
command line together with the time of execution.
For Windows Server 2003 x64
C:\Program Files (x86)\Fujitsu Siemens\RAID\FJutils\HDDchk.bat
For Windows Server 2003/Windows 2000 Server
C:\Program Files\Fujitsu Siemens\RAID\FJutils\HDDchk.bat
To specify the scheduled execution, enter the following "AT" command.
AT <Start Time> /every:<Day of Week> "Command Line"
• To execute the HDD check every Friday at 18 pm, on Windows Server 2003/Windows 2000
Server
AT 18:00 /every:F "C:\Program Files\Fujitsu Siemens\RAID\
FJutils\HDDchk.bat"
• To execute the HDD check every day at 9 pm, on Windows Server 2003 x64
AT 21:00 /every:M,T,W,Th,F,S,Su "C:\Program Files (x86)\Fujitsu Siemens\RAID\FJutils\HDDchk.bat"
` To specify the day of the week, use the following abbreviations:
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
M
T
W
Th
F
S
Su
` For details on how to use the "AT" command, see Windows Help.
` To see whether the HDD check is properly executed at the specified time, check that the log
entry shown below is recorded in the OS application log at the specified time. If no log entries
shown below are recorded at the specified time, review the settings.
Source
: Fujitsu ServerView Services
Type
: Information
Event ID
: 1
Description: Adapter LSI MegaRAID SAS xx (x): MDC started on
Logical Drive x (Server xxx)
[Note]: Each "×" in the descriptions corresponds to a string of characters or digits, depending
on your operating environment.
119
Chapter 4 Array Configuration and Management [ServerView RAID]
4.3.3 Uninstallation of HDD Check Scheduler
Follow the procedure below to uninstall HDD Check Scheduler:
1
Log on to Windows with Administrator privileges.
2
Click [Start] button – [All Programs] (or [Programs]) – [Accessories] –
[Command Prompt].
The command prompt window opens.
3
4
Type "AT" and press the [Enter] key.
Write down the [ID] value for the row with the following value in the [Command
Line] column:
For Windows Server 2003 x64
C:\Program Files (x86)\Fujitsu Siemens\RAID\FJutils\HDDchk.bat
For Windows Server 2003/Windows 2000 Server
C:\Program Files\Fujitsu Siemens\RAID\FJutils\HDDchk.bat
Example: If the "AT" command output is as follows, the ID is 13.
C:\Documents and Settings\Administrator>at
Status ID Day
Time
Command Line
---------------------------------------------------------------------1 Each M F
10:00 AM
"C:\Program Files (x86)\Fujitsu
\F5FBFE01\ServerView Services\WebServer\ClearMyLogs.exe"
13 Each M T
12:00 PM
"C:\Program Files (x86)\Fujitsu
Siemens\RAID\FJutils\HDDchk.bat"
5
Delete the currently registered HDD check schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 13 /delete
120
MegaRAID SAS User's Guide
4.4 Installing Battery Recalibration
Scheduler [Windows]
Battery Recalibration Scheduler is a tool to periodically perform battery recalibration
for the products shown below. This section explains how to install Battery
Recalibration Scheduler on a Windows server.
• MegaRAID SAS 300-8E ROMB with a battery
• MegaRAID SAS 8408E
• MegaRAID SAS 8344ELP with a battery
• RAUD 5/6 SAS based on LSI MegaRAID with a battery
` See also "1.3.8 Battery Backup Unit (BBU)" (Jpg.36) before using this tool.
` Recalibration takes 12 hours with the server power on. During recalibration, the logical drive in Write
Back mode shifts automatically to Write Through mode for safety. Therefore, see "4.4.2 Changing
Battery Recalibration Start Date and Time" (Jpg.122) to set a start date and time that minimizes the
effect on the business.
` MegaRAID SAS 8300XLP does not require the installation of this tool or periodical recalibration.
` Battery Recalibration Scheduler performs recalibration periodically using the standard OS scheduling
function ("AT" command for Windows, or Cron for Linux).
` We recommend that you perform battery recalibration about once a month or every two months.
` If the server restarts or shuts down during battery recalibration, the battery recalibration is resumed
from where it was stopped the next time.
4.4.1 Installation of Battery Recalibration Scheduler
Follow the procedure below to install Battery Recalibration Scheduler.
1
Log on to Windows with Administrator privileges.
2
Before installing Battery Recalibration Scheduler, complete the following
preparations:
• Check that ServerView RAID is installed.
• Make sure that ServerView is installed and working properly.
• Insert the Array Controller Document & Tool CD provided with this product into the CD/
DVD drive.
• Exit all application software.
121
Chapter 4 Array Configuration and Management [ServerView RAID]
` Exit all application software before starting the installation. In particular, if you install the software while Event Viewer, Services, or Computer Management is running, the installation may
fail.
3
Click [Start] button – [Run...]. Enter the following file name and click [OK].
[CD/DVD drive]:\RAIDTOOL\BATCS\Windows\install.bat
The message "Installing Battery Recalibration Scheduler." appears at the command prompt.
4
When the message "Installation of Battery Recalibration has finished." appears,
press the [Enter] key.
The command prompt window closes.
` When you install Battery Recalibration Scheduler for the first time, the recalibration is set to start the
first day of every month at 11:00 by default.
` If you reinstall and overwrite Battery Recalibration Scheduler, the previously set start date and time
settings will be kept.
4.4.2 Changing Battery Recalibration Start Date and Time
The start date and time for the Battery Recalibration can be modified using the "AT" command of the
operating system. To modify the start date and time, perform the following procedure.
` We recommend that you perform battery recalibration about once a month or every two months.
1
Log on to Windows with Administrator privileges.
2
Click [Start] button – [All Programs] – [Accessories] – [Command Prompt] to
open the command prompt.
3
Type "AT" and press the [Enter] key.
4
Write down the [ID] value for the row with the following value in the [Command
Line] column:
For Windows Server 2003 x64
C:\Program Files (x86)\Fujitsu Siemens\RAID\FJutils\Batrec.bat
122
MegaRAID SAS User's Guide
For Windows Server 2003/Windows 2000 Server
C:\Program Files\Fujitsu Siemens\RAID\FJutils\Batrec.bat
Example: If the "AT" command output is as follows, the ID is 7.
C:\Documents and Settings\Administrator>at
Status ID Day
Time
Command Line
---------------------------------------------------------------------1 Each M F
10:00 AM
"C:\Program Files (x86)\Fujitsu
\F5FBFE01\ServerView Services\WebServer\ClearMyLogs.exe"
6 Each M T
12:00 PM
"C:\Program Files (x86)\Fujitsu
Siemens\RAID\FJutils\HDDchk.bat"
7 Each 1
11:00 PM
"C:\Program Files (x86)\Fujitsu
Siemens\RAID\FJutils\Batrec.bat"
5
Delete the currently registered Battery Recalibration schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 7 /delete
6
Register a new schedule. Using the "AT" command, register the following
command line together with the date and time of execution.
For Windows Server 2003 x64
C:\Program Files (x86)\Fujitsu Siemens\RAID\FJutils\Batrec.bat
For Windows Server 2003/Windows 2000 Server
C:\Program Files\Fujitsu Siemens\RAID\FJutils\Batrec.bat
To specify the scheduled execution, enter the following "AT" command.
AT <Start Time> /every:<Date> "Command Line"
To execute the Battery Recalibration every 15th at 8 am: (For Windows Server 2003/Windows
2000 Server)
AT 18:00 /every:F "C:\Program Files\Fujitsu Siemens\RAID\
FJutils\HDDchk.bat"
` For details on how to use the "AT" command, see Windows Help.
` To confirm whether battery recalibration is configured correctly, enter "AT" at the command
prompt and check the displayed result.
Check that the date, time, and the command line set in step 6 are correct.
123
Chapter 4 Array Configuration and Management [ServerView RAID]
4.4.3 Uninstallation of Battery Recalibration Scheduler
Follow the procedure below to uninstall Battery Recalibration Scheduler:
1
Log on to Windows with Administrator privileges.
2
Click [Start] button – [All Programs] (or [Programs]) – [Accessories] –
[Command Prompt].
A command prompt window opens.
3
4
Type "AT" and press the [Enter] key.
Write down the [ID] value for the row with the following value in the [Command
Line] column:
For Windows Server 2003 x64
C:\Program Files (x86)\Fujitsu Siemens\RAID\FJutils\Batrec.bat
For Windows Server 2003/Windows 2000 Server
C:\Program Files\Fujitsu Siemens\RAID\FJutils\Batrec.bat
Example: If the "AT" command output is as follows, the ID is 7.
C:\Documents and Settings\Administrator>at
Status ID Day
Time
Command Line
---------------------------------------------------------------------1 Each M F
10:00 AM
"C:\Program Files (x86)\Fujitsu
\F5FBFE01\ServerView Services\WebServer\ClearMyLogs.exe"
6 Each M T
12:00 PM
"C:\Program Files (x86)\Fujitsu
Siemens\RAID\FJutils\HDDchk.bat"
7 Each 1
11:00 PM
Siemens\RAID\FJutils\Batrec.bat"
5
Delete the currently registered Battery Recalibration schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 7 /delete
124
"C:\Program Files (x86)\Fujitsu
MegaRAID SAS User's Guide
4.5 Starting and Exiting ServerView
RAID Manager
This section explains how to start and exit ServerView RAID Manager.
4.5.1 Preparations and Precautions for using ServerView
RAID Manager
You need to configure the Web browser settings before using ServerView RAID Manager. Also, note the
following precautions:
z General precautions
• ServerView RAID Manager use a Java plug-in. You must install Java on the server or client PC on
which you use ServerView RAID Manager. If Java is not already installed, see "Installing Java™ 2
Runtime Environment Standard Edition" under "Chapter 2 Installation" in "ServerView User's
Guide" on PRIMERGY Startup Disc, and install Java.
• On servers with the RHEL-AS4(EM64T) or RHEL-ES4(EM64T) system, Java plug-ins do not work.
Therefore, when you manage the array controllers in an RHEL-AS4(EM64T) or RHELES4(EM64T) environment, you need a separate Windows server or client PC to run ServerView
RAID Manager.
• When you use ServerView RAID Manager on the server, do not use proxy servers for the IP address
and localhost.
• Do not use the [Back], [Forward], and [Refresh] buttons in the Web browser.
z When using internet explorer as your Web browser
• Enable SSL.
Select [Tools] – [Internet Options] – [Advanced] – [Security], and enable SSL 3.0 and TSL 1.0.
• Start the Web browser and add the zone setting of Web site as follows:
1. In Internet Explorer, select [Tools] – [Internet Options].
2. Click the [Security] tab and select [Intranet] (or [Local intranet] in Internet Explorer 7) or
[Trusted sites].
3. Click [Sites] (or [Advanced] in Windows 2000) and add the following URL of the server where
you installed ServerView RAID: https://<the name or IP address of the server>.
4. Click [Close].
5. Click [Custom Level].
6. Set [Enable] for [Run ActiveX controls and plug-ins].
125
Chapter 4 Array Configuration and Management [ServerView RAID]
z When using Mozilla Firefox / SeaMonkey as your Web browser
Select [Edit] – [Configuration], and enable the following items in the configuration window:
• "SSL 2.0" and "SSL 3.0"
• "Enable Java"
4.5.2 Starting and Logging in ServerView RAID Manager
You can start ServerView RAID Manager in several ways as follows:
z Starting from the [Start] button
Start ServerView RAID Manager from the [Start] button.
This method can only be used on the Windows server on which ServerView RAID is installed.
z Starting from ServerView
Start ServerView RAID Manager by utilizing the RAID Manager linking function of ServerView.
For information about how to start ServerView RAID Manager from ServerView, see "RAID Manager
Linking" in the "ServerView User's Guide" on PRIMERGY Startup Disc.
z Starting by specifying a server name or IP address directly
Start ServerView RAID Manager by specifying the host name or IP address of the server directly. Using
this method, you can manage the array controllers on the server from a remote client PC.
1
Start ServerView RAID Manager.
Starting from the [Start] button
1. Click [Start] button – [All Programs] (or [Program]) – [Fujitsu Siemens] –
[ServerView RAID Manager Start].
Starting by Specifying the Server Name or IP Address Directly
1. Start the Web browser.
2. Type the following URL and press the [Enter] key.
https://<the name or the IP address of the server>:3173/
` If a "Security Alert" message appears, click [Yes] to continue.
` If the following message appears on the startup of Java, click [Yes] to continue.
•"The web site's certificate is invalid. Do you want to continue?"
•"The web site's certificate cannot be verified. Do you want to continue?"
` If the message "The name of the site does not match the name on the certificate. Do you want
to run the application?" appears on the startup of Java, click [Run] to continue.
126
MegaRAID SAS User's Guide
When ServerView RAID Manager is started, the login window appears.
` If you leave the Java startup popup window open for a long time while starting ServerView
RAID Manager, the following window may appear and ServerView RAID Manager cannot be
started. In this case, close the Web browser, and then start ServerView RAID Manager again.
2
Type the user name in [Username].
• When logging in with Administrator privileges
Type the user name that belongs to the "raid-adm", "Administrators" (for Windows) or "root"
(for Linux) group.
• When logging in with User privileges
Type a user name that does not belong to the "raid-adm", "Administrators" (for Windows) or
"root" (for Linux) group.
3
Type a password in [Password].
127
Chapter 4 Array Configuration and Management [ServerView RAID]
4
Click [Login].
The main window of ServerView RAID Manager appears.
` If you type the wrong password for logging in, you may be unable to enter the password again.
In this case, click [Username:], and then enter the user account and the correct password.
` In ServerView RAID Manager, the available functions are limited by the access privileges. For
details about access privileges, see "4.1.3 Access Privileges to ServerView RAID" (Jpg.110).
` Do not change the status of the language selection button in the login window.
Leave it as
.
` The following event recorded after login may indicate that the operation to finish ServerView
RAID Manager last time was not appropriate. This, however, does not interrupt any of your
operation at the next login.
ID: 10172
Event: User xxxxx (amRUI) logged out
4.5.3 Exiting ServerView RAID Manager
This section explains how to exit ServerView RAID Manager.
1
In the ServerView RAID Manager menu bar, click [File] – [Exit].
The login window appears.
2
128
Exit the Web browser.
MegaRAID SAS User's Guide
4.6 ServerView RAID Manager
Window Layout
The following provides a description of the windows, buttons, and menu items
displayed when using ServerView RAID Manager.
4.6.1 Startup Window Layout and Functions
When ServerView RAID Manager is started, the following main window appears.
Object
Window
Menu Bar
Toolbar
Tree View
Event
Window
„ Object window
The window displays information about the object (device) selected in the tree view. Use the tabs at the
top of the object window to switch the information displayed.
• [General] Tab
This tab displays information about the object, such as the IP address, the OS, and the capacities of
the hard disk drives and logical drives.
• [Settings] Tab
This tab displays the settings of the object. It also allows you to modify the settings of the object.
• [Layout] Tab
This tab allows you to see the configuration of the object.
129
Chapter 4 Array Configuration and Management [ServerView RAID]
• [Background activities] Tab
This tab allows you to see the status of the background tasks currently running for the object.
` The information displayed in each tab of the object window varies with the selected object. The
[Background activities] tab is not displayed when no background tasks are running.
„ Menu bar
ServerView RAID Manager provides menus for performing various functions.
For details on the ServerView RAID Manager menus, see "4.6.2 Menu Layout and Function"
(Jpg.131).
„ Toolbar
The toolbar contains the following buttons:
•
(Back/Forward)
These buttons allow you to go back/forward in the object selection history for the tree view.
•
(Change Access Mode)
This button allows you to switch the access mode of the object. Access modes represent the operation
privileges for ServerView RAID Manager. The following access modes are available:
• Read only access
You can only see the information.
• Write access
You can make any modifications.
When you want to operate the disk array or modify the settings for the controller and logical
drives, you must set the Write access mode.
` When you log in to ServerView RAID with Administrator privileges, you can use the Write
access mode. When you log in with User privileges, you can only use the Read only access
mode.
J"4.5.2 Starting and Logging in ServerView RAID Manager" (pg.126)
` When you log in with Administrator privileges in the Read only access mode and perform any
modification such as modifying the settings, the following popup window appears. Click [Yes]
to automatically switch the access mode to the Write access mode.
„ Tree view
The tree view displays all the objects related to the array controller as icons in a tree.
For details, see "4.6.3 Layout of the Tree View" (Jpg.134).
130
MegaRAID SAS User's Guide
„ Event window
ServerView RAID monitors the operation of the array controllers and hard disks connected to the
controllers.
When any behavior that is considered as an event (for example, a failure of a hard disk or an allocation
of a spare disk) occurs, ServerView RAID Manager is notified of it and displays it in the event window.
The following information appears.
table: Event window
Event
Severity
Description
Priority level of the event. The following icons are used:
Information
Warning
Error
Date
Date and time when the event occurred.
Source
Object (device) where the event occurred.
ID
ID of the event
Event
Event description
` ServerView RAID Manager displays only the last 100 events in the event window. You can not refer to
the old events because events before the last 100 are overwritten with the newer events.
To refer to the old events that you can not view on the Server RAID Manager event window can be
obtained in Windows event viewer or in /var/log/messages of Linux.
4.6.2 Menu Layout and Function
This section explains the layout and functions of ServerView RAID Manager menu items.
„ [File] menu
table: [File] menu
Menu
Exit
Function
Select this item to close the current session and return to the login window.
„ [Actions] menu
` The items in the [Actions] menu vary with the object selected in the tree view and the status of the
object. Note that grayed out menu items are disabled.
` The [Actions] menu is the same as the right-click menu for the object selected in the tree view.
131
Chapter 4 Array Configuration and Management [ServerView RAID]
z When an array controller is selected
table: [Actions] menu (when an array controller is selected)
Menu
Function
Scan configuration
Select this item to redetect all devices connected to the array controller.
Create logical drive
Select this item to set a disk array configuration. This function enables you to
define disk groups and logical drives.
For details, see "4.8.1 Creating Disk Array Configuration (Create Logical Drive)"
(Jpg.149).
Delete all logical drives
Select this item to delete all the logical drives connected to the array controller.
Delete last logical drive
Select this item to delete the last created logical drive (i.e. the logical drive with
the highest drive number).
Alarm on / Alarm off
Not supported. Do not use them.
Start Patrol Read
Cancel Patrol Read
Clear configuration
Select this item to clear all the disk array configurations of the array controller.
For details, see "4.8.6 Deleting Disk Array Configuration Information"
(Jpg.160).
Manage foreign
configuration
Not supported. Do not use it.
z When a hard disk is selected
table: [Actions] menu (when a hard disk is selected)
Menu
Locate device
Function
Turns on the hard disk failure LED to indicate the disk location.
Stop location
Turns off the hard disk failure LED that was turned on with [Locate Device].
Make online
Forces the status of the hard disk to online (operational).
Note:
` Do not use this function unless you are instructed to do so, for example
during maintenance. This operation may cause loss of data.
Make offline
Forces the status of the hard disk to offline (failed).
Note:
` Do not use this function unless you are instructed to do so, for example
during preventive replacement of a hard disk or during maintenance.
This operation may cause loss of data.
Make ready
Changes the status of the failed hard disk to Available status.
Note:
` Do not use this function unless you are instructed to do so, for example
during maintenance.
Replace missing Disk
Reassigns a hard disk to the disk group.
Note:
` Do not use this function unless you are instructed to do so, for example
during maintenance.
Start rebuild
Cancel rebuild
Starts rebuild ([Rebuild]) for the selected hard disk.
Stops the rebuild running for the selected hard disk.
Note:
` Do not use this function unless you are instructed to do so, for example
during maintenance.
132
MegaRAID SAS User's Guide
table: [Actions] menu (when a hard disk is selected)
Menu
Manage hot spare
Function
Sets or manage spare disks. For how to operate, see "4.8.4 Setting and Releasing
Spare Disk" (Jpg.157)
z When a logical drive is selected
table: [Actions] menu (when a logical drive is selected)
Menu
Function
Migrate logical drive
Increases the capacity of the logical drive.
Delete logical drive
Not supported. Do not use it.
Locate logical drive
Turns on the failure LEDs of the hard disks that make up the selected logical drive
to indicate their locations.
Stop location
Turns off the hard disk failure LEDs that were turned on with [Locate Logical
Drive].
Start MDC
Starts the Make Data Consistent ([Make Data Consist]) for the selected logical
drive.
Cancel MDC
Stops the Make Data Consistent running for the selected logical drive.
Cancel BGI
Stops the initialization process running in the background.
Even if the background initialization process is stopped, it will automatically be
restarted after a certain period of time.
Start rebuild
Starts rebuild ([Rebuild]) for the selected logical drive.
Cancel rebuild
Stops the rebuild running for the selected logical drive.
Note:
` Do not use this function unless you are instructed to do so, for example
during maintenance.
Start initialization
Not supported. Do not use it.
Note:
` If you use this function, the data on the logical drive will be deleted.
Please be careful.
Cancel initialization
Not supported. Do not use it.
z When a battery backup unit is selected
table: [Actions] menu (when a battery backup unit is selected)
Menu
Recalibration
Function
Starts the battery recalibration.
Note:
` Note that a logical drive set to Write Back mode operates in Write
Through mode during battery recalibration.
133
Chapter 4 Array Configuration and Management [ServerView RAID]
z When a File Log is selected
table: [Actions] menu (when a File Log is selected)
Menu
Clear log
Function
Deletes the event log file.
Note:
` Do not use it. Event log files are used when investigating failures.
If you delete event log files, it may become difficult to investigate when
failures occur.
„ [Help] menu
table: [Help] menu
Menu
Function
Info about ServerView RAID
Displays the version information of ServerView RAID.
Contents and index
Not supported.
4.6.3 Layout of the Tree View
This section explains the icons in the tree view shown at the left of the main ServerView RAID Manager
window.
In the tree view, you can see the status of the hard disks and logical drives.
Servers
Array Controllers
Battery Backup Units
Hard Disks
Ports
Logical Drives
File Log
System Log
Plug-in
134
MegaRAID SAS User's Guide
The screen will be as shown below when SES (SCSI Enclosure Service) device and/or SAS Expander
are connected to the array controller.
Array Controllers
Ports
SAS Expander
Hard Disks
SES Devices
Fan Units under SES devices
Power Units under SES devices
Temperature Sensors under SES devices
z Servers
At the top of the tree, the names of the connected servers are displayed.
z Controllers
The array controllers installed on the server are displayed.
Each controller number is shown in ( ).
z Battery backup units
The battery backup units installed on the array controller are displayed. This only applies to products
with batteries. The status of battery units are not supported in ServerView RAID Manager.
Use the event logs to monitor the batteries.
` The battery backup unit may be displayed with the (
) icon during battery recalibration or battery
charging, but this does not mean a failure.
135
Chapter 4 Array Configuration and Management [ServerView RAID]
z Ports
The ports of the array controller are displayed.
Each port number is shown in ( ).
` A port name does not indicate hard disk types connected, but port types. It always shows "SAS Port".
` When a number of ports are widely linked, the number of ports are consecutively displayed such as
"SAS Port (0-1-2-3)."
z Hard disks
The vendor names and product names of the hard disks connected to the array controller are displayed.
The displayed in a parenthesis is: the device number of a hard disk slot number such as (3), or an
enclosure number and a slot number such as (1:4).
You can also check the present status of each hard disk with icons.
table: Hard disk status icon
Icon
Displayed in
Description
Online (Operational)
A part of the array and functioning properly
White
Unused
(Available)
Unused or available
White
with a "+" mark
Spare Disk
(Global hot spare)
A spare disk
Gray
with an "x" mark
Failure/Offline
(Failed/Offline)
A part of the array, but has failed or is
unreadable/unwritable
White
with an "x" mark
Failure
(Failed)
Not a part of the array, and has failed
White
(dotted frame)
with an "x" mark
Unrecognizable
(Failed (missing))
Not recognized, or failed
Rebuilding
Rebuild in progress
Failure Prediction
(S.M.A.R.T. errors)
Failure expected
Locating
[Locate Device] function running
Gray
Gray
with an "!" mark
Gray
with yellow
background
136
Status
Gray
MegaRAID SAS User's Guide
table: Hard disk status icon
Icon
Displayed in
White
with a blue "!"
mark
Status
Incorrect configuration
information detected
(Foreign configuration)
Description
Information about an old array or an externalarray configuration exists on the hard disk.
This icon appears in the following cases:
• When a hard disk that has been used before
is installed.
• When a hard disk that has failed once is
detected again.
If the hard disk is in "Failed”state at the same
time as it is in this state, regard it as a failed
hard disk.
` When you select the icon of each hard disk, more detailed information appears in the object window.
Note that you cannot see some information for unrecognizable hard disks.
For details, see "4.9.3 Checking Hard Disk Status" (Jpg.167).
` S.M.A.R.T. errors and Foreign configuration may appear in combination with another status.
z Fan units, power units, and temperature sensors under SES devices
Monitoring these devices is not supported in ServerView RAID.
z Logical drives
The logical drives created under the array controller are displayed. Each logical drive number is shown
in ( ).
You can also see the status of each logical drive.
table: Logical drive status icons
Icon
Status
Description
Online
(Operational)
Normal
Partially critical
(Partially
Degraded)
Operating with redundancy. But a hard disk has been failed
Critical
(Degraded)
Operating without redundancy
Offline (Failed)
Not available
Locating
[Locate Logical Drive] function running
Incorrect
configuration
information
detected
(Foreign
configuration)
This icon may be displayed when the hard disk with the "Foreign
configuration" status exists.
This displays the information in the hard disk and is not actual logical
drive (cannot be seen from the OS).
This icon may be displayed in the following cases:
• When a failed hard disk exists.
• When a hard disk that has been used before is connected.
137
Chapter 4 Array Configuration and Management [ServerView RAID]
` When you select the icon of each logical drive, more detailed information appears in the object
window. For details, see "4.9.4 Checking Logical Drive Status" (Jpg.169).
z File log, system log, and plug-in
You can configure the log files and the OS event log for ServerView RAID.
For details, see "4.7.4 Setting ServerView RAID" (Jpg.146).
138
MegaRAID SAS User's Guide
4.7 Settings
This section explains how to change each parameter for array controllers, logical
drives, and event logging.
4.7.1 Changing Array Controller Setting
You can check and change array controller settings.
` The controller settings must be set within the ranges shown in the following table. You may only
change items specified as default in the table. If the settings are outside of the specified ranges,
correct operation may not be ensured.
` Apart from the controller settings, you may be required to make various settings on the server itself.
See "User's Guide" on PRIMERGY Startup Disc provided with the server on how to set up the server.
1
Start ServerView RAID and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select the controller (
).
139
Chapter 4 Array Configuration and Management [ServerView RAID]
3
Click the [Settings] tab in the object window.
The current settings are displayed in the tab.
4
Click [Edit] to set each item.
A setting window appears. For the items that can be set, see the following:
• When you set Tasks:
J"„ Tasks" (pg.141)
• When you set Others:
J"„ Others" (pg.142)
5
Click [OK].
A confirmation window appears.
6
Click [Apply].
You will see the change reflected on the [Settings] tab in the object window.
140
MegaRAID SAS User's Guide
„ Tasks
You can primarily set the contents associated with background tasks.
table: Array controller — tasks
Options
Setting
Init mode
Normal
initialization
BGI rate
Migration rate
Description
Cannot be
changed
Not supported.
[Note 1]
Default
Sets the background initialization priority for normal I/O.
[Note 1]
Default
Sets the Expand Capacity priority for normal I/O.
MDC rate
[Note 1]
Default
Sets the Make Data Consistent priority for normal I/O.
Patrol Read mode
Disabled
Cannot be
changed
Not supported.
Auto rebuild
Enabled
Cannot be
changed
Enables automatic rebuild after hard disk replacement.
Rebuild rate
[Note 1]
Default
Sets the rebuild priority for normal I/O.
[Note 1]: For MegaRAID SAS 300-8E ROMB, MegaRAID SAS 8300XLP、MegaRAID SAS 8408E,
and MegaRAID SAS 8344ELP: 80
For RAID 5/6 SAS based on LSI MegaRAID: 30
` While increasing the values for BGI rate, Migration rate, MDC rate, or Rebuild rate increases the
background task performance, it may also decrease the rate of normal I/O.
141
Chapter 4 Array Configuration and Management [ServerView RAID]
„ Others
table: Array controller — others
Options
142
Setting
Description
Alarm control
Disabled
Cannot be
changed
If a buzzer for notifying errors is installed in the array controller,
this enables or disables the buzzer.
S.M.A.R.T. poll
interval
5
Cannot be
changed
Specifies a polling interval for S.M.A.R.T. detection.
Spinup drive
count
2
Cannot be
changed
Sets the number of hard disks that start rotating at the same time.
Spinup delay
6
Cannot be
changed
Specifies the rotation start interval between hard disks.
Auto flush interval
4
Cannot be
changed
Sets the data write interval from the cache memory to the hard
disk.
Coercion mode
None
Cannot be
changed
Sets the capacity rounding function for unifying hard disk
capacities.
Cluster enable
No
Fixed
Not supported.
MegaRAID SAS User's Guide
4.7.2 Configuring Battery Backup Unit
You can check and change the operation mode of a battery backup unit.
This setting is automatically changed to the appropriate setting after installation of the RAID
management tool.
1
Start ServerView RAID and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select a battery backup unit (
3
Click the [Settings] tab in the object window.
).
The current settings are displayed in the tab.
4
Click [Edit] to set "Disabled".
table: Battery backup unit— Misc.Properties
Options
Auto learn mode
5
Setting
Disabled
Setting
value
during the
operation
Description
This item sets the battery recalibration mode. Make sure
to set it to "Disabled".
Click [OK].
The confirmation window appears.
6
Click [Apply].
You will see the change reflected on the [Settings] tab in the object window.
143
Chapter 4 Array Configuration and Management [ServerView RAID]
4.7.3 Setting Logical Drive
You can check and change the logical drives.
1
Start ServerView RAID and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select the logical drive (
3
Click the [Settings] tab in the object window.
).
The current settings are displayed in the tab.
4
Click [Edit] to set each item.
A setting window appears. For the items that can be set, see the following:
J"„ Cache" (pg.145)
` Setting a name for a logical drive in the Logical Drive is not supported. Do not use this item.
5
Click [OK].
A confirmation window appears.
6
Click [Apply].
You will see the change reflected on the [Settings] tab in the object window.
144
MegaRAID SAS User's Guide
„ Cache
You can set information about the access method of logical drives.
table: Logical drive — Cache
Options
Setting
Description
Default write mode
Write-through
Default
Sets the Erite Policy of the logical drive. The following
configurable modes can be selected: Write-through,
Write-back, Always write-back (Independent of BBU),
and bad BBU.
For details about the Write Policy, see "1.3.1 Write
Policy" (Jpg.26).
Default read mode
No read-ahead
Cannot be
changed
Not supported. Do not change them.
Default cache mode
Direct
Cannot be
changed
Disk cache mode
Disabled
Cannot be
changed
` Before you change the Default write mode, make sure that you understand the Write Policy. Using the
Write-back or bad BBU without preventing power off due to power interruption may cause data loss.
For details, see "1.3.1 Write Policy" (Jpg.26).
145
Chapter 4 Array Configuration and Management [ServerView RAID]
4.7.4 Setting ServerView RAID
You can configure the log files and the OS event log for ServerView RAID.
1
Start ServerView RAID and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select the icon you want.
3
Click the [Settings] tab in the object window.
The current settings are displayed in the tab.
When you select File Log in the tree view:
When you select System Log in the tree view:
4
Click [Edit] to set each item.
A setting window appears. For the items that can be set, see the following:
• When you set File Log:
J"„ File log" (pg.147)
• When you set System Log:
J"„ System log" (pg.148)
146
MegaRAID SAS User's Guide
` ServerView RAID, Setting the Multiplexer and the LSIStoreLib-Plugin is not supported, so do
not use these items.
5
Click [OK].
A confirmation window appears.
6
Click [Apply].
You will see the change reflected on the [Settings] tab in the object window.
„ File log
table: File log
Options
Setting
Description
Logging
Enabled
Cannot be
changed
Enables event logging to the log file. Always use the
program with this option Enabled.
Log level
Information
Cannot be
changed
Sets a priority level for events that execute logging.
Events that have a priority level equal to or greater than
the one set here will be logged in the log file. Do not
change the Information.
File name
RAIDLog.xml
Cannot be
changed
Log file name.
File size
10
Cannot be
changed
Sets the log file size limit.
Log method
Rotation
Cannot be
changed
Sets the method of log rotation.
Max. save files
5
Default
Maximum number of log files. We recommend that you
set this value equal to or greater than the default value.
147
Chapter 4 Array Configuration and Management [ServerView RAID]
` The log files for ServerView RAID are stored as RAIDLog.xml (or RAIDLog<number>.xml) in the
following folders:
For Windows 2000 Server/
Windows Server 2003
C:\Program Files\Fujitsu Siemens\RAID\web\public\
For Windows Server 2003 x64
C:\Program Files (x86)\Fujitsu Siemens\RAID\web\public\
For Linux
/opt/fsc/RAID/web/public/
Do not delete or edit the log files since they may be used when investigation is necessary. The
maximum file size to be used ranges from 20MB to 110MB, depending on the settings. Browsing or
monitoring the log files is not supported.
„ System log
table: System log
Options
Setting
Description
Logging
Enabled
Default
Enables event logging to the OS event log.
Log level
Information
Default
Sets a priority level of events that are logged in the OS event
log. Events that have a priority level equal to or greater than the
one set here will be logged.
Debug is not supported.
` ServerView RAID logs events that occur in the array controller in the OS application log as events of
the "Source: ServerView RAID". However, when ServerView is installed, events that occur in the array
controller are logged also as events of the "Source: Fujitsu ServerView Services".
` The event log for which the settings can be changed under System Logging is the one that contains
the "Source: ServerView RAID".
148
MegaRAID SAS User's Guide
4.8 Operating RAID Configuration
This section explains the procedure for creating a new disk array configuration,
expanding the capacity, and setting hot spare.
` Disk array operations require logging in to ServerView RAID Manager with Administrator privileges.
They also require that the access mode is set to [Write access].
For details about access modes, see "„ Toolbar" (Jpg.130).
4.8.1 Creating Disk Array Configuration (Create Logical Drive)
To create a new array configuration, or to add an array configuration in free space of a disk, follow the
procedure below:
` During rebuild, the array configuration cannot be created or deleted. Perform these procedures after
the rebuild is completed.
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select the array controller (
), right-click, and then click
[Create logical drive] from the displayed menu.
The [Parameters] tab of the Create logical drive window appears.
149
Chapter 4 Array Configuration and Management [ServerView RAID]
3
Configure the logical drives.
1. Select a RAID level for the logical drive.
Click T under [RAID level] and select the RAID level for the logical drive from the
displayed list.
` The configurable RAID level is limited according to the number of unused hard disks or the free
space in an existing disk group.
` When there is free space in a predefined disk group, you can only set the same RAID level as
that of the logical drive that is already set in the disk group. (Logical drives with different RAID
levels cannot be created within the same group.)
` Do not change the default stripe size (64 [K]).
2. Specify the capacity of the logical drive.
• When creating a single logical drive, a logical drive with RAID 10, or the last
logical drive in the disk group:
In [Capacity of the logical drive], select [Use maximum capacity].
The maximum capacity of the logical drive is set as a capacity.
• When multiple logical drives are created in the disk group:
In [Capacity of the logical drive], select [Use only] and specify a suitable capacity.
The default unit for entering the capacity of the logical drive is GB. If you set in MB,
select [MB] from the pull-down menu (KB units are not supported).
` The capacity of the logical drive may be automatically adjusted to match the block size.
` If multiple logical drives are created in a single disk group, you cannot expand the capacity of
the logical drive with the expand capacity function later.
` If you create a RAID 10 logical drive, the capacity of the logical drive cannot be specified.
3. Set a Write Policy of the logical drive.
Click T of [Write mode] in [General parameters], and select the Write Policy from the
displayed list.
` Before using the Write Policy, see "1.3.1 Write Policy" (Jpg.26) and make sure you understand what it does.
` If there is no battery backup module, the logical drive is created in Write Through mode even if
[Write Back] is enabled. To enable the Write Policy if there is no battery backup module, set the
Write mode to [Always Write-back (independent of BBU state)].
4. Set other parameters.
Change the settings as follows if different:
table: Parameter settings
Parameter
150
Setting item
Read mode
No read-ahead
Cache mode
Direct
Disk cache mode
Disabled
Init mode
No initialization
Name
(Blank)
MegaRAID SAS User's Guide
4
Click the [Layout] tab to allocate a hard disk for a logical drive.
` When you set the logical drive to Write back or Bad BBU and click the [Layout] tab, the following confirmation message appears. If the settings are acceptable, click [Yes]:
The following window appears.
1. In the left tree of the window, select an unused hard disk (
free space (
) that belongs to the existing disk group.
2. Click [Add].
The hard disk you selected or added appears in the Current layout.
) or a hard disk with
` When selecting a hard disk with free space that is included in an existing disk group, all the
hard disks in that group are added to [Current layout].
151
Chapter 4 Array Configuration and Management [ServerView RAID]
3. Repeat the preceding steps to allocate as many hard disks as you need for the
RAID level you set.
table: RAID levels and necessary number of hard disks
RAID Level
RAID 0
Number of hard disks
1 or more
RAID 1
2
RAID 5
3 or more
RAID 6
3 or more
RAID 10
Even number equal to or larger than four
Number of used blocks
on the hard disks
Number of start blocks
on the hard disks
Indicates that the selected hard disk
is configuring the existing logical
drive x
(In this figure, logical drive 0.)
Used capacity
If [Available] appears in the [Used by] column after selecting a hard disk that belongs to
the disk group in the tree, there is some free space in the hard disk.
` Use hard disks of the same capacity and type within a logical drive. If a mixture of different
hard disks are connected, check them in advance referring to "4.9.3 Checking Hard Disk Status" (Jpg.167).
` If you allocate a new hard disk to a logical drive, a disk group is automatically configured
together with the logical drive.
` If there is a hard disk with free space in the existing disk group, you cannot allocate an unused
hard disk to a logical drive. Use all the free space in the hard disks of the disk group before
allocating an unused hard disk to the logical drive.
` If you allocate a hard disk with free space in an existing disk group to a logical drive, add all of
the hard disks within that disk group.
When deallocating hard disks from a logical drive:
In the [Current layout] area on the left side of the window, select a hard disk, and click [Remove].
152
MegaRAID SAS User's Guide
5
Click [Create].
` If you cannot click [Create] because it is grayed out, the following causes are possible.
Review the allocation of hard disks in the step 4.
•The number of hard disks is not enough for the selected RAID level.
•All of the hard disks within an existing disk group have not been added.
A confirmation window appears.
6
Type "yes" and click [OK].
A new disk array configuration is created.
4.8.2 Expanding Capacity of Logical Drive (Migrate Logical
Drive)
You can expand the capacity and change the RAID level for existing logical drives.
` There are certain conditions to note and precautions to take for capacity expansion. Read "1.3.5
Capacity Expansion" (Jpg.33) carefully before expanding the capacity.
` The capacity of RAID 10 logical drives cannot be expanded.
1
Back up the data to prepare for unexpected problems.
2
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
3
Perform Make Data Consistent (Jpg.161) on the logical drive whose capacity is
to be expanded and check if it completes successfully.
` If the Make Data Consistent is not completed successfully, do not expand the capacity of the
logical drive.
153
Chapter 4 Array Configuration and Management [ServerView RAID]
4
In the tree view, select the logical drive (
), right-click, and then click
[Migrate Logical Drive] from the displayed menu.
The following window appears.
5
Select the RAID level after capacity expansion.
Click T under [RAID level] and select the RAID level for the logical drive from the displayed
list. After the expansion, the RAID level of the logical drive will be converted to the RAID level
selected here.
` If you convert a RAID 1 ,5 or 6 logical drive to RAID 0, note that the logical drive will lose its
redundancy.
6
154
Click the [Layout] tab.
MegaRAID SAS User's Guide
7
Add hard disks to the disk group.
1. In the tree in the left side of the window, select an unused hard disk (
).
2. Click [Add].
The hard disk you selected or added appears in the Current layout.
3. Repeat the preceding steps to add further hard disks.
You can add hard disks until the total number of drives in the disk group displayed in the
[Current layout] reaches 32.
` Make sure that the number of hard disks in the disk group does not exceed 32.
` Use additional hard disks of the same capacity and type as the existing hard disks in the disk
group. If a mixture of different hard disks are connected, check them in advance referring to
"4.9.3 Checking Hard Disk Status" (Jpg.167).
When deallocating hard disks from a logical drive:
In the [Current layout] area on the left hand of the window, select a hard disk, and click
[Remove].
8
Click [Apply].
A confirmation window appears.
9
Type "yes" and click [OK].
The capacity expansion process starts. Wait until the process is completed.
` Do not turn off, reset or restart the server while capacity expansion is in progress. Doing so may cause
loss of data in the target logical drive.
` If the server is turned off during capacity expansion, access to the hard disk is automatically resumed
after the server restarts. In this case, wait until the access lamp on the hard disk turns off to ensure that
no access is made to the hard disk, redo the array configuration, and then restore the data backed up
before the expansion.
` If the RAID level of a logical drive after the expansion has data redundancy (RAID 1, RAID 5 or RAID
6), background initialization will be performed after the capacity expansion is complete.
155
Chapter 4 Array Configuration and Management [ServerView RAID]
4.8.3 Deleting Existing Logical Drive (Delete Last Logical
Drive)
This section explains how to delete an existing logical drive.
` When you delete logical drives, start deleting them from the last created one (the drive with the highest
number.) Do not delete them in any order than starting from the last created logical drive.
` We recommend that you back up data on all of the logical drives as a safeguard against accidental
data loss due to operational errors before you delete logical drives.
` For how to delete all logical drives (i.e. to clear an array configuration), see "4.8.6 Deleting Disk Array
Configuration Information" (Jpg.160).
` If a background task is running, wait until the background task finished before you start deleting logical
drives.
1
Back up the data to prepare for unexpected problems.
2
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
3
In the tree view, select the array controller (
) where the logical drive to be
deleted is created, right-click, and then click [Delete last logical drive] from the
displayed menu.
` Be careful not to click [Delete all logical drive]. If you click [Delete all logical drive], all the logical drives are deleted at once. If a wrong logical drive is deleted, click [Cancel] in the confirmation window and start again from the beginning.
A confirmation window appears.
4
Type "yes" and click [OK].
The last created logical drive is deleted.
` If you accidentally delete wrong logical drives, recreate the array configuration, and then restore the
data backed up before the deletion.
156
MegaRAID SAS User's Guide
` If all the logical drives in a disk group are deleted, the disk group will also automatically be deleted, and
the hard disks that composed the disk group will be marked as unused.
4.8.4 Setting and Releasing Spare Disk
` There are some conditions and notes to configure spare disk. Make sure to read "„ Hot spare rebuild"
(Jpg.30) before setting hot spare.
„ Setting spare disks
This section explains how to set spare disks.
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select an unused hard disk (
), right-click, and then click
[Manage hot spare] from the displayed menu.
3
Click [Create].
The confirmation window appears.
4
Click [Yes].
The icon of the unused hard disk changes to a spare disk icon (
).
157
Chapter 4 Array Configuration and Management [ServerView RAID]
` If a disk group exists that consists of hard disks with a capacity larger than that of the hard disk
to be set as a spare, the following message appears when you click [Create global hot spare].
If you want to set the spare disk, click [Yes].
` Use a spare disk of the same capacity and type as the hard disks in the disk group.
` When there are two or more disk groups that use different hard disk capacities, set a spare
disk for each type of hard disk.
„ Releasing spare disks
This section explains how to release spare disks.
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select the hard disk (
) where the spare disk is to be
released, right-click the drive, and then click [Manage hot spare] from the
displayed menu.
3
158
Click [Delete].
MegaRAID SAS User's Guide
4
Click [Yes].
The spare disk icon changes to an unused hard disk icon (
).
4.8.5 Changing the Write Policy
For this array controller, you can configure the Write Policy for each logical drive.
To change the Write Policy of a logical drive, following the procedure below:
` Before using the Write Policy, see "1.3.1 Write Policy" (Jpg.26) and make sure you understand what it
does.
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select the logical drive (
) whose Write Policy you want to
change.
3
Click the [Setting] tab, and click [Edit] in [Cache].
The [Edit:LogicalDrive_n] (n stands for a number) window appears.
The current Write Policy appears in the [Default write mode] window.
` The setting values for other than [Default write mode] are not allowed to be changed. Do not
change them.
4
Click T of [Default write mode], and select the Write Policy you want to set from
the displayed list.
159
Chapter 4 Array Configuration and Management [ServerView RAID]
5
Click [OK].
The [Apply changed settings] window appears.
6
Click [Apply].
The Write Policy changes to the new mode.
` If you change [Default write mode] to [Write-back] or [Write cache bad BBU], the following
warning message appears. If you want to enable the write cache, click [Yes].
4.8.6 Deleting Disk Array Configuration Information
The "Disk array configuration information" refers to the information created when the disk array is
configured, such as the disk group and logical drive capacity, the RAID level, and which hard disk
belongs to which disk group.
You can delete all the existing logical drives defined in the array controller and make all the connected
hard disk unused by deleting the disk array configuration information.
` You should only delete disk array configuration information when instructed to do so during
maintenance. All data on the logical drives will be lost by this operation.
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
160
MegaRAID SAS User's Guide
2
In the tree view, select the controller (
) whose disk array configuration
information you want to delete, right-click, and then click [Clear configuration]
from the displayed menu.
A confirmation window appears.
3
Type "yes" and click [OK].
The existing disk array configuration information is deleted, and all logical drives are deleted.
4.8.7 Make Data Consistent
Make Data Consistent, also called redundant data regeneration, is a function that regenerates the parity
or mirrored data on redundant logical drives and makes the array configuration consistent.
When a server failure or a power failure results in a dirty OS shutdown, the array may become
inconsistent. When a dirty OS shutdown occurs, perform this function as soon as possible.
` Make Data Consistent can be performed on logical drives with redundancy such as RAID 1, RAID 5,
RAID 6, and RAID 10 logical drives in online status (operational), and a RAID 6 logical drive in partially
degraded status. Make Data Consistent cannot be performed on logical drives without redundancy
such as RAID 0 logical drives or logical drives in critical (degraded) or offline (failed) status.
` In addition to keeping the data consistent in the array, the Make Data Consistent also automatically
corrects any media errors on the hard disks.
` Make Data Consistent can be performed simultaneously for several logical drives.
To perform the Make Data Consistent, follow the procedure below.
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
161
Chapter 4 Array Configuration and Management [ServerView RAID]
2
In the tree view, select a logical drive (
) where the Make Data Consistent
is to be performed, right-click, and then click [Start MDC] from the displayed
menu.
A confirmation window appears.
3
Click [Yes].
When the Make Data Consistent is started, [MDC running] appears in [Activity] of the object
window, and the progress of the Make Data Consistent appears. When the progress bar reaches
100% and the window closes, the check is complete.
4.8.8 Rebuild
Rebuild is the operation to recover a logical drive in critical status (degraded) to online (operational)
status. For details about the rebuild, see "1.3.3 Rebuild" (Jpg.30).
To perform a manual rebuild, following the procedure below.
` Usually, rebuild is automatically executed after replacing the hard disk. For how to replace the hard
disk and how to perform rebuild, see "Chapter 6 Replacing Hard Disk" (Jpg.243).
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select a logical drive in degraded status (
), right-click, and
then click [Start rebuild] from the displayed menu.
The confirmation window appears.
3
Click [Yes].
When the rebuild is started, [Rebuilding] appears in [Activity] of the object window, and the
progress of the rebuild appears. When the progress bar reaches 100% and the window closes, the
check is complete.
162
MegaRAID SAS User's Guide
4.8.9 Recalibration
Recalibration is a process to recalibrate the battery capacity.
To perform recalibration manually, use the following procedure:
` Run battery recalibration before the operation when:
• You bought a controller with a battery backup unit installed in it.
• You installed a new battery backup unit that you bought.
• You changed units that have batteries.
Note that recalibration may automatically run, leaving management tool recalibration disabled. Then
you do not need to manually do recalibration.
` Battery recalibration takes 12 hours with the server power on. If the server is turned on or off during a
battery recalibration, the battery recalibration restarts from the beginning.
` During recalibration, the logical drive in Write Back mode shifts automatically to Write Through mode
for safety. When the battery recalibration is completed, the Write Policy is automatically back to Write
Back.
1
Start ServerView RAID Manager and log in with Administrator privileges.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, select a battery backup unit (
), right-click, and then click
[Recalibration] from the displayed menu.
The recalibration starts.
163
Chapter 4 Array Configuration and Management [ServerView RAID]
4.9 Checking Each Status
[ServerView RAID Manager]
The following information can be checked using ServerView RAID Manager.
• Information about events or errors that have occurred: "Appendix A List of ServerView RAID Event
Log" (Jpg.270)
• Server information: "4.9.1 Checking the Server Condition" (Jpg.164)
• Array configuration or controller information: "4.9.2 Checking Array Controller Status" (Jpg.165)
• Hard disk information: "4.9.3 Checking Hard Disk Status" (Jpg.167)
• Logical drive information: "4.9.4 Checking Logical Drive Status" (Jpg.169)
• Information about tasks running in the background: "4.9.5 Checking Progress of Background Task"
(Jpg.171)
4.9.1 Checking the Server Condition
Selecting a server name displayed on the top of the tree view displays information about the server on
which ServerView RAID is installed.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
Click the name of the server you want to check in the tree view.
Detailed information about the selected server appears.
table: Detailed information about servers
Item
System
164
Category
Description
Name
Server name.
IP Address
Displays the server IP address.
The loopback address (127.0.0.1) may be displayed depending
on the server network settings.
Fully Qualified
Domain Name
Server FQDN.
MegaRAID SAS User's Guide
table: Detailed information about servers
Item
Operation System
Category
Description
Vendor
OS vendor name.
Version
OS type and version.
Edition
OS edition.
Service pack
Service pack applied to OS.
Processor
architecture
CPU type of OS.
[Note]: All of the items may not be displayed depending on the OS type or settings.
4.9.2 Checking Array Controller Status
Selecting an array controller in the tree view displays detailed information about the array controller in
the object window.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
Click the array controller (
) you want to check in the tree view.
Detailed information about the selected array controller appears in the [General] tab.
165
Chapter 4 Array Configuration and Management [ServerView RAID]
table: Detailed nformation about array controllers
Item
Adapter
PCI Location
Ports
Devices(max)
Properties
Category
Description
Name
The model name of the array controller.
ID
The number of the array controller.
Vendor
The vendor name of the array controller.
Product
The product name of the array controller.
Serial number
The serial number of the array controller.
Memory size
The cache memory size of the array controller.
FlashROM size
The size of the array controller's FlashROM.
NVRAM size
The size of the array controller's NVRAM.
Firmware package version
The version included the array controller's firmware and
BIOS, etc.
Firmware version
The version of the array controller's firmware.
Firmware build time
The build date and time of the array controller's firmware.
BIOS version
The version of the array controller's BIOS.
Driver version
The version of the array controller's driver.
Bus
The bus number for the array controller.
Function
The function number for the array controller.
Device
The device number for the array controller.
Number
The number of ports on the array controller.
Protocol
The protocol supported by the array controller.
Physical
Logical maximum number of physical devices.
Logical
Logical maximum number of logical devices.
S.M.A.R.T. support
Support status of S.M.A.R.T.
Alarm present
Indicates whether the alarm is present or not.
Inconsistency handling
Operation method for data consistency check. This
product adopts MDC (Make Data Consistent).
Correctable errors
These counters are not supported.
These counters indicate the number of recovery attempts
made by the array controller for temporary or minor
errors. They can be ignored unless the hard disk receives a
failure status.
Uncorrectable errors
Cluster active
This value is not supported.
Status
The current status of the array controller appears.
Additional Status
Displays the additional information on the current state of
the array controller.
` Regarding the information displayed in the [Settings] tab, see "4.7.1 Changing Array Controller
Setting" (Jpg.139).
` The [Background activities] tab appears if a background task is running.
Regarding the information displayed in the [Background activities] tab, see "„ Checking using
background activities from array controllers" (Jpg.172).
166
MegaRAID SAS User's Guide
4.9.3 Checking Hard Disk Status
Detailed information about hard disks connected to the controller appears in the object window.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
Click the hard disk (
) you want to check in the tree view.
The detailed information about the selected hard disk appears.
When selecting the [General] tab
167
Chapter 4 Array Configuration and Management [ServerView RAID]
table: Detailed information about hard disks
Item
Disk
168
Category
Description
Name
Hard disk model name. The number in parentheses indicates a
hard disk slot number, an enclosure number, and a slot number.
Device number
The device number for the hard disk
Enclosure number
The enclosure number of the hard disk that it is installed in. It is
only displayed to the hard disks connected to a SAS expander.
Slot
The number of the slot where the hard disk is installed
Vendor
Hard disk vendor name
Product
Hard disk product name
Type
The protocol type of the hard disk
SAS address 00
SAS address of the hard disks
Serial number
Serial number of the hard disk
Firmware version
The version of the hard disk's firmware
Transfer width
The data transfer width of the hard disk appears
Physical size
The physical capacity of the hard disk
Config. size
The hard disk's available capacity when connected to the array
controller.
Foreign configuration
Indicates whether configuration information significantly
different from the current information is present or not. By
default, [No] appears. [Yes] may appear when there is a failed
hard disk.
Misc errors
These counters are not supported. Although these counters show
the recovery frequency to the temporary / negligible error
performed by the array controller, there is no problem as long as
the state of the hard disk is not Dead state.
S.M.A.R.T. errors
The counter for S.M.A.R.T. failure predictions for the hard disk
Media errors
These counters are not supported.
These counters indicate the number of recovery attempts made
by the array controller for temporary or minor errors. They can
be ignored unless the hard disk receives a failure status.
Activity
The running tasks for the hard disk are displayed
• Idle: No running tasks.
• Rebuilding: A rebuild is in progress.
Estimated time
remaining
This category appears only while the background task is
running. For details, see "4.9.5 Checking Progress of
Background Task" (Jpg.171).
Status
The current status of the hard disk appears
MegaRAID SAS User's Guide
When selecting the [Layout] tab
table: Layout information about hard disks
Item
Description
Config. size
Available hard disk capacity when connecting to the array controller
Usage
Logical drive information that the hard disk is allocated to
4.9.4 Checking Logical Drive Status
Detailed information about logical drives appears in the object window.
You can change the displayed information by switching the tabs at the top of the object window.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, click the logical drive you want to browse (
).
Detailed information about the selected logical drive appears in the object window.
3
Click the tab you want to check in the object window.
When you select the [General] tab:
169
Chapter 4 Array Configuration and Management [ServerView RAID]
table: Detailed information about logical drives
Item
Logical Drive
Category
Description
Name
The name of the logical drive
Logical drive number
Logical drive number
RAID level
The RAID level set for the logical drive
Stripe size
The striping size used by the logical drive
Logical size
The logical size of the logical drive
Physical size
The physical size of the logical drive
Operating system
device name
The hard disk location of the logical drive in the OS
Initialization status
The initialized status of the logical drive
• Initialized: Already initialized
• Uninitialized: Not initialized
Since this product supports background initialization, logical
drives are automatically initialized even if [Uninitialized]
appears. Consequently, you can ignore this message.
Cache
Activity
The running tasks for the logical drive
When background tasks are running, the running tasks and their
progress are displayed on the progress bar.
For details, see "4.9.5 Checking Progress of Background Task"
(Jpg.171).
Estimated time
remaining
This category appears only while the background task is
running. For details, see "4.9.5 Checking Progress of
Background Task" (Jpg.171).
Status
The current status of the logical drive
Write mode
The current Write Policy status of the logical drive
Read mode
Cache mode
This item is not supported
Disk cache mode
When you select the [Layout] tab:
table: Logical drive layout information
Item
170
Description
Disk
The hard disks that compose the target logical drive are displayed
Used capacity
The capacity of hard disks used by the target logical drive
Partitions
The partition information of the target logical drive
MegaRAID SAS User's Guide
` Regarding the information displayed in the [Settings] tab, see "4.7.3 Setting Logical Drive" (Jpg.144).
4.9.5 Checking Progress of Background Task
There are four kinds of background tasks: initialization, rebuild, Make Data Consistent and capacity
expansion. ServerView RAID Manager enables you to view the progress of these tasks with progress
bars.
The progress bar shows the approximate time for the task to complete (only when using ServerView
RAID v2.1.x).
The background tasks for which the progress can be checked are as follows:
table: Background task
Background task
Activities
Background Initialization
BGI
Make Data Consistent
MDC running
Rebuild
Rebuilding
Capacity Expansion
Migrating
How to check background tasks
• Checking using detailed information about
logical drives
• Checking Using Background activities from
Array Controllers
• Checking using detailed information about hard
disks (rebuild only)
„ Checking using detailed information about logical drives
With this method, you can check the background tasks being executed on the selected logical drive.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, click the logical drive (
3
Click the [General] tab.
).
You can check the type and progress of the background tasks being executed in [Activity].
171
Chapter 4 Array Configuration and Management [ServerView RAID]
` If rebuilds are simultaneously being executed for the multiple hard disks in a RAID 10 configuration, the progress displayed in [Activity] of the logical drive is the average value for each
rebuild progress of the hard disks.
` When using ServerView RAID v2.1.x or later, the approximate time to complete the background task appears in [Estimated time remaining]. However, use this time only as a guideline
since the actual time may be different depending on the system load.
„ Checking using background activities from array controllers
With this method, you can check all the background tasks being executed in the selected array controller.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
In the tree view, click the controller (
3
Click the [Background activities] tab.
).
The logical drives where background tasks are currently being executed are displayed in [Logical
Drive], and you can check the type and progress of the background tasks being executed in
[Activity].
` When you click the button (
) to the right of the information for each logical drive, the target logical drive is selected in the tree view, so that you can view detailed information about
that logical drive.
` While rebuild is in progress, both the progress for the logical drive and the progress for the
hard disk are displayed.
` When using ServerView RAID v2.1.x or later, the approximate time to complete the background task appears in [Activity]. However, use this time only as a guideline since the actual
time may be different depending on the system load.
„ Checking using detailed information about hard disks (rebuild only)
With this method, you can check the rebuilds being executed on the selected hard disk.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
172
In the tree view, click a hard disk being rebuilt (
).
MegaRAID SAS User's Guide
3
Click the [General] tab.
You can check the progress of the rebuild being executed in [Activity].
` When using ServerView RAID v2.1.x or later, the approximate time to complete the background task
appears in [Estimated time remaining]. However, use this time only as a guideline since the actual time
may be different depending on the system load.
173
Chapter 4 Array Configuration and Management [ServerView RAID]
174
Chapter 5
Array Configuration and
Management [GAM]
This chapter explains an overview of and
requirements for, and how to install and use
GAM.
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
Overview of and Requirements for GAM . . . . . . . . . . . . .
Installing GAM [Windows] . . . . . . . . . . . . . . . . . . . . . .
Installing HDD Check Scheduler [Windows] . . . . . . . . .
Installing Battery Recalibration Scheduler [Windows] . . . .
Starting and Exiting GAM . . . . . . . . . . . . . . . . . . . . . . . . .
GAM Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . .
Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating RAID Configuration . . . . . . . . . . . . . . . . . . . . .
Viewing Information [GAM] . . . . . . . . . . . . . . . . . . . . . . .
Maintenance Functions . . . . . . . . . . . . . . . . . . . . . . . . . .
176
183
188
192
196
198
207
212
228
239
175
Chapter 5 Array Configuration and Management [GAM]
5.1 Overview of and Requirements
for GAM
This section explains GAM (Global Array Manager).
GAM is used to monitor, manage, maintain, and configure an array controller, and
hard disks and logical drives that are connected to the array controller.
5.1.1 GAM Overview
GAM is an application softwre that monitors and manages the array controller on the OS.
GAM also allows you to manage a disk array system connected to an array controller (RAID controller).
The GAM functions require the interaction between the GAM Server and the GAM Client.
z GAM Server (monitoring function)
GAM Server monitors, collects, and notifies information about the status and the resource usage of the
disk array.
z GAM Client (management function)
GAM Client provides fault management, highly reliable messaging, and excellent OS support.
You can manage the maintenance of disk arrays and hard disks from the server or from a client PC
connected to the network.
` To ensure stable operation of PRIMERGY, install GAM (or ServerView RAID) when using the array
controller. If GAM (or ServerView RAID) is not installed, failures will not be detected. You will also be
unable to perform maintenance correctly.
` Install either GAM or ServerView RAID, but do not install both. For which to use, see ReadmeEN.html
on the Array Controller Document & Tool CD. If by mistake you have installed ServerView RAID rather
than GAM, uninstall ServerView RAID and HDD Check Scheduler, and then install GAM and HDD
Check Scheduler. Do not operate the server with both ServerView RAID and GAM installed.
` Only start GAM Client when management or maintenance of arrays is necessary. From a security point
of view, it is not recommended to run GAM Client continuously. While signing on from GAM Client, if
the accessed server shuts down, GAM Client cannot communicate with GAM Server and cannot
respond, which prevents the user from operating it. In that case, wait for the GAM Server that is to be
accessed to start up again, or forcibly exit GAM Client.
176
MegaRAID SAS User's Guide
5.1.2 Requirements for GAM
An appropriate server environment is required for GAM Server and GAM Client. Use hardware and
software that meet the following conditions:
„ GAM server
You must have the following environment to use GAM Server.
table: Requirements for GAM Server
Item
Contents
Hard disk
• For Windows
64MB or more free space in the partition in the OS
• For Linux
64MB or more free space under /usr and /var
Application
TCP/IP, SNMP service, and ServerView must be installed.
OS
A supported OS of the server that the array controller is installed in.
` Apply the latest Service Pack for the OS.
` Make sure to install the Fujitsu-supported device drivers and GAM.
` Make sure to configure the network properly. If there is a problem with the network configuration, you
may not be able to monitor the status of arrays by ServerView or events may not be notified.
` When change a host name or an IP address of the server with a GAM-Server installed in it, uninstall
the GAM Server after the change and install it again.
„ GAM Client (when managed from a client PC)
When GAM Client is installed on a client PC different from the server, the following environment is
required for the client PC.
table: Requirements for GAM Client
Item
Network
Contents
Network connection with available TCP/IP
Input device
A mouse or other pointing device
Processor
Pentium® or later
Memory
256MB or more
Hard disk
32MB or more free space
Monitor
800 × 600 or better resolution (1024 × 768 or more recommended)
OS
Windows Server 2003
Windows XP
Windows 2000 Service Pack 4 or later
Windows 2000 Professional Service Pack 4 or later
177
Chapter 5 Array Configuration and Management [GAM]
5.1.3 Access Privileges to GAM
You need to sign on to GAM to use the GAM functions. User authentication is based on the user
accounts registered in the OS. Note that the available functions vary depending on the user account used
to sign on. There are three levels of access privileges as shown below:
„ Guest privileges
When using GAM with Guest privileges, it is not necessary to sign on. With Guest privileges, only the
RAID status and occurring events can be checked. It is not possible to set or change parameters.
„ User privileges
This is mainly used to monitor the status of controllers, hard disks, and logical drives. To use User
privileges, sign on with a user name and passwords registered in the OS. With User privileges, in
addition to using the functions made available with Guest privileges, several parameters can be changed.
It is also possible to view the detailed status of the selected controller and RAID subsystem. Note that it
is not possible to perform management operations such as changing disk array configurations, rebuilding
drives, and changing parameters related to controllers and drivers.
` RAID cannot be configured with User privileges. We recommend that you sign on with User privileges
when only monitoring RAID or only checking its status.
„ Administrator privileges
This function is used for management, maintenance, and configuration of controllers, hard disks, and
logical drives. To use Administrator privileges, sign on as "gamroot". In addition to the monitoring
functions made available with Guest or User privileges, it is possible to use all other functions including
creating/changing a RAID configuration, rebuilding drives, making logical drive data consistent, and
changing a drive status.
` When using GAM with Administrator privileges, data may be lost in the array controller depending on
the operation. Read this Chapter and use GAM accordingly.
` If GAM information cannot be monitored from ServerView, the network settings may be incorrect. In
this case, check the network settings again.
178
MegaRAID SAS User's Guide
5.1.4 Using GAM in Linux Environment
To use GAM in Linux environment, you need to install device drivers and GAM.
For using Linux, see the PRIMERGY page on the Fujitsu website (http://primergy.fujitsu.com/)
` GAM Client can only be installed on servers or PCs running Windows. Even when monitoring array
controllers on Linux servers using GAM Client, GAM Client cannot be installed on Linux servers.
Prepare a Windows server or client PC and install GAM Client on it.
The following figure shows a system configuration that GAM Client on a Windows server or on a client
PC manages a Linux server.
Windows Server
or
Client PC
Monitoring and Setting
GAM
Linux Server
GAM Server
Notifying GAM Event
GAM Client
Array Controller
` On Linux servers, you need to install GAM Server and edit the configuration file to set the GAM event
recipient and enable storing event logs after the installation. For more details, see the "Installation
Guide" for Linux at the above URL.
` If there is an intervening firewall in the environment, you need to configure the network settings so that
the port used by the GAM protocol is not blocked.
GAM uses the TCP port 157 and 158.
179
Chapter 5 Array Configuration and Management [GAM]
5.1.5 Using GAM in a Network Environment
In a network environment, arrays on multiple servers can be monitored and managed from a Windows
client connected to the network.
The following figure shows a system configuration in which GAM Client on the other Windows client
manages GAM Server.
Windows Server
GAM Server
Monitoring and Setting GAM
Array Controller
Notifying GAM Event
Windows Server
or
Client PC
Linux Server
Monitoring and Setting GAM
GAM Server
Notifying GAM Event
Array Controller
GAM Client
Monitoring and Setting GAM
Windows Server
Notifying GAM Event
GAM Server
Array Controller
` You need to configure the server receiving GAM events during GAM installation. For details, see step
12 in "5.2.1 How to Install GAM" (Jpg.183).
` If there is an intervening firewall in the environment, you need to configure the network settings so that
the port used by the GAM protocol is not blocked.
GAM uses the TCP port 157 and 158.
` One GAM Client can manage up to a maximum of 100 GAM Servers.
When managing more than 100 servers at the same time, one Windows server or one client PC to be
used as GAM Client is necessary per 100 servers.
` If multiple versions of the GAM Server coexist, use the version of GAM Client that corresponds to the
latest version of GAM Server, or a later version.
180
MegaRAID SAS User's Guide
„ Interaction with ServerView AlarmService
The following figure shows the interaction between ServerView and AlarmService when GAM Client
on the other Windows server (client) manages GAM Server. OS event logs can be stored both on the
GAM Server and on the Windows server (client).
z When storing OS event logs on the GAM Client Server/PC
Windows Server
or
Client PC
Windows Server or Linux Server
Monitoring and Setting GAM
GAM Server
GAM Client
ServerView
AlarmService
Notifying GAM
Event (SNMP Trap)
SNMP Service
Notifying GAM
Event (SNMP Trap)
Array Controller
OS Event Log
ServerView
AlarmService
OS Event Log
` ServerView must be installed on the GAM Client server/PC as well.
` Make sure to install ServerView on the server.
181
Chapter 5 Array Configuration and Management [GAM]
5.1.6 When Using Both ServerView RAID and GAM
When using both ServerView RAID and GAM on a network, you can use ServerView RAID Manager
and GAM Client simultaneously on the management client PC or Windows server.
You can use the following configuration:
Server
Management Client PC
or
Windows Server
ServerView RAID
Service
Notifying
㪪㪼㫉㫍㪼㫉㪭㫀㪼㫎㩷㪩㪘㪠㪛
Event
Monitoring and
setting the disk array
GAM Client
Monitoring and
setting the disk array
ServerView RAID Manager
Array Controller
Server
GAM Server
Notifying
GAM Event
Array Controller
If ServerView is installed on the management client PC or Windows server, you can start the
ServerView RAID Manager or GAM Client program for a server managed by ServerView by making
use of ServerView's interaction with the RAID Manager. For details about the RAID Manager linking,
see "RAID Manager Linking" in the "ServerView User's Guide".
` When you want to install GAM Client on a Windows server where ServerView RAID is already
installed, install only GAM Client. Do not install GAM Server.
182
MegaRAID SAS User's Guide
5.2 Installing GAM [Windows]
This section explains how to install GAM on a Windows server.
` GAM cannot be installed by overwriting an existing installation. Make sure to uninstall any existing
version of GAM before reinstalling GAM.
` Restart the OS after installing or uninstalling GAM.
` If Service Pack 1 of Windows Server 2003 has been applied, the following message may pop up when
restarting the system just after installing or uninstalling GAM.
A problem has been detected and Windows has shut down to
prevent damage to your computer.
Name:
SNMP Service
There will be no problem with operations. Click [Close] to close the message.
` To record events in OS event logs, make sure to install ServerView and configure the event-logging
settings. For details, see "ServerView User's Guide".
5.2.1 How to Install GAM
Follow the procedure below to install GAM.
1
Log on to Windows with Administrator privileges.
2
Before installing GAM, complete the following preparation:
• Check that TCP/IP is installed and working properly.
• Check that ServerView is installed and working properly.
• Insert the "Array Controller Document & Tool CD" provided with this product into the CD/
DVD drive.
• Exit all application software.
` Exit all application software before starting the installation. In particular, if you install the software while Event Viewer or Computer Management is running, the installation may fail.
3
Click [Start] button – [Run...]. Type the following path and click [OK].
[CD/DVD drive]:\RAIDTOOL\GAM\Windows\install.bat
The [Global Array Manager Setup] wizard starts up.
4
On the [Welcome] screen, click [Next].
The [Software License Agreement] screen appears.
183
Chapter 5 Array Configuration and Management [GAM]
5
Click [Yes].
The [Select Components] screen appears.
Make sure the boxes next to [Global Array Manager Server] and [Global Array Manager Client]
are checked.
6
Select [Global Array Manager Server] and click [Change].
The [Select Sub-components] screen appears.
Make sure [Program Files] and [SNMP] are checked.
7
Confirm the settings and click [Continue].
The [Select Components] screen appears again.
8
Click [Next].
The [Choose Destination Location] screen appears.
9
Click [Next].
The installation location for GAM appears.
` If GAM is already installed, a warning message will appear to confirm overwriting. After clicking
[Cancel] to close the warning message box, click [Cancel] and then [Exit Setup] to quit the
GAM setup. If the command prompt appears, click the [X] button to close the command
prompt. After uninstalling GAM Client and GAM Server, perform the installation again.
184
MegaRAID SAS User's Guide
10
Confirm the installation location and click [Next].
The files are copied.
11
Specify the client receiving events from GAM Server.
In the text box, enter the name of the computer where GAM Client is being installed and click
[Next].
The [Server Event Logging] screen appears.
` If GAM Client is installed on the same computer as GAM Server, enter the name of the server.
` To specify multiple clients receiving events, enter the servers' computer names or IP
addresses separated by spaces. You can specify up to 25 clients receiving events at a time.
` If the IP address or computer name of the Client is changed after GAM Server has been
installed, events cannot be correctly notified. In this case, GAM Server needs to be first uninstalled and then reinstalled.
If the IP address is automatically obtained from the DHCP server, the IP address may be
changed depending on the timing when the system is turned on/off or restarted. If DHCP is
being used, specifying a computer name is recommended.
12
Make sure [Enable event logging on the server machine] is checked and click
[Next].
` This option must be enabled.
13
When the full path name of the configuration file appears, click [OK].
The [Setup Complete] screen appears.
14
Click [Finish] to exit.
Following the message displayed at the command prompt, press the [Enter] key and carry on
processing until the command prompt closes.
15
Restart the system.
185
Chapter 5 Array Configuration and Management [GAM]
16
After the restart, create the user account "gamroot" with GAM Administrator
privileges and a user account with GAM User privileges (e.g. gamuser) as
Windows user accounts.
Assign the user account "gamroot" to the Administrators group.
` When creating the account with GAM Administrator privileges, uncheck the [User must change
password at next logon] checkbox.
Also check the [Password never expires] checkbox.
If you do not make the above settings, you may be unable to sign on to GAM.
` Create each user account as an OS user account.
5.2.2 Uninstalling GAM
Follow the procedure below to uninstall GAM.
` Uninstall GAM only when reinstalling or updating it. Do not operate the server without GAM in general.
„ Uninstalling GAM client
1
Log on to Windows with Administrator privileges.
` Exit all software before starting the uninstallation.
If uninstalling the software while Event Viewer or Computer Management is running, the uninstallation will fail. Make sure to exit all programs.
2
Click [Start] button – [Settings] – [Control Panel].
3
Double-click [Add or Remove Applications] (or [Add or Remove Programs]
depending on the OS).
4
Select [Mylex Global Array Manager Client v.x.xx-xx] from the application list
and click [Change/Remove].
The message "Are you sure you want to completely remove 'Mylex Global Array Manager Client
vx.xx-xx' and all of its components?" appears.
5
Click [Yes].
The uninstallation process starts.
6
186
When the uninstallation is finished, click [OK].
MegaRAID SAS User's Guide
„ Uninstalling GAM server
1
Log on to Windows with Administrator privileges.
` Exit all software before starting the uninstallation.
If uninstalling the software while Event Viewer or Computer Management is running, the uninstallation will fail. Make sure to exit all software.
2
Click [Start] button – [Settings] – [Control Panel].
3
Double-click [Add or Remove Applications] (or [Add or Remove Programs]
depending on the OS).
4
Select [Mylex Global Array Manager Server v.x.xx-xx] from the application list
and click [Change/Remove].
The message "Are you sure you want to completely remove 'Mylex Global Array Manager
Server vx.xx-xx' and all of its components?" appears.
5
Click [Yes].
The uninstallation process starts.
6
When the uninstallation is finished, click [OK].
7
Select [LSI 1030 Storage SNMP Agent] from the application list and click
[Remove].
The message "Are you sure you want to remove LSI 1030 Storage SNMP Agent vx.xx-xx from
your computer?" appears.
8
Click [Yes].
The uninstallation process starts.
9
Select [LSI SWR IDE Storage SNMP Agent] from the application list and click
[Remove].
The message "Are you sure you want to remove LSI SWR IDE Storage SNMP Agent vx.xx-xx
from your computer?" appears.
10
Click [Yes].
The uninstallation process starts.
11
Restart the system.
187
Chapter 5 Array Configuration and Management [GAM]
5.3 Installing HDD Check Scheduler
[Windows]
HDD Check Scheduler is a tool to detect or recover media errors on hard disks, by
periodically performing Make Data Consistent of the media.
This section explains how to install HDD Check Scheduler on a Windows server.
` Make sure to install HDD Check Scheduler. Make sure to install GAM before installing HDD Check
Scheduler.
` If you update GAM, or uninstall and then reinstall it, be sure also to reinstall HDD Check Scheduler
afterwards.
` During the HDD check, the I/O performance for the logical drives decreases to some extent (up to
about 30%). After the installation, set the start time so that the check is performed during non-business
hours, or low-business hours, referring to "5.3.2 Modifying HDD Check Start Time" (Jpg.189).
` When you install HDD Check Scheduler, the check is set to start every day at 12:00 by default.
` For an overview of the HDD Scheduler functions, see "1.3.7 HDD Check Scheduler" (Jpg.36).
` HDD Check Scheduler performs Make Data Consistent periodically using the standard OS scheduling
function ("AT" command for Windows, or Cron for Linux).
` We recommend that you perform the HDD check, at least once a week.
` If the server restarts or shuts down during HDD check, the HDD check is resumed from where it was
stopped the next time.
5.3.1 Installation Procedure for HDD Check Scheduler
Follow the procedure below to install HDD Check Scheduler.
1
Log on to Windows with Administrator privileges.
2
Before installing HDD Check Scheduler, complete the following preparations:
• Check that GAM is installed.
• Check that ServerView is installed and working properly.
• Insert the "Array Controller Document & Tool CD" provided with this product into the CD/
DVD drive.
• Exit all software.
` Exit all software before starting the installation. In particular, if you install the software while
Event Viewer or Computer Management is running, the installation may fail.
188
MegaRAID SAS User's Guide
3
Click [Start] button – [Run...]. Enter the following file name and click [OK].
[CD/DVD drive]:\RAIDTOOL\HDDCS\Windows\install.bat
The message "Installing HDD Check Scheduler" appears at the command prompt.
4
When the message "Installation of HDD Check Scheduler has finished."
appears, press the [Enter] key to close the command prompt.
` When you install HDD Check Scheduler for the first time, the HDD check is set to start every day at
12:00 by default.
` If you reinstall and overwrite HDD Check Scheduler, the previously set start time setting will be kept.
5.3.2 Modifying HDD Check Start Time
The start time for the HDD check can be modified using the "AT" command of the operating system. To
modify the start time, perform the following procedure.
` We recommend that you perform the HDD check regularly, at least once a week.
1
Log on to Windows with Administrator privileges.
2
Click [Start] button – [All Programs] – [Accessories] – [Command Prompt] to
open the command prompt.
3
Type "AT" and press the [Enter] key.
4
Write down the [ID] value for the row with the following value in the
[Command Line] column:
For Windows 2000 Server
C:\WINNT\system32\GAMSERV\HDDchk.bat
For Windows Server 2003
C:\WINDOWS\system32\GAMSERV\HDDchk.bat
For Windows Server 2003 x64
C:\WINDOWS\SysWOW64\GAMSERV\HDDchk.bat
Example: If the "AT" command output is as follows, the ID is 11.
C:\Documents and Settings\Administrator>at
Status ID
Day
Time
Command Line
---------------------------------------------------------------------1
Each M F
10:00 AM
"C:\ProgramFiles\
Fujitsu\F5FBFE01\ServerView Services\WebServer\ClearMyLogs.exe"
11
Each M T W Th F
12:00 PM
C:\WINDOWS\system32\
GAMSERV\HDDchk.bat
189
Chapter 5 Array Configuration and Management [GAM]
5
Delete the currently registered HDD check schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 11 /delete
6
Register a new schedule. Using the "AT" command, register the following
command line together with the time of execution.
For Windows 2000 Server
C:\WINNT\system32\GAMSERV\HDDchk.bat
For Windows Server 2003
C:\WINDOWS\system32\GAMSERV\HDDchk.bat
For Windows Server 2003 x64
C:\WINDOWS\SysWOW64\GAMSERV\HDDchk.bat
To specify the scheduled execution, enter the following "AT" command.
AT <Start Time> /every:<Day of Week> "Command Line"
• To execute the HDD check every Friday at 6 pm, on Windows Server 2003 (except for
Windows Server 2003 x64):
at 18:00 /every:F "C:\Windows\system32\GAMSERV\HDDchk.bat"
• To execute the HDD check every day at 9 pm, on Windows 2000 Server
at 21:00 /every:M,T,W,Th,F,S,Su "C:\WINNT\system32\GAMSERV\
HDDchk.bat"
` To specify the day of the week, use the following abbreviations:
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
M
T
W
Th
F
S
Su
` For details on how to use the "AT" command, see Windows Help.
` To see whether the HDD check is properly executed at the specified time, check that a log
entry is recorded in the OS application log at the specified time. If no log entries are recorded
at the specified time, review the settings.
Source
:
Type
:
EventID
:
Description:
started.
190
Fujitsu ServerView Services
Information
1
Consistency check / Make Data Consistent is
MegaRAID SAS User's Guide
5.3.3 Uninstallation Procedure for HDD Check Scheduler
Follow the procedure below to uninstall HDD Check Scheduler:
1
Log on to Windows with Administrator privileges.
` Exit all software before starting the uninstallation.
If uninstalling the software while Event Viewer or Computer Management is running, the uninstallation will fail. Make sure to exit all software.
2
Click [Start] button – [All Programs] – [Accessories] – [Command Prompt].
A command prompt window opens.
3
4
Type "AT" and press the [Enter] key.
Write down the [ID] value for the row with the following value in the
[Command Line] column:
For Windows 2000 Server
C:\WINNT\system32\GAMSERV\HDDchk.bat
For Windows Server 2003
C:\WINDOWS\system32\GAMSERV\HDDchk.bat
For Windows Server 2003 x64
C:\WINDOWS\SysWOW64\GAMSERV\HDDchk.bat
Example: If the "AT" command output is as follows, the ID is 11.
C:\Documents and Settings\Administrator>at
Status ID
Day
Time
Command Line
---------------------------------------------------------------------1
Each M F
10:00 AM
"C:\Program Files\
Fujitsu\F5FBFE01\ServerView Services\WebServer\ClearMyLogs.exe"
11
Each M T W Th F
12:00 PM
C:\WINDOWS\system32\
GAMSERV\HDDchk.bat
5
Delete the currently registered HDD check schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 11 /delete
191
Chapter 5 Array Configuration and Management [GAM]
5.4 Installing Battery Recalibration
Scheduler [Windows]
Battery Recalibration Scheduler is a tool to periodically perform battery recalibration
for MegaRAID SAS 300-8E ROMB equipped with a battery. This section explains
how to install Battery Recalibration Scheduler on a Windows server.
` When updating GAM (or reinstalling GAM after uninstalling it), make sure to reinstall Battery
Recalibration Scheduler after updating GAM.
` See also "1.3.8 Battery Backup Unit (BBU)" (Jpg.36) before using this tool.
` Recalibration takes 12 hours with the server power on. During recalibration, the logical drive in Write
Back mode shifts automatically to Write Through mode for safety. Therefore, see "5.4.2 Modifying
HDD Check Start Date and Time" (Jpg.193) to set a start date and time that minimizes the effect on
the business.
` MegaRAID SAS 8300XLP does not require the installation of this tool or periodical recalibration.
` Battery Recalibration Scheduler performs recalibration periodically using the standard OS scheduling
function ("AT" command for Windows, or Cron for Linux).
` We recommend that you perform battery recalibration about once a month or every two months.
` If the server restarts or shuts down during battery recalibration, the battery recalibration is resumed
from where it was stopped the next time.
5.4.1 Installation Procedure for Battery Recalibration
Scheduler
Follow the procedure below to install Battery Recalibration Scheduler.
1
Log on to Windows with Administrator privileges.
2
Before installing Battery Recalibration Scheduler, complete the following
preparations:
• Check that GAM is installed.
• Make sure that ServerView is installed and working properly.
• Insert the Array Controller Document & Tool CD provided with this product into the CD/
DVD drive.
• Exit all software.
` Exit all software before starting the installation. In particular, if you install the software while
Event Viewer, Services, or Computer Management is running, the installation may fail.
192
MegaRAID SAS User's Guide
3
Click [Start] button – [Run...]. Enter the following file name and click [OK].
[CD/DVD drive]:\RAIDTOOL\BATRCS\Windows\install.bat
The message "Installing Battery Recalibration Scheduler." appears at the command prompt.
4
When the message "Installation of Battery Recalibration Scheduler has
finished." appears, press the [Enter] key.
The command prompt window closes.
` When you install Battery Recalibration Scheduler for the first time, the recalibration is set to start the
first day of every month at 11:00 by default.
` If you reinstall and overwrite Battery Recalibration Scheduler, the previously set start date and time
settings will be kept.
5.4.2 Modifying HDD Check Start Date and Time
The start date and time for the Battery Recalibration can be modified using the "AT" command of the
operating system. To modify the start date and time, perform the following procedure.
` We recommend that you perform battery recalibration about once a month or every two months.
1
Log on to Windows with Administrator privileges.
2
Click [Start] – [All Programs] – [Accessories] – [Command Prompt] to open the
command prompt.
3
Type "AT" and press the [Enter] key.
4
Write down the [ID] value for the row with the following value in the [Command
Line] column:
For Windows Server 2003 x64
C:\WINDOWS\SysWOW64\GAMSERV\Batrec.bat
For Windows Server 2003
C:\WINDOWS\system32\GAMSERV\Batrec.bat
For Windows 2000 Server
C:\WINNT\system32\GAMSERV\Batrec.bat
Example: If the "AT" command output is as follows, the ID is 4.
C:\Documents and Settings\Administrator>at
Status ID Day
Time
Command Line
---------------------------------------------------------------------3 Each M T 12:00 PM
"C:\WINDOWS\system32\GAMSERV\HDDchk.bat"
4 Each 1
11:00 PM
"C:\WINDOWS\system32\GAMSERV\Batrec.bat"
193
Chapter 5 Array Configuration and Management [GAM]
5
Delete the currently registered Battery Recalibration schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 4 /delete
6
Register a new schedule. Using the "AT" command, register the following
command line together with the date and time of execution.
For Windows Server 2003 x64
C:\Windows\SysWOW64\GAMSERV\Batrec.bat
For Windows Server 2003
C:\windows\system32\GAMSERV\Batrec.bat
For Windows 2000 Server
C:\WINNT\system32\GAMSERV\Batrec.bat
To specify the scheduled execution, enter the following "AT" command.
AT <Start Time> /every:<Date> "Command Line"
To execute the Battery Recalibration every 15th at 8 am, (For Windows Server 2003)
AT 8:00 /every:15 "C:\Windows\system32\GAMSERV\Batrec.bat"
` For details on how to use the "AT" command, see Windows Help.
` To confirm whether battery recalibration is configured correctly, enter "AT" at the command
prompt and check the displayed result.
Check that the date, time, and the command line set in step 6 are correct.
194
MegaRAID SAS User's Guide
5.4.3 Uninstallation Procedure for Battery Recalibration
Scheduler
Follow the procedure below to uninstall Battery Recalibration Scheduler:
1
Log on to Windows with Administrator privileges.
` Exit all programs before starting the uninstallation.
If uninstalling the software while Event Viewer or Computer Management is running, the uninstallation will fail. Make sure to exit all programs.
2
Click [Start] – [All Programs] (or [Programs]) – [Accessories] – [Command
Prompt].
A command prompt window opens.
3
4
Type "AT" and press the [Enter] key.
Write down the [ID] value for the row with the following value in the [Command
Line] column:
For Windows Server 2003 x64
C:\Windows\SysWOW64\GAMSERV\Batrec.bat
For Windows Server 2003
C:\windows\system32\GAMSERV\Batrec.bat
For Windows 2000 Server
C:\WINNT\system32\GAMSERV\Batrec.bat
Example: If the "AT" command output is as follows, the ID is 4. (For Windows Server 200)
C:\Documents and Settings\Administrator>at
Status ID Day
Time
Command Line
--------------------------------------------------------------------- 5
3 Each M T 4 Each 1
12:00 PM
11:00 PM
"C:\WINDOWS\system32\GAMSERV\HDDchk.bat"
"C:\WINDOWS\system32\GAMSERV\Batrec.bat"
Delete the currently registered Battery Recalibration schedule.
Execute the following command:
AT <ID in step 4> /delete
Example: AT 4 /delete
195
Chapter 5 Array Configuration and Management [GAM]
5.5 Starting and Exiting GAM
This section explains how to start and exit GAM.
5.5.1 Starting GAM and Signing On
GAM requires user authentication to limit the availability of functions according to the usage. You have
to sign on to GAM to obtain User access privileges or higher.
` When GAM is started for the first time after the installation, the [Define Server Groups] window
appears. See "5.7.1 Server group and server settings" (Jpg.207) to make the settings.
` Only start GAM Client when management or maintenance of arrays is necessary. From a security point
of view, it is not recommended to run GAM Client continuously. While signing on from GAM Client, if
the accessed server shuts down, GAM Client cannot communicate with GAM Server and cannot
respond, which prevents the user from operating it. In that case, wait for the GAM Server that is to be
accessed to start up again, or forcibly exit GAM Client.
1
To start GAM, click [Start] – [Programs] (or [All Programs] in Windows Server
2003) – [Mylex Global Array Manager Client].
If a server group or server is already defined, [Global Status View] appears.
` GAM starts with Guest privileges. To use User or Administrator privileges, you have to sign on.
2
When you double-click the server icon in the [Global Status View] window, or
perform operations that require the sign on.
` You can also open the [Sign On] window by selecting [Sign on] from the [Administration] menu.
` If the GAM Client and GAM Server are installed on different servers (for a Linux system, etc.),
enter the password for the GAM Server.
196
MegaRAID SAS User's Guide
3
Sign on to GAM.
1. Type your user name.
• When signing on with User privileges
Type a user name in [Username].
• When signing on with Administrator privileges
Type "gamroot" in [Username].
2. Type a password in [Password].
If [Remember password for this session] is checked, uncheck it.
` Note that if this option is checked, you can automatically sign on to different servers with the
same password. To avoid automatically accessing servers, it is recommended to keep this
option unchecked.
Even if this option is checked, you need to sign on again when GAM Client is exited once.
3. Click [Sign-on].
` GAM restricts the availability of functions according to access privileges. For access privileges,
see "5.1.3 Access Privileges to GAM" (Jpg.178).
5.5.2 Exiting GAM
To exit GAM, click [Exit] from [File] in the GAM menu bar.
197
Chapter 5 Array Configuration and Management [GAM]
5.6 GAM Window Layout
The following provides a description of the windows, buttons, and menu items
displayed when using GAM.
5.6.1 Startup Window Layout and Functions
When GAM is started, a window consisting of [Global Status View] and [Log Information Viewer]
appear.
Server Group Selection box
Controller Selection box
Menu bar
Toolbar
Global Status
view
Controller icon
Server icon
Log Information
viewer
„ Menu bar
Allows you to perform GAM functions such as [Controller View and RAID Assist].
For details on the GAM menus, see "5.6.2 Menu Layout and Functions" (Jpg.201).
„ Toolbar
Buttons for frequently used GAM functions.
For details on the toolbar, see "5.6.3 Toolbar Icon" (Jpg.203).
„ Server Group Selection box
The server group names which are registered in GAM Client are displayed. Clicking ▼ switches the
server groups to be managed.
198
MegaRAID SAS User's Guide
„ Controller Selection box
Allows you to select the array controller to be operated. Clicking ▼ displays the onboard array
controller connected to the currently selected server, or the controller ID and type (e.g. MegaRAID SAS
300-8E ROMB) of the array card.
„ Global Status View
Displays the servers in the currently selected server group.
z Server icon
Displays the server status.
Server name (e.g. PRIMERGY) or IP address (e.g. 192.168.1.5)
OS (e.g. W2K3: Windows Server 2003, Linux: Linux)
Status of the server
The server status icon appears as follows.
table: Server status
Icon
Color
Server Status
Green
Normal
Yellow
Waiting for server connection.
Red
The server is down or disconnected. The following are possible causes.
• Network malfunction
• No power on the server
• The server IP or host name has been changed.
• GAM Server is not installed or not running on the server.
199
Chapter 5 Array Configuration and Management [GAM]
z Controller icons
Indicates the array controller status on the servers.
Controller Icons are displayed to the right of the server icons. The numbers in the parentheses show the
numbers of connected array controllers. The array controllers have the following statuses.
table: Array controller status
Icon
Color
Array Controller Status
Green
The array controller and the logical drives under the controller are
operating normally.
Yellow
The array controller and the logical drives under the controller are in
Critical status, or there is trouble with the connected hard disks.
Red
The array controller or the logical drive under the controller is not
operating properly.
„ Log Information Viewer
Displays events on the array controller.
table: Log Information Viewer
Events
Event ID
Details
The level of the event to be reported is indicated with an icon that signifies Information,
Caution, Warning, or Others. The ID assigned to the event being reported is also displayed.
Severity
Priority level of the event.
Source
IP address or name of the server that sent the event.
Source Time
Time when the event occurred.
Device Address
Other data regarding the addresses of related devices, operations in question, and the reason
why the event was sent.
Description
Event description
Sequence (Seq)
Event sequence number
Local Time
Time when the event occurrence was signaled to GAM Client.
` Log Information Viewer only shows events that occur while the GAM Client is running.
To see all the events that have occurred on the array controller, refer to the event log for the operating
system.
200
MegaRAID SAS User's Guide
5.6.2 Menu Layout and Functions
This section describes the function of the GAM menu items.
„ [File] menu
table: [File] menu
Menu
Function
Open Configuration
This function is not supported. Do not use it.
Save Configuration
Saves the current RAID configuration in a file.
For more details, see "„ Saving disk array configuration information" (Jpg.226).
Clear Configuration
Clears all the RAID configurations of the currently selected array controller.
For more details, see "„ Deleting disk array configuration information" (Jpg.227).
` The above menus are only available when you sign on with Administrator privileges to open the
[Controller View].
` Executing [Open Configuration] or [Clear Configuration] deletes the existing array configurations and
all the data on the logical drives. Do not perform these operations unless directed by your maintenance
engineer.
„ [View] menu
table: [View] menu
Menu
Function
Global Status View
Displays the [Global Status View] window.
With the default settings, [Global Status View] opens automatically when GAM starts up.
Controller View
Displays the [Controller View] window. Displays information for each device and the
status of hard disks or logical drives connected to the controller.
Log Information
Viewer
Displays the [Log Information Viewer] window. This window shows events or errors that
occurred in the array controller.
[Log Information Viewer] opens automatically when GAM Client starts up.
Foreground
Initialize Status
Shows the progress of foreground initialization on a logical drive. This can only be
selected while foreground initialization is in progress.
This function is not supported.
Background
Initialize Status
Shows the progress of background initialization on a logical drive. This can only be
selected while background initialization is in progress.
Rebuild Status
Shows the rebuild progress.
This can only be selected while rebuild is in progress.
Make Data
Consistent Status
Shows the Make Data Consistent progress.
This can only be selected while Make Data Consistent is in progress.
Expand Capacity
Status
Shows the capacity expansion process progress.
This can only be selected while a capacity expansion process is in progress.
Note:
` Do not restart or shut down the system while a capacity expansion process is in
progress. Doing so may cause loss of data.
201
Chapter 5 Array Configuration and Management [GAM]
table: [View] menu
Menu
Function
Patrol Read Status
This function is not supported. Do not use it.
Error Table
This function is not supported. Do not use it.
„ [Administration] menu
table: [Administration] menu
Menu
Function
Sign On
Allows you to sign on when using GAM's monitoring and setting functions. Signing on
with a User account registered on the server enables you to use the monitoring function
(available with User privileges). Signing on with "gamroot" enables you to use GAM's
setting and management functions (available with Administrator privileges).
Define Server
Groups
Sets a server group and the names or IP addresses of servers in the group.
Select Current
Server Group
Selects a server group. Functions in the same manner as when the [Server Selection] box is
operated directly.
Note:
` Make sure to select a server group registered with [Define Server Group].
Select Current
Controller
Selects a controller to be managed. Functions in the same manner as when the
[Controller Selection] box is operated directly.
RAID Assist
Sets a disk array configuration. This function enables you to define disk groups and logical
drives.
For details, see "5.8.1 Starting RAID Assist Function" (Jpg.212).
Initialize Logical
Drives
This function is not supported. Do not use it.
Controller
Information
Displays the main information for the currently selected array controller.
Enclosure
Information
Displays SES and SAF-TE Enclosure Management information.
Controller Options
Sets parameters for the currently selected array controller.
For details, see "5.7.2 Setting and Changing Controller Options" (Jpg.208).
Physical Device
Options
This function is not supported. Do not use it.
Intelligent BBU
When the RAID has a battery backup unit, its status appears.
Scan Devices
Detects the hard disks connected again.
Advanced
Functions
Other functions. Selecting this opens a submenu.
Note:
` This function may cause data loss on logical drives.
Note:
` The Enclosure Information function is not supported. Hard disk cabinets cannot
be monitored with this function.
• Flash Utility
Updates the firmware on the array controller.
Note:
` Do not update the firmware except the versions supported by Fujitsu.
202
Settings
This function is not supported. Do not use it.
Alarm Sound
This function is not supported. Do not use it.
Consistency Check
with Restoration
This function is not supported. Do not use it.
MegaRAID SAS User's Guide
5.6.3 Toolbar Icon
The toolbar icons at the top of the [GAM] window enable you to start up frequently used functions.
table: Toolbar icons
Icon
Function
Displays the [RAID Assist] window and starts creating a RAID configuration. Functions in the same
manner as when [RAID Assist] is selected from the [Administration] menu.
Rescans the devices. Functions in the same manner as when [Scan Devices] is executed from the
[Administration] menu.
Displays array controller information. Functions in the same manner as when [Controller Information]
is selected from the [Administration] menu.
This function is not supported. Do not use it.
Opens the [Sign On] window. Functions in the same manner as when [Sign On] is selected from the
[Administration] menu.
This function is not supported.
Displays Help.
203
Chapter 5 Array Configuration and Management [GAM]
5.6.4 Starting Controller View and the Window Layout
The [Controller View] window enables you to monitor the status of hard disks or logical drives.
To open the [Controller View] window, select [Controller View] from the GAM [View] menu
(Jpg.201). If the [Sign On] window opens, sign on referring to "5.5.1 Starting GAM and Signing On"
(Jpg.196).
The following window appears.
The [Controller View] window shows the information below regarding the controller currently selected
in the [Controller Selection] box.
z The number of enclosures connected to controllers.
Each enclosure appears as a tower on the left.
204
MegaRAID SAS User's Guide
z Hard disk
Displays information about each hard disk.
Target ID ("Enclosure ID" and "Hard Disk ID" are not supported for this array
controller. Indefinite values are displayed.)
Capacity of hard disk.
Type and status of hard disk.
The hard disk status icon appears as follows.
table: Hard disk status icon
Icon
Color
Green
Status
Status
Online
(Online)
Normal
Failure / Offline
(Dead /
Unconfigured Bad)
The hard disk has a failure, cannot be recognized, or
cannot be read and written.
Yellow
Rebuild
(Rebuilding)
Rebuild in progress
Green + white
Spare disk
(Hot Spare)
Spare disk
Yellow
Failure expected
(Critical)
Failure expected
Not applied
Unused
(Unconfigured)
Unused or available
Red
` Double-click the icon for each hard disk to see more detailed information. For more details, see "5.9.3
Viewing Hard Disk Information" (Jpg.231).
` If a hard disk is in an unrecognizable state, detailed information may not be displayed even when
double-clicking its hard disk icon.
205
Chapter 5 Array Configuration and Management [GAM]
z Logical drive
Displays information about each logical drive.
Logical Drive ID
RAID Level of logical drive.
Capacity of logical drive.
Status of logical drive.
The logical drive status icon appears as follows.
table: Logical drive status icon
Icon
Color
Status
Description
Green
Online
Normal
Yellow
Critical
Operating without redundancy
Red
Offline
Not available
Make Data
Consistent
Performing Make Data Consistent for the logical drive
Green
` Double-click the icon of each logical drive to see more detailed information. For more details, see "5.9.4
Viewing Logical Drive Information" (Jpg.234).
206
MegaRAID SAS User's Guide
5.7 Settings
This section explains how to set parameters.
The following two items are available:
• Server group and server settings
• Controller option settings
5.7.1 Server group and server settings
The [Server Group Setting] window automatically opens when the GAM Client is started for the first
time. Add a server group and servers according to the following procedures:
1
Click the [Add] button below the [Server Groups] area.
2
Type a name for the server group to be added using the [Adding Item] window.
3
Click [OK].
The added server group name appears in the [Server Groups] area.
4
Select the added server group and click the [Add] button below the [Servers]
area.
The [Adding Item] window appears.
5
Type the name or the IP address of the server computer that you want to
monitor in the [Adding Item] window.
` Do not specify "localhost" or the loopback address "127.0.0.1" as the computer name or the IP
address of the server to be monitored.
6
Click [OK].
The entered server name is added in the [Server] area.
207
Chapter 5 Array Configuration and Management [GAM]
7
Click [OK] to close the [Define Server Groups] window.
Check that the registered server appears in [Global Status View].
` You can also set a server group by selecting [Define Server Groups] from the [Administration] menu
(Jpg.202).
` The maximum number of the servers to be monitored that can be set is 100.
5.7.2 Setting and Changing Controller Options
You can check and change array controller options from [Controller Options] in the [Administration]
menu.
` The controller options must be set within the ranges shown in the following table. You may change only
options specified as default in the table. If the settings are outside of the specified ranges, correct
operation may not be ensured.
„ Controller Options tab
208
MegaRAID SAS User's Guide
table: Array controller properties (set with Controller Options tab)
Options
Global
Parameters
Startup
Parameters
Parameter
Setting
Description
Enable Automatic Rebuild
Management
Enable
Cannot be
changed
Enables automatic rebuild after
hard disk replacement.
Rate
80
Default
Sets the rebuild priority for
normal I/O.
Enable Background
Initialization
Enable
Fixed
Enables the background
initialization function.
Rate
80
Default
Sets the background initialization
priority for normal I/O.
Check Consistency / Make
Data Consistent Rate
80
Default
Sets the Make Data Consistent
priority for normal I/O.
MORE Rate
80
Default
Sets the Expand Capacity priority
for normal I/O.
Enable Auto Drive Sizing
Disable
Fixed
Enables rounding of the hard disk
capacity.
Disk Spin-up
On Command
Fixed
Not supported
Devices per Spins
2
Cannot be
changed
Sets the number of hard disks that
start rotating at the same time.
Initial Delay
0
Fixed
Not supported
Delay Between Spins
6
Cannot be
changed
Specifies the rotation start interval
between hard disks.
Clustering
Parameters
Enable Clustering
Disable
Fixed
Not supported
Controller Host ID
0
Fixed
Not supported
Cache Line
Size (MB)
User Selected
16
Fixed
Not supported
Active
16
Fixed
Not supported
` While increasing the values for Rebuild Rate, Background Initialization Rate, Make Data Consistent
Rate and More Rate increases background task performance, it may also decrease the rate of normal
I/O.
209
Chapter 5 Array Configuration and Management [GAM]
„ Advanced tab
Selecting the [Advanced] tab enables you to set [Advanced] options.
table: Array controller properties (set with the [Advanced] tab)
Options
Parameter
Setting
Description
Temporarily
Offline
RAID Array
Enable
Disable
Fixed
Not supported
Device
Health
Monitoring
(S.M.A.R.T/
I.E.C)
Enable Polling
Enable
Fixed
Enables the hard disk failure
prediction (S.M.A.R.T.) function.
Polling Interval
300
Cannot be
changed
Specifies a polling interval for
S.M.A.R.T detection.
Patrol Read
Start Automatically on
Start Up
Disable
Cannot be
changed
Not supported
Delay between Iterations
168
Default
Not supported
` Apart from the controller options, you may be required to make various settings on the server itself.
See "User's Guide" on "PRIMERGY Startup Disc" provided with the server on how to set up the server.
210
MegaRAID SAS User's Guide
5.7.3 Configuring Battery Backup Unit
You can change and check the operation mode of the battery backup unit.
The settings will be automatically corrected after RAID management tool installation.
1
Start up GAM Client and sign on with Administrator privileges.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Intelligent BBU] from the [Administration] menu.
The following window appears.
3
Select "Disable" from [Auto Learn Mode].
table: Intelligent battery backup unit properties
Options
Auto Learn Mode
4
Setting
Disabled
Setting
value
during the
operation
Description
This item sets the battery recalibration mode. Make sure
to set it to "Disable".
Click [Cancel].
The settings of [Auto Learn Mode] are reflected and the window closes.
211
Chapter 5 Array Configuration and Management [GAM]
5.8 Operating RAID Configuration
To create a new disk group or logical drive with GAM, use the RAID Assist function.
RAID Assist enables you to create or add an array configuration, expand the capacity
and set hot spares.
` Disk array operations require signing on with Administrator privileges.
5.8.1 Starting RAID Assist Function
You can start RAID Assist by selecting [RAID Assist] from the [Administration] menu.
The following window appears.
` You cannot use the RAID Assist function while rebuilding, expanding the capacity, or running the Make
Data Consistent.
` Operating RAID Assist may cause loss of the disk array configuration or data files. Read the manual
carefully before use.
` Automatic Configuration and Assisted Configuration are not supported. Do not use them. Use Manual
Configuration to create a RAID configuration.
` RAID Assist cannot configure the RAID 10 logical drive. To configure the RAID 10 logical drive, use
WebBIOS.
J"2.3.1 Creating Disk Array Configuration" (pg.63)
212
MegaRAID SAS User's Guide
„ Manual Configuration
To start setting the array configuration, click [Manual Configuration].
The following window appears.
z Edit Configuration
Used for setting/releasing a hot spare or for deleting a logical drive.
` Do not use Edit Configuration for any other purposes than to delete a logical drive or to set/release a hot
spare.
z New Configuration
Deletes the old array configuration and data (if any) and applies a new array configuration to the array
controller. This function is used when no array configuration exists on the array controller, or when
creating a new array configuration after deleting the existing array configuration completely.
` Executing New Configuration deletes the existing configuration information. Use this function with
caution since it will delete all the existing logical drives and the data inside.
z Delete Logical Drives
Not supported. Do not use it. Use [Edit Configuration] to delete logical drives.
z Add Logical Drive
Used for setting up an additional logical drive while keeping the existing array configuration as is. One
or more logical drives must be set for the selected array controller, and there must be free space on an
unused (Unconfigured) hard disk or in a disk group.
213
Chapter 5 Array Configuration and Management [GAM]
z Expand Arrays
To expand the logical drive's capacity, an unused (Unconfigured) hard disk is added to an existing disk
group and data on the drive are reconfigured. The data on the logical drive to be expanded will not be
destroyed.
5.8.2 Creating New Disk Array Configuration (New
Configuration)
To create a new array configuration, or to create a new array configuration after completely deleting the
existing array configuration, perform the following procedure:
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [RAID Assist] from the [Administration] menu.
The [RAID Assist] window appears.
3
Click [Manual Configuration].
The [Manual Configuration] window appears.
4
Click [New Configuration].
The following window appears. At this point, create a disk group.
The disk group appears in the [Disk Arrays] area at the top left of the window.
Drag & Drop required hard disks.
A list of unused hard disks appears in the [Unused Disk Drives] area at the bottom of the window.
Select an unused hard disk from the above list and drag it to the [Disk Array A0] area. The
dragged-and-dropped hard disk will become part of the disk group A0.
A maximum of 32 hard disks can be added to one disk group.
` When selecting unused hard disks, you can select multiple hard disks at a time by holding
down the [Ctrl] key during the selection.
` For RAID 1 arrays, only two hard disks can be used in one disk group.
214
MegaRAID SAS User's Guide
` Do not use the [Add Array] at this point. To create multiple disk groups, use [Add Logical Drive]
after completing this procedure.
` Use hard disks of the same capacity and type in one disk group. If a mixture of different hard
disks are connected, check them in advance referring to "5.9.3 Viewing Hard Disk Information"
(Jpg.231).
Removing hard disks from the disk group
You can remove hard disks from the disk group by dragging them from the [Disk Arrays] area
and dropping them into the [Unused Disk Drives] area.
Undoing the configuration
Click [Clear All] if you want to reconfigure a disk group from the beginning. All the settings are
cleared.
Setting a Spare Disk
Select an unused hard disk and click [Make Spare]. The icon of the unused hard disk changes to a
spare disk icon.
To release a spare disk, select a spare disk and click [Remove Spare].
` Do not drag a hard disk assigned as a spare disk into the [Disk Arrays] area.
` Use a spare disk of the same capacity and type as the hard disks in the disk group.
` When there are two or more disk groups that use different hard disks, set a spare disk for each
type of hard disk.
5
When the creation of the disk group is completed, click the [Logical Drives] tab
to configure the logical drives.
1. Select a RAID level for the logical drive.
Click ▼ under [RAID Level] and select the RAID level for the logical drive from the
displayed list.
` GAM cannot configure the RAID 10 logical drive. To configure the RAID 10 logical drive, use
WebBIOS.
J"„ How to create disk array configuration" (pg.64)
215
Chapter 5 Array Configuration and Management [GAM]
2. Type the capacity of the logical drive to be created in [Capacity-Logical], or enter
the physical capacity to be used in [Capacity-Physical].
When creating only a single logical drive in the disk array, or when creating the last logical
drive in the disk group, do not change the default size. When creating multiple logical
drives, enter a smaller value than the entire capacity to leave the required capacity for the
others.
` Type the size in either of the two capacity fields. When a value is entered in one field, the other
value is automatically calculated and displayed.
` The capacity of the logical drive may be automatically adjusted to match the block size.
` Do not add multiple logical drives at a time. To create multiple logical drives in a single disk
group, use the [Add Logical Drive] function (Jpg.217) after completing this procedure.
If multiple logical drives are created in a single disk group, you cannot expand the capacity with
the [Expand Capacity] function later.
3. Check the [Write Cache] checkbox to use the logical drive as a write-back drive.
` Before using write-back drives, see "1.3.1 Write Policy" (Jpg.26).
` If there is no battery backup unit, the logical drive is created in Write Through mode even if
[Write Cache] is enabled. To use a logical drive in Write Back mode, see "5.8.7 Changing the
Write Policy" (Jpg.225) and change the write mode settings after creating the logical drive.
4. Check that the other parameters are set to the following values.
If any difference is found, reset the settings as follows:
table: Parameter settings
Parameter
Setting
Init Drive?
Disabled
Stripe Size
64 KB
Read Control
Normal
Direct I/O
Enabled
` This array controller does not support the foreground initialization function on the OS side.
Logical drives with redundancy are automatically initialized with background initialization.
6
216
Click [Add Drive] to register the new logical drive.
MegaRAID SAS User's Guide
7
Click [Apply] to enable the disk array configuration.
When Write Cache is enabled
When Write Cache is enabled, the following confirmation window appears. Click [YES].
A final confirmation window appears.
8
Type "YES" and click [OK].
A new disk array configuration is created.
9
A message that the logical drive is available appears. Click [OK] to exit.
5.8.3 Adding Logical Drive to Existing Disk Array
Configuration (Add Logical Drive)
The following explains the procedures for adding a new logical drive to the existing disk array
configuration. To add a new logical drive, it is necessary to have either an unused drive or free space in
the existing disk group.
Below is the procedure for executing Add Logical Drive.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [RAID Assist] from the [Administration] menu.
The [RAID Assist] window appears.
3
Click [Manual Configuration].
The [Manual Configuration] window appears.
217
Chapter 5 Array Configuration and Management [GAM]
4
Click [Add Logical Drive].
The [Disk Arrays] tab window appears.
` If there is free space in the defined disk group, the [Logical Drives] tab appears. In this case,
see "5.8.2 Creating New Disk Array Configuration (New Configuration)" (Jpg.214) and follow
the procedure from step 5 to assign logical drives.
5
Click [Add Array] to configure a new disk group.
An empty disk group is added in the [Disk Arrays] area.
6
Select an unused hard disk from the [Unused Disk Drives] area and drag it to
the [Disk Arrays] area.
The dragged hard disk will become part of the disk group.
A maximum of 32 hard disks can be added to one disk array.
` When selecting unused hard disks, you can select multiple hard disks at a time by holding
down the [Ctrl] key during the selection.
` For RAID 1 arrays, only two hard disks can be used in one disk group.
` To remove hard disks from the disk group, drag them from the [Disk Arrays] area and drop
them into the [Unused Disk Drives] area.
` Do not add multiple disk groups at a time. To create an additional disk group, complete this
procedure, apply the configuration, and then perform Add Logical Drive again.
` Use hard disks of the same capacity and type in one disk group. If a mixture of different hard
disks are connected, check them in advance referring to "5.9.3 Viewing Hard Disk Information"
(Jpg.231).
Setting a Spare Disk
Select an unused hard disk and click [Make Spare].
The icon of the unused hard disk changes to a spare disk icon.
To release a spare disk, select the spare disk to be released and then click [Remove Spare].
218
MegaRAID SAS User's Guide
` Do not drag a hard disk assigned as a spare disk into the [Disk Arrays] area.
` Use a spare disk of the same capacity and type as the hard disks in the disk group.
` When there are two or more disk groups that use different hard disks, set a spare disk for each
type of hard disk.
7
When the configuration of the disk group and the spare disks are finished, click
the [Logical Drives] tab to start configuring logical drives.
The procedure for configuring logical drives is the same as the one for configuring a new disk
array. See "5.8.2 Creating New Disk Array Configuration (New Configuration)" (Jpg.214) and
follow the procedure from step 5.
5.8.4 Expanding Capacity of Logical Drive (Expand Array)
You can expand the capacity and change the RAID level for existing logical drives.
` There are certain conditions to note and precautions to take for capacity expansion. Read "1.3.5
Capacity Expansion" (Jpg.33) carefully before the capacity expansion.
` The capacity of the RAID10 logical drive cannot be expanded.
1
To prepare for unexpected problems, perform data backup.
2
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
3
Perform Make Data Consistent (Jpg.239) on the logical drive whose capacity is
to be expanded and confirm that the check is completed successfully.
` If the Make Data Consistent is not completed successfully, do not perform capacity expansion.
4
Select [RAID Assist] from the [Administration] menu.
The [RAID Assist] window appears.
5
Click [Manual Configuration].
The [Manual Configuration] window appears.
219
Chapter 5 Array Configuration and Management [GAM]
6
Click [Expand Array].
The following window appears.
7
Select the logical drive to be expanded and click [OK].
The [Disk Arrays] tab window appears.
8
Select an unused hard disk from the [Unused Disk Drives] area and drag it to
the disk group displayed at the top left of the window.
You can add hard disks until the total number of drives in the disk group reaches 32.
` Make sure that the number of hard disks in the disk group does not exceed 32.
` Use additional hard disks of the same capacity and type as the existing hard disks in the disk
group. If a mixture of different hard disks are connected, check them in advance referring to
"5.9.3 Viewing Hard Disk Information" (Jpg.231).
220
MegaRAID SAS User's Guide
9
10
When the addition of the hard disk to the disk group is finished, click the
[Logical Drives] tab to start configuring the logical drive.
Select a RAID level for the logical drive.
Click ▼ under [RAID Level] and select the RAID level for the logical drive from the displayed
list.
After the expansion, the RAID level of the logical drive will be converted to the RAID level
selected here.
` If you convert a RAID 1 or 5 logical drive to RAID 0, note that the logical drive will lose its
redundancy.
` Do not change the Stripe Size.
11
Click [Apply].
When the following confirmation window appears, click [YES].
A final confirmation window appears.
12
Type "YES" and click [OK].
A window showing the progress of the capacity expansion appears and the expansion process
starts. Wait until the process is completed.
221
Chapter 5 Array Configuration and Management [GAM]
` Do not turn off, reset or restart the server while capacity expansion is in progress. Doing so may cause
loss of data in the target logical drive.
` If the server is turned off during capacity expansion, access to the hard disk is automatically resumed
after the server restarts. In this case, wait until the access lamp on the hard disk turns off to ensure that
no access is made to the hard disk, redo the array configuration, and then restore the data backed up
before the expansion.
` If the RAID level of the logical drive after the expansion has data redundancy (that is RAID 1 or RAID
5), background initialization will be performed after the capacity expansion is completed.
5.8.5 Deleting Existing Logical Drive (Edit Configuration)
Use [Edit Configuration] to delete logical drives.
` The [Delete Logical Drive] function in [Manual Configuration] is not supported. Do not use it.
` Do not use [Edit Configuration] for operations other than deleting a logical drive or setting/releasing
spare disks. To create a disk group or logical drives, use [New Configuration] or [Add Logical Drive].
` Make sure to back up data before you delete a logical drive.
` You can only delete the last created logical drive (the drive with the highest number).
` For how to delete all logical drives (i.e. to clear an array configuration), see "5.8.8 Saving and Deleting
Disk Array Configuration Information" (Jpg.226).
1
To prepare for unexpected problems, perform data backup.
2
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
3
Select [RAID Assist] from the [Administration] menu.
The [RAID Assist] window appears.
4
Click [Manual Configuration].
The [Manual Configuration] window appears.
5
Click [Edit Configuration].
When the [Disk Arrays] tab appears, click the [Logical Drives] tab to display a list of the
currently defined logical drives.
` Do not change the disk group configuration on the [Disk Arrays] tab. If you change the disk
group configuration, all the existing logical drives will be deleted. Should the disk group configuration be accidentally changed, click [Cancel] and restart the procedure.
222
MegaRAID SAS User's Guide
6
Click [Delete Drive].
One logical drive will be deleted at a time in descending order from the last in the list.
` Do not click [Clear All]. If you click [Clear All], all the logical drives are deleted at once. Should
the wrong logical drive be deleted, click [Cancel] and start again from the beginning.
7
When completing deletion of logical drives from the list, reconfirm that you
haven't deleted any wrong drives. If everything is OK, click [Apply].
The following warning message appears.
8
Click [Yes].
A final confirmation window appears.
9
Type "YES" and click [OK].
` Should you accidentally delete the wrong logical drives, recreate the array configuration, and
then restore the data backed up before the deletion.
` If all the logical drives in a disk group are deleted, the disk group will also automatically be
deleted, and the hard disks that composed that disk group will be marked as unused.
5.8.6 Setting and Releasing Spare Disk (Edit Configuration)
This section explains how to set and release spare disks.
` Do not use [Edit Configuration] for any other operations than deleting a logical drive or setting/
releasing spare disks. To create a disk group or logical drives, use [New Configuration] or [Add Logical
Drive].
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
223
Chapter 5 Array Configuration and Management [GAM]
2
Select [RAID Assist] from the [Administration] menu.
The [RAID Assist] window appears.
3
Click [Manual Configuration].
The [Manual Configuration] window appears.
4
Click [Edit Configuration].
The [Disk Arrays] tab window appears.
5
Select an unused hard disk in the [Unused Disk Drives] area and click [Make
Spare].
The icon of the unused hard disk changes to a spare disk icon.
To release a spare disk, select a spare disk icon and click [Remove Spare].
` If a disk group exists that consists of hard disks with a capacity larger than that of the hard disk
to be set as a spare disk, the following message appears when you click [Make Spare]. Click
[OK].
` Do not drag a spare disk or an unused hard disk into the [Disk Arrays] area.
` Use a spare disk of the same capacity and type as the hard disks in the disk group.
` When there are two or more disk groups that use different hard disks, set a spare disk for each
type of hard disk.
6
When the configuration of the spare disk is completed, confirm that the existing
logical drives displayed on the right side have not been changed.
If everything is OK, click the [Logical Drives] tab.
7
Click [Apply].
A final confirmation window appears.
8
224
Type "YES" and click [OK].
MegaRAID SAS User's Guide
5.8.7 Changing the Write Policy
For this array controller, you can configure the write policy for each logical drive.
To change the write policy of a logical drive, perform the following procedure.
` Before using write-back, see "1.3.1 Write Policy" (Jpg.26) and make sure that you understand the
idea.
` If the write policy is set to "Enabled (Write Back)" when the battery is not installed, the "BadBBU" mode
is set on WebBIOS. For details about "BadBBU", see "„ Notes on Write Back (or Bad BBU)"
(Jpg.27).
` If the write policy is changed on GAM when the battery is installed, it is switched between the "Write
Through" mode and the "Write Back" mode by default. However, if the "BadBBU" mode is set on
WebBIOS, it is switched between the "WriteThrough" mode and the "BadBBU" mode when seeing
from GAM. To set the "Write Back" mode again, change the write policy on WebBIOS.
` To use the "BadBBU" mode when the battery is installed, change the write policy on WebBIOS.
` When the battery is failed or the write policy is set to "Write Back" during battery reconditioning,
"Disabled" appears as Write Cache and not changed. It is automatically changed to "Enabled" when
the battery is reconditioned.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller View] from the [View] menu.
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
3
Double-click the icon of the logical drive that you want to change the write
policy for in the [Controller View] window.
The [Logical Drive Information] window appears.
225
Chapter 5 Array Configuration and Management [GAM]
4
The current write policy appears in the [Write Cache] field of the [Logical Drive
Information] window.
• Disabled: Operating in Write Through mode
• Enabled: Operating in Write Back or Bad BBU mode
5
Click the [Enable Write Cache] or [Disable Write Cache] button at the bottom of the
window.
The write policy changes to the alternative mode.
5.8.8 Saving and Deleting Disk Array Configuration
Information
Disk array configuration information refers to the information created when the disk array is configured,
such as the disk group or logical drive capacity, RAID level, and which hard disk belongs to which disk
group.
„ Saving disk array configuration information
You can save the current disk array configuration information on a floppy disk or a hard disk.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Save Configuration] from the [File] menu.
3
Type a file name and click [Save As].
The current disk array configuration information is saved as a file.
226
MegaRAID SAS User's Guide
„ Deleting disk array configuration information
You can delete disk array configuration information.
` Do not delete disk array configuration information unless instructed by your maintenance engineer. All
data on the logical drives will be lost by this operation.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Clear Configuration] from the [File] menu.
When the following confirmation window appears, click [YES].
If you want to quit deleting the disk array configuration information, click [No].
A final confirmation window appears.
3
Type "YES" and click [OK].
The disk array configuration information is deleted.
227
Chapter 5 Array Configuration and Management [GAM]
5.9 Viewing Information [GAM]
The following information can be viewed using GAM.
• Information about events or errors that have occurred: "Appendix B List of GAM Event Log"
(Jpg.304)
• Array configuration or controller information: "5.9.2 Viewing Array Controller Information"
(Jpg.230)
• Hard disk information: "5.9.3 Viewing Hard Disk Information" (Jpg.231)
• Logical drive information: "5.9.4 Viewing Logical Drive Information" (Jpg.234)
• Information about tasks running in the background: "5.9.5 Checking Progress of Background Tasks"
(Jpg.236)
5.9.1 Events
GAM monitors the operation of array controllers and hard disks connected to the controllers. If a
behavior that should be treated as an event (a serious event such as a hard disk failure or an event related
to spare disk allocation) is found, GAM is notified of that event.
Events such as disk array system errors, information, or management tasks are displayed in the [Log
Information Viewer].
` For monitoring array controllers, use the OS event log (the application log; Source: Fujitsu ServerView
Services). However, if the GAM Client has not been started, or if the network has a failure,
[Log Information Viewer] cannot monitor the log for events that occur in the array controller.
` Although the event log notified by GAM (source: gamevlog) is recorded, ignore it since it is not
supported. Also, if there are logs for the array controller which are notified by ServerView around the
event log, refer to them. For the list of logs notified by ServerView, see "Appendix B List of GAM Event
Log" (Jpg.304).
` To enter events or errors into the event logs of the operating system, it is necessary to install
ServerView. See "User's Guide" in "PRIMERGY Startup Disc" supplied with the server to install and
configure ServerView.
` The GAM Server records detailed information about occurred events in the file "GAMEVLOG.LOG".
This file may be used when investigation is necessary. (Viewing or monitoring of this file is not
supported.) The path where "GAMEVLOG.LOG" is stored is as follows, depending on the OS:
228
For Windows 2000 Server
C:\WINNT\system32\GAMSERV\GAMEVLOG.LOG
For Windows Server 2003
C:\Windows\system32\GAMSERV\GAMEVLOG.LOG
For Windows Server 2003 x64
C:\Windows\SysWOW64\GAMSERV\GAMEVLOG.LOG
For Linux
/var/log/gamevlog.log
MegaRAID SAS User's Guide
` While GAM Client is running, if the IP address of the server to be monitored is changed or the LAN
connection is disconnected, the "Lost connection to server, or server is down" message will be
recorded every 10 minutes. In such cases, confirm the network status and that the GAM Server is
working properly, and then restart the GAM Client.
„ Log Information Viewer
Log Information Viewer is automatically displayed when the GAM Client is started and an array
controller is detected.
` The event histories displayed in the Log Information Viewer are stored in the file GAM2CL.LOG.
This file may be used when investigation is necessary. (Viewing or monitoring of this log file is not
supported).
GAM2CL.LOG is stored in the following locations.
For Windows Server 2003,
Windows 2000 Server
C:\Program Files\Mylex\Global Array Manager Client\gam2cl.log
For Windows Server 2003 x64
C:\Program Files (x86)\Mylex\Global Array Manager Client\gam2cl.log
To manually open the Log Information Viewer, select [Log Information Viewer] from the [View] menu.
For the meaning of each item displayed in the Log Information Viewer, see "5.6.1 Startup Window
Layout and Functions" (Jpg.198).
„ Displaying detailed information about each event
When detailed information about an event displayed in Log Information Viewer is needed, open the
[Event Information] window.
To open the [Event Information] window, double-click the event in the Log Information Viewer.
Detailed information about the selected event appears.
` Click [OK] to close the window.
229
Chapter 5 Array Configuration and Management [GAM]
5.9.2 Viewing Array Controller Information
„ Using Controller View
Using Controller View, you can view the status of the array controller and the hard disks or logical
drives connected to the controller. For how to start Controller View, and for details about its icons, see
"5.6.4 Starting Controller View and the Window Layout" (Jpg.204).
„ Displaying detailed information about array controllers
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller Information] from the [Administration] menu.
The [Controller Information] window appears.
` You can configure controller options by clicking [Controller Options].
For details about the controller options, see "5.7.2 Setting and Changing Controller Options"
(Jpg.208).
` Click [Close] to close the window.
230
MegaRAID SAS User's Guide
„ Detailed information about array controllers
The following information appears.
table: Detailed Information about array controllers
Item
Description
Model
The model name of the array controller.
Firmware Version
The version of the array controller's firmware.
Intelligent BBU
Indicates whether there is a battery backup unit for the array controller.
Package Version
The version of the array controller's package.
BIOS Version
The version of the array controller's BIOS.
Cache Size
The cache size of the array controller.
FlashROM Size
The size of the array controller's FlashROM.
Bus Type
The type of the host-side bus.
Channels
This item is not supported.
Physical Devices
The number of hard disks connected to the array controller.
Max. Physical Devices
This item is not supported.
Logical Drives
The number of logical drives.
Max. Logical Drives
This item is not supported.
Bus
The bus number for the array controller.
Device #
The device number for the array controller.
IRQ
The IRQ number.
5.9.3 Viewing Hard Disk Information
Using Controller View, you can view detailed information about the hard disks connected to the
controller.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller View] from the [View] menu.
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
` Each drive column indicates the hard disks connected to each enclosure or to each channel of
the controller.
231
Chapter 5 Array Configuration and Management [GAM]
3
Double-click the icon for the hard disk to see the information about it.
Detailed information about the selected hard disk appears.
` The channel, target and LUN information displayed in the title bar is not supported.
` Click [Close] to close the window.
„ Detailed information about hard disks
The following information appears.
table: Detailed information about hard disks
Item
Description
Vendor
Information about the hard disk vendor.
Product
Product model name of the hard disk.
Revision
The version of the hard disk's firmware.
Bus Width
The bus width. The value for this array controller is "Serial".
Sync / Linked / Soft Reset /
CmdQue / ANSI Version
These items are not supported.
Serial
Serial number of the hard disk.
Enclosure
Enclosure ID that the hard disk is connected to.
Slot
The slo numbert where the hard disk is installed.
Nego. Transfer Speed
This item is not supported.
Nego. Bus Width
The current bus width. The value for this array controller is "Serial".
Sector Size
The sector size.
Physical Capacity
The physical capacity of the hard disk.
Config. Size
The hard disk's available capacity when connected to this array controller.
Status
The current status of the hard disk.
For details about the status, see "z Hard disk" (Jpg.205).
232
MegaRAID SAS User's Guide
table: Detailed information about hard disks
Item
Description
Soft Errors / Parity Errors /
Hard Errors / Misc Errors
These counters are not supported.
(The number of recovery attempts made by the array controller for temporary or
minor errors. This can be ignored unless the hard disk gets a failure status.)
PFA Count
The counter for the S.M.A.R.T. failure predictions for the hard disk.
„ Function buttons
You can perform the following operations using the buttons.
• [Rebuild] button
This button is enabled only when the status of the hard disk is Failure.
Click this button to perform rebuild of the hard disk.J"5.10.2 Rebuild" (pg.240)
• [Make Ready] button
Not supported.
` Do not use the [Make Ready] button unless instructed by your maintenance engineer.
• [Make Online]/[Make Offline] button
Forcibly changes the status of the hard disk to "Online" or "Offline".
` Do not use the [Make Online] or [Make Offline] button unless instructed by your maintenance
engineer. In particular, always use the rebuild operation to restore "Online" status of the hard
disk that has become "Offline". This operation may cause loss of data.
• [Locate] button
Blinks the failure LED of the hard disk to indicate the disk's location.
• [ReplaceMissing] button
Reassigns a hard disk to the disk group.
` Do not use the [ReplaceMissing] button unless you are instructed to do so by your maintenance engineer.
• [Close] button
Closes the detailed hard disk information window.
233
Chapter 5 Array Configuration and Management [GAM]
5.9.4 Viewing Logical Drive Information
Using Controller View, you can view detailed information about the defined logical drives.
The logical drives are displayed to the right in the [Controller View] window. Each icon represents one
logical drive.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller View] from the [View] menu.
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
3
Double-click the icon of a logical drive to see the information about it.
Detailed information about the selected logical drive appears.
` The logical drive number appears on the title bar.
` Click [Close] to close the window.
234
MegaRAID SAS User's Guide
„ Detailed information about logical drives
The following information appears.
table: Detailed information about logical drives
Item
Description
RAID Level
The RAID level set for the logical drive.
Fault Tolerant
Indicates whether the logical drive has a redundancy feature or not.
Optimized for Speed
The setting whether the priority of logical drive's RAID level is placed on speed or
not.
Optimized for Capacity
The setting whether the priority of logical drive's RAID level is placed on capacity or
not.
Logical Size
The logical size of the logical drive.
Physical Size
The physical size of the logical drive.
Stripe Size
The striping size used by the logical drive.
Status
The current status of the logical drive.
For details about the status, see "z Logical drive" (Jpg.206).
Write Cache
The current write policy set for the logical drive.
• Disabled: Write Through mode
• Enabled: Write Back or Bad BBU mode
Read Control
This item is not supported.
I/O Control
This item is not supported.
Used Array Capacity
Displays the ratio of the logical drive's capacity to the disk group's total capacity.
` The RAID 10 logical drive is displayed as RAID 1 on GAM. In the case of the RAID 10 logical drive, two
or more disk groups are displayed on the graph of Used Array Capacity.
„ Function buttons
You can perform the following operations using the buttons.
• [Locate] button
Blinks the failure LED of all the hard disks that compose the logical drive to indicate their locations.
• [Make Data Consistent] button
Starts the Make Data Consistent. For details, see "5.10.1 Make Data Consistent" (Jpg.239).
• [Enable Write Cache] / [Disable Write Cache] button
Changes the write policy of the logical drive. The available button depends on the current write
policy. For details, see "5.8.7 Changing the Write Policy" (Jpg.225).
• [Show Bad Data Blocks] button
Not supported.
• [Close] button
Closes the detailed logical drive information window.
235
Chapter 5 Array Configuration and Management [GAM]
5.9.5 Checking Progress of Background Tasks
There are four kinds of background tasks: initialization, rebuild, Make Data Consistent and capacity
expansion. GAM enables you to check the progress of these tasks with progress bars.
From the pace of the progress bar, you can figure out approximately how long the task will take from
start to finish.
„ Background Initialization Status
When the background initialization of a logical drive is in progress, you can check its progress by
selecting [Background Initialize Status] from the [View] menu.
You can cancel the initialization of logical drives by checking the [Cancel] checkbox for each logical
drive and clicking [Cancel].
Click [Close] to close the [Background Initialize Status] window.
` The color of the background task progress bar is different for each logical drive.
` Even if you cancel the background initialization, it is automatically restarted after a certain interval.
„ Rebuild Status
When rebuild is in progress, you can check its progress by selecting [Rebuild Status] from the [View]
menu.
Click [Close] to close the [Rebuild Status] window.
236
MegaRAID SAS User's Guide
` When there are multiple logical drives assigned to a disk group, the rebuild begins from the logical
drive with the lowest number in ascending order. For example, when two logical drives 0 and 1 are
assigned to one disk group, after the rebuild of the logical drive 0 is completed 100%, the rebuild of the
logical drive 1 starts from 0%.
` Do not cancel the rebuild.
„ Make Data Consistent Status
When the Make Data Consistent is in progress, you can check its progress by selecting [Make Data
Consistent Status] from the [View] menu.
You can cancel the Make Data Consistent of logical drives by checking the [Cancel] checkbox for each
logical drive and clicking [Cancel].
Click [Close] to close the [Consistency Check Status] window.
„ Expand Capacity Status
When a capacity expansion is in progress, you can check its progress by selecting [Expand Capacity
Status] from the [View] menu.
Click [Close] to close the [Expand Capacity Status] window.
` Do not restart or shut down the system while a capacity expansion process is in progress. Doing so
may cause data loss.
` Do not perform any other GAM operations while a capacity expansion process is in progress.
237
Chapter 5 Array Configuration and Management [GAM]
„ Calculating approximate time needed for a background task
For background initialization, rebuild, Make Data Consistent, and capacity expansion, you can figure
out approximate time that the task takes from start to finish from the pace of the progress bar.
1
2
Measure the period of time required for the progress bar to advance 1%.
Calculate the approximate time that the task takes from start to finish, using the
following formula.
For background initialization, making data consistency, and capacity expansion:
(Period measured in step 1) × 100
For Rebuild:
(Period in step 1) × 100 × (total LD capacity in DG / capacity of LD in rebuild)
* DG: Disk Group, LD: Logical Drive
` Use the calculated time only as a guideline. The actual time may be different from the calculated time
depending on the system load and other factors.
238
MegaRAID SAS User's Guide
5.10Maintenance Functions
GAM provides the following maintenance functions.
• Making data consistency for logical drive (Make Data Consistent)Jpg.239
• Rebuilding offline hard disks (Rebuild)Jpg.240
5.10.1 Make Data Consistent
Make Data Consistent, also called redundant data regeneration, is a function that regenerates the parity
or mirrored data on redundant logical drives and makes the array structure consistent.
When the OS does not shut down properly because of a server failure or a power failure, the array may
become inconsistent. In this case, perform this function as early as possible.
` Make Data Consistent can be performed on redundant logical drives, i.e. RAID 1, RAID 5, or RAID10
logical drives in online status. Make Data Consistent cannot be performed on logical drives without
redundancy, i.e. RAID 0 logical drives or logical drives in critical/offline status.
` In addition to keeping the data consistent, the Make Data Consistent also automatically corrects any
media errors on the hard disks.
` Make Data Consistent can be performed simultaneously for several logical drives.
To make data consistency, perform the following procedure.
1
Start up GAM and sign on with Administrator privileges.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller View] from the [View] menu.
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
3
Double-click the icon of the logical drive for which Make Data Consistent is to
be performed from the [Controller View] window.
Detailed information about the logical drive appears in the [Logical Drive Information] window.
4
Click [Make Data Consistent] to start the Make Data Consistent.
When the Make Data Consistent is started, the [Make Data Consistent Status] window appears,
where the progress of the Make Data Consistent appears. When the progress bar reaches 100%
and the window closes, the check is completed.
239
Chapter 5 Array Configuration and Management [GAM]
5.10.2 Rebuild
To execute rebuild manually, perform the following procedure.
` Usually, rebuild is automatically executed after replacing the hard disk. For how to replace the hard
disk and how to perform rebuild, see "Chapter 6 Replacing Hard Disk" (Jpg.243).
1
Start up GAM and sign on with Administrator privileges.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller View] from the [View] menu.
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
3
Double-click the icon of a hard disk with "Failure" state (
) in the
[Controller View] window.
The detailed information about the hard disk appears in the [Disk Device Information] window.
4
Click [Rebuild].
The [Rebuild Status] window appears and rebuild starts.
When the rebuild is finished, the following window appears and the hard disk and the related
logical drives are restored to Online status.
5
240
Click [OK] to exit.
MegaRAID SAS User's Guide
5.10.3 Recalibration
Recalibration is a process to recalibrate the battery capacity.
To perform recalibration manually, use the following procedure:
` Perform recalibration when:
• You bought the array controller with a battery backup unit installed in.
• You bought a new battery backup unit and install it into the array controller.
• You changed a part of the controller with a battery.
Note, however, that recalibration may automatically start and operation from a management tool to
start recalibration may be cancelled. Then you do not need to recalibrate the unit anymore.
` Battery recalibration takes 12 hours with the server power on. If the server is turned on or off during a
battery recalibration, the battery recalibration restarts from the beginning.
` During recalibration, the logical drive in Write Back mode shifts automatically to Write Through mode
for safety. When the battery recalibration is completed, the write policy is automatically restored to
Write Back.
1
Start up GAM and sign on with Administrator privileges.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Intelligent BBU] from the [Administration] menu.
The following window appears.
3
Click [Recalibrate].
The battery recalibration starts.
4
Click [Cancel].
The window closes.
241
Chapter 5 Array Configuration and Management [GAM]
242
Chapter 6
Replacing Hard Disk
This chapter explains maintenance related
issues, such as hard disk replacement. Since the
procedure varies depending on the management
tools used, read the description concerning your
management tool.
6.1 How to Replace Hard Disk [ServerView RAID] . . . . . . . . . 244
6.2 How to Replace Hard Disk [GAM] . . . . . . . . . . . . . . . . . . 260
243
Chapter 6 Replacing Hard Disk
6.1 How to Replace Hard Disk
[ServerView RAID]
This section explains maintenance related issues, such as replacing hard disks using
ServerView RAID.
6.1.1 Checking Hard Disk to be Replaced [ServerView
RAID]
Check the target hard disk number before replacing it.
1
Start ServerView RAID Manager and log in.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
Check the hard disk icon in the tree view.
A failed hard disk is indicated with the
/
icon.
A hard disk that has been predicted to fail is indicated with the
icon.
The slot number can be confirmed at the following location on the hard disk icon.
Check here for the hard disk number. In this case, it is "2".
Check the number shown below to specify the location of the hard disk under SAS expander.
Check here for the hard disk enclosure number and slot
number. In this case, the enclosure is "1", and the slot is "3".
` If there are any hard disks being rebuilt (indicated with
), wait until the rebuild is finished. After the rebuild is complete, check the hard disk status again.
3
For the details, see to the [General] tab of the object window.
Detailed information about the selected hard disk appears.
If "S.M.A.R.T. errors" appears in the [Status] field, you will be informed of a failure prediction
sign (S.M.A.R.T.).
` The detailed information may not be displayable depending on the failure condition of the hard
disk.
244
MegaRAID SAS User's Guide
4
If there is a failed hard disk or a hard disk that is predicted to fail, replace it
using the following procedures.
When there is a failed hard disk
• When your server supports hot swap, replace the hard disk by referring to "6.1.2 Replacing
Failed Hard Disk [ServerView RAID] (With Hot Swap Support)" (Jpg.245).
• When your server does not support hot swap, replace the hard disk by referring to "6.1.3
Replacing Failed Hard Disk [ServerView RAID] (No Hot Swap Support)" (Jpg.247).
When there is a hard disk that is predicted to fail
See "6.1.4 Preventive Replacement of Hard Disk [ServerView RAID]" (Jpg.249) to replace the
hard disk with the failure prediction sign.
When a hard disk failed and another is predicted to fail
` First, replace the failed hard disk and perform rebuild. After that, confirm that the failure
indication of the replaced hard disk has disappeared, i.e. that the logical drive status is
"Operational", and then replace the hard disk that is predicted to fail, as a preventive measure.
If the hard disk that is predicted to fail is replaced before the failed hard disk, rebuild cannot be
performed and data will be lost.
` Failed hard disks can also be confirmed using WebBIOS. Start the WebBIOS and check the [Physical
Drives] view. For more details, see "2.2.1 Checking Hard Disk Status" (Jpg.51).
6.1.2 Replacing Failed Hard Disk [ServerView RAID] (With
Hot Swap Support)
When a hard disk fails, replace it with a new one as soon as possible. This section describes the
procedure to change hard disks when your server supports hot swap (changing disks with the server
running).
` For how to remove / install hard disks, and hot swap support, see "User's Guide" on PRIMERGY
Startup Disc supplied with the server.
` Replace the failed hard disk with a new one of the same model (with the same capacity and speed) as
a rule.
` Never remove any other hard disks than a failed one while the server is running.
1
Check the disk number of the failed hard disk and locate it.
The bay number is the number of the slot number plus one. Get the slot number with the step 1
and 2 of "6.1.1 Checking Hard Disk to be Replaced [ServerView RAID]" (Jpg.244).
Example: If the slot number is 2, the location of the disk is bay 3.
245
Chapter 6 Replacing Hard Disk
2
Check that the lit LED is corresponding to the failed hard disk unit bay on the
server.
For the bay locations and the LED location, see "User's Guide" on PRIMERGY Startup Disc
supplied with the server.
3
Pull out the failed hard disk about an inch (1 to 3 cm) to disconnect it from the
connector.
For how to remove hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
` Do not completely pull out the hard disk from the server here.
4
Wait at least one minute until the hard disk motor stops spinning.
5
Pull out the failed hard disk completely from the hard disk unit bay.
6
Install a new hard disk at the same location as the failed hard disk once was.
7
Check the following:
The confirmation procedure differs depending on whether a spare disk was set before the hard
disk failure.
If a spare disk was set:
Shortly after installing a new hard disk, it automatically becomes a spare disk, and the
corresponding hard disk failure LED turns off.
In the tree view of the ServerView RAID Manager, select the icon of the replaced hard disk to see
if "Global Hot Spare" appears in the [Status] field of the object window.
If no spare disk was set:
Shortly after installing a new hard disk, rebuild automatically starts for the new hard disk. When
the rebuild starts, the hard disk failure LED starts flashing and it goes off when the rebuild is
complete.
After the rebuild is complete, in the tree view of the ServerView RAID Manager, select the icon
of the replaced hard disk to see if "Operational" appears in the [Status] field of the object
window.
` When the following event is recorded in the OS event log, or in the Event Window of the ServerView RAID Manager, the rebuild is complete.
("X" indicates the number of the hard disk where the rebuild was performed.)
246
MegaRAID SAS User's Guide
• Source: ServerView RAID event, or ServerView RAID Manager event window
ID: 10267
Event: <Type and number of controller>: Rebuild complete on
Disk X
• Events via ServerView
Source
: Fujitsu ServerView Services
Type
: Information
Event ID
: 1
Description: <Type and number of controller>: Rebuild complete on Disk X
` For the approximate time to complete the rebuild, see "„ Estimated time for rebuild" (Jpg.31)
or "4.9.5 Checking Progress of Background Task" (Jpg.171).
` If the server restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next time.
6.1.3 Replacing Failed Hard Disk [ServerView RAID] (No
Hot Swap Support)
When a hard disk fails, replace it with a new one as soon as possible. This section describes the
procedure to change hard disks when your server does not support hot swap (changing disks with the
server runnning).
` For how to remove / install hard disks, and hot swap support, see "User's Guide" on PRIMERGY
Startup Disc supplied with the server.
` Replace the failed hard disk with a new one of the same model (with the same capacity and speed) as
a rule.
` Never remove any other hard disks than a failed one while the server is running.
1
Confirm the disk number of the failed hard disk and locate it.
The bay number is the number of the slot number plus one. Get the slot number with the step 1
and 2 of "6.1.1 Checking Hard Disk to be Replaced [ServerView RAID]" (Jpg.244).
Example: If the slot number is 2, the location of the disk is bay 3.
For the locations of the bays, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
2
Shutdown the server and disconnect the AC cable.
3
Disconnect all the cables that are connected to the failed hard disk, and
completely pull out the failed hard disk.
For how to remove hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
247
Chapter 6 Replacing Hard Disk
4
Install a new hard disk at the same location where the failed hard disk was
previously installed.
Connect all the cables that were connected to the failed one to the new one.
5
Turn the server on and start the OS.
6
Start ServerView RAID Manager to check the following:
The confirmation procedure differs depending on whether a spare disk was set before the hard
disk failure.
If a spare disk was set:
The replaced one automatically becomes a new spare disk.
After the rebuild is complete, in the tree view of the ServerView RAID Manager, select the icon
of the replaced hard disk to see if the [Status] is "Global Hot Spare".
The replacement procedure is complete here.
If no spare disk was set:
The new hard disk becomes the hard disk without an array configuration.
In the tree view of the ServerView RAID Manager, select the icon of the replaced hard disk to see
if the [Status] is "Available".
Proceed to the following steps.
7
Install the new hard disk into the array configuration.
1. Log in ServerView RAID Manager with an administrative privileges.
2. Check the logical drive status.
In the tree view of ServerView RAID Manager, select an logical drive icon in critical or
partially critical state (
). Check if its Status is "Degraded" or "Partially Degraded".
3. In the ServerView RAID Manager tree view, right-click the hard disk icon of the
newly installed (
) to select [Replace missing disk] from the displayed menu.
When the [Write access needed!] window appears, click yes to proceed.
4. Select an empty slot (
) and click [Replace].
The [Confirmation needed] window appears.
5. Click [Yes].
` The procedure above will result in the Status of the new hard disk in "Offline" (
hard disk failure only after this operation.
8
248
Rrebuild the new hard disk.
). It is not a
MegaRAID SAS User's Guide
1. In the SeverView RAID Manager tree view, right-click the icon of the new hard disk
(
), and select [Start rebuild] from the displayed menu.
The [Confirmation needed] window appears.
2. Click [Yes].
Rebuild starts.
After the rebuild, select the icon of the new hard disk in the SeverView RAID Manager tree
view to see if the Status is "Operational".
` When the following events are recorded in the OS event log, or in the Event Window of the
ServerView RAID Manager, the rebuild is complete. ("X" indicates the number of the hard disk
where the rebuild was performed.)
•Source: ServerView RAID events, or ServerView RAID Manager event window
ID: 10267
Event: <Type and number of controller>: Rebuild complete on
Disk X
•For events via ServerView
Source
: Fujitsu ServerView Services
Type
: Information
Event ID
: 1
Description: <Type and number of controller>: Rebuild complete on Disk X
` For the approximate time to complete rebuild, see "„ Estimated time for rebuild" (Jpg.31) or
"4.9.5 Checking Progress of Background Task" (Jpg.171).
` If the server restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next time.
6.1.4 Preventive Replacement of Hard Disk [ServerView
RAID]
When the hard disk failure prediction function (PFA/S.M.A.R.T.) reports a hard disk as "S.M.A.R.T.
errors", it means that the disk may fail in the near future. If the hard disk status becomes "S.M.A.R.T.
errors", replace that disk as a preventive measure.
The procedure for preventive replacement of a hard disk differs depending on the RAID level
(redundancy availability) on the logical drive whose hard disk is to be replaced, and ,with a RAID level
with redundancy, whether the hard disk supports hot swap.
• When the logical drive does not have redundancy (RAID 0):
J"„ Preventive replacement of hard disk with RAID 0 configuration" (pg.264)
• When the logical drive has redundancy (RAID 1, RAID 5, RAID 6, or RAID 10), and supports
hot swap:
J"„ Preventive replacement of hard disk with RAID 1, RAID 5, RAID 6, or RAID 10 configuration
(with hot swap support)" (pg.253)
249
Chapter 6 Replacing Hard Disk
• When the logical drive has redundancy (RAID 1, RAID 5, RAID 6, or RAID 10), but does not
support hot swap:
J"„ Preventive replacement of a hard disk with RAID 1, RAID 5, RAID 6, or RAID 10
configuration (without hot swap support)" (pg.256)
Follow the procedure in "„ Checking availability of redundancy" (Jpg.263) if you do not know
whether the logical drive has redundancy or not.
` For how to remove / install hard disks, and hot swap support, see "User's Guide" on PRIMERGY
Startup Disc supplied with the server.
` Replace the hard disk that is predicted to fail with a new one of the same model (with the same
capacity and speed) as a rule.
` We recommend that you back up the data before performing preventive replacement of a hard disk.
` If there is a failed hard disk, replace it first by referring to "6.1.2 Replacing Failed Hard Disk
[ServerView RAID] (With Hot Swap Support)" (Jpg.245) or "6.1.3 Replacing Failed Hard Disk
[ServerView RAID] (No Hot Swap Support)" (Jpg.247). If any hard disks are being rebuilt, wait until it
is complete.
„ Checking availability of redundancy
Following the procedure below if you do not know whether the logical drive has redundancy or not.
1
Start ServerView RAID Manager and log in it.
J"4.5 Starting and Exiting ServerView RAID Manager" (pg.125)
2
Check the number of the hard disk that is predicted to fail.
Adding one to the slot number identified in steps 1 to 2 in "6.1.1 Checking Hard Disk to be
Replaced [ServerView RAID]" (Jpg.244) is the bay number.
Example: If the slot number is 2, the location of the disk is bay 3.
3
In the tree view, select a logical drive (
), and click the [Layout] tab in the
object window.
A list of the hard disks that compose the selected logical drive appears.
4
250
Check whether the hard disk, which was predicted to have a failure in the step
2, is included in the hard disks that configure the logical drive.
MegaRAID SAS User's Guide
If there is a hard disk that is predicted to fail:
Click the [General] tab and check the RAID level.
Depending on the RAID level, replace the hard disk as a preventive measure.
If there is no hard disk that is predicted to fail:
Repeat the steps from 3 to check the other logical drives.
„ Preventive replacement of hard disk with RAID 0 configuration
If the hard disk to be replaced belongs to a RAID 0 logical drive, the disk array must be reconfigured and
the data must be restored from the backup.
Follow the procedure below to replace the hard disk as a preventive measure:
` Replace the hard disk that is predicted to fail with a new one of the same model (with the same
capacity and speed) as a rule.
1
Back up all the data on the hard disks connected to this array controller.
2
Using ServerView RAID Manager, check the disk number of the hard disk that
has a failure prediction sign (
) and locate that disk.
Adding one to the slot number identified in steps 1 to 2 in "6.1.1 Checking Hard Disk to be
Replaced [ServerView RAID]" (Jpg.244) is the bay number.
Example: If the slot number is 2, the location of the disk is bay 3.
` If there is a failed hard disk, replace it first by referring to "6.1.2 Replacing Failed Hard Disk
[ServerView RAID] (With Hot Swap Support)" (Jpg.245) or "6.1.3 Replacing Failed Hard Disk
[ServerView RAID] (No Hot Swap Support)" (Jpg.247). If any hard disks are being rebuilt, wait
until it is complete.
3
Restart the server.
4
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
251
Chapter 6 Replacing Hard Disk
5
Select [Configuration Wizard] from the main menu.
The [Configuration Wizard] window appears.
6
Select [Clear Configuration] and click [Next].
When the following warning message appears, click [Yes].
` By selecting [Clear Configuration], all the data stored on the hard disks connected to this array
controller is deleted.
7
Close WebBIOS and turn off the server.
J"2.1.2 Exiting WebBIOS" (pg.50)
8
Replace all the hard disks that are predicted to fail with new ones.
For how to replace hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
9
10
Turn on the server when the hard disk replacement is completed.
Create a disk array configuration using WebBIOS.
J"2.3.1 Creating Disk Array Configuration" (pg.63)
252
MegaRAID SAS User's Guide
11
Restore the backup data.
„ Preventive replacement of hard disk with RAID 1, RAID 5, RAID 6, or
RAID 10 configuration (with hot swap support)
If a hard disk is to be performed the preventive replacement configures RAID 1, RAID 5, RAID 6, or
RAID 10 logical drive, and the server supports hot swap, follow the procedure below as a preventive
measure.
` If the hard disk that is predicted to fail has RAID 0 array, do not perform this procedure for the
preventive replacement. See "„ Preventive replacement of hard disk with RAID 0 configuration"
(Jpg.264) for the replacement procedure.
` Replace the hard disk that is predicted to fail with a new one of the same model (with the same
capacity and speed).
` When two or more hard disks are predicted to fail, replace one at a time.
` Back up the data before the preventive replacement of a hard disk.
` Do not follow this procedure if your server does not support hot swap. Even with RAID 1 / RAID 5 /
RAID 6 / RAID 10, when your server does not support hot swap, see "„ Preventive replacement of a
hard disk with RAID 1, RAID 5, RAID 6, or RAID 10 configuration (without hot swap support)"
(Jpg.256).
1
Using ServerView RAID Manager, check the disk number of the hard disk that
has a failure prediction sign (
) and locate that disk.
Adding one to the slot number identified in steps 1 to 2 in "6.1.1 Checking Hard Disk to be
Replaced [ServerView RAID]" (Jpg.244) is the bay number.
Example: If the slot number is 2, the location of the disk is bay 3.
` If there is a failed hard disk, replace it first by referring to "6.1.2 Replacing Failed Hard Disk
[ServerView RAID] (With Hot Swap Support)" (Jpg.245) or "6.1.3 Replacing Failed Hard Disk
[ServerView RAID] (No Hot Swap Support)" (Jpg.247). If any hard disks are being rebuilt, wait
until it is complete.
2
Make sure that there are no media errors by performing Make Data Consistent.
J"4.8.7 Make Data Consistent" (pg.161)
253
Chapter 6 Replacing Hard Disk
3
In the tree view, select the hard disk (
) with a failure prediction sign.
Detailed information about the selected hard disk appears in the object window.
If "S.M.A.R.T. errors" appears in the [Status] field, you will be informed of a failure prediction
sign (S.M.A.R.T.).
4
In the tree view, select the target hard disk, right-click, and then click [Locate
device] from the displayed menu to check the location of the target hard disk on
the server.
The hard disk failure LED corresponding to the hard disk starts blinking.
For the location of the bays and of the hard disk failure LED, see "User's Guide" on PRIMERGY
Startup Disc supplied with the server.
` The hard disk confirmed here has received a failure prediction sign (the target hard disk for
preventive replacement).
Out a mark on this disk to identify it later.
5
After checking the location, in the tree view, select the target hard disk, rightclick, and then click [Stop location] from the displayed menu.
The failure LED turns off.
6
In the tree view, select the target hard disk, right-click, and then click [Make
Offline] from the displayed menu.
The following message appears.
Are you sure you want to set this physical disk to offline?
254
MegaRAID SAS User's Guide
7
Type "yes" and click [OK].
` If a hot spare disk has been set, rebuild is automatically started.
` The hard disk failure LED for the disk to be replaced is now lit.
If the hard disk failure LED is not lit, right-click the disk to be replaced, and then click [Locate
device] from the displayed menu again to check the location of the disk to be replaced. Should
you change a hard disk other than the one to be replaced to [Make Offline], continue to perform
the preventive replacement procedure for the hard disk as [Make Offline] and complete the
rebuild. After that, perform the preventive replacement procedure for the correct disk to be
replaced.
8
Check that the [Status] field for the target hard disk has changed to "Failed",
"Offline" or "Available" in the object window.
9
Pull out the hard disk identified in step 4 about an inch (1 to 3 cm) to disconnect
it from the connector.
For how to remove hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
` Make sure to remove a right hard disk. Removing a wrong hard disk may cause a loss of data.
` Do not pull out the hard disk completely from the server at this point.
10
Wait at least one minute until the hard disk motor has stopped spinning.
11
Pull out the hard disk that is predicted to fail completely from the hard disk unit
bay.
12
Install a new hard disk at the same location where the removed hard disk was
previously installed.
13
Check the following:
If a spare disk was set:
Shortly after installing a new hard disk, it automatically becomes a spare disk.
In the tree view of the ServerView RAID Manager, select the icon of the replaced hard disk to
check if "Global Hot Spare" appears in the [Status] field of the object window.
If no spare disk was set:
Shortly after installing a new hard disk, rebuild is automatically started for the newly installed
hard disk. When the rebuild is started, the hard disk's failure LED that was lit starts flashing, and
then turns off when the rebuild is completed.
After the rebuild is completed, in the tree view of the ServerView RAID Manager, select the icon
of the replaced hard disk to check if "Operational" appears in the [Status] field of the object
window.
255
Chapter 6 Replacing Hard Disk
` When the following event is recorded in the OS event log, or in the Event Window of the
ServerView RAID Manager, the rebuild is completed.
(“X” indicates the number of the hard disk where the rebuild was performed.)
•Source: ServerView RAID event, or ServerView RAID Manager event window
ID: 10267
Event: <Type and number of the controller>: Rebuild complete
on Disk X
•Event via ServerView
Source
: Fujitsu ServerView Services
Type
: Information
Event ID
: 1
Description: <Type and number of the controller>: Rebuild complete on Disk X
` If the server restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next time.
` For the approximate time to complete the rebuild, see "„ Estimated time for rebuild" (Jpg.31)
or "4.9.5 Checking Progress of Background Task" (Jpg.171).
` If you replace a hard disk while the Locate Device function is in progress, the disk may be displayed with the (
) icon after the replacement, indicating that the Locate Device function is
in progress. If this happens, right-click on the hard disk and select [Stop location] from the displayed menu.
„ Preventive replacement of a hard disk with RAID 1, RAID 5, RAID 6,
or RAID 10 configuration (without hot swap support)
If a hard disk is to be performed the preventive replacement configures RAID 1, RAID 5, RAID 6, or
RAID 10 logical drive, and the server does not support hot swap, follow the procedure below as a
preventive measure.
` If the hard disk that is predicted to fail has RAID 0 array, do not perform this procedure for the
preventive replacement. See "„ Preventive replacement of hard disk with RAID 0 configuration"
(Jpg.264) for the replacement procedure.
` Replace the hard disk that is predicted to fail with a new one of the same model (with the same
capacity and speed).
` When two or more hard disks are predicted to fail, replace one at a time.
` Back up the data before the preventive replacement of a hard disk.
1
Using ServerView RAID Manager, check the disk number of the hard disk that
has a failure prediction sign (
) and locate it.
The slot number identified in steps 1 to 2 in "6.1.1 Checking Hard Disk to be Replaced
[ServerView RAID]" (Jpg.244) plus one is the bay number.
Example: If the slot number is 2, the location of the disk is bay 3.
For specifying a bay location, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
256
MegaRAID SAS User's Guide
` If there is a failed hard disk, replace it first by referring to "6.1.2 Replacing Failed Hard Disk
[ServerView RAID] (With Hot Swap Support)" (Jpg.245) or "6.1.3 Replacing Failed Hard Disk
[ServerView RAID] (No Hot Swap Support)" (Jpg.247). If any hard disks are being rebuilt, wait
until it is complete.
2
Make sure that there are no errors on the media with Make Data Consistent.
J"4.8.7 Make Data Consistent" (pg.161)
3
In the tree view, right-click the hard disk icon (
sign to select [Make Offline].
) with a failure prediction
The [Confirmation needed] window appears.
Type [Yes], and click [OK].
` Rebuild automatically starts if hot spare is set.
4
In the object window, check if the Status of the hard disk to be replaced is
"Failed", "Offline", or "Available".
5
Shutdown the server and disconnect the AC cable.
6
Disconnect all the cables that are connected to the failed hard disk, and
completely pull out the failed hard disk.
For how to remove hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
7
Install a new hard disk at the same location where the failed hard disk was
previously installed.
Connect all the cables that were connected to the failed one to the new one.
8
Turn the server on and start the OS.
9
Start ServerView RAID Manager to check the following:
The confirmation procedure differs depending on whether a spare disk was set before the hard
disk failure.
If a spare disk was set:
The replaced one automatically becomes a new spare disk.
After the rebuild is complete, in the tree view of the ServerView RAID Manager, select the icon
of the replaced hard disk to see if the [Status] is "Global Hot Spare".
The replacement procedure is complete here.
If no spare disk was set:
The new hard disk becomes the hard disk without an array configuration.
In the tree view of the ServerView RAID Manager, select the icon of the replaced hard disk to see
if the [Status] is "Available".
Proceed to the following steps.
257
Chapter 6 Replacing Hard Disk
10
Install the new hard disk into the array configuration.
1. Log in ServerView RAID Manager with administrative privileges.
2. Check the logical drive status.
In the tree view of ServerView RAID Manager, select an logical drive icon in critical or
partially critical (
). Check if its Status is "Degraded" or "Partially Degraded".
3. In the ServerView RAID Manager tree view, right-click the hard disk icon of the
newly mounted (
) to select [Replace missing disk] from the displayed menu.
When the [Write access needed!] window appears, click[Yes] to proceed.
4. Select an empty slot (
) and click [Replace].
The [Confirmation needed] window appears.
5. Click [Yes].
` The procedure above will result in the Status of the new hard disk in "Offline" (
). It is not a
hard disk failure only after this operation.
11
Rrebuild the new hard disk.
1. In the SeverView RAID Manager tree view, right-click the icon of the new hard disk
(
), and select [Start rebuild] from the displayd menu.
The [Confirmation needed] window appears.
2. Click [Yes].
Rebuild starts.
After the rebuild, select the icon of the new hard disk in the SeverView RAID Manager tree
view to see if the Status is "Operational".
258
MegaRAID SAS User's Guide
` When the following events are recorded in the OS event log, or in the Event Window of the
ServerView RAID Manager, the rebuild is complete. ("X" indicates the number of the hard disk
where the rebuild was performed.)
•Source: ServerView RAID event, or ServerView RAID Manager event window
ID: 10267
Event: <Type and number of controller>: Rebuild complete on
Disk X
•Events via ServerView
Source
: Fujitsu ServerView Services
Type
: Information
Event ID
: 1
Description: <Type and number of controller>: Rebuild complete on Disk X
` For the approximate time to complete the rebuild, see "„ Estimated time for rebuild" (Jpg.31)
or "4.9.5 Checking Progress of Background Task" (Jpg.171).
` If the server restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next time.
259
Chapter 6 Replacing Hard Disk
6.2 How to Replace Hard Disk [GAM]
This section explains maintenance related issues in GAM such as hard disk
replacement.
6.2.1 Checking Hard Disk to Replace [GAM]
Check the slot number of the target hard disk before replacing it.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller View] from the [View] menu.
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
3
Check the displayed icon for the hard disk.
A failed hard disk is indicated with the
icon.
A hard disk that has been predicted to fail is indicated with the
icon.
The slot number can be confirmed at the following location on the hard disk icon.
Slot ID
In this case, the Slot ID is "4".
` If there are any hard disks being rebuilt (indicated with
), wait until the rebuild is
finished. After the rebuild has finished, check the hard disk status again.
4
Double-click the hard disk icon to confirm detailed information.
Detailed information about the selected hard disk appears.
If the [PFA Count] in the [Device Errors] field appears as "Found", a failure prediction sign
(S.M.A.R.T.) has been detected.
` The detailed information may not be displayed depending on the failure condition of the hard
disk.
260
MegaRAID SAS User's Guide
5
If there is a failed hard disk or a hard disk that is predicted to fail, replace it by
following procedure below.
If there is a failed hard disk
See "6.2.2 Replacing Failed Hard Disk [GAM]" (Jpg.261) to replace the hard disk.
If there is a hard disk that is predicted to fail
See "6.2.3 Preventive Replacement of hard disk [GAM]" (Jpg.263) to replace the hard disk with
the failure prediction sign.
When a hard disk failed and another is predicted to fail
` First, replace the failed hard disk and perform rebuild. After that, confirm that the failure
indication of the replaced hard disk has disappeared, i.e. that the logical drive status is online,
and then replace the hard disk that is predicted to fail, as a preventive measure.
If the hard disk that is predicted to fail is replaced before the failed hard disk, rebuild cannot be
performed and data will be lost.
` Failed hard disks can also be confirmed using WebBIOS. Start the WebBIOS and check the [Physical
Drives] view. For more details, see "2.2.1 Checking Hard Disk Status" (Jpg.51).
6.2.2 Replacing Failed Hard Disk [GAM]
If a hard disk fails, it must be replaced with a new one as soon as possible.
` For how to remove and install hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied
with the server.
` Replace the failed hard disk with a new one of the same model (with the same capacity and speed) as
a rule.
` When connecting a hard disk that has previously been used in a disk array configuration on a general
host adapter, perform a low level format of the hard disk on the host adapter in advance.
` Never remove any hard disks while the server is turned on, except to replace a failed disk.
1
Confirm the slot number of the failed hard disk and locate the disk.
Adding one to the slot number identified in steps 1 to 3 in "6.2.1 Checking Hard Disk to Replace
[GAM]" (Jpg.260) is the bay number.
Example: If the slot number is 4, the location of the disk is bay 5.
2
Check that the hard disk failure LED is lit for the bay corresponding to the failed
hard disk on the server.
For the location of the bays and of the hard disk failure LED, see "User's Guide" on PRIMERGY
Startup Disc supplied with the server.
261
Chapter 6 Replacing Hard Disk
3
Pull out the failed hard disk about an inch (1 to 3 cm) to disconnect it from the
connector.
For how to remove hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
` Do not pull out the hard disk completely from the server at this point.
4
Wait at least one minute until the hard disk motor has stopped spinning.
5
Pull out the failed hard disk completely from the hard disk unit bay.
6
Install a new hard disk at the same location where the failed hard disk was
previously installed.
7
Check the following:
The confirmation procedure differs depending on whether a spare disk was set before the hard
disk failure.
If a spare disk was set:
Shortly after installing a new hard disk, it automatically becomes a spare disk, and the
corresponding hard disk failure LED goes off.
Make sure that the status of the replaced hard disk has changed to "Hot Spare" in the [Disk
Device Information] window (Jpg.231) of GAM.
If no spare disk was set:
Shortly after installing a new hard disk, rebuild is automatically started for the newly installed
hard disk. When the rebuild is started, the hard disk's failure LED that was lit starts flashing, and
then goes off when the rebuild is complete.
When the rebuild is finished, make sure that the status of the replaced hard disk has changed to
"On Line" in the [Disk Device Information] window (Jpg.231) of GAM.
` When the following event is recorded in the OS event log, or in the Log Information Viewer of
the GAM Client, the rebuild is complete.
([ctl] indicates the controller number and [chn] indicates the slot number of the hard disk.)
•For Log Information Viewer
I-7
ctl:x chn:y tgt:z
Rebuild is over.
•For OS Event Log
Source
:Fujitsu ServerView Services
Type
: Information
Event ID
: 1
Description: [ctl:x chn:y tgt:x] Rebuild is over.
To confirm the completion of rebuild in GAM Client, do not close GAM Client until the rebuild is
complete.
` For the approximate time to complete the rebuild, see "„ Estimated time for rebuild" (Jpg.31)
or "„ Calculating approximate time needed for a background task" (Jpg.238).
` If the server restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next time.
262
MegaRAID SAS User's Guide
6.2.3 Preventive Replacement of hard disk [GAM]
When the hard disk failure prediction function (PFA/S.M.A.R.T.) reports a hard disk as "Critical", it
means that the disk may fail in the near future. If the hard disk status becomes "Critical", replace that
disk as a preventive measure.
` For how to remove and install hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied
with the server.
` Replace the hard disk that is predicted to fail with a new one of the same model (with the same
capacity and speed) as a rule.
` We recommend that you back up the data before performing preventive replacement of a hard disk.
` If there is a failed hard disk at this point, replace that disk first by referring to "6.2.2 Replacing Failed
Hard Disk [GAM]" (Jpg.261). If any hard disks are being rebuilt, wait until the rebuild process is
finished.
„ Checking availability of redundancy
The procedure for preventive replacement of a hard disk is different depending on the RAID level
(availability of redundancy) on the logical drive that the target hard disk is installed in.
• When the logical drive does not have redundancy (RAID 0):
J"„ Preventive replacement of hard disk with RAID 0 configuration" (pg.264)
• When the logical drive has redundancy (RAID 1, RAID 5, or RAID 10):
J"„ Preventive replacement of hard disk with RAID 1, RAID 5, or RAID 10 configuration"
(pg.266)
Following the procedure below if you do not know whether the logical drive has redundancy or not.
1
Start up GAM and sign on.
J"5.5 Starting and Exiting GAM" (pg.196)
2
Select [Controller View] from the [View] menu.
J"5.6.4 Starting Controller View and the Window Layout" (pg.204)
263
Chapter 6 Replacing Hard Disk
3
Right-click to select the logical drive icon displayed in the [Logical Drives] field
in the [Controller View] window of GAM.
Check the [Physical Devices] field. The icons for the hard disks configuring the selected logical
drive appear in white.
RAID level of
the logical drive
Right-click
the logical drive
Hard disk drives
composing the logical drive
` Right-clicking the logical drive icon again reverts the display to its original status.
4
Check all the hard disks included in the disk array configuration for each logical
drive.
5
Check which logical drive uses the failure-predicted hard disk (
6
Check the RAID level for the logical drive.
).
„ Preventive replacement of hard disk with RAID 0 configuration
If the hard disk to be replaced belongs to a RAID 0 logical drive, the disk array must be reconfigured and
the data must be restored from the backup.
Follow the procedure below to replace the hard disk as a preventive measure:
` Replace the hard disk that is predicted to fail with a new one of the same model (with the same
capacity and speed) as a rule.
1
264
Back up all the data on the hard disks connected to the array controller.
MegaRAID SAS User's Guide
2
By using GAM, check the slot number of the hard disk with a failure prediction
sign (
) to locate the drive.
Adding one to the slot number identified in steps 1 to 3 in "6.2.1 Checking Hard Disk to Replace
[GAM]" (Jpg.260) is the bay number.
Example: If the slot number is 4, the location of the disk is bay 5.
` If there is a failed hard disk at this point, replace that disk first by referring to "6.2.2 Replacing
Failed Hard Disk [GAM]" (Jpg.261). If any hard disks are being rebuilt, wait until the rebuild
process is finished.
3
Restart the server.
4
Start up WebBIOS.
J"2.1.1 Starting Up WebBIOS" (pg.46)
5
Select [Configuration Wizard] from the main menu.
The [Configuration Wizard] window appears.
6
Select [Clear Configuration] and click [Next].
When the following warning message appears, click [Yes].
265
Chapter 6 Replacing Hard Disk
` By performing [Clear Configuration], all the data stored on the hard disks connected to this
array controller is deleted.
7
Close WebBIOS and turn off the server.
J"2.1.2 Exiting WebBIOS" (pg.50)
8
Replace all the hard disks that are predicted to fail with new ones.
For how to replace hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
9
10
Turn on the server when the hard disk replacement is complete.
Create a disk array configuration using WebBIOS.
J"2.3.1 Creating Disk Array Configuration" (pg.63)
11
Restore the backup data.
„ Preventive replacement of hard disk with RAID 1, RAID 5, or RAID 10
configuration
If the target hard disk for the preventive replacement is configuring a RAID 1, RAID 5, or RAID 10
logical drive, follow the procedure below for the preventive replacement.
` If the hard disk that is predicted to fail configure a RAID 0 array, do not perform this procedure as the
preventive replacement. See "„ Preventive replacement of hard disk with RAID 0 configuration"
(Jpg.264) for the replacement procedure.
` Replace the hard disk that is predicted to fail with a new one of the same model (with the same
capacity and speed) as a rule.
` When two or more hard disks are predicted to fail, replace one disk at a time.
` Back up the data before a preventive replacement of a hard disk.
1
By using GAM, check the slot number of the hard disk with a failure prediction
sign (
) to locate the disk.
Adding one to the slot number identified in steps 1 to 3 in "6.2.1 Checking Hard Disk to Replace
[GAM]" (Jpg.260) is the bay number.
Example: If the slot number is 4, the location of the disk is bay 5.
` If there is a failed hard disk at this point, replace that disk first, referring to "6.2.2 Replacing
Failed Hard Disk [GAM]" (Jpg.261). If any hard disks are being rebuilt, wait until the rebuild
process is finished.
2
Make sure that there are no media errors by performing Make Data Consistent.
J"5.10.1 Make Data Consistent" (pg.239)
266
MegaRAID SAS User's Guide
3
Double-click the icon of the hard disk with the failure prediction sign.
Detailed information about the selected hard disk appears.
Make sure that its "Status" is indicated as "Critical".
4
Click [Locate] to check the location of the target hard disk on the server.
The hard disk failure LED corresponding to the hard disk starts blinking.
For the location of the bays and of the hard disk failure LED, see "User's Guide" on PRIMERGY
Startup Disc supplied with the server.
` The hard disk confirmed here has received a failure prediction sign (the target hard disk for
preventive replacement).
Put a mark on this disk to identify it later.
5
Click [OK] when the location is confirmed.
The failure LED goes off.
6
Click the [Make Offline] button. When the [WARNING] window appears, enter
[YES] and click [OK].
` If a hot spare is set, rebuild is automatically started.
` The hard disk failure LED for the disk to be replaced is now lit.
If the hard disk failure LED is not lit, click [Locate] again to check the location of the disk for the
preventive replacement.
` If you choose a wrong hard disk for [Make Offline], continue the preventive replacement procedure with that hard disk with [Make Offline] and complete the rebuild. After that, perform the
preventive replacement procedure for the proper disk.
267
Chapter 6 Replacing Hard Disk
7
Check that the following log entry appears in the GAM Log Information Viewer.
Event ID
: E-50
Description: Physical disk status changed to offline
8
Pull out the hard disk identified in the step 4 about an inch (1 to 3 cm) to
disconnect it from the connector.
For how to remove hard disks, see "User's Guide" on PRIMERGY Startup Disc supplied with the
server.
` Make sure to remove a right hard disk. Removing a wrong hard disk may cause a loss of data.
` Do not pull out the hard disk completely from the server at this point.
9
Wait at least one minute until the hard disk motor has stopped spinning.
10
Pull out the hard disk that is predicted to fail completely from the hard disk bay.
11
Install a new hard disk at the same location where the removed hard disk was
previously installed.
12
Check the following:
If a spare disk was set:
Shortly after installing a new hard disk, it automatically becomes a spare disk.
Make sure that the status of the replaced hard disk has changed to "Hot Spare" in the [Disk
Device Information] window (Jpg.231) of GAM.
If no spare disk was set:
Shortly after installing a new hard disk, rebuild is automatically started for the newly installed
hard disk. When the rebuild is started, the hard disk's failure LED that was lit starts blinking, and
then goes off when the rebuild is complete.
When the rebuild is finished, make sure that the status of the replaced hard disk has changed to
"On Line" in the [Disk Device Information] window (Jpg.231) of GAM.
` If the server restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next time.
` If the [Controller View] display is not updated, execute [Scan Devices] from the [Administration]
menu.
268
Appendix
This section explains the event codes for
ServerView RAID and GAM, and how to replace
batteries.
A List of ServerView RAID Event Log . . . . . . . . . . . . . . . . . 270
B List of GAM Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
C Replacing Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
269
Appendix
A
List of ServerView RAID Event
Log
With ServerView, SNMP traps issued by ServerView RAID can be saved in the OS
logs. ServerVew RAID also has an own function to save logs.
• For Windows
Events coming through ServerView are recorded as the source "Fujitsu ServerView Services" in the
Event Viewer application log.
Events from ServerView RAID are recorded as the source "ServerView RAID" in the Event Viewer
application log.
• For Linux
Events coming through ServerView are recorded as the source "Fujitsu ServerView Services" in the
system log .
Events from ServerView RAID are recorded as the source "ServerView RAID" in the system log.
` Refer to the events by ServerView instead of ServerView RAID when events are notified from both.
The log also records the location of the device. Types of locations are as follows.
table: Meaning of event log strings
Character String
Meaning
[Note 1]
Server %s
Name of the server. Events coming through ServerVeiw only save them.
Adapter %s
Displays names and numbers of the controller.
As for this array controller, the name is "LSI MegaRAID SAS ..." or "RAID 5/6 SAS based
on LSI MegaRAID".
Disk %s
The number of hard disks.
"x" or "y:x" appears in %s representing the hard disk numbers.
Logical Drive %s
The number of the logical drive.
[Note 1]: %s is replaced with a number or a character string.
` Unless ServerView is installed, logging into the OS event logs from the source "Fujitsu ServerView
Services" will not be possible. See "User’s Guide" located on "PRIMERGY Startup Disc" supplied with
the server to install and configure ServerView.
270
MegaRAID SAS User's Guide
The relationship between event types and each event log function is as follows:
table: Event log types and descriptions
Severity
Description
Severity with the
ServerView RAID Manager
OS Event Log Type
CRITICAL
Severe error
Error
Error
MAJOR
Error
Error
Error
MINOR
Warning
Warning
Warning
INFORMATIONAL
Information (No
action required)
Informational
Information
„ List of ServerView RAID Event Log
` The ID numbers described below shows event IDs for the source "ServerView RAID", and Specific
Numbers for SNMP traps.
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
1
INFORMA
TIONAL
Undefined Event
(Server %s)
An unknown event has
occurred.
If there is an error before or after
an event, perform the proper
recovery action for that error.
2
INFORMA
TIONAL
Connection to
ServerView RAID
established
(Server%s)
Connection to ServerView
RAID has been confirmed.
None.
3
INFORMA
TIONAL
Disconnected from
ServerView RAID
(Server%s)
Connection to ServerView
RAID has been cut.
None.
4
CRITICAL
Unexpected
disconnect from
ServerView RAID
(Server%s)
Connection to ServerView
RAID has been
unexpectedly cut.
Check if you can log in
ServerView RAID Manager. If you
can not, restart the ServerView
RAID services.
10000
INFORMA
TIONAL
Unknown event
(Server %s)
An unknown event has
occurred.
If there is an error before or after
an event, perform the proper
recovery action for that error.
10002
MINOR
Write access to
ServerView RAID
revoked by user %s
(%s) (Server %s)
Write Access mode has
been canceled.
Another client has obtained
Write Access mode.
None.
10003
MAJOR
Adapter %s: BBU
temperature out of
range (Server %s)
Abnormal battery
temperature is detected.
Check the fan status in
ServerView. If the fan has a
failure, follow the corrective
procedure of the server. If the fan
has no failure, check the
surrounding temperature. If the
problem recurs after checking the
surrounding temperature, replace
the battery backup unit.
271
Appendix
table: List of ServerView RAID event logs
ID
272
Severity
Log Entry
Description
Recovery Action
10004
MAJOR
Adapter %s: BBU
temperature unstable
(Server %s)
Abnormal battery
temperature is detected.
Check the fan status in
ServerView. If the fan has a
failure, follow the corrective
procedure of the server. If the fan
has no failure, check the
surrounding temperature. If the
problem recurs after checking the
surrounding temperature, replace
the battery backup unit.
10005
MAJOR
Adapter %s: BBU
temperature above
threshold (Server
%s)
Abnormal battery
temperature is detected.
Check the fan status in
ServerView. If the fan has a
failure, follow the corrective
procedure of the server. If the fan
has no failure, check the
surrounding temperature. If the
problem recurs after checking the
surrounding temperature, replace
the battery backup unit.
10006
MAJOR
Adapter %s: BBU
voltage out of range
(Server %s)
Abnormal battery voltage is
detected.
Replace the battery backup unit.
10007
MAJOR
Adapter %s: BBU
voltage unstable
(Server %s)
Battery voltage is unstable.
Replace the battery backup unit.
10008
MAJOR
Adapter %s: BBU
voltage below
threshold (Server
%s)
Battery voltage is below the
threshold.
Wait until the battery charging is
completed.
10009
MAJOR
Adapter %s: BBU
communication error
(Server %s)
An error occurred during
the communication with the
battery backup unit.
Replace the battery backup unit.
10010
INFORMA
TIONAL
Adapter %s: BBU
reconditioning
started (Server %s)
Battery recalibration has
started.
None.
10011
INFORMA
TIONAL
Adapter %s: BBU
status becomes
normal (Server %s)
The battery is now in
normal state.
None.
10012
INFORMA
TIONAL
Adapter %s: BBU
good (Server %s)
The battery is normal.
None.
10013
CRITICAL
Adapter %s: BBU
failed (Server %s)
The battery backup unit has
failed.
Replace the battery backup unit.
10014
MAJOR
Adapter %s: BBU
fast charging failed
(Server %s)
Rapid battery charging has
failed.
Replace the battery backup unit.
10015
MINOR
Adapter %s: BBU
charge count
exceeded (Server
%s)
The number of battery
recharging times has
reached the maximum
limit.
Replace the battery backup unit.
10016
MINOR
Adapter %s: BBU
needs reconditioning
(Server %s)
Battery recalibration is
necessary.
Perform recalibration.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10023
MAJOR
Adapter %s: Disk
(%s) timed out
(Server %s)
The hard disk has been
timed out.
Check that the hard disk is
connected properly.
If the hard disk has failed, replace
and rebuild it.
10024
INFORMA
TIONAL
Adapter %s: Global
hot spare created on
disk (%s) (Server
%s)
A spare disk has been
created.
None.
10025
MINOR
Adapter %s: Global
hot spare deleted on
disk (%s) (Server
%s)
A spare disk has been
disabled.
None.
10026
INFORMA
TIONAL
Adapter %s:
Dedicated hot spare
created on disk (%s)
(Server %s)
A dedicated spare disk has
been created.
A dedicated spare disk is not
supported. Reconfigure the spare
disk.
10027
MINOR
Adapter %s:
Dedicated hot spare
deleted on disk (%s)
(Server %s)
A dedicated spare disk has
been deleted.
None.
10028
INFORMA
TIONAL
Adapter %s: Disk
(%s) marked
available (Server
%s)
The hard disk is now
unused.
None.
10029
INFORMA
TIONAL
Adapter %s: Rebuild
on disk (%s) started
(Server %s)
Rebuilding the hard disk
has started.
None.
10030
MAJOR
Adapter %s: Rebuild
on disk (%s) failed
(Server %s)
Rebuilding the hard disk
has failed.
Check the current logical drive
status.
• For the critical state:
Replace the failed hard disk and
perform rebuild again.
• For the offline state:
Contact an office listed in the
"Contact Information" of "Start
Guide".
10032
INFORMA
TIONAL
Adapter %s: New
disk (%s) detected
(Server %s)
A new hard disk has been
detected.
None.
10033
MINOR
Adapter %s: Disk
(%s) removed
(Server %s)
A hard disk was removed.
None.
10038
MAJOR
Adapter %s: Error
on disk (%s)
detected (Server %s)
An error has been detected
on a hard disk.
Replace the failed hard disk and
perform rebuild.
10039
INFORMA
TIONAL
Adapter %s:
Channel %s was
reset (Server %s)
A channel has been reset.
None.
10040
MAJOR
Adapter %s: Retry I/
O on disk (%s)
(Server %s)
I/O retry for the hard disk
has been performed.
There is no problem as long as
there is no hard disk failure,
because the firmware has
performed a recovery.
273
Appendix
table: List of ServerView RAID event logs
ID
274
Severity
Log Entry
Description
Recovery Action
10050
MAJOR
Adapter %s:
Temperature sensor
%s in enclosure %s
above threshold
(Server %s)
Temperature sensor in
enclosure is above the
threshold.
Check the fan status in
ServerView. If the fan has a
failure, follow the corrective
procedure of the server. If the fan
has no failure, check the
surrounding temperature.
10055
INFORMA
TIONAL
Adapter %s: Rebuild
started on logical
drive %s (Server %s)
Rebuilding the logical drive
has started.
None.
10056
INFORMA
TIONAL
Adapter %s: Rebuild
finished on logical
drive %s (Server %s)
Rebuilding the logical drive
has been completed.
None.
10057
MAJOR
Adapter %s: Rebuild
failed on logical
drive %s (Server %s)
Rebuilding the logical drive
has failed.
Check the current logical drive
status.
• For the critical state:
Replace the failed hard disk and
perform rebuild again.
• For the offline state:
Contact an office listed in the
"Contact Information" of "Start
Guide".
10058
MINOR
Adapter %s: Rebuild
aborted on logical
drive %s (Server %s)
Rebuilding the logical drive
has been aborted.
Perform rebuild again.
10068
INFORMA
TIONAL
Adapter %s:
Migration started on
logical drive %s
(Server %s)
The capacity expansion
process of the logical drive
has started.
None.
10069
INFORMA
TIONAL
Adapter %s:
Migration finished
on logical drive %s
(Server %s)
The capacity expansion
process of the logical drive
has been completed.
None.
10070
MAJOR
Adapter %s:
Migration failed on
logical drive %s
(Server %s)
The capacity expansion
process of the logical drive
has failed.
Recreate the array configuration
and restore the data from the
backup.
10071
MINOR
Adapter %s:
Migration aborted on
logical drive %s
(Server %s)
The capacity expansion
process of the logical drive
has been aborted.
Recreate the array configuration
and restore the data from the
backup.
10072
INFORMA
TIONAL
Adapter %s: Patrol
Read started (Server
%s)
Patrol Read has started.
None. Patrol Read is not
supported. Check the array
controller configuration.
10073
INFORMA
TIONAL
Adapter %s: Patrol
Read finished
(Server %s)
Patrol Read has been
completed.
None. Patrol Read is not
supported. Check the array
controller configuration.
10074
MINOR
Adapter %s: Patrol
Read aborted (Server
%s)
Patrol Read has been
aborted.
None.
10075
INFORMA
TIONAL
Adapter %s: Patrol
Read stopped
(Server %s)
Patrol Read has stopped.
None.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10076
INFORMA
TIONAL
Adapter %s: Patrol
Read paused (Server
%s)
Patrol Read has paused.
None.
10077
INFORMA
TIONAL
Adapter %s: Patrol
Read continued
(Server %s)
Patrol Read has resumed.
None.
10078
MAJOR
Adapter %s: Logical
drive %s degraded
(Server %s)
The logical drive is now
critical.
Replace the failed hard disk and
perform rebuild.
10079
CRITICAL
Adapter %s: Logical
drive %s failed
(Server %s)
The logical drive is now
offline.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10080
INFORMA
TIONAL
Adapter %s: Logical
drive %s created
(Server %s)
The logical drive has been
created.
None.
10081
MINOR
Adapter %s: Logical
drive %s deleted
(Server %s)
The logical drive has been
deleted.
None.
10082
INFORMA
TIONAL
Adapter %s: Logical
drive %s operational
(Server %s)
The logical drive is now
online.
None.
10085
INFORMA
TIONAL
Adapter %s:
Initialization started
on logical drive %s
(Server %s)
Foreground initialization of
the logical drive has started.
None.
10086
INFORMA
TIONAL
Adapter %s:
Initialization
finished on logical
drive %s (Server %s)
Foreground initialization of
the logical drive has been
completed.
None.
10087
INFORMA
TIONAL
Adapter %s: BGI
started on logical
drive %s (Server %s)
Background initialization
of the logical drive has
started.
None.
10088
INFORMA
TIONAL
Adapter %s: BGI
finished on logical
drive %s (Server %s)
Background initialization
of the logical drive has
been completed.
None.
10089
MINOR
Adapter %s: BGI
canceled on logical
drive %s (Server %s)
Background initialization
of the logical drive has
been canceled.
None. Background initialization
resumes automatically after a
certain period of time.
10090
MINOR
Adapter %s:
Initialization
canceled on logical
drive %s (Server %s)
Foreground initialization of
the logical drive has been
canceled.
None.
10095
INFORMA
TIONAL
Adapter %s: Alarm
enabled (Server %s)
An alarm has been enabled.
None.
10096
MINOR
Adapter %s: Alarm
disabled (Server %s)
An alarm has been
disabled.
None.
10101
INFORMA
TIONAL
Adapter %s: Patrol
Read disabled
(Server %s)
Patrol Read has been
disabled.
None.
275
Appendix
table: List of ServerView RAID event logs
276
ID
Severity
Log Entry
Description
Recovery Action
10102
INFORMA
TIONAL
Adapter %s: Patrol
Read set to
automatic (Server
%s)
Patrol Read has been set to
Automatic mode.
None. Patrol Read is not
supported. Check the array
controller configuration.
10103
INFORMA
TIONAL
Adapter %s: Patrol
Read set to manual
(Server %s)
Patrol Read has been set to
Manual mode.
None. Patrol Read is not
supported. Check the array
controller configuration.
10104
INFORMA
TIONAL
Adapter %s: Patrol
Read delay changed
(Server %s)
Patrol Read Delay has been
changed.
None. Patrol Read is not
supported. Check the array
controller configuration.
10105
INFORMA
TIONAL
Adapter %s:
Initialization set to
normal (Server %s)
Initialization mode has
been set to Normal.
None.
10106
INFORMA
TIONAL
Adapter %s:
Initialization set to
fast (Server %s)
Initialization mode has
been set to Fast.
None.
10107
INFORMA
TIONAL
Adapter %s: Initiator
ID changed (Server
%s)
The Initiator ID has been
changed.
Do not change the Initiator ID.
Check the configuration of the
array controller and set the correct
value.
10108
INFORMA
TIONAL
Adapter %s:
Automatic rebuild
enabled (Server %s)
Auto Rebuild has been
enabled.
None.
10109
INFORMA
TIONAL
Adapter %s:
Automatic rebuild
disabled (Server %s)
Auto Rebuild has been
disabled.
None.
10113
INFORMA
TIONAL
Adapter %s: MDC
rate changed to
%s%% (Server %s)
MDC Rate has been
changed.
None.
10114
INFORMA
TIONAL
Adapter %s: BIOS
enabled (Server %s)
BIOS has been enabled.
None.
10115
INFORMA
TIONAL
Adapter %s: BIOS
disabled (Server %s)
BIOS has been disabled.
None.
10116
INFORMA
TIONAL
Adapter %s: BIOS
stop on error enabled
(Server %s)
BIOS Stop on Error has
been enabled.
None.
10117
INFORMA
TIONAL
Adapter %s: BIOS
stop on error
disabled (Server %s)
BIOS Stop on Error has
been disabled.
None.
10118
INFORMA
TIONAL
Adapter %s: Write
cache on all disks
enabled (Server %s)
Write cache has been
enabled on all hard disks.
Enabling write cache is not
supported. Check the logical drive
settings.
10119
INFORMA
TIONAL
Adapter %s: Write
cache on all disks
disabled (Server %s)
Write cache has been
disabled on all hard disks.
None.
10120
INFORMA
TIONAL
Adapter %s: Readahead on all disks
enabled (Server %s)
Read Ahead has been
enabled on all hard disks.
Enabling Read Ahead is not
supported. Check the logical drive
settings.
10121
INFORMA
TIONAL
Adapter %s: Readahead on all disks
disabled (Server %s)
Read Ahead has been
disabled on all hard disks.
None.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10124
INFORMA
TIONAL
Adapter %s: Spinup
drive count changed
(after next reboot)
(Server %s)
Spinup Drive Count has
been changed.
None.
10125
INFORMA
TIONAL
Adapter %s: Spinup
delay changed (after
next reboot) (Server
%s)
Spinup Delay has been
changed.
None.
10131
INFORMA
TIONAL
Adapter %s:
S.M.A.R.T. poll
interval changed
(Server %s)
S.M.A.R.T. poll interval
has been changed.
None.
10132
INFORMA
TIONAL
Adapter %s:
Configuration
rescanned (Server
%s)
The array configuration has
been rescanned.
None.
10133
INFORMA
TIONAL
Adapter %s:
Configuration
cleared (Server %s)
The array configuration has
been deleted.
None.
10151
MAJOR
Adapter %s: BBU
voltage problem
detected (Server %s)
Abnormal battery voltage is
detected.
Replace the battery backup unit.
10152
MAJOR
Adapter %s: BBU
temperature problem
detected (Server %s)
Abnormal battery
temperature is detected.
Check the fan status in
ServerView. If the fan has a
failure, follow the corrective
procedure of the server. If the
problem recurs after checking the
surrounding temperature, replace
the battery backup unit.
10153
INFORMA
TIONAL
Adapter %s: BBU
charging (Server %s)
The battery is charging.
None.
10154
CRITICAL
Adapter %s: BBU
failed (Server %s)
A battery has failed.
Replace the battery backup unit.
10155
INFORMA
TIONAL
Adapter %s: BBU
normal (Server %s)
The battery is normal.
None.
10156
INFORMA
TIONAL
Adapter %s: BBU
discharging (Server
%s)
The battery is discharging.
None.
10168
INFORMA
TIONAL
Adapter %s: Logical
drive %s: Name
changed (Server %s)
The name of the logical
drive has been changed.
None.
10171
INFORMA
TIONAL
User %s (%s) logged
in (Server %s)
The user has logged in.
None.
10172
INFORMA
TIONAL
User %s (%s) logged
out (Server %s)
The user has logged out.
None.
10180
INFORMA
TIONAL
Adapter %s: BBU
charging started
(Server %s)
Battery charging has
started.
None.
277
Appendix
table: List of ServerView RAID event logs
ID
278
Severity
Log Entry
Description
Recovery Action
10195
MAJOR
Adapter %s: Unable
to recover cache data
from TBBU (Server
%s)
Cache data could not be
recovered from the battery
backup unit.
Shut down the system properly,
and then restart the system.
10196
INFORMA
TIONAL
Adapter %s: Cache
data recovered from
TBBU successfully
(Server %s)
Cache data has been written
from the battery backup
unit.
None.
10199
INFORMA
TIONAL
Adapter %s: BGI
rate changed (Server
%s)
BGI Rate has been
changed.
None.
10200
INFORMA
TIONAL
Adapter %s: Adapter
cache discarded due
to memory/BBU
problems (Server
%s)
Cache data has been
deleted due to a problem
with the cache memory or
the battery backup unit.
Check the log entries around this
entry and take the necessary
measure.
10202
INFORMA
TIONAL
Adapter %s: Cache
data recovered
successfully (Server
%s)
Cache data has been
recovered successfully.
None.
10203
MINOR
Adapter %s: Adapter
cache discarded due
to firmware version
Incompatibility
(Server %s)
Cache data has been
discarded due to the
difference in firmware
versions.
None.
10204
CRITICAL
Adapter %s: Fatal
firmware error: %s
(Server %s)
A fatal error has occurred
in the firmware.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10205
INFORMA
TIONAL
Adapter %s: Factory
defaults restored
(Server %s)
Factory default has been
restored.
Check the controller's settings and
change them to the correct values.
10206
MAJOR
Adapter %s: Flash
downloaded image
corrupt (Server %s)
The downloaded firmware
image is corrupted.
Update the firmware again using a
correct image.
10207
MAJOR
Adapter %s: Flash
erase error (Server
%s)
The Flash erasure has
failed.
Update the firmware again.
10208
MAJOR
Adapter %s: Flash
timeout during erase
(Server %s)
A timeout has occurred
during the Flash erasure.
Update the firmware again.
10209
MAJOR
Adapter %s: Flash
error (Server %s)
The Flash has failed.
Update the firmware again.
10210
INFORMA
TIONAL
Adapter %s:
Flashing image: %s
(Server %s)
A Flash of the image has
been performed.
None.
10211
INFORMA
TIONAL
Adapter %s: Flash of
new firmware
image(s) complete
(Server %s)
A Flash of the new
firmware image has been
completed.
None.
10212
MAJOR
Adapter %s: Flash
programming error
(Server %s)
An error has occurred
during the Flash
programming.
Update the firmware again.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10213
MAJOR
Adapter %s: Flash
timeout during
programming
(Server %s)
A timeout has occurred
during the Flash
programming.
Update the firmware again.
10214
MINOR
Adapter %s: Flash
chip type unknown
(Server %s)
The chip type of the Flash
is unknown.
Update the firmware again using
the correct image.
Check if the target controller that
needs to be updated is correct.
10215
MAJOR
Adapter %s: Flash
command set
unknown (Server
%s)
The Flash command is
unknown.
Update the firmware again using a
proper tool.
10216
MAJOR
Adapter %s: Flash
verification failure
(Server %s)
The Flash verification has
failed.
Update the firmware again.
10217
INFORMA
TIONAL
Adapter %s: Flush
rate changed to %s
seconds (Server %s)
The Flush Rate has been
changed.
None.
10218
INFORMA
TIONAL
Adapter %s:
Hibernate command
received from host
(Server %s)
The hibernation command
was received from the
server.
None.
10219
INFORMA
TIONAL
Adapter %s: Event
log cleared (Server
%s)
The event log has been
cleared.
None.
10220
INFORMA
TIONAL
Adapter %s: Event
log wrapped (Server
%s)
The event log has reached
the maximum capacity and
old log entries have been
deleted.
None.
10221
MAJOR
Adapter %s: Multibit ECC error:
ECAR=%s
ELOG=%s (%s)
(Server %s)
A multi-bit error has been
detected.
Replace the cache memory or the
battery backup unit. If the problem
recurs, contact an office listed in
the "Contact Information" of "Start
Guide".
10222
MAJOR
Adapter %s: Singlebit ECC error:
ECAR=%s
ELOG=%s (%s)
(Server %s)
A single-bit error has been
detected.
Replace the cache memory or the
battery backup unit. If the problem
recurs, contact an office listed in
the "Contact Information" of "Start
Guide".
10223
MAJOR
Adapter %s: Not
enough adapter
memory (Server %s)
There is not a sufficient
amount of Controller
memory available.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10224
INFORMA
TIONAL
Adapter %s: Patrol
Read rate changed to
%s%% (Server %s)
Patrol Read Rate has been
changed.
None.
10225
INFORMA
TIONAL
Adapter %s:
Migration rate
changed to %s%%
(Server %s)
Capacity Expansion Rate
has been changed.
None.
279
Appendix
table: List of ServerView RAID event logs
280
ID
Severity
Log Entry
Description
Recovery Action
10226
INFORMA
TIONAL
Adapter %s:
Shutdown command
received from host
(Server %s)
The shutdown command
was received from the
server.
None.
10227
INFORMA
TIONAL
Adapter %s: Test
event: '%s' (Server
%s)
A test event has been
issued.
None.
10228
INFORMA
TIONAL
Adapter %s: Time
established as %s;
(%s seconds since
power on) (Server
%s)
The current time has been
set.
None.
10229
INFORMA
TIONAL
Adapter %s: User
entered firmware
debugger (Server
%s)
The firmware has entered
the debug mode.
None.
10230
INFORMA
TIONAL
Adapter %s: BGI
corrected medium
error (logical drive
%s at LBA %s on
disk (%s) at LBA
%s) (Server %s)
A medium error has been
corrected during the
background initialization.
None.
10231
MAJOR
Adapter %s: BGI
completed with
uncorrectable errors
on logical drive %s
(Server %s)
The background
initialization has been
completed, but
unrecoverable errors have
been detected.
If an unreadable file is found
during operation, restore the file
from the backup.
10232
MAJOR
Adapter %s: BGI
detected
uncorrectable
multiple medium
errors (disk (%s) at
LBA %s on logical
drive %s) (Server
%s)
Multiple unrecoverable
media errors have been
detected during the
background initialization.
If an unreadable file is found
during operation, restore the file
from the backup.
10233
MAJOR
Adapter %s: BGI
failed on logical
drive %s (Server %s)
Background initialization
of the logical drive has
failed.
Check the log entries around this
entry and take the necessary
measure.
10235
INFORMA
TIONAL
Adapter %s: Logical
drive %s: %s
changed (Server %s)
A property of the logical
drive has been changed.
None.
10236
INFORMA
TIONAL
Adapter %s: MDC
corrected medium
error (logical drive
%s at LBA %s on
disk (%s) at LBA
%s) (Server %s)
A medium error has been
corrected during Make
Data Consistent.
None.
10240
MAJOR
Adapter %s:
Initialization failed
on logical drive %s
(Server %s)
Foreground initialization
has failed.
Check the log entries around this
entry and take the necessary
measure.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10242
INFORMA
TIONAL
Adapter %s: Fast
initialization started
on logical drive %s
(Server %s)
Fast initialization has
started.
None.
10243
INFORMA
TIONAL
Adapter %s: Full
initialization started
on logical drive %s
(Server %s)
Foreground initialization
has started.
None.
10244
INFORMA
TIONAL
Adapter %s: Logical
drive %s: Property
%s updated (Server
%s)
A property of the logical
drive has been changed.
None.
10245
MAJOR
Adapter %s:
Migration detected
uncorrectable
multiple medium
errors (logical drive
%s at LBA %s on
disk (%s) at LBA
%s) (Server %s)
Multiple unrecoverable
media errors have been
detected during the
capacity expansion.
If an unreadable file is found
during operation, restore the file
from the backup.
10247
INFORMA
TIONAL
Adapter %s:
Migration resumed
on logical drive %s
(Server %s)
Capacity expansion has
resumed.
None.
10248
MAJOR
Adapter %s: Resume
migration of logical
drive %s failed due
to Configuration
Mismatch (Server
%s)
Resumption of the capacity
expansion has failed due to
a mismatched
configuration.
Recreate the array configuration
and restore the data from the
backup.
10249
INFORMA
TIONAL
Adapter %s: State
change on logical
drive %s from
operational to
operational (Server
%s)
The logical drive is now
online.
None.
10250
MINOR
Adapter %s: Clear
aborted on disk (%s)
(Server %s)
PD Clear has been aborted.
None.
10251
MAJOR
Adapter %s: Clear
failed on disk (%s)
(error %s) (Server
%s)
PD Clear has failed.
None.
10252
INFORMA
TIONAL
Adapter %s: Clear
progress on disk
(%s) is %s (Server
%s)
PD Clear is in progress.
None.
10253
INFORMA
TIONAL
Adapter %s: Clear
started on disk (%s)
(Server %s)
PD Clear has started.
None.
10254
INFORMA
TIONAL
Adapter %s: Clear
finished on disk (%s)
(Server %s)
PD Clear has been
completed.
None.
281
Appendix
table: List of ServerView RAID event logs
ID
282
Severity
Log Entry
Description
Recovery Action
10255
MAJOR
Adapter %s: Error
on disk (%s) (error
%s) (Server %s)
An error has occurred on
the hard disk. Error codes
in (Error x) mean as
follows:
240: general failure
243: timeout
244: no drive
250: no path
252: no cable
02: check condition
08: busy
These error codes indicate
the reason why the array
controller has cut the hard
disk. They do not indicate
the cause of a hard disk
failure.
Replace the failed hard disk and
perform rebuild.
10258
MAJOR
Adapter %s: Hot
spare S.M.A.R.T.
polling failed on disk
(%s) (error %s)
(Server %s)
S.M.A.R.T. polling of a
spare disk has failed.
Change the hard disk. After
changing the disk, configure it as a
spare disk.
10259
MAJOR
Adapter %s: Disk
(%s) is not supported
(Server %s)
An unsupported hard disk
has been detected.
Use a supported hard disk.
10260
INFORMA
TIONAL
Adapter %s: Patrol
Read corrected
medium error on
disk (%s) at LBA %s
(Server %s)
A medium error has been
corrected during Patrol
Read.
None.
10262
MAJOR
Adapter %s: Patrol
Read found an
uncorrectable
medium error on
disk (%s) at LBA %s
(Server %s)
Multiple unrecoverable
media errors have been
detected during Patrol
Read.
If an unreadable file is found
during operation, restore the file
from the backup.
10263
MINOR
Adapter %s:
Predictive failure:
Disk (%s) (Server
%s)
A failure has been
predicted for a hard disk.
Replace the hard disk as a
preventive measure.
10264
MAJOR
Adapter %s:
Puncturing bad
block on disk (%s) at
LBA %s (Server %s)
A medium error has been
detected in the source disk
drive during rebuild.
If an unreadable file is found
during operation, restore the file
from the backup.
10265
MINOR
Adapter %s: Rebuild
aborted by user on
disk (%s) (Server
%s)
Rebuilding has been
canceled.
Perform rebuild again.
10266
INFORMA
TIONAL
Adapter %s: Rebuild
complete on logical
drive %s (Server %s)
Rebuilding the logical drive
has been completed.
None.
10267
INFORMA
TIONAL
Adapter %s: Rebuild
complete on disk
(%s) (Server %s)
Rebuilding the hard disk
has been completed.
None.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10269
INFORMA
TIONAL
Adapter %s: Rebuild
resumed on disk
(%s) (Server %s)
Rebuilding has resumed.
None.
10270
INFORMA
TIONAL
Adapter %s: Rebuild
automatically started
on disk (%s) (Server
%s)
Rebuilding the hard disk
has started automatically.
None.
10273
MAJOR
Adapter %s:
Unrecoverable
medium error during
rebuild on disk (%s)
at LBA %s (Server
%s)
An unrecoverable medium
error has been detected
during rebuild.
If an unreadable file is found
during operation, restore the file
from the backup.
10274
INFORMA
TIONAL
Adapter %s:
Corrected medium
error during
recovery on disk
(%s) at LBA %s
(Server %s)
A medium error has been
corrected.
None.
10275
MAJOR
Adapter %s:
Unrecoverable
medium error during
recovery on disk
(%s) at LBA %s
(Server %s)
An unrecoverable media
error has been detected.
If an unreadable file is found
during operation, restore the file
from the backup.
10276
INFORMA
TIONAL
Adapter %s:
Unexpected sense:
Disk (%s), CDB:%s,
Sense:%s (Server
%s)
Sense information of the
hard disk has been reported.
There is no problem as long as the
target hard disk is online because
the controller has performed a
recovery.
10277
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from available to
available (Server
%s)
The hard disk is now
unused.
None.
10278
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
available to available
(Server %s)
The hard disk is now
unused.
None.
10281
MINOR
Adapter %s:
Dedicated hot spare
(%s) no longer
useful due to deleted
array (Server %s)
The dedicated spare disk is
unavailable because the
logical drive was deleted.
The dedicated spare disk is not
supported. Reconfigure the spare
disk.
10282
MINOR
Adapter %s: SAS
topology error: Loop
detected (Server %s)
A loop has been detected in
the SAS topology.
Check the connections of the hard
disks and cables. If this error
recurs, contact an office listed in
the "Contact Information" of "Start
Guide".
283
Appendix
table: List of ServerView RAID event logs
ID
284
Severity
Log Entry
Description
Recovery Action
10283
MINOR
Adapter %s: SAS
topology error:
Unaddressable
device (Server %s)
A device is unaddressable
with the SAS topology.
Check the connections of the hard
disks and cables. If the system
connections are correct, yet a hard
disk has failed, replace the hard
disk and perform rebuild.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10284
MINOR
Adapter %s: SAS
topology error:
Multiple ports to the
same SAS address
(Server %s)
Multiple ports are
connected to the same SAS
address in the SAS
topology.
Check the connections of the hard
disks and cables. If this error
recurs, contact an office listed in
the "Contact Information" of "Start
Guide".
10285
MINOR
Adapter %s: SAS
topology error:
Expander error
(Server %s)
An error has been detected
in the Expander.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10286
MINOR
Adapter %s: SAS
topology error: SMP
timeout (Server %s)
An SMP timeout has been
detected.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10287
MINOR
Adapter %s: SAS
topology error: Out
of route entries
(Server %s)
Route entries cannot be
found.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10288
MINOR
Adapter %s: SAS
topology error:
Index not found
(Server %s)
Index was not found.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10289
MINOR
Adapter %s: SAS
topology error: SMP
function failed
(Server %s)
An error has been detected
in an SMP function.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10290
MINOR
Adapter %s: SAS
topology error: SMP
CRC error (Server
%s)
A CRC error has been
detected in SMP.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10291
MINOR
Adapter %s: SAS
topology error:
Multiple subtractive
(Server %s)
An error has been detected
in the SAS topology.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10292
MINOR
Adapter %s: SAS
topology error: Table
to table (Server %s)
An error has been detected
in the SAS topology.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10293
MINOR
Adapter %s: SAS
topology error:
Multiple paths
(Server %s)
Multiple paths exist.
Check the connections of the hard
disk and cables. If this error recurs,
contact an office listed in the
"Contact Information" of "Start
Guide".
10294
MAJOR
Adapter %s: Unable
to access disk (%s)
(Server %s)
The hard disk cannot be
accessed.
Replace the failed hard disk and
perform rebuild.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10295
MINOR
Adapter %s:
Dedicated hot spare
not useful for all
arrays (Server %s)
No array is available for the
dedicated spare disk.
The dedicated spare disk is not
supported. Reconfigure the spare
disk.
10296
MINOR
Adapter %s: Global
hot spare does not
cover all arrays
(Server %s)
No array is available for a
spare disk.
Check the array configuration to
make the spare disk available.
Check the capacity of the spare
disk.
10297
MINOR
Adapter %s:
Marking logical
drive %s
inconsistent due to
active writes at
shutdown (Server
%s)
The consistency of the
logical drive has been lost
due to shutdown during the
Write operation.
Perform Make Data Consistent.
10298
INFORMA
TIONAL
Adapter %s: BBU
present (Server %s)
A battery backup unit was
detected.
None.
10299
INFORMA
TIONAL
Adapter %s: BBU
not present (Server
%s)
There is no battery backup
unit.
If the system does not have any
battery backup unit, no action is
required.
If the system does have a battery
backup unit, replace the battery
backup unit.
10300
INFORMA
TIONAL
Adapter %s: New
BBU detected
(Server %s)
A new battery backup unit
has been detected.
None.
10301
INFORMA
TIONAL
Adapter %s: BBU
has been replaced
(Server %s)
The battery backup unit has
been replaced.
None.
10302
INFORMA
TIONAL
Adapter %s: BBU
temperature is
normal (Server %s)
The temperature of the
battery backup unit is now
normal.
None.
10303
MINOR
Adapter %s: BBU
needs to be replaced
- SOH bad (Server
%s)
The battery backup unit
needs to be replaced.
The event occurs right after the
battery backup unit replacement.
Due to the insufficiently charged
battery after the replacement, this
event may occur. Follow
"Appendix C Replacing Battery"
(Jpg.327).
The event occurs during regular
operation.
Replace a battery backup unit.
10304
INFORMA
TIONAL
Adapter %s: BBU
relearn started
(Server %s)
Battery recalibration has
started.
None.
10305
INFORMA
TIONAL
Adapter %s: BBU
relearn in progress
(Server %s)
Battery recalibration is in
progress.
None.
10306
INFORMA
TIONAL
Adapter %s: BBU
relearn finished
(Server %s)
Battery recalibration has
been completed.
None.
285
Appendix
table: List of ServerView RAID event logs
ID
286
Severity
Log Entry
Description
Recovery Action
10307
MINOR
Adapter %s: BBU
relearn timed out
(Server %s)
A timeout has occurred
during the battery
recalibration.
Perform recalibration again.
10308
INFORMA
TIONAL
Adapter %s: BBU
relearn pending:
BBU is under charge
(Server %s)
The battery is charging and
the battery recalibration is
in wait mode.
None.
10309
INFORMA
TIONAL
Adapter %s: BBU
relearn postponed
(Server %s)
BBU recondition has been
postponed.
Automatic Learn is not supported.
Check the battery backup unit
settings.
10310
INFORMA
TIONAL
Adapter %s: BBU
relearn will start in 4
days (Server %s)
Battery recalibration will
start within 4 days.
Automatic Learn is not supported.
Check the battery backup unit
settings.
10311
INFORMA
TIONAL
Adapter %s: BBU
relearn will start in 2
day (Server %s)
Battery recalibration will
start within 2 days.
Automatic Learn is not supported.
Check the battery backup unit
settings.
10312
INFORMA
TIONAL
Adapter %s: BBU
relearn will start in 1
day (Server %s)
Battery recalibration will
start within 1 day.
Automatic Learn is not supported.
Check the battery backup unit
settings.
10313
INFORMA
TIONAL
Adapter %s: BBU
Relearn will start in
5 hours (Server %s)
Battery recalibration will
start within 5 hours.
Automatic Learn is not supported.
Check the battery backup unit
settings.
10314
MINOR
Adapter %s: BBU
removed (Server %s)
The battery backup unit
was removed.
Extremely low voltage of a battery
after battery replacement may
result in this event. If ID: 10298
"BBU present" is recorded, there is
no problem. Follow "Appendix C
Replacing Battery" (Jpg.327). If
ID: 10298 "BBU present" is not
recorded, check if a battery backup
unit is correctly installed.
10315
INFORMA
TIONAL
Adapter %s:
Enclosure (SES)
discovered on %s
(Server %s)
SES enclosure has been
detected.
None.
10317
MINOR
Adapter %s:
Enclosure %s
communication lost
(Server %s)
Communication with
enclosure has been cut.
Check the cable connections. If
this problem recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10318
INFORMA
TIONAL
Adapter %s:
Enclosure %s
communication
restored (Server %s)
Communication with
enclosure has been
restored.
None.
10325
MINOR
Adapter %s:
Enclosure %s not
supported; too many
enclosures
connected to port
(Server %s)
Enclosure is not working
because the number of
enclosures detected are
more than those supported.
Check the cable connections. If
this problem recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10331
MINOR
Adapter %s:
Enclosure %s not
responding (Server
%s)
Enclosure is not
responding.
Check the cable connections. If
this problem recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10332
MINOR
Adapter %s: SAS/
SATA mixing not
supported in
enclosure; %s
disabled (Server %s)
SAS/SATA mix is not
supported in enclosure.
Replace it with the supported hard
disk.
10333
INFORMA
TIONAL
Adapter %s:
Enclosure (SES) hot
plug on %s was
detected, but is not
supported (Server
%s)
SES enclosure has been hot
plugged.
None.
10336
MINOR
Adapter %s: Disk
(%s) too small to be
used for auto rebuild
(Server %s)
The hard disk capacity is
insufficient for rebuild.
Replace the hard disk with one of
sufficient capacity.
10337
INFORMA
TIONAL
Adapter %s: BBU
enabled; changing
Write-through
logical drives to
Write-back (Server
%s)
The battery backup unit has
been enabled. The logical
drive operation mode has
switched from the Write
Through mode to the Write
Back mode.
None.
10338
MINOR
Adapter %s: BBU
disabled; changing
Write-back logical
drives to Writethrough (Server %s)
The battery backup unit has
been disabled. The logical
drive operation mode has
switched from the Write
Back mode to the Write
Through mode.
The event occurs at the system
start right after the battery backup
unit replacement.
Due to the insufficiently charged
battery after the replacement, this
event may occur. Follow
"Appendix C Replacing Battery"
(Jpg.327).
The event occurs at the regular
system start.
Turn on the server for 12 hours or
more after the event occurs, and
charge the battery. Replace the
battery backup unit if ID:10337
does not occur after 12hours.
The event occurs during regular
operation.
There is no problem if it occurs
during battery recalibration
(including the scheduled one). If
not, replace the battery backup
unit.
10339
INFORMA
TIONAL
Adapter %s: Bad
block table on disk
(%s) is 80% full
(Server %s)
The Bad Block Table use
rate has exceeded 80%.
A large number of uncorrectable
bad block occurred. If an
unreadable file is found during
operation, restore the file from the
backup.
287
Appendix
table: List of ServerView RAID event logs
ID
288
Severity
Log Entry
Description
Recovery Action
10340
MINOR
Adapter %s: Bad
block table on disk
(%s) is full; unable
to log Block %s
(Server %s)
The Bad Block Table is
full.
A large number of uncorrectable
bad block occurred. If an
unreadable file is found during
operation, restore the file from the
backup.
10341
MINOR
Adapter %s: MDC
aborted due to
ownership loss on
logical drive %s
(Server %s)
Make Data Consistent has
been aborted due to an
ownership change.
If necessary, perform Make Data
Consistent again.
10342
MINOR
Adapter %s: BGI
aborted due to
ownership loss on
logical drive %s
(Server %s)
Background initialization
has been aborted due to an
ownership change.
None.
10343
MINOR
Adapter %s: BBU/
charger problems
detected; SOH bad
(Server %s)
A battery charger problem
has been detected.
Replace the battery backup unit.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10344
MINOR
Adapter %s: Singlebit ECC error:
ECAR=%s
ELOG=%s (%s);
warning threshold
exceeded (Server
%s)
A single-bit error has been
detected.
Replace the cache memory or the
battery backup unit.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10345
MINOR
Adapter %s: Singlebit ECC error:
ECAR=%s,
ELOG=%s, (%s);
critical threshold
exceeded (Server
%s)
A single-bit error has been
detected.
Replace the cache memory or the
battery backup unit.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10346
INFORMA
TIONAL
Adapter %s: Singlebit ECC error:
ECAR=%s
ELOG=%s (%s);
further reporting
disabled (Server %s)
A single-bit error has been
detected.
Replace the cache memory or the
battery backup unit.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10353
INFORMA
TIONAL
Adapter %s:
Retention test started
on previous reboot
(Server %s)
The NVRAM retention test
has started.
None.
10354
INFORMA
TIONAL
Adapter %s:
NVRAM Retention
test passed (Server
%s)
The NVRAM retention test
has been completed.
None.
10355
MINOR
Adapter %s:
NVRAM retention
test failed (Server
%s)
The NVRAM retention test
has failed.
Contact an office listed in the
"Contact Information" of "Start
Guide".
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10356
INFORMA
TIONAL
Adapter %s: %s test
finished %s passes
successfully (Server
%s)
The test has been
completed.
None.
10357
MINOR
Adapter %s: %s test
FAILED on %s pass.
fail data:
errorOffset=%s
goodData=%s
badData=%s (Server
%s)
The test has failed.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10358
INFORMA
TIONAL
Adapter %s: Selfcheck diagnostics
finished (Server %s)
The self-test has been
completed.
None.
10359
INFORMA
TIONAL
Adapter %s: Foreign
configuration
detected (Server %s)
Foreign Configuration has
been detected.
None.
10360
INFORMA
TIONAL
Adapter %s: Foreign
configuration
imported (Server
%s)
Foreign Configuration has
been imported.
None.
10361
INFORMA
TIONAL
Adapter %s: Foreign
configuration
cleared (Server %s)
Foreign Configuration has
been cleared.
None.
10362
MINOR
Adapter %s:
NVRAM is corrupt;
reinitializing (Server
%s)
The NVRAM had a failure
and re-initialization is in
progress.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10363
MINOR
Adapter %s:
NVRAM mismatch
occurred (Server %s)
An NVRAM mismatch has
occurred.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10364
MINOR
Adapter %s: SAS
wide port %s lost
link on PHY %s
(Server %s)
The SAS wide port has lost
its link.
Check the connections of the hard
disk and cables. If the system
connections are correct, yet a hard
disk has failed, replace the hard
disk and perform rebuild.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10365
INFORMA
TIONAL
Adapter %s: SAS
wide port %s
restored link on PHY
%s (Server %s)
The SAS wide port has
restored its link.
None.
10366
MINOR
Adapter %s: SAS
port %s PHY %s has
exceeded the
allowed error rate
(Server %s)
The errors in the SAS port
have exceeded the
permissible limit.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10367
MINOR
Adapter %s: Bad
block reassigned on
disk (%s) from LBA
%s to LBA %s
(Server %s)
A bad block of the hard
disk has been relocated.
None.
289
Appendix
table: List of ServerView RAID event logs
ID
290
Severity
Log Entry
Description
Recovery Action
10369
MINOR
Adapter %s:
Enclosure %s
temperature sensor
%s differential
detected (Server %s)
An enclosure temperature
difference was detected.
None.
10371
INFORMA
TIONAL
Adapter %s: Time
duration provided by
host is not sufficient
for self-checking
(Server %s)
The system has not
provided enough time for
self-checking.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10372
INFORMA
TIONAL
Adapter %s: Disk
(%s) on array %s
row %s marked
missing (Server %s)
The hard disk has been
marked as missing.
Replace the failed hard disk and
perform rebuild.
10373
INFORMA
TIONAL
Adapter %s: Disk
(%s) replaced
missing on array %s
row %s (Server %s)
Replace Missing of the
hard disk has been
performed.
None.
10377
MINOR
Adapter %s: Disk
(%s) is not certified
(Server %s)
The hard disk is not a
certified disk.
Replace the hard disk with a
certified disk.
10378
MINOR
Adapter %s: Dirty
cache data discarded
by user (Server %s)
Dirty cache data has been
discarded by user.
Perform Make Data Consistent.
10382
MINOR
Adapter %s:
Previous
configuration
completely missing
at boot (Server %s)
The previous configuration
was not found during
startup.
Turn off the server and check that
hard disks, cables, the power
supply, etc. are connected
properly.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
10383
INFORMA
TIONAL
Adapter %s: BBU
charge complete
(Server %s)
The battery charging has
been completed.
None.
10385
INFORMA
TIONAL
Adapter %s:
Dedicated hot spare
(%s) imported as
global due to
missing arrays
(Server %s)
The dedicated spare disk
has been imported as a
spare disk because the
target array does not exist.
None.
10386
INFORMA
TIONAL
Adapter %s: Disk
(%s) rebuild not
possible as SAS/
SATA is not
supported in an array
(Server %s)
Rebuilding the hard disk is
not possible because SAS/
SATA is not supported.
None.
10388
MAJOR
Adapter %s: Logical
drive %s partially
degraded (Server
%s)
The logical drive is now
critical.
Replace the failed hard disk and
perform rebuild.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
10389
INFORMA
TIONAL
10390
Log Entry
Description
Recovery Action
Adapter %s: BBU
requires
reconditioning;
please initiate a
LEARN cycle
(Server %s)
Recalibration is necessary.
Perform recalibration on a battery
backup unit.
INFORMA
TIONAL
Adapter %s:
Coercion mode
changed (Server %s)
The coercion mode has
been changed.
None.
10391
INFORMA
TIONAL
Adapter %s: BBU
automatic learn
mode changed
(Server %s)
The Autolearn mode of the
battery has been changed.
None.
10392
INFORMA
TIONAL
Adapter %s: BBU
atomatic learn period
changed (Server %s)
The Autolearn period of the
battery has been changed.
None.
10393
INFORMA
TIONAL
Adapter %s: BBU
learn delay interval
changed (Server %s)
The delay interval for the
battery has been changed.
None.
10394
INFORMA
TIONAL
Adapter %s: BBU
next learn time
changed (Server %s)
The time for next battery
recalibration has been
changed.
None.
10395
INFORMA
TIONAL
Adapter %s: Max.
disk count for Patrol
Read changed to %s
(Server %s)
The Max. Physical Drive
Count of Patrol Read has
been changed.
None.
10396
INFORMA
TIONAL
Adapter %s:
Continuous
patrolling enabled
(Server %s)
Continuous patrolling has
been enabled.
None.
10397
INFORMA
TIONAL
Adapter %s:
Continuous
patrolling disabled
(Server %s)
Continuous patrolling has
been disabled.
None.
10398
MAJOR
Adapter %s: MDC
finished with errors
on logical drive %s
(Server %s)
Make Data Consistent has
been completed, but
multiple media errors were
detected during the Make
Data Consistent.
If an unreadable file is found
during operation, restore the file
from the backup.
10399
INFORMA
TIONAL
Adapter %s: Logical
drive %s disabled
because RAID-5 is
not supported by this
RAID key (Server
%s)
The logical drive has been
disabled because RAID 5 is
not supported by the RAID
key.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10400
INFORMA
TIONAL
Adapter %s: Logical
drive %s disabled
because RAID-6 is
not supported by this
RAID key (Server
%s)
The logical drive has been
disabled because RAID 6 is
not supported by the RAID
key.
Contact an office listed in the
"Contact Information" of "Start
Guide".
291
Appendix
table: List of ServerView RAID event logs
ID
292
Severity
Log Entry
Description
Recovery Action
10401
MINOR
Adapter %s: Logical
drive %s disabled
because SAS drives
are not supported by
this RAID key
(Server %s)
The logical drive has been
disabled because the SAS
hard disks are not
supported by the RAID key.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10402
MINOR
Adapter %s: Disks
missing (Server %s)
The hard disk does not
exist.
Replace the failed hard disk and
perform rebuild.
10403
INFORMA
TIONAL
Adapter %s: Rebuild
rate changed to
%s%% (Server %s)
Rebuild Rate has been
changed.
None.
10405
INFORMA
TIONAL
Adapter %s:
S.M.A.R.T. poll
interval changed to
%s min (Server %s)
S.M.A.R.T. poll interval
has been changed.
None.
10406
INFORMA
TIONAL
Adapter %s: MDC
started on logical
drive %s (Server %s)
Make Data Consistent has
started.
None.
10407
INFORMA
TIONAL
Adapter %s: MDC
finished on logical
drive %s (Server %s)
Make Data Consistent has
been completed.
None.
10408
MAJOR
Adapter %s: MDC
failed on logical
drive %s (Server %s)
Make Data Consistent has
failed.
Replace the failed hard disk and
perform rebuild.
10409
MINOR
Adapter %s: MDC
aborted on logical
drive %s (Server %s)
Make Data Consistent has
been aborted.
If necessary, perform Make Data
Consistent again.
10412
MAJOR
Adapter %s: State
change on logical
drive %s from
operational to
degraded (Server
%s)
The logical drive has
changed from online to
critical.
Replace the failed hard disk and
perform rebuild.
10413
MAJOR
Adapter %s: State
change on logical
drive %s from
operational to
partially degraded
(Server %s)
The logical drive has
changed from online to
partially critical.
Replace the failed hard disk and
perform rebuild.
10414
CRITICAL
Adapter %s: State
change on logical
drive %s from
operational to failed
(Server %s)
The logical drive has
changed from online to
offline.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10415
INFORMA
TIONAL
Adapter %s: State
change on logical
drive %s from
degraded to
operational (Server
%s)
The logical drive has been
restored from critical to
online.
None.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10416
MAJOR
Adapter %s: State
change on logical
drive %s from
degraded to
degraded (Server
%s)
The logical drive is now
critical.
Replace the failed hard disk and
perform rebuild.
10417
MAJOR
Adapter %s: State
change on logical
drive %s from
degraded to partially
degraded (Server
%s)
The logical drive is now
partially critical.
Replace the failed hard disk and
perform rebuild.
10418
CRITICAL
Adapter %s: State
change on logical
drive %s from
degraded to failed
(Server %s)
The logical drive has
changed from critical to
offline.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10419
INFORMA
TIONAL
Adapter %s: State
change on logical
drive %s from
partially degraded to
operational (Server
%s)
The logical drive has been
restored from critical to
online.
None.
10420
MAJOR
Adapter %s: State
change on logical
drive %s from
partially degraded to
degraded (Server
%s)
The logical drive is now
critical.
Replace the failed hard disk and
perform rebuild.
10421
MAJOR
Adapter %s: State
change on logical
drive %s from
partially degraded to
partially degraded
(Server %s)
The logical drive is now
critical.
Replace the failed hard disk and
perform rebuild.
10422
CRITICAL
Adapter %s: State
change on logical
drive %s from
partially degraded to
failed (Server %s)
The logical drive has
changed from partially
critical to offline.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10423
INFORMA
TIONAL
Adapter %s: State
change on logical
drive %s from failed
to operational
(Server %s)
The logical drive has
changed from offline to
online.
None.
10424
MAJOR
Adapter %s: State
change on logical
drive %s from failed
to degraded (Server
%s)
The logical drive has
changed from offline to
critical.
Replace the failed hard disk and
perform rebuild.
293
Appendix
table: List of ServerView RAID event logs
ID
294
Severity
Log Entry
Description
Recovery Action
10425
MAJOR
Adapter %s: State
change on logical
drive %s from failed
to partially degraded
(Server %s)
The logical drive has
changed from offline to
partially critical.
Replace the failed hard disk and
perform rebuild.
10426
CRITICAL
Adapter %s: State
change on logical
drive %s from failed
to failed (Server %s)
The logical drive is now
offline.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10427
CRITICAL
Adapter %s: State
change by user on
disk (%s) from
available to failed
(Server %s)
The hard disk has changed
from unused to failed.
Replace the failed hard disk.
10428
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
available to hot spare
(Server %s)
The hard disk has changed
from the unused to a spare
disk.
None.
10429
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
available to
rebuilding (Server
%s)
The hard disk has changed
from unused to rebuilding.
None.
10430
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
available to
operational (Server
%s)
The hard disk has changed
from unused to online.
None.
10431
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from failed
to available (Server
%s)
The hard disk has changed
from failed to unused.
None.
10432
CRITICAL
Adapter %s: State
change by user on
disk (%s) from failed
to failed (Server %s)
The hard disk is now failed.
Replace the failed hard disk and
perform rebuild.
10433
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from failed
to hot spare (Server
%s)
The hard disk has changed
from the failed to a spare
disk.
None.
10434
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from failed
to rebuilding (Server
%s)
The hard disk has changed
from failed to rebuilding.
None.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10435
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from failed
to operational
(Server %s)
The hard disk has changed
from failed to online.
None.
10436
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from hot
spare to available
(Server %s)
The hard disk has changed
from a spare disk to the
unused.
None.
10437
CRITICAL
Adapter %s: State
change by user on
disk (%s) from hot
spare to failed
(Server %s)
The hard disk has changed
from a spare disk to the
failed.
Replace the failed hard disk and
configure the new disk as a spare
disk.
10438
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from hot
spare to hot spare
(Server %s)
The hard disk is now a
spare disk.
None.
10439
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from hot
spare to rebuilding
(Server %s)
The hard disk has changed
from a spare disk to the
rebuilding.
None.
10440
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from hot
spare to operational
(Server %s)
The hard disk has changed
from a spare disk to the
online.
None.
10441
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
rebuilding to
available (Server
%s)
The hard disk has changed
from rebuilding to unused.
None.
10442
CRITICAL
Adapter %s: State
change by user on
disk (%s) from
rebuilding to failed
(Server %s)
The hard disk has changed
from rebuilding to failed.
Replace the failed hard disk and
perform rebuild.
10443
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
rebuilding to hot
spare (Server %s)
The hard disk has changed
from the rebuilding to a
spare disk.
None.
10444
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
rebuilding to
rebuilding (Server
%s)
The hard disk is now
rebuilding.
None.
295
Appendix
table: List of ServerView RAID event logs
296
ID
Severity
Log Entry
Description
Recovery Action
10445
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
rebuilding to
operational (Server
%s)
The hard disk has changed
from rebuilding to online.
None.
10446
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
operational to
available (Server
%s)
The hard disk has changed
from online to unused.
None.
10447
CRITICAL
Adapter %s: State
change by user on
disk (%s) from
operational to failed
(Server %s)
The hard disk has changed
from online to failed.
Replace the failed hard disk and
perform rebuild.
10448
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
operational to hot
spare (Server %s)
The hard disk has changed
from the online to a spare
disk.
None.
10449
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
operational to
rebuilding (Server
%s)
The hard disk has changed
from online to rebuilding.
None.
10450
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
operational to
operational (Server
%s)
The hard disk is now
online.
None.
10451
CRITICAL
Adapter %s: State
change on disk (%s)
from available to
failed (Server %s)
The hard disk has changed
from unused to failed.
Replace the failed hard disk.
10452
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from available to hot
spare (Server %s)
The hard disk has changed
from the unused to a spare
disk.
None.
10453
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from available to
rebuilding (Server
%s)
The hard disk has changed
from unused to rebuilding.
None.
10454
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from available to
operational (Server
%s)
The hard disk has changed
from unused to online.
None.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10455
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from failed to
available (Server
%s)
The hard disk has changed
from failed to unused.
None.
10456
CRITICAL
Adapter %s: State
change on disk (%s)
from failed to failed
(Server %s)
The hard disk is now failed.
Replace the failed hard disk and
perform rebuild.
10457
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from failed to hot
spare (Server %s)
The hard disk has changed
from the failed to a spare
disk.
None.
10458
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from failed to
rebuilding (Server
%s)
The hard disk has changed
from failed to rebuilding.
None.
10459
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from failed to
operational (Server
%s)
The hard disk has changed
from failed to online.
None.
10460
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from hot spare to
available (Server
%s)
The hard disk has changed
from a spare disk to the
unused.
None.
10461
CRITICAL
Adapter %s: State
change on disk (%s)
from hot spare to
failed (Server %s)
The hard disk has changed
from a spare disk to the
failed.
Replace the failed hard disk and
configure the new disk as a spare
disk.
10462
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from hot spare to hot
spare (Server %s)
The hard disk is now a
spare disk.
None.
10463
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from hot spare to
rebuilding (Server
%s)
The hard disk has changed
from a spare disk to the
rebuilding.
None.
10464
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from hot spare to
operational (Server
%s)
The hard disk has changed
from a spare disk to the
online.
None.
10465
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from rebuilding to
available (Server
%s)
The hard disk has changed
from rebuilding to unused.
None.
297
Appendix
table: List of ServerView RAID event logs
298
ID
Severity
Log Entry
Description
Recovery Action
10466
CRITICAL
Adapter %s: State
change on disk (%s)
from rebuilding to
failed (Server %s)
The hard disk has changed
from rebuilding to failed.
Replace the failed hard disk and
perform rebuild.
10467
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from rebuilding to
hot spare (Server
%s)
The hard disk has changed
from the rebuilding to a
spare disk.
None.
10468
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from rebuilding to
rebuilding (Server
%s)
The hard disk is now
rebuilding.
None.
10469
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from rebuilding to
operational (Server
%s)
The hard disk has changed
from rebuilding to online.
None.
10470
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from operational to
available (Server
%s)
The hard disk has changed
from online to unused.
None.
10471
CRITICAL
Adapter %s: State
change on disk (%s)
from operational to
failed (Server %s)
The hard disk has changed
from online to failed.
Replace the failed hard disk and
perform rebuild.
10472
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from operational to
hot spare (Server
%s)
The hard disk has changed
from the online to a spare
disk.
None.
10473
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from operational to
rebuilding (Server
%s)
The hard disk has changed
from online to rebuilding.
None.
10474
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from operational to
operational (Server
%s)
The hard disk is now
online.
None.
10475
MAJOR
Adapter %s: MDC
detected
uncorrectable
multiple medium
errors (disk (%s) at
LBA %s on logical
drive %s) (Server
%s)
Multiple media errors have
been detected during Make
Data Consistent.
If an unreadable file is found
during operation, restore the file
from the backup.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10476
MAJOR
Adapter %s: Disk
(%s) missing after
reboot (Server %s)
A hard disk was not found
after reboot.
This may occur at the restart after
adding or removing option cards.
Check the array condition with
ServerView RAID Manager. If it is
OK, there is no problem. Also,
there is no problem if the condition
is the same as the one described at
"1.5.4 Using ServerView RAID
under the Windows 2000 Server
Environment" (Jpg.42). If there
is a failed hard disk, replace it and
rebuild the new one.
10477
MAJOR
Adapter %s: Logical
drive (%s) missing
after reboot (Server
%s)
A logical drive was not
found after reboot.
This may occur at the restart after
adding or removing option cards.
Check the array condition with
ServerView RAID Manager. If it is
OK, there is no problem. Also,
there is no problem if , after
changing array configuration, the
condition is the same as the one
described at "1.5.4 Using
ServerView RAID under the
Windows 2000 Server
Environment" (Jpg.42).
If this error occurs during regular
operation, contact an office listed
in the "Contact Information" of
"Start Guide".
10478
INFORMA
TIONAL
Adapter %s: Disk
(%s) appeared new
after reboot (Server
%s)
A new hard disk has been
found after the reboot.
None.
10479
INFORMA
TIONAL
Adapter %s: Logical
drive %s appeared
new after reboot
(Server %s)
A new logical drive has
been found after the reboot.
None.
10485
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from available to
offline (Server %s)
The hard disk has changed
from unused to offline.
None.
10486
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
available to offline
(Server %s)
The hard disk has changed
from unused to offline.
None.
10487
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from failed
to offline (Server
%s)
The hard disk has changed
from failed to offline.
None.
299
Appendix
table: List of ServerView RAID event logs
ID
300
Severity
Log Entry
Description
Recovery Action
10488
MINOR
Adapter %s: State
change by user on
disk (%s) from hot
spare to offline
(Server %s)
The hard disk has changed
from a spare disk to the
offline.
Replace the failed hard disk and
perform rebuild.
10489
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
offline to available
(Server %s)
The hard disk has changed
from offline to unused.
None.
10490
MAJOR
Adapter %s: State
change by user on
disk (%s) from
offline to failed
(Server %s)
The hard disk has changed
from offline to failed.
Replace the failed hard disk and
perform rebuild.
10491
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
offline to hot spare
(Server %s)
The hard disk has changed
from the offline to a spare
disk.
None.
10492
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
offline to offline
(Server %s)
The hard disk has changed
from offline to offline.
None.
10493
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
offline to operational
(Server %s)
The hard disk has changed
from offline to online.
None.
10494
INFORMA
TIONAL
Adapter %s: State
change by user on
disk (%s) from
offline to rebuilding
(Server %s)
The hard disk has changed
from offline to rebuilding.
None.
10495
MINOR
Adapter %s: State
change by user on
disk (%s) from
operational to offline
(Server %s)
The hard disk has changed
from online to offline.
Replace the failed hard disk and
perform rebuild.
10496
MINOR
Adapter %s: State
change by user on
disk (%s) from
rebuilding to offline
(Server %s)
The hard disk has changed
from rebuilding to offline.
Replace the failed hard disk and
perform rebuild.
10497
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from failed to offline
(Server %s)
The hard disk has changed
from failed to offline.
None.
10498
MINOR
Adapter %s: State
change on disk (%s)
from hot spare to
offline (Server %s)
The hard disk has changed
from a spare disk to the
offline.
Replace the failed hard disk and
perform rebuild.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10499
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from offline to
available (Server
%s)
The hard disk has changed
from offline to unused.
None.
10500
MAJOR
Adapter %s: State
change on disk (%s)
from offline to failed
(Server %s)
The hard disk has changed
from offline to failed.
Replace the failed hard disk and
perform rebuild.
10501
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from offline to hot
spare (Server %s)
The hard disk has changed
from the offline to a spare
disk.
None.
10502
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from offline to
offline (Server %s)
The hard disk has changed
from offline to offline.
None.
10503
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from offline to
operational (Server
%s)
The hard disk has changed
from offline to online.
None.
10504
INFORMA
TIONAL
Adapter %s: State
change on disk (%s)
from offline to
rebuilding (Server
%s)
The hard disk has changed
from offline to rebuilding.
None.
10505
MINOR
Adapter %s: State
change on disk (%s)
from operational to
offline (Server %s)
The hard disk has changed
from online to offline.
Replace the failed hard disk and
perform rebuild.
10506
MINOR
Adapter %s: State
change on disk (%s)
from rebuilding to
offline (Server %s)
The hard disk has changed
from rebuilding to offline.
Replace the failed hard disk and
perform rebuild.
10509
INFORMA
TIONAL
Adapter %s: Rebuild
on disk (%s)
resumed (Server %s)
Rebuild resumes on the
hard disk.
None.
10511
INFORMA
TIONAL
Adapter %s: BGI
restarted on logical
drive %s (Server %s)
Background initialization
resumes on the logical drive.
None.
10513
INFORMA
TIONAL
Adapter %s: Rebuild
on logical drive %s
resumed (Server %s)
Rebuild resumes on the
logical drive.
None.
10518
MAJOR
Adapter %s: SAS
port %s lost link
(Server %s)
SAS link has been lost.
Check the cable connection. If this
occurs again, contact an office
listed in the "Contact Information"
of "Start Guide".
10519
INFORMA
TIONAL
Adapter %s: SAS
port %s restored link
(Server %s)
SAS link has been restored.
None.
301
Appendix
table: List of ServerView RAID event logs
302
ID
Severity
Log Entry
Description
Recovery Action
10526
CRITICAL
Adapter %s: Adapter
missing after reboot
(Server %s)
The controller has been
missing.
This is not a problem if this occurs
after removal of the array
controller. Otherwise, contact an
office listed in the "Contact
Information" of "Start Guide".
10527
INFORMA
TIONAL
Adapter %s: Adapter
appeared new after
reboot (Server %s)
A new controller has been
detected.
None.
10528
MINOR
Adapter %s: Rebuild
aborted on disk (%s)
(Server %s)
Rebuild has been aborted.
If there are failed hard disks,
replace and rebuild them.
10536
CRITICAL
Adapter %s:
Command timeout
on disk (%s),
CDB:%s (Server
%s)
Command timeout has been
occurred.
If there are failed hard disks,
replace and rebuild them.
10537
MINOR
Adapter %s: Disk
(%s) reset (type %s)
(Server %s)
Reset has been issued to the
hard disk.
If there are failed hard disks,
replace and rebuild them.
10540
MAJOR
Adapter %s:
Uncorrectable
medium error logged
for logical drive %s
at LBA %s (on disk
(%s) at LBA %s)
(Server %s)
An uncorrectable error has
been detected.
If an unreadable file is found
during operation, restore the file
from the backup.
10541
MINOR
Adapter %s:
Medium error
corrected on logical
drive %s at LBA %s
(Server %s)
Media errors have been
restored.
None.
10542
MINOR
Adapter %s: Bad
block table on disk
(%s) is 100%% full
(Server %s)
Bad Block Table of the
hard disk is full.
A large number of uncorrectable
bad block occurred. If an
unreadable file is found during
operation, restore the file from the
backup.
10544
CRITICAL
Adapter %s: Adapter
needs replacement,
faulty IOP detected
(Server %s)
Failures have been detected
in the controller IO
processor.
Contact an office listed in the
"Contact Information" of "Start
Guide".
10559
INFORMA
TIONAL
Adapter %s:
Additional
information for
failed disk (%s) firmware version:
%s, serial number
%s, first use: %s,
total running time:
%s days (Server %s)
Information on additional
SATA hard disk appears:
the firmware version of the
failed SATA, the serial
number, the date of the first
use, and the total running
time.
None.
MegaRAID SAS User's Guide
table: List of ServerView RAID event logs
ID
Severity
Log Entry
Description
Recovery Action
10560
INFORMA
TIONAL
Adapter %s: If the
logical size of
logical drive %s has
changed use
appropriate
operating system
tool to reread disk
information (Server
%s)
Information on the OS
needs to be updated as the
logical drive capacity has
been changed.
None.
10561
INFORMA
TIONAL
Adapter %s:
Enclosure device
exposure changed
(Server %s)
The setting for enclosure
display has been changed.
None.
10572
MAJOR
Adapter %s: Cache
discarded for
missing or offline
logical drive %s
(Server %s)
The data stored in a cache
has been discarded for the
logical drive was
inaccessible.
Shut down the system properly,
and then restart the system.
303
Appendix
B
List of GAM Event Log
With ServerView installed, occurred events are recorded in the OS event logs by
ServerView.
• For Windows
Events are recorded by the Event Viewer application log from the source "Fujitsu ServerView
Services".
• For Linux
Events are recorded in the system log from the source "Fujitsu ServerView Services".
The device address is filled in at the beginning of the event log (the bracketed part). The device address
indicates where the event occurred.
table: Meaning of event log strings
Character String
Meaning
ctl:
Controller ID
chn:
Slot number of hard disk
tgt:
Not used by this array controller.
logdrv:
Logical drive number
` Unless ServerView is installed, event logging to Event Viewer will not occur. See "User’s Guide"
located on "PRIMERGY Startup Disc" supplied with the server to install and configure ServerView.
The correspondence between severity for GAM events (SNMP TRAP), severity for GAM Client, and
the event log type is shown in the table below.
table: Event log types and descriptions
Severity
304
Description
Severity in GAM Client
OS event log type
CRITICAL
Severe error
1
Error
MAJOR
Error
2
Error
MINOR
Warning
3
Warning
INFORMATIONAL
Information (No
action required)
4
Information
MegaRAID SAS User's Guide
„ List of GAM event logs
` The number within the parentheses in the GAM ID appears in hexadecimal format.
` The GAM IDs in decimal format represent Specific Numbers on SNMP trap.
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
1
(0x001)
Info/1
A physical disk has
been placed online.
A hard disk has become
online.
None.
2
(0x002)
Info/1
Physical disk
added as hot spare.
A hard disk has been set as
a hot spare.
None.
3
(0x003)
Error/3
Physical disk error
found.
• A bad sector was found
on the hard disk.
• A mechanical failure of
the device.
• The host device
detected an invalid
sequence.
• The target device is
missing.
Check the state of the target hard
disk. If it has a failure, see "6.2.2
Replacing Failed Hard Disk
[GAM]" (Jpg.261) to replace it
and perform rebuild. If the error
occurred only temporarily and
does not recur, the hard disk is
recovered and no action is
required. However, if this error
occurs frequently, we recommend
that you replace the disk as a
preventive measure, referring to
"6.2.3 Preventive Replacement of
hard disk [GAM]" (Jpg.263).
4
(0x004)
Error/3
Physical disk PFA
condition found;
this disk may fail
soon.
A failure has been
predicted for the hard
disk.
See "6.2.3 Preventive Replacement
of hard disk [GAM]" (Jpg.263)
and replace the hard disk as a
preventive measure.
5
(0x005)
Info/1
An automatic
rebuild has started.
Rebuild has started
automatically.
None.
6
(0x006)
Info/1
A rebuild has
started.
Rebuild has started by
user.
None.
7
(0x007)
Info/1
Rebuild is over.
Rebuild is completed.
None.
8
(0x008)
Info/1
Rebuild is
cancelled.
Rebuild has been
canceled.
Perform rebuild again.
9
(0x009)
Error/3
Rebuild stopped
with error.
Rebuild failed for some
reasons.
See "5.9.4 Viewing Logical Drive
Information" (Jpg.234) to check
the current status of the logical
drive.
• For critical state:
See "6.2.2 Replacing Failed
Hard Disk [GAM]" (Jpg.261)
to replace the hard disk and
perform rebuild again.
• For offline state:
Contact an office listed in the
"Contact Information" of "Start
Guide".
305
Appendix
table: List of GAM event logs
GAM ID
306
Severity
Description
Details
Corrective action
10
(0x00A)
Error/3
Rebuild stopped
with error. New
device failed.
Rebuild failed due to a
failure found on the target
hard disk for the rebuild.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
11
(0x00B)
Error/3
Rebuild stopped
because logical
drive failed.
Rebuild failed due to
failures in multiple hard
disks.
Contact an office listed in the
"Contact Information" of "Start
Guide".
12
(0x00C)
Error/3
Physical disk has
failed.
A hard disk has failed.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
13
(0x00D)
Info/1
A new physical
disk has been
found.
A new hard disk was
detected.
None.
14
(0x00E)
Info/1
A physical disk has
been removed.
A hard disk was removed.
A hard disk has become
undetectable.
None.
15
(0x00F)
Info/1
A previously
configured disk is
now available.
A hard disk is now in
Unconfigured state.
None.
16
(0x010)
Info/1
Expand Capacity
Started.
A capacity expansion
process has started.
None.
17
(0x011)
Info/1
Expand Capacity
Completed.
The capacity expansion
has been completed.
None.
18
(0x012)
Error/3
Expand Capacity
Stopped with error.
Multiple hard disks failed
and the capacity
expansion process
terminated abnormally.
Recreate the array configuration
and restore the data from backup.
19
(0x013)
Error/3
SCSI command
timeout on hard
device.
A command timeout was
detected.
Because the controller is
performing a recovery, there is no
problem as long as there are no
failed hard disks.
20
(0x014)
Error/3
SCSI command
abort on hard disk.
A SCSI command was
aborted.
Because the controller is
performing a recovery, there is no
problem as long as there are no
failed hard disks.
21
(0x015)
Warning/2
SCSI command
retried on hard
disk.
A SCSI command was
retried.
Because the controller is
performing a recovery, there is no
problem as long as there are no
failed hard disks.
23
(0x017)
Warning/2
Soft error found.
An error was detected on a
hard disk, but it was
resolved.
Because the controller is
performing a recovery, no action is
required. If this error occurs
frequently, see "6.2.3 Preventive
Replacement of hard disk [GAM]"
(Jpg.263) to replace the hard disk
as a precautionary measure.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
24
(0x018)
Warning/2
25
(0x019)
Description
Details
Corrective action
Misc error found.
An error was detected on a
hard disk, but it was
resolved.
Because the controller is
performing a recovery, no action is
required. If this error occurs
frequently, see "6.2.3 Preventive
Replacement of hard disk [GAM]"
(Jpg.263) to replace the hard disk
as a precautionary measure.
Info/1
SCSI device reset.
The firmware issued a
device reset.
None.
28
(0x01C)
Error/3
Request Sense
Data available.
A hard disk reported sense
information.
Because the controller is
performing a recovery, no action is
required as long as the
corresponding disk is Online.
29
(0x01D)
Info/1
Initialization
started.
A hard disk formatting has
started.
Wait until the format is completed.
30
(0x01E)
Info/1
Initialization
completed.
The hard disk format has
been completed.
None.
31
(0x01F)
Error/3
Initialization
failed.
The hard disk format failed.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk.
32
(0x020)
Error/3
Initialization
canceled.
The hard disk format was
canceled.
Format the hard disk again.
33 - 41
(0x021 0x029)
Error/3
A physical disk
failed because •••
A hard disk has failed.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
42
(0x02A)
Error/3
A physical disk set
to failed state by
host.
A Make Offline has been
executed by the controller.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
43 - 49
(0x02B 0x031)
Error/3
A physical disk
failed because •••
A hard disk has failed.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
50
(0x032)
Error/3
Physical disk
status changed to
offline.
A hard disk has become
offline.
None.
51
(0x033)
Info/1
Physical disk
status changed to
hot spare.
The hard disk has become
"Hot Spare".
None.
52
(0x034)
Error/3
Physical disk
status changed to
rebuild.
The hard disk has become
rebuild.
None.
53
(0x035)
Warning/2
Physical device ID
did not match.
The hard disk ID does not
match.
Check the logs surrounding the
process and perform necessary
actions.
54
(0x036)
Error/3
Physical disk
failed to start.
A hard disk failed to start.
Check that the hard disk is
connected properly. If the hard disk
has failed, see "6.2.2 Replacing
Failed Hard Disk [GAM]"
(Jpg.261) to replace the hard disk
and perform rebuild.
307
Appendix
table: List of GAM event logs
308
GAM ID
Severity
55
(0x037)
Warning/2
56
(0x038)
Description
Details
Corrective action
Physical disk
negotiated
different offset
than config.
A hard disk has negotiated
an offset different from
the configuration.
Check that the hard disk is
connected properly. If the hard disk
has failed, see "6.2.2 Replacing
Failed Hard Disk [GAM]"
(Jpg.261) to replace the hard disk
and perform rebuild.
Warning/2
Physical disk
negotiated
different bus width
than config.
A hard disk has negotiated
a bus width different from
the configuration.
Check that the hard disk is
connected properly. If the hard disk
has failed, see "6.2.2 Replacing
Failed Hard Disk [GAM]"
(Jpg.261) to replace the hard disk
and perform rebuild.
57
(0x039)
Error/3
Disk missing on
startup.
No hard disk was detected
during startup.
Check that the hard disk is
connected properly. If the hard disk
has failed, see "6.2.2 Replacing
Failed Hard Disk [GAM]"
(Jpg.261) to replace the hard disk
and perform rebuild.
58
(0x03A)
Error/3
Rebuild startup
failed due to lower
disk capacity.
Insufficient hard disk
space to perform the
rebuild.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk with a disk of
the same model (with the same
capacity and speed) as the other
disks, and then perform rebuild.
61
(0x03D)
Info/1
A standby rebuild
has started.
Standby rebuild started.
If the hard disk has failed, see
"6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.261) to replace the
hard disk and perform rebuild.
62
(0x03E)
Info/1
Hot spare replaced
with a smaller
capacity physical
disk.
A hot spare with a smaller
capacity was set.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk with a disk of
the same model (with the same
capacity and speed) as the other
disks, and then perform rebuild.
67
(0x043)
Error/3
Physical Disk
found on only one
disk channel.
A hard disk is connected
to only one disk channel.
Check that the hard disk is
connected properly. If the hard disk
has failed, see "6.2.2 Replacing
Failed Hard Disk [GAM]"
(Jpg.261) to replace the hard disk
and perform rebuild.
68
(0x044)
Info/1
Physical disk type
is not approved by
vendor.
An installed hard disk is
not vendor approved.
Use a vendor supported hard disk.
69
(0x045)
Error/3
Physical disk has
acquired an
inappropriate loop
ID. Enclosure
disk-slot
operations are
disabled while this
condition persists.
A hard disk has acquired
an inappropriate loop ID.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild. If this error recurs, contact
an office listed in the "Contact
Information" of "Start Guide".
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
70
(0x046)
Error/3
Physical disk port
has failed or
cannot operate at
the configured
channel speed.
• A hard disk has failed.
• The hard disk is not
compatible with the
system.
• The enclosure slot
hardware failed.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild. If this error recurs, contact
an office listed in the "Contact
Information" of "Start Guide".
71
(0x047)
Error/3
Mirror Race
recovery failed for
logical drive.
Mirror Race recovery
failed.
Perform Make Data Consistent
from GAM. For how to perform
Make Data Consistent, see "5.10.1
Make Data Consistent" (Jpg.239).
72
(0x048)
Error/3
Controller
parameters
checksum
verification failed restored default.
A mistake was found in
the checksum of the
controller parameters.
Check and correct the parameters
in the [Adapter Properties]
(Jpg.60) of WebBIOS. If the
message still appears, contact an
office listed in the "Contact
Information" of "Start Guide".
73
(0x049)
Info/1
Online controller
firmware upgrade
has started.
An online controller
firmware upgrade has
started.
None.
74
(0x04A)
Info/1
Online firmware
upgrade has
completed
successfully.
An online firmware
upgrade has been
completed successfully.
None.
75
(0x04B)
Error/3
Online firmware
upgrade has failed.
An online firmware
upgrade has failed.
Perform the online controller
firmware upgrade again. If the
message still appears, contact an
office listed in the "Contact
Information" of "Start Guide".
76
(0x04C)
Info/1
A Configuration
On Disk (COD)
with unsupported
features has been
detected.
The array configuration
information of the hard
disk contains features that
are not supported.
An array configuration
information created by
another system was
detected.
Connect a compatible hard disk.
77
(0x04D)
Info/1
New battery found.
A new battery was
detected.
None.
78
(0x04E)
Error/3
Battery backup
unit charger error.
The battery backup unit
charger has failed.
Replace the battery backup unit.
79
(0x04F)
Error/3
Battery will not
hold a charge.
A battery has failed.
Replace the battery backup unit.
80
(0x050)
Error/3
Firmware entered
unexpected state at
run-time.
The firmware entered
unexpected state at runtime.
Check the installation of the cache
memory or battery backup unit.
If the message still appears,
replace the cache memory or the
battery backup unit.
85
(0x055)
Info/1
Unable to recover
medium error
during patrol read.
Recovery of a medium
error failed during the
Patrol Read operation.
If a corrupted file is found, restore
it from the backup.
86
(0x056)
Info/1
Rebuild resumed.
Rebuild restarted.
None.
309
Appendix
table: List of GAM event logs
GAM ID
310
Severity
Description
Details
Corrective action
87
(0x057)
Info/1
Patrol Read
operation moved to
next available
target.
Patrol Read operation
started with the next
available hard disk.
None.
88
(0x058)
Info/1
Patrol Read
operation moved to
next available
channel.
Patrol Read operation
started with the next
available channel.
None.
89
(0x059)
Info/1
Physical disk
transfer speed
changed.
The transfer speed of the
hard disk has changed due
to an unknown error.
Check the previous logs and
perform necessary steps.
90
(0x05A)
Error/3
Channel is
suspended due to
some faults.
An abnormal state was
found in the channel.
Contact an office listed in the
"Contact Information" of "Start
Guide".
95
(0x05F)
Info/1
Configured
physical disk
replaced by user by
a smaller capacity
disk.
A hard disk has been
replaced with a smaller
capacity drive than
configured.
Reconnect a proper hard disk.
97
(0x061)
Info/1
PD Clear aborted.
PD Clear was aborted.
None.
98
(0x062)
Error/3
PD Clear failed.
PD Clear has failed.
Replace the hard disk.
99
(0x063)
Info/1
PD Clear started.
PD Clear was started.
None.
100
(0x064)
Info/1
PD Clear
completed.
PD Clear has been
completed.
None.
101
(0x065)
Error/3
Error.
An unknown error was
detected.
If the hard disk has failed, see
"6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.261) to replace the
hard disk and perform rebuild. If
the message still appears, contact
an office listed in the "Contact
Information" of "Start Guide".
102
(0x066)
Error/3
Hot Spare SMART
polling failed.
SMART polling of the Hot
Spare failed.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
Then configure the spare disk
referring to "2.4 Setting/Releasing
Spare Disk" (Jpg.84).
103
(0x067)
Info/1
Patrol Read
corrected medium
error.
A medium error was
corrected by Patrol Read.
None.
104
(0x068)
Error/3
Reassign write
operation failed.
A Reassign operation
failed.
If the hard disk has failed, see
"6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.261) to replace the
hard disk and perform rebuild.
105
(0x069)
Error/3
Unrecoverable
medium error
during rebuild.
An unrecoverable medium
error was detected during
rebuild process.
If a corrupted file is found, restore
it from the backup.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
106
(0x06A)
Info/1
Corrected medium
error during
recovery.
A medium error was
corrected.
None.
107
(0x06B)
Error/3
Unrecoverable
medium error
during recovery.
An unrecoverable medium
error was detected.
If a corrupted file is found, restore
it from the backup.
110
(0x06E)
Info/1
Dedicated Hot
Spare no longer
useful due to
deleted array.
No corresponding disk
group exists for the
dedicated spare disk.
The dedicated spare disk is not
supported. Reset the spare disk.
111
(0x06F)
Info/1
Dedicated Hot
Spare created.
A Dedicated spare disk
was created.
The dedicated spare disk is not
supported. Reset the spare disk.
112
(0x070)
Warning/2
Dedicated Hot
Spare disabled.
The Dedicated Hot Spare
was removed.
None.
113
(0x071)
Info/1
Dedicated Hot
Spare no longer
useful for all
arrays.
No corresponding disk
group exists for the
dedicated spare disk.
The dedicated spare disk is not
supported. Reset the spare disk.
114
(0x072)
Info/1
Global Hot Spare
created.
A Global Hot Spare was
created.
None.
115
(0x073)
Warning/2
Global Hot Spare
disabled.
The Global Hot Spare was
disabled.
None.
116
(0x074)
Info/1
Global Hot Spare
does not cover all
arrays.
The capacity of a spare
disk is insufficient, and
there is no array targeted
for Hot Spare rebuild.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk with a disk of
the same model (with the same
capacity and speed) as the other
disks, and then perform rebuild.
119
(0x077)
Warning/2
PD too small to be
used for autorebuild.
The rebuild could not be
started because the
capacity of the hard disk
is smaller then the other
hard disk.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk with a disk of
the same model (with the same
capacity and speed) as the other
disks, and then perform rebuild.
120
(0x078)
Warning/2
Bad block table on
PD is 80% full.
The Bad Block Table use
rate has exceeded 80%.
See "6.2.3 Preventive Replacement
of hard disk [GAM]" (Jpg.263)
and replace the hard disk as a
preventive measure.
121
(0x079)
Error/3
Bad block table on
PD is full; unable
to log blocks.
The Bad Block Table is
full.
See "6.2.3 Preventive Replacement
of hard disk [GAM]" (Jpg.263)
and replace the hard disk as a
preventive measure.
126
(0x07E)
Info/1
Firmware
corrected the
'Read' error.
The media error was
corrected.
None.
128
(0x080)
Info/1
Consistency check /
Make Data
Consistent is started.
Make Data Consistent has
started.
None.
129
(0x081)
Info/1
Consistency check
/ Make Data
Consistent is
finished.
Make Data Consistent has
been completed
successfully.
None.
311
Appendix
table: List of GAM event logs
GAM ID
312
Severity
Description
Details
Corrective action
130
(0x082)
Error/3
Consistency check
/ Make Data
Consistent is
cancelled.
Make Data Consistent was
canceled.
None.
132
(0x084)
Error/3
Consistency check
/ Make Data
Consistent on
logical drive
failed.
Make Data Consistent was
aborted, since the logical
drive had not been made
Online.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
Then, redo Make Data Consistent.
134
(0x086)
Error/3
Logical drive has
been made offline.
The logical drive has been
made Offline.
The logical drive(s) cannot
continue running in this state.
Recreate the array configuration
and restore the data from backup.
135
(0x087)
Error/3
Logical drive is
critical.
The logical drive is in
Critical state due to a hard
disk failure.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
136
(0x088)
Info/1
Logical drive has
been placed online.
The logical drive has been
placed online.
None.
137
(0x089)
Info/1
An automatic
rebuild has started
on logical drive.
Rebuild started
automatically.
None.
138
(0x08A)
Info/1
A manual rebuild
has started on
logical drive.
Rebuild started manually.
None.
139
(0x08B)
Info/1
Rebuild on logical
drive is over.
Rebuild has been
completed.
None.
140
(0x08C)
Error/3
Rebuild on logical
drive is cancelled.
Rebuild was canceled.
Perform the rebuild again.
141
(0x08D)
Error/3
Rebuild stopped
with error.
Rebuild terminated
abnormally.
Check the logs surrounding the
process and perform necessary
actions.
142
(0x08E)
Error/3
Rebuild stopped
with error. New
physical disk
failed.
Rebuild terminated
abnormally due to a
failure on the target hard
disk.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
143
(0x08F)
Error/3
Rebuild stopped
because logical
drive failed.
The source disk of the
rebuild failed.
Contact an office listed in the
"Contact Information" of "Start
Guide".
144
(0x090)
Info/1
Logical drive
initialization
started.
An initialization of a
logical drive has started.
None.
145
(0x091)
Info/1
Logical drive
initialization done.
The initialization of the
logical drive has been
completed.
None.
146
(0x092)
Error/3
Logical drive
initialization
cancelled.
The initialization of the
logical drive was
canceled.
Perform the initialization process
again.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
147
(0x093)
Error/3
Logical drive
initialization
failed.
The initialization
terminated abnormally.
The logical drive is now in
Offline state.
Backup all the data on the logical
drive and see "6.2.2 Replacing
Failed Hard Disk [GAM]"
(Jpg.261) to replace the hard disk.
Recreate the array configuration.
Then restore the data from backup.
148
(0x094)
Info/1
A logical drive has
been found.
A new logical drive has
been detected.
None.
149
(0x095)
Info/1
A logical drive has
been deleted.
A logical drive was
deleted.
None.
150
(0x096)
Info/1
Expand Capacity
Started.
A capacity expansion
process has started.
None.
151
(0x097)
Info/1
Expand Capacity
Completed.
The capacity expansion
has been completed.
None.
152
(0x098)
Error/3
Expand Capacity
stopped with error.
The capacity expansion
process terminated
abnormally due to failures
in multiple hard disks.
The logical drive(s) cannot
continue running in this state.
Recreate the array configuration
and restore the data from backup.
153
(0x099)
Error/3
Bad Blocks found.
A bad block was detected
during Make Data
Consistent, rebuild, or
capacity expansion
process.
• During Make Data Consistent/
capacity expansion: The bad
block will be repaired, so there
is no problem.
• During rebuild: If a corrupted
file is found, restore it from the
backup.
154
(0x09A)
Info/1
System drive size
changed.
The capacity of the logical
drive has changed.
None.
155
(0x09B)
Info/1
System drive type
changed.
• A new configuration
was added.
• The capacity expansion
has been completed.
None.
156
(0x09C)
Error/3
Bad data blocks
found. Possible
data loss.
Bad blocks were found on
multiple hard disks at the
same location.
If a corrupted file is found, restore
it from the backup.
157
(0x09D)
Info/1
Logical drive LUN
mapping has been
written to config.
Logical drive LUN
mapping has been written
to config.
None.
158
(0x09E)
Error/3
Attempt to read
data from block
that is marked in
Bad Data Table.
An attempt has been made
to read data logged in the
BDT table.
If a corrupted file is found, restore
it from the backup.
159
(0x09F)
Error/3
Data for Disk
Block has been lost
due to Logical
Drive problem.
Due to a problem with the
logical drive, cache data
could not be written to the
hard disk.
Check the logs surrounding the
process and perform necessary
actions.
162
(0x0A2)
Info/1
A standby rebuild
has started on a
logical drive.
Standby rebuild started.
If the hard disk has failed, see
"6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.261) to replace the
hard disk and perform rebuild.
313
Appendix
table: List of GAM event logs
GAM ID
314
Severity
Description
Details
Corrective action
163
(0x0A3)
Error/3
Reconstruct
detected
uncorrectable
double medium
errors.
Due to media errors
detected in the same
position on multiple hard
disks, data cannot be
recovered.
If a corrupted file is found, restore
it from the backup.
164
(0x0A4)
Info/1
Reconstruction
resumed.
Reconstruction was
resumed.
None.
165
(0x0A5)
Error/3
Reconstruction
resume failed due
to configuration
mismatch.
Reconstruction resume
terminated abnormally
due to configuration
mismatch.
Recreate the array and restore the
backup data.
166
(0x0A6)
Info/1
LD Properties
updated.
A parameter has changed
on the logical drive.
None.
167
(0x0A7)
Error/3
Marking LD
inconsistent due to
active writes at
shutdown.
The consistency of the
logical drive was lost due
to shutdown during the
writing process.
Perform Make Data Consistent
from GAM. For how to perform
Make Data Consistent, see "5.10.1
Make Data Consistent" (Jpg.239).
176
(0x0B0)
Info/1
Logical drive
background
initialization
started.
BGI started.
None.
177
(0x0B1)
Info/1
Logical drive
background
initialization
stopped.
BGI stopped by the user or
the firmware.
None.
178
(0x0B2)
Info/1
Logical drive
background
initialization
paused.
BGI was paused for
operations with higher
priority.
None.
179
(0x0B3)
Info/1
Logical drive
background
initialization
restarted.
BGI resumed after a
pause.
None.
180
(0x0B4)
Error/3
Logical drive
background
initialization
failed.
BGI terminated
abnormally.
Check the logs surrounding the
process and perform necessary
actions.
181
(0x0B5)
Info/1
Logical drive
background
initialization
completed.
BGI has been completed.
None.
182
(0x0B6)
Error/3
Low battery charge
level. Logical
drive may have
lost data.
Data may be lost because
the power has been off for
a long time with data
maintained in the cache
memory.
Perform Make Data Consistent
(Jpg.239) from GAM. If necessary,
restore the data from the backup after
reconfiguring the array.
185
(0x0B9)
Info/1
Unable to recover
medium error
during background
initialization.
Unrecoverable medium
error detected during
background initialization.
If a corrupted file is found, restore
it from the backup.
256
(0x100)
Error/3
Fan failure.
A fan failure was detected.
Check the fan with ServerView,
and take the necessary measures.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
257
(0x101)
Info/1
Fan has been
restored.
The fan was restored.
None.
258
(0x102)
Error/3
Fan failure.
A fan failure was detected.
Check the fan with ServerView,
and take the necessary measures.
259
(0x103)
Info/1
Storage cabinet fan
is not present.
No fan was detected.
None.
272
(0x110)
Error/3
Power supply
failure.
The power supply has
failed.
Check the power supply status
with ServerView, and take the
necessary measures.
273
(0x111)
Info/1
Power supply has
been restored.
The PSU was restored.
None.
274
(0x112)
Error/3
Power supply
failure.
The power supply has
failed.
Check the power supply status
with ServerView, and take the
necessary measures.
275
(0x113)
Info/1
Storage cabinet
power supply is
not present.
No power supply was
detected.
None.
288
(0x120)
Error/3
Over temperature.
Temperature is
above 70 degrees
Celsius.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
289
(0x121)
Warning/2
Temperature is
above 50 degrees
Celsius.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
290
(0x122)
Info/1
Normal
temperature has
been restored.
The temperature is now
normal.
None.
291
(0x123)
Error/3
Over temperature.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
292
(0x124)
Info/1
Storage cabinet
temperature sensor
is not present.
No temperature sensor
was detected.
None.
320
(0x140)
Error/3
Fan failure.
A fan failure was detected.
Check the fan with ServerView,
and take the necessary measures.
321
(0x141)
Info/1
Fan has been
restored.
The fan was restored.
None.
322
(0x142)
Info/1
Fan is not present.
No fan was detected.
None.
323
(0x143)
Error/3
Power supply
failure.
The power supply has
failed.
Check the power supply status
with ServerView, and take the
necessary measures.
324
(0x144)
Info/1
Power supply has
been restored.
The PSU was restored.
None.
315
Appendix
table: List of GAM event logs
GAM ID
316
Severity
Description
Details
Corrective action
325
(0x145)
Info/1
Power supply is
not present.
No power supply was
detected.
None.
326
(0x146)
Error/3
Temperature is
over safe limit.
Failure imminent.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
327
(0x147)
Error/3
Temperature is
above working
limit.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
328
(0x148)
Info/1
Normal
temperature has
been restored.
The temperature is now
normal.
None.
329
(0x149)
Info/1
Temperature
sensor is not
present.
No temperature sensor
was detected.
None.
330
(0x14A)
Error/3
Enclosure access
critical.
An error occurred in the
access to the enclosure.
Contact an office listed in the
"Contact Information" of "Start
Guide".
331
(0x14B)
Info/1
Enclosure access
has been restored.
Enclosure access was
restored.
None.
332
(0x14C)
Error/3
Enclosure access is
offline.
An error occurred in the
access to the enclosure.
Contact an office listed in the
"Contact Information" of "Start
Guide".
334
(0x14E)
Info/1
Enclosure services
ready.
Enclosure is ready for
service.
None.
335
(0x14F)
Info/1
Access to
temperature sensor
has been lost.
Access to the temperature
sensor was lost.
None.
336
(0x150)
Info/1
Access to power
supply status
information has
been lost.
Access to the power
supply status information
was lost.
None.
337
(0x151)
Info/1
Access to fan
status information
has been lost.
Access to the fan status
information was lost.
None.
338
(0x152)
Error/3
Physical disks in
enclosure being
spundown.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
339
(0x153)
Error/3
Temperature is
below working
limit.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
340
(0x154)
Error/3
Temperature is
under safe limit.
Failure imminent.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature.
346
(0x15A)
Error/3
Enclosure not
supported; too
many enclosures
connected to port.
• Enclosure is not
supported.
• Too many Enclosures
are connected to the
port.
Check the condition of the system
connections.
347
(0x15B)
Error/3
Enclosure
firmware
mismatch.
The enclosure firmware
does not match.
Contact an office listed in the
"Contact Information" of "Start
Guide".
348
(0x15C)
Error/3
Sensor bad.
The sensor is abnormal.
Contact an office listed in the
"Contact Information" of "Start
Guide".
349
(0x15D)
Error/3
Enclosure phy bad.
The Enclosure PHY is
abnormal.
Contact an office listed in the
"Contact Information" of "Start
Guide".
350
(0x15E)
Error/3
SAS/SATA mixing
not supported in
enclosure; PD
disabled.
The hard disk cannot be
used, because SAS and
SATA devices are mixed.
Check if any unsupported hard
disks are installed. If there is an
unsupported hard disk installed,
replace it with a supported one.
351
(0x15F)
Warning/2
Enclosure (SES)
hotplug on was
detected, but is not
supported.
An Enclosure hotplug was
detected, but is not
supported.
None.
352
(0x160)
Info/1
Enclosure power
supply has been
turned off.
The enclosure power
supply was turned off.
None.
353
(0x161)
Info/1
Enclosure power
supply has been
turned on.
The enclosure power
supply was turned on.
None.
354
(0x162)
Info/1
Enclosure power
supply cable has
been removed.
The enclosure power
supply cable was
removed.
Insert the power supply cable.
355
(0x163)
Info/1
Enclosure power
supply cable has
been inserted.
The enclosure power
supply cable was inserted.
None.
356
(0x164)
Info/1
Enclosure fan
returned to normal.
The enclosure fan returned
to normal.
None.
357
(0x165)
Info/1
Enclosure
temperature
difference has been
detected.
An enclosure temperature
difference was detected.
None.
384
(0x180)
Info/1
Array management
server software
started
successfully.
GAM Server started
successfully.
None.
385
(0x181)
Error/3
Write back error
Failed to write cache.
Check the logs surrounding the
process and perform necessary
actions.
317
Appendix
table: List of GAM event logs
318
GAM ID
Severity
Description
Details
Corrective action
386
(0x182)
Warning/2
Internal log
structures getting
full, PLEASE
SHUTDOWN
AND RESET THE
SYSTEM IN THE
NEAR FUTURE.
Due to many
configuration changes, the
configuration change table
is full.
Shut down the system properly,
power off the server and turn it
back on.
If the same log still appears,
contact an office listed in the
"Contact Information" of "Start
Guide".
388
(0x184)
Error/3
Controller is dead.
System is
disconnecting from
this controller.
The SCSI array controller
failed.
Contact an office listed in the
"Contact Information" of "Start
Guide".
389
(0x185)
Info/1
Controller has
been reset.
The controller received a
reset command.
Because the firmware is
performing a recovery, there is no
problem as long as there are no
failed hard disks.
390
(0x186)
Info/1
Controller is
found.
A controller was detected.
None.
391
(0x187)
Error/3
Controller is gone.
System is
disconnecting from
this controller.
• The power to the
controller was cut off.
• The controller was
removed from the
system.
Contact an office listed in the
"Contact Information" of "Start
Guide".
392
(0x188)
Info/1
Battery present.
A battery backup unit was
detected.
None.
393
(0x189)
Error/3
Battery is bad.
The battery backup unit
has failed.
Replace the battery backup unit.
394
(0x18A)
Info/1
Battery power OK.
The battery is fully
charged. (The charge level
is above the set threshold.)
None.
395
(0x18B)
Error/3
Controller is gone.
System is
disconnecting from
this controller.
• The power to the
controller was cut off.
• The controller was
removed from the
system.
Contact an office listed in the
"Contact Information" of "Start
Guide".
396
(0x18C)
Info/1
Controller
powered on.
A new controller was
installed.
None.
397
(0x18D)
Info/1
Controller is
online.
A controller came online.
None.
398
(0x18E)
Error/3
Controller is gone.
System is
disconnecting from
this controller.
• The power to the
controller was cut off.
• The controller was
removed from the
system.
Contact an office listed in the
"Contact Information" of "Start
Guide".
399
(0x18F)
Warning/2
Controller's
partner is gone,
controller is in
failover mode now.
The controller went
Offline.
None.
400
(0x190)
Info/1
Battery
reconditioning is
started.
Recalibration of the
battery was started.
None.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
401
(0x191)
Info/1
Battery
reconditioning is
finished.
Recalibration of the
battery has been
completed.
None.
402
(0x192)
Info/1
Battery
reconditioning is
canceled.
Recalibration of the
battery was canceled.
Perform the battery recalibration
again.
403
(0x193)
Error/3
Installation
aborted.
The configuration
changed while the system
was offline.
Shut down the server and check the
hard disk connections. Check that
the appropriate hard disks are
installed, and remove any
inappropriate hard disks.
(For example, a hard disk for
another system may have been
installed by mistake.)
If this does not resolve the
problem, reconfigure the array and
restore the backup data.
404
(0x194)
Error/3
Controller firmware
mismatch.
The controller firmware
has been replaced with an
old version.
Contact an office listed in the
"Contact Information" of "Start
Guide".
405
(0x195)
Error/3
The Battery
Backup Unit is
removed.
The battery backup unit
was removed.
Extremely low voltage of a battery
after battery replacement may
result in this event. If ID: 392
(0x188) "Battery present." is
recorded, there is no problem.
Follow "Appendix C Replacing
Battery" (Jpg.327). If ID: 392
(0x188) "Battery present." is not
recorded, check if a BBU is
correctly installed.
406
(0x196)
Error/3
WARM BOOT
failed.
A memory error was
detected during the boot
process.
Replace the cache memory or the
battery backup unit.
407
(0x197)
Info/1
Battery calibration
cycle started.
Recalibration of the
battery was started.
None.
408
(0x198)
Info/1
Battery calibration
cycle finished.
Recalibration of the
battery has been
completed.
None.
409
(0x199)
Info/1
Battery calibration
cycle was
cancelled.
Recalibration of the
battery was canceled.
Perform the battery recalibration
again.
410
(0x19A)
Error/3
Battery is not
present.
No battery was detected.
If a battery backup unit is used,
check its connection. If this error
recurs, replace the battery backup
unit.
411
(0x19B)
Info/1
Controller entered
conservative cache
mode.
The SCSI array controller
entered Conservative
Cache Mode.
None.
412
(0x19C)
Info/1
Controller entered
normal cache
mode.
The SCSI array controller
entered Normal Cache
Mode.
None.
319
Appendix
table: List of GAM event logs
GAM ID
320
Severity
Description
Details
Corrective action
413
(0x19D)
Info/1
Controller device
start complete.
The controller device
started.
None.
414
(0x19E)
Error/3
Soft ECC error
corrected.
An ECC error was
detected in the memory.
Replace the memory module or the
battery backup unit.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
415
(0x19F)
Error/3
Hard ECC error
corrected.
An ECC error was
detected in the memory.
Replace the memory module or the
battery backup unit.
If this error recurs, contact an
office listed in the "Contact
Information" of "Start Guide".
416
(0x1A0)
Info/1
Battery recondition
suggested.
Recalibration of the
battery is recommended.
Perform the battery recalibration.
418
(0x1A2)
Error/3
BBU out of
service.
The battery cannot supply
power to the cache
memory.
Replace the battery backup unit.
425
(0x1A9)
Error/3
Controller boot
ROM image needs
to be reloaded.
An inappropriate firmware
image was loaded.
Contact an office listed in the
"Contact Information" of "Start
Guide".
426
(0x1AA)
Error/3
Controller is using
default non-unique
world-wide name.
The controller's MAC
address was lost, or not
set.
Contact an office listed in the
"Contact Information" of "Start
Guide".
427
(0x1AB)
Error/3
Mirror Race
recovery failed.
Mirror Race recovery
failed.
Perform Make Data Consistent
from GAM. For how to perform
Make Data Consistent, see "5.10.1
Make Data Consistent" (Jpg.239).
428
(0x1AC)
Error/3
Mirror Race on
critical drive.
The hard disk has a
failure.
See "6.2.2 Replacing Failed Hard
Disk [GAM]" (Jpg.261) to
replace the hard disk and perform
rebuild.
431
(0x1AF)
Error/3
Controller
improperly
shutdown! Data
may have been
lost.
The consistency of the
logical drive was lost due
to an invalid shutdown
process.
Perform Make Data Consistent
from GAM. For how to perform
Make Data Consistent, see "5.10.1
Make Data Consistent" (Jpg.239).
440
(0x1B8)
Error/3
Error in Mirror
Race Table.
An error occurred in the
Mirror Race Table.
Check the array configuration. If
the array configuration is correct,
perform Make Data Consistent. If
the array configuration is invalid,
reconfigure the array and restore
the data from the backup.
442
(0x1BA)
Info/1
Patrol Read
iteration
completed.
Patrol Read has been
completed.
None.
443
(0x1BB)
Info/1
Controller entered
'Write Through'
cache mode.
The controller entered
'Write Through' cache
mode.
None.
444
(0x1BC)
Info/1
Controller entered
'Write Back' cache
mode.
The controller entered
'Write Back' cache mode.
None.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
446
(0x1BE)
Info/1
Data in Cache
flushed during
power up.
Data in the cache memory
was flushed at the time of
system boot.
None.
447
(0x1BF)
Error/3
Data in Cache not
flushed during
power up.
Data in the cache memory
failed to flush at the time
of system boot due to an
abnormal configuration.
Check the array configuration. If
the array configuration is correct,
perform Make Data Consistent. If
the array configuration is invalid,
reconfigure the array and restore
the data from the backup.
448
(0x1C0)
Info/1
Consistency Check
rate changed.
The rate of Make Data
Consistent has been
changed.
None.
449
(0x1C1)
Info/1
Background
initialization rate
changed.
The background
initialization rate has been
changed.
None.
450
(0x1C2)
Info/1
Flush rate
changed.
The flush rate has been
changed.
None.
451
(0x1C3)
Info/1
Patrol Read Rate
changed.
The Patrol Read Rate has
been changed.
None.
452
(0x1C4)
Info/1
Rebuild rate
changed.
The rebuild rate has been
changed.
None.
453
(0x1C5)
Info/1
Reconstruction
rate changed.
The reconstruction rate
has been changed.
None.
455
(0x1C7)
Info/1
Alarm disabled by
user.
The user disabled the
alarm.
None.
456
(0x1C8)
Info/1
Alarm enabled by
user.
The user enabled the
alarm.
None.
457
(0x1C9)
Error/3
Unable to recover
cache data due to
configuration
mismatch.
The cache data cannot be
recovered due to a
configuration mismatch.
If the array configuration is
correct, perform Make Data
Consistent (Jpg.239). If the array
configuration is invalid,
reconfigure the array and restore
the data from the backup.
458
(0x1CA)
Info/1
Cache data
recovered
successfully.
The cache data was
recovered successfully.
None.
460
(0x1CC)
Info/1
Factory defaults
restored.
A factory default was
restored.
Reconfigure the controller if
necessary.
461
(0x1CD)
Info/1
Hibernate
command received
from host.
A hibernate command was
received from the host.
None.
462
(0x1CE)
Info/1
Event log cleared.
The NVRAM log was
cleared.
None.
463
(0x1CF)
Info/1
Event log
wrapped.
The NVRAM log was
wrapped.
None.
464
(0x1D0)
Error/3
Not enough
controller memory.
Insufficient controller
memory was detected.
Replace the cache memory or the
battery backup unit.
465
(0x1D1)
Info/1
Patrol Read
paused.
Patrol Read operation was
temporarily paused.
None.
321
Appendix
table: List of GAM event logs
GAM ID
322
Severity
Description
Details
Corrective action
466
(0x1D2)
Info/1
Patrol Read
resumed.
Patrol Read operation was
resumed.
None.
467
(0x1D3)
Info/1
Patrol Read
started.
Patrol Read operation was
started.
None.
468
(0x1D4)
Info/1
Shutdown
command received
from host.
A shutdown command
was received from the
host.
None.
469
(0x1D5)
Info/1
User entered
firmware
debugger.
The user entered firmware
debug mode.
None.
470
(0x1D6)
Error/3
Battery
temperature is
high.
Abnormal temperature
was detected.
Check the fan status with
ServerView. In the event of a fan
failure, take the necessary
measures. If there is no fan failure,
adjust the ambient temperature. If
this error recurs, replace the
battery backup unit.
471
(0x1D7)
Info/1
Battery is
charging.
The battery is charging.
None.
472
(0x1D8)
Info/1
Battery is
discharging.
The battery is discharging.
None.
473
(0x1D9)
Error/3
Battery needs to be
replaced.
Replacement of the
battery is required.
The event occurs right after the
battery backup unit replacement.
Due to the insufficiently charged
battery after the replacement, this
event may occur. Follow
"Appendix C Replacing Battery"
(Jpg.327)
The event occurs during regular
operation.
Replace the battery backup unit.
474
(0x1DA)
Error/3
Battery relearn
timed out.
The battery recalibration
was timed out.
Perform the battery recalibration
again. If this error recurs, replace
the battery backup unit.
475
(0x1DB)
Info/1
Battery relearn
pending: Battery is
under charge.
The recalibration of the
battery is pending because
the battery is being
charged.
None.
478
(0x1DE)
Info/1
BBU enabled;
changing WT
logical drives to
WB.
The battery backup unit
became enabled and the
logical drive was changed
from Write Through mode
to Write Back mode.
None.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
479
(0x1DF)
Warning/2
BBU disabled;
changing WB
logical drives to
WT.
The battery backup unit
became disabled and the
logical drive was changed
from Write Back mode to
Write Through mode.
The event occurs at the system
start right after the battery backup
unit replacement.
Due to the insufficiently charged
battery after the replacement, this
event may occur. Follow
"Appendix C Replacing Battery"
(Jpg.327).
The event occurs at the system
start during regular operation.
Turn on the server for 12 hours or
more after the event occurs to
charge the battery. Replace the
battery backup unit if
ID:478(0x1DE) does not occur
after 12 hours.
The event occurs during regular
operation.
There is no problem if it occurs
during battery recalibration
(including the scheduled one). If
not, replace the battery backup
unit.
480
(0x1E0)
Info/1
Battery charge
complete
The battery charge has
been completed.
None.
481
(0x1E1)
Info/1
Battery Relearn
request received.
A request to recalibration
the battery was received.
Perform recalibration for a battery
backup unit.
482
(0x1E2)
Info/1
Controller Cache
discarded by user.
The user discarded the
Controller Cache.
None.
483
(0x1E3)
Info/1
Previous
configuration is
completely
missing at boot.
The array configuration
was missing at boot time.
• Shut down the system and check
the connection to the hard disk.
• Check that the cabinet is
properly connected.
• Check the state of the power
supply.
512
(0x200)
Info/1
System started.-
The server or GAM Server
started.
None.
514
(0x202)
Info/1
User logged in.-
The user logged in to the
server.
None.
515
(0x203)
Info/1
User logged out.-
The user logged out from
the server.
None.
516
(0x204)
Info/1
Server alive.
• Reconnected to the
server.
• The server rebooted.
None.
517
(0x205)
Error/3
Lost connection to
server, or server is
down.
• The network
connection to the server
was lost.
• The server shut down.
Check the network. Check that
GAM Server was properly
executed. Check that the server is
running.
518
(0x206)
Info/1
Automatic reboot
count has changed.
Automatic reboot count
has changed.
None.
519
(0x207)
Info/1
Battery test has
started.
A battery test started.
None.
323
Appendix
table: List of GAM event logs
GAM ID
324
Severity
Description
Details
Corrective action
520
(0x208)
Info/1
Battery test
complete.
The battery test has been
completed.
None.
521
(0x209)
Info/1
Battery test
canceled.
The battery test was
canceled.
None.
522
(0x20A)
Error/3
Battery test failed battery bad.
Errors were detected
during the battery test.
Replace the battery backup unit.
700
(0x2BC)
Info/1
Event log empty.
The content of the event
log has become blank.
None.
701
(0x2BD)
Info/1
Event log entries
lost.
Event Log entries were
lost.
None.
702
(0x2BE)
Info/1
Request Sense.
Sense Information was
reported.
Because the firmware is
performing a recovery, there is no
problem as long as there are no
failed hard disks.
703
(0x2BF)
Info/1
Set real time clock.
The clock was set.
None.
800
(0x320)
Info/1
New Configuration
Received.
A new array configuration
was issued.
None.
801
(0x321)
Info/1
Configuration
Cleared.
The array configuration
was cleared.
None.
802
(0x322)
Warning/2
Configuration
Invalid.
The array configuration
information is invalid.
Check that the hard disk is
connected properly. If this does not
resolve the problem, recreate the
array and recover the backup data.
803
(0x323)
Warning/2
Configuration On
Disk Access Error.
The array configuration
information could not be
read from the hard disk.
Check the array configuration. If
there is a failed hard disk, see
"6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.261) to replace it
and perform rebuild.
If the array configuration is
invalid, reconfigure the array and
restore the data from the backup.
804
(0x324)
Warning/2
Configuration on
disk converted.
The array configuration
information on the hard
disk was converted.
None.
805
(0x325)
Warning/2
Configuration On
Disk Import
Failed.
The array configuration
information could not be
imported.
Shut down the server and check the
hard disk connections. Check that
the appropriate hard disks are
installed, and remove any
inappropriate hard disks. (For
example, a hard disk for another
system may have been installed by
mistake.) If this does not resolve
the problem, reconfigure the array
and restore the backup data.
806
(0x326)
Info/1
A debug dump
exists on this
system.
A debug dump exists on
this system.
None.
807
(0x327)
Info/1
A debug dump
exists on this
system.
A debug dump exists on
this system.
None.
MegaRAID SAS User's Guide
table: List of GAM event logs
GAM ID
Severity
Description
Details
Corrective action
808
(0x328)
Info/1
No valid
Configuration On
Disk (COD) found.
No valid Configuration
On Disk (COD) found.
Check if the hard disk connected
was previously used in another
system. If a hard disk that was
previously used in another system
is connected, that hard disk must
be formatted completely before
use.
810
(0x32A)
Info/1
MegaRAID
firmware
initialization started.
The initialization of the
MegaRAID firmware
started.
None.
811
(0x32B)
Error/3
Unable to recover
cache data from
TBBU.
Cache data cannot be
recovered from the battery
backup unit.
Shut down the system properly,
and then restart the system.
812
(0x32C)
Info/1
Cache data
recovered from
TBBU
successfully.
Data was successfully
written to the cache
memory.
None.
960
(0x3C0)
Error/3
SAS topology
error: Loop
detected.
Loop detected in the SAS
topology.
Check the condition of the system
connections. If this error recurs,
even though the connections are
correct, contact an office listed in
the "Contact Information" of "Start
Guide".
961
(0x3C1)
Error/3
SAS topology
error:
Unaddressable
device.
Device is unaddressable in
the SAS topology.
Check the condition of the system
connections. If the system
connections are correct but there is
a failed hard disk, see
"6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.261)
to replace the hard disk and
perform rebuild. If this error
recurs, contact an office listed in
the "Contact Information" of "Start
Guide".
962
(0x3C2)
Error/3
SAS topology
error: Multiple
ports to the same
SAS address.
Multiple ports were
connected to the same
SAS address in the SAS
topology.
Check the condition of the system
connections. If this error recurs,
even though the connections are
correct, contact an office listed in
the "Contact Information" of "Start
Guide".
963
(0x3C3)
Error/3
SAS topology
error: Expander
error.
An error was detected in
the Expander.
Contact an office listed in the
"Contact Information" of "Start
Guide".
964
(0x3C4)
Error/3
SAS topology
error: SMP
timeout.
SMP timeout was
detected.
Contact an office listed in the
"Contact Information" of "Start
Guide".
965
(0x3C5)
Error/3
SAS topology
error: Out of route
entries.
Route entries cannot be
found.
Contact an office listed in the
"Contact Information" of "Start
Guide".
966
(0x3C6)
Error/3
SAS topology
error: Index not
found.
Index was not found.
Contact an office listed in the
"Contact Information" of "Start
Guide".
325
Appendix
table: List of GAM event logs
GAM ID
326
Severity
Description
Details
Corrective action
967
(0x3C7)
Error/3
SAS topology
error: SMP
function failed.
An error was detected in
an SMP function.
Contact an office listed in the
"Contact Information" of "Start
Guide".
968
(0x3C8)
Error/3
SAS topology
error: SMP CRC
error.
A CRC error was detected
in SMP.
Contact an office listed in the
"Contact Information" of "Start
Guide".
969
(0x3C9)
Error/3
SAS topology
error: Multiple
subtractive.
An error was detected in
the SAS topology.
Contact an office listed in the
"Contact Information" of "Start
Guide".
970
(0x3CA)
Error/3
SAS topology
error: Table to
table.
An error was detected in
the SAS topology.
Contact an office listed in the
"Contact Information" of "Start
Guide".
971
(0x3CB)
Error/3
SAS topology
error: Multiple
paths.
Multiple paths exist.
Check the condition of the system
connections. If this error recurs,
even though the connections are
correct, contact an office listed in
the "Contact Information" of "Start
Guide".
MegaRAID SAS User's Guide
C
Replacing Battery
The battery for the cache memory is mounted in models that come with a battery
backup unit. The battery is a consumable part and its capacity decreases over time.
Replace the battery periodically.
The length of the data holding time will decrease gradually over the life of the battery. The speed of this
decrease depends on the environment, especially on high temperatures. As an example, if the
temperature surrounding the server is 25 degrees Celsius, change the battery after two to three years of
the purchase. In a worst-case scenario, if you continue to use the battery at an extremely low capacity,
the battery fluid may leak.
Regarding battery replacement, there are cases when you need to buy a new server or replace a server, or
when you need to contact an office listed in the "Contact Information" of "Start Guide". For the details,
see "User’s Guide" located on "PRIMERGY Startup Disc supplied with the server.
For how to physically replace a battery, see "User’s Guide" located on "PRIMERGY Startup Disc
supplied with the server, or the manual come with a battery backup unit.
Check if the event that detected the following battery is recorded.
• When using ServerView RAID
• Events via ServerView
Source
:
Type
:
Event ID
:
Description:
(Server %s)
Fujitsu ServerView Services
Information
1
<Type and number of controller>: BBU present
• Source: ServerView RAID events, or ServerView RAID Manager event window.
Source
:ServerView RAID
ID
: 10298
Description: <Type and number of controller>: BBU present
• When using GAM
Source
:
Type
:
Event ID
:
Description:
Fujitsu ServerView Services
Information
1
Battery present
When the voltage of the replaced battery is extremely low, both messages shown above and below
appear at a time resulting in no batteries detected. By charging the battery more than 60 minutes, a
battery will be normally detected from the next restart.
327
Appendix
• When using ServerView RAID
• Events via ServerView
Source
:
Type
:
Event ID
:
Description:
(Server %s)
Fujitsu ServerView Services
error
3
<Type and number of controller>: BBU removed
• Source: ServerView RAID events, or ServerView RAID Manager event window.
Source
:ServerView RAID
ID
: 10314
Description: <Type and number of controller>: BBU removed
• When using GAM
Source
:
Type
:
Event ID
:
Description:
Fujitsu ServerView Services
Information
3
The Battery Backup Unit is removed.
` The battery is recyclable. At the end of it's useful life, under various states and local laws, it may be
illegal to dispose of this battery into the municipal waste stream. Check with your local solid waste
officials for details in your area for recycling options or proper disposal.
328
MegaRAID SAS User's Guide
Index
A
Actions Menu . . . . . . . . . . . . . . . . . . . . . . 131
Add Logical drive . . . . . . . . . . . . . . . . . . . 213
Administration Menu . . . . . . . . . . . . . . . . . 202
Administrator Privileges . . . . . . . . . . . . . . 110
Array Controller
Detailed information (GAM) . . . . . . . . . 230
Detailed information (ServerView RAID)165
Detailed information (WebBIOS) . . . . . . 60
Hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . 106
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Property . . . . . . . . . . . . . . . . . . . . . . . . 61
Setting and changing. . . . . . . . . . . . . . 139
Specifications . . . . . . . . . . . . . . . . . . . . 16
Updating the Device Drivers . . . . . . . . 102
Work Flow . . . . . . . . . . . . . . . . . . . . . . . 14
Array controller
Controller icons . . . . . . . . . . . . . . . . . . 200
Controller Options . . . . . . . . . . . . . . . . 208
Setting and Changing Options. . . . . . . 208
B
Background Initialization
Checking the Progress (ServerView RAID)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Checking the Progress (WebBIOS) . . . . 58
Background initialization . . . . . . . . . . . . . . . 29
Checking the progress (GAM) . . . . . . . 236
Background Task . . . . . . . . . . . . . . . . . . . 171
Background task . . . . . . . . . . . . . . . . . 58, 236
Bad BBU. . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Battery Backup Unit . . . . . . . . . . . . . . . . . . 36
Battery backup unit . . . . . . . . . . . . . . . . . . 135
Battery recalibration scheduler
Installation. . . . . . . . . . . . . . . . . . . . . . 121
Uninstallation. . . . . . . . . . . . . . . . . . . . 124
BBU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
C
Capacity Expansion . . . . . . . . . . . . . 153, 219
Checking the Progress(GAM) . . . . . . . 237
Checking the Progress(WebBIOS) . . . . 58
Capacity expansion. . . . . . . . . . . . . . . . 33, 89
Checking progress(ServerView RAID). 171
Checking Availability of Redundancy . . . . 263
Checking availability of redundancy . . . . . 250
Consistency check . . . . . . . . . . . . . . . . . . 161
Viewing progress (ServerView RAID) . 171
Controller icon . . . . . . . . . . . . . . . . . .135, 200
Controller Options. . . . . . . . . . . . . . . . . . . .208
Controller Selection Box . . . . . . . . . . . . . . .199
Controller View . . . . . . . . . . . . . . . . . . . . . .204
Administration Menu . . . . . . . . . . . . . . .202
File Menu . . . . . . . . . . . . . . . . . . . . . . .201
View Menu . . . . . . . . . . . . . . . . . . . . . .201
Viewing Hard Disk Information . . . . . . .231
Viewing Logical Drive Information . . . . .234
D
Device Drivers
Creating Driver Disks . . . . . . . . . . . . . .102
Updating the Drivers (Windows Server 2003)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Updating the Drivers (Windows 2000 Server)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Disk Array
Disk Groups . . . . . . . . . . . . . . . . . . . . . .23
Disk array . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Add Logical Drive . . . . . . . . . . . . . . . . .217
Creating configuration (GAM) . . . . . . . .214
Creating configuration (WebBIOS) . . . . .63
Creating configuration (ServerView RAID)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Deleting configuration (GAM) . . . . . . . .227
Deleting configuration (ServerView RAID)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Deleting configuration (WebBIOS) . . . . .82
RAID Assist. . . . . . . . . . . . . . . . . . . . . .212
Saving Configuration. . . . . . . . . . . . . . .226
Disk Group . . . . . . . . . . . . . . . . . . . . . . . . . .23
Logical drive . . . . . . . . . . . . . . . . . . . . . .23
Disk Groups
Capacity Expansion . . . . . . . . . . . . . . . .33
Configuration example . . . . . . . . . . . . . .24
E
Edit Configuration . . . . . . . . . . . .213, 222, 223
Event Window . . . . . . . . . . . . . . . . . . . . . .131
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
GAM . . . . . . . . . . . . . . . . . . . . . . . . . . .304
ServerView RAID . . . . . . . . . . . . . . . . .270
Expand Array . . . . . . . . . . . . . . . . . . .214, 219
Expand Capacity Status . . . . . . . . . . . . . . .237
F
Fast Initialization . . . . . . . . . . . . . . . . . . . . . .30
329
Checking the Progress . . . . . . . . . . . . . . 58
File Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
File Menu. . . . . . . . . . . . . . . . . . . . . . 131, 201
Foreground Initialization. . . . . . . . . . . . . . . . 28
G
GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Access privileges . . . . . . . . . . . . . . . . . 178
Events . . . . . . . . . . . . . . . . . . . . . . . . . 304
Exiting . . . . . . . . . . . . . . . . . . . . . . . . . 197
Installation . . . . . . . . . . . . . . . . . . . . . . 183
Log On . . . . . . . . . . . . . . . . . . . . . . . . . 196
Maintenance Functions . . . . . . . . . . . . 239
RAID Assist function. . . . . . . . . . . . . . . 212
Requirements. . . . . . . . . . . . . . . . . . . . 177
Setting/Releasing Spare Disk . . . . . . . . 223
Starting. . . . . . . . . . . . . . . . . . . . . . . . . 196
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . 203
Uninstallation . . . . . . . . . . . . . . . . . . . . 186
Window Layout. . . . . . . . . . . . . . . . . . . 198
GAM Client . . . . . . . . . . . . . . . . . . . . . . . . 176
Installation . . . . . . . . . . . . . . . . . . . . . . 183
Server group and server settings . . . . . 207
Uninstallation . . . . . . . . . . . . . . . . . . . . 186
GAM Server . . . . . . . . . . . . . . . . . . . . . . . . 176
Installation . . . . . . . . . . . . . . . . . . . . . . 183
Uninstallation . . . . . . . . . . . . . . . . . . . . 187
Global Array Manager . . . . . . . . . . . . . . . . 176
Global Status View. . . . . . . . . . . . . . . . . . . 199
Guest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
H
Hard disk
Checking Availability of Redundancy . . 263
Checking availability of redundancy . . . 250
Detailed information(Controller View) . . 231
Detailed information(WebBIOS) . . . . . . . 51
Disk Groups . . . . . . . . . . . . . . . . . . . . . . 23
Formatting . . . . . . . . . . . . . . . . . . . . . . . 95
Logical drive . . . . . . . . . . . . . . . . . . . . . . 23
Manual Rebuild . . . . . . . . . . . . . . 162, 240
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Preventive Replacement . . . . . . . 249, 263
RAID Levels . . . . . . . . . . . . . . . . . . . . . . 18
Replacing . . . . . . . . . . . . . . . 245, 247, 261
Status Icon . . . . . . . . . . . . . . . . . . 136, 205
Using Controller View . . . . . . . . . . . . . . 167
Hard disk failure prediction function . . . . . . . 35
HDD Check Scheduler. . . . . . . . . . . . . . . . . 36
Installation . . . . . . . . . . . . . . . . . . 117, 192
Uninstallation . . . . . . . . . . . . . . . . 120, 195
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . 134
Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
330
I
Installation
Battery Recalibration Schedule . . . . . . 121
GAM . . . . . . . . . . . . . . . . . . . . . . . . . . 183
GAM Client . . . . . . . . . . . . . . . . . . . . . 183
GAM Server . . . . . . . . . . . . . . . . . . . . . 183
HDD Check Scheduler . . . . . 117, 188, 192
ServerView RAID . . . . . . . . . . . . . . . . . 114
L
Log Information Viewer . . . . . . . . . . . 200, 229
Logical drive . . . . . . . . . . . . . . . . . . . . . . . . 23
Add to disk array configuration . . . . . . . 217
Background Initialization . . . . . . . 171, 236
Capacity Expansion
. . . . . . . . . . . . . 89, 153, 171, 219, 237
Checking status . . . . . . . . . . . . . . . . . . 169
Configuration example . . . . . . . . . . . . . . 24
Deleting . . . . . . . . . . . . . . . . . 92, 156, 222
Initialization . . . . . . . . . . . . . . . . . . . . . . 28
Make Data Consistent . . . . . . . . . . . 32, 88
RAID Levels. . . . . . . . . . . . . . . . . . . . . . 18
Rebuild. . . . . . . . . . . . . . . . . . . . . . . . . . 30
Status. . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Status Icon . . . . . . . . . . . . . . . . . . 137, 206
Using Controller View. . . . . . . . . . . . . . 234
Logical drive initialization
Fast initialization. . . . . . . . . . . . . . . . . . . 86
M
Make Data Consistent . . . . . . . . . . 32, 88, 239
Checking the Progress(GAM) . . . . . . . 237
Checking the Progress(ServerView RAID)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Checking the Progress(WebBIOS). . . . . 58
Make Data Consistent Status. . . . . . . . . . . 237
MegaRAID SAS 300-8E ROMB. . . . . . . . . . 16
MegaRAID SAS 8300XLP . . . . . . . . . . . . . . 16
MegaRAID SAS 8344ELP . . . . . . . . . . . . . . 16
MegaRAID SAS 8408E . . . . . . . . . . . . . . . . 16
Migrate Logical Drive . . . . . . . . . . . . . . . . . 153
Migrating . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Mirroring + striping . . . . . . . . . . . . . . . . . . . . 21
N
New Configuration . . . . . . . . . . . . . . . . . . . 214
New configuration . . . . . . . . . . . . . . . . . . . 213
P
PFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
PFA Count/S.M.A.R.T. . . . . . . . . . . . . 249, 263
MegaRAID SAS User's Guide
Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
R
RAID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
RAID Assist . . . . . . . . . . . . . . . . . . . . . . . 212
Add Logical Drive . . . . . . . . . . . . . . . . 213
Create . . . . . . . . . . . . . . . . . . . . . . . . . 214
Edit Configuration . . . . . . . . . . . . . . . . 213
Expand Array . . . . . . . . . . . . . . . . . . . 214
New Configuration. . . . . . . . . . . . . . . . 213
RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . 18
Redundancy . . . . . . . . . . . . . . . . . . . . . 18
RAID 5/6 SAS based on LSI MegaRAID . . . 16
Rebuild . . . . . . . . . . . . . . . . . . . . 30, 162, 240
Checking the Progress(GAM) . . . . . . . 236
Checking the Progress(ServerView RAID)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Checking the Progress(WebBIOS) . . . . 58
Hot Spare Rebuild . . . . . . . . . . . . . . . . . 30
Manual Rebuild . . . . . . . . . . . . . . . . . . . 31
Rebuild Status . . . . . . . . . . . . . . . . . . . 236
Recalibration. . . . . . . . . . . . . . . . . . . 163, 241
Redundancy . . . . . . . . . . . . . . . . . . . . . . . . 18
Redundant data regeneration . . . . . . 161, 239
Replacing battery . . . . . . . . . . . . . . . . . . . 327
S
S.M.A.R.T. . . . . . . . . . . . . . . . . . . . . . . . . . 35
SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Server group and server settings . . . . . . . 207
Server Icon . . . . . . . . . . . . . . . . . . . . 135, 199
Server Selection Box . . . . . . . . . . . . . . . . 198
ServerView . . . . . . . . . . . . . . . . . . . . . . . . 177
ServerView AlarmService . . . . . . . . . 112, 181
ServerView RAID
Access privileges . . . . . . . . . . . . . . . . 110
Events. . . . . . . . . . . . . . . . . . . . . . . . . 270
Installation. . . . . . . . . . . . . . . . . . . . . . 114
Log in . . . . . . . . . . . . . . . . . . . . . . . . . 126
Requirements . . . . . . . . . . . . . . . . . . . 109
Setting and Releasing Spare Disk Drives
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Uninstallation. . . . . . . . . . . . . . . . . . . . 116
ServerView RAID Manager
Change Access Mode . . . . . . . . . . . . . 130
Exiting . . . . . . . . . . . . . . . . . . . . . . . . . 128
Starting . . . . . . . . . . . . . . . . . . . . . . . . 126
Window Layout . . . . . . . . . . . . . . . . . . 129
Spare disk. . . . . . . . . . . . . . . . . . . . . . . . . . 30
Release. . . . . . . . . . . . . . . . . . . . . . . . 157
Releasing . . . . . . . . . . . . . . . . . . . 85, 223
Setting. . . . . . . . . . . . . . . . . . 84, 157, 223
Starting
Controller View . . . . . . . . . . . . . . . . . . .204
GAM . . . . . . . . . . . . . . . . . . . . . . . . . . .196
RAID Assist. . . . . . . . . . . . . . . . . . . . . .212
ServerView RAID Manager . . . . . . . . . .126
WebBIOS . . . . . . . . . . . . . . . . . . . . . . . .46
Status
Hard disk. . . . . . . . . . . . . . . . . . . . . . . . .25
Logical drive . . . . . . . . . . . . . . . . . . . . . .25
Status Icon
Hard disk. . . . . . . . . . . . . . . . . . . .136, 205
Logical drive . . . . . . . . . . . . . . . . .137, 206
Striping . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Striping + Parity . . . . . . . . . . . . . . . . . . . . . .20
System Log . . . . . . . . . . . . . . . . . . . . . . . .138
T
Tree View . . . . . . . . . . . . . . . . . . . . . . . . . .134
U
Uninstallation
Battery Recalibration Scheduler . . . . . .124
GAM . . . . . . . . . . . . . . . . . . . . . . . . . . .186
GAM Client . . . . . . . . . . . . . . . . . . . . . .186
GAM Server . . . . . . . . . . . . . . . . . . . . .187
HDD Check Scheduler . . . . .120, 191, 195
ServerView RAID . . . . . . . . . . . . . . . . .116
User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
User Privileges . . . . . . . . . . . . . . . . . . . . . .110
V
View Menu . . . . . . . . . . . . . . . . . . . . . . . . .201
W
WebBIOS . . . . . . . . . . . . . . . . . . . . . . . . . . .45
[Configured Drives] View. . . . . . . . . . . . .49
[Virtual Drives] View . . . . . . . . . . . . . . . .49
Exiting. . . . . . . . . . . . . . . . . . . . . . . . . . .50
Starting . . . . . . . . . . . . . . . . . . . . . . . . . .46
Viewing array controller. . . . . . . . . . . . . .60
Viewing background task . . . . . . . . . . . .58
Viewing hard disk . . . . . . . . . . . . . . . . . .51
Viewing logical drive . . . . . . . . . . . . . . . .54
Window Layout . . . . . . . . . . . . . . . . . . . .48
Write Back . . . . . . . . . . . . . . . . . . . . . . . . . .27
Write Cache . . . . . . . . . . . . . . . . . . . . . . . . .26
Write Policy. . . . . . . . . . . . . . . . . . . . . . . . . .26
Write policy
Changing (ServerView RAID) . . . . . . . .159
Changing(GAM) . . . . . . . . . . . . . . . . . .225
Write Through. . . . . . . . . . . . . . . . . . . . . . . .26
331
MegaRAID SAS User's Guide
B7FY-2321- 01ENZ0-00
Issued on
January, 2008
Issued by
FUJITSU LIMITED
● The contents of this manual may be revised without prior notice.
● Fujitsu assumes no liability for damages to third party copyrights or other rights
arising from the use of any information in this manual.
● No part of this manual may be reproduced in any form without the prior written
permission of Fujitsu.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement