B7fy 2311 01en

Integrated Mirroring 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 describes an overview, configuration precautions for the disk array, and the array
configuration flow.
Chapter 2 Array Configuration and Management [BIOS Utility]
This chapter explains the procedure to set up BIOS Utility. BIOS Utility is a basic utility to set
up and manage the array controller.
Chapter 3 Preparations
This chapter explains how to update device drivers and apply hotfix.
Chapter 4 Array Configuration and Management [ServerView RAID]
This chapter explains an overview of and requirements for ServerView RAID Manager, and how
to install and use it.
Chapter 5 Array Configuration and Management [GAM]
This chapter explains the overview and requirements of GAM, and how to install and use it.
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.
Appendix
This section explains the event codes for ServerView RAID and GAM, and the notes on the
array controller usage.
1
Before Reading This Manual
This manual is a guide for using the array controller (Integrated Mirroring SAS).
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.
• CD/DVD drive letters are shown as [CD/DVD drive]. Enter your drive letter 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.
2
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
Integrated Mirroring SAS the array controller, this array controller
Microsoft® Windows Server® 2003, Standard Edition Windows Server 2003 Windows
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 Windows Server

Microsoft® Windows Server® 2003, Enterprise x64 Edition 2003 x64［Note 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
Microsoft® Windows® 2000 Professional Windows 2000 Professional
Microsoft® Windows® XP Professional Windows XP
Red Hat Enterprise Linux 5 (for x86) 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 SLES9 or SUSE Linux
[Note 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).
3
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.
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 Logic, Global Array Manager (GAM), and Integrated Mirroring are trademarks or registered trademarks of LSI Logic
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.
4
Contents
Chapter 1 Overview
1.1 Array Controller Work Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2 Overview of the Disk Array Configuration . . . . . . . . . . . . . . . . . 12
1.2.1 Array controller specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
1.2.2 What is Disk Array? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.2.3 RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.2.4 Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
1.2.5 Checking Hard Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
1.3 Disk Array Configuration Features . . . . . . . . . . . . . . . . . . . . . . . 16
1.3.1 Logical Drive Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.3.2 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.3.3 Media Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.3.4 Hard Disk Failure Prediction Function (PFA / S.M.A.R.T.) . . . . . . . . . . . . .17
1.4 Notes before Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4.1 Cautions When Using This Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.4.2 Notes on Hard Disk to Be Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.5 Notes on Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.5.1 Notes on Using Array Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
1.5.2 Using ServerView RAID under Windows 2000 Server Environment . . . .19

2.1 Starting and Exiting BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.1 Starting BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
2.1.2 Exiting BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
2.2 BIOS Utility Screen Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3 Viewing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3.1 Viewing Information on Array Controller . . . . . . . . . . . . . . . . . . . . . . . . . .28
2.3.2 Viewing Information on Logical Drive and Hard Disk . . . . . . . . . . . . . . . .31
2.4 Creating and Deleting Logical Drive . . . . . . . . . . . . . . . . . . . . . . 36
2.4.1 Creating and Initializing Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
2.4.2 Deleting Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
2.5 Low Level Formatting of Hard Disks . . . . . . . . . . . . . . . . . . . . . 45
3.1 Updating Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.1.1 Creating Driver Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
3.1.2 Updating Drivers (Windows Server 2003) . . . . . . . . . . . . . . . . . . . . . . . . .50
3.1.3 Updating Drivers (Windows 2000 Server) . . . . . . . . . . . . . . . . . . . . . . . . .52
5
3.2 Applying Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 4 Array Configuration and Management

[ServerView RAID]
4.1 Requirements for ServerView RAID . . . . . . . . . . . . . . . . . . . . . . 56
4.1.1 ServerView RAID Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.2 Requirements for ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.1.3 Access Privileges to ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.1.4 Using ServerView RAID in Linux Environment . . . . . . . . . . . . . . . . . . . . . 59
4.1.5 Operation via Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.1.6 When Using ServerView RAID and GAM . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.2 Installing ServerView RAID [Windows] . . . . . . . . . . . . . . . . . . . 62
4.2.1 How to Install ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.2.2 How to Uninstall ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.3 Starting and Exiting ServerView RAID Manager . . . . . . . . . . . . 65
4.3.1 Preparations and Precautions for using ServerView RAID Manager . . . . 65
4.3.2 Starting ServerView RAID Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.3 Exiting ServerView RAID Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.4 ServerView RAID Manager Window Layout . . . . . . . . . . . . . . . . 69
4.4.1 Startup Window Layout and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.4.2 Menu Layout and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.3 Tree View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.5 Setting ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.6 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.7 Checking Status [ServerView RAID Manager] . . . . . . . . . . . . . 80
4.7.1 Checking Server Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.7.2 Checking Array Controller Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.7.3 Checking Hard Disk Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.7.4 Checking Logical Drive Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.7.5 Checking Progress of Background Task . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5.1 Overview and Requirements for GAM . . . . . . . . . . . . . . . . . . . . 90
5.1.1 GAM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
5.1.2 Requirements for GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5.1.3 Access Privileges to GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5.1.4 Using GAM in Linux Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5.1.5 Using GAM in Network Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.1.6 When Using Both ServerView RAID and GAM . . . . . . . . . . . . . . . . . . . . . 96
5.2 Installing GAM［Windows］ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.2.1 How to Install GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.2.2 Uninstalling GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
6
5.3 Starting and Exiting GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

5.3.1 Starting GAM and Signing On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
5.3.2 Exiting GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
5.4 GAM Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.4.1 Startup Window Layout and Functions . . . . . . . . . . . . . . . . . . . . . . . . . .104
5.4.2 Menu Layout and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
5.4.3 Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
5.4.4 Starting Controller View and the Window Layout . . . . . . . . . . . . . . . . . . .109
5.5 Server Group and Server Setting . . . . . . . . . . . . . . . . . . . . . . . 111
5.6 Viewing Information [GAM] . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.6.1 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.6.2 Viewing Array Controller Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.6.3 Viewing Hard Disk Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.6.4 Viewing Logical Drive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5.6.5 Checking Progress of Background Tasks . . . . . . . . . . . . . . . . . . . . . . . .120
5.7 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

6.1 How to Replace Hard Disk [ServerView RAID] . . . . . . . . . . . . 124
6.1.1 Checking Hard Disk to be Replaced [ServerView RAID] . . . . . . . . . . . .124
6.1.2 Replacing Failed Hard Disk [ServerView RAID] . . . . . . . . . . . . . . . . . . .125
6.1.3 Preventive Replacement of Hard Disk [ServerView RAID] . . . . . . . . . . .127
6.2 How to Replace Hard Disk [GAM] . . . . . . . . . . . . . . . . . . . . . . . 131
6.2.1 Checking Hard Disk to be Replaced [GAM] . . . . . . . . . . . . . . . . . . . . . .131
6.2.2 Replacing Failed Hard Disk [GAM] . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
6.2.3 Preventive Replacement of Hard Disk [GAM] . . . . . . . . . . . . . . . . . . . . .134
Appendix
A A List of ServerView RAID Event Logs . . . . . . . . . . . . . . . . . . 138
B A List of GAM Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
C Notes on Usage for the Array Controller . . . . . . . . . . . . . . . . . 171
C.1 When Replacing Array Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
7
8
Chapter 1
Overview
This chapter describes an overview,

configuration precautions for the disk array, and
the array configuration flow.
1.1 Array Controller Work Flow . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 Overview of the Disk Array Configuration . . . . . . . . . . . . . 12
1.3 Disk Array Configuration Features . . . . . . . . . . . . . . . . . . 16
1.4 Notes before Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5 Notes on Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9
Chapter 1 Overview
1.1 Array Controller Work Flow
The work flow when using a disk array controller is as follows:
For Windows
１. Designing the Disk Array

Set the operation pattern of the disk array 㸢1.2 Overview of the Disk Array Configuration
configuration. Design the RAID level and 㸢1.3 Disk Array Configuration Features
the logical drive configuration.
２. Configuring the Disk Array

Configure the disk array using BIOS Utility before installing the OS.
㸢䇭Chapter 2 Array Configuration and Management [BIOS Utility] ServerStart will help
you set up Steps
３. Installing the OS
from ĳ to ĵ.
㸢䇭"User's Guide" provided with the server
㸢䇭3.2 Applying the Hotfix
４. Installing the Management Tools

Install the following management tools. 㩷Chapter 4 Array Configuration and
䇭䇭䊶ServerView RAID䇭* Management [ServerView RAID]
䇭䇭䊶Global Array Manager(GAM)䇭* Chapter 5 Array Configuration and
Management [GAM]
* Either one tool can be installed. For details, see ReadmeEN.html on the "Array Controller Document & Tool CD".
５. Updating the Device Drivers

Update the device drivers to the latest version 㸢䇭3.1 Updating the Device Drivers
stored on the "Array Controller Document & Tool CD".
６. Preparing the Environment for the Management Tools

Register the user account with the OS to use 㩷Chapter 4 Array Configuration and
the management tools. (This is not required Management [ServerView RAID]
if it is set at the installation of the management Chapter 5 Array Configuration and
tools.) Management [GAM]
10
For Linux
For Linux inforomation, see the PRIMERGY page on the Fujitsu website (http://primergy.fujitsu.com/).
１. Designing the Disk Array

Set the operation pattern of the disk array 㸢1.2 Overview of the Disk Array Configuration
configuration. Design the RAID level and 㸢1.3 Disk Array Configuration Features
the logical drive configuration.
２. Configuring the Disk Array

Configure the disk array using WebBIOS before installing the OS.
㸢䇭Chapter 2 Array Configuration and Management [BIOS Utility]
３. Installing the OS
㸢䇭 "Installation Guide"
４. Installing the Management Tools

Install the following management tools. 㸢䇭 "Installation Guide"
䇭䇭䊶ServerView RAID䇭*
䇭䇭䊶Global Array Manager(GAM)䇭*
䇭䇭
* Either one tool can be installed. For details, see ReadmeEN.html on the "Array Controller Document & Tool CD".
５. 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.)
11
Chapter 1 Overview
1.2 Overview of the Disk Array

Configuration
This section describes an overview of the disk array (RAID levels and logical drives)
and its function.
1.2.1 Array controller specifications
The specifications of the array controller described in this manual are as follows:
table: Specifications
Item Contents
Product name No model name No model name RAID 0/1 SAS 4P
(LSI SAS 1068) (LSI SAS 1064E) (LSI SAS 1064E)
Where to be installed Onboard [Note 1] Onboard [Note 1] PCI-E Slot installable card
in the server
Interface SAS (Serial Attached SCSI)
The number of ports 8 ports 4 ports 4 ports
Cache memory and Not available
capacity
Supported OS OS supported by the server
Management Tools Available tools are: (1) BIOS Utility 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 management tools before using the array controller.
Install either ServerView RAID or GAM, but not both at a time. For which to use, see
ReadmeEN.html on Array Controller Document & Tool CD.
• BIOS Utility
BIOS Utility in the array controller.
J"Chapter 2 Array Configuration and Management [BIOS Utility]" (pg.23)
• ServerView RAID
J"Chapter 4 Array Configuration and Management [ServerView RAID]" (pg.55)
• Global Array Manager (GAM)
J"Chapter 5 Array Configuration and Management [GAM]" (pg.89)
[Note 1]: It is installed on the baseboard of the server.
12
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 disks to achieve better performance and higher reliability than when using a single
hard disk.
An array controller controls the access to each hard disk. There are different types of control methods
that are defined as RAID levels.
By using a redundant RAID level, system operation can be continued without data loss in the event of a
hard disk failure.
1.2.3 RAID Levels
There are several types of RAID levels, with different characteristics.

This array controller only supports RAID 1.
table: Characteristics of each RAID level
RAID Number of
Available total capacity Redundancy
Level hard disks
RAID 1 2 Capacity of one hard disk Yes
RAID 1 (Mirroring)
Mirroring is a function in which data is written into two hard disks in duplicate. When operating in
RAID 1 disk array configuration, the system always writes the same data in the two hard disks using the
redundancy feature. Operation continues even when one of the hard disks fails and loses redundancy
(Critical).
RAID 1 always consists of two hard disks and the actual capacity you can use is the capacity of one hard
disk.
D-2
Data D-1 D-3
Hard Disk 1
D-1
Array Controller
D-2 D-3 D-1 D-2 D-3
Hard Disk 1
` With RAID 1, operation continues even if one of the hard disks fails (critical). However, the data could
be lost if both hard disks fail. If the status of a logical drive becomes critical, replace the failed hard disk
as soon as possible to recover the redundancy.
See "Chapter 6 Replacing Hard Disk" (Jpg.123) for how to replace hard disks.
` Backup the data as frequently as possible just in case even with redundancy.
13
Chapter 1 Overview
1.2.4 Logical Drive
A logical drive is a logical hard disk space created when a disk array is configured. The OS recognizes it
as same as a single hard disk.
As shown in the following figure, with RAID 1, two hard disks compose one logical drive, but the OS
recognizes it as if a single hard disk was connected.
Logical drive 0
Hard disk 1 Hard disk 2
` Hard disks in a logical drive should be of the same model (with the same capacity and speed).
` This array controller can support only one logical drive.
` Right after the creation of a logical drive using this array controller, the logical drive does not have
redundancy. To use it with redundancy, initialization of the logical drive is required. For details, see
"1.3.1 Logical Drive Initialization" (Jpg.16).
Status during hard disk failure

If one of the hard disks fails, the logical drive loses its redundancy, and the status becomes critical.
If the other drive also fails, the logical drive status becomes "Offline" (unavailable).
1.2.5 Checking Hard Disk Status
Hard disks and logical drives should be regularly monitored, and be replaced if there is a failure or
indication of a failure.
` Status indicators differ depending on a management tool. For the status information, see the
appropriate section in your management tool's documents.
• BIOS Utility
J"2.3.2 Viewing Information on Logical Drive and Hard Disk" (pg.31)
• ServerView RAID
J"4.4.3 Tree View Layout" (pg.73)
• GAM
J"5.4.4 Starting Controller View and the Window Layout" (pg.109)
` 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 A List of ServerView RAID Event Logs" (pg.138)
J"Appendix B A List of GAM Event Logs" (pg.158)
14
Logical drive status

Logical drive statuses are shown in the table below.
table: Logical drive status
Status Description
Online The logical drive is operating normally.
Critical A redundant logical drive (RAID 1) is currently operating without redundancy due to a
hard disk failure. Replace the failed hard disk as soon as possible and perform a rebuild to
restore the online status. See "Chapter 6 Replacing Hard Disk" (Jpg.123) for how to
replace hard disks and rebuild.
Offline This indicates that the logical drive is not operating. Two or more hard disk failure in a
logical drive leads to offline state. The data in the logical drive will be lost.
Hard disk status

Hard disk statuses are shown in the table below.
table: Hard disk status
Status Description
Online The hard disk is configured in the disk array and operating normally.
Unused It is out of operation as the hard disks are not configured in the disk array. The hard disk is
operating normally.
Failed The disk is damaged and data read/write is disabled. Replace the hard disk and perform a
rebuild. See "Chapter 6 Replacing Hard Disk" (Jpg.123) for how to replace a hard disk.
Offline Data read/write is disabled by the array controller. Perform a rebuild to use the hard disk
again.
Rebuild The hard disk is currently being rebuilt.
Failure Predicted The hard disk is currently operating normally, but may fail in the near future (failure
predicted status). See "Chapter 6 Replacing Hard Disk" (Jpg.123) 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 disks may be
operating without redundancy. The hard disk must be replaced as soon as possible. See "6.1.2
Replacing Failed Hard Disk [ServerView RAID]" (Jpg.125) and "6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.132) fo how to replace a hard disk.
` This array controller sets the redundancy management priority as primary or secondary for each hard
disk in the logical drive.
When one hard disk has failed, the other operating drive is set as primary, and the rebuild is performed
using the primary drive for the secondary drive.
15
Chapter 1 Overview
1.3 Disk Array Configuration Features
This section explains the features in disk array configuration.
1.3.1 Logical Drive Initialization
To enable a logical drive to operate with redundancy, initialization is required to make the hard disks in
the logical drive consistent.
Right after the creation of a logical drive using this array controller, the logical drive does not have
redundancy and data is only stored on the primary hard disk. The initialization can be done with a
rebuild. For details about rebuild, see "1.3.2 Rebuild" (Jpg.16).
` The logical drive does not have redundancy until the initialization is completed. So if the primary hard
disk fails, the data will be lost.
` Before the initialization, the secondary hard disk cannot be used and its failure LED remains lit.
` The initialization is done with a rebuild, which means that the hard disk failure LED of the secondary
drive keeps blinking during the initialization.
1.3.2 Rebuild
Even if a hard disk in a logical drive fails, if there is redundancy (RAID 1), the logical drive continues to
operate in critical. However, if another hard disk in the same logical drive also fails, the status of the
logical drive becomes unavailable (offline). Rebuild is a operation to recover a logical drive from critical
to normal (online).
The rebuild process is performed in the background in parallel with normal I/O access. During
rebuilding, if a logical drive becomes critical, the redundancy of the logical drive remains lost. Once the
rebuild is complete, it is restored to online.
You can start a rebuild by executing [Synchronize] in BIOS Utility or by executing [Rebuild] in the
array management tool (ServerView or GAM).
Estimated time for rebuild

The estimated time for rebuild differs depending on I/O load from the server. The table below shows the
estimated time when the I/O load is none and high.
It also differs depending on such factors as the server configuration and the availability of hard disks to
be used. Use them only as a reference.
table: Estimated time for rebuild
Hard disk capacity No load High load
73GB approx. 4 hrs approx. 7 hrs
16
` The rebuild is performed in parallel with regular I/O operation. Therefore, I/O performance for the
logical drives can be degraded during rebuild. With this array controller, the I/O performance degrades
about 50% at maximum.
` If the system restarts or shuts down during rebuild, the rebuild is resumed from where it was stopped
the next time.
1.3.3 Media Verification
Media verification is a function that detects media errors on a hard disk in advance and restores data
using the data on the other hard disks.
This array controller always performs media verification when the logical drive is in online state.
If there are media errors on the hard disks that were not replaced, the rebuild cannot restore their data.
Media verification reduces the risk of data loss at rebuild, by correcting media errors in advance.
1.3.4 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 hard disks, which determines the
failure risk 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.3 Preventive
Replacement of Hard Disk [ServerView RAID]" (Jpg.127) or "6.2.3 Preventive Replacement of Hard
Disk [GAM]" (Jpg.134) for the replacement procedure. The hard disk for which failure is predicted can
be identified by management tools or event logs.
17
Chapter 1 Overview
1.4 Notes before Operation
Check the following before starting the operation.
1.4.1 Cautions When Using This Product
The usage may be limited depending on the server to be installed in.
1.4.2 Notes on Hard Disk to Be Used
The following notes apply to the hard disks to be used. Please read them in advance.
z Usable hard disk

Use the hard disks of the same model (with the same capacity and speed) in a logical drive. Check that
the installed hard disks have the same capacity and speed. Also, 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 disks 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 installing it to the array controller.
The same caution applies when using hard disks used by this product on another system. See "2.5 Low
Level Formatting of Hard Disks" (Jpg.45) and completely erase the information on the hard disk before
using it on another system.
z Removing hard disk

When the server is runnning, do not remove 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.
18
1.5 Notes on Operation
This section contains notes concerning system operation when using this array
controller.
1.5.1 Notes on Using Array Controller
When using Windows in a disk array configuration, one of the following events may be recorded in the
Event Viewer's system log:
Source : lsi_sas
Type : Warning
Event ID : 129
Description: The description for Event ID (129) in Source (lsi_sas) cannot
be found.
(The rest is omitted.)
Source : lsi-sas
Type : Error
Event ID : 11
Description: The driver detected a controller error on ¥Device¥RaidPortN
(The rest is omitted.)
These logs entry means that an internal reset has been issued in the device driver, but since the event has
been restored by the OS retry, you can continue 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 Using ServerView RAID under 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 is installed, the number of created
logical drives, the number of installed hard disks, and the setting values of the server name.
19
Chapter 1 Overview
z For events via ServerView
Source 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 1068SASIME-2399 (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 1068SASIME-2399 (0): Logical drive (0) missing after reboot
(Server PRIMERGY03)
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 1068SASIME-2399 (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 1068SASIME-2399 (0): Logical drive (0) missing after reboot
When the events above are recorded, check the state of the array using ServerView RAID Manager. If
the array is recognized as the normal state, ignore the events.
20
` Information that Windows SCSI mini port driver outputs will be changed by applying the hotfix. So, the
information is different from what ServerView RAID had until then. So, the events above occur at the
first restarting after applying the hotfix.
` The events will not occur if the state of the array is normal after the next startups.
` The events are recorded when restarting the server after installing Windows 2000 Server since the
hotfix is automatically applied if you install the server using ServerStart.
21
Chapter 1 Overview
22
Chapter 2
Array Configuration and
Management [BIOS Utility]
This chapter explains the procedure to set up

BIOS Utility. BIOS Utility is a basic utility to set
up and manage the array controller.
2.1 Starting and Exiting BIOS Utility . . . . . . . . . . . . . . . . . . . . 24

2.2 BIOS Utility Screen Layout . . . . . . . . . . . . . . . . . . . . . . . 27
2.3 Viewing Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.4 Creating and Deleting Logical Drive . . . . . . . . . . . . . . . . . 36
2.5 Low Level Formatting of Hard Disks . . . . . . . . . . . . . . . . . 45
23
2.1 Starting and Exiting BIOS Utility
This section explains how to start up and exit BIOS Utility. BIOS Utility starts from
BIOS at system startup, regardless of whether the OS has been installed or not on
the computer to be used.
` The terms "logical drive" and "array controller" used in this manual are displayed as "Array" and
"Adapter" respectively in BIOS Utility. Read the manual by replacing the terms with those used in BIOS
Utility when necessary.
2.1.1 Starting BIOS Utility
Follow the procedure below:
1 After turning on the server, press the [Ctrl] + [C] keys while the following
messages are displayed on the screen.
LSI Logic Corp. MPT SAS BIOS

MPTBIOS-x.xx.xx.xx (xxxx.xx.xx)
Copyright xxxx-xxxx LSI Logic Corp.
Press Ctrl C to start LSI Logic Configuration Utility
Press the [Ctrl]+[C] keys while the message "Press Ctrl C to start LSI Logic
Configuration Utility" is deiplayed on the screen.
The following message appears and BIOS Utility starts up after the POST of the server is
complete.
Please wait, invoking SAS Configuration Utility.
` If the following message appears, the hard disk may have a failure.
xxxx enter the LSI Logic Configuration
Utility to investigate!
In this case, see "Chapter 6 Replacing Hard Disk" (Jpg.123) to check the hard disk status. If
there is a failed hard disk, replace the disk and perform rebuild.
24
BIOS Utility starts and the [Adapter List] screen appears.
` For this array controller, "SAS1068" or "SAS1064E", depending on a server and a card,
appears on [Adapter] of the above screen.
2.1.2 Exiting BIOS Utility
Follow the procedure below to exit BIOS Utility.
1 Display the [Adapter List] screen.

If another screen is displayed, press the [Esc] key several times until the [Adapter List] screen
appears.
25
2 Press the [Esc] key.

The [Exit Menu] appears.
3 Select [Exit the Configuration Utility and Reboot] and press the [Enter] key.
BIOS Utility closes and the system restarts.
26
2.2 BIOS Utility Screen Layout
BIOS Utility screen consists of three areas.

The displayed contents vary depending on functions to be selected.
Header Area
Main Area
Footer Area
` In BIOS Utility, press the [Esc] key to return to the previous screen.
Header area
The upper row shows the name and the version number of this utility. The lower row shows the name of
the current screen.
Main area
The main area for each screen. Configurable items and menus are displayed in yellow and can be
configured by moving the cursor using the keyboard.
Footer area
A help message for the current screen appears. Explanation of function keys is displayed.
27
2.3 Viewing Information
With BIOS Utility, you can see information on the array controller, a logical drive, and
hard disks.
• Viewing Information on Array Controller (Jpg.28)
• Viewing Information on Logical Drive and Hard Disk (Jpg.31)
2.3.1 Viewing Information on Array Controller
Information about the array controller is displayed on the [Adapter Properties] and the [Global
Properties] screens.
Adapter Properties
1 Start up BIOS Utility.

J"2.1.1 Starting BIOS Utility" (pg.24)
` If BIOS Utility is already running and another screen is displayed, press the [Esc] key several
times until the [Adapter List] screen appears.
2 Check that the [Adapter List] menu is selected and press the [Enter] key.
` This screen is for selecting an array controller to be accessed, but only one controller is shown.
So, simply press the [Enter] key.
The [Adapter Properties] screen appears.
28
table: Array controller information on the [Adapter Properties] screen

Item Description
Adapter Displays the name of the array controller.
PCI Slot Displays the PCI slot number where the array controller is installed.
PCI Address Displays the array controller's PCI address configured by the server BIOS.
Displays, from left to right, the bus number, the device number, and the
function number.
MPT Firmware Displays the firmware revision of the array controller.
Revision
SAS Address Displays the SAS address of the array controller.
NVDATA Version Displays the NVRAM revision of the array controller.
Status Displays the status of the array controller.
Enabled Indicates that the array controller BIOS is available.
Disabled Indicates that the array controller BIOS is unavailable.
Error Indicates that the array controller's BIOS is not operating due to failures.
Boot Order Displays the boot order of the array controllers when multiple array controllers
are installed. With this array controller, this item is always "0" because only
one controller can be installed on the server.
Boot Support Displays the control configuration for this array controller. For this array
controller, this item is set as "Enabled BIOS & OS" (i.e. this array controller is
controllable from either BIOS or the OS driver) and the configuration cannot
be changed.
` Press the [Esc] key to return to the [Adapter List] screen. If you have changed settings, the
confirmation screen appears. Select [Discard changes then exit this menu].
Global Properties

29
2 Check that the [Adapter List] menu is selected and press the [Alt] + [N] keys to
select the [Global Properties] menu.
The [Global Properties] screen appears.
` Do not change the default values of the items on this screen. If you have changed them by
mistake, select [Restore Defaults] and press the [Enter] key to restore the default values.
table: Array controller information on the [Global Properties] screen

Item Description
Pause When Boot Alert Indicates whether or not to pause operation when a failure is detected during
Displayed the array controller's Power On Self Test (POST).
The default value is "No".
Boot Information Displays the scope of the information that is displayed during the array
Display Mode controller's POST (e.g. hard disks).
The default value is "Display adapter & installed devices".
Set Interrupt Indicates whether or not to accept INT 13h interrupts.
The default value is "Hook interrupt, the default".
` Press the [Esc] key to return to the [Adapter List] screen. If you have changed settings, the
confirmation screen appears. Select [Discard changes then exit this menu].
30
2.3.2 Viewing Information on Logical Drive and Hard Disk
You can see the information on logical drive and hard disks on the [View Array] screen.

` This screen is for selecting an array controller to be accessed, but only one controller is shown.
So, simply press the [Enter] key.
3 Select [RAID Properties] and press the [Enter] key.

The [Select New Array Type] screen appears.
31
4 Select [View Existing Array] and press the [Enter] key.

The [View Array] screen appears, which displays the information about a logical drive and the
hard disks that belong to the logical drive.
` When no logical drives exist, [View Existing Array] is not displayed.
See " Information on logical drives" (Jpg.32) for information on logical drives, and
" Information on hard disks" (Jpg.33) for details on hard disks.
5 Press the [Esc] key to close the screen.

The display returns to the [Adapter Properties] screen.
Information on logical drives

This section explains each item in the information on logical drives.
` The information on logical drives is displayed at the top of the main area of the [View Array] screen.
z Array
The total number of logical drives existing on the array controller and the number of the logical drives
for which information is currently shown are displayed. Since this array controller only suppors one
logical drive, "1 of 1" always appears.
z Identifier
The name to identify the logical drive if displayed. It is usually displayed as "LSILOGICLogical Volume
3000".
z Type
The type of logical drive is displayed. It is always displayed as "IM ".
32
z Scan Order
The scan order among multiple logical drives is displayed. Since this array controller only supports one
logical drive, "0" always appears .
z Size (MB)
The total capacity of the logical drive is displayed.
z Status
The current status of the logical drive is isplayed. The meaning of each status is shown below:
table: Logical drive status
Status Indicator Description
Optimal The logical drive is operating normally.
The logical drive is operating without redundancy because one of the hard disks has failed.
Degraded See "Chapter 6 Replacing Hard Disk" (Jpg.123) and immediately replace the failed hard
disk.
The logical drive is unavailable because multiple hard disks have failed. See "Chapter 6
Failed
Replacing Hard Disk" (Jpg.123) and immediately replace the failed hard disks.
xx% Syncd The logical drive is being rebuilt or initialized. The progress is displayed as a percentage.
Inactive The logical drive cannot be used because it has been used in another system and the hard
disks still contain the previous system information. See "2.5 Low Level Formatting of Hard
Disks" (Jpg.45) to format the hard disks, and then configure a new logical drive.
Information on hard disks

This section explains each item of the hard disk information.
` The information on hard disks is displayed at the bottom of the [View Array] screen.
z Slot Num
The number of a physical slot in which the hard disk is installed is displayed.
z Device Identifier
The hard disk vendor name, the model name, and the firmware version of the hard disk are displayed
from left to right.
z RAID Disk
It indicates whether or not a hard disk is contained in the logical drive with "Yes" or "No".
z Hot Spr
It indicates whether or not a hard disk is assigned as a hot spare drive with "Yes" or "No". This is always
"No", because this array controller does not support the hot spare function.
33
z Drive Status
It displays the current status of the hard disk. The meaning of each status is shown below:
table: Hard disk status
Status
Description
Indication
--------- The hard disk is operating normally but does not belong to a logical drive.
Primary The hard disk is operating normally and is configured as the primary disk of RAID 1.
Secondary The hard disk is operating normally and is configured as the secondary disk of RAID 1.
Missing The hard disk has failed and there is no response.
See "Chapter 6 Replacing Hard Disk" (Jpg.123), and replace the failed hard disk.
Failed The hard disk has a failure.
Offline The hard disk is offline state and data read/write is disabled.
See "Chapter 6 Replacing Hard Disk" (Jpg.123) and replace the hard disk in the offline state.
Initing The hard disk is being formatted.
Inactive The hard disk cannot be used because it contains information of another system.
See "2.5 Low Level Formatting of Hard Disks" (Jpg.45) to format the hard disk before using
it.
There is also a possibility that the detected hard disk has a failure. See "Chapter 6 Replacing
Hard Disk" (Jpg.123), and if the hard disk has a failure, immediately replace the drive.
Not Syncd The hard disk is included in a logical drive, but the initialization or the rebuild is not
complete. If the hard disk is in this status even though initialization or rebuild is complete, the
drive must have a failure.
See "Chapter 6 Replacing Hard Disk" (Jpg.123) to replace the failed hard disk.
Wrg Type The hard disk cannot be used as a part of logical drive because the drive is the wrong type or
is not an appropriate product.
If the hard disk is in this status, the drive may have a failure.
Too Small The hard disk cannot be used as a part of logical drive because its capacity is too small.
Max Dsks The number of hard disks exceeds the maximum possible number that can be configured in a
logical drive.
No SMART The hard disk cannot be used because it does not support S.M.A.R.T. failure prediction
function.
Wrg Intfc The hard disk cannot be used as a part of logical drive because its interface is not SAS.
z Pred Fail
It displays with "Yes" or "No" whether or not the hard disk is operating with the PFA (S.M.A.R.T.) over
the threshold.
34
` A hard disk with [Pred Fail] "Yes" is exceeding the PFA (S.M.A.R.T.) threshold and may fail in the near
future. See "Chapter 6 Replacing Hard Disk" (Jpg.123) to replace the hard disk as soon as possible
as a preventive measure.
z Size
The capacity of the hard disk is displayed in MB.
35
2.4 Creating and Deleting Logical

Drive
To use a logical drive with redundancy (RAID 1), create and initialize it with BIOS
Utility.
When deleting a logical drive, the hard disks configured in the logical drive can be
restored unconfigured.
2.4.1 Creating and Initializing Logical Drive
Follow the procedure below to create a logical drive.

After creating a logical drive, initialize it to make it redundant.
` For how to initialize a logical drive, see "1.3.1 Logical Drive Initialization" (Jpg.16).

` This screen is for selecting an array controller to access, but only one controller is shown. So,
simply press the [Enter] key.
36

4 Select [Create IM Volume] and press the [Enter] key.
` This array controller does not support [Create IME Volume] and [Create IS Volume] functions.
Do not select them.
The [Create New Array] screen appears.
37
5 Move the cursor to the [RAID Disk] field of the hard disk to be configured as the
primary disk and press the [Space] key.
` The drive with [Slot Num] "0" is usually configured as the primary disk.
The methods to make a logical drive are displayed.
6 Press the [M] key to select a method from the upper row.
` Do not press the [D] key here. This array controller does not support the method selected with
the [D] key.
A list of the installed hard disks is displayed. Check that the [Drive Status] of the drive selected in
the step 4 is displayed as "Primary".
38
7 Move the cursor to the [RAID Disk] field of another drive and press the [Space]
key.
The [Drive Status] becomes "Secondary".
8 Press the [C] key.

The confirmation screen to create a logical drive appears.
9 Select [Save changes then exit this menu] and press the [Enter] key.
The creation of the logical drive starts. It may take from several seconds to up to a minute to
create a logical drive.
When the creation is complete, the [Adapter Properties] screen appears.
` The created logical drive does not have redundancy. Make sure to make it redundant by initial-
izing it.
39
10 Initialize the logical drive. Select [RAID Properties] and press the [Enter] key.

The [View Array] screen appears.
40
12 Select [Manage Array] and press the [Enter] key.

The [Manage Array] screen appears.
13 Select [Synchronize Array] and press the [Enter] key.
` This array controller does not support the [Manage Hot Spare] function. Do not select it.
The confirmation screen to initialize a logical drive appears.
41
14 Press the [Y] key.

The [Manage Array] screen appears and the initialization of the logical drive starts.
` The logical drive does not have redundancy until the completion of the initialization. And if the
primary hard disk fails, data will be lost.
` Before the initialization, the secondary hard disk cannot be used and its failure LED remains lit.
` The initialization is done with a rebuild, which means that the hard disk failure LED of the sec-
ondary drive flashes during the initialization.
` This array controller supports background initialization. If you exit BIOS Utility and restart the
server, initialization is performed in parallel with the OS installation.
15 Press the [Esc] key twice to return to the [Adapter Properties] screen.
2.4.2 Deleting Logical Drive
To delete the logical drive and restore the hard disks to their original state (not belonging to a logical
drive), follow the procedure below.
` Note that the data on hard disks are deleted when the logical drive is deleted.

42


The [View Array] screen appears.
43
5 Select [Manage Array] and press the [Enter] key.

The [Manage Array] screen appears.
6 Select [Delete Array] and press the [Enter] key.

The confirmation screen to delete the logical drive appears.
7 Press the [Y] key.

The deletion of the logical drive starts. It may take from several seconds to up to a minute to
delete the logical drive.
When the deletion is finished, the [Adapter Properties] screen appears.
44
2.5 Low Level Formatting of Hard Disks
This section explains how to perform a low level formatting of hard disks in BIOS
Utility.
When you reuse a hard disk that was previously used in another system, follow the
procedure below to format it.
` All the data on a hard disk are deleted when the drive is formatted.
` Do not turn off or restart the server during formatting. The hard disk will fail and become unusable.
` Hard disk formatting takes a long time. The time required depends on the type of the hard disk, but
approximately 1.5 minutes per GB. (For example, it takes about 110 minutes to format a 73GB hard
disk.) Make sure you have enough time before performing formatting, as the formatting cannot be
interrupted once it has been started.
` Hard disk formatting can only be done for hard disks that are not contained in a logical drive.
` To format the hard disks contained in a logical drive, delete the logical drive first, referring to "2.4.2
Deleting Logical Drive" (Jpg.42) , and then format the hard disk with the following procedure.
` It is not possible to format multiple hard disks at the same time.

45
3 Select [SAS Topology] and press the [Enter] key.

The [SAS Topology] screen appears.
4 Select [Direct Attached Devices] and press the [Enter] key.

A list of the connected hard disks is displayed.
46
5 Select the hard disk you wish to format and press the [Alt] + [D] keys.
The [Device Properties] screen appears.
6 Select [Format] and press the [Enter] key.

The [Device Format] screen appears.
47
7 Press the [F] key.

Hard disk formatting starts and a progress bar is displayed at the bottom of the screen.
Formatting is complete when the progress bar reaches 100% (the end).
8 Press the [Esc] key three times to return to the [Adapter Properties] screen.
48
Chapter 3
Preparations
This chapter explains how to update device

drivers and apply hotfix.
3.1 Updating Device Drivers . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.2 Applying Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
49
3.1 Updating Device Drivers
This section explains how to update the device drivers installed in the server.
The driver update operation varies depending on the OS to be used.
Before the update, create driver disks using "Array Controller Document & Tool CD".
` Even if the OS is newly installed in the server, the drivers need to be updated when those included on
"Array Controller Document & Tool CD" are the latest version.
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 Disks
Before updating the device drivers, create driver disks with "Array Controller Document & Tool CD" by
following the procedure below.
1 Prepare formatted floppy disks.
2 Insert "Array Controller Document & Tool CD" into the CD/DVD drive.
3 Copy the drivers for the OS to be used from the following folder on the CD-
ROM 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\IM-SAS\W2K Integrated Mirroring SAS Windows
2000 Drivers Disk
Windows Server 2003 \Drivers\IM-SAS\W2K3 Integrated Mirroring SAS Windows
Server 2003 Drivers Disk
Windows Server 2003 x64 \Drivers\IM-SAS\W2K3x64 Integrated Mirroring SAS Windows
Server 2003 for x64 Edition Drivers
Disk
` For the device driver version, see ReadmeEN.html on "Array Controller Document & Tool CD".
3.1.2 Updating Drivers (Windows Server 2003)
1 Log on to Windows with Administrator privileges.
2 Exit all programs before updating.
50
3 Select [System] from [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 [LSI Logic Adapter, SAS 3000 series, 8-port with 1068 -StorPort]
or [LSI Logic Adapter, SAS 3000 series, 4-port 1064E-StorPort].
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
"Integrated Mirroring SAS Windows Server 2003 Drivers Disk"
• For Windows Server 2003 x64
"Integrated Mirroring SAS Windows Server 2003 for x64 Edition Drivers Disk"
12 Enter "A:\" in [Copy manufacturer's file from] and click [OK].
13 Select [LSI Logic Adapter, SAS 3000 series, 8-port with 1068 -StorPort] or [LSI
Logic Adapter, SAS 3000 series, 4-port 1064E-StorPort] in 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.
15 Click [Close] to close the [Properties] window.
` If the [Change System Settings] window appears, click [No].
16 Restart the system.
` To confirm if the device driver is correctly read, check that either of the following controllers is
displayed in [SCSI and RAID controller] of the Device Manager.
51
• LSI Logic Adapter, SAS 3000 series, 8-port with 1068 -StorPort
or
• LSI Logic Adapter, SAS 3000 series, 4-port 1064E-StorPort
Also, to check the version of the device driver that is being read, double-click the above controller
name, select the [Driver] tab and see the version information.
3.1.3 Updating Drivers (Windows 2000 Server)
2 Exit all programs before updating.
3 Select [System] from [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 [LSI Adapter, SAS 3000 series, 8-port with 1068] or [LSI Adapter,
SAS 3000 series, 4-port with 1064E].
The [Properties] window appears.
7 Select the [Driver] tab and click [Update Driver].

The [Device Driver Upgrade Wizard] window appears.
8 Click [Next].
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 "Integrated Mirroring SAS Windows 2000
Drivers Disk" in the floppy disk drive.
11 Enter "A:\" in [Copy manufacturer's file from] and click [OK].
12 Select [LSI Adapter, SAS 3000 series, 8-port with 1068] or [LSI Adapter, SAS
3000 series, 4-port with 1064E] in 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.
52
` If the [Change System Settings] window appears, click [No].
` To confirm if the device driver is correctly read, check that either of the following controllers is
displayed in [SCSI and RAID controller] of the Device Manager.
• LSI Adapter, SAS 3000 series, 8-port with 1068
or
• LSI Adapter, SAS 3000 series, 4-port with 1064E
Also, to check the version of the device driver that is being read, double-click the above controller
name, select the [Driver] tab and see the version information.
53
3.2 Applying Hotfix
In order to use this array controller in a Windows environment, hotfix needs to be

applied.
` For the hotfix, use "PRIMERGY Startup Disc" or "ServerStart Disc 1 CD-ROM" 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
2 Close all applications.
3 Insert "PRIMERGY Startup Disc" or "ServerStart Disc 1 CD-ROM" into the CD/
DVD drive.
4 Run the following program to apply the 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 x64 Service Pack 1
[CD/DVD drive]:\HOTFIX\W2K3x64\WindowsServer2003.WindowsXP-KB916048-
x64-ENU.exe
54
Chapter 4
Management
[ServerView RAID]
This chapter explains an overview of and
requirements for ServerView RAID Manager, and
how to install and use it.
4.1 Requirements for ServerView RAID . . . . . . . . . . . . . . . . . 56

4.2 Installing ServerView RAID [Windows] . . . . . . . . . . . . . . . 62
4.3 Starting and Exiting ServerView RAID Manager . . . . . . . . 65
4.4 ServerView RAID Manager Window Layout . . . . . . . . . . . 69
4.5 Setting ServerView RAID . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.6 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.7 Checking Status [ServerView RAID Manager] . . . . . . . . . 80
55
4.1 Requirements for ServerView

RAID
This section describes ServerView RAID.

ServerView RAID is to monitor, manage, maintain, and configure array controllers
and the hard disks and logical drives that are connected to the array controller.
4.1.1 ServerView RAID Overview
This 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
controller.
z ServerView RAID Manager

It is a graphical user interface that uses a Web browser and Java. You manage and configure array
controller with ServerView RAID Manager.
ServerView RAID Manager㧔GUI㧕 ServerView RAID Service

(Service)
Array Controller
56
` 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 which to use, see ReadmeEN.html
on Array Controller Document & Tool CD. If by mistake you have installed GAM rather than
ServerView RAID, you must uninstall GAM, and then install ServerView RAID. 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
Description
Category
For Windows For Linux
Hard disk 150MB or more free space in the 150MB or more free space under /opt
installation partition of the OS
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 Mozilla Firefox 1.0.4 or later
SeaMonkey 1.0.3 or later
Java Java™ 2 Runtime Environment Standard Edition V1.5.0_06 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). For the list of logs notified by ServerView, see "Appendix A A List of ServerView
RAID Event Logs" (Jpg.138).
57
ServerView RAID Manager (when managed from 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 Server 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 need to 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. The two levels of access privileges are shown below:
User privilege
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 rebuild hard disks, or modify the parameters for ServerView RAID.
` Some operation such as rebuild cannot be performed with User privileges. We recommend that you
log in with User privileges unless you need to operate the array or modify the settings.
Administrator privilege
This privileges are for management, maintenance, and configuration of the array controllers, hard disks,
and logical drives. To use the Administrator privilege, log in to ServerView RAID Manager as a user
belonging to the "raid-adm" group or the Administrators group. In addition to the functions available
with User privileges, you can use all the other functions such as rebuilding hard disks, and changing the
hard disk status.
58
` 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 properly.
` Make sure to create the "raid-adm" group and name it "raid-adm".
4.1.4 Using ServerView RAID in Linux Environment
To use ServerView RAID in Linux environment, install device drivers for Linux and ServerView RAID.
When using the software in an RHEL-AS4 (EM64T) or RHEL-ES4 (EM64T) environment

` The Java plug-ins do not work on the servers with the RHEL-AS4 (EM64T) or RHEL-ES4 (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 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 Operation via Network" (Jpg.59).
4.1.5 Operation via Network
In a network environment, an array on a server 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 Monitoring and setting Server
Client PC the disk array
ServerView RAID
Service
Notifying
ServerView RAID Event
ServerView RAID Manager

Array Controller
59
` Each ServerView RAID Manager program can manage only one server.
When you want to 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 will not be blocked.
ServerView RAID uses the TCP port 3173.
Interaction with ServerView AlarmService

ServerView RAID logs the events of the array controllers in the OS event log on the server using
ServerView AlarmService. When you want to 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, the configuration is as follows:
Windows Server
or Windows Server or Linux Server
Monitoring and setting
Client PC the disk array
Notifying ServerView RAID

ServerView RAID Service
Event (SNMP Trap)
ServerView
AlarmService SNMP Service
ServerView RAID Notifying
Manager ServerView RAID Array Controller
OS Event Log Event (SNMP Trap)
ServerView
AlarmService
OS Event Log
` Make sure to install ServerView on the server.
60
4.1.6 When Using 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.
The configuration is as follows:
Server
ServerView RAID
Service
Notifying
㪪㪼㫉㫍㪼㫉㪭㫀㪼㫎㩷㪩㪘㪠㪛
Event
Management Client PC
or
Windows Server
Monitoring and
setting the disk array Array Controller
Monitoring and
setting the disk array
GAM Client Server
ServerView RAID Manager 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.
` 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 different versions of GAM Servers coexist, use the newer version of GAM Client than GAM Server.
61
4.2 Installing ServerView RAID

[Windows]
This section explains how to install ServerView RAID on a Windows server.
` ServerView RAID cannot be installed by overwriting an existing installation. Make sure to uninstall any
existing version of ServerView RAID before updating or reinstalling ServerView RAID.
` 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.
2 Before installing ServerView RAID, complete the following preparations:

• Make sure that ServerView is installed and working properly.
• Insert Array Controller Document & Tool CD provided with this product into the CD/DVD
drive.
• Exit all applications.
` Exit all applications 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 the [Start] button – [Run...]. Enter the following path and click [OK].
[CD/DVD drive]:\RAIDTOOL\SVRAID\Windows\install.bat
The message "Installation of ServerView RAID has started." is displayed at the command
prompt, and the installation of ServerView RAID begins.
4 When the message "Installation of ServerView RAID has finished." is displayed

at the command prompt, press the [Enter] key.
The command prompt window closes.
62
6 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" disk 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 [User must change password at
next logon].
Generally, [Password never expires] should be checked. Unless the account is configured as
above, you may be unable to log in to ServerView RAID Manager properly, because the pro-
gram 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.

` Make sure to create the "raid-adm" group. Make sure to create the group with the name "raid-
adm".
4.2.2 How to Uninstall ServerView RAID
Follow the procedure below to uninstall ServerView RAID.
` Do not uninstall ServerView RAID unless you need to update ServerView RAID or in other special
cases.
` Exit all programs before starting the uninstallation.

If uninstalling the software while Event Viewer, Services, or Computer Management is running,
the uninstallation will fail. Make sure to exit all the programs.
2 Click the [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 OS).
The message "Are you sure you want to remove ServerView RAID from your computer?" is
displayed.
63
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.
64
4.3 Starting and Exiting ServerView

RAID Manager
This section explains how to start and exit ServerView RAID Manager.
4.3.1 Preparations and Precautions for using ServerView

RAID Manager
Configure the necessary Web browser before using ServerView RAID Manager. Also, note the
following precautions:
z General precautions
• ServerView RAID Manager needs Java plug-in. Install Java on the server or client PC on which you
use ServerView RAID Manager. If Java is not installed, install Java by referring to "Installing Java™
2 Runtime Environment Standard Edition" under "Chapter 2 Installation" in "ServerView User's
Guide" on PRIMERGY Startup Disc.
• On servers with the RHEL-AS4 (EM64T) or RHEL-ES4 (EM64T) system, Java plug-ins do not
work. Therefore, when you want to manage the array controllers in an RHEL-AS4 (EM64T) or
RHEL-ES4 (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

• Set SSL enable.
Select [Tools] – [Internet Options] – [Advanced] – [Security], and set SSL 2.0 and SSL 3.0 enable.
• If you use Windows 2003 Internet Explorer as the Web browser, start the Web browser and add the
Web site as follows:
1. In Internet Explorer, select [Tools] – [Internet Options].
2. Click the [Security] tab and select [Local intranet] 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].
65
z When using Mozilla Firefox / SeaMonkey as your web browser

Select [Edit] – [Configuration], and set the following items enable in the configuration window:
• "SSL 2.0" and "SSL 3.0"
• "Enable Java"
4.3.2 Starting ServerView RAID Manager
Follow one of the procedures below to start ServerView RAID Manager:
z 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 From ServerView
Start ServerView RAID Manager with the RAID Manager linking function of ServerView.
For how to start ServerView RAID Manager from ServerView, see "RAID Manager Linking" in
"ServerView User's Guide" on PRIMERGY Startup Disc.
z From the server name or IP address

Start ServerView RAID Manager by directly specifying the host name or the IP address of the server.
Using this method, you can manage the array controllers on the server from a remote client PC.
1 Start the ServerView RAID Manager.

Starting from the [Start] button
1. Click [Start] button – [All Programs] (or [Program]) – [Fujitsu Siemens] –
[ServerView RAID Manager Start].
Starting by directly specifying the server name or IP address
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.
66
When ServerView RAID Manager is started, the login window appears.
` If you leave the Java startup popup window open for a long time when 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 Enter the user name in [Username].

• When logging in with Administrator privileges
Enter the user name that belongs to the "raid-adm" or Administrators group.
• When logging in with User privileges
Enter a user name that does not belong to the "raid-adm" or Administrators group.
3 Enter a password in [Password].
4 Click [Login].
The main window of ServerView RAID Manager appears.
67
` If you type the wrong password for logging in, you may not be able to enter the password
again. In this case, click [Username:], and then enter the user account and the correct pass-
word.
` 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.58).
` Do not change the status of the language selection button in the login window.
Leave it as .
4.3.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 Exit the Web browser.
68
4.4 ServerView RAID Manager

Window Layout
This section explains the windows, buttons, and menu items displayed when using
ServerView RAID Manager.
4.4.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 HDDs and LDs.
• [Settings] Tab
This tab displays the settings of the object. It also allows you to change the settings of the object.
• [Layout] Tab
This tab allows you to see the configuration of the object.
69
• [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
Menu bar provides menus for performing various function of ServerView RAID Manager.
For details on the ServerView RAID Manager menus, see "4.4.2 Menu Layout and Functions" (Jpg.71).
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.
` You can use the [Write access] mode only when you log in to ServerView RAID with Adminis-
trator privileges. When you log in with User privileges, you can only use the [Read only access]
mode.
J"4.3.2 Starting ServerView RAID Manager" (pg.66)
` 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 make the access mode automatically switched 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.4.3 Tree View Layout" (Jpg.73).
70
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 the completion
of the rebuild) occurs, ServerView RAID Manager is notified of it and displays it in the event window.
The following information is displayed.
table: Event window
Event Description
Severity 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
` For monitoring the array controllers, use the OS event log (the application log; Source: Fujitsu
ServerView Services).
ServerView RAID Manager displays only the last 100 events in the event window.
For example, if you start ServerView RAID Manager after a long interval, you may lose the events for
that period, because the old events are overwritten by new events.
4.4.2 Menu Layout and Functions
This section explains the layout and functions of ServerView RAID Manager menu items.
[File] menu
table: [File] menu

Menu Function
Exit 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 unavailable.
` The [Actions] menu is the same as the right-clicked menu when the object is selected in the tree view.
71
z When an array controller is selected
table: [Actions] menu (When an array controller selected)

Menu Function
Scan configuration Select this item to redetect all devices connected to the array controller.
Create logical drive Not supported. Do not use it.
Delete all logical drives Not supported. Do not use it.
Delete last logical drive Not supported. Do not use it.
Clear configuration Not supported. Do not use it.
z When a hard disk is selected
table: [Actions] menu (When a hard disk is selected)

Menu Function
Locate device It turns on the hard disk failure LED to indicate the drive's location.
Stop location It turns off the hard disk failure LED that was turned on with [Locate Device].
Create global hot spare Not supported. Do not use it.
Delete global hot spare Not supported. Do not use it.
Make online Not supported. Do not use it.
Make offline It changes 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 data loss.
Start rebuild Starts a rebuild ([Rebuild]) for the selected hard disk.
z When a logical drive is selected
table: [Actions] menu (When a logical drive is selected)

Menu Function
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 rebuild Starts a rebuild ([Rebuild]) for the selected logical drive.
z When a file log is selected
table: [Actions] menu (When a file log is selected)

Menu Function
Clear log Deletes the event log file.
Note:
` Do not use it. Event log files are used when analyzing failures.
If you delete event log files, the analysis may become difficult.
72
[Help] menu
table: [Help] menu

Menu Function
Info about ServerView RAID Displays the version information of ServerView RAID.
Contents and index Not supported.
4.4.3 Tree View Layout
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 the logical drive.
Server
Array Controller
Hard disk
Ports
Logical Drive
File Log
System Log
Plug-in
z Server
At the top of the tree, the names of the connected servers are displayed.
z Controller
The array controllers installed on the server are displayed.
Each controller number is shown in ( ).
z Port
The ports of an array controller are displayed.
Each port number is shown in ( ).
z Hard disk
The vendor names and product names of the hard disks connected to the array controller are displayed.
The device number of each hard disk is shown in ( ).
73
You can also see the status of each hard disk with icons.
table: hard disk status icon
Icon Displayed in Status Description
Gray Online Configuring an array and operating normally
(Operational)
White Unused Unused or available

(Available)
Gray Failure/Offline The hard disk configuring the array is being

with an "×" mark (Offline) failed, or unwritable
White Unrecognizable Not recognized, or failed.

(dotted frame) (Failed (Missing))
with "×"
Gray Rebuild Rebuild is in progress
(Rebuilding)
Gray Failure Prediction A failure is expected

with "!" (S.M.A.R.T. Error)
Yellow background Locating [Locate Device] function is running
` When you select the icon of each hard disk, more detailed information is displayed in the object
window. Note that you cannot see some information on unrecognizable hard disks.
For details, see "4.7.3 Checking Hard Disk Status" (Jpg.82).
` S.M.A.R.T. Error may appear with another status.
z Logical drive
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 with icons.
table: Logical drive status icons
Icon Status Description
Online Operating normally.
(Operational)
Critical Operating without redundancy

(Degraded)
Offline Not available

(Failed)
Locating [Locate Logical Drive] function is running on the logical drive.
` When you select the icon of each logical drive, more detailed information is displayed in the object
window. For details, see "4.7.4 Checking Logical Drive Status" (Jpg.84).
74
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.5 Setting ServerView RAID" (Jpg.76).
75
4.5 Setting ServerView RAID
This section explains how to change each parameter for event logging.
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.3 Starting and Exiting ServerView RAID Manager" (pg.65)
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 logging 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.77)
• When you set System log:
J" System log" (pg.78)
76
` Setting for ServerView RAID, the Multiplexer and the LSIStorelibIR-Plugin are not supported,
Do not use them.
5 Click [OK].
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 Sets event logging to the log file enable. Always set this
changed option Enabled.
Log level Information Cannot be Sets a priority level for events that execute logging.
changed 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 from the Information.
File name RAIDLog.xml Cannot be Log file name.
changed
File size 10 Cannot be Sets the log file size limit.
changed
Log method Rotation Cannot be Sets the method of log rotation.
changed
Max. save files 5 Default The maximum number of log files. We recommend that
you set this value equal to or greater than the default
value.
77
` The log files for ServerView RAID are stored as RAIDLog.xml (or RAIDLog<number>.xml) in the
following folders:
For Windows 2000 server/ C:\Program Files\Fujitsu Siemens\RAID\web\public\

Windows Server 2003
For Windows Server 2003 x64 C:\Program Files (x86)\Fujitsu Siemens\RAID\web\public\
For Linux /opt/SMAW/RAID/web/public/
Do not delete or edit the log files since they may be used for failure analysis. The available maximum
file size 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 Sets event logging to the OS event log enable.
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 whose settings you can change under System Log is "Source: ServerView RAID".
78
4.6 Rebuild
This section explains how to rebuild hard disks.
Rebuild is an operation to recover a logical drive in "Critical" status (Degraded) to "Online"

(Operational) status. For details on rebuild, see "1.3.2 Rebuild" (Jpg.16).
To manually execute a rebuild, follow the procedure below.
` 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.70).
` Just replacing a hard disk does not execute a rebuild. Make sure to perform the rebuild operation.
For how to replace the hard disk and perform a rebuild, see "Chapter 6 Replacing Hard Disk"
(Jpg.123).
1 Start the ServerView RAID Manager and log in with Administrator privileges.
2 In the tree view, right-click the replaced hard disk ( ), and [Start rebuild]
from the displayed menu.
A confirmation window appears.
3 Click [Yes].
When the rebuild starts, [Rebuilding] appears in [Activity] of the object window, and the
progress of the rebuild is displayed. When the progress bar reaches 100% and the window closes,
the rebuild is complete.
79
4.7 Checking Status [ServerView

RAID Manager]
The following information can be checked using ServerView RAID Manager.
• Information on events or errors that have occurred: "Appendix A A List of ServerView RAID Event
Logs" (Jpg.138)
• Server information: "4.7.1 Checking Server Condition" (Jpg.80)
• Array configuration or controller information: "4.7.2 Checking Array Controller Status" (Jpg.81)
• Hard disk information: "4.7.3 Checking Hard Disk Status" (Jpg.82)
• Logical drive information: "4.7.4 Checking Logical Drive Status" (Jpg.84)
• Information on tasks running in the background: "4.7.5 Checking Progress of Background Task"
(Jpg.86)
4.7.1 Checking Server Condition

Selecting a server name displayed on the top of the tree view displays information on the server that
ServerView RAID is installed in.
1 Start ServerView RAID Manager and log in.

2 Click the server you want to check in the tree view.

Detailed information on the selected server is displayed.
table: Detailed information on servers

Item Category Description
System 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.
80
table: Detailed information on servers

Operation System Vendor OS vendor name.
Version OS type and version.
Edition OS edition.
Service pack Service pack applied to OS.
Processor CPU type of OS.
architecture
[Note]: Not all of the items may be displayed depending on the OS types or settings.
4.7.2 Checking Array Controller Status
Selecting an array controller in the tree view displays detailed information on the array controller in the
object window.

2 Click the array controller ( ) you want to check in the tree view.
Detailed information on the selected array controller is displayed in the [General] tab.
81
table: Detailed information about array controllers

Adapter Name Model name of the array controller.
ID The number of the array controller.
Vendor Vendor name of the array controller.
Product Product name of the array controller.
Serial number Serial number of the array controller.
NVRAM size Size of the array controller NVRAM.
Firmware version Firmware version of the array controller.
BIOS version BIOS version of the array controller.
Driver name Driver name of the array controller.
Driver version Driver version of the array controlle.
PCI Location Bus Bus number for the array controller.
Function Function number for the array controller.
Device Device number for the array controller.
Ports Number Number of ports on the array controller.
Protocol Protocol supported by the array controller.
Devices Physical Logical maximum number of physical devices.
(max)
Logical Logical maximum number of logical devices.
Properties Auto rebuild Indicates whether auto rebuild is enabled or disabled.
Alarm present Indicates whether the alarm is present or not.
Correctable errors Not supported.
These counters indicate the number of recovery attempts
Uncorrectable errors
made by the array controller for temporary or minor
errors. They can be ignored unless the hard disk receives a
failure status.
Coercion mode Indicates whether or not coercion of the hard disk capacity
is performed.
Status Displays the current status of the array controller.
Additional status Displays the details of the current status of the array
controller
` The [Background activities] tab is displayed if a background task is running.

` Regarding the information displayed in the [Background activities] tab, see " Checking with
Background activities from array controller" (Jpg.87).
4.7.3 Checking Hard Disk Status
Detailed information on hard disks connected to the controller is displayed in the object window.

82
2 Click the hard disk ( ) you want to check in the tree view.
Detailed information about the selected hard disk is displayed.
table: Detailed information on hard disks

Disk Name Hard disk model name. The number in parentheses is the device
number of the hard disk.
Device number Device number of the hard disk.
Slot Number of the slot where the hard disk is installed.
SAS address 00 SAS address of the hard disks.
Vendor Hard disk vendor name.
Product Hard disk product name.
Type Protocol type of the hard disk.
Serial number Serial number of the hard disk.
Firmware version Version of the hard disk's firmware.
Transfer speed Ttransfer speed between the hard disk and the controller.
Transfer width Data transfer width of the hard disk is displayed.
Physical size Physical capacity of the hard disk.
Config. size Available hard disk capacity when connected to the array
controller.
Foreign configuration Not supported.
S.M.A.R.T errors Counts S.M.A.R.T. failure predictions for the hard disk.
Activity Displays running tasks for the hard disk.
• Idle: No running tasks.
• Rebuilding: A rebuild is in progress.
Status Displays current status of the hard disk.
83
4.7.4 Checking Logical Drive Status
Detailed information on logical drives is displayed in the object window.

You can change the displayed information by switching the tabs at the top of the object window.

2 In the tree view, click the logical drive you want to check ( ).
Detailed information about the selected logical drive is displayed in the object window.
3 Click the tab you want to check in the object window.

When you select the [General] tab:
84
table: Detailed information about logical drives

Logical Drive Name Logical drive name.
Logical drive number Logical drive number.
RAID level RAID level set for the logical drive.
Stripe size Striping size used by the logical drive.
Logical size Logical size of the logical drive.
Physical size Physical size of the logical drive.
Activity 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.7.5 Checking Progress of Background Task"
(Jpg.86).
Status Current status of the logical drive.
Cache Write mode Current write policy status of the logical drive.
Read mode Not supported.
Disk cache mode
Misc. Operating system Overview of HDD devices used in the OS.
properties device name
When you select the [Layout] tab:
table: Logical drive layout information

Overview Disk Displays the hard disks composing the target logical drive.
Used capacity Displays the capacity of hard disks used in the target logical drive.
Partitions Displays the overview of HDD devices used in the OS
85
4.7.5 Checking Progress of Background Task
ServerView RAID Manager allows you to view the progress of rebuild 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.
table: Background task
Background task Activities How to check background tasks
Rebuild Rebuilding • With detailed information on logical drives
• With background activities from array controllers
• With detailed information on hard disks
Checking with detailed information on logical drives

You can check the background tasks runnning on the selected logical drive.

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 running in [Activity].
86
Checking with Background activities from array controller

You can check all the background tasks runnning in the selected array controller.

2 In the tree view, click the controller ( ).
3 Click the [Background activities] tab.

The logical drives where background tasks are runnning are displayed in [Logical Drive], and
you can check the type and progress of the background tasks runnning in [Activity].
` When you click the button ( ) to the right of the information for each hard disk or logical
drive, the target hard disk or logical drive is selected in the tree view, so that you can view
detailed information about the hard disk or logical drive.
` During rebuild, both the progress for the logical drive and the hard disk are displayed.
87
Checking with detailed information on hard disk

You can check rebuild running on the selected hard disk.

2 In the tree view, click a hard disk ( ).
3 Click the [General] tab.

You can check the progress of the rebuild being executed in [Activity].
How to calculate estimated time for background task

For on-going background tasks, you can figure out approximate time a task will take referring to the
progress bar.
1 Measure the period of time taken for a progress bar to advance 1%.
2 Calculate the approximate time that the task takes from start to finish, using the
following formula.
(Period measured in Step 1) × 100
` 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.
88
Chapter 5
Management [GAM]
This chapter explains the overview and

requirements of GAM, and how to install and use
it.
5.1 Overview and Requirements for GAM . . . . . . . . . . . . . . . 90

5.2 Installing GAM ［Windows］ . . . . . . . . . . . . . . . . . . . . . . 97
5.3 Starting and Exiting GAM . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4 GAM Window Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.5 Server Group and Server Setting . . . . . . . . . . . . . . . . . . . 111
5.6 Viewing Information [GAM] . . . . . . . . . . . . . . . . . . . . . . . 112
5.7 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
89
5.1 Overview 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 the logical drive 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 Array Controller Document & Tool CD. If by mistake you have installed ServerView RAID rather
than GAM, uninstall ServerView RAID, and then install GAM. 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.
90
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
Appication 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-specified 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.
GAM Client (when managed from 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 Contents
Network Network connection with available TCP/IP
Input device A mouse or other pointing devices
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 Server Service Pack 4 or later
Windows 2000 Professional Service Pack 4 or later
91
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 a password 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 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.
92
5.1.4 Using GAM in Linux Environment
To use GAM in a Linux environment, you need to install device drivers and GAM.
For using Linux, see the Linux manual 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 Linux Server
Client PC Monitoring and Setting
GAM
GAM Server
Notifying GAM Event
GAM Client
Array Controller
` On Linux servers, install GAM Server and edit the configuration file to set the GAM event recipient and
enable storing event logs after the installation. For details, see the Linux manual on the URL sited
above.
the port used by the GAM protocol is not blocked.
GAM uses the TCP port 157 and 158.
93
5.1.5 Using GAM in 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 that 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 Linux Server
Client PC
GAM Server
Notifying GAM Event
GAM Client Array Controller
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
11 in "5.2.1 How to Install GAM" (Jpg.97).
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 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 different versions of GAM Servers coexist, use the newer version of GAM Client than GAM Server.
94
Interaction with ServerView AlarmService

The following figure shows the interaction with ServerView AlarmService when GAM Client on the
other Windows servers (client) manage 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 Windows Server or Linux Server
Client PC
GAM Server
Notifying GAM
Event (SNMP Trap)
ServerView
GAM Client AlarmService 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.
95
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
ServerView RAID
Service
Notifying
㪪㪼㫉㫍㪼㫉㪭㫀㪼㫎㩷㪩㪘㪠㪛
Event
Management Client PC
or
Windows Server
Monitoring and
setting the disk array Array Controller
Monitoring and
setting the disk array
GAM Client Server
ServerView RAID Manager 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.
96
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 Users Guide".
5.2.1 How to Install GAM
Follow the procedure below to install GAM.
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 "Array Controller Document & Tool CD" provided with this product into the CD/DVD
drive.
• Exit all applications.
` Exit all applications 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 the [Start] button – [Run...]. Enter 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.
97
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 is displayed.
` 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 is displayed, click the [×] button to close the command
prompt. After uninstalling GAM Client and GAM Server, perform the installation again.
98
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 unin-
stalled 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.
99
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

If uninstalling the software while [Event Viewer] or [Computer Management] is running, the
uninstallation will fail. Make sure to exit all programs.

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].
6 When the uninstallation is finished, click [OK].
100
Uninstalling GAM server

If uninstalling the software while Event Viewer or Computer Management is running, the unin-
stallation will fail. Make sure to exit all programs.

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].
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.xxxx from
your computer?" appears.
8 Click [Yes].
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 v3.00.0000
from your computer?" appears.
10 Click [Yes].
101
5.3 Starting and Exiting GAM
This section explains how to start and exit GAM.
5.3.1 Starting GAM and Signing On
GAM requires user authentication to limit the availability of functions according to uses. 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.5 Server Group and Server Setting" (Jpg.111) 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 the [Start] button – [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.
3 Sign on to GAM.
1. Enter your user name.
102
• When signing on with User privileges

Enter a user name in [Username].
• When signing on with Administrator privileges
Enter "gamroot" in [Username].
2. Enter 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.92).
5.3.2 Exiting GAM
To exit GAM, click [Exit] from [File] in the GAM menu bar.
103
5.4 GAM Window Layout

The following provides a description of the windows, buttons, and menu items
displayed when using GAM.
5.4.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.4.2 Menu Layout and Functions" (Jpg.106).
Toolbar
Buttons for frequently used GAM functions.
For details on the toolbar, see "5.4.3 Toolbar Icons" (Jpg.108).
Server group selection box

The server group names which are registered in GAM Client are displayed. Clicking ▼ switches the
server groups to be managed.
104
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. Integrated
Mirroring SAS) 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 is displayed 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
105
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 Details
Event ID 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.
5.4.2 Menu Layout and Functions
This section describes the function of the GAM menu items.
[File] menu
table: [File] menu
Menu Function
Open Configuration Not supported.
Save Configuration Not supported.
Clear Configuration Not supported.
106
[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 Not supported.
Background Initialize Status Not supported.
Rebuild Status Shows the rebuild progress.
This can only be selected while a rebuild is in progress.
Make Data Consistent Status Not supported.
Expand Capacity Status Not supported.
Patrol Read Status Not supported.
Error Table Not supported.
[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 Not supported..
Initialize Logical Drives Not supported.
Controller Information Displays the main information for the currently selected array controller.
Enclosure Information Not supported.
Controller Options Not supported.
Physical Device Options Not supported.
Intelligent BBU Not supported.
Scan Devices Redetects the hard disks connected.
Advanced Functions Not supported.
Settings Not supported.
107
table: [Administration] menu

Menu Function
Alarm Sound Not supported.
Consistency Check with Not supported.
Restoration
5.4.3 Toolbar Icons
The toolbar icons at the top of the [GAM] window enable you to start up frequently used functions.
table: Toolbar icons

Icon Function
Not supported.
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.
Not supported.
Opens the [Sign On] window. Functions in the same manner as when [Sign On] is selected from the
[Administration] menu.
Not supported.
Displays Help.
108
5.4.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.107). If the [Sign On] window opens, sign on referring to "5.3.1 Starting GAM and Signing On"
(Jpg.102).
The following window appears.
The [Controller View] window shows the information below regarding the controller currently selected
in the [Controller Selection] box.
109
z Hard disks
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 is displayed as follows.

table: Hard disk status icon
Icon Color Status Description
Green Online Normal
(OnLine)
Red Failure / Offline The hard disk has a failure, cannot be
(Dead / Offline) recognized, or cannot be read and written.
Yellow Rebuild Rebuild in progress
(Rebuilding)
Yellow Failure expected Failure expected
(Critical)
Not applied Unused Unused or available
(Unconfigured)
` Double-click the icon for each hard disk to see more detailed information. For more details, see "5.6.3
Viewing Hard Disk Information" (Jpg.115).
` If a hard disk is in an unrecognizable state, detailed information may not be displayed even when
double-clicking its hard disk icon.
z Logical drives
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 is displayed as follows.

table: Logical drive status icon
Icon Color Status Description
Green Online Normal
Yellow Critical Operating without redundancy
Red Offline Not available
` Double-click the icon of each logical drive to see more detailed information. For more details, see "5.6.4
Viewing Logical Drive Information" (Jpg.118).
110
5.5 Server Group and Server Setting
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 Enter a name for the server group to be added using the [Adding Item] window.
3 Click [OK].
The added server group name is displayed in the [Server Groups] area.
4 Select the added server group and click the [Add] button below the [Servers] area.
The [Adding Item] window is displayed.
5 Enter 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.
7 Click [OK] to close the [Define Server Groups] window.

Confirm 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.107).
` The maximum number of the servers to be monitored that can be set is 100.
111
5.6 Viewing Information [GAM]

The following information can be viewed using GAM.
• Information about events or errors that have occurred: "Appendix B A List of GAM Event Logs"
(Jpg.158)
• Array configuration or controller information: "5.6.2 Viewing Array Controller Information"
(Jpg.114)
• Hard disk information: "5.6.3 Viewing Hard Disk Information" (Jpg.115)
• Logical drive information: "5.6.4 Viewing Logical Drive Information" (Jpg.118)
• Information about tasks running in the background: "5.6.5 Checking Progress of Background Tasks"
(Jpg.120)
5.6.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 such as
the completion notice of the rebuild) 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 A List of GAM
Event Logs" (Jpg.158).
` To write events or errors on the event logs in the OS, you need to install ServerView. See the
"ServerView User's Guide" bundled with ServerView for the installation and settings.
` 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:
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
` 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.
112
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, C:\Program Files\Mylex\Global Array Manager Client\gam2cl.log

Windows 2000 Server
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.4.1 Startup Window
Layout and Functions" (Jpg.104).
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 is displayed.
` Click [OK] to close the window.
113
5.6.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.4.4 Starting Controller View and the Window Layout" (Jpg.109).
Displaying detailed information about the array controller
1 Start up GAM and sign on.

J"5.3 Starting and Exiting GAM" (pg.102)
2 Select [Controller Information] from the [Administration] menu.

The [Controller Information] window appears.
` Click [Close] to close the window.
114
Detailed information about the array controller

table: Detailed information about the array controller
Item Description
Model The model name of the array controller.
Firmware Version The version of the array controller's firmware.
Intelligent BBU Not supported.
Package Version Not supported.
BIOS Version The version of the array controller's BIOS.
Cache Size Not supported.
FlashROM Size Not supported.
Bus Type The type of the host-side bus.
Channels Not supported.
Physical Devices The number of hard disks connected to the array controller.
Max. Physical Devices Not supported.
Logical Drives The number of the logical drives controlled by this array controller.
Max. Logical Drives Not supported.
Bus The bus number for the array controller.
Device # The device number for the array controller.
IRQ The IRQ number.
5.6.3 Viewing Hard Disk Information

Using Controller View, you can view detailed information about the hard disks connected to the
controller.

2 Select [Controller View] from the [View] menu.

` Each drive column indicates the hard disks connected to each enclosure or to each channel of
the controller.
115
3 Double-click the icon for the hard disk to see the information about it.
` The Channel, Target and Lun information displayed in the title bar is not supported.
Detailed information about hard disks

table: Detailed information about hard disks
Item Description
Vendor Information about the hard disk vendor.
Product Model number 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 / Not supported.
CmdQue / ANSI Version
Serial Serial number of the hard disk.
Slot The number of the slot where the hard disk is installed.
Nego. Transfer Speed Not supported.
Nego. Bus Width Not supported.
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 disks" (Jpg.110).
116
table: Detailed information about hard disks

Item Description
Soft Errors / Parity Errors / Not supported.
Hard Errors / Misc Errors (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 a
rebuild of the hard disk.J"5.7 Rebuild" (pg.121)
• [Make Ready] button
Not supported.
` Do not use the [Make Ready] button unless you are instructed to do so by your maintenance
engineer.
• [Make Offline] button

Forcibly changes the status of the hard disk to "Offline".
` Do not use the [Make Offline] button unless you are instructed to do so by your maintenance
engineer.
• [Make Online] button

Not supported.
• [Locate] button
Blinks the failure LED of the hard disk to indicate the drive's location.
• [ReplaceMissing] button
Not supported.
• [Close] button
Closes the detailed hard disk information window.
117
5.6.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.


3 Double-click the icon of a logical drive to see the information about it.
Detailed information about the selected logical drive is displayed.
` The logical drive number is displayed on the title bar.

118
Detailed information about logical drives

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 drives" (Jpg.110).
Write Cache Not supported.
Used Array Capacity Displays the ratio of the logical drive's capacity to the hard disk's total 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.
• [Close] button
Closes the detailed logical drive information window.
119
5.6.5 Checking Progress of Background Tasks
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.
Rebuild Status
When a 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.
` Do not cancel the rebuild.
Calculating the approximate time needed for a background task

For rebuild, you can figure out approximate time that the task takes from start to finish from the pace of
the progress bar.
1 Measure the period of time required for the progress bar to advance 1%.
2 Calculate the approximate time that the task takes from start to finish, using the
following formula.
(Period measured in Step 1) × 100
` 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.
120
5.7 Rebuild
To execute a rebuild manually, follow the procedure below.
` Just replacing the hard disk does not execute a rebuild. Make sure to perform the rebuild operation.
For how to replace the hard disk and how to perform a rebuild, see "Chapter 6 Replacing Hard Disk"
(Jpg.123).
1 Start up GAM and sign on with Administrator privileges.


3 Double-click the icon of a hard disk with "Failure" state ( ) in the

[Controller View] window.
The detailed information about the hard disk is displayed in the [Disk Device Information]
window.
4 Click [Rebuild].
The [Rebuild Status] window appears and a 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 Click [OK] to exit.
121
122
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] . . . . . . . . . 124

6.2 How to Replace Hard Disk [GAM] . . . . . . . . . . . . . . . . . . 131
123
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 the ServerView RAID Manager and log in.

2 Verify that the hard disk icon is displayed 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.
Verify the hard disk number here.

In this case, it is "2".
` If there are any hard disks being rebuilt (indicated with ), wait until the rebuild is fin-
ished. After the rebuild has finished, check the hard disk status again.
3 To get detailed information, refer to the [General] tab of the object window.
If "S.M.A.R.T. Error" is displayed in the [Status] field, you will be informed of a failure
prediction warning (S.M.A.R.T.).
` The detailed information may not be displayable depending on the failure condition of the hard
disk.
124
4 If there is a failed hard disk or a hard disk that is predicted to fail, replace it
using the following procedures.
If there is a failed hard disk
See "6.1.2 Replacing Failed Hard Disk [ServerView RAID]" (Jpg.125) to replace the hard disk.
If there is a hard disk that is predicted to fail
See "6.1.3 Preventive Replacement of Hard Disk [ServerView RAID]" (Jpg.127) to replace the
hard disk with the failure prediction warning.
When a hard disk failed and another is predicted to fail

` First, replace the failed hard disk and perform a rebuild. After that, confirm that the failure indi-
cation of the replaced hard disk has disappeared, i.e. that the logical drive status is "Opera-
tional", 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 BIOS Utility. Start BIOS Utility and check the [View
Array] view. For more details, see "2.3.2 Viewing Information on Logical Drive and Hard Disk"
(Jpg.31).
6.1.2 Replacing Failed Hard Disk [ServerView RAID]
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" located on "PRIMERGYStartup 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 hard disks while the server is turned on, except to replace a failed drive.
1 Confirm the drive number of the failed hard disk and locate the drive.
Adding one to the slot number identified in steps 1 to 2 in J"6.1.1 Checking Hard Disk to be
Replaced [ServerView RAID]" (pg.124) results in the bay number.
Example: If the slot number is 2, the location of the drive is bay 3.
2 Confirm that the hard disk failure LED is lit for the bay corresponding to the
failed hard disk on the server.
For the locations of the bays and of the hard disk failure LED, see "User’s Guide" located on
"PRIMERGY Startup Disc supplied with the server.
125
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" located on "PRIMERGY Startup Disc
` 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 bay.
6 Install a new hard disk at the same location where the failed hard disk was
previously installed.
7 In the tree view, select the newly installed hard disk ( ) in Degraded status,
right-click, and then click [Start rebuild] from the displayed menu.
8 Click [Yes].
A rebuild is automatically started.
When the rebuild is started, the hard disk's failure LED that was lit starts flashing, and then turns
off when the rebuild is complete.
After the rebuild is completed, in the tree view of the ServerView RAID Manager, select the icon
of the replaced hard disk to verify that "Operational" is displayed 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 Serv-
erView RAID Manager, the rebuild is complete.
("X" indicates the number of the hard disk where the rebuild was performed.)
• In the Event Window
ID: 10267
Event: <Type and number of the controller>: Rebuild complete
on disk X
• For OS Event Log
Source : Fujitsu ServerView Services

Type : Information
Event ID : 1
Description: <Type and number of the controller>: Rebuild
complete on disk X
126
` For the approximate time to complete the rebuild, see " Estimated time for rebuild" (Jpg.16)
or " How to calculate estimated time for background task" (Jpg.88).
` If the system restarts or shuts down during rebuild, the rebuild is resumed from where it was
stopped the next time.
6.1.3 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.
Error", it means that the drive may fail in the near future. If the hard disk status becomes "S.M.A.R.T.
Error", replace that drive as a preventive measure.
` For how to remove and install hard disks, see "User’s Guide" located on "PRIMERGY Startup Disc
a rule.
` We recommend that you back up the data before performing preventive replacement of a hard disk.
` When two or more hard disks are predicted to fail, replace one drive at a time.
` If any hard disk is being rebuilt, wait until the rebuild process is finished.
Preventive replacement of hard disk with RAID 1 configuration

If the target hard disk for the preventive replacement belongs to a RAID 1 logical drive, follow the
procedure below as a preventive measure.
1 Using ServerView RAID Manager, check the drive number of the hard disk that
has a failure prediction warning ( ) and locate that drive.
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.124) results in the bay number.
` If there is a failed hard disk at this point, replace that drive first, referring to "6.1.2 Replacing
Failed Hard Disk [ServerView RAID]" (Jpg.125). If any hard disk is being rebuilt, wait until the
rebuild process is finished.
127
2 In the tree view, select the hard disk ( ) with a failure prediction warning.
Detailed information about the selected hard disk is displayed in the object window.
If "S.M.A.R.T. Error" is displayed in the [Status] field, you will be informed of a failure
prediction warning (S.M.A.R.T.).
3 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 to flash or light up.
` The hard disk confirmed here has received a failure prediction warning (the target hard disk for
preventive replacement).
We recommend that you put some kind of mark on this drive to identify it.
4 After checking the location, in the tree view, select the target hard disk, right-
click, and then click [Stop location] from the displayed menu.
The failure LED turns off.
5 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?
6 Enter "yes" and click [OK].
128
7 Verify that the [Status] field for the target hard disk has changed to "Offline" in
the object window.
8 Pull out the hard disk identified in Step 3 about an inch (1 to 3 cm) to disconnect
it from the connector.
` Do not remove a hard disk that is in good condition. Doing so may cause loss of data.
` The hard disk failure LED for the drive to be replaced is now lit.
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
12 In the tree view, select the newly installed hard disk ( ) in Degraded status,
right-click, and then click [Start rebuild] from the displayed menu.
13 Click [Yes].
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 verify that "Operational" is displayed in the [Status] field of the
object window.
129
` When the following event is recorded in the OS event log, or in the Event Window of the Serv-
erView RAID Manager, the rebuild is completed.
(“X” indicates the number of the hard disk where the rebuild was performed.)
• In the Event Window
ID: 10267
Event: <Type and number of the controller>: Rebuild complete
on disk X
Source : Fujitsu ServerView Services

Type : Information
Event ID : 1
Description: <Type and number of the controller>: Rebuild com-
plete on disk X
or " How to calculate estimated time for background task" (Jpg.88).
130
6.2 How to Replace Hard Disk [GAM]
This section explains maintenance related issues, such as hard disk replacement in
GAM.
6.2.1 Checking Hard Disk to be Replaced [GAM]
Check the slot number of the target hard disk before replacing it.


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 fin-
ished. After the rebuild has finished, check the hard disk status again.
4 Double-click the hard disk icon to confirm detailed information.

If the [PFA Count] in the [Device Errors] field is displayed as "Found", a failure prediction
warning (S.M.A.R.T.) has been detected.
` The detailed information may not be displayable depending on the failure condition of the hard
disk.
131
5 If there is a failed hard disk or a hard disk that is predicted to fail, replace it
using the following procedures.
If there is a failed hard disk
See "6.2.2 Replacing Failed Hard Disk [GAM]" (Jpg.132) 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.134) to replace the hard disk
with the failure prediction warning.
When a hard disk failed and another is predicted to fail

` First, replace the failed hard disk and perform a rebuild. After that, confirm that the failure indi-
cation 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 BIOS Utility. Start BIOS Utility and check the [View
Array] view. For more details, see "2.3.2 Viewing Information on Logical Drive and Hard Disk"
(Jpg.31).
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.
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 drive.
1 Confirm the slot number of the failed hard disk and locate the drive.
Replaced [GAM]" (Jpg.131) results in the bay number.
2 Confirm 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" located on
132
3 Pull out the failed hard disk about an inch (1 to 3 cm) to disconnect it from the
connector.
5 Pull out the failed hard disk completely from the hard disk bay.
6 Install a new hard disk at the same location where the failed hard disk was
7 Double-click the icon for the newly installed hard disk on the [Controller View]
window.
The [Disk Device Information] window appears.
8 Click [Rebuild].
When the rebuild is finished, make sure that the status of the replaced hard disk has changed to
"Online" in the [Disk Device Information] window (Jpg.115) 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.
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
completed.
or " Calculating the approximate time needed for a background task" (Jpg.120).
133
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 drive may fail in the near future. If the hard disk status becomes "Critical", replace that
drive as a preventive measure.
a rule.
` We recommend that you back up the data before performing preventive replacement of a hard disk.
` If any hard disk is being rebuilt, wait until the rebuild process is finished.
Preventive replacement a hard disk with a RAID 1 configuration

If the target hard disk for the preventive replacement belongs to a RAID 1 logical drive, follow the
procedure below for the preventive replacement.
1 Using GAM, check the slot number of the hard disk with a failure prediction
warning ( ) and locate the drive.
Replaced [GAM]" (Jpg.131) results in the bay number.
` If there is a failed hard disk at this point, replace that drive first, referring to "6.2.2 Replacing
Failed Hard Disk [GAM]" (Jpg.132). If any hard disk is being rebuilt, wait until the rebuild pro-
cess is finished.
134
2 Double-click the icon of the hard disk with the failure prediction warning.
Make sure that its [Status] is indicated as "Critical".
3 Click [Locate] and check the location of the target hard disk on the server.
The hard disk failure LED corresponding to the hard disk starts to flash or light up.
For the location of the bays and of the hard disk failure LED, see "User’s Guide" located on
` The hard disk confirmed here has received a failure prediction warning (the target hard disk for
preventive replacement).
We recommend that you put some kind of mark on this drive to identify it.
4 Click [OK] when the location is confirmed.

The failure LED turns off.
5 Click the [Make Offline] button. When the [WARNING] window appears, enter
[YES] and click [OK].
6 Confirm that the following log entry is displayed in the GAM Log Information
Viewer.
Event ID : E-50
Description: Physical disk status changed to offline
7 Pull out the hard disk identified in Step 3 about an inch (1 to 3 cm) to disconnect
it from the connector.
135
` Do not remove a hard disk that is in good condition. Doing so may cause loss of data.
` Although a pop-up of "Error returned by firmware." may appear when the hard disk is replaced
during executing the Locate function, the operation is not affected. Click [OK] to close the pop-
up window.
9 Pull out the hard disk that is predicted to fail completely from the hard disk bay.
10 Install a new hard disk at the same location where the removed hard disk was
11 Double-click the icon for the newly installed hard disk on the [Controller View]
window.
The [Disk Device Information] window appears
12 Click [Rebuild].
When the rebuild is finished, make sure that the status of the replaced hard disk has changed to
"Online" in the [Disk Device Information] window (Jpg.115) of GAM.
` If the [Controller View] display is not updated, execute [Scan Devices] from the [Administration]
menu.
136
Appendix
This section explains the event codes for

ServerView RAID and GAM, and the notes on
the array controller usage.
A A List of ServerView RAID Event Logs . . . . . . . . . . . . . . . 138

B A List of GAM Event Logs . . . . . . . . . . . . . . . . . . . . . . . . 158
C Notes on Usage for the Array Controller . . . . . . . . . . . . . . 171
137
Appendix
A A List of ServerView RAID Event

Logs
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 log also records the location of the device. Types of locations are as follows.
table: Meaning of event log strings
[Note 1]
Character String Meaning
Server %s Name of the server
Adapter %s Type and number of the controller
As for this product, the names are "LSI 1068SASIME ...", "LSI 1064ESASIME ...",
and "RAID 0/1 SAS 4P".
Disk %s Number of the hard disk
Logical Drive %s 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.
The relationship between the severity of each ServerView RAID event (SNMP TRAP) and the type of
event log displayed in the event window of the ServerView RAID Manager is as follows:
table: Event log types and descriptions
Severity with the
Severity Description OS Event Log Type
ServerView RAID Manager
CRITICAL Severe error Error Error
MAJOR Error Error Error
MINOR Warning Warning Warning
Information (No
INFORMATIONAL Informational Information
action required)
138
table: A list of ServerView RAID event logs

ID Severity Log Entry Description Recovery Action
1 INFORMA Undefined event (Server %s) An unknown event has If there is an error before
TIONAL occurred. or after an event, perform
the proper recovery action
for that error.
10000 INFORMA Unknown event (Server %s) An unknown event has If there is an error before
TIONAL occurred. or after an event, perform
the proper recovery action
for that error.
If there is no error, no
action required.
10002 MINOR Write access to ServerView Write Access mode has None.
RAID revoked by user %s been canceled.
(%s) (Server %s) Another client has
obtained Write Access
mode.
10017 INFORMA Adapter %s: SCSI sense data A hard disk reported sense There is no problem as
TIONAL on disk (%s) available: %s information. long as the target hard disk
(Server %s) is online because the
controller has performed a
recovery.
10021 INFORMA Adapter %s: Disk (%s) The hard disk status is None.
TIONAL marked online (Server %s) now online.
10022 CRITICAL Adapter %s: Disk (%s) The hard disk status is None.
marked offline (Server %s) now offline.
10023 MAJOR Adapter %s: Disk (%s) timed The hard disk has been Check that the hard disk is
out (Server %s) timed out. connected properly.
If the hard disk has failed,
replace it and perform a
rebuild.
10024 INFORMA Adapter %s: Global hot spare A global hot spare has None.
TIONAL created on disk (%s) (Server been created.
%s)
10025 MINOR Adapter %s: Global hot spare A global hot spare has None.
deleted on disk (%s) (Server been disabled.
%s)
10026 INFORMA Adapter %s: Dedicated hot A dedicated spare disk Dedicataed spare disks are
TIONAL spare created on disk (%s) drive has been created. not supported. Make sure
(Server %s) to properly set a spare
disk.
10027 MINOR Adapter %s: Dedicated hot The dedicated spare disk None.
spare deleted on disk (%s) has been disabled.
(Server %s)
10028 INFORMA Adapter %s: Disk (%s) The hard disk status is None.
TIONAL marked available (Server %s) now available.
10029 INFORMA Adapter %s: Rebuild on disk Rebuilding of the hard None.
TIONAL (%s) started (Server %s) disk has started.
139
Appendix

10030 MAJOR Adapter %s: Rebuild on disk Rebuilding the hard disk Check the present status
(%s) failed (Server %s) has failed. of the logical drive.
• If in the critical state:
Replace the failed hard
disk and perform a
rebuild again.
• If in the offline state:
Contact an office listed
in the "Contact
Information" of the
"Start Guide".
10032 INFORMA Adapter %s: New disk (%s) A new hard disk has been None.
TIONAL detected (Server %s) detected.
10033 MINOR Adapter %s: Disk (%s) A hard disk was removed. Replace and rebuild the
removed (Server %s) hard disk.
10038 MAJOR Adapter %s: Error on disk An error has been detected Replace the hard disk
(%s) detected (Server %s) on a hard disk. failure, and perform a
rebuild.
10039 INFORMA Adapter %s: Channel %s was A channel has been reset. None.
TIONAL reset (Server %s)
10040 MAJOR Adapter %s: Retry I/O on I/O retry for the hard disk There is no problem as
disk (%s) (Server %s) has been performed. long as there is no hard
disk failure, because the
firmware has performed a
recovery.
10041 MAJOR Adapter %s: ECC Error on An ECC error on the hard There is no problem as
disk (%s) (Server %s) disk has been detected. long as the target hard disk
is online because the
recovery.
10043 MAJOR Adapter %s: Media error on A media error has been There is no problem as
disk (%s) (Server %s) detected on the hard disk. long as the target hard disk
is online because the
recovery.
10044 MINOR Adapter %s: S.M.A.R.T. A failure has been Replace the hard disk as a
warning on disk (%s) (Server predicted for a hard disk. preventive measure.
%s)
10045 MINOR Adapter %s: S.M.A.R.T. A failure has been Replace the hard disk as a
error on disk (%s) (Server predicted for a hard disk. preventive measure.
%s)
10055 INFORMA Adapter %s: Rebuild started Rebuilding of the logical None.
TIONAL on logical drive %s (Server drive has started.
%s)
10056 INFORMA Adapter %s: Rebuild finished Rebuilding of the logical None.
TIONAL on logical drive %s (Server drive has been completed.
%s)
140

10057 MAJOR Adapter %s: Rebuild failed Rebuilding of the logical Check the present status
on logical drive %s (Server drive has failed. of the logical drive.
%s) • If in the critical state:
Replace the failed hard
disk and perform a
rebuild again.
• If in the offline state:
Contact an office listed
in the "Contact
Information" of the
"Start Guide".
10058 MINOR Adapter %s: Rebuild aborted Rebuilding of the logical Perform the rebuild again.
on logical drive %s (Server drive has been aborted.
%s)
10059 INFORMA Adapter %s: Rebuild paused Rebuilding of the logical None.
TIONAL on logical drive %s (Server drive has paused.
%s)
10078 MAJOR Adapter %s: Logical drive The logical drive status is Replace and rebuild the
%s degraded (Server %s) now degraded. failed hard disk.
10079 CRITICAL Adapter %s: Logical drive The logical drive status is Contact an office listed in
%s failed (Server %s) now offline. the "Contact Information"
of "Start Guide".
10080 INFORMA Adapter %s: Logical drive The logical drive has been None.
TIONAL %s created (Server %s) created.
10081 MINOR Adapter %s: Logical drive A new logical drive has None.
%s deleted (Server %s) been deleted.
10082 INFORMA Adapter %s: Logical drive The logical drive status is None.
TIONAL %s operational (Server %s) now online.
10085 INFORMA Adapter %s: Initialization Foreground initialization None.
TIONAL started on logical drive %s of the logical drive has (Foreground Initialization
(Server %s) started. is not supported.)
10086 INFORMA Adapter %s: Initialization Foreground None.
TIONAL finished on logical drive %s Initialization of the logical (Foreground Initialization
(Server %s) drive has been completed. is not supported.)
10087 INFORMA Adapter %s: BGI started on Background initialization None.
TIONAL logical drive %s (Server %s) of the logical drive has
started.
10088 INFORMA Adapter %s: BGI finished on Background initialization None.
TIONAL logical drive %s (Server %s) of the logical drive has
been completed.
10089 MINOR Adapter %s: BGI canceled Background initialization None. (Background
on logical drive %s (Server of the logical drive has initialization resumes
%s) been canceled. automatically after a
certain period of time.)
10090 MINOR Adapter %s: Initialization Foreground initialization None.
canceled on logical drive %s of the logical drive has (Foreground Initialization
(Server %s) been canceled. is not supported.)
10095 INFORMA Adapter %s: Alarm enabled An alarm has been An alarm is not supported.
TIONAL (Server %s) enabled. Check array controller
settings.
141
Appendix

10096 MINOR Adapter %s: Alarm disabled An alarm has been None.
(Server %s) disabled.
10108 INFORMA Adapter %s: Automatic Auto Rebuild has been None.
TIONAL rebuild enabled (Server %s) enabled.
10109 INFORMA Adapter %s: Automatic Auto Rebuild has been None.
TIONAL rebuild disabled (Server %s) disabled.
10114 INFORMA Adapter %s: BIOS enabled BIOS has been enabled. None.
TIONAL (Server %s)
10115 INFORMA Adapter %s: BIOS disabled BIOS has been disabled. None.
TIONAL (Server %s)
10116 INFORMA Adapter %s: BIOS stop on Stop on Error has been None.
TIONAL error enabled (Server %s) enabled.
10117 INFORMA Adapter %s: BIOS stop on Stop on Error has been None.
TIONAL error disabled (Server %s) disabled.
10131 INFORMA Adapter %s: S.M.A.R.T. poll S.M.A.R.T. Poll Interval None.
TIONAL interval changed (Server %s) has been changed.
10132 INFORMA Adapter %s: Configuration Rescan of the array None.
TIONAL rescanned (Server %s) configuration has been
performed.
10133 INFORMA Adapter %s: Configuration The array configuration None.
TIONAL cleared (Server %s) has been deleted.
10168 INFORMA Adapter %s: Logical drive The name of the logical None.
TIONAL %s: Name changed (Server drive has been changed.
%s)
10170 MAJOR Reboot required (Server %s) Reboot is required. Restart the system.
10171 INFORMA User %s (%s) logged in The user has logged in. None.
TIONAL (Server %s)
10172 INFORMA User %s (%s) logged out The user has logged out. None.
TIONAL (Server %s)
10204 CRITICAL Adapter %s: Fatal firmware A fatal error has occurred Contact an office listed in
error: %s (Server %s) in the firmware. the "Contact Information"
of "Start Guide".
10205 INFORMA Adapter %s: Factory defaults Factory default has been Check the controller's
TIONAL restored (Server %s) restored. settings and change them
to the correct values.
10206 MAJOR Adapter %s: Flash The downloaded firmware Update the firmware again
downloaded image corrupt image is corrupted. by using a correct image.
(Server %s)
10207 MAJOR Adapter %s: Flash erase error The Flash erasure has Update the firmware
(Server %s) failed. again.
10208 MAJOR Adapter %s: Flash timeout A timeout has occurred Update the firmware
during erase (Server %s) during the Flash erasure. again.
10209 MAJOR Adapter %s: Flash error The Flash has failed. Update the firmware
(Server %s) again.
10210 INFORMA Adapter %s: Flashing image: A Flash of the image has None.
TIONAL %s (Server %s) been performed.
10211 INFORMA Adapter %s: Flash of new A Flash of the new None.
TIONAL firmware image(s) complete firmware image has been
(Server %s) completed.
142

10212 MAJOR Adapter %s: Flash An error has occurred Update the firmware
programming error (Server during the Flash again.
%s) programming.
10213 MAJOR Adapter %s: Flash timeout Timeout has occurred Update the firmware
during programming (Server during the Flash again.
%s) programming.
10214 MINOR Adapter %s: Flash chip type The chip type of the Flash Update the firmware again
unknown (Server %s) is unknown. using the correct image.
Check to see if the target
controller that needs to be
updated is correct.
10215 MAJOR Adapter %s: Flash command The Flash command is not Update the firmware again
set unknown (Server %s) recognized. by using the correct tool.
10216 MAJOR Adapter %s: Flash The Flash verification has Update the firmware
verification failure (Server failed. again.
%s)
10217 INFORMA Adapter %s: Flush rate The Flush Rate has been None.
TIONAL changed to %s seconds changed in seconds.
(Server %s)
10218 INFORMA Adapter %s: Hibernate The hibernation command None.
TIONAL command received from host was received from the
(Server %s) server.
10219 INFORMA Adapter %s: Event log The event log has been None.
TIONAL cleared (Server %s) cleared.
10220 INFORMA Adapter %s: Event log The event log has reached None.
TIONAL wrapped (Server %s) the maximum capacity
and old log entries have
been deleted.
10221 MAJOR Adapter %s: Multi-bit ECC A multi-bit error has been Replace the cache
error: ECAR=%s detected. memory or the battery
backup unit. If this error
occurs again, contact an
office listed in the
"Contact Information" of
"Start Guide".
10222 MAJOR Adapter %s: Single-bit ECC A single-bit error has been Replace the cache
"Start Guide".
10223 MAJOR Adapter %s: Not enough There is not a sufficient Contact an office listed in
adapter memory (Server %s) amount of Controller the "Contact Information"
memory. of "Start Guide".
10226 INFORMA Adapter %s: Shutdown The shutdown command None.
TIONAL command received from host was received from the
(Server %s) server.
10227 INFORMA Adapter %s: Test event: '%s' A test event has been None.
TIONAL (Server %s) issued.
143
Appendix

10228 INFORMA Adapter %s: Time The system time has been None.
TIONAL established as %s; (%s set.
seconds since power on)
(Server %s)
10229 INFORMA Adapter %s: User entered The firmware has entered None.
TIONAL firmware debugger (Server the debug mode.
%s)
10235 INFORMA Adapter %s: Logical drive A property of the logical None.
TIONAL %s: %s changed (Server %s) drive has been changed.
10240 MAJOR Adapter %s: Initialization Foreground initialization None.
failed on logical drive %s has failed. (Foreground initialization
(Server %s) on the OS is not
supported.)
10241 INFORMA Adapter %s: Initialization Foreground initialization None.
TIONAL progress on logical drive %s is in progress. (Foreground initialization
is %s (Server %s) on the OS is not
supported.)
10243 INFORMA Adapter %s: Full Full initialization has None.
TIONAL initialization started on started.
logical drive %s (Server %s)
10244 INFORMA Adapter %s: Logical drive A property of the logical None.
TIONAL %s: Property %s updated drive has been changed.
(Server %s)
10249 INFORMA Adapter %s: State change on The logical drive status is None.
TIONAL logical drive %s from now online.
operational to operational
(Server %s)
10255 MAJOR Adapter %s: Error on disk An error has occurred on Replace and rebuild the
(%s) (error %s) (Server %s) the hard disk. failed hard disk.
10259 MAJOR Adapter %s: Disk (%s) is not An unsupported hard disk Use a supported hard disk.
supported (Server %s) has been detected.
10263 MINOR Adapter %s: Predictive A failure has been Replace the hard disk as a
failure: Disk (%s) (Server predicted for a hard disk. preventive measure.
%s)
10264 MAJOR Adapter %s: Puncturing bad A media error has been If an unreadable file is
block on disk (%s) at LBA detected in the source hard found during operation,
%s (Server %s) disk during the rebuild. restore the file from the
backup.
10265 MINOR Adapter %s: Rebuild aborted The rebuild has been Perform the rebuild again.
by user on disk (%s) (Server canceled.
%s)
10266 INFORMA Adapter %s: Rebuild The rebuild of the logical None.
TIONAL complete on logical drive %s drive has been completed.
(Server %s)
10267 INFORMA Adapter %s: Rebuild The rebuild of the hard None.
TIONAL complete on disk (%s) disk has been completed.
(Server %s)
10268 INFORMA Adapter %s: Rebuild The rebuild is in progress. None.
TIONAL progress on disk (%s) is %s
(Server %s)
144

10269 INFORMA Adapter %s: Rebuild The rebuild has resumed. None.
TIONAL resumed on disk (%s) (Server
%s)
10270 INFORMA Adapter %s: Rebuild The rebuild of the hard None.
TIONAL automatically started on disk disk has started
(%s) (Server %s) automatically.
10272 MAJOR Adapter %s: Reassign write The reassign operation has Replace and rebuild the
operation failed on disk (%s) failed. failed hard disk.
at LBA %s (Server %s)
10273 MAJOR Adapter %s: Unrecoverable An unrecoverable media If an unreadable file is
medium error during rebuild error has been detected found during operation,
on disk (%s) at LBA %s during the rebuild. restore the file from the
(Server %s) backup.
10274 INFORMA Adapter %s: Corrected A media error has been None.
TIONAL medium error during recovered.
recovery on disk (%s) at
LBA %s (Server %s)
10275 MAJOR Adapter %s: Unrecoverable An unrecoverable media If an unreadable file is
medium error during error has been detected. found during operation,
recovery on disk (%s) at restore the file from the
LBA %s (Server %s) backup.
10276 INFORMA Adapter %s: Unexpected Sense information of the There is no problem as
TIONAL sense: Disk (%s) hard disk has been long as the target hard disk
reported. is online because the
controller has performed
recovery.
10277 INFORMA Adapter %s: State change on The hard disk is now None.
TIONAL disk (%s) from available to available.
available (Server %s)
10278 INFORMA Adapter %s: State change by The hard disk status is None.
TIONAL user on disk (%s) from now available.
available to available (Server
%s)
10282 MINOR Adapter %s: SAS topology A loop has been detected Check the connections of
error: Loop detected (Server in the SAS topology. the hard disk and cables. If
%s) this error occurs again,
contact an office listed in
the "Contact Information"
of "Start Guide".
10283 MINOR Adapter %s: SAS topology A device is unaddressable Check the connections of
error: Unaddressable device with the SAS topology. the hard disk and cables. If
(Server %s) the system connections
are correct, yet a hard disk
has failed, replace the hard
disk and perform a
rebuild.
If this error occurs again,
of "Start Guide".
145
Appendix

10284 MINOR Adapter %s: SAS topology Multiple ports are Check the connection
error: Multiple ports to the connected to the same configuration. If this error
same SAS address (Server SAS address in the SAS occurs again, contact an
%s) topology. office listed in the
"Start Guide".
10285 MINOR Adapter %s: SAS topology An error has been detected Contact an office listed in
error: Expander error (Server in the Expander. the "Contact Information"
%s) of "Start Guide".
10286 MINOR Adapter %s: SAS topology An SMP timeout has been Contact an office listed in
error: SMP timeout (Server detected. the "Contact Information"
10287 MINOR Adapter %s: SAS topology Route entries cannot be Contact an office listed in
error: Out of route entries found. the "Contact Information"
(Server %s) of "Start Guide".
10288 MINOR Adapter %s: SAS topology Index cannot be found. Contact an office listed in
error: Index not found the "Contact Information"
error: SMP function failed in an SMP function. the "Contact Information"
10290 MINOR Adapter %s: SAS topology A CRC error has been Contact an office listed in
error: SMP CRC error detected in SMP. the "Contact Information"
error: Multiple subtractive in the SAS topology. the "Contact Information"
error: Table to table (Server in the SAS topology. the "Contact Information"
10293 MINOR Adapter %s: SAS topology Multiple paths exist. Check the connections of
error: Multiple paths (Server the hard disk and cables. If
%s) this error occurs again,
of "Start Guide".
10294 MAJOR Adapter %s: Unable to The hard disk cannot be Replace and rebuild the
access disk (%s) (Server %s) accessed. failed hard disk.
10297 MINOR Adapter %s: Marking logical The consistency of the None.
drive %s inconsistent due to logical drive has been lost Automatically restored
active writes at shutdown due to the shutdown with Write Journaling.
(Server %s) during the Write
operation.
10336 MINOR Adapter %s: Disk (%s) too There is not a sufficient Replace the hard disk with
small to be used for auto amount of hard disk sufficient capacity.
rebuild (Server %s) capacity to perform a
rebuild.
10339 INFORMA Adapter %s: Bad block table The Bad Block Table use Replace the hard disk as a
TIONAL on disk (%s) is 80% full rate has exceeded 80%. preventive measure.
(Server %s)
146

10340 MINOR Adapter %s: Bad block table The Bad Block Table is Replace the hard disk as a
on disk (%s) is full; unable to full. preventive measure.
log Block %s (Server %s)
10344 MINOR Adapter %s: Single-bit ECC A single-bit error has been Replace the cache
"Start Guide".
10345 MINOR Adapter %s: Single-bit ECC A single-bit error has been Replace the cache
"Start Guide".
10346 INFORMA Adapter %s: Single-bit ECC A single-bit error has been Replace the cache
TIONAL error: ECAR=%s detected. memory or the battery
"Start Guide".
10353 INFORMA Adapter %s: Retention test The NVRAM retention None.
TIONAL started on previous reboot test has started.
(Server %s)
10354 INFORMA Adapter %s: NVRAM The NVRAM retention None.
TIONAL retention test passed (Server test has been completed.
%s)
10355 MINOR Adapter %s: NVRAM The NVRAM retention Contact an office listed in
retention test failed! (Server test has failed.
%s)
of "Start Guide".
10356 INFORMA Adapter %s: %s test finished The test has been None.
TIONAL %s passes successfully completed.
(Server %s)
10357 MINOR Adapter %s: %s test failed on The test has failed. Contact an office listed in
%s pass. fail data: the "Contact Information"
errorOffset=%s of "Start Guide".
goodData=%s badData=%s
(Server %s)
10358 INFORMA Adapter %s: Self-check The self-test has been None.
TIONAL diagnostics finished (Server completed.
%s)
10359 INFORMA Adapter %s: Foreign Foreign Configuration has None.
TIONAL configuration detected been detected. (Replace and rebuild the
(Server %s) failed hard disks.)
TIONAL configuration imported been imported.
(Server %s)
147
Appendix

TIONAL configuration cleared (Server been cleared.
%s)
10362 MINOR Adapter %s: NVRAM is The NVRAM had a Contact an office listed in
corrupt; reinitializing (Server failure and re- the "Contact Information"
%s) initialization is in of "Start Guide".
progress.
10363 MINOR Adapter %s: NVRAM An NVRAM mismatch Contact an office listed in
mismatch occurred (Server has occurred. the "Contact Information"
10364 MINOR Adapter %s: SAS wide port The SAS wide port has Check the connections of
%s lost link on PHY %s lost its link. the system, and replace
(Server %s) the failed hard disk and
perform a rebuild.
of "Start Guide".
10365 INFORMA Adapter %s: SAS wide port The SAS wide port has None.
TIONAL %s restored link on PHY %s restored its link.
(Server %s)
10366 MINOR Adapter %s: SAS port %s The errors in the SAS port Contact an office listed in
have exceeded the the "Contact Information"
threshold. of "Start Guide".
10367 MINOR Adapter %s: Bad block A bad block of the hard None.
reassigned on disk (%s) from disk has been relocated.
LBA %s to LBA %s (Server
%s)
10368 INFORMA Adapter %s: Adapter hot A controller has been None.
TIONAL plug detected (Server %s) detected.
10371 INFORMA Adapter %s: Time duration The system has not Contact an office listed in
TIONAL provided by host is not provided enough time for the "Contact Information"
sufficient for self-checking self-checking. of "Start Guide".
(Server %s)
10372 INFORMA Adapter %s: Disk (%s) on The hard disk has been Replace and rebuild the
TIONAL array %s row %s marked marked as missing. failed hard disk.
missing (Server %s)
10377 MINOR Adapter %s: Disk (%s) is not The hard disk is not a Replace the hard disk with
certified (Server %s) certified drive. a certified drive.
10378 MINOR Adapter %s: Dirty cache data Dirty cache data has been Perform Make Data
discarded by user (Server discarded by the user's Consistent.
%s) operation.
10379 MINOR Adapter %s: Disks missing An undetected hard disk Replace and rebuild the
from configuration at boot during startup exists. failed hard disk.
(Server %s)
10380 MINOR Adapter %s: Logical drives The logical drive status Replace and rebuild the
missing drives and will go was offline during startup. failed hard disk.
offline at boot: %s (Server
%s)
148

10382 MINOR Adapter %s: Previous The previous Turn off the server and
configuration completely configuration cannot be check the connection of
missing at boot (Server %s) found during startup. the hard disks, cables, the
power supply, etc..
of "Start Guide".
10386 INFORMA Adapter %s: Disk (%s) Rebuilding of the hard None.
TIONAL rebuild not possible as SAS/ disk is not possible (SATA HDD is not
SATA is not supported in an because SAS/SATA is not supported.)
array (Server %s) supported.
10388 MAJOR Adapter %s: Logical drive The logical drive status is Replace and rebuild the
%s partially degraded now degraded. failed hard disk.
(Server %s)
10390 INFORMA Adapter %s: Coercion mode The coercion mode has None.
TIONAL changed (Server %s) been changed.
10401 MINOR Adapter %s: Logical drive The logical drive has been Contact an office listed in
%s disabled because SAS disabled because the SAS the "Contact Information"
drives are not supported by hard disks are not of "Start Guide".
this RAID key (Server %s) supported by the RAID
key.
10402 MINOR Adapter %s: Disks missing hard disks do not exist. Replace and rebuild the
(Server %s) failed hard disk.
10403 INFORMA Adapter %s: Rebuild rate Rebuild Rate has been None.
TIONAL changed to %s%% (Server changed.
%s)
10405 INFORMA Adapter %s: S.M.A.R.T. poll S.M.A.R.T. Poll Interval None.
TIONAL interval changed to %s min has been changed.
(Server %s)
10412 MAJOR Adapter %s: State change on The logical drive status Replace and rebuild the
logical drive %s from has changed from online failed hard disk.
operational to degraded to degraded.
(Server %s)
logical drive %s from has changed from online failed hard disk.
operational to partially to critical.
degraded (Server %s)
10414 CRITICAL Adapter %s: State change on The logical drive status Contact an office listed in
logical drive %s from has changed from online the "Contact Information"
operational to failed (Server to offline. of "Start Guide".
%s)
10415 INFORMA Adapter %s: State change on The logical drive status None.
TIONAL logical drive %s from has been restored from
degraded to operational degraded to online.
(Server %s)
10416 MAJOR Adapter %s: State change on The logical drive status is Replace and rebuild the
logical drive %s from now degraded. failed hard disk.
degraded to degraded (Server
%s)
149
Appendix

logical drive %s from now degraded. failed hard disk..
degraded to partially
logical drive %s from has changed from the "Contact Information"
degraded to failed (Server degraded to offline. of "Start Guide".
%s)
TIONAL logical drive %s from has been restored from
partially degraded to degraded to online.
operational (Server %s)
partially degraded to
partially degraded to partially
logical drive %s from has changed from the "Contact Information"
partially degraded to failed degraded to offline. of "Start Guide".
(Server %s)
TIONAL logical drive %s from failed has changed from offline
to operational (Server %s) to online.
logical drive %s from failed has changed from offline failed hard disk.
to degraded (Server %s) to degraded.
logical drive %s from failed has changed from offline failed hard disk.
to partially degraded (Server to degraded.
%s)
10426 CRITICAL Adapter %s: State change on The logical drive status is Contact an office listed in
logical drive %s from failed now offline. the "Contact Information"
to failed (Server %s) of "Start Guide".
10427 CRITICAL Adapter %s: State change by The hard disk status has Replace the failed hard
user on disk (%s) from changed from available to disk.
available to failed (Server failed.
%s)
10428 INFORMA Adapter %s: State change by The hard disk has changed None.
TIONAL user on disk (%s) from from unused to a spare
available to hot spare (Server disk.
%s)
10429 INFORMA Adapter %s: State change by The hard disk status has None.
TIONAL user on disk (%s) from changed from available to
available to rebuilding rebuilding.
(Server %s)
150

available to operational operational.
(Server %s)
TIONAL user on disk (%s) from failed changed from failed to
to available (Server %s) available.
10432 CRITICAL Adapter %s: State change by The hard disk status is Replace and rebuild the
user on disk (%s) from failed now failed. failed hard disk.
to failed (Server %s)
TIONAL user on disk (%s) from failed from the failed to a spare (HotSpare is not
to hot spare (Server %s) disk. supported.)
to rebuilding (Server %s) rebuilding.
to operational (Server %s) operational.
TIONAL user on disk (%s) from hot from a spare disk to the (HotSpare is not
spare to available (Server available. supported.)
%s)
10437 CRITICAL Adapter %s: State change by The hard disk has changed Replace the failed hard
user on disk (%s) from hot from a spare disk to the disk and configure the
spare to failed (Server %s) failed. new drive as a HotSpare
drive.
(HotSpare is not
supported.)
10438 INFORMA Adapter %s: State change by The hard disk is now a None.
TIONAL user on disk (%s) from hot spare disk. (HotSpare is not
spare to hot spare (Server supported.)
%s)
TIONAL user on disk (%s) from hot from a spare disk to (HotSpare is not
spare to rebuilding (Server rebuild. supported.)
%s)
TIONAL user on disk (%s) from hot changed from a spare disk (HotSpare is not
spare to operational (Server to operational. supported.)
%s)
TIONAL user on disk (%s) from changed from rebuilding
rebuilding to available to available.
(Server %s)
10442 CRITICAL Adapter %s: State change by The hard disk status has Replace and rebuild the
user on disk (%s) from changed from rebuilding failed hard disk.
rebuilding to failed (Server to failed.
%s)
151
Appendix

TIONAL user on disk (%s) from changed from rebuilding (HotSpare is not
rebuilding to hot spare to a spare disk. supported.)
(Server %s)
TIONAL user on disk (%s) from now rebuilding.
rebuilding to rebuilding
(Server %s)
TIONAL user on disk (%s) from changed from rebuilding
rebuilding to operational to operational.
(Server %s)
TIONAL user on disk (%s) from changed from operational
operational to available to available.
(Server %s)
10447 CRITICAL Adapter %s: State change by The hard disk status has Replace and rebuild the
user on disk (%s) from changed from operational failed hard disk.
operational to failed (Server to failed.
%s)
operational to hot spare to a spare disk.
(Server %s)
operational to rebuilding to rebuilding.
(Server %s)
TIONAL user on disk (%s) from now operational.
operational to operational
(Server %s)
10451 CRITICAL Adapter %s: State change on The hard disk status has Replace the failed hard
disk (%s) from available to changed from available to disk.
failed (Server %s) failed.
10452 INFORMA Adapter %s: State change on The hard disk status has None.
TIONAL disk (%s) from available to changed from available to
hot spare (Server %s) a spare disk.
rebuilding (Server %s) rebuilding.
operational (Server %s) operational.
TIONAL disk (%s) from failed to changed from failed to
available (Server %s) available.
10456 CRITICAL Adapter %s: State change on The hard disk status is Replace and rebuild the
disk (%s) from failed to now failed. failed hard disk.
failed (Server %s)
152

TIONAL disk (%s) from failed to hot changed from failed to a (HotSpare is not
spare (Server %s) spare disk. supported.)
TIONAL disk (%s) from hot spare to changed from a spare disk
available (Server %s) to available.
10461 CRITICAL Adapter %s: State change on The hard disk status has Replace the failed hard
disk (%s) from hot spare to changed from a spare disk disk and configure the
failed (Server %s) to failed. new drive as a spare disk
drive.
(HotSpare is not
supported.)
10462 INFORMA Adapter %s: State change on The hard disk status is None.
TIONAL disk (%s) from hot spare to now a spare disk. (HotSpare is not
hot spare (Server %s) supported.)
10463 INFORMA Adapter %s: State change on The hard disk status has Replace and rebuild the
TIONAL disk (%s) from hot spare to changed from a spare disk failed hard disk.
rebuilding (Server %s) to rebuilding. (HotSpare is not
supported.)
10464 INFORMA Adapter %s: State change on The hard disk status has None
TIONAL disk (%s) from hot spare to changed from a spare disk (HotSpare is not sup-
operational (Server %s) to operational. ported.)
TIONAL disk (%s) from rebuilding to changed from rebuilding
10466 CRITICAL Adapter %s: State change on The hard disk status has Replace and rebuild the
disk (%s) from rebuilding to changed from rebuilding failed hard disk.
failed (Server %s) to failed.
TIONAL disk (%s) from rebuilding to changed from rebuilding (HotSpare is not
hot spare (Server %s) to a spare disk. supported.)
TIONAL disk (%s) from rebuilding to now rebuilding.
rebuilding (Server %s)
TIONAL disk (%s) from rebuilding to changed from rebuilding
operational (Server %s) to operational.
TIONAL disk (%s) from operational to changed from operational
10471 CRITICAL Adapter %s: State change on The hard disk status has Replace and rebuild the
disk (%s) from operational to changed from operational failed hard disk.
failed (Server %s) to failed.
153
Appendix

TIONAL disk (%s) from operational to changed from operational (HotSpare is not
hot spare (Server %s) to a spare disk. supported.)
TIONAL disk (%s) from operational to changed from operational
rebuilding (Server %s) to rebuilding.
TIONAL disk (%s) from operational to now operational.
operational (Server %s)
10476 MAJOR Adapter %s: Disk (%s) A hard disk was not found At the OS restart after
missing after reboot (Server during startup. adding and removing
%s) option cards, this event
may occur. Check the
condition of the array
using ServerView RAID
Manager. If it is OK, then
there is no problem. Also,
the problem described at
"1.5.2 Using ServerView
RAID under Windows
2000 Server
Environment" (Jpg.19) is
not a problem. When there
are failed hard disks,
replace and rebuild them.
10477 MAJOR Adapter %s: Logical drive A logical drive cannot be At the OS restart after
(%s) missing after reboot found during startup. adding and removing
(Server %s) option cards, this event
may occur. Check the con-
dition of the array using
ServerView RAID Man-
ager. If it is OK, then there
is no problem. Also, this
event occurs after the
array configuration or the
problem described at
"1.5.2 Using ServerView
RAID under Windows
2000 Server
Environment" (Jpg.19)
occurs, there is no prob-
lem. When it occurs dur-
ing regular operation,
of "Start Guide".
10478 INFORMA Adapter %s: Disk (%s) A new hard disk has been None.
TIONAL appeared new after reboot found after the reboot.
(Server %s)
10479 INFORMA Adapter %s: Logical drive A new logical drive has None.
TIONAL %s appeared new after reboot been found after the
(Server %s) reboot.
154

offline (Server %s) offline.
available to offline (Server offline.
%s)
to offline (Server %s) offline.
10488 MINOR Adapter %s: State change by The hard disk status has Replace and rebuild the
user on disk (%s) from hot changed from a spare disk failed hard disk.
spare to offline (Server %s) to offline.
TIONAL user on disk (%s) from changed from offline to
offline to available (Server available.
%s)
10490 MAJOR Adapter %s: State change by The hard disk status has Replace and rebuild the
user on disk (%s) from changed from offline to failed hard disk.
offline to failed (Server %s) failed.
TIONAL user on disk (%s) from changed from offline to a
offline to hot spare (Server spare disk.
%s)
offline to offline (Server %s) offline.
offline to operational (Server operational.
%s)
offline to rebuilding (Server rebuilding.
%s)
user on disk (%s) from changed from operational failed hard disk.
operational to offline (Server to offline.
%s)
user on disk (%s) from changed from rebuilding failed hard disk.
rebuilding to offline (Server to offline.
%s)
10498 MINOR Adapter %s: State change on The hard disk status has Replace and rebuild the
disk (%s) from hot spare to changed from a spare disk failed hard disk.
offline (Server %s) to offline.
TIONAL disk (%s) from offline to changed from offline to
available (Server %s) available.
155
Appendix

10500 MAJOR Adapter %s: State change on The hard disk status has Replace and rebuild the
disk (%s) from offline to changed from offline to failed hard disk.
failed (Server %s) failed.
TIONAL disk (%s) from offline to hot changed from offline to a
spare (Server %s) spare disk.
disk (%s) from operational to changed from operational failed hard disk.
disk (%s) from rebuilding to changed from rebuilding failed hard disk.
10509 INFORMA Adapter %s: Rebuild on Rebuilding of the hard None.
TIONAL disk (%s) resumed (Server disk has resumed.
%s)
10511 INFORMA Adapter %s: BGI restarted on Background initialization None.
TIONAL logical drive %s (Server %s) has restarted on the logical
drive.
10513 INFORMA Adapter %s: Rebuild on Rebuilding of the logical None.
TIONAL logical drive %s resumed drive has resumed.
(Server %s)
10518 MAJOR Adapter %s: SAS port %s SAS link has None.
lost link (Server %s) disconnected.
10519 INFORMA Adapter %s: SAS port %s SAS link has restored. None.
TIONAL restored link (Server %s)
10526 CRITICAL Adapter %s: Adapter missing A controller is missing. None.
after reboot (Server %s)
10527 INFORMA Adapter %s: Adapter A controller is newly None.
TIONAL appeared new after reboot detected.
(Server %s)
10528 MINOR Adapter %s: Rebuild aborted Rebuilding has stopped. None.
on disk (%s) (Server %s)
10536 CRITICAL Adapter %s: Command A timeout occurred during None.
timeout on disk (%s), CDB: a command processing.
%s (Server %s)
10537 MINOR Adapter %s: Disk (%s) reset A hard disk is prompted to None.
(type %s) (Server %s) reset.
156

10540 MAJOR Adapter %s: Uncorrectable An uncorrectable medium None.
medium error logged for error is detected.
logical drive %s at LBA %s
(on disk (%s) at LBA %s)
(Server %s)
10541 MINOR Adapter %s: Medium error A medium error has been None.
corrected on logical drive %s corrected.
at LBA %s (Server %s)
10544 CRITICAL Adapter %s: Adapter needs A failure has detected on None.
replacement, faulty IOP IO processor of a
detected (Server %s) controller.
10559 INFORMA Adapter %s: Additional Additional information for None.
TIONAL information for failed disk a failed hard disk is
(%s) - firmware version: %s, displayed.
serial number %s, first use:
%s, total running time: %s
days
157
Appendix
B A List of GAM Event Logs
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 Description Severity in GAM Client OS event log type
CRITICAL Severe error 1 Error
MAJOR Error 2 Error
MINOR Warning 3 Warning
Information (No
INFORMATIONAL 4 Information
action required)
158
The number within the parentheses of the GAM ID is displayed in hexadecimal format.
table: A list of GAM event logs
GAM ID Severity Description Details Corrective action
1 Info/1 A physical disk has A hard disk has become None.
(0x001) been placed online. operational.
2 Info/1 Physical disk A hard disk has been set as None.

(0x002) added as hot spare. a hot spare.
3 Error/3 Physical disk error • A bad sector was found Check the state of the target hard
(0x003) found. on the media. disk. If it has a failure, see "6.2.2
• A mechanical failure of Replacing Failed Hard Disk
the device. [GAM]" (Jpg.132) to replace it
• The host device and perform a rebuild. If the error
detected an invalid occurred only temporarily and
sequence. does not occur again, the hard disk
• The target device is is recovered and no action is
missing. required. However, if this error
occurs frequently, we recommend
that you replace the drive as a
precautionary measure, referring to
"6.2.3 Preventive Replacement of
Hard Disk [GAM]" (Jpg.134).
4 Error/3 Physical disk PFA A failure has been See "6.2.3 Preventive Replacement
(0x004) condition found; predicted for the hard of Hard Disk [GAM]" (Jpg.134)
this disk may fail disk. and replace the hard disk as a
soon. preventive measure.
5 Info/1 An automatic Rebuild started None.

(0x005) rebuild has started. automatically.
6 Info/1 A rebuild has Rebuild started via a None.

(0x006) started. command.
7 Info/1 Rebuild is over. Rebuild has been None.

(0x007) completed.
8 Info/1 Rebuild is Rebuild was canceled. Perform the rebuild again.

(0x008) cancelled.
9 Error/3 Rebuild stopped Rebuild terminated See "5.6.4 Viewing Logical Drive
(0x009) with error. abnormally. Information" (Jpg.118) to check
(When abnormality occurs the current status of the logical
in the SAS interface, this drive.
may be notified not during • For Critical state:
rebuild processing.) See "6.2.2 Replacing Failed
Hard Disk [GAM]" (Jpg.132)
to replace the hard disk and
perform the rebuild again.
• For Offline state:
Contact an office listed in the
"Contact Information" of "Start
Guide".
10 Error/3 Rebuild stopped Rebuild terminated See "6.2.2 Replacing Failed Hard
(0x00A) with error. New abnormally due to a Disk [GAM]" (Jpg.132) to
device failed. failure found on the target replace the hard disk and perform a
hard disk for the rebuild. rebuild.
11 Error/3 Rebuild stopped Rebuild terminated Contact an office listed in the
(0x00B) because logical abnormally due to failures "Contact Information" of "Start
drive failed. in multiple hard disks. Guide".
159
Appendix

12 Error/3 Physical disk has A hard disk has failed. See "6.2.2 Replacing Failed Hard
(0x00C) failed. Disk [GAM]" (Jpg.132) to
replace the hard disk and perform a
rebuild.
13 Info/1 A new physical A new hard disk was None.
(0x00D) disk has been detected.
found.
14 Info/1 A physical disk has A hard disk was removed. None.
(0x00E) been removed. A hard disk has become
undetectable.
15 Info/1 A previously A hard disk is now in None.
(0x00F) configured disk is Unconfigured state.
now available.
19 Error/3 SCSI command A command timeout was Because the controller is
(0x013) timeout on hard detected. performing a recovery, there is no
device. problem as long as there are no
failed hard disks.
20 Error/3 SCSI command A SCSI command was Because the controller is
(0x014) abort on hard disk. aborted. performing a recovery, there is no
problem as long as there are no
failed hard disks.
21 Warning/2 SCSI command A SCSI command was Because the controller is
(0x015) retried on hard retried. performing a recovery, there is no
disk. problem as long as there are no
failed hard disks.
23 Warning/2 Soft error found. An error was detected on a Because the controller is
(0x017) hard disk, but it was performing a recovery, no action is
resolved. required. If this error occurs
frequently, see "6.2.3 Preventive
Replacement of Hard Disk
[GAM]" (Jpg.134) to replace the
hard disk as a precautionary
measure.
24 Warning/2 Misc error found. An error was detected on a Because the controller is
(0x018) hard disk, but it was performing a recovery, no action is
resolved. required. If this error occurs
frequently, see "6.2.3 Preventive
Replacement of Hard Disk
hard disk as a precautionary
measure.
25 Info/1 SCSI device reset. The firmware issued a None.
(0x019) device reset.
28 Error/3 Request Sense A hard disk reported sense Because the controller is
(0x01C) Data available. information. performing a recovery, no action is
required as long as the
corresponding disk is Online.
29 Info/1 Initialization A hard disk formatting has Wait until the format is completed.
(0x01D) started. started.
30 Info/1 Initialization The hard disk format has None.
(0x01E) completed. been completed.
160

31 Error/3 Initialization The hard disk format failed. See "6.2.2 Replacing Failed Hard
(0x01F) failed. Disk [GAM]" (Jpg.132) to
replace the hard disk.
32 Error/3 Initialization The hard disk format was Format the hard disk again.
(0x020) canceled. canceled.
33 - 41 Error/3 A physical disk A hard disk has failed. See "6.2.2 Replacing Failed Hard
(0x021 - failed because ••• Disk [GAM]" (Jpg.132) to
0x029) replace the hard disk and perform a
rebuild.
42 Error/3 A physical disk set A Make Offline has been See "6.2.2 Replacing Failed Hard
(0x02A) to failed state by executed by the controller. Disk [GAM]" (Jpg.132) to
host. replace the hard disk and perform a
rebuild.
43 - 49 Error/3 A physical disk A hard disk has failed. See "6.2.2 Replacing Failed Hard
(0x02B - failed because ••• Disk [GAM]" (Jpg.132) to
0x031) replace the hard disk and perform a
rebuild.
50 Error/3 Physical disk A hard disk has become None.
(0x032) status changed to offline.
offline.
52 Error/3 Physical disk The hard disk status has None.
(0x034) status changed to become rebuild.
rebuild.
53 Warning/2 Physical device ID The hard disk ID does not Check the logs surrounding the
(0x035) did not match. match. process and perform necessary
actions.
54 Error/3 Physical disk A hard disk failed to start. Check that the hard disk is
(0x036) failed to start. connected properly. If the hard disk
has failed, see "6.2.2 Replacing
Failed Hard Disk [GAM]"
(Jpg.132) to replace the hard disk
and perform a rebuild.
55 Warning/2 Physical disk A hard disk has negotiated Check that the hard disk is
(0x037) negotiated an offset different from connected properly. If the hard disk
different offset the configuration. has failed, see "6.2.2 Replacing
than config. Failed Hard Disk [GAM]"
56 Warning/2 Physical disk A hard disk has negotiated Check that the hard disk is
(0x038) negotiated a bus width different from connected properly. If the hard disk
different bus width the configuration. has failed, see "6.2.2 Replacing
than config. Failed Hard Disk [GAM]"
57 Error/3 Physical drive No hard disk was detected Check that the hard disk is
(0x039) missing on startup. during startup. connected properly. If the hard disk
has failed, see "6.2.2 Replacing
161
Appendix

58 Error/3 Rebuild startup Insufficient hard disk See "6.2.2 Replacing Failed Hard
(0x03A) failed due to lower space to perform the Disk [GAM]" (Jpg.132) to
disk capacity. rebuild. replace the hard disk with a drive
of the same model (with the same
capacity and speed) as the other
drives, and then perform a rebuild.
67 Error/3 Physical Disk A hard disk is connected Check that the hard disk is
(0x043) found on only one to only one disk channel. connected properly. If the hard disk
disk channel. has failed, see "6.2.2 Replacing
68 Info/1 Physical disk type An installed hard disk is Use a vendor supported hard disk.
(0x044) is not approved by not vendor approved.
vendor.
69 Error/3 Physical disk has A hard disk has acquired See "6.2.2 Replacing Failed Hard
(0x045) acquired an an inappropriate loop ID. Disk [GAM]" (Jpg.132) to
inappropriate loop replace the hard disk and perform a
ID. Enclosure rebuild. If this error occurs again,
disk-slot contact an office listed in the
operations are "Contact Information" of "Start
disabled while this Guide".
condition persists.
70 Error/3 Physical disk port • A hard disk has failed. See "6.2.2 Replacing Failed Hard
(0x046) has failed or • The hard disk is not Disk [GAM]" (Jpg.132) to
cannot operate at compatible with the replace the hard disk and perform a
the configured system. rebuild. If this error occurs again,
channel speed. • The enclosure slot contact an office listed in the
hardware failed. "Contact Information" of "Start
Guide".
72 Error/3 Controller A mistake was found in Check and correct the parameters
(0x048) parameters the checksum of the in the [Adapter Properties]
checksum controller parameters. (Jpg.28)) of WebBIOS. If the
verification failed - message still appears, contact an
restored default. office listed in the "Contact
Information" of "Start Guide".
73 Info/1 Online controller An online controller None.
(0x049) firmware upgrade firmware upgrade has
has started. started.
74 Info/1 Online firmware An online firmware None.
(0x04A) upgrade has upgrade has been
completed completed successfully.
successfully.
75 Error/3 Online firmware An online firmware Perform the online controller
(0x04B) upgrade has failed. upgrade has failed. firmware upgrade again. If the
message still appears, contact an
office listed in the "Contact
162

76 Info/1 A Configuration The array configuration Connect a compatible hard disk.
(0x04C) On Disk (COD) information of the hard
with unsupported disk contains features that
features has been are not supported.
detected. An array configuration
information created by
another system was
detected.
80 Error/3 Firmware entered The firmware entered Check the installation of the cache
(0x050) unexpected state at unexpected state at run- memory or battery backup unit.
run-time. time. If the message still appears,
replace the cache memory or the
battery backup unit.
85 Info/1 Unable to recover Recovery of a medium If a corrupted file is found, restore
(0x055) medium error error failed during the it from the backup.
during patrol read. Patrol Read operation.
86 Info/1 Rebuild resumed. Rebuild restarted. None.
(0x056)
89 Info/1 Physical disk The transfer speed of the Check the previous logs and
(0x059) transfer speed hard disk has changed due perform necessary steps.
changed. to an unknown error.
90 Error/3 Channel is An abnormal state was Contact an office listed in the
(0x05A) suspended due to found in the channel. "Contact Information" of "Start
some faults. Guide".
95 Info/1 Configured A hard disk has been Reconnect a proper hard disk.
(0x05F) physical disk replaced with a smaller
replaced by user by capacity drive than
a smaller capacity configured.
disk.
101 Error/3 Error. An unknown error was If the hard disk has failed, see
(0x065) detected. "6.2.2 Replacing Failed Hard Disk
hard disk and perform a rebuild. If
the message still appears, contact
an office listed in the "Contact
104 Error/3 Reassign write A Reassign operation If the hard disk has failed, see
(0x068) operaton failed. failed. "6.2.2 Replacing Failed Hard Disk
hard disk and perform a rebuild.
105 Error/3 Unrecoverable An unrecoverable medium If a corrupted file is found, restore
(0x069) medium error error was detected during it from the backup.
during rebuild. the rebuild process.
106 Info/1 Corrected medium A medium error was None.
(0x06A) error during corrected.
recovery.
107 Error/3 Unrecoverable An unrecoverable medium If a corrupted file is found, restore
(0x06B) medium error error was detected. it from the backup.
during recovery.
163
Appendix

119 Warning/2 PD too small to be The rebuild could not be See "6.2.2 Replacing Failed Hard
(0x077) used for auto- started because the Disk [GAM]" (Jpg.132) to
rebuild. capacity of the hard disk is replace the hard disk with a drive
smaller then the other hard of the same model (with the same
disk. capacity and speed) as the other
drives, and then perform a rebuild.
120 Warning/2 Bad block table on The Bad Block Table use See "6.2.3 Preventive Replacement
(0x078) PD is 80% full. rate has exceeded 80%. of Hard Disk [GAM]" (Jpg.134)
and replace the hard disk as a
preventive measure.
121 Error/3 Bad block table on The Bad Block Table is See "6.2.3 Preventive Replacement
(0x079) PD is full; unable full. of Hard Disk [GAM]" (Jpg.134)
to log blocks. and replace the hard disk as a
preventive measure.
126 Info/1 Firmware The media error was None.
(0x07E) corrected the corrected.
'Read' error.
134 Error/3 Logical drive has The logical drive has been The logical drive(s) cannot
(0x086) been made offline. made Offline. continue running in this state.
Recreate the array configuration
and restore the data from backup.
135 Error/3 Logical drive is The logical drive is in See "6.2.2 Replacing Failed Hard
(0x087) critical. Critical state due to a hard Disk [GAM]" (Jpg.132) to
disk failure. replace the hard disk and perform a
rebuild.
136 Info/1 Logical drive has The logical drive has been None.
(0x088) been placed online. placed online.
137 Info/1 An automatic Rebuild started None.
(0x089) rebuild has started automatically.
on logical drive.
138 Info/1 A manual rebuild Rebuild started manually. None.
(0x08A) has started on
logical drive.
139 Info/1 Rebuild on logical Rebuild has been None.
(0x08B) drive is over. completed.
140 Error/3 Rebuild on logical Rebuild was canceled. Perform the rebuild again.
(0x08C) drive is cancelled.
141 Error/3 Rebuild stopped Rebuild terminated Check the logs surrounding the
(0x08D) with error. abnormally. process and perform necessary
actions.
142 Error/3 Rebuild stopped Rebuild terminated See "6.2.2 Replacing Failed Hard
(0x08E) with error. New abnormally due to a Disk [GAM]" (Jpg.132) to
physical disk failure on the target hard replace the hard disk and perform a
failed. disk. rebuild.
143 Error/3 Rebuild stopped The source disk of the Contact an office listed in the
(0x08F) because logical rebuild failed. "Contact Information" of "Start
drive failed. Guide".
144 Info/1 Logical drive An initialization of a None.
(0x090) initialization logical drive has started.
started.
164

145 Info/1 Logical drive The initialization of the None.
(0x091) initialization done. logical drive has been
completed.
146 Error/3 Logical drive The initialization of the Perform the initialization process
(0x092) initialization logical drive was again.
cancelled. canceled.
147 Error/3 Logical drive The initialization Backup all the data on the logical
(0x093) initialization terminated abnormally. drive and see "6.2.2 Replacing
failed. The logical drive is now in Failed Hard Disk [GAM]"
Offline state. (Jpg.132) to replace the hard disk.
Recreate the array configuration.
Then restore the data from backup.
148 Info/1 A logical drive has A new logical drive has None.
(0x094) been found. been detected.
149 Info/1 A logical drive has A logical drive was None.
(0x095) been deleted. deleted.
153 Error/3 Bad Blocks found. A bad block was detected • During Make Data Consistent/
(0x099) during the Make Data capacity expansion: The bad
Consistent, rebuild, or block will be repaired, so there
capacity expansion is no problem.
process. • During rebuild: If a corrupted
file is found, restore it from the
backup.
155 Info/1 System drive type • A new configuration None.
(0x09B) changed. was added.
• The capacity expansion
has been completed.
156 Error/3 Bad data blocks Bad blocks were found on If a corrupted file is found, restore
(0x09C) found. Possible multiple hard disks at the it from the backup.
data loss. same location.
157 Info/1 Logical drive LUN Logical drive LUN None.
(0x09D) mapping has been mapping has been written
written to config. to config.
158 Error/3 Attempt to read An attempt has been made If a corrupted file is found, restore
(0x09E) data from block to read data logged in the it from the backup.
that is marked in BDT table.
Bad Data Table.
159 Error/3 Data for Disk Due to a problem with the Check the logs surrounding the
(0x09F) Block has been lost logical drive, cache data process and perform necessary
due to Logical could not be written to the actions.
Drive problem. hard disk.
163 Error/3 Reconstruct Due to media errors If a corrupted file is found, restore
(0x0A3) detected detected in the same it from the backup.
uncorrectable position on multiple hard
double medium disks, data cannot be
errors. recovered.
164 Info/1 Reconsrtuction Reconstruction was None.
(0x0A4) resumed. resumed.
165 Error/3 Reconstruction Reconstruction resume Recreate the array and restore the
(0x0A5) resume failed due terminated abnormally backup data.
to configuraiton due to configuration
mismatch. mismatch.
165
Appendix

166 情報 /1 LD Properties Parameter of the logical None.
(0x0A6) updated. drive has been changed.
350 Error/3 SAS/SATA mixing The hard disk cannot be Check if any unsupported hard
(0x15E) not supported in used, because SAS and disks are installed. If there is an
enclosure; PD SATA devices are mixed. unsupported hard disk installed,
disabled. replace it with a supported one.
384 Info/1 Array management GAM Server started None.
(0x180) server software successfully.
started
successfully.
386 Warning/2 Internal log Due to many Shut down the system properly,
(0x182) structures getting configuration changes, the power off the server and turn it
full, PLEASE configuration change table back on.If the same log still
SHUTDOWN is full. appears, contact an office listed in
AND RESET THE the "Contact Information" of "Start
SYSTEM IN THE Guide".
NEAR FUTURE.
388 Error/3 Controller is dead. The SCSI array controller Contact an office listed in the
(0x184) System is failed. "Contact Information" of "Start
disconnecting from Guide".
this controller.
389 Info/1 Controller has The controller received a Because the firmware is
(0x185) been reset. reset command. performing a recovery, there is no
failed hard disks.
390 Info/1 Controller is A controller was detected. None.
(0x186) found.
391 Error/3 Controller is gone. • The power to the Contact an office listed in the
(0x187) System is controller was cut off. "Contact Information" of "Start
disconnecting from • The controller was Guide".
this controller. removed from the
system.
(0x18B) System is controller was cut off. "Contact Information" of "Start
system.
396 Info/1 Controller A new controller was None.
(0x18C) powered on. installed.
397 Info/1 Controller is A controller came online. None.
(0x18D) online.
(0x18E) System is controller was cut off. "Contact Information" of "Start
system.
399 Warning/2 Controller's The controller went None.
(0x18F) partner is gone, Offline.
controller is in
failover mode now.
166

403 Error/3 Installation The configuration Shut down the server and check the
(0x193) aborted. changed while the system hard disk connections. Check that
was offline. 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 Error/3 Controller firmware The controller firmware Contact an office listed in the
(0x194) mismatch. has been replaced with an "Contact Information" of "Start
old version. Guide".
413 Info/1 Controller device The controller device None.
(0x19D) start complete. started.
414 Error/3 Soft ECC error An ECC error was Replace the memory module or the
(0x19E) Corrected. detected in the memory. battery backup unit.
415 Error/3 Hard ECC error An ECC error was Replace the memory module or the
(0x19F) Corrected. detected in the memory. battery backup unit.
425 Error/3 Controller boot An inappropriate firmware Contact an office listed in the
(0x1A9) ROM image needs image was loaded. "Contact Information" of "Start
to be reloaded. Guide".
426 Error/3 Controller is using The controller's MAC Contact an office listed in the
(0x1AA) default non-unique address was lost, or not "Contact Information" of "Start
world-wide name. set. Guide".
428 Error/3 Mirror Race on The hard disk has a See "6.2.2 Replacing Failed Hard
(0x1AC) critical drive. failure. Disk [GAM]" (Jpg.132) to
replace the hard disk and perform a
rebuild.
440 Error/3 Error in Mirror An error occurred in the Check the array configuration. If
(0x1B8) Race Table. Mirror Race Table. the array configuration is correct,
perform a Make Data Consistent.
If the array configuration is
invalid, reconfigure the array and
restore the data from the backup.
444 Info/1 Controller entered The controller entered None.
(0x1BC) 'Write Back' cache 'Write Back' cache mode.
mode.
446 Info/1 Data in Cache Data in the cache memory None.
(0x1BE) flushed during was flushed at the time of
power up. system boot.
447 Error/3 Data in Cache not Data in the cache memory Check the array configuration. If
(0x1BF) flushed during failed to flush at the time the array configuration is correct,
power up. of system boot due to an perform a Make Data Consistent.
abnormal configuration. If the array configuration is
452 Info/1 Rebuild rate The rebuild rate has been None.
(0x1C4) changed. changed.
460 Info/1 Factory defaults A factory default was Reconfigure the controller if
(0x1CC) restored. restored. necessary.
167
Appendix

461 Info/1 Hibernate A hibernate command was None.
(0x1CD) command received received from the host.
from host.
462 Info/1 Event log cleared. The NVRAM log was None.
(0x1CE) cleared.
463 Info/1 Event log The NVRAM log was None.
(0x1CF) wrapped. wrapped.
700 Info/1 Event log empty. The content of the event None.
(0x2BC) log has become blank.
701 Info/1 Event log entries Event Log entries were None.
(0x2BD) lost. lost.
702 Info/1 Request Sense. Sense Information was Because the firmware is
(0x2BE) reported. performing a recovery, there is no
failed hard disks.
703 Info/1 Set real time clock. The clock was set. None.
(0x2BF)
800 Info/1 New Configuration A new array configuration None.
(0x320) Received. was issued.
801 Info/1 Configuration The array configuration None.
(0x321) Cleared. was cleared.
802 Warning/2 Configuration The array configuration Check that the hard disk is
(0x322) Invalid. information is invalid. connected properly. If this does not
resolve the problem, recreate the
array and recover the backup data.
803 Warning/2 Configuration On The array configuration Check the array configuration. If
(0x323) Disk Access Error. information could not be there is a failed hard disk, see
read from the hard disk. "6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.132) to replace it
If the array configuration is
804 Warning/2 Configuration on The array configuration None.
(0x324) disk converted. information on the hard
disk was converted.
805 Warning/2 Configuration On The array configuration Shut down the server and check the
(0x325) Disk Import information could not be hard disk connections. Check that
Failed. imported. 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 Info/1 A debug dump A debug dump exists on None.
(0x326) exists on this this system.
system.
168

807 Info/1 A debug dump A debug dump exists on None.
(0x327) exists on this this system.
system.
808 Info/1 No valid No valid Configuration Check if the hard disk connected
(0x328) Configuration On On Disk (COD) found. was previously used in another
Disk (COD) found. system. If a hard disk that was
previously used in another system
is connected, that hard disk must
be formatted completely before
use.
810 Info/1 MegaRAID The initialization of the None.
(0x32A) firmware MegaRAID firmware
initialization started. started.
960 Error/3 SAS topology Loop detected in the SAS Check the condition of the system
(0x3C0) error: Loop topology. connections. If this error occurs
detected. again, even though the connections
are correct, contact an office listed
in the "Contact Information" of
"Start Guide".
961 Error/3 SAS topology Device is unaddressable in Check the condition of the system
(0x3C1) error: the SAS topology. connections. If the system
Unaddressable connections are correct but there is
device. a failed hard disk, see
"6.2.2 Replacing Failed Hard Disk
[GAM]" (Jpg.132)
to replace the hard disk and
perform a rebuild. If this error
occurs again, contact an office
listed in the "Contact Information"
of "Start Guide".
962 Error/3 SAS topology Multiple ports were Check the condition of the system
(0x3C2) error: Multiple connected to the same connections. If this error occurs
ports to the same SAS address in the SAS again, even though the connections
SAS address. topology. are correct, contact an office listed
"Start Guide".
963 Error/3 SAS topology An error was detected in Contact an office listed in the
(0x3C3) error: Expander the Expander. "Contact Information" of "Start
error. Guide".
964 Error/3 SAS topology SMP timeout was Contact an office listed in the
(0x3C4) error: SMP detected. "Contact Information" of "Start
timeout. Guide".
965 Error/3 SAS topology Route entries cannot be Contact an office listed in the
(0x3C5) error: Out of route found. "Contact Information" of "Start
entries. Guide".
966 Error/3 SAS topology Index was not found. Contact an office listed in the
(0x3C6) error: Index not "Contact Information" of "Start
found. Guide".
(0x3C7) error: SMP an SMP function. "Contact Information" of "Start
function failed. Guide".
169
Appendix

968 Error/3 SAS topology A CRC error was detected Contact an office listed in the
(0x3C8) error: SMP CRC in SMP. "Contact Information" of "Start
error. Guide".
(0x3C9) error: Multiple the SAS topology. "Contact Information" of "Start
subtractive. Guide".
(0x3CA) error: Table to the SAS topology. "Contact Information" of "Start
table. Guide".
971 Error/3 SAS topology Multiple paths exist. Check the condition of the system
(0x3CB) error: Multiple connections. If this error occurs
paths. again, even though the connections
are correct, contact an office listed
"Start Guide".
170
C Notes on Usage for the Array

Controller
This section explains notes on usages for this array controller.
C.1 When Replacing Array Controllers
Changing an array controller due to some kind of troubles when using Integrated Mirroring SAS
function (RAID 1) of this array controller will result in the loss of information about hard disk
consistency stored in the array controller. In order to make the data consistent again, you need to
initialize the logical drive of the array controller.
This is required because the array controller stores the consistency data concerning whether the Write
data was properly written into hard disks in the past. The data is stored on a nonvolatile RAM
(NVRAM) of the controller. Saving information with a maintenance tool will enable you to restore the
information after the controller replacement. With successful data saving and restoration, you do not
need to initialize the logical drive.
Depending, however, on what caused the problem like a failure of the system itself, a maintenance tool
may not start on the system and the data may not be saved. Then you need to initialize the logical drives
to make the data consistent. Even when you succeed in saving and restoring NVRAM information,
unsuccessful data consistency result will require you the initialization.
Logical drive initialization described here is the same as a rebuild operation for its identical operation to
copy data on the background and make the data consistent between two hard disks.
Notes during initialization

• Logical drive initialization of Integrated Mirroring SAS is done through background initialization.
You can use the hard disks even during the initialization process. The operation may be slower than
on initialized logical drives due to insufficient I/O processing. Operation slow down may account for
up to 50% of the full operation.
• During the OS operation, the hard disk failure LED on the front side of the hard disk to be initialized
blinks just like at the time of rebuilding operation. With ServerView, maintenance LEDs on the front
and back of the controller blink. After the initialization, the LEDs automatically stop blinking. Then
check the condition of each device through not only the LEDs but also such devices as ServerView
Console.
• Resetting or turning off the server before the completion of the initialization will stop the
initialization. The next initialization will start from the point at which the initialization was stopped
last time it was reset or shut down.
• RAID 1 logical drive is without redundancy until the completion of the initialization. It regains the
redundancy once the initialization is completed.
171
Appendix
• You can assure the completion of initialization by displaying logical drive information from
ControllerView of GAM utility. Online status means the completion. Critical status means unfinished
initialization. J"z Logical drives" (pg.110)
For ServerView RAID, Online status of a logical drive means the completion. Critical status means
unfinished initialization. J"z Logical drive" (pg.74)
Estimated time for initialization

Estimated time for the initialization without hard disk access is shown below. The time shown below is
the total time period for the OS operation without any kind of power shut down.
It takes longer than what shown below when initialization takes place with access to hard disks.
table: Estimated time for initialization
Hard disk capacity No load High load
73GB approx. 4hrs approx. 7hrs
` Information in the with load columns is the estimated time for all time high-loaded access from hard
disks.
` The numbers described above are estimates. The actual time may be different depending on your
system environment.
172
Integrated Mirroring SAS User’s Guide
Index
A E
Actions Menu . . . . . . . . . . . . . . . . . . . . . . . 71 Event Window . . . . . . . . . . . . . . . . . . . . . . .71
Adapter Properties . . . . . . . . . . . . . . . . . . . 28 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Administration Menu . . . . . . . . . . . . . . . . . 107 GAM . . . . . . . . . . . . . . . . . . . . . . . . . . .158
Administrator Privileges . . . . . . . . . . . . . . . 58 ServerView RAID . . . . . . . . . . . . . . . . .138
Array Controller
Controller Icons . . . . . . . . . . . . . . . . . . 106 F
Detailed information (GAM) . . . . . . . . . 114
Detailed information (ServerView RAID) 81 File Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Hotfix. . . . . . . . . . . . . . . . . . . . . . . . . . . 54 File Menu . . . . . . . . . . . . . . . . . . . . . . .71, 106
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Specifications . . . . . . . . . . . . . . . . . . . . 12 G
Updating the Device Drivers . . . . . . . . . 50 GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Viewing information in the BIOS Utility . 28 Access privileges . . . . . . . . . . . . . . . . . .92
Work Flow . . . . . . . . . . . . . . . . . . . . . . . 10 Events. . . . . . . . . . . . . . . . . . . . . . . . . .158
Exiting. . . . . . . . . . . . . . . . . . . . . . . . . .103
B Installation. . . . . . . . . . . . . . . . . . . . . . . .97
Background Task . . . . . . . . . . . . . . . . 86, 120 Log On . . . . . . . . . . . . . . . . . . . . . . . . .102
BIOS Utility . . . . . . . . . . . . . . . . . . . . . . . . . 23 Requirements . . . . . . . . . . . . . . . . . . . . .91
Exiting . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Starting . . . . . . . . . . . . . . . . . . . . . . . . .102
Formatting hard disk . . . . . . . . . . . . . . . 45 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . .108
Starting . . . . . . . . . . . . . . . . . . . . . . . . . 24 Uninstallation . . . . . . . . . . . . . . . . . . . .100
Viewing array controller . . . . . . . . . . . . . 28 Window Layout . . . . . . . . . . . . . . . . . . .104
Viewing hard disk . . . . . . . . . . . . . . . . . 31 GAM Client . . . . . . . . . . . . . . . . . . . . . . . . . .90
Viewing logical drive . . . . . . . . . . . . . . . 31 Installation. . . . . . . . . . . . . . . . . . . . . . . .97
Window Layout . . . . . . . . . . . . . . . . . . . 27 Server group and server settings . . . . .111
Uninstallation . . . . . . . . . . . . . . . . . . . .100
GAM ID . . . . . . . . . . . . . . . . . . . . . . . . . . .159
C GAM Server . . . . . . . . . . . . . . . . . . . . . . . . .90
Controller Icon . . . . . . . . . . . . . . . . . . . . . . 73 Installation. . . . . . . . . . . . . . . . . . . . . . . .97
Controller Icons. . . . . . . . . . . . . . . . . . . . . 106 Uninstallation . . . . . . . . . . . . . . . . . . . .101
Controller Selection Box . . . . . . . . . . . . . . 105 Global Array Manager. . . . . . . . . . . . . . . . . .90
Controller View . . . . . . . . . . . . . . . . . . . . . 109 Global Properties . . . . . . . . . . . . . . . . . . . . .29
Administration Menu . . . . . . . . . . . . . . 107 Global Status View . . . . . . . . . . . . . . . . . . .105
File Menu . . . . . . . . . . . . . . . . . . . . . . 106 Guest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
View Menu . . . . . . . . . . . . . . . . . . . . . 107
Viewing Hard Disk Information . . . . . . 115 H
Viewing Logical Drive Information . . . . 118
Hard disk
Detailed information(Controller View) . .115
D Low level formatting . . . . . . . . . . . . . . . .45
Device Drivers Manual Rebuild . . . . . . . . . . . . . . . .79, 121
Creating Driver Disks . . . . . . . . . . . . . . 50 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Updating the Drivers (Windows Server 2003) Preventive Replacement . . . . . . . .127, 134
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 RAID Levels . . . . . . . . . . . . . . . . . . . . . .13
Updating the Drivers (Windows 2000 Server) Replacing . . . . . . . . . . . . . . . . . . .125, 132
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Status Icon . . . . . . . . . . . . . . . . . . .73, 110
Disk array . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Using Controller View . . . . . . . . . . . . . . .82
Disk Groups Viewing in the BIOS Utility. . . . . . . . . . . .31
Logical Drives . . . . . . . . . . . . . . . . . . . . 14 Logical Drives . . . . . . . . . . . . . . . . . . . . .14
173
Hard disk failure prediction function . . . . . . . 17 Access privileges . . . . . . . . . . . . . . . . . . 58
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Events . . . . . . . . . . . . . . . . . . . . . . . . . 138
Hotfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Installation . . . . . . . . . . . . . . . . . . . . . . . 62
Log in. . . . . . . . . . . . . . . . . . . . . . . . . . . 66
I Requirements. . . . . . . . . . . . . . . . . . . . . 57
Uninstallation . . . . . . . . . . . . . . . . . . . . . 63
Installation ServerView RAID Manager
GAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Change Access Mode . . . . . . . . . . . . . . 70
GAM Client. . . . . . . . . . . . . . . . . . . . . . . 97 Exiting . . . . . . . . . . . . . . . . . . . . . . . . . . 68
GAM Server . . . . . . . . . . . . . . . . . . . . . . 97 Starting. . . . . . . . . . . . . . . . . . . . . . . . . . 66
ServerView RAID . . . . . . . . . . . . . . . . . . 62 Window Layout . . . . . . . . . . . . . . . . . . . 69
SNMP TRAP . . . . . . . . . . . . . . . . . . . . . . . 138
L Starting
Log Information Viewer . . . . . . . . . . . 106, 113 BIOS Utility . . . . . . . . . . . . . . . . . . . . . . 24
Logical drive. . . . . . . . . . . . . . . . . . . . . . . . . 14 Controller View. . . . . . . . . . . . . . . . . . . 109
Deleting . . . . . . . . . . . . . . . . . . . . . . 36, 42 GAM . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Initialization . . . . . . . . . . . . . . . . . . . . . . 16 ServerView RAID Manager . . . . . . . . . . 66
RAID Levels . . . . . . . . . . . . . . . . . . . . . . 13 Status
Rebuild. . . . . . . . . . . . . . . . . . . . . . . . . . 16 Hard disk . . . . . . . . . . . . . . . . . . . . . . . . 15
Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Logical Drives . . . . . . . . . . . . . . . . . . . . 15
Status Icon . . . . . . . . . . . . . . . . . . . 74, 110 Status Icon
Using Controller View . . . . . . . . . . . . . . 118 Hard disk . . . . . . . . . . . . . . . . . . . . 73, 110
Checking status . . . . . . . . . . . . . . . . . . . 84 Logical Drives . . . . . . . . . . . . . . . . 74, 110
System Log . . . . . . . . . . . . . . . . . . . . . . . . . 75
M
T
Media Verification. . . . . . . . . . . . . . . . . . . . . 17
Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . 73
P U
PFA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Uninstallation
PFA Count/S.M.A.R.T. . . . . . . . . . . . . 127, 134 GAM . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 GAM Client . . . . . . . . . . . . . . . . . . . . . 100
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 GAM Server . . . . . . . . . . . . . . . . . . . . . 101
ServerView RAID . . . . . . . . . . . . . . . . . . 63
User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
R User Privileges . . . . . . . . . . . . . . . . . . . . . . 58
RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
RAID Levels. . . . . . . . . . . . . . . . . . . . . . . . . 13 V
Rebuild . . . . . . . . . . . . . . . . . . . . . 16, 79, 121
Checking the Progress(GAM). . . . . . . . 120 View Menu. . . . . . . . . . . . . . . . . . . . . . . . . 107
Checking the Progress(ServerView RAID)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Rebuild Status . . . . . . . . . . . . . . . . . . . 120
S
S.M.A.R.T. . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Server group and server settings . . . . . . . . 111
Server Icon . . . . . . . . . . . . . . . . . . . . . 73, 105
Server Selection Box . . . . . . . . . . . . . . . . . 104
ServerView . . . . . . . . . . . . . . . . . . . . . . . . . 91
ServerView AlarmService . . . . . . . . . . . 60, 95
ServerView RAID
174
Integrated Mirroring SAS
User's Guide
B7FY-2311-01ENZ0-00
Issued on January, 2008
Issued by FUJITSU LIMITED
• The contents of this manuals 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.

B7fy 2311 01en

Uploaded by

Copyright:

Available Formats

B7fy 2311 01en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B7fy 2311 01en

Uploaded by

Copyright:

Available Formats

Integrated Mirroring SAS User's Guide

Before Reading This Manual

 Key descriptions / operations

 CD/DVD drive descriptions

 Entering commands (keys)

 Screen shots and figures

Microsoft® Windows Server® 2003, Standard x64 Edition Windows Server

Microsoft® Windows® 2000 Server Windows 2000 Server

Microsoft® Windows® 2000 Professional Windows 2000 Professional

Microsoft® Windows® XP Professional Windows XP

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 SLES9 or SUSE Linux

 Information for PRIMERGY

All Rights Reserved, Copyright© FUJITSU LIMITED 2008

Screen shot(s) reprinted with permission from Microsoft Corporation.

Chapter 2 Array Configuration and Management [BIOS Utility]

Chapter 4 Array Configuration and Management

Chapter 5 Array Configuration and Management [GAM]

5.3 Starting and Exiting GAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 6 Replacing Hard Disk

This chapter describes an overview,

1.1 Array Controller Work Flow . . . . . . . . . . . . . . . . . . . . . . . 10

1.1 Array Controller Work Flow

The work flow when using a disk array controller is as follows:

１. Designing the Disk Array

２. Configuring the Disk Array

４. Installing the Management Tools

５. Updating the Device Drivers

６. Preparing the Environment for the Management Tools

１. Designing the Disk Array

２. Configuring the Disk Array

４. Installing the Management Tools

５. Preparing the Environment for the Management Tools

1.2 Overview of the Disk Array

1.2.1 Array controller specifications

[Note 1]: It is installed on the baseboard of the server.

1.2.2 What is Disk Array?

1.2.3 RAID Levels

There are several types of RAID levels, with different characteristics.

1.2.4 Logical Drive

Hard disk 1 Hard disk 2

 Status during hard disk failure

1.2.5 Checking Hard Disk Status

 Logical drive status

 Hard disk status

1.3 Disk Array Configuration Features

This section explains the features in disk array configuration.

1.3.1 Logical Drive Initialization

 Estimated time for rebuild

1.3.3 Media Verification

1.3.4 Hard Disk Failure Prediction Function (PFA /

1.4 Notes before Operation

Check the following before starting the operation.

1.4.1 Cautions When Using This Product

The usage may be limited depending on the server to be installed in.

Key descriptions / operations

CD/DVD drive descriptions

Entering commands (keys)

Screen shots and figures

Information for PRIMERGY

Status during hard disk failure

Logical drive status

Hard disk status

Estimated time for rebuild

Information on logical drives

Information on hard disks