Universal RAID Utility
(VMware Version)
User's Guide
1st Edition
February 2009
808-882328-750-A
Trademarks
NEC ESMPRO and NEC EXPRESSBUILDER are trademarks of NEC Corporation.
VMware is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions.
All other product, brand, or trade names used in this publication are the trademarks or registered trademarks of their
respective trademark owners.
Notes
1.
No part of this manual may be reproduced in any form without the prior written permission of NEC
Corporation.
2.
The contents of this manual may be revised without prior notice.
3.
The contents of this manual shall not be copied or altered without the prior written permission of NEC
Corporation.
4.
All efforts have been made to ensure the accuracy of all information in this manual. If you notice any part
unclear, incorrect, or omitted in this manual, contact the sales agent where you purchased this product.
5.
NEC assumes no liability arising from the use of this product, nor any liability for incidental or consequential
damages arising from the use of this manual regardless of Item 4.
2
Introduction
This User’s Guide describes RAID System management utility "Universal RAID Utility".
See "Appendix A : Glossary" for the terms on the Universal RAID Utility and those used in this User’s Guide.
Before the Universal RAID Utility can be used, you should carefully read the User’s Guide of the RAID System
managed by the Universal RAID Utility and that of the computer in which the RAID System is installed.
The User’s Guide is intended to be read by engineers who are fully familiar with the functions and
operations of VMware ESX Server. Refer to the online help and related documentation for the operations and
concerns of VMware ESX Server.
Symbols used in the text
The User’s Guide uses the following three symbols. Follow these symbols and their meanings to use the
Universal RAID Utility appropriately.
Symbol
Description
Indicates a matter or caution you should particularly obey on operations of the Universal RAID
Utility.
Indicates a notice you should check to operate the Universal RAID Utility.
Indicates effective or convenient information which help you if you know them.
3
Contents
Overview
7
What is Universal RAID Utility?
Structure of Universal RAID Utility
7
8
Setup of Universal RAID Utility
9
Operation Environments
9
Hardware
Software
Others
9
9
9
Installation and Uninstallation
11
Setup Program
New Installation
Update Installation
Uninstallation
12
12
12
13
Starting or Stopping Universal RAID Utility
raidsrv service
14
14
Starting Universal RAID Utility in Single User Mode
14
raidcmd
Standard and Advanced Modes
14
15
Running Mode when startup
Changing Running Mode
15
16
Functions of raidcmd
17
Command Line
Returned Value from raidcmd
Error Messages of raidcmd
Commands of raidcmd
17
17
17
17
Referring to Information on RAID System
Referring to Property of RAID Controller
Referring to Property of Logical Drive
Referring to Property of Physical Device
Referring to Property of Disk Array
Checking Execution Status of Operation
Referring to RAID System Operation Log
18
18
19
20
21
22
22
Configuration of RAID System
23
Making Hot Spare
24
About Global Hot Spare
About Dedicated Hot Spare
Making Global Hot Spare
Making Dedicated Hot Spare
Removing Hot Spare
24
25
26
26
27
Configuring RAID System Easily
28
Procedure of Easy Configuration of RAID System
RAID Controller Enabling Easy Configuration to Be Executed
Physical Devices Available for Easy Configuration
4
28
29
30
Creating Logical Drives by Easy Configuration
Making Hot Spares by Easy Configuration
30
32
Creating Logical Drive Easily
34
Operation Procedure of "Create Logical Drive - Simple Mode"
Physical Devices Available for "Create Logical Drive - Simple Mode"
Creating Logical Drives by "Create Logical Drive - Simple Mode"
Creating Logical Drive Freely
Operation Procedure of "Create Logical Drive - Custom Mode"
Disk Arrays and Physical Devices Available for "Create Logical Drive - Custom Mode"
Creating Logical Drives by "Create Logical Drive - Custom Mode"
34
35
35
36
36
37
37
Deleting Logical Drive
39
Deleting Logical Drive
39
Maintenance of RAID System
40
Providing Patrol Read for Physical Devices
40
Setting Whether Patrol Read Is Executed or Not
Checking Result of Executing Patrol Read
Setting Patrol Read Priority
40
40
40
Checking Logical Drive Consistency
42
Executing Consistency Check Manually
Executing Consistency Check for arbitrary Logical Drive
Stopping Consistency Check
Checking Result of Executing Consistency Check
Setting Consistency Check Priority
Initializing Logical Drive
42
42
43
43
43
45
Executing Initialization
Stopping Initialization
Checking Result of Executing Initialization
Setting Initialization Priority
45
46
46
46
Rebuilding Physical Device
48
Executing Rebuild
Stopping Rebuild
Checking Result of Executing Rebuild
Setting Rebuild Priority
48
48
49
49
Checking Location of Physical Device
50
Procedure of Checking Location of Physical Device
Changing Status of Physical Device Forcibly
To [Online] Forcibly
To [Failed] Forcibly
51
51
52
Troubleshooting RAID System
53
Failure Detection Measures
54
Status Display by raidcmd
Logging Events to RAID Log
Buzzer in RAID Controller
Logging Events to OS Log
Sending Alert to NEC ESMPRO Manager
54
54
54
54
54
Monitoring Faults of Physical Devices
Operation
Operation
Operation
Operation
50
56
in no failures of Physical Devices
when redundancy of Logical Drive degraded or lost due to failure of Physical Device
when failed Physical Device is replaced to recover RAID System
when the Logical Drive is offline due to failure of Physical Device
Monitoring Battery Status
Operation when battery operates normally
Operation when battery does not operate normally
Monitoring Enclosure Status
Monitoring Various Events of RAID System
Replacing Physical Device for Prevention
5
57
58
60
61
62
62
62
63
63
63
Operation in no detection of S.M.A.R.T. error
Operation when S.M.A.R.T. error is detected
64
64
Changing of Settings of Universal RAID Utility
Changing TCP port number
65
65
raidcmd Command Reference
66
cc
ccs
delld
econfig
hotspare
init
mkldc
mklds
oplist
optctrl
optld
property
rebuild
runmode
sbuzzer
slotlamp
stspd
66
66
66
67
67
68
68
70
71
71
72
73
73
74
74
74
75
Notes on Use of Universal RAID Utility
76
Operation Environment
76
Use of IPv6
76
Appendix A : Glossary
77
Basic Terms on RAID System
Basic Terms on Functions of RAID System
Basic Terms on Universal RAID Utility
77
78
78
Appendix B : Logs/Events
79
6
Overview
This chapter describes the overview of the Universal RAID Utility.
What is Universal RAID Utility?
The Universal RAID Utility enables RAID Systems in a computer to be managed.
The Universal RAID Utility is characterized as follows.
1. Allowing a variety of RAID Systems to be managed
Conventionally, a specific management utility must be used for each RAID System. On the other
hand, only the Universal RAID Utility can manage more than one RAID System. For the RAID
Systems which the Universal RAID Utility can manage, refer to the documentation on computers
and RAID Systems.
2. Operating in either Standard or Advanced Mode
The Universal RAID Utility can operate in two running modes, which are Standard Mode and
Advanced Modes.
The Standard Mode provides the Universal RAID Utility with standard management functions of
RAID Systems.
The Advanced Mode provides the Universal RAID Utility with advanced management and
maintenance functions of RAID Systems.
Using the two running modes appropriately depending on users and jobs allows the usability of the
Universal RAID Utility to be improved and malfunctions to be avoided.
3. Configuring RAID Systems easily
Using the Universal RAID Utility, you can configure a RAID System easily without expert knowledge
of the RAID System.
The Universal RAID Utility provides the "simple Logical Drive create function" allowing a Logical
Drive to be created by selecting only two selection items according to the guide of the Universal
RAID Utility and the "Easy Configuration" allowing a RAID System to be configured only by defining
uses of unused Physical Devices.
4. Supporting general functions required for configurations, operations and maintenances of RAID
Systems
The Universal RAID Utility supports general functions for configuring a RAID System (including
creating Logical Drive and making Hot Spare), general operation functions (including log recording,
Patrol Read and Consistency Check), and general functions required for maintenance (including
Rebuild and Locate functions).
5. Troubleshooting RAID Systems
The Universal RAID Utility can detect failures occurred in RAID Systems by using various functions.
The raidcmd, the CLI of the Universal RAID Utility, indicates the configurations and status of RAID
Systems comprehensibly. In addition, the Universal RAID Utility registers failures occurred in RAID
Systems not only to the dedicated log but also the log of VMware ESX Server. Further, the Universal
RAID Utility can send alerts to the NEC ESMPRO Manager normally attached to NEC Express series
systems.
7
Structure of Universal RAID Utility
The Universal RAID Utility consists of the following modules:
raidsrv service
The raidsrv service always operates in the computer to manage RAID Systems. Receiving a
processing request from the raidcmd, the raidsrv service provides proper information on a RAID
System or performs an appropriate operation for the RAID System. In addition, the raidsrv service
manages events occurred in RAID Systems, registers them to several logs.
raidcmd
The raidcmd is the application managing and monitoring the RAID system by CLI.
The raidcmd is the command that indicates the configuration and status of a RAID System or
operates on a console providing configurations and operations.
Universal RAID Utility
Computer
raidcmd
RAID Log
raidsrv
service
RAID System
Figure 1 Configuration of Universal RAID Utility
8
Setup of Universal RAID Utility
This chapter describes installation or uninstallation of the Universal RAID Utility.
Operation Environments
The Universal RAID Utility can operate in the following environments.
Hardware
Computers
The computers can contain RAID Systems to be managed by the Universal RAID Utility.
RAID Systems to be managed by Universal RAID Utility
For RAID Systems which can be managed by the Universal RAID Utility, refer to the documentation
attached to the computer in which RAID Systems are installed and that attached to the RAID
Controller including the Universal RAID Utility.
Software
VMware ESX Server
The Universal RAID Utility can operate in the following VMware ESX Server.
VMware ESX 3.5 Update 1 or later
You must install the Universal RAID Utility in the ESX Server. Don't install in the virtual machine.
Single user mode
The Universal RAID Utility uses network functions. Accordingly, the Universal RAID Utility cannot be
used in the single user mode without network functions. For how to use the Universal RAID Utility in
the single user mode, see "Starting Universal RAID Utility in Single User Mode".
Others
System Requirements
Resource
VMware ESX Server 3
Available Hard Disk Space
50MB or more
RAM
512MB or more
9
TCP ports used by Universal RAID Utility
The Universal RAID Utility uses the following two TCP ports.
TCP ports used by Universal RAID Utility
52805 and 52806
For the change of TCP ports number using Universal RAID Utility, see "Changing TCP port number".
10
Installation and Uninstallation
This section describes the procedure of installation and uninstallation of Universal RAID Utility on VMware
ESX Server.
In order to install or uninstall Universal RAID Utility, you can use "setup.sh" as setup program of Universal
RAID Utility. You must select the option parameter of setup.sh by either Installation or Uninstallation. If
you want to install Universal RAID Utility, the setup program checks whether the Universal RAID Utility
exists in the computer in which RAID Systems are used.
The procedure of Installation and Uninstallation is below.
You must install the Universal RAID Utility in the ESX Server. Don't install in the
virtual machine.
Start Installation or
Uninstallation
Which do you execute ?
Uninstallation
Installation
Uninstallation
Uninstallation
(use setup.sh)
No
Universal RAID Utility
exist ?
New Installation
エラー! 参照元が見つかりませ
ん。
Yes
New Installation
(use setup.sh)
Older Version
Universal RAID Utility
exist ?
Yes
Update Installation
Update Installation
(use setup.sh)
No
End Installation or
Uninstallation
Figure 2 The procedure of Installation/Uninstallation
11
Setup Program
The setup program is contained in the installation image of the Universal RAID Utility. Before the
Universal RAID Utility can be installed or uninstalled, you must prepare the installation image.
The procedure for starting Setup Program of Universal RAID Utility is below.
Step 1 Log in to the computer with administrator authority to install or uninstall Universal RAID
Utility.
Press Alt key and F1 key at boot screen of VMware ESX Server to switch to service
console. Log in to VMware ESX Server with administrator authority to install or
uninstall Universal RAID Utility.
Step 2
See the "Figure 2 The procedure of Installation/Uninstallation" about next step.
New Installation
Use setup.sh in the install image for the installation of Universal RAID Utility newly.
Step 1
Execute setup.sh in the
installation image.
Change the current directory to the
directory in which the installation
image is stored and type as follows:
sh setup.sh --install
> cd directory name involved install image
> sh setup.sh --install
>
> rpm -q UniversalRaidUtility
2
UniversalRaidUtility-1.xx-y
>
> rpm -q storelib
storelib-2.zz-0
>
1
Step 2 At the end of setup.sh, the
installation is completed. Check the
result of the installation by using the rpm command. When the installation is completed properly, the
following two packages are installed:
UniversalRAIDUtility-1.xx-y (xx is minor version, y is revision number) and
storelib-2.zz-0. (zz is minor version)
If the installation fails, these packages do not exist in the computer.
Update Installation
The Setup Program execute the Update Installation when there is the old version of Universal RAID
Utility in the computer. The Setup Program use the following setting continuously.
■
■
■
■
The contents of RAID log
TCP port using Universal RAID Utility
The running mode of raidcmd
The scheduled task of consistency check in crontab of VMware ESX Server 3
See "New Installation" about the procedure of Update Installation.
12
Uninstallation
Use setup.sh in the install image for the uninstallation of Universal RAID Utility.
Step 1 Execute setup.sh in the
installation image.
Change the current directory to the
directory in which the installation
image is stored and type as follows:
sh setup.sh --uninstall
> cd directory name involved install image
> sh setup.sh --uninstall
1
>
> rpm -q UniversalRaidUtility
error: package UniversalRaidUtility is not installed
>
> rpm -q storelib
error: package storelib is not installed
>
Step 2 At the end of setup.sh, the
uninstallation is completed. Check the
result of the uninstallation by using the
rpm command. When the uninstallation is completed properly, the following two packages are
uninstalled:
UniversalRaidUtility-1.xx-y (xx is minor version, y is revision number) and
storelib-2.zz-0. (zz is minor version)
13
2
Starting or Stopping Universal RAID
Utility
This chapter describes the procedure of starting or stopping each module in the Universal RAID Utility.
raidsrv service
The raidsrv service is started automatically when your computer is booted and stopped automatically
when your computer is shut down.
Without operation of the raidsrv service, the Universal RAID Utility cannot operate normally. Neither make
the raidsrv service be not started nor stop the raidsrv service.
If the raidsrv service terminates abnormally due to occurrence of an error or a process of
the raidsrv service is terminated forcibly, the lock file for avoiding double starts is left. If
the state remains, the raidsrv service may not be started.
If this occurs, delete the following file before restarting the raidsrv service:
/var/lock/subsys/raidsrv
Starting Universal RAID Utility in Single User Mode
The Universal RAID Utility uses network functions. Accordingly, the Universal RAID Utility cannot be
used in the single user mode without network functions. To use the Universal RAID Utility in the single
user mode, first enable the network functions in the following procedure and start the raidsrv service.
Step 1
Start the network service.
Step 2
Start the raidsrv service.
Step 3 Check that the raidsrv service
is started normally.
If a process ID appears, the raidsrv
service is started normally.
> /etc/init.d/network start
1
>
> /etc/init.d/raidsrv start
>
> /etc/init.d/raidsrv status
raidsrv (pid 3738 3718) is running...
>
2
3
raidcmd
raidcmd is command on console.
The raidcmd is executed on a console. Use the raidcmd by the methods described in "Functions of
raidcmd".
A user having the administrator authority should run the raidcmd. Only users having the
administrator authority can execute the raidcmd.
14
Standard and Advanced Modes
The raidcmd can operate in two running modes, which are Standard Mode and Advanced Modes.
The Standard Mode provides the raidcmd with standard management functions for RAID Systems.
The Advanced Mode provides the raidcmd with advanced management and maintenance functions for
RAID Systems.
Using the two running modes appropriately depending on users and jobs allows the usability of the
raidcmd to be improved and malfunctions to be avoided.
The table below lists the functions of the raidcmd available in each mode.
Function
raidcmd
Standard
Advanced
command
mode
mode
See property
property
Create Logical Drive (simple)
mklds
Create Logical Drive (custom)
mkldc
Silence Buzzer
sbuzzer
Consistency Check (start)
cc
Consistency Check (stop)
cc
Consistency Check (start)
for schedule running
ccs
Initialization (start)
init
Initialization (stop)
init
Delete Logical Drive
delld
Rebuild (start)
rebuild
Rebuild (stop)
rebuild
Hot Spare (make)
hotspare
Hot Spare (remove)
hotspare
Change Status of Physical Device
(Online)
stspd
Change Status of Physical Device (Failed)
stspd
Location of Physical Device
slotlamp
Easy Configuration
econfig
Change running mode
runmode
See the version
run raidcmd without
command
See status of operation
oplist
Set option parameters of RAID Controller
optctrl
Set option parameters of Logical Drive
optld
Functions other than above
Running Mode when startup
raidcmd starts with Standard Mode at first after installing Universal RAID Utility. If you want to change
the running mode, you must to use the "runmode" command (The running mode doesn't change the
mode when restart the computer).
15
Changing Running Mode
The procedure of changing the running mode is below.
raidcmd
You can change the running mode by the "runmode" command.
Step 1
If you want to change
from Standard Mode to
Advanced Mode, run the
"runmode" command with
-md=a parameter.
> raidcmd runmode -md=a
Changed running mode to "Advanced Mode".
>
>
> raidcmd runmode -md=s
Changed running mode to "Standard Mode".
>
Step 2
If you want to change
from Advanced Mode to
Standard Mode, run the "runmode" command with -md=s parameter.
16
1
2
Functions of raidcmd
This chapter describes the functions of the raidcmd.
Command Line
To use the raidcmd, specify a command and one or more parameters for the command if necessary.
> raidcmd (command) (parameters of command)
To use the raidcmd, you should log in to the computer as a user having the administrator
authority. Only users having the administrator authority can execute the raidcmd.
Executing the raidcmd without any command and its parameters indicates the version of
the raidcmd.
Returned Value from raidcmd
The returned value of the raidcmd is the result of executing the command.
Returned value
Execution result
0
Normal termination of command
1
Abnormal termination of command
Error Messages of raidcmd
When a command of the raidcmd terminates abnormally, the relevant error message appears in the
following format:
> raidcmd (command) (parameters of command)
raidcmd : error message
>
Commands of raidcmd
See "raidcmd Command Reference" for commands of the raidcmd.
17
Referring to Information on RAID
System
This chapter describes how to see the configurations and status of RAID Systems and the RAID System
operation log.
Referring to Property of RAID Controller
For the information on a RAID Controller, see the property of the RAID Controller.
Use the "property" command to see the
property of a RAID Controller.
> raidcmd property -tg=rc -c=1
RAID Controller #1
ID
: 0
Vendor
: LSI Corporation
Model
: MegaRAID SAS PCI Express(TM) ROMB
Firmware Version
: 1.12.02-0342
Cache Size
: 128MB
Battery Status
: Normal
Rebuild Priority
: High
Consistency Check Priority : Low
Patrol Read
: Enable
Patrol Read Priority
: Low
Buzzer Setting
: Enable
>
Item
raidcmd
Description
RAID Controller #X
Indicates the management number (logical address) of the RAID Controller in the
Universal RAID Utility.
The Universal RAID Utility assigns a number beginning with 1 for each RAID
Controller.
ID
Indicates the original identification value of the RAID Controller. The BIOS utility of
the RAID Controller uses the address of the identification value.
Vendor
Indicates the vendor of the RAID Controller.
Model
Indicates the model name of the RAID Controller.
Firmware Version
Indicates the version of the RAID Controller.
Cache Size
Indicates the size of cache on RAID Controller in MB.
Universal RAID Utility Ver1.20 or later version allows this item.
Battery Status
Indicates the status of the battery installed in the RAID Controller.
Three possible status are as follows:
Normal: Indicates that the battery can be used normally。
Warning: Indicates that the battery cannot be used normally due to some reason.
Not Present: Indicates that no battery is installed in the RAID Controller.
Initialize Priority
Indicates the priority level of Initialize executed in the computer system.
Three possible Initialize Priorities are as follows:
High: Executes Initialize at high priority.
Middle: Executes Initialize at balanced priority.
Low: Executes Initialize at low priority.
Rebuild Priority
Indicates the priority level of Rebuild executed in the computer system.
Three possible Rebuild Priorities are as follows:
High: Executes Rebuild at high priority.
Middle: Executes Rebuild at balanced priority.
Low: Executes Rebuild at low priority.
18
Item
raidcmd
Description
Consistency Check Priority
Indicates the priority level of Consistency Check executed in the computer system.
Three possible Consistency Check Priorities are as follows:
High: Executes Consistency Check at high priority.
Middle: Executes Consistency Check at balanced priority.
Low: Executes Consistency Check at low priority.
Patrol Read
Indicates whether Patrol Read is executed or not.
Enable: Executes Patrol Read.
Disable: Does not execute Patrol Read.
Patrol Read Priority
Indicates the priority level of Patrol Read executed in the computer system.
Three possible Patrol Read Priorities are as follows:
High: Executes Patrol Read at high priority.
Middle: Executes Patrol Read at balanced priority.
Low: Executes Patrol Read at low priority.
Buzzer Setting
Indicates whether the Buzzer of the RAID Controller is used if a failure occurs in
the RAID System.
Enable: Uses the Buzzer.
Disable: Does not use the Buzzer.
RAID Controllers of some types do not support items appearing in the properties of RAID
Controllers and/or items whose settings can be changed. Unsupported items indicate
space or do not appear in the list.
Referring to Property of Logical Drive
For the information on a Logical Drive, see the property of the Logical Drive.
Use the "property" command to see the
property of a Logical Drive.
> raidcmd property -tg=ld -c=1 -l=1
RAID Controller #1 Logical Drive #1
ID
: 0
Physical Device Number
: 1, 2, 3
Disk Array Information
: 1 (order 1/1)
RAID Level
: RAID 5
Capacity
: 20GB
Stripe Size
: 64KB
Cache Mode (Current)
: Write Back
Cache Mode (Setting)
: Auto Switch
Status
: Online
>
Item
raidcmd
Description
RAID Controller #X
Logical Drive #Y
Indicates the management number (logical address) of the Logical Drive in the
Universal RAID Utility.
The Universal RAID Utility assigns a number beginning with 1 in correspondence
with the value of [ID].
ID
Indicates the original identification value of the Logical Drive. Use this value to
create Logical Drives managed by the BIOS utility of the RAID Controller
correspond with those managed by the Universal RAID Utility.
Physical Device Number
Indicates the numbers of Physical Devices configuring the Disk Array in which the
Logical Drive exists.
Disk Array Information
Indicates the number of the Disk Array in which the Logical Drive exists and the
information on the location in the Disk Array. The information is displayed in the
following format.
Disk Array number (order sequence number starting from the top / sequence
number of Logical Drive in Disk Array)
RAID Level
Indicates the RAID Level of the Logical Drive.
19
Item
raidcmd
Description
The value can be RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, or RAID 50.
Capacity
Indicates the capacity of the Logical Drive in GB.
Stripe Size
Indicates the Stripe Size of the Logical Drive.
The value can be 1KB, 2KB, 4KB, 8KB, 16KB, 32KB, 64KB, 128KB, 256KB,
512KB, or 1024KB.
Cache Mode (Current)
Indicates the current value of the mode of writing data to the cache memory
installed in the RAID Controller.
Three possible modes are as follows:
Write Back: Writes data to the cache memory asynchronously.
Write Through: Writes data to the cache memory synchronously.
Cache Mode (Setting)
Indicates the mode of writing data to the cache memory installed in the RAID
Controller.
Three possible modes are as follows:
Auto Switch: Switches the mode automatically between Write Back and Write
Through depending on the existence and/or status of battery.
Write Back: Writes data to the cache memory asynchronously.
Write Through: Writes data to the cache memory synchronously.
Status
Indicates the status of the Logical Drive.
Three possible status are as follows:
Online: Indicates that the redundancy of the Logical Drive is retained.
Degraded: Indicates that the redundancy of the Logical Drive is lost or degraded.
Accessing to the Logical Drive is enabled.
Offline: Indicates that the Logical Drive is offline and accessing to the Logical
Drive is disabled.
Each RAID Controller supports specific RAID Levels and Stripe Sizes. Unsupported
items indicate space or do not appear in the list.
Each RAID Controller supports specific Cache Modes. Unsupported Cache Modes do not
appear.
Each RAID Controller supports specific items appearing on the Property tab of the
Logical Drive and specific items whose settings can be changed. Unsupported items
indicate space or do not appear in the list.
Referring to Property of Physical Device
For the information on a Physical Device, see the property of the Physical Device.
Use the "property" command to see the
property of a physical drive.
> raidcmd property -tg=pd -c=1 -p=1
RAID Controller #1 Physical Device #1
ID
: 0
Enclosure
: 1
Slot
: 1
Interface
: SAS
Vendor/Model
: SEAGATE ST936751SS
Firmware Version
: 0001
Serial Number
: 3PE073VM
Capacity
: 33GB
Status
: Online
S.M.A.R.T.
: Normal
>
Item
raidcmd
RAID Controller #X
Physical Device #Y
Description
Indicates the management number (logical address) of the Physical Device in the
Universal RAID Utility.
The Universal RAID Utility arranges Physical Devices in the ascending order of IDs
and assigns a number beginning with 1 sequentially to the Physical Devices.
20
Item
raidcmd
Description
ID
Indicates the original identification value of the Physical Device. Use this value to
make Physical Devices managed by the BIOS utility of the RAID Controller
correspond with those managed by the Universal RAID Utility.
The format of the ID varies depending on the types of RAID Controllers.
Enclosure
Indicates the number of Enclosure inserted Physical Device.
This value is a number beginning with 1.
Slot
Indicates the number of Slot inserted Physical Device.
This value is a number beginning with 1.
Interface
Indicates the type of the interface to which the Physical Device is connected.
Two possible types are as follows:
SAS : Serial Attached SCSI
SATA : Serial ATA
Vendor/Model
Indicates the vendor and model name of the Physical Device.
Firmware Version
Indicates the version of the Physical Device.
Serial Number
Indicates the serial number of the Physical Device.
Capacity
Indicates the capacity of the Physical Device in GB.
Status
Indicates the status of the Physical Device.
Five possible status are as follows:
Online: Indicates that the Physical Device is incorporated into a Logical Drive to
operate normally.
Failed: Indicates that the Physical Device is incorporated into a Logical Drive but
is failed.
Rebuilding: Indicates that the Physical Device is rebuilding.
Hot Spare: Indicates that the Physical Device is set as a Hot Spare.
Ready: Indicates that the Physical Device is not incorporated into a Logical Drive.
Hot Spare Information
Indicates the Hot Spare mode of the Physical Device if it is specified as a Hot
Spare.
Two possible modes are as follows:
Global: The Physical Device can be used as a Hot Spare of any Disk Array in the
RAID Controller.
Dedicated: The Physical Device can be used as a Hot Spare of the specified Disk
Array. Also indicates the number of the specified Disk Array.
S.M.A.R.T.
Indicates the diagnosis result of the S.M.A.R.T. (Self-Monitoring, Analysis and
Reporting Technology) function. Two possible statuses are as follows.
Normal: Does not detect any error caused by the S.M.A.R.T. function.
Detected: Detects one or more errors caused by the S.M.A.R.T. function.
Each RAID Controller supports specific items appearing on the Property tab of the
Physical Device and specific items whose settings can be changed. Unsupported items
indicate space or do not appear in the list.
Even if Physical Device does not break down when you execute Make Offline, [Status]
item is changed to [Failed].
Referring to Property of Disk Array
For the information on a Disk Array, see the property of the Disk Array. raidcmd allows the displaying of
the property of Disk Array only.
Use the "property" command to see the
property of a Disk Array.
> raidcmd property -tg=da -c=1 -a=1
RAID Controller #1 Disk Array #1
Physical Device Number
: 1, 2, 3
Capacity
: 67GB
Unused Capacity
: 47GB
>
21
Item
Description
raidcmd
RAID Controller #X
Disk Array #Y
Indicates the management number (logical address) of the Disk
Array in the Universal RAID Utility.
Physical Device Number
Indicates the numbers of Physical Devices configuring the Disk
Array.
Capacity
Indicates the capacity of the Disk Array in GB.
Unused Capacity
Indicates the total capacity of unused area in the Disk Array in GB.
Checking Execution Status of Operation
The raidcmd allows the checking execution status of operation in the RAID System.
To check the execution status of operation
by raidcmd, use the "oplist" command.
The following operations are displayed by
the "oplist" command. The target
components and status appear in
operations:
Initialize
> raidcmd oplist
RAID Controller #1
Logical Drive #1 : Consistency Check (52%)
Logical Drive #2 : Initialize (33%)
Physical Device #1(0): Rebuild (99%)
RAID Controller #2
Logical Drive #1 : Consistency Check (2%)
Physical Device #2(1): Rebuild (22%)
>
Rebuild
Consistency Check
The operation performed at execution of the raidcmd appears. Terminated operations do not appear. For
the results of terminated operations, see the RAID Log and/or properties.
Physical Device has two numbers on oplist.
Physical Device #M(N)
M : The number of Physical Device
N : ID of Physical Device
Referring to RAID System Operation Log
Operations done for RAID Systems and events occurred in the RAID Systems are registered to the RAID
Log of the Universal RAID Utility. See "Logging Events to RAID Log" for detail.
Use text editor or otherwise to refer to RAID Log.
22
Configuration of RAID System
This chapter describes the configuration of a RAID System by using the Universal RAID Utility.
The Universal RAID Utility provides a variety of functions depending on purposes.
Would like to make
Hot Spare as
measures against
failure of Physical
Device.
Would like to
configure RAID
System easily due to
no expert knowledge
of RAID System.
Allows Global or Dedicated
Hot Spare to be made
without errors.
See "Making Hot Spare".
See "Configuring RAID
System Easily".
Provides "Easy Configuration"
allowing RAID System to be
configured without expert
knowledge of RAID System.
See "Creating Logical
Drive Easily".
Would like to add a
Logical Drive easily.
Allows Logical Drive to be
made only by setting two
selection items.
Would like to specify
configuration of
Logical Drive closely
or create more than
one Logical Drive at a
time.
Would like to delete
unnecessary Logical
Drive. However, it is
anxious about
destruction of system
by mistake.
See "Creating Logical
Drive Freely".
Allows information on
Logical Drive to be set
closely or more than one
Logical Drive to be created
at a time at will.
See "Deleting Logical
Drive".
Disables Logical Drive
containing boot partition
to be deleted by mistake.
Figure 3 RAID System configuration functions
23
Making Hot Spare
The Universal RAID Utility can make a Hot Spare to be replaced with a Physical Device in which a failure
occurs.
Hot spares can have the following two modes.
Mode
Global (Hot Spare)
Dedicated (Hot Spare)
Description
Available as a Hot Spare of every Disk Array for a single RAID Controller.
Available as a Hot Spare of a specific Disk Array for a single RAID Controller.
In either mode, note the following to have a Hot Spare operate normally.
A Hot Spare can operate properly only for a Disk Array configured with Physical Devices of the same
interface type.
A Hot Spare can operate properly only if the Hot Spare has the capacity equal to or larger than that
of the Physical Device in which a failure occurs.
A Physical Device in which a S.M.A.R.T. error is detected cannot be used as a Hot Spare.
About Global Hot Spare
Global Hot Spare is a Hot Spare of every Logical Drives for a single RAID Controller.
Ex.1 : If you make the Global Hot Spare on the RAID Controller which has Logical Drive #1 and #2,
the Global Hot Spare is a Hot Spare of Logical Drive #1 and #2.
Logical Drive Logical Drive
#1
#2
Global Hot
Spare
Figure 4 Global Hot Spare 1
Ex.2 : If you create the Logical Drive #3 on the RAID System of Ex.1, the Global Hot Spare is a Hot
Spare for the Logical Drive #3 too.
Logical Drive Logical Drive
#1
#2
Logical Drive
#3
Global Hot
Spare
Figure 5 Global Hot Spare 2
24
About Dedicated Hot Spare
Dedicated Hot Spare is a Hot Spare of specified Logical Drives for a single RAID Controller. The
Dedicated Hot Spare features the following :
Dedicated Hot Spare is a Hot Spare of specified Logical Drives.
One Dedicated Hot Spare can be a Hot Spare of one or more Logical Drives.
One or more Dedicated Hot Spare can be a Hot Spare of one or more Logical Drives.
Dedicated Hot Spares cannot be created in a Disk Array containing Logical Drives
with the RAID Level being RAID 0.
Ex 1 : You make the Dedicated Hot Spare on the RAID Controller which has Logical Drive #1 and #2.
If you specify only the Logical Drive #1 as the target Logical Drive, the Dedicated Hot Spare is
a Hot Spare of Logical Drive #1.
Logical Drive Logical Drive
#1
#2
Dedicated
Hot Spare
Figure 6 Dedicated Hot Spare 1
Ex 2 : In case of the RAID System in Ex1, If you specify the Logical Drive #1 and #2 as the target
Logical Drive, the Dedicated Hot Spare is a Hot Spare of Logical Drive #1 and #2.
Logical Drive
#1
Logical Drive
#2
Dedicated
Hot Spare
Figure 7 Dedicated Hot Spare 2
Ex 3 : In case of the RAID System in Ex1, you can add more Dedicated Hot Spare . If you add the
Dedicated Hot Spare #2 to the Logical Drive #1, the both Dedicated Hot Spare are the Hot
Spare for the Logical Drive #1.
Logical Drive Logical Drive
#1
#2
Dedicated
Hot Spare #1
Figure 8 Dedicated Hot Spare 3
25
Dedicated
Hot Spare #2
Ex 4 : In case of the RAID System in Ex2, you can add more Dedicated Hot Spare likely Ex2. If you
add the Dedicated Hot Spare to the Logical Drive #1 and #2, the both Dedicated Hot Spare
are the Hot Spare for the Logical Drive #1 and #2.
Logical Drive Logical Drive
#1
#2
Dedicated
Hot Spare #1
Dedicated
Hot Spare #2
Figure 9 Dedicated Hot Spare 4
Making Global Hot Spare
The procedure of making a Global Hot Spare is described below.
raidcmd
Use the "hotspare" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device with which
a Hot Spare is made
Physical Device
Number of the Physical Device with which a Global Hot Spare is made
Step 1
Execute the "hotspare"
command with -mr option and
the following parameters.
> raidcmd hotspare -c=1 -p=6 -mr=make
Make Global Hot Spare.
1
Do you continue ? [yes(y) or no(n)] : yes
>
Step 2
If you see the property
of the Physical Device after
making the Global Hot Spare,
you find that the value of
[Status] is changed to [Hot
Spare] and new item [Hot Spare
Information] appears with value
[Global].
> raidcmd property -tg=pd -c=1 -p=6
2
RAID Controller #1 Physical Device #6
ID
: 5
Enclosure
: 1
Slot
: 6
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Hot Spare
Hot Spare Information
: Global
S.M.A.R.T.
: Normal
>
Making Dedicated Hot Spare
The procedure of making a Dedicated Hot Spare is described below.
raidcmd
Use the "hotspare" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device with which
a Hot Spare is made
26
Item
Description
Physical Device
Number of the Physical Device with which a Dedicated Hot Spare is
made.
The capacity of the Physical Device should be equal to or larger than any
Physical Device used by the target Disk Array.
Disk Array
Number of the target Disk Array using the Dedicated Hot Spare
Step 1
Execute the "hotspare"
command with -mr option and
the defined parameters.
1
> raidcmd hotspare -c=1 -p=6 -mr=make -a=2
Make Dedicated Hot Spare.
Do you continue ? [yes(y) or no(n)] : yes
>
Step 2
If you see the property
of the Physical Device after
making the Dedicated Hot
Spare, you find that the value of
[Status] is changed to [Hot
Spare] and new item [Hot Spare
Information] appears with value
[Dedicated].
> raidcmd property -tg=pd -c=1 -p=6
2
RAID Controller #1 Physical Device #6
ID
: 5
Enclosure
: 1
Slot
: 6
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Hot Spare
Hot Spare Information
: Dedicated (Disk Array #2)
S.M.A.R.T.
: Normal
>
Removing Hot Spare
The procedure of removing a Hot Spare is described below.
raidcmd
Use the "hotspare" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device from which
the Hot Spare is removed
Physical Device
Number of the Physical Device from which the Hot Spare is removed
Step 1
Execute the "hotspare"
command with -mr option and
the defined parameters.
> raidcmd hotspare -c=1 -p=6 -mr=remove
Remove Hot Spare.
Do you continue ? [yes(y) or no(n)] : yes
>
Step 2
If you see the property
of the Physical Device after
removing the Hot Spare, the
value of [Status] is changed to
[Ready] and item [Hot Spare
Information] disappears.
> raidcmd property -tg=pd -c=1 -p=6
2
RAID Controller #1 Physical Device #6
ID
: 5
Enclosure
: 1
Slot
: 6
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Ready
S.M.A.R.T.
: Normal
>
27
1
Configuring RAID System Easily
The Universal RAID Utility supports the Easy Configuration function allowing configurations such as
creating Logical Drive and making a Hot Spare to be provided in the state where unused Physical Devices
are connected to RAID Controllers.
If you decide the number of Physical Devices used for data storage (or the number of Physical Devices
configuring Logical Drives) and the number of Physical Devices used as Hot Spares among unused
Physical Devices connected to RAID Controllers, the Universal RAID Utility automatically configure the
RAID System.
The benefits of configuring a RAID System by using the Easy Configuration are as follows. The Universal
RAID Utility performs the jobs which must be examined and manipulated to configure a RAID System
instead.
Allowing a RAID System to be configured only by specifying three items, or a RAID Controller, the
number of Physical Devices used for Logical Drives and the number of Logical Drives to be created.
Allowing the Universal RAID Utility to set all the items associated with Logical Drives (including RAID
Level, Capacity, and Stripe Size) automatically.
Allowing more than one Logical Drive to be created at a time.
Making Dedicated Hot Spares for Logical Drives automatically created by Universal RAID Utility if
Physical Devices are left for Hot Spares.
Procedure of Easy Configuration of RAID System
The following describes the procedure of configuring a RAID System easily.
raidcmd
Use the "econfig" command.
Step 1
Connect Physical Devices used for Easy Configuration to the RAID Controller at this
timing if required.
Step 2
Execute the "econfig" command.
Step 3
Specify the conditions on Easy Configuration of the raidcmd.
In step 1/3, select the RAID Controller to be configured. Enter the RAID Controller to be
configured.
In the list, RAID Controllers which do not meet the conditions on Easy Configuration do not
appear.
28
Step 4
In step 2/3, specify
the number of Physical Devices
used for Logical Drive(s)
("Physical Device count using
Logical Drive(s)") and the
number of Logical Drives to be
created in the RAID Controller
("Making Logical Drive count").
If Physical Devices of different
Interface Types exist, specify the
number of Physical Devices in
Interface Types (in the example
shown to the right, proper
settings are provided for
Physical Devices of the SAS
interface. If other Physical
Devices of different Interface
Types exist, perform the
operation in Interface Types).
> raidcmd econfig
Step 1/3 : Select RAID Controller
2
RAID Controller #1 [MegaRAID SAS PCI Express(TM) ROMB]
RAID Controller #2 [LSI Corporation MegaRAID SAS 8408E]
3
RAID Controller [1-2] : 1
Step 2/3 : Set the contents of configuration
<Physical Device (Interface Type : SAS)>
Unused Physical Device count
: 7
Physical Device count using Logical Drive(s) [ 2- 7] : 6
Hot Spare count
: 1
Do you continue ? [yes(y) or no(n)] : y
Maximum Logical Drive count
Creating Logical Drive count [ 1- 2]
4
: 2
: 1
Do you continue ? [yes(y) or no(n)] : y
Step 3/3 : Confirm the contents of configuration
Step 5
Step 3/3 shows the
RAID Controller #1 [LSI MegaRAID SAS 8202E]
Logical Drive #1 [RAID 5 : 200GB]
configuration of the RAID
Physical Device #1(0), 2(1), 3(2) [SAS]
System to be configured by the
Physical Device #7(6) [SAS] Dedicated Hot Spare
Easy Configuration. To configure
Logical Drive #2 [RAID 5 : 200GB]
the RAID System according to
Physical Device #4(3), 5(4), 6(5) [SAS]
Physical Device #7(6) [SAS] Dedicated Hot Spare
the displayed information, type
Logical Drive #3 [RAID 1 : 200GB]
"yes". To change the
Physical Device #8(7), 9(8) [SATA]
configuration, type "no".
Physical Device #10(9) [SATA] Dedicated Hot Spare
f you type "yes", the raidcmd
5
<Caution>
executes the configuration of
Create Logical Drive #2 with different Physical Devices of a
the RAID System and
capacity. Therefore, Logical Drive capacity is decided by the
terminates normally. Making
smallest Physical Device of capacity.
Logical Drives and Hot Spares is
Run the above configuration.
now completed. See the
Initialize all of Logical Drive after creating them. You can see
property of each component to
the progress and the result of initialization by "oplist" and
check the configuration.
"property" commands.
However, the Initialize of the
Do you continue ? [yes(y) or no(n)] : yes
Logical Drives having been
>
created may not be completed.
The progress and result of
initializing the Logical Drives can be checked by using the "oplist" command.
Physical Device has two numbers in Step 3/3.
Physical Device #M(N)
M : The number of Physical Device
N : ID of Physical Device
RAID Controller Enabling Easy Configuration to Be
Executed
Any RAID Controller enabling Easy Configuration to be executed must meet the following conditions.
RAID Controllers meeting the conditions incompletely do not appear in the RAID Controller list in step
1/3 of the [Easy Configuration] wizard.
1
Allowing Dedicated Hot Spares to be made, and
2
Connecting with more than one unused Physical Device.
29
Physical Devices Available for Easy Configuration
Only unused Physical Devices are available for Easy Configuration. Unused Physical Devices are those
with their [Status] being [Ready].
Creating Logical Drives by Easy Configuration
Logical Drives created by Easy Configuration are described below.
RAID Levels and the number of Logical Drives allowed to be created
The RAID Level of a Logical Drive created by Easy Configuration should be RAID 1 or RAID 5.
Whether RAID 1 or RAID 5 is used is defined by RAID Levels supported by the RAID Controller and
the number of Physical Devices used by the Logical Drive.
The number of Logical Drives allowed to be created is also defined by the similar conditions.
RAID Controller supporting RAID Levels RAID 1 and RAID 5
Number of Physical
Devices used by
Logical Drive
RAID Level of Logical
Drive
Number of Logical Drives allowed to be created
2
RAID 1
1
3-5
RAID 5
1
6 or more
RAID 5
Number of Physical Devices used by Logical Drive /
3
RAID Controller supporting RAID 1 only
Number of Physical
Devices used by
Logical Drive
RAID Level of Logical
Drive
Number of Logical Drives allowed to be created
2 or more
RAID 1
Number of Physical Devices used by Logical Drive /
2
The Easy Configuration can only create Logical Drives of RAID 1 or RAID 5.
Physical Devices used for Logical Drives
Physical Devices of lower Physical Device Numbers are used preferentially for Logical Drives to be
created excluding those for making Hot Spares.
Ex. : If Physical Devices #1 - #7 can be used for Easy Configuration and Physical Device #3 is used
as a Hot Spare, Logical Drives #1 and #2 are created with Physical Devices #1 and #2 having
lower Physical Device Numbers and Physical Devices #5, #6 and #7, respectively.
Physical
Device #1
Physical
Device #2
Physical
Device #3
Hot Spare
Physical
Device #4
Logical
Drive #1
Physical
Device #5
Physical
Device #6
Logical
Drive #2
Figure 10 Assigning Physical Devices in Easy Configuration 1
30
Physical
Device #7
If more than one Logical Drive are created and the number of Physical Devices configuring a
Logical Drive is not equal to others, a larger number of Physical Devices should be assigned to a
Logical Drive having a smaller logical number.
Ex.: If Physical Devices #1 - #7 can be used for Easy Configuration and two Logical Drives are
created, Logical Drives #1 and #2 are created with four Physical Devices #1 - #4 and three
Physical Devices #5 - #7, respectively.
Physical
Device #1
Physical
Device #2
Physical
Device #3
Physical
Device #4
Physical
Device #5
Logical
Drive #1
Physical
Device #6
Physical
Device #7
Logical
Drive #2
Figure 11 Assigning Physical Devices in Easy Configuration 2
Physical Devices in which S.M.A.R.T. errors are detected cannot be used to create
Logical Drives.
Capacity of Logical Drive
The capacity of a Logical Drive to be created is defined by the RAID Level and the capacities of
Physical Devices used for the Logical Drive.
The Easy Configuration uses the entire areas of the Physical Devices to create a Logical Drive.
When a single Logical Drive is created by using Physical Devices of different capacities, the
smallest capacity is applied among those of the Physical Devices.
Ex.: If Physical Devices #1 - #7 of different capacities can be used in Easy Configuration to create
two Logical Drives, use Physical Devices #1 - #4 and #5 - #7 to create Logical Drives #1 and
#2, respectively. The capacity of each Logical Drive is defined by the smallest capacity among
those of the Physical Devices for the Logical Device.
Physical
Device #1
50GB
Physical
Device #2
50GB
Logical
Drive #1
150GB
RAID 5
Physical
Device #3
150GB
Physical
Device #4
100GB
Only 50GB is used in
each Physical Device
(#3 and #4) because
the smallest capacity is
50GB (remaining
capacities 100GB and
50GB are not used in #3
and #4, respectively).
Physical
Device #5
100GB
Physical
Device #6
100GB
Logical
Drive #2
200GB
RAID 5
Only 100GB can be
used in Physical
Device #7 because
the smallest capacity
is 100GB in the
Physical Devices.
(Remaining 50GB is
not used.)
Figure 12 Capacities of Logical Drives in Easy Configuration
31
Physical
Device #7
150GB
Items set for Logical Drive
The values of other selection items set for a Logical Drive to be created are defined as shown in the
table below.
Selection item
Value
Stripe Size
Uses the default value set for the RAID Controller. (The value varies
depending on the type of the RAID Controller.)
Cache Mode
Uses the default value set for the RAID Controller. (The value varies
depending on the type of the RAID Controller.)
Initialization Mode
Full
Making Hot Spares by Easy Configuration
This section describes the information on Hot Spares to be made by the Easy Configuration.
Number of Hot Spares
The number of Hot Spares is defined by the number of unused Physical Devices connected to the
RAID Controller and the number of Physical Devices used for Logical Drives. The number of Hot
Spares results from subtracting [Number of Physical Devices specified for Logical Drives] from
[Unused Physical Device count] in step 2/3 of the [Easy Configuration] wizard.
Physical Devices used as Hot Spares
Physical Devices of larger capacities are preferentially used as Hot Spares. Among Physical Devices
of the same capacity, Physical Devices of larger Physical Device Numbers are preferentially used as
Hot Spares.
Ex.: For the example shown below, Physical Devices #1 - #7 can be used in Easy Configuration to
make two Hot Spares. Three Physical Devices have the largest capacity of 150GB. Accordingly,
use Physical Devices #5 and #6 of larger Physical Device Numbers among the three Physical
Devices as Hot Spares.
Physical
Device #1
100GB
Physical
Device #2
100GB
Physical
Device #3
150GB
Physical
Device #4
100GB
Physical
Device #5
150GB
Physical
Device #6
150GB
Hot Spare
Hot Spare
Physical
Device #7
100GB
Figure 13 Assigning Hot Spares in Easy Configuration
Physical Devices in which S.M.A.R.T. errors are detected cannot be used to make
Hot Spares.
Modes of Hot Spares
The Easy Configuration can only make Dedicated Hot Spares but cannot make Global Hot Spares.
If more than one Logical Drive is created, the Dedicated Hot Spare can be used for all Logical
Drives to be created.
Ex.: If Physical Devices #1 - #7 are used in Easy Configuration to create two Logical Drives and a
single Hot Spare, the Hot Spare will be the Dedicated Hot Spare for each Logical Drive.
32
Physical Devices
#1, #2 and #3
Physical Devices
#4, #5 and #6
Physical
Device #7
Logical
Drive #1
Logical
Drive #2
Dedicated
Hot Spare
Figure 14 Making Dedicated Hot Spare in Easy Configuration 1
Ex.: If Physical Devices #1 - #8 are used in Easy Configuration to create two Logical Drives and two
Hot Spares, Hot Spares #1 and #2 will be the Dedicated Hot Spares for Logical Drives #1 and
#2, respectively.
Physical Devices
#1, #2 and #3
Physical Devices
#4, #5 and #6
Physical
Device #7
Physical
Device #8
Logical
Drive #1
Logical
Drive #2
Hot Spare
#1
Hot Spare
#2
Figure 15 Making Dedicated Hot Spares in Easy Configuration 2
33
Creating Logical Drive Easily
The Universal RAID Utility supports "Create Logical Drive - Simple Mode" in which a Logical Drive can be
created only by selecting two selection items according to the guide.
"Create Logical Drive - Simple Mode" allows you to create a Logical Drive only by specifying two selection
items, or the RAID Level of the Logical Drive and Physical Devices to be used.
The benefits of creating a Logical Drive with "Create Logical Drive - Simple Mode" are as follows. The
Universal RAID Utility defines selection items which you should examine to create a Logical Drive instead
of you.
Allowing a Logical Drive to be created only by specifying two selection items (RAID Level and
Physical Devices to be used).
Allowing the Universal RAID Utility to set all setting items (including Capacity and Stripe Size) other
than the RAID Level and Physical Devices to be used automatically.
Operation Procedure of "Create Logical Drive - Simple
Mode"
This section describes the procedure of creating a Logical Drive by "Create Logical Drive - Simple
Mode".
raidcmd
Use "mklds" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller in which a Logical Drive is created
Physical Device
Numbers of the Physical Devices with which a Logical Drive is created.
The required number of Physical Devices varies depending on the RAID
Level of the Logical Drive to be created.
RAID Level
RAID Level at which a Logical Drive is made.
"Create Logical Drive - Simple Mode" allows a Logical Drive with RAID
Level being RAID 1 or RAID 5 to be created.
Step 1
Connect Physical Devices used for a Logical Drive to the RAID Controller at this
timing if required.
Step 2
Execute the "mklds"
command with the defined
parameters.
Step 3
Type "yes" to reply to
the confirmation message. Then
a Logical Drive is created.
> raidcmd mklds -c=1 -p=3,4,5 -rl=5
raidcmd creates Logical Drive #2.
Do you continue ? [yes(y) or no(n)] : y
2
3
raidcmd created Logical Drive #2, and started to initialize it.
You can see the progress and the result of initialize by "oplist"
and "property" commands.
4
>
Step 4
After the Logical Drive
is created completely, the
raidcmd terminates normally. The Logical Drive has been created completely. You can check
the information on the Logical Drive by using the "property" command. However, the Initialize
of the Logical Drive having been created may not be completed. The progress and result of
initializing the Logical Drive can be checked by using the "oplist" command.
34
Physical Devices Available for "Create Logical Drive Simple Mode"
Unused Physical Devices are available for "Create Logical Drive - Simple Mode". Unused Physical
Devices are those with their [Status] being [Ready].
Physical Devices in which S.M.A.R.T. errors are detected cannot be used to create
Logical Drives.
Creating Logical Drives by "Create Logical Drive - Simple
Mode"
This section describes the information on Logical Drives to be created by "Create Logical Drive - Simple
Mode".
RAID Level
The RAID Level of a Logical Drive which can be created by "Create Logical Drive - Simple Mode"
should be RAID 1 or RAID 5.
Capacity of Logical Drive
The capacity of a Logical Drive to be created is defined by the RAID Level and the capacities of
Physical Devices used for the Logical Drive. In "Create Logical Drive - Simple Mode", a Logical Drive
is created by using the entire areas of the Physical Devices.
Items set for Logical Drive
The values of other selection items set for a Logical Drive to be created are defined as shown in the
table below.
Selection item
Value
Stripe Size
Uses the default value set for the RAID Controller. (The value varies
depending on the type of the RAID Controller.)
Cache Mode
Uses the default value set for the RAID Controller. (The value varies
depending on the type of the RAID Controller.)
Initialization Mode
Full
35
Creating Logical Drive Freely
The Universal RAID Utility supports "Create Logical Drive - Custom Mode" in which a Logical Drive can be
created as required by specifying the setting items of the Logical Drive closely.
"Create Logical Drive - Custom Mode" allows you to create a Logical Drive by specifying the setting items
of the Logical Drive closely. It can also be used to create Logical Drives of several RAID Levels or create a
Logical Drive by using unused area of Disk Array. In addition, "Create Logical Drive - Custom Mode"
enables more than one Logical Drive to be created at a time.
The benefits of creating Logical Drives by "Create Logical Drive - Custom Mode" are as follows:
Allows Logical Drives of various RAID Levels (RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, and RAID 50)
to be created.
Allows selection items (including Capacity, Stripe Size, Cache Mode and Initialization Mode) to be
specified closely.
Allows not only unused Physical Devices but also unused area of Disk Array to be used to create a
Logical Drive of RAID 0, RAID 1, RAID 5, or RAID 6.
Operation Procedure of "Create Logical Drive - Custom
Mode"
This section describes the procedure of creating a Logical Drive by "Create Logical Drive - Custom
Mode".
"Create Logical Drive - Custom Mode" is available only in the Advanced Mode.
raidcmd
Use the "mkldc" command. A count of Logical Drive created by raidcmd is 1 at same time.
Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller in which a Logical Drive is created
Physical Device
Numbers of the Physical Devices used to create a Logical Drive if used.
The required number of Physical Devices varies depending on the RAID
Level of the Logical Drive to be created.
Disk Array
Number of the Disk Array used to create a Logical Drive if used
RAID Level
RAID Level of a Logical Drive to be created.
"Create Logical Drive - Custom Mode" allows a Logical Drive with RAID
Level being RAID 0 RAID 1, RAID 5, RAID 6, RAID 10, RAID 50 to be
created.
Capacity
Capacity of a Logical Drive to be created.
This value may be omitted if a Logical Drive is created by using unused
Physical Devices entirely.
Stripe Size
Stripe Size of a Logical Drive to be created
This value may not be specified if the default value for the RAID
Controller is used.
Cache Mode
Cache Mode of a Logical Drive to be created.
This value may not be specified if the default value for the RAID
Controller is used.
Initialization Mode
Operation mode for Initialize executed after a Logical Drive is created.
The [Full] mode is recommended. In the [Full] mode, the Initialize Mode
may not be specified.
36
Step 1
Connect Physical Devices used for a Logical Drive to the RAID Controller at this
timing if required.
Step 2
Execute the "mkldc"
command with the defined
parameters.
Step 3
Type "yes" to reply to
the confirmation message. Then
a Logical Drive is created.
> raidcmd mkldc -c=1 -p=3,4,5 -rl=5 -cp=100 -ss=64 -cm=auto
-im=full
raidcmd creates Logical Drive #2
2
3
Do you continue ? [yes(y) or no(n)] : y
raidcmd created Logical Drive #2, and started to initialize it.
You can see the progress and the result of initialize by "oplist"
and "property" commands.
4
>
Step 4
After the Logical Drive
is created completely, the
raidcmd terminates normally. The Logical Drive has been created completely. You can check
the information on the Logical Drive by using the "property" command. However, the Initialize
of the Logical Drive having been created may not be completed. The progress and result of
initializing the Logical Drive can be checked by using the "oplist" command.
Disk Arrays and Physical Devices Available for "Create
Logical Drive - Custom Mode"
For "Create Logical Drive - Custom Mode", Disk Arrays or unused Physical Devices are available
depending on the RAID Level of the Logical Drive to be created.
Physical Devices in which S.M.A.R.T. errors are detected cannot be used to create
Logical Drives.
Logical Drive with RAID Level being RAID 0, RAID 1, RAID 5 or RAID 6
Disk Arrays containing empty areas or unused Physical Devices are available for creating a Logical
Drive with the RAID Level being RAID 0, RAID 1, RAID 5, or RAID 6.
Among empty areas in a Disk Array, the empty area existing at the end of the Disk Array can be
used. The RAID Level of a Logical Drive to be created must be the same as that of the Logical
Drives existing in the area used on the Disk Array.
If unused Physical Devices are used, create a Disk Array and create a Logical Drive on it. Unused
Physical Devices are those with their [Status] being [Ready].
Logical Drive with RAID Level being RAID 10 or RAID 50
Only unused Physical Devices are available for Logical Drives with RAID Level being RAID 10 or
RAID 50. Unused Physical Devices are those with their [Status] being [Ready].
Creating Logical Drives by "Create Logical Drive Custom Mode"
This section describes the information on Logical Drives to be created by "Create Logical Drive Custom Mode".
RAID Levels
The RAID Level of a Logical Drive which can be created by "Create Logical Drive - Custom Mode"
should be RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, or RAID 50.
Supported RAID Levels vary in RAID Controllers. Unsupported RAID Levels cannot
be selected.
37
Capacity of Logical Drive
A Logical Drive to be created in the Custom Mode can have any capacity. However, a Logical Drive
with the RAID Level being RAID 10 or RAID 50 must be created by using the entire areas of
Physical Devices.
Items set for Logical Drive
The values of other selection items set for a Logical Drive to be created are defined as shown in the
table below.
Selection Item
Value
Stripe Size
Select a value out of 1KB, 2KB, 4KB, 8KB, 16KB, 32KB, 64KB, 128KB,
256KB, 512KB, and 1024KB.
Cache Mode
Three possible values are as follows:
Auto Switch: Switches the mode automatically between Write Back and
Write Through depending on the existence and/or status of battery.
Write Back: Writes data to the cache memory asynchronously.
Write Through: Writes data to the cache memory synchronously.
Initialization Mode
Two possible values are as follows:
Full: Initializes both the management and data areas in the Logical Drive.
Quick: Initializes only the management information in the Logical Drive.
Supported Stripe Sizes and cache mode vary in RAID Controllers. Unsupported
Stripe Sizes and cache modes cannot be selected.
38
Deleting Logical Drive
The Universal RAID Utility can delete a Logical Drive becoming unnecessary.
The function of deleting a Logical Drive is available only in the Advanced Mode.
Before a Logical Drive is deleted, check if the Logical Drive contains required data.
Deleting a Logical Drive causes all the data saved in the Logical Drive to be lost.
Any Logical Drive meeting the following conditions cannot be deleted.
Containing the boot partition.
Located at other than the end of Disk Array.
Deleting Logical Drive
The procedure of deleting a Logical Drive is described below.
raidcmd
Use the "delld" command. Define the following parameters before executing the raidcmd.。
Item
Description
RAID Controller
Number of the RAID Controller containing the Logical Drive to be deleted
Logical Drive
Number of the Logical Drive to be deleted
Step 1
Execute the "delld"
command with the defined
parameters.
> raidcmd delld -c=1 -l=2
Delete Logical Drive #2
1
Do you continue ? [yes(y) or no(n)] : yes
>
39
Maintenance of RAID System
This chapter describes the maintenance of a RAID System using the Universal RAID Utility.
Providing Patrol Read for Physical Devices
The Patrol Read function reads data saved in all Physical Devices in a RAID System entirely to check
whether a read error occurs or not repeatedly in the background. The Universal RAID Utility provides the
function of indicating whether Patrol Read is executed or not and the function of changing the Patrol Read
Priority.
The Patrol Read is effective to find failures including Physical Device media errors early. Be sure to
execute Patrol Read for a RAID Controller if it supports the Patrol Read.
Setting Whether Patrol Read Is Executed or Not
Whether Patrol Read is executed or not should be set in RAID Controllers. The procedure of setting
whether Patrol Read is executed or not is described below.
Changing the setting whether Patrol Read is executed or not is available only in the
Advanced Mode.
raidcmd
Use the "optctrl" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller for which whether Patrol Read is executed
or not is set
Execution of Patrol Read
Enable/Disable Patrol Read.
Step 1
Execute the "optctrl"
command with -pr option and
the defined parameters.
Step 2
> raidcmd optctrl -c=1 -pr=enable
>
1
Check the execution result by using the "property" command.
Checking Result of Executing Patrol Read
You can find the result of executing Patrol Read by checking the RAID Log of the Universal RAID Utility.
When detects something problem, Universal RAID Utility records the log in the RAID Log.
Setting Patrol Read Priority
You can set the priority in which Patrol Read is executed in your computer. The procedure of setting the
Patrol Read Priority is described below.
Changing the priority of Patrol Read is available only in the Advanced Mode.
40
raidcmd
Use the "optctrl" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller for which Patrol Read Priority is set
Patrol Read Priority
Value set after Patrol Read Priority is changed.
Select a value out of High, Middle, and Low.
Step 1
Execute the "optctrl"
command with -prp option and
the defined parameters.
Step 2
Check the execution
result by using the "property"
command.
> raidcmd optctrl -c=1 -prp=high
1
>
> raidcmd property -tg=rc -c=1
RAID Controller #1
ID
: 0
Vendor
: LSI Corporation
Model
: MegaRAID SAS PCI Express(TM) ROMB
Firmware Version
: 1.12.02-0342
Cache Size
: 128MB
Battery Status
: Normal
Rebuild Priority
: High
Consistency Check Priority : Low
Patrol Read
: Enable
Patrol Read Priority
: High
2
Buzzer Setting
: Enable
>
41
Checking Logical Drive Consistency
The Consistency Check function checks the consistency between the data in the data area of a Logical
Drive and the parity. The Universal RAID Utility can start or stop Consistency Check and change the priority
in which Consistency Check is executed.
The Consistency Check is effective next to Patrol Read to find failures including Physical Device media
errors early. Execute Consistency Check periodically if the RAID Controller does not support Patrol Read. If
the Universal RAID Utility is installed, routine execution of the Consistency Check is set for RAID
Controllers not supporting Patrol Read.
Starting or stopping the Consistency Check is enabled both in the Standard Mode and
Advanced Mode. The function of changing the priority at which the Consistency Check is
executed is available only in the Advanced Mode.
Executing Consistency Check Manually
Consistency Check is executed in Logical Drives. The procedure of starting Consistency Check is
described below.
The Consistency Check can be executed only for Logical Drives with [Status] being
[Online]. The Consistency Check cannot be executed for Logical Drives with RAID Level
being RAID 0.
raidcmd
Use the "cc" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Logical Drive for which
Consistency Check is executed
Logical Drive
Number of the Logical Drive for which Consistency Check is executed
Step 1
Execute the "cc"
command with -op option and
the defined parameters.
> raidcmd cc -c=1 -l=2 -op=start
1
>
> raidcmd oplist
2
RAID Controller #1
Logical Drive #2 : Consistency Check (30%)
>
Step 2
After the Consistency
Check is started, the raidcmd
terminates normally. Check the
execution status of the Consistency Check by using the "oplist" command.
Executing Consistency Check for arbitrary Logical Drive
The Universal RAID Utility makes a task for scheduled execution of Consistency Check so that a RAID
Controller not supporting Patrol Read can find failures including media errors early. To execute
Consistency Check for arbitrary Logical Drive by raidcmd, use the function of scheduler as cron.
Universal RAID Utility make the task for a RAID Controller which does not support Patrol Read that
execute consistency check for arbitrary Logical Drive.
42
Task provided by Universal RAID Utility
The Universal RAID Utility registers a task such as that shown in the table below in a cron if it is
installed.
The functions of cron can be used to change the schedule of executing Consistency Check or delete
tasks. For how to use cron, see the cron(8)、crontab(1)、crontab(5) by "man" command.
Item
Description
Execution day of the week
Wednesday
Starting time
AM 0:00
Execution command
/opt/nec/raidcmd/raidcmd ccs
Execution account
root
Executing Consistency Check for all Logical Drives for RAID Controller
not supporting Patrol Read
To execute Consistency Check for all Logical Drives of a RAID Controller not supporting Patrol Read,
use the ccs command of the raidcmd.
Stopping Consistency Check
You can stop Consistency Check being executed on the way. The procedure of stopping Consistency
Check is described below.
raidcmd
Use the "cc" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Logical Drive for which
Consistency Check is stopped
Logical Drive
Number of the Logical Drive for which Consistency Check is stopped
Step 1
Execute the "cc"
command with -op option and
the defined parameters.
> raidcmd cc -c=1 -l=2 -op=stop
>
> raidcmd oplist
2
RAID Controller #1
>
1
Step 2
After the Consistency
Check is stopped, the raidcmd
terminates normally. The stopped Consistency Check disappears from the list of the "oplist"
command.
Checking Result of Executing Consistency Check
You can find the result of executing Consistency Check by checking the RAID Log of the Universal RAID
Utility.
Detecting a problem, the Consistency Check records the log in the RAID Log.
Setting Consistency Check Priority
You can set the priority at which Consistency Check is executed in the computer. The procedure of
setting the Consistency Check Priority is described below.
43
Setting Consistency Check Priority are available only in the Advanced Mode.
raidcmd
Use the "optctrl" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller for which Consistency Check Priority is set
Consistency Check
Priority
Value set after Consistency Check Priority is set.
Select a value out of High, Middle, and Low.
Step 1
Execute the "optctrl"
command with -ccp option and
the defined parameters.
Step 2
Check the execution
result by using the "property"
command.
> raidcmd optctrl -c=1 -ccp=middle
1
> raidcmd property -tg=rc -c=1
RAID Controller #1
ID
: 0
Vendor
: LSI Corporation
Model
: MegaRAID SAS PCI Express(TM) ROMB
Firmware Version
: 1.12.02-0342
Cache Size
: 128MB
Battery Status
: Normal
Rebuild Priority
: High
Consistency Check Priority : Middle
2
Patrol Read
: Enable
Patrol Read Priority
: Low
Buzzer Setting
: Enable
>
44
Initializing Logical Drive
The Initialize writes 0s into the entire area of a Logical Drive to erase the data saved in the Logical Drive.
Use the function when you want to erase the data saved in a Logical Drive fully.
Initialization has two modes listed in the table below.
Mode
Description
Full
Writes 0s into the entire area of a Logical Drive to erase the data fully.
Quick
Writes 0s into some blocks in a Logical Drive. Only erases OS installation and
partition management information. Initialization of the mode is completed earlier
than that of the full mode. However, because 0s are not written into the
remaining area, data consistency is not held in the Logical Drive.
Initialize are available only in the Advanced Mode.
The Consistency Check of a Logical Drive initialized in the quick mode causes a data
inconsistency error to occur due to no data consistency.
The Logical Drive containing the boot partition cannot be initialized.
Executing Initialization
Initialization should be executed in Logical Drives. The procedure of executing Initialize is described
below.
raidcmd
Use the "init" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Logical Drive to be
initialized
Logical Drive
Number of the Logical Drive to be initialized
Initialization cannot be executed for any Logical Drive with [Status] being [Online].
Step 1
Execute the "init"
command with -op option and
the defined parameters.
> raidcmd init -c=1 -l=2 -op=start
>
> raidcmd oplist
2
RAID Controller #1
Logical Drive #2 : Initialize (50%)
>
Step 2
After the Initialize is
started, the raidcmd terminates
normally. Check the execution
status of the Initialize by using the "oplist" command.
45
1
Stopping Initialization
You can stop Initialize being executed on the way. The procedure of stopping Initialize is described
below.
raidcmd
Use the "init" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Logical Drive for which
Initialize is stopped
Logical Drive
Number of the Logical Drive for which Initialize is stopped
Step 1
Execute the "init"
command with -op option and
the defined parameters.
> raidcmd init -c=1 -l=2 -op=stop
>
> raidcmd oplist
2
>
1
Step 2
After the Initialize is
stopped, the raidcmd terminates normally. The stopped Initialize disappears from the list of
the "oplist" command.
Checking Result of Executing Initialization
You can find the result of executing Initialize by checking the RAID Log of the Universal RAID Utility.
Detecting a problem, the Initialize records the log in the RAID Log.
Setting Initialization Priority
You can set the priority at which Initialization is executed in the computer. The procedure of setting the
Initialization Priority is described below.
Setting Initialization Priority are available only in the Advanced Mode.
RAID Controllers of some types may not support the setting Initialization Priority. If
does not support this function, raidcmd does not display this item in the property of
RAID Controller and the execution of the "optctrl" command of raidcmd fails.
raidcmd
Use the "optctrl" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller for which Initialization Priority is set
Initialization Priority
Value set after Initialization Priority is set.
Select a value out of High, Middle, and Low.
46
Step 1
Execute the "optctrl"
command with -ip option and
the defined parameters.
Step 2
Check the execution
result by using the "property"
command.
> raidcmd optctrl -c=1 -ip=middle
> raidcmd property -tg=rc -c=1
RAID Controller #1
ID
: 0
Vendor
: Vendor Name
Model
: Model Name
Firmware Version
: 1.00
Cache Size
: 128MB
Battery Status
: Normal
Initialization Priority
: Middle
Rebuild Priority
: Middle
Consistency Check Priority : Low
Patrol Read
: Enable
Patrol Read Priority
: Low
Buzzer Setting
: Enable
>
47
1
2
Rebuilding Physical Device
Rebuild means incorporation of a new Physical Device to a Logical Drive after a Physical Device is
replaced with the new one due to occurrence of an event such as a failure. In general, the Rebuild is
automatically started by a function of the RAID Controller called standby rebuild or hot-swap rebuild.
Accordingly, manual Rebuild is not required so often. If required, use the Universal RAID Utility.
Manual Rebuild is available only in the Advanced Mode.
Executing Rebuild
Rebuild is executed for a Physical Device. The procedure of executing Rebuild is described below.
raidcmd
Use the "rebuild" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device for which
Rebuild is executed
Physical Device
Number of the Physical Device for which Rebuild is executed
Rebuild can be executed if [Status] of a Physical Device is set to [Failed] and
[Status] of the Logical Drive using the physical drive is set to [Degraded].
Step 1
Connect the Physical Device used for Rebuild to a RAID Controller at this timing if
required.
Step 2
Execute the "rebuild"
command with -op option and
the defined parameters.
> raidcmd rebuild -c=1 -p=3 -op=start
>
> raidcmd oplist
3
RAID Controller #1
Physical Device #3(2) : Rebuild (70%)
>
2
Step 3
After the Rebuild is
started, the raidcmd terminates
normally. Check the execution
status of the Rebuild by using the "oplist" command.
Stopping Rebuild
You can stop Rebuild being executed on the way. The procedure of stopping Rebuild is described
below.
The function of stopping Rebuild is available only in the Advanced Mode.
raidcmd
Use the "rebuild" command. Define the following parameters before executing the raidcmd.。
48
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device for which
Rebuild is stopped
Physical Device
Number of the Physical Device for which Rebuild is stopped
Step 1
Execute the "rebuild"
command with -op option and
the defined parameters.
> raidcmd rebuild -c=1 -p=3 -op=stop
>
> raidcmd oplist
2
>
1
Step 2
After the Rebuild is
stopped, the raidcmd
terminates normally. The stopped Rebuild disappears from the list of the "oplist" command.
Checking Result of Executing Rebuild
You can find the result of executing Rebuild by checking the Tree View, the property of the Physical
Device and the RAID Log of the Universal RAID Utility.
If Rebuild succeeds, the icon of the Physical Device subject to the Rebuild changes to [Online] on the
Tree View. In addition, the [Status] in the Property tab of the Physical Device is set to [Online].
When detects something problem, Universal RAID Utility records the log in the RAID Log.
Setting Rebuild Priority
You can set the priority at which Rebuild is executed in the computer. The procedure of setting the
Rebuild Priority is described below.
Setting Rebuild Priority are available only in the Advanced Mode.
raidcmd
Use the "optctrl" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller for which Rebuild Priority is set
Rebuild Priority
Value set after Rebuild Priority is set.
Select a value out of High, Middle, and Low.
Step 1
Execute the "optctrl"
command with -rp option and
the defined parameters.
Step 2
Check the execution
result by using the "property"
command.
> raidcmd optctrl -c=1 -rp=middle
1
> raidcmd property -tg=rc -c=1
RAID Controller #1
ID
: 0
Vendor
: LSI Corporation
Model
: MegaRAID SAS PCI Express(TM) ROMB
Firmware Version
: 1.12.02-0342
Cache Size
: 128MB
Battery Status
: Normal
2
Rebuild Priority
: Middle
Consistency Check Priority : Middle
Patrol Read
: Enable
Patrol Read Priority
: Low
Buzzer Setting
: Enable
>
49
Checking Location of Physical Device
The locate function can be used when you want to know the slot to which a specific Physical Device
appearing in the Universal RAID Utility is inserted in the computer or enclosure. In actual, locate turns
on the DISK lamp on the computer or enclosure in which the specified Physical Device is installed. (The
DISK lamp blinks depending on the types of the computer or enclosures.) Searching for the Physical
Device with the DISK lamp being ON allows the Physical Device for which "check location" is executed
on raidcmd to be identified.
raidcmd don't support the indication of the status (ON or OFF) of DISK lamp. Therefore,
you can't recognize the location of the Physical Device when you turn ON the lamp of
two or more Physical Devices at same time. You should turn ON the lamp of Physical
Device one by one. It is convenient when you put down the number of the Physical
Device which turned on a DISK lamp because you can confirm the number of the
Physical Device when turn off the DISK lamp.
Procedure of Checking Location of Physical Device
Locate is executed for a Physical Device. The locate procedure is described below.
raidcmd
Use the "slotlamp" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device for which
its location is checked
Physical Device
Number of the Physical Device for which its location is checked
Step 1
To turn on the DISK
lamp for locate, execute the
"slotlamp" command with the
-sw option set to "on" using the
defined parameters.
> raidcmd slotlamp -c=1 -p=3 -sw=on
>
>
> raidcmd slotlamp -c=1 -p=3 -sw=off
>
Step 2
To turn off the lighting
DISK lamp, execute the "slotlamp" command with the -sw option set to "off".
50
1
2
Changing Status of Physical Device Forcibly
The function of changing status of a Physical Device forcibly can be used when you want to change the
[Status] of a Physical Device to [Online] or [Failed] forcibly for a maintenance job or another. The function
may not be used in normal operation.
The function of changing the status of a Physical Device forcibly is available only in the
Advanced Mode.
The function of changing the status of a Physical Device forcibly may not be able to
change the status to the desired one depending on the status of the Physical Device (such
as a severe failure).
To [Online] Forcibly
To set the [Status] of a Physical Device to [Online] forcibly, use Make Online. The procedure of
executing Make Online is described below.
raidcmd
Use the "stspd" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device with its
status set to [Online] forcibly
Physical Device
Number of the Physical Device with its status set to [Online] forcibly
Step 1
Execute the "stspd"
command with -st option and
the defined parameters.
Step 2
If the "stspd"
command succeeds, the
[Status] of the physical device is
set to [Online].
> raidcmd stspd -c=1 -p=4 -st=online
1
> raidcmd property -tg=pd -c=1 -p=3
RAID Controller #1 Physical Device #3
ID
: 2
Enclosure
: 1
Slot
: 3
Interface
: SAS
Vendor/Model
: SEAGATE ST936751SS
Firmware Version
: 0001
Serial Number
: 3PE073VM
Capacity
: 33GB
2
Status
: Online
S.M.A.R.T.
: Normal
>
51
To [Failed] Forcibly
To set the [Status] of a Physical Device to [Failed] forcibly, use Make Offline. The procedure of
executing Make Offline is described below.
raidcmd
Use the "stspd" command. Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller containing the Physical Device with its
status set to [Failed] forcibly
Physical Device
Number of the Physical Device with its status set to [Failed] forcibly
Step 1
Execute the "stspd"
command with -st option and
the defined parameters.
Step 2
If the "stspd"
command succeeds, the
[Status] of the physical device is
set to [Failed].
> raidcmd stspd -c=1 -p=1 -st=offline
1
> raidcmd property -tg=pd -c=1 -p=3
RAID Controller #1 Physical Device #3
ID
: 2
Enclosure
: 1
Slot
: 3
Interface
: SAS
Vendor/Model
: SEAGATE ST936751SS
Firmware Version
: 0001
Serial Number
: 3PE073VM
Capacity
: 33GB
Status
: Failed
2
S.M.A.R.T.
: Normal
>
52
Troubleshooting RAID System
The Universal RAID Utility provides various measures to monitor occurrences of failures in the RAID System. The
figure below shows the image of the troubleshooting function provided by the Universal RAID Utility.
Universal RAID Utility
raidcmd
NEC ESMPRO Manager
RAID Log
Measure 1
Failures in RAID
System detected
by RAID
controllers appear
on raidcmd.
Measure 2
All events occurred in RAID
Systems are recorded to RAID
Log. text editor or otherwise
allow referring RAID Log.
Measure 3
Buzzer sounds
at occurrence of
failure if
installed in RAID
Controller.
Measure 4
Among events
recorded in RAID
log, important
events are also
recorded to syslog.
Measure 5
For events logged in
OS Log, alerts are sent
to NEC ESMPRO
Manager.
OS Log
Buzzer
RAID System
Figure 16 Troubleshooting image of RAID System
This chapter describes the troubleshooting of a RAID System done by using the Universal RAID Utility.
53
Failure Detection Measures
The Universal RAID Utility provides several fault detection measures as shown in Figure 16
Troubleshooting image of RAID System. The measures are described below.
Status Display by raidcmd
You can see the status of each component in a RAID System by using the "property" command. For the
information in the property, see "Referring to Information on RAID System
Logging Events to RAID Log
The Universal RAID Utility logs all events occurred in the RAID System to the RAID Log in the Universal
RAID Utility.
The data in the RAID Log can be seen by using a text editor or otherwise. Note the character code
when you see the RAID Log.
Operating System
VMware ESX Server 3
Path and File Name
Character Code
/var/log/raidsrv/raid.log
UTF-8
For details of events to be registered to the RAID Log, see "Appendix B : Logs/Events".
Buzzer
uzzer in RAID Controller
If a RAID Controller is equipped with a Buzzer, the RAID Controller sounds the Buzzer for some types of
failures occurred.
The Buzzer sounds until the stopping it by raidcmd.
raidcmd
Use the "sbuzzer" command.
Define the following parameters before executing the raidcmd.
Item
Description
RAID Controller
Number of the RAID Controller for which Buzzer is stopped
Step 1
Execute the "sbuzzer"
command with the defined
parameter.
> raidcmd sbuzzer -c=1
>
1
Logging Events to OS Log
Among RAID System events logged in the RAID Log, the Universal RAID Utility also logs important
events to the syslog.
See "Appendix B : Logs/Events" for detail.
Sending Alert to NEC ESMPRO Manager
Among RAID System events logged in the OS Log, the Universal RAID Utility sends important events
which may affect the operations and managements of the computer to the NEC ESMPRO Manager as
alerts. To send alerts, the event monitoring function provided by the NEC ESMPRO Agent can be used.
If the NEC ESMPRO Agent is installed in the computer in which the Universal RAID Utility is installed
54
and alert transmission is set, RAID System events detected by the Universal RAID Utility will be
automatically subject to alert transmission to the NEC ESMPRO Manager.
For alerts sent to the NEC ESMPRO Manager, see "Appendix B : Logs/Events".
For alert transmission provided by the NEC ESMPRO Agent, see the relevant
documentation of the NEC ESMPRO Agent.
Using report coordination of NEC ESMPRO/AlertManager
To transfer alerts sent to the NEC ESMPRO Manager by using the inter-manager communication
function or to use alerts on report coordination of the NEC ESMPRO/AlertManager, add the
following registry to the computer in which the NEC ESMPRO Manager is installed.
Registry key
CPU architecture (x86) :
HKEY_LOCAL_MACHINE\SOFTWARE\NEC\NVBASE\AlertViewer\AlertType\URAIDUTL
CPU architecture (x64) :
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\NVBASE\AlertViewer\AlertType\URAID
UTL
Values
Name
Type
Data
WavDefault
REG_SZ
Default.wav
AniDefault
REG_SZ
Default.bmp
Image
REG_SZ
Default.bmp
SmallImage
REG_SZ
Default.bmp
Permission
In case of the operation system is Windows XP(exclude Home Edition), Windows 2000, Windows
Server 2003, Windows NT, add the following permissions.
Name
Type
Administrators
Full Control
Everyone
Read
SYSTEM
Full Control
ESMPRO User Group
Full Control
ESMPRO User Group is the name group for the management of NEC ESMPRO
Manager (specified it when installed NEC ESMPRO Manager). If you forget the
name of group, see the following registry key.
CPU architecture (x86) : HKEY_LOCAL_MACHINE\SOFTWARE\NEC\NVBASE
CPU architecture (x64) : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
\NEC\NVBASE
Value : LocalGroup
55
Monitoring Faults of Physical Devices
The Universal RAID Utility can take the following measures to monitor failures of Physical Devices
detected by RAID Controllers.
raidcmd
RAID Log
Buzzer
syslog
Alert
Depending on type
of RAID Controller
If a Physical Device used for a Logical Drive is failed, the status of the Physical Device changes to [Failed].
In addition, the status of the Logical Drive using the Physical Device changes to [Degraded] or [Offline]
depending on the redundancy. The status of the Physical Device and Logical Device remains unchanged
until the problem is solved.
The raidcmd indicates the status of Physical Devices and
Logical Drives on their properties.
[Symbols]
Logical drive
Physical device
Physical device (Hot Spare)
56
Operation in no failures of Physical Devices
If all Physical Devices used by a Logical Drive operates
normally (with their [Status] being [Online]), the Logical
Drive is in the online status (with its [Status] being
[Online]).
The raidcmd shows the status as shown in the figure
below.
Status of RAID System
#1 [Online]
RAID Level: 5
#1
#2
#3
#4
[Online] [Online] [Online] [Hot spare]
> raidcmd property -tg=ld -c=1 -l=1
RAID Controller #1 Logical Drive #1
ID
: 0
Physical Device Number
: 1, 2, 3
Disk Array Number
: 1
RAID Level
: 5
Stripe Size
: 64KB
Capacity
: 146GB
Cache Mode (Current)
: Write Back
Cache Mode (Setting)
: Auto Switch
Status
: Online
>
[Status] of Logical Drive is
[Online].
> raidcmd property -tg=pd -c=1 -p=1
RAID Controller #1 Physical Device #1
ID
: 0
Enclosure
: 1
Slot
: 1
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
>
[Status] of every Physical
Device is [Online].
> raidcmd property -tg=pd -c=1 -p=2
RAID Controller #1 Physical Device #2
ID
: 0
Enclosure
: 1
Slot
: 2
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
S.M.A.R.T.
: Normal
>
> raidcmd property -tg=pd -c=1 -p=3
RAID Controller #1 Physical Device #3
ID
: 0
Enclosure
: 1
Slot
: 3
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
S.M.A.R.T.
: Normal
>
Figure 17 Display of raidcmd in no failures of Physical Devices
57
Operation when redundancy of Logical Drive degraded
or lost due to failure of Physical Device
If one or more Physical Devices used by a Logical Drive
are failed (with their [Status] being [Failed]) to degraded
or lost the redundancy of the Logical Drive, the Logical
Drive is degraded (with its [Status] being [Degraded]).
Status of RAID System
#1 [Degraded]
RAID Level: 5
The raidcmd shows the status as shown in the figure
below.
#1
#2
[Online] [Online]
> raidcmd property -tg=ld -c=1 -l=1
RAID Controller #1 Logical Drive #1
ID
: 0
Physical Device Number
: 1, 2, 3
Disk Array Number
: 1
RAID Level
: 5
Stripe Size
: 64KB
Capacity
: 146GB
Cache Mode (Current)
: Write Back
Cache Mode (Setting)
: Auto Switch
Status
: Degraded
>
#3
[Failed]
#4
[Hot spare]
[Status] of Logical Drive
changes to [Degraded]
because of lost the
redundancy.
> raidcmd property -tg=pd -c=1 -p=1
RAID Controller #1 Physical Device #1
ID
: 0
Enclosure
: 1
Slot
: 1
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
S.M.A.R.T.
: Normal
>
[Status] of no failure Physical
Device is [Online].
> raidcmd property -tg=pd -c=1 -p=2
RAID Controller #1 Physical Device #2
ID
: 0
Enclosure
: 1
Slot
: 2
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
S.M.A.R.T.
: Normal
>
> raidcmd property -tg=pd -c=1 -p=3
RAID Controller #1 Physical Device #3
ID
: 0
Enclosure
: 1
Slot
: 3
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Failed
S.M.A.R.T.
: Normal
>
[Status] of Failed Physical
Device changed to [Failed].
Figure 18 Display of raidcmd under lost the redundancy of Logical Drive
58
The status of a Logical Drive is defined depending on the RAID Level and the
number of Physical Devices failed.
If the RAID Level is RAID 10 or RAID 50 and two Physical Devices are failed, the
status will be [Degraded] or [Offline] depending on the failed Physical Devices.
RAID
Level
RAID 0
RAID 1
RAID 5
RAID 6
RAID 10
RAID 50
Number of failed Physical Devices
1
2
Offline
Offline
Degraded
Offline
Degraded
Offline
Degraded
Degraded
Degraded
Degraded/Offline
Degraded
Degraded/Offline
0
Onine
Onine
Onine
Onine
Onine
Onine
59
3 or more
Offline
Offline
Offline
Offline
Offline
Operation when failed Physical Device is replaced to
recover RAID System
Using the RAID System continuously with the
redundancy of a Logical Drive remaining degraded may
cause the data in the Logical Drive to be lost when
another Physical Device is failed further. Recover a
Logical Drive of degraded redundancy by Hot Spare or
replacement of the failed Physical Device.
If Hot Spare or replacement of a failed Physical Device
operates Rebuild, the status of the Physical Device
changes during the rebuilding (with its [Status] changed
to [Rebuilding]).
Status of RAID System
#1 [Degraded]
RAID Level: 5
#1
#2
[Online] [Online]
#3
[Failed]
#4
[Rebuilding]
The raidcmd shows the status as shown in the figure below.
> raidcmd property -tg=ld -c=1 -l=1
RAID Controller #1 Logical Drive #1
ID
: 0
Physical Device Number
: 1, 2, 3
Disk Array Number
: 1
RAID Level
: 5
Stripe Size
: 64KB
Capacity
: 146GB
Cache Mode (Current)
: Write Back
Cache Mode (Setting)
: Auto Switch
Status
: Degraded
>
[Degraded] of [Status]
remain unchanged until
rebuild is completed.
> raidcmd property -tg=pd -c=1 -p=3
RAID Controller #1 Physical Device #3
ID
: 0
Enclosure
: 1
Slot
: 3
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Ready
S.M.A.R.T.
: Normal
>
> raidcmd property -tg=pd -c=1 -p=4
RAID Controller #1 Physical Device #4
ID
: 0
Enclosure
: 1
Slot
: 4
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Rebuilding
S.M.A.R.T.
: Normal
>
Failure of Physical Device after
Rebuild is started brings various
results depending on type of RAID
Controller or failure as follows;
[Status] is changed to [Ready],
Physical Devices cannot be
recognized, and [Status] remains
[Failed].
[Status] of Hot Spare
changes to [Rebuilding].
Figure 19 Display of raidcmd after rebuilding of Physical Device
60
Operation when the Logical Drive is offline due to failure
of Physical Device
If you continue to use the RAID System with lost
redundancy of a Logical Drive and another Physical
Device is failed further, the redundancy of the Logical
Drive is lost completely. The status of a Logical Drive
without redundancy is offline (with its [Status] being
[Offline]). The data in a Logical Drive in the offline
status is lost. Replace all failed Physical Devices and
Rebuild the RAID System.
The raidcmd shows the status as shown in the figure
below.
> raidcmd property -tg=ld -c=1 -l=1
RAID Controller #1 Logical Drive #1
ID
: 0
Physical Device Number
: 1, 2, 3
Disk Array Number
: 1
RAID Level
: 5
Stripe Size
: 64KB
Capacity
: 146GB
Cache Mode (Current)
: Write Back
Cache Mode (Setting)
: Auto Switch
Status
: Offline
>
Status of RAID System
#1 [Offline]
RAID Level: 5
#1
[Online]
#2
[Failed]
#3
[Failed]
[Offline] of Logical Drive
changes to [Offline]
because of loss of
redundancy.
> raidcmd property -tg=pd -c=1 -p=1
RAID Controller #1 Physical Device #1
ID
: 0
Enclosure
: 1
Slot
: 1
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
S.M.A.R.T.
: Normal
>
> raidcmd property -tg=pd -c=1 -p=2
RAID Controller #1 Physical Device #2
ID
: 0
Enclosure
: 1
Slot
: 2
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Failed
S.M.A.R.T.
: Normal
>
> raidcmd property -tg=pd -c=1 -p=3
RAID Controller #1 Physical Device #3
ID
: 0
Enclosure
: 1
Slot
: 3
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Failed
S.M.A.R.T.
: Normal
>
[Status] of both failed
Physical Devices change
to [Failed].
Figure 20 Display of raidcmd under lost redundancy of Logical Drive
61
Monitoring Battery Status
The Universal RAID Utility can monitor battery status which the RAID Controller detects by the following
means.
raidcmd
RAID Log
Buzzer
syslog
Alert
Depending on type
of RAID Controller
The Universal RAID Utility monitors events of the battery installed in the RAID Controller. The Universal
RAID Utility logs detected battery events in the RAID Log. Any event indicating occurrence of a problem in
the battery reflects the battery status as the status of the RAID Controller (by changing the status of the
RAID Controller to [Warning]). The battery status is retailed as the status of the RAID Controller until the
problem is solved.
Operation when battery operates normally
If the battery operates normally, the [Battery Status] of RAID Controller is [Normal].
The raidcmd shows the status as shown in the figure below.
> raidcmd property -tg=rc -c=1
RAID Controller #1
ID
: 0
Interface
: SAS
Vendor
: LSI Logic
Model
: MegaRAID SAS PCI Express(TM) ROMB
Firmware Version
: 1.14-02-0342
Cache Size
: 128MB
Battery Status
: Normal
Initialize Priority
: Middle
Rebuild Priority
: High
Consistency Check Priority : High
Patrol Read
: Enable
Patrol Read Priority
: Low
Buzzer Setting
: Enable
>
[Battery Status] of RAID
Controller is [Normal].
Figure 21 Display of raidcmd under normal Battery operation
Operation when battery does not operate normally
If the battery does not operate normally, the [Battery Status] of RAID Controller is [Warning].
The raidcmd shows the status as shown in the figure below.
> raidcmd property -tg=rc -c=1
RAID Controller #1
ID
: 0
Interface
: SAS
Vendor
: LSI Logic
Model
: MegaRAID SAS PCI Express(TM) ROMB
Firmware Version
: 1.14-02-0342
Cache Size
: 128MB
Battery Status
: Warning
Initialize Priority
: Middle
Rebuild Priority
: High
Consistency Check Priority : High
Patrol Read
: Enable
Patrol Read Priority
: Low
Buzzer Setting
: Enable
>
[Battery Status] of RAID
Controller changes to
[Warning].
Figure 22 Display of raidcmd under abnormal Battery operation
62
Monitoring Enclosure Status
The Universal RAID Utility can monitor enclosure status which the RAID Controller detects by the following
means.
raidcmd
RAID Log
Buzzer
syslog
Alert
Depending on type
of RAID Controller
The Universal RAID Utility monitors events of the enclosure detected by the RAID Controller. The Universal
RAID Utility logs detected enclosure events to the RAID Log. In addition, the Universal RAID Utility records
important events to the syslog and sends alerts to the NEC ESMPRO Manager.
The raidcmd does not indicate the severity of events in this category to the property of RAID system.
See "Appendix B : Logs/Events" for detail about the event of enclosure.
Monitoring Various Events of RAID System
The Universal RAID Utility can monitor other events which the RAID Controller detects by the following
means.
raidcmd
RAID Log
Buzzer
syslog
Alert
Depending on type
of RAID Controller
The Universal RAID Utility monitors various events of the RAID System as well as failures of Physical
Devices, battery events and enclosure events described above. The Universal RAID Utility logs events
detected in the RAID System to the RAID Log. In addition, the Universal RAID Utility records important
events to the syslog and sends alerts to the NEC ESMPRO Manager.
The raidcmd does not indicate the severity of events in this category to Tree View and the property of RAID
system.
See "Appendix B : Logs/Events" for detail about the various event of RAID system.
Replacing Physical Device for Prevention
If Physical Devices support S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) and the RAID
Controller can detects S.M.A.R.T. errors, the Universal RAID Utility can monitor the S.M.A.R.T. errors by the
following means.
raidcmd
RAID Log
Buzzer
syslog
Alert
Depending on type
of RAID Controller
The Universal RAID Utility monitors S.M.A.R.T. errors occurred in Physical Devices. Detecting a S.M.A.R.T.
error, the Universal RAID Utility logs the event to the RAID Log. In addition, the Universal RAID Utility
reflects the status of S.M.A.R.T. in a Physical Device as the status of the Physical Device (by changing the
status of the Physical Device to [Warning]). The status of the Physical Device is retained as its status until
the S.M.A.R.T. error is solved.
63
Operation in no detection of S.M.A.R.T. error
If S.M.A.R.T. errors are not detected at all, the [S.M.A.R.T.] of Physical Device is [Normal].
The raidcmd shows the status as shown in the figure below.
> raidcmd property -tg=pd -c=1 -p=1
RAID Controller #1 Physical Device #1
ID
: 0
Enclosure
: 1
Slot
: 1
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
S.M.A.R.T.
: Normal
>
[S.M.A.R.T.] of Physical Device is
[Normal] if S.M.A.R.T. error is
not detected.
Figure 23 Display of raidcmd in no detection of S.M.A.R.T. error
Operation when S.M.A.R.T. error is detected
If a S.M.A.R.T. error is detected, the [S.M.A.R.T.] of Physical Device is [Detected].
The raidcmd shows the status as shown in the figure below.
> raidcmd property -tg=pd -c=1 -p=1
RAID Controller #1 Physical Device #1
ID
: 0
Enclosure
: 1
Slot
: 1
Interface
: SAS
Vendor/Model
: Seagate ST12345678
Firmware Version
: BK09
Serial Number
: 1111
Capacity
: 146GB
Status
: Online
S.M.A.R.T.
: Detected
>
[S.M.A.R.T.] of Physical
Device changes to [Detected]
if S.M.A.R.T. error not
detected.
Figure 24 Display of raidcmd in detection of S.M.A.R.T. error
64
Changing of Settings of Universal RAID
Utility
This chapter describes how to change the settings of the Universal RAID Utility.
Changing TCP port number
If the TCP port number using Universal RAID Utility is same one of other application, you can change the
TCP port number using Universal RAID Utility.
A user having the administrator authority should change the TCP port number. Only users
having the administrator authority can change the TCP port number.
Step 1
Log in to the computer as a user having the administrator authority.
Step 2
Abort the raidcmd if it is used.
Step 3
Stop raidsrv service.
> /etc/init.d/raidsrv stop
Stopping raidsrv services:
>
3
Step 4
First, modify the configuration [socket]
file of raidsrv service. The configuration data port=52805
event port=52806
file of raidsrv service is
/etc/opt/nec/raidsrv/raidsrv.conf.
[log file]
Open this file by text editor, change
"data port" and "event port" in [socket] section to new TCP port numbers.
Step 5
Next, modify the
[network]
ip=127.0.0.1
configuration file of raidcmd. The
5
port=52805
configuration file of raidcmd is
[log_system]
/etc/opt/nec/raidcmd/raidcmd.conf.
max_size=10000
Open this file by text editor, change
"port" in [network] section to new TCP port number. The value of "port" is same value with "data port"
of raidsrv service.
Step 6
If complete to modify three
configuration files, start raidsrv service.
> /etc/init.d/raidsrv start
Starting raidsrv services:
>
65
6
[OK]
raidcmd Command Reference
This chapter describes commands of the raidcmd.
cc
[Overview]
Starts or stops Consistency Check.
[Format]
raidcmd cc -c=<controller> -l=<logicaldrive> -op={start|stop}
Command Parameter
-c=<controller>
-l=<logicaldrive>
-op={start|stop}
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
Specify the Logical Drive to be processed.
<logicaldrive> : Logical Drive Number
Specify whether Consistency Check is started or stopped.
start : Starts Consistency Check.
stop : Stops Consistency Check.
[Description]
Starts Consistency Check of the specified Logical Drive or stops Consistency Check executed for the
specified Logical Drive.
[Condition]
Starting Consistency Check can be provided for a Logical Drive with [Status] being [Online].
Stopping Consistency Check can be provided for a Logical Drive with [Status] being [Online] or
[Degraded].
ccs
[Overview]
Starts Consistency Check of Logical Drives in the RAID Controllers in which Patrol Read is not
supported.
[Format]
raidcmd ccs
[Description]
Starts Consistency Check of Logical Drives in the RAID Controllers in which Patrol Read is not
supported.
[Condition]
Consistency check is executed for Logical Drives with [Status] being [Online].
delld
[Overview]
Deletes a Logical Drive.
[Format]
raidcmd delld -c=<controller> -l=<logicaldrive> [-y]
Command Parameter
-c=<controller>
Description
Specify the RAID Controller to be processed.
66
Command Parameter
-l=<logicaldrive>
[-y]
Description
<controller> : RAID Controller Number
Specify the Logical Drive to be processed.
<logicaldrive> : Logical Drive Number
Deletes the Logical Drive immediately without displaying the
message of confirming that the Logical Drive may be deleted.
[Description]
Deletes the specified Logical Drive.
Logical drive allowed to be deleted
If more than one Logical Drive exist in a single Disk Array, only the Logical Drive located at the
end of the Disk Array can be deleted. Logical drives at the top and middle of the Disk Array
cannot be deleted.
The Logical Drive containing the boot partition cannot be deleted.
Deletion of Disk Array
If deleting the specified Logical Drive causes no Logical Drives to exist in the Disk Array at all,
the Disk Array itself will also be deleted.
[Condition]
This command can be executed only in the Advanced Mode.
econfig
[Overview]
Configures a RAID System with a RAID Controller easily.
[Format]
raidcmd econfig
[Description]
Executes easy configuration which can automatically configure a RAID System with the specified
RAID Controller. For details of the easy configuration, see "Configuring RAID System Easily".
hotspare
[Overview]
Makes or removes a Hot Spare.
[Format]
raidcmd hotspare -c=<controller> -p=<physicaldevice> -mr={make [-a=<diskarray1>
[,<diskarrayX>] ] | remove } [-y]
Command Parameter
-c=<controller>
-p=<physicaldevice>
-mr={make
[-a=<diskarray1>[,<diskarrayX>]] |
remove}
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
Specify the Physical Device to be processed.
<physicaldevice> : Physical Device Number
Specify that a Hot Spare is made or removed.
make: Makes a Hot Spare.
Depending on whether the -a option exists or not, the type of
the Hot Spare to be made varies (Global or Dedicated). Specify
Disk Arrays to be subject to hot swap if a Dedicated Hot Spare
is made.
If the -a option does not exist for making a Hot Spare, a Global
Hot Spare will be made with the specified Physical Device.
If the -a option exists and Disk Arrays are specified correctly for
making a Hot Spare, a Dedicated Hot Spare will be made with
the specified Physical Device.
<diskarray1>, <diskarrayX>: Disk Array Numbers
67
Command Parameter
[-y]
Description
remove: Removes a Hot Spare.
Changes the status without displaying the message of
confirming that the Hot Spare is made or removed.
[Description]
Makes a Global or Dedicated Hot Spare with the specified Physical Device or removes the Hot
Spare of the specified Physical Device.
[Condition]
The capacity of the Physical Device to be a Dedicated Hot Spare should be equal to or larger than
that of any Physical Device used in the Disk Array.
Dedicated Hot Spares cannot be made in a Disk Array containing one or more Logical Drives with
RAID Level being RAID 0.
init
[Overview]
Starts or stops Initialization.
[Format]
raidcmd init -c=<controller> -l=<logicaldrive> -op={start|stop} [-im={full|quick}]
Command Parameter
-c=<controller>
-l=<logicaldrive>
-op={start|stop}
[-im={full|quick}]
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
Specify the Logical Drive to be processed.
<logicaldrive> : Logical Drive Number
Specify that Initialize is started or stopped.
start: Starts Initialize.
stop: Stops Initialize.
Specify the Initialize Mode.
full: Full Initialize
quick: Quick Initialize
The full mode is selected if -im is omitted.
-im is valid only when -op=start is specified.
[Description]
Starts Initialize of the specified Logical Drive or stops Initialize being executed for the specified
Logical Drive.
[Condition]
Starting Initialize can be provided for a Logical Drive with its [Status] being [Online].
Stopping Initialize can be provided for a Logical Drive with its [Status] being [Online] or [Degraded].
mkldc
[Overview]
Creates a Logical Drive with advanced parameter settings.
[Format]
Making a Logical Drive having RAID Level of RAID 0, RAID 1, RAID 5 or RAID 6:
raidcmd mkldc -c=<controller> {-p=<physicaldevice1>, <physicaldevice2>
[,<physicaldeviceX>, ... ,<physicaldeviceZ>] | -a=<diskarray> } –rl={0 | 1 | 5 | 6} [-cp=<capacity>]
[-ss={1 | 2 | 4 | 8 | 16 | 32 | 64 | 128 | 256 | 512 | 1024}] [-cm={auto | writeback | writethru}]
[-im={full | quick}] [-y]
68
Command Parameter
-c=<controller>
{-p=<physicaldevice1>,
<physicaldevice2>
[,<physicaldeviceX>, ... ,<physicaldeviceZ
>] | -a=<diskarray> }
-rl={0 | 1 | 5 | 6}
[-cp=<capacity>]
[-ss={1 | 2 | 4 | 8 | 16 | 32 | 64 | 128 |
256 | 512 | 1024}]
[-cm={auto | writeback | writethru}]
[-im={full | quick}]
[-y]
Description
Specify the RAID Controller connecting with Physical Devices
used for the Logical Drive.
<controller> : RAID Controller Number
Specify Physical Devices used to create the Logical Drive or a
Disk Array.
Use -p option to specify Physical Devices.
<physicaldevice1,2,X,Z> : Physical Device Numbers.
Delimit Physical Devices with ",".
Specify -a option to specify a Disk Array.
<diskarray> : Disk Array Number
Specify the RAID Level of the Logical Drive to be created as
follows:
0 : RAID 0
1 : RAID 1
5 : RAID 5
6 : RAID 6
Specify the capacity of the Logical Drive to be created.
<capacity>: capacity in GB
Creates the Logical Drive of the maximum capacity available if
-cp is omitted.
Specify the Stripe Size of the Logical Drive to be created.
1KB, 2KB, 4KB, 8KB, 16KB, 32KB, 64KB, 128KB, 256KB,
512KB, 1024KB
The default value for the RAID Controller is used if -ss is
omitted.
Specify the Cache Mode of the Logical Drive to be created.
auto : Auto Switch
writeback : Write Back
writethru : Write Through
The default value for the RAID Controller is used if -cm is
omitted.
Specify the Initialize Mode of the Logical Drive to be created.
full : Full mode
quick : Quick mode
The full mode is used if -im is omitted.
Creates the Logical Drive immediately without displaying the
message of confirming that the Logical Drive may be created.
Making a Logical Drive having RAID Level of RAID 10:
raidcmd mkldc -c=<controller> -p=<physicaldevice1>,
<physicaldevice2> ,<physicaldevice3>,<physicaldevice 4> –rl=10 [-ss={1 | 2 | 4 | 8 | 16 | 32 | 64
| 128 | 256 | 512 | 1024}] [-cm={auto | writeback | writethru}] [-im={full | quick}] [-y]
Command Parameter
-c=<controller>
-p=<physicaldevice1>,
<physicaldevice2>
<physicaldevice3>,<physicaldevice4>
-rl=10
[-ss={1 | 2 | 4 | 8 | 16 | 32 | 64 | 128 |
256 | 512 | 1024}]
[-cm={auto | writeback | writethru}]
[-im={full | quick}]
Description
Specify the RAID Controller connecting with Physical Devices
used for the Logical Drive.
<controller> : RAID Controller Number
Specify Physical Devices used to create the Logical Drive.
<physicaldevice1,2,3,4> : Physical Device Numbers
Delimit the physical drives with ",".
Specify the RAID Level of the Logical Drive to be created.
10 : RAID 10
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
69
[-y]
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
Making a Logical Drive having RAID Level of RAID 50:
raidcmd mkldc -c=<controller>
-p=<physicaldevice1>,<physicaldevice2>,<physicaldevice3>,<physicaldevice4>,<physicaldevice5>,
<physicaldevice6>[,...,<physicaldeviceX>] –rl=50 [-ss={1 | 2 | 4 | 8 | 16 | 32 | 64 | 128 | 256 |
512 | 1024}] [-cm={auto | writeback | writethru}] [-im={full | quick}] [-y]
Command Parameter
-c=<controller>
-p=<physicaldevice1>,<physicaldevice2>
, <physicaldevice3>,<physicaldevice4>,
<physicaldevice5>,<physicaldevice6>
[,<physicaldeviceX>]
-rl=50
[-ss={1 | 2 | 4 | 8 | 16 | 32 | 64 | 128 |
256 | 512 | 1024}]
[-cm={auto | writeback | writethru}]
[-im={full | quick}]
[-y]
Description
Specify the RAID Controller connecting with Physical Devices
used for the Logical Drive.
<controller> : RAID Controller Number
Specify Physical Devices used to create the Logical Drive. The
number of Physical Devices must be six or larger and also even.
<physicaldevice1,2,3,4,5,6,X> : Physical Device Numbers.
Delimit the physical drives with ",".
Specify the RAID Level of the Logical Drive to be created.
50 : RAID 50
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
Same as the value specified when the RAID Level is RAID 0,
RAID 1, RAID 5 or RAID 6.
[Description]
Creates a Logical Drive with advanced parameter settings.
The raidcmd create a Logical Drive and terminates after Initialize is started. You can check the
progress and result of the Initialize by using "oplist" and "property" commands.
RAID Levels allowed to be created
RAID 0、RAID 1、RAID 5、RAID 6、RAID 10、RAID 50
Available Physical Devices
Physical Devices with [Status] of [Ready]
Physical Devices not used at all
Available Disk Array
Disk Array not used at all or having empty area at the end. The RAID Level of the Logical Drive to
be created must be the same as that of the Logical Drive existing on the same Disk Array.
Configuration of Disk Array and Logical Drive to be created
Creates a single Disk Array and a single Logical Drive with the specified Physical Devices if the
Disk Array is created newly.
Capacity of Logical Drive with RAID Level of RAID 10 or RAID 50
For the RAID Level of RAID 10 or RAID 50, use the entire areas of Physical Devices to create a
Logical Drive. You cannot specify the capacities of the Physical Devices.
[Condition]
This command can be executed only in the Advanced Mode.
mklds
[Overview]
Creates a Logical Drive with simple parameter settings.
[Format]
raidcmd mklds -c=<controller> -p=<physicaldevice1>, <physicaldevice2>
[,<physicaldeviceX>, ... ,<physicaldeviceZ>] –rl={1 | 5} [-y]
70
Command Parameter
-c=<controller>
-p=<physicaldevice1>,
<physicaldevice2>
[,<physicaldeviceX>, ... ,<physicaldeviceZ
>]
-rl={1 | 5}
[-y]
Description
Specify the RAID Controller connecting with Physical Devices
used for the Logical Drive.
<controller> : RAID Controller Number
Specify Physical Devices used to create the Logical Drive.
<physicaldevice1,2,X,Z> : Physical Device Number
Delimit the physical drives with ",".
Specify the RAID Level of the Logical Drive to be created.
1 : RAID 1
5 : RAID 5
Creates the Logical Drive immediately without displaying the
message of confirming that the Logical Drive may be created.
[Description]
Creates a Logical Drive simply by specifying only two parameters, or Physical Devices used for the
Logical Drive and RAID Level.
The raidcmd creates a Logical Drive and terminates after Initialize is started. You can check the
progress and result of the Initialize by using "oplist" and "property" commands.
RAID Levels allowed to be created
RAID 1、RAID 5
Available Physical Devices
Physical Devices with [Status] of [Ready]
Physical Devices not used at all
Configuration of Disk Array and Logical Drive to be created
Creates a single Disk Array and a single Logical Drive with the specified Physical Devices.
Other parameters
Creates a Logical Drive with parameters set as follows:
Capacity : Creates a Logical Drive by using the entire areas of Physical Devices. The actual
capacity varies depending on the RAID Level.
Stripe Size : 64KB
Cache Mode : Default mode of RAID Controller
Initialization Mode : Full
oplist
[Overview]
Displays the list of operations performed in a RAID Controller and their progresses.
[Format]
raidcmd oplist
[Description]
Displays the list of operations performed in a RAID Controller and their progresses.
Displayed operations
Initialization, Rebuild and Consistency Check
Display of terminated operation
oplist indicates operations being executed but does not indicate terminated operations.
optctrl
[Overview]
Allows you to set optional parameters of a RAID Controller.
[Format]
raidcmd optctrl -c=<controller> {-ip={high | middle | low} | -rp={high | middle | low} | -ccp={high |
middle | low} | -pr={enable | disable} | -prp={high | middle | low} | -be={enable | disable} }
71
Command Parameter
-c=<controller>
-ip={high | middle | low}
-rp={high | middle | low}
-ccp={high | middle | low}
-pr={enable | disable}
-prp={high | middle | low}
-be={enable | disable}
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
Specify the Initialize Priority.
high: High priority
middle: Middle priority
low: Low priority
Specify the Rebuild Priority.
high: High priority
middle: Middle priority
low: Low priority
Specify the Consistency Check Priority.
high: High priority
middle: Middle priority
low: Low priority
Specify whether Patrol Read is executed or not.
enable: Executed
disable: Not executed
Specify the Patrol Read Priority.
high: High priority
middle: Middle priority
low: Low priority
Specify whether the Buzzer is enabled or disabled.
enable: Enabled
disable: Disabled
[Description]
Allows you to set optional parameters of the specified RAID Controller (including Initialize Priority,
Rebuild Priority, Consistency Check Priority, Patrol Read execution and Priority, and Buzzer
enable/disable).
Only a single parameter can be set at a time. Concurrent set of more than one parameter is
disabled.
[Condition]
This command can be executed only in the Advanced Mode.
optld
[Overview]
Allows you to set optional parameters of a Logical Drive.
[Format]
raidcmd optld -c=<controller> -l=<logicaldrive> -cm={auto | writeback | writethru}
Command Parameter
-c=<controller>
-l=<logicaldrive>
-cm={auto | writeback | writethru}
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
Specify the Logical Drive to be processed.
<logicaldrive> : Logical Drive Number
Specify the Cache Mode
auto : Auto Switch
writeback : Write Back
writethru : Write Through
[Description]
Allows you to set optional parameters (Cache Mode) of the specified Logical Drive.
[Condition]
This command can be executed only in the Advanced Mode.
72
property
[Overview]
Displays the properties of RAID Controllers, Disk Arrays, Logical Drives and/or Physical Devices.
[Format]
raidcmd property –tg= { all | rc [-c=<controller>] | da -c=<controller> [-a=<diskarray>] | ld
-c=<controller> [-l=<logicaldrive>] | pd -c=<controller> [-p=<physicaldevice>] }
Command Parameter
-tg=all
-tg=rc [-c=<controller>]
-tg=da -c=<controller> [-a=<diskarray>]
-tg=ld -c=<controller> [-l=<logicaldrive>]
-tg=pd -c=<controller>
[-p=<physicaldevice>]
Description
Indicates the properties of all RAID Systems.
Indicates the property of the specified RAID Controller.
Specify a RAID Controller Number with -c to indicate the
property of the specific RAID Controller.
Omit -c to indicate the properties of all RAID Controllers.
<controller>: RAID Controller Number
Indicates the property of the Disk Array.
Specify a RAID Controller Number with -c.
Specify a Disk Array Number with -a to indicate the property of
the specific Disk Array.
Omit -a to indicate the properties of all Disk Arrays for the RAID
Controller specified with -c.
<controller> : RAID Controller Number
<diskarray>: Disk Array Number
Indicates the property of the Disk Array.
Specify a RAID Controller Number with -c.
Specify a Logical Drive Number with -a to indicate the property
of the specific Logical Drive.
Omit -l to indicate the properties of all Logical Drives for the
RAID Controller specified with -c.
<controller> : RAID Controller Number
<logicaldrive>: Logical drive number
Indicates the property of the Disk Array.
Specify a RAID Controller Number with -c.
Specify a Physical Device Number with -a to indicate the
property of the specific Physical Device.
Omit -p to indicate the properties of all Physical Devices for the
RAID Controller specified with -c.
<controller> : RAID Controller Number
<physicaldevice>: Physical device number
[Description]
Displays the properties of RAID Controllers, Disk Arrays, Logical Drives and/or Physical Devices. The
properties of all managed RAID Systems connected to the computer or those of specific RAID
Controllers, Disk Arrays, Logical Drives and Physical Devices can be displayed.
rebuild
[Overview]
Starts or stops Rebuild.
[Format]
raidcmd rebuild -c=<controller> -p=<physicaldevice> -op={start|stop}
Command Parameter
-c=<controller>
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
73
Command Parameter
-p=<physicaldevice>
-op={start|stop}
Description
Specify the Physical Device to be processed.
<physicaldevice> : Physical Device Number
Specify that Rebuild is started or stopped.
start: Starts Rebuild.
stop: Stops Rebuild.
[Description]
Starts Rebuild of the specified Physical Device or stops Rebuild being executed for the specified
Logical Drive.
[Condition]
This command can be executed only in the Advanced Mode.
Starting Rebuild can be executed for a Physical Device with [Status] being [Failed] used by a Logical
Drive with [Status] being [Degraded].
runmode
[Overview]
Changes the running mode of the raidcmd.
[Format]
raidcmd runmode [-md={a|s}]
Command Parameter
[-md={a|s}]
Description
Specify the altered running mode. If -md option is not specified,
shows the current running mode.
a: Advanced mode
s: Standard mode
[Description]
Changes the running mode of the raidcmd or indicates the current running mode.
Valid period of mode after change
The running mode is valid unless it is changed by the runmode command. The running mode
remains unchanged if the computer is rebooted.
[Condition]
Changing the running mode to the Standard Mode in the Standard Mode causes an error to occur.
Changing the running mode to the Advanced Mode in the Advanced Mode causes an error to occur.
sbuzzer
[Overview]
Stops the Buzzer on a RAID Controller.
[Format]
raidcmd sbuzzer -c=<controller>
Command Parameter
-c=<controller>
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
[Description]
Stops the Buzzer sounding in the specified RAID Controller.
The command terminates normally if it is executed without Buzzer sounding.
slotlamp
[Overview]
Turns on or off the DISK lamp of the computer or enclosure in which Physical Devices are installed.
74
[Format]
raidcmd slotlamp -c=<controller> -p=<physicaldevice> -sw={on|off}
Command Parameter
-c=<controller>
-p=<physicaldevice>
-sw={on|off}
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
Specify the Physical Device to be processed.
<physicaldevice> : Physical Device Number
Specify that the lamp is turned on or off.
on: Turns on the lamp.
off: Turns off the lamp.
[Description]
Turns on or off the DISK lamp on the computer or enclosure in which the specified Physical Device
is installed.
Executing the raidcmd with -sw=on while the DISK lamp is already ON causes the command to
terminate normally.
Executing the raidcmd with -sw=off while the DISK lamp is already OFF causes the command to
terminate normally.
stspd
[Overview]
Changes the status of a Physical Device to online or failed forcibly.
[Format]
raidcmd stspd -c=<controller> -p=<physicaldevice> -st={online|offline} [-y]
Command Parameter
-c=<controller>
-p=<physicaldevice>
-st={online|offline}
[-y]
Description
Specify the RAID Controller to be processed.
<controller> : RAID Controller Number
Specify the Physical Device to be processed.
<physicaldevice> : Physical Device Number
Specify the altered status.
online: Online status
offline: Failed status
Changes the status without the message of confirming that the
status may be changed.
[Description]
Changes the [Status] of the specified Physical Device to [Online] or [Failed].
[Condition]
This command can be executed only in the Advanced Mode.
75
Notes on Use of Universal RAID Utility
This chapter describes the notes on use of the Universal RAID Utility.
Operation Environment
Use of IPv6
The Universal RAID Utility cannot operate in the IPv6 (Internet Protocol version 6) environment. Use the
Universal RAID Utility in the IPv4 environment. To manage a RAID System in the IPv6 environment, use
the BIOS utility of the RAID Controller.
76
Appendix A : Glossary
The terms used on the Universal RAID Utility are listed in the tables below.
Basic Terms on RAID System
Term
Description
RAID System
The RAID System has the ability of using hard disk drives in a computer as
Disk Arrays.
The RAID System handles a single RAID Controller as a single system.
RAID Controller
The RAID Controller can use hard disk drives as Disk Arrays.
Physical Device
Physical Devices are used by a RAID System. For most RAID Systems,
Physical Devices mean hard disk drives. Physical Devices can be other
than hard disk drives if the RAID Controller can connect with devices other
than hard disk drives.
Disk Array
The virtual hard disk space is created by some Physical Devices. So, you
cannot see Disk Array on operating system. You can create Logical Drive
on Disk Array.
Logical Drive
The virtual hard disk drive is created on a Disk Array to be recognized by
OS. A specific RAID Level should be set for each Logical Drive.
Hot Spare
Hard disk drives of the type are prepared previously to be replaced with a
Physical Device in which a failure occurs.
Global Hot Spare
Available as a Hot Spare of any Disk Array in a single RAID Controller.
Dedicated Hot Spare
Available as a Hot Spare of a specific Disk Array in a single RAID
Controller.
Battery
The battery is intended to hold the information on the cache memory in a
RAID Controller if the power supplied to the RAID Controller is interrupted.
Cache Memory
The cache is intended to improve the I/O performance of a RAID
Controller.
Enclosure
Means a module equipped with slots to which Physical Devices are
inserted.
Fan Unit
Means a cooling fan unit installed in an enclosure.
Power Supply Unit
Means a power unit supplying power to an enclosure.
Power Sensor
Means a sensor monitoring the power supply unit in an enclosure.
Temperature Sensor
Means a sensor monitoring the temperature of an enclosure.
Enclosure Management Module
Means a module managing an enclosure.
77
Basic Terms on Functions of RAID System
Term
Description
Operation
Generic term of maintenance functions requiring certain periods for
executions such as Rebuild and Consistency Check
Configuration
Means the configuration of a RAID System.
Initialize
Writes 0s into the entire area of a Logical Drive to erase the data in the
Logical Drive.
Rebuild
Writes the data in a failed hard disk drive into a new hard disk drive
replaced to Rebuild the Logical Drive.
Consistency Check
Reads all sectors on hard disk drives configuring a Logical Drive to verify
the data or provide parity check.
Patrol Read
Reads all sectors on hard disk drives in a RAID System to check whether
errors occur or not.
Cache Mode
Indicates the mode in which data is written into the cache memory in a
RAID Controller.
Make Online
Means that a Physical Device is entered into the Online status manually.
Make Offline
Means that a Physical Device is entered into the Failed status manually.
Buzzer
Indicates a Buzzer installed in a RAID Controller. The Buzzer notifies you of
occurrence of a failure with sound.
Basic Terms on Universal RAID Utility
Term
Description
Standard Mode
Default running mode of Universal RAID Utility.
In the mode, you can use the standard functions for managing the RAID
System.
Advanced Mode
Maintenance/high-performance mode of Universal RAID Utility.
To use this mode, expert knowledge on RAID is required. You can mainly
use the functions required for maintenance jobs, functions of setting data
about a RAID System closely to configure the system and functions of
changing parameters.
Easy Configuration
The function is provided by the Universal RAID Utility to configure a RAID
System easily.
Allows an optimum RAID System to be configured only by deciding the
number of Physical Devices used by a Logical Drive and the number of
Logical Drives for each RAID Controller.
RAID Log
Means the log for the Universal RAID Utility.
OS Log
Means the log provided by OS.
Alert
Means the operation of sending events such as failures occurred in a RAID
System to external systems.
rescan
Means the operation of acquiring all the information on managed RAID
Systems to update the information managed by the Universal RAID Utility
to the latest.
78
Appendix B : Logs/Events
The list of log and event , alert messages that Universal RAID Utility logs to RAID Log and syslog.
Event Source, Alert Type
Alert Type : URAIDUTL
[Log]
[Alert]
R : Universal RAID Utility logs this event to RAID Log.
O : Universal RAID Utility logs this event to syslog.
M and MA : Universal RAID Utility send this event to NEC ESMPRO Manager as alert.
[ Address ] description in [Description]
The [ Address ] description is different from the version of Universal RAID Utility.
Category of Event
Type
RAID Controller
Battery
1
Physical Device
2
Description
[CTRL:%1(ID=%2)]
%1 : Number of RAID Controller
%2 : ID of RAID Controller
[CTRL:%1(ID=%2) PD:%3(ID=%4 ENC=%5 SLT=%6) %7%8%9]
%1 : Number of RAID Controller
%2 : ID of RAID Controller
%3 : Number of Physical Device
%4 : ID of Physical Device
%5 : Enclosure Number of Physical Device
%6 : Slot Number of Physical Device
%7 : Vendor of Physical Device
%8 : Model of Physical Device
%9 : Firmware Version of Physical Device
Logical Drive
3
[CTRL:%1(ID=%2) LD:%3(ID=%4)]
%1 : Number of RAID Controller
%2 : ID of RAID Controller
%3 : Number of Logical Drive
%4 : ID of Logical Drive
79
Category of Event
Enclosure
Type
4
Description
[CTRL:%1(ID=%2) ENC:%3]
%1 : Number of RAID Controller
%2 : ID of RAID Controller
%3 : Number of Enclosure
Power Supply Unit in
Enclosure
5
Fan Unit in Enclosure
6
[CTRL:%1(ID=%2) ENC:%3 POW:%4]
%1 : Number of RAID Controller
%2 : ID of RAID Controller
%3 : Number of Enclosure
%4 : Number of Power Supply Unit
[CTRL:%1(ID=%2) ENC:%3 FAN:%4]
%1 : Number of RAID Controller
%2 : ID of RAID Controller
%3 : Number of Enclosure
%4 : Number of Fan Unit
80
Event ID
(hex digit)
0201
(400000C9)
0202
(400000CA)
0203
(400000CB)
0204
(400000CC)
Severi
ty
Informa
tion
Informa
tion
Informa
tion
Informa
tion
0205
(400000CD)
0206
(400000CE)
0207
(400000CF)
0208
(400000D0)
0209
(400000D1)
0210
(400000D2)
0211
(800000D3)
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Warning
0212
(C00000D4)
0301
(4000012D)
0302
(4000012E)
0303
(4000012F)
0304
(C0000130)
0305
(80000131)
0306
(4000132)
0307
(40000133)
0308
(C0000134)
0309
(40000135)
Fatal
Description
Log
[Address Type 1 ] The buzzer of RAID
Controller is enable.
[Address Type 1 ] The buzzer of RAID
Controller is disable.
[Address Type 1 ] The Rebuild Priority of RAID
Controller was changed. (Value : %2)
[Address Type 1 ] The Consistency Check
Priority of RAID Controller was changed.
(Value: %2)
[Address Type 1 ] The Initialize Priority of RAID
Controller was changed. (Value : %2)
[Address Type 1 ] Auto Patrol Read function is
enable.
[Address Type 1 ] Auto Patrol Read function is
disable.
[Address Type 1 ] A Patrol Read Priority of
RAID Controller was changed. (Value : %2)
[Address Type 1 ] Patrol Read was started.
R
[Address Type 1 ] Patrol Read completed.
Alert
Deal Method
Memo
R
R
%2 : Changed value
*1
R
%2 : Changed value
*1
R
%2 : Changed value
*1
R
R
R
%2 : Changed value
*1
R
R
[Address Type 1 ] A Warning Error happened
to RAID Controller. Detail : %2
RO
M
[Address Type 1 ] A Fatal Error happened to
RAID Controller. Detail : %2
[Address Type 2 ] Physical Device is Online.
RO
MA
RO
M
[Address Type 2 ] Physical Device is Ready.
RO
M
[Address Type 2 ] Physical Device is Hot
Spare.
[Address Type 2 ] Physical Device is Failed.
RO
M
RO
MA
Warning
[Address Type 2 ] Detected S.M.A.R.T. Error.
RO
Informa
tion
Informa
tion
Fatal
[Address Type 2 ] Rebuild was started.
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Fatal
Summary
RAID Controller
Warning
RAID Controller Fatal
Please check the RAID Controller. If some
kind of problem happens to the RAID
Controller repeatedly, please replace it.
Please replace the RAID Controller.
None
MA
Physical Device
Online
Physical Device
Ready
Physical Device Hot
Spare
Physical Device
Failed
S.M.A.R.T. Error
RO
MA
Rebuild Started
None
[Address Type 2 ] Rebuild completed.
RO
MA
Rebuild Completed
None
[Address Type 2 ] Rebuild failed.
RO
MA
Rebuild Failed
Please replace the Physical Device.
[Address Type 2 ] Rebuild was stopped.
RO
MA
Rebuild Stopped
None
81
None
None
Please replace the Physical Device.
Please replace the Physical Device.
%2 : Detail
information
%2 : Detail
information
Event ID
(hex digit)
Severi
ty
0311
(40000137)
0312
(40000138)
0313
(40000139)
0314
(4000013A)
0315
(4000013B)
0316
(4000013C)
0317
(8000013D)
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Warning
0318
(C000013E)
0319
(4000013F)
Fatal
Informa
tion
Description
Log
Alert
[Address Type 2 ] Physical Device was
inserted.
[Address Type 2 ] Physical Device was
removed.
[Address Type 2 ] Global Hot Spare created.
RO
M
RO
M
[Address Type 2 ] Dedicated Hot Spare
created.
[Address Type 2 ] Global Hot Spare removed.
R
[Address Type 2 ] Dedicated Hot Spare
removed.
[Address Type 2 ] A Warning Error happened
to Physical Device. Detail : %6
R
Summary
Physical Device
Inserted
Physical Device
Removed
Deal Method
None
None
R
R
RO
M
Physical Device
Warning
RO
MA
Physical Device Fatal
RO
MA
None
[Address Type 2 ] An Uncorrectable Medium
Error happened to Physical Device.
RO
MA
Physical Device
Medium
Error(Correctable)
Physical Device
Medium
Error(Uncorrectable)
Logical Drive Online
If there is Hot Spare, RAID System will rebuild
automatically. If there is not it, please replace
the Physical Device and rebuild it.
Please replace the Physical Device and
recreate the Logical Drive. Next restore the
backup data to the Logical Drive.
[Address Type 2 ] A Fatal Error happened to
Physical Device. Detail : %6
[Address Type 2 ] A Correctable Medium Error
happened to Physical Device.
0320
(C0000140)
Fatal
0401
(40000191)
0402
(80000192)
Informa
tion
Warning
[Address Type 3 ] Logical Drive is Online.
RO
M
[Address Type 3 ] Logical Drive is Degraded.
RO
MA
Logical Drive
Degraded
0403
(C0000193)
Fatal
[Address Type 3 ] Logical Drive is Offline.
RO
MA
Logical Drive Offline
0404
(40000194)
0405
(40000195)
0406
(C0000196)
Informa
tion
Informa
tion
Fatal
MA
Initialization Failed
0407
(400000197)
0409
(40000199)
0410
(4000019A)
Informa
tion
Informa
tion
Informa
tion
[Address Type 3 ] Initialization was started.
R
[Address Type 3 ] Initialization completed.
R
[Address Type 3 ] Initialization failed.
Memo
RO
[Address Type 3 ] Initialization was stopped.
R
[Address Type 3 ] Consistency Check was
started.
[Address Type 3 ] Consistency Check
completed.
R
R
82
Please check the Physical Device. If some
kind of problem happens to the Physical
Device repeatedly, please replace it.
Please replace the Physical Device.
Please replace the Physical Device.
None
Please retry Initialization. If Initialization
failed repeatedly, the RAID System may have
some kind of problem. Please deal with the
problem of the RAID System.
%3 : Detail
information
%3 : Detail
information
Event ID
(hex digit)
Severi
ty
Log
Alert
Fatal
[Address Type 3 ] Consistency Check failed.
RO
MA
Consistency Check
Failed
Please retry Consistency Check. If
Consistency Check failed repeatedly, the RAID
System may have some kind of problem.
Please deal with the problem of the RAID
System.
0412
(4000019C)
0413
(C000019D)
Informa
tion
Fatal
[Address Type 3 ] Consistency Check was
stopped.
[Address Type 3 ] Data Inconsistency Error
happened to Logical Drive by Consistency
Check and corrected it.
R
MA
Data Inconsistency
Error Corrected
Please replace the Physical Device for the
prevention of failure(You need to ask it which
Physical Device do you replace). Next restore
the backup data to the Logical Drive after
replacement of Physical Device.
[Hint]
Please execute Consistency Check again
when the load of system is low. If the same
error does not occur on the second test, the
Physical Device does not have any problem. If
the same error occurs, please replace the
Physical Device.
0415
(4000019F)
0416
(400001A0)
0417
(400001A1)
0418
(400001A2)
0419
(400001A3)
0420
(800001A4)
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Informa
tion
Warning
[Address Type 3 ] Logical Drive was created.
R
[Address Type 3 ] Logical Drive was deleted.
R
[Address Type 3 ] The Cache Mode of Logical
Drive was changed. (Value : %3)
[Address Type 3 ] Background Initialization
was started.
[Address Type 3 ] Background Initialization
completed.
[Address Type 3 ] Background Initialization
failed.
RO
M
Cache Mode
Changed
None
MA
Background
Initialization Failed
The RAID System may have some kind of
problem. Please deal with the problem of the
RAID System.
0421
(400001A5)
0422
(C00001A6)
Informa
tion
Fatal
[Address Type 3 ] Background Initialization
was stopped.
[Address Type 3 ] An Uncorrectable Error
happened to Logical Drive.
RO
MA
Logical Drive
Uncorrectable Error
0423
(400001A7)
Informa
tion
[Address Type 3 ] A Corrected Error happened
to Logical Drive.
RO
MA
Logical Drive
Corrected Error
Please replace the Physical Device (You need
to ask it which Physical Device do you
replace). After replacement of Physical
Device, recreate the Logical Drive and restore
the backup data to it.
Please replace the Physical Device for the
prevention of failure(You need to ask it which
Physical Device do you replace). Next restore
the backup data to the Logical Drive after
replacement of Physical Device.
0411
(C000019B)
Description
RO
Summary
Deal Method
R
R
83
%3 : Changed value
*1
R
RO
Memo
Event ID
(hex digit)
Severi
ty
Description
Log
Alert
Summary
0424
(800001A8)
Warning
[Address Type 3 ] A Warning Error happened
to Logical Drive. Detail : %3
RO
M
0425
(C00001A9)
Fatal
[Address Type 3 ] A Fatal Error happened to
Logical Drive. Detail : %3
RO
MA
Logical Drive Fatal
0501
(400001F5)
0502
(800001F6)
Informa
tion
Warning
[Address Type 1 ] Battery was detected.
MA
Battery Disconnect
Please check the Battery. If some kind of
problem happen to the Battery repeatedly,
please replace it.
0503
(400001F7)
0504
(400001F8)
0505
(800001F9)
Informa
tion
Informa
tion
Warning
[Address Type 1 ] Battery was replaced.
R
[Address Type 1 ] The temperature of battery
is normal.
[Address Type 1 ] The temperature of battery
is high.
R
0506
(800001FA)
Warning
0507
(800001FB)
0508
(800001FC)
0601
(80000259)
Warning
Please check the Battery. If some kind of
problem happens to the Battery repeatedly,
please replace it.
Please check the Battery. If some kind of
problem happens to the Battery repeatedly,
please replace it.
Please replace the Battery.
0602
(C000025A)
Fatal
0603
(8000025B)
[Address Type 1 ] Battery was disconnected.
Logical Drive
Warning
Deal Method
R
RO
RO
M
Battery Temperature
High
[Address Type 1 ] The voltage of battery is low.
RO
M
Battery Voltage Low
[Address Type 1 ] A Fatal Error happened to
battery .
[Address Type 1 ] The Battery state is
unstable.
[Address Type 4 ] A Warning Error happened
to Enclosure.
RO
MA
Battery Fatal
RO
M
Enclosure Warning
[Address Type 4 ] A Fatal Error happened to
Enclosure.
RO
MA
Warning
[Address Type 4 ] The temperature of
Enclosure is Warning level.
RO
M
0604
(C000025C)
Fatal
[Address Type 4 ] The temperature of
Enclosure is Fatal level.
RO
MA
0605
(8000025D)
Warning
[Address Type 5 ] An error happened to the
Power Supply Unit of Enclosure.
RO
MA
Enclosure Power
Supply Unit Error
0606
(8000025E)
Warning
[Address Type 6 ] An error happened to the
Fan Unit of Enclosure.
RO
MA
Enclosure Fan Unit
Error
Warning
Warning
The RAID Controller and/or the Physical
Device may have some kind of problem. You
need to ask it which component has broken.
The RAID Controller and/or the Physical
Device may have some kind of problem. You
need to ask it which component has broken.
RO
Enclosure Fatal
Enclosure
Temperature
Warning
Enclosure
Temperature Fatal
84
Please check the Enclosure. If some kind of
problem happens to the Enclosure repeatedly,
please deal with the problem of the
Enclosure.
Please check the Enclosure. If some kind of
problem happens to the Enclosure repeatedly,
please deal with the problem of the
Enclosure.
Please check the Fan Unit of the Enclosure. If
some kind of problem happens to the Fan
Unit, please deal with the problem.
Please check the Fan Unit of the Enclosure. If
some kind of problem happens to the Fan
Unit, please deal with the problem.
Please check the Power Supply Unit of the
Enclosure. If some kind of problem happens
to the Power Supply Unit, please deal with the
problem.
Please check the Fan Unit of the Enclosure. If
some kind of problem happens to the Fan
Unit, please deal with the problem.
Memo
%3 : Detail
Information
%3 : Detail
information
Event ID
(hex digit)
0701
(400002BD)
0702
(400002BE)
Severi
ty
Informa
tion
Informa
tion
Description
[Address Type 1 ] The Configuration was
cleared.
raidsrv Configuration
Log
Alert
RO
M
Summary
Configuration
Cleared
O
Deal Method
Memo
None
X, Y, Z : Number of
Physical Device used
in Logical Drive
[CTRL:%1(ID=%2)] Vendor Product Firmware
Version
[LD:%3(ID=%4)] RAID:RAIDlevel PD:X,Y,Z
(count of LD STS:Status
[PD:%5(ID=%6 ENC=%7 SLT=%8]
Vendor/Model Firmware Version STS:Status
%1 : Number of RAID Controller
%2 : ID of RAID Controller
%3 : Number of Logical Drive
%4 : ID of Logical Device
%5 : Number of Physical Device
%6 : ID of Physical Device
%7 : Enclosure Number of Physical Device
%8 : Slot Nuimber of Physical Device
*1 : This item may not include in log message by the type of RAID Controller
85
Download PDF
Similar pages