advertisement
Hitachi Compute Rack Series
MegaRAID Storage Manager
Instruction Manual
F
AST
F
IND
L
INKS
Product Version
Getting Help
Contents
MK-90CRC010-01
© 2010-2013 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.
Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users.
Some of the features described in this document might not be currently available.
Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at
https://portal.hds.com
.
Notice: Hitachi, Ltd., products and services can be ordered only under the terms
and conditions of the applicable Hitachi Data Systems Corporation agreements.
The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of
Hitachi, Ltd., in the United States and other countries.
Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage,
Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star
Network, and Universal Storage Platform are registered trademarks of Hitachi Data
Systems Corporation.
AIX, AS/400, DB2, Domino, DS8000, Enterprise Storage Server, ESCON, FICON,
FlashCopy, IBM, Lotus, OS/390, RS6000, S/390, System z9, System z10, Tivoli,
VM/ESA, z/OS, z9, zSeries, z/VM, z/VSE are registered trademarks and DS6000,
MVS, and z10 are trademarks of International Business Machines Corporation.
All other trademarks, service marks, and company names in this document or website are properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft
Corporation.
ii
MegaRAID Storage Manager Instruction Manual
Contents
Abbreviation of Disk Array Management Utility .............................................. viii
Version of MegaRAID Storage Manager .......................................................... ix
Restrictions on use of MegaRAID Storage Manager ..............................................1-5
With Centralized management by Linux........................................................1-5
When introducing network security ..............................................................1-5
Changing an IP address, enabling or disabling a network, or connecting or
MegaRAID Storage Manager of management PC and management server.......1-9
System environment required for MegaRAID Storage Manager .....................1-10
MegaRAID Storage Manager.................................................................. 2-1
Installing and removing MegaRAID Storage Manager ...........................................2-2
MegaRAID Storage Manager Instruction Manual
Starting MSM (for remote connection) ........................................................2-60
Displaying multiple connected servers ........................................................2-64
Switching servers to be displayed (for remote connection) ...........................2-67
Screen configuration and descriptions of MegaRAID Storage Manager .................2-72
Functions of MegaRAID Storage Manager..........................................................2-82
Changing the setting of virtual drive(s) .....................................................2-113
Consistency check of virtual drives ...........................................................2-118
Diagnosing cache back module (BBU).......................................................2-145
Displaying task progress and terminating a task ........................................2-157
Setting network security exceptions..........................................................2-161
Operation of Disk Arrays ........................................................................3-1
Periodical consistency check of LSI Software RAID virtual drives.................... 3-2
Checking the status of both disk array and physical drives ............................ 4-2
iv Contents
MegaRAID Storage Manager Instruction Manual
Contacting the maintenance company ..........................................................4-3
MegaRAID Storage Manager Instruction Manual
Preface
This document describes how to use the MegaRAID Storage Manager.
This preface includes the following information:
Notice: The use of MegaRAID Storage Manager and all other Hitachi Data
Systems products is governed by the terms of your agreement(s) with Hitachi
Data Systems.
Preface
vii
MegaRAID Storage Manager Instruction Manual
Intended Audience
This document is intended for the personnel who are involved in managing, configuring and operating the Compute Rack.
Product Version
This document revision applies to MegaRAID Storage Manager version
11.08.03-02.
Release Notes
Release notes contain requirements and more recent product information that may not be fully described in this manual. Be sure to review the release notes before installation.
Document Revision Level
Revision Date Description
MK-90CRC010-02
MK-90CRC010-03
December 2012
July 2013
Revision 02, supersedes and replaces Revision 01
Revision 03, supersedes and replaces Revision 02
Document Organization
The table below provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter.
Chapter Description
This chapter explains what you should know about MegaRAID Storage
Manager (MSM) before use. Read this chapter before you uses the product.
Chapter 2, MegaRAID Storage Manager
This chapter explains how to install, remove, configure, and use MSM.
Chapter 3, Operation of Disk Arrays
This chapter explains how to operate disk arrays.
Chapter 4, In the Event of a Fault
This chapter explains the troubleshooting procedures against disk array faults.
This chapter explains a MSM events list etc.
Abbreviation of Disk Array Management Utility
In this manual, MegaRAID Storage Manager is abbreviated to the following:
•
MegaRAID Storage Manager (hereafter MSM)
viii Preface
MegaRAID Storage Manager Instruction Manual
Version of MegaRAID Storage Manager
The version number displayed in the windows of MegaRAID Storage Manager shown in this manual may differ from the version number of your MegaRAID
Storage Manager.
MegaRAID Storage Manager Instruction Manual
Document Conventions
The term "Compute Rack" refers to all the models of the Compute Rack, unless otherwise noted.
This document uses the following typographic conventions:
Convention Description
Bold
Italic
Indicates text on a window, other than the window title, including menus, menu options, fields, and labels. Example: Click OK.
Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file
Note: Angled brackets (< >) are also used to indicate variables. screen/code
Indicates text that is displayed on screen or entered by the user.
Example:
# pairdisplay -g oradb
< > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example:
# pairdisplay -g <group>
Note: Italic font is also used to indicate variables.
[ ] square brackets Indicates optional values. Example: [ a | b ] indicates that you can choose a, b, or nothing.
{ } braces Indicates required or expected values. Example: { a | b } indicates that you must choose either a or b.
| vertical bar underline
Indicates that you have a choice between two or more options or arguments.
Examples:
[ a | b ] indicates that you can choose a, b, or nothing.
{ a | b } indicates that you must choose either a or b.
Indicates the default value. Example: [ a | b ]
This document uses the following icons to draw attention to information:
Icon Meaning Description
NOTICE
WARNING
CAUTION
NOTICE
This indicates the presence of a potential risk that might cause death or severe injury.
This indicates the presence of a potential risk that might cause relatively mild or moderate injury.
This indicates the presence of a potential risk that might cause severe damage to the equipment and/or damage to surrounding properties.
This indicates notes not directly related to injury or severe damage to equipment.
Note
Tip This indicates advice on how to make the best use of the equipment.
x Preface
MegaRAID Storage Manager Instruction Manual
Getting Help
If you purchased this product from an authorized HDS reseller, contact that reseller for support. For the name of your nearest HDS authorized reseller, refer to the HDS support web site for locations and contact information. To contact the Hitachi Data Systems Support Center, please visit the HDS website for current telephone numbers and other contact information: http://support.hds.com
.
Before calling the Hitachi Data Systems Support Center, please provide as much information about the problem as possible, including:
•
The circumstances surrounding the error or failure.
•
The exact content of any error message(s) displayed on the host system(s).
Comments
Please send us your comments on this document: [email protected]
.
Include the document title, number, and revision, and refer to specific sections and paragraphs whenever possible. All comments become the property of
Hitachi Data Systems Corporation. Thank you!
MegaRAID Storage Manager Instruction Manual
xii Preface
MegaRAID Storage Manager Instruction Manual
1
Usage Precautions
This chapter explains what you should know about MegaRAID Storage
Manager (MSM) before use. Read this chapter before you uses the product.
Restrictions on use of MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
RAID utility
This system unit supports two types of RAID utilities, Server installation and
monitoring tool internal storage monitor and MSM.
If you use unified management by MSM, install MSM.
For Server installation and monitoring tool internal storage
monitor, see "Server installation and monitoring tool User's Guide - internal storage monitoring functions".
MegaRAID Storage Manager
MSM is the utility software for managing disk array-mounted system units.
MSM consists of MegaRAID Storage Manager Server (MSM Server) and
MegaRAID Storage Manager Client (MSM Client).
A MSM instance becomes an MSM Server or an MSM Client depending on the specification made at the time of installation.
In an environment without Server installation and monitoring tool internal
storage monitor / MSM installed, you might fail to detect a fault that causes loss of critical data or suffer inconvenience in fault analysis. Make sure that you install and use Server installation and monitoring tool internal storage
monitor / MSM.
When you update MSM, always remove the old version before installing the new version.
A management PC is a PC that manages and monitors servers by MSM
Client. A "management server" is a server that manages and monitors servers including itself. A "managed server" is a server that is managed and monitored.
MSM provides the following functions:
•
Monitoring, managing, and maintaining disk array controllers and physical and virtual drives connected to disk array controllers, as well as remotely conducting these operations from a management PC
•
Centralized management
MegaRAID Storage Manager Instruction Manual
MSM consists of the following modules: (This is different from the actual program configuration.)
Table 1-1
General module Description
MSM Server
MSM Client
Core of MSM. It conducts various fault monitoring.
(This module outputs events to the system log.)
Displays fault events on the GUI.
(It is also used for remote management with a management PC.)
MSM SNMP
MSM remote
Reports faults via the SNMP interface.
Conducts real-time communication between different MSM instances over the network.* 1
*1: This module sends multicast packets on the network every five seconds.
IP address: 229.111.112.12 (A packet is sent from each LAN port.)
Content and operation of an MSM installation depend on its installation format.
Table 1-2
No
.
Installation format
1 Complete
Installed content and its operation
2 Standalone
(Recommended installation format)
3 Client
Management and operation is enabled by MSM Server itself and by remote control.
All modules except MSM remote and MSM SNMP
(recommended) or all modules except MSM remote
Operation is enabled only by MSM Server itself.
MSM Client module
Remote management and operation with a management PC is enabled.
MegaRAID Storage Manager Instruction Manual
Centralized management of MSM is enabled from a management PC.
Management PC
MSM Client
Centralized management from management PC
Managed server 1
(MSM Client, MSM Server)
Managed server 2
(MSM Client, MSM Server)
Manage server 3
(MSM Client, MSM Server)
Figure 1-1
A single management server can manage multiple servers including itself. If there is only one server, the server can be its own manager.
Management server
(Managed server 1)
(MSM Client, MSM Server)
Managed server 2
(MSM Client, MSM Server)
Managed server 3
(MSM Client, MSM Server)
Figure 1-2
A management PC cannot manage a server that is connected to a network segment different from that of the management PC itself.
When server management is centralized by a management PC, place the servers in the same segment.
For centralized management by the MSM remote monitoring, a multicast packet is sent on the network every five seconds for each server.
(Recommended installation format)
When you do not conduct central management from a management PC or a management server, which also manages itself, install MSM in the
"Standalone" format.
OS event log logging and notification by pop-up windows are made only at the system unit where the event has occurred.
The above processing is not performed on the remotely connected management PC.
Services MrMonitor and MrMonitor monitoring are not installed in MSM
Ver.11.08.XX.XX or later.
MegaRAID Storage Manager Instruction Manual
Restrictions on use of MegaRAID Storage Manager
This section explains the restrictions that you should know before using MSM
(MSM Client) with a management PC.
For other restrictions, see " Restrictions " on page 2-184
.
With Remote monitoring
In an environment where centralized management is conducted, make sure that the MSM Client of the management PC has been stopped when you restart or switch off a managed server.
If you restart or power off a managed server with the MSM Client running, the MSM Client becomes silent for about five minutes.
With Centralized management by Linux
When MSM is installed on Linux®, set the host name in the format conforming to the fully qualified domain name (FQDN). Remote monitoring does not work if a host name does not conform to the FQDN format.
When introducing network security
MSM uses its reserved ports 3071 and 5571. These port numbers cannot be changed. When introducing network security, register these ports as exceptions.
When you use the firewall of Windows or Red Hat Enterprise Linux, you need to register the MSM module as an exception. For Linux, MSM functions are
limited. See " Setting network security " on page 2-161
for details.
IP addresses
MSM needs to obtain an IP address for its operation. Set an IP address for each system unit. When a system unit obtains an IP address automatically, connect the system unit to a DHCP server.
Restart the system unit after setting an IP address.
Disable an unused LAN if any.
For centralized management of managed servers, set the default gateway address.
When there are multiple LAN addresses, the LAN address with the highest bind priority is configured as the default IP address of MSM.
MegaRAID Storage Manager Instruction Manual
In an environment where an IP address cannot be obtained, MSM may not be able to issue event notifications (That is, MSM may not be able to record events in the application log and MegaRAID Storage Manager log).
In this case, an event is registered in the Windows application log with source: MSMFramework, Type: Warning, and Event ID: 1.
MegaRAID Storage Manager Instruction Manual
Changing an IP address, enabling or disabling a network, or connecting or disconnecting a TP line
In the event of IP changing an address, enabling or disabling a network, or connecting or disconnecting a TP line, stop MSM service according to the following procedure:
For Windows:
1. Activate the service.
2. Right-click the MSMFramework service, and select [Stop (O)].
3. The Another Service Stop window opens. Click [Yes (Y)].
4. Confirm that the MSMFramework service has stopped and the [State] has become blank.
5. Change an IP address, enable or disable network, or connect or disconnect a TP line.
6. Right-click the MSMFramework service, and select [Start (S)].
7. Confirm that the MSMFramework service has started and the [State] has become Started.
8. Restart the system unit.
The procedure is completed.
If you fail to follow the above procedure, MSM may become unstable
(unable to display status of servers including itself, or having CPU overload). If the system shows such a phenomenon, execute the above procedure excluding step 5.
If no LAN cable is connected although a LAN port is available with a fixed IP address in the OS setup, the following pop-up message may appear after the system unit is started.
Action: Confirm the following and restart the system unit.
- Check the connection of the LAN port and the LAN cable.
- Disable an unused LAN port if any.
MegaRAID Storage Manager Instruction Manual
For Linux:
1. At /etc/rc.d/init.d/, stop the following service by the stop command:
• vivaldiframeworkd
[Command]
# service vivaldiframeworkd stop
2. Change an IP address, enable or disable a network, or connect or disconnect a TP line.
3. At /etc/rc.d/init.d/, start the following service by the start command:
• vivaldiframeworkd
[Command]
# service vivaldiframeworkd start
4. Restart the system unit.
The procedure is completed.
If you fail to follow the above procedure, MSM may become unstable
(unable to display status of servers including itself, or having CPU overload). If the system shows such a phenomenon, repeat the procedure above excluding step 3.
If no LAN cable is connected although a LAN port is available with a fixed IP address in the OS setup, the following pop-up message may appear after the system starts.
Action: Confirm the following and restart the system unit.
- Check the connection of the LAN port and the LAN cable.
- Disable an unused LAN port if any.
MegaRAID Storage Manager Instruction Manual
MegaRAID Storage Manager of management PC and management server
The MSM version differs depending on a model.
If system units of different MSM versions exist in the same network, the management PC or the management server might not be able to connect to a managed server.
In such a case, update the MSM of the management PC to the latest version before using it. If centralized management by a management PC is not conducted, let the system unit with the latest version of MSM take the management server role.
Centralized management by a management PC
Update MSM of management PC to the latest version.
Management PC
MSM Client
Latest version
Managed server 1
(MSM Client, MSM Server)
Latest version
Managed server 2
(MSM Client, MSM Server)
Old version
Managed server 3
(MSM Client, MSM Server)
Old version
Figure 1-3
Centralized management by a management server
Management server
(Managed server 1)
(MSM Client, MSM Server)
Latest version
Management server
(Managed server 2)
(MSM Client, MSM Server)
Old version
Management server
(Managed server 3)
(MSM Client, MSM Server)
Old version
Let the system unit with the latest version of MSM take the management server role
Figure 1-4
For MSM update procedure, see " Installing and removing MegaRAID Storage
.
You must restart the system unit after MSM update.
MegaRAID Storage Manager Instruction Manual
System environment required for MegaRAID Storage Manager
MSM requires a system environment that satisfies the following conditions:
•
Intel Pentium or equivalent processors
•
A system memory capacity of at least 256 MB (512 MB recommended)
•
A network interface (when remote management functionality is used)
•
A spare capacity of 400 MB or more in the physical drive
(We recommend a spare capacity of 1 GB or more including the space for log files.)
•
A mouse or other pointing device
•
A graphic controller and a display with 800 x 800 dots or more
(We recommend a resolution of 1024 x 768 or higher.)
•
For Windows:
Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or
Windows XP
•
For Linux:
Red Hat Enterprise Linux Server 6, Red Hat Enterprise Linux 5
•
TCP/IP protocol installation (when the remote management function is used)
MegaRAID Storage Manager Instruction Manual
LSI Software RAID
For LSI Software RAID, the functions of MSM listed below cannot be used:
Table 1-3
Function Description Reference pages
Expansion of virtual drive capacity
Write cache change
LED blinking
Cache back module (BBU) diagnosis
Enable/disable setting of
SMART copyback
Firmware update
Patrol Read setting
Task rate setting
Setting of power-saving mode of physical drives
Setting of consistency check processing method
SSD Guard
TM
Buzzer setting of disk array controller
Expands the capacity by adding a new physical drive to the existing virtual drive.
Changes the cache setting of disk array controller.
Makes LED of each physical drive blink.
Diagnoses the cache back module (BBU).
Changes the enable/disable setting of SMART copyback.
* This function is configured with MegaCli.
Updates the firmware of disk array controller.
Configures Patrol Read, which runs in the background.
Sets the rates of various tasks.
Sets the power-saving mode of physical drives.
Sets consistency check processing method.
Configures the buzzer of disk array controller.
-
-
-
-
-
-
MegaRAID Storage Manager Instruction Manual
MegaRAID Storage Manager Instruction Manual
2
MegaRAID Storage Manager
This chapter explains how to install, remove, configure, and use MSM.
Installing and removing MegaRAID Storage Manager
Activating MegaRAID Storage Manager
Exiting MegaRAID Storage Manager
Screen configuration and descriptions of MegaRAID Storage Manager
Functions of MegaRAID Storage Manager
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-1
Installing and removing MegaRAID Storage Manager
In an environment without Server installation and monitoring tool internal
storage monitor / MSM installed, you might fail to detect a fault that causes loss of critical data or suffer inconvenience in fault analysis. Make sure that you install and use Server installation and monitoring tool internal storage
monitor / MSM.
When you update MSM, always remove the old version of MSM before installing a new version.
Installation
The MSM installation procedure is described below.
MSM installation is different in location and procedure depending on a management configuration.
•
For standalone server management
• Server: Installed by the standalone format
(Exclude MSM Remote and MSM SNMP using the installation option.)
•
Centralized management of managed servers (single or multiple) from a management PC
•
Management PC: Installed in the client format
(Exclude MSM SNMP using the installation option.)
• Managed server: Installed in the complete format
(Exclude MSM SNMP using the installation option.)
•
Centralized management of multiple managed servers by the management server
•
Management server: installed in the complete format
(Exclude MSM SNMP using the installation option.)
•
Managed server: installed in the complete format
(Exclude MSM SNMP using the installation option.)
2-2 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
The MSM Client function must be installed for maintenance work of managed servers. Install all MSM modules (MSM Server and MSM
Client. MSM SNMP is excluded.) on the managed server.
After installation, refer to " Initialization " on page 2-71
for configuration.
If you install the MSM to Red Hat Enterprise Linux 6 (64-bit x86_64), there are libraries required to install it. Please install the required
(Recommended installation format)
When you do not conduct centralized management from a management PC or a management server, which also manages itself, install MSM in the standalone format.
For a Linux environment, we recommend that you use GUI for installation.
For Windows, Microsoft visual c++ 2005 is installed before the installation of MSM.
In the case of Windows, if you set up MSM while the Windows
Server Post-setup Security Updates window is kept open after completion of the OS installation, the MSM alert window opens as
Windows Security Alert because the firewall is enabled.
Handle this situation with reference to " Setting network security " on
page
.
For Linux, CUI installation of MSM is not supported except for the standalone format. Install MSM with reference to "
Linux: Installation in the standalone format (Recommended format) " on page 2-32
.
If MSM is installed in the CUI environment of Linux, the only MSM functions that can be used are event output to Linux
(var/log/messages) and some functions that use MegaCli (functions described in this manual such as a consistency check).
Pop-up window notification is disabled in the default setting of Linux event notifications. To enable pop-up window notification in the GUI
environment, see " Setting " on page 2-171
.
In a non-GUI environment, pop-up window notification is not supported and should remain disabled.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-3
Required libraries in Red Hat Enterprise Linux 6 (64-bit x86_64) environment
If you install the MSM to Red Hat Enterprise Linux 6 (64-bit x86_64), there are libraries required to install it.
Please install libraries from the media of each Red Hat Enterprise Linux 6.
•
Required libraries for Red Hat Enterprise Linux Server 6.4 (64-bit x86_64)
• libstdc++-4.4.7-3.el6.i686.rpm
• compat-libstdc++-33-3.2.3-69.el6.i686.rpm
• libXau-1.0.6-4.el6.i686.rpm
• libxcb-1.8.1-1.el6.i686.rpm
• libX11-1.5.0-4.el6.i686.rpm
• libXext-1.3.1-2.el6.i686.rpm
• libXi-1.6.1-3.el6.i686.rpm
• libXtst-1.2.1-2.el6.i686.rpm
•
Required libraries for Red Hat Enterprise Linux Server 6.2 (64-bit x86_64)
• libstdc++-4.4.6-3.el6.i686.rpm
• compat-libstdc++-33-3.2.3-69.el6.i686.rpm
• libXau-1.0.5-1.el6.i686.rpm
• libxcb-1.5-1.el6.i686.rpm
• libX11-1.3-2.el6.i686.rpm
• libXext-1.1-3.el6.i686.rpm
• libXi-1.3-3.el6.i686.rpm
• libXtst-1.0.99.2-3.el6.i686.rpm
• Required libraries for Red Hat Enterprise Linux Server 6.1 (64-bit x86_64)
• libstdc++-4.4.5-6.el6.i686.rpm
• compat-libstdc++-33-3.2.3-69.el6.i686.rpm
• libXau-1.0.5-1.el6.i686.rpm
• libxcb-1.5-1.el6.i686.rpm
• libX11-1.3-2.el6.i686.rpm
• libXext-1.1-3.el6.i686.rpm
• libXi-1.3-3.el6.i686.rpm
• libXtst-1.0.99.2-3.el6.i686.rpm
Please perform the following command to install the library.
(The following is one example)
# rpm -ivh <Library to install>
2-4 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Windows: Installation in the standalone format (Recommended format)
In the event of installation in the standalone format, MSM alone cannot realize centralized management from a management PC nor the centralized management of multiple servers by a management server, which also manages itself.
Make sure that you select Custom in the Setup Type window of step
11 of the installation procedure. Do not select standalone for installation.
1. Start Windows and logon as Administrator.
2. Insert the "Server installation and monitoring tool DVD" or "Driver Kit CD" in the CD/DVD drive.
3. [ When "Server installation and monitoring tool DVD" is used ]
Execute the following MegaRAID Storage Manager installer file while referring to "Support_EN.html" as attachment in the "Server installation and monitoring tool DVD". The directory path of MSM is different according to the system unit and OS.
(1) Default installation location
"d:\(the target directory path)\TOOL\MSM_Installer.exe" *1 *2
(2) Non-default installation location, and fault monitoring through SNMP interface
"d:\(the target directory path)\Setup.exe" *2
[ When "Driver Kit CD" is used ]
Select Start > Run, enter information as shown below, and click OK.
(1) Default installation location
"d:\Win2008\UTILITY\MSM\TOOL\MSM_Installer.exe" *1 *2
(2) Non-default installation location, and fault monitoring through SNMP interface
"d:\Win2008\UTILITY\MSM\Setup.exe" *2
*1: Running MSM_Installer.exe, the DOS prompt window opens. After a few minutes, when a pop-up window opens asking you to restart the system unit, perform the procedure from step 20.
*2: d stands for a CD/DVD drive.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-5
4. Click Install when the following window opens.
The following progress window is displayed.
5. Click Yes when the following window opens.
2-6 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
6. Click Next when the following window opens.
7. The license agreement window opens. Select I accept the terms in the
license agreement and click Next.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-7
8. The Customer Information window opens. Read the description on the
MSM usage privileges and click Next.
Select Only for current user if you use MSM only as Administrator.
2-8 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
9. The window for specifying MSM installation destination opens. Change the installation location as necessary and click Next.
The default installation destinations are as follows:
• 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
• 32bit OS:
C:\Program Files\MegaRAID Storage Manager
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-9
10. The Setup Type window opens. Confirm the installation descriptions and click Next.
Make sure that you check Custom Installation, and click Next.
11. The detailed version of the Setup Type window opens. Check Custom and click Next.
2-10 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
12. The Custom Setup window opens.
If you use SNMP, do not select anything and go to the next step.
If you do not use SNMP, select Server > Optional Utilities > SNMP, and select This feature will not be available.
(*We recommend that you select This feature will not be available.)
13. Select Server > Plugins > NetworkCapability, and select This feature
will not be available.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-11
14. Select Server > Plugins > CIM, select This feature will not be
available, and click Next.
15. The Ready to Install the program window opens. Confirm the content and click Install.
Installation starts.
2-12 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
16. When the installation is finished, the InstallShield Wizard Completed window is displayed. Click Finish.
17. The installer is terminated, and an MSM icon is generated on the desktop.
18. [ When "Server installation and monitoring tool DVD" is used ]
Execute the following MegaRAID Storage Manager installer file while referring to "Support_EN.html" as attachment in the "Server installation and monitoring tool DVD". The directory path of MSM is different according to the system unit and OS.
"d:\(the target directory path)\TOOL\MSM_Installer.exe"
[ When "Driver Kit CD" is used ]
Select Start > Run, enter information as shown below, and click OK.
"d:\Win2008\UTILITY\MSM\TOOL\MSM_Installer.exe"
* d stands for a CD/DVD drive.
When this file is executed, the DOS prompt window opens.
Make sure that you execute MSM_Installer.exe.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-13
19. After completion, a pop-up window opens to prompt you to restart the system unit.
20. Remove the CD/DVD from the drive, and click YES on the pop-up window.
The system unit restarts.
Make sure that you restart the system unit after MSM installation.
21. When Windows has started, logon as Administrator.
The Window firewall blocks the MSM module (javaw) if enabled. Handle this matter with reference to "
Setting network security " on page 2-161
.
MSM installation in the standalone format is completed.
After installation, configure the disk array controller in accordance with
your operation with reference to " Initialization " on page 2-71
.
2-14 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Windows: Installation in complete format (Installation on a management server or managed server)
Make sure that you select Custom Installation in the Setup Type window of step 10 of the installation procedure. Do not select
Complete for installation.
If you intend to manage a standalone server without network connection, follow the description "Windows: Installation in the standalone format".
1. Boot Windows and logon as Administrator.
2. Insert the "Server installation and monitoring tool DVD" or "Driver Kit CD" in the CD/DVD drive.
3. [ When "Server installation and monitoring tool DVD" is used ]
Execute the following MegaRAID Storage Manager installer file while referring to "Support_EN.html" as attachment in the "Server installation and monitoring tool DVD". The directory path of MSM is different according to the system unit and OS.
"d:\(the target directory path)\Setup.exe"
[ When "Driver Kit CD" is used ]
Select Start > Run, enter information as shown below, and click OK.
"d:\Win2008\UTILITY\MSM\Setup.exe"
* d stands for a CD/DVD drive.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-15
4. Click Install when the following window opens.
The following progress window is displayed.
2-16 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
5. Click Yes when the following window opens.
6. Click Next when the following window is displayed.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-17
7. The license agreement window opens. Select I accept the terms in
the license agreement and click Next.
8. The Customer Information window opens. Read the description on the
MSM usage privileges and click Next.
Select Only for current user if you use MSM only as Administrator.
2-18 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
9. The window for specifying MSM installation destination opens. Change the installation location as necessary and click Next.
The default installation destinations are as follows:
• 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
• 32bit OS:
C:\Program Files\MegaRAID Storage Manager
10. The Setup Type window opens. Confirm the installation details and click
Next.
Make sure that you check Custom Installation, and click Next.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-19
11. The detailed Setup Type window opens. Check Custom and click Next.
12. The Custom Setup window opens.
If you use SNMP, do not select anything and click Next.
If you do not use SNMP, select Server > Optional Utilities > SNMP, select This feature will not be available, and click Next.
(* We recommend that you select This feature will not be available.)
2-20 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
13. The Ready to Install the Program window opens. Confirm the content and click Install.
Installation starts.
14. When the installation is finished, the InstallShield Wizard Completed window opens. Click Finish.
15. The installer is terminated, and then an MSM icon is generated on the desktop.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-21
16. [ When "Server installation and monitoring tool DVD" is used ]
Execute the following MegaRAID Storage Manager installer file while referring to "Support_EN.html" as attachment in the "Server installation and monitoring tool DVD". The directory path of MSM is different according to the system unit and OS.
"d:\(the target directory path)\TOOL\MSM_Installer.exe"
[ When "Driver Kit CD" is used ]
Select Start > Run, enter information as shown below, and click OK.
"d:\Win2008\UTILITY\MSM\TOOL\MSM_Installer.exe"
* d stands for a CD/DVD drive.
When this is executed, the DOS prompt window opens.
Make sure that you execute MSM_Installer.exe.
2-22 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
17. After completion, a pop-up window opens to prompt you to restart the system unit.
18. Remove the CD/DVD from the drive, and click YES on the pop-up window.
The system unit restarts.
Make sure that you restart the system unit after MSM installation.
19. When Windows has started, logon as Administrator.
The Window firewall blocks the MSM module (javaw) if enabled. Handle
this situation with reference to " Setting network security
.
MSM installation in the complete format is completed.
After installation, configure the disk array controller in accordance with your
operation with reference to " Initialization " on page 2-71
.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-23
Windows: Installation in client format (Installation on a management PC)
Make sure that you select Custom in the Setup Type window of step 11 of the installation procedure. Do not select Client for installation.
MSM installation to a management PC is not required for the standalone operation.
1. Boot Windows and logon as Administrator.
2. Insert the "Server installation and monitoring tool DVD" or "Driver Kit CD" in the CD/DVD drive.
3. [ When "Server installation and monitoring tool DVD" is used ]
Execute the following MegaRAID Storage Manager installer file while referring to "Support_EN.html" as attachment in the "Server installation and monitoring tool DVD". The directory path of MSM is different according to the system unit and OS.
"d:\(the target directory path)\Setup.exe"
[ When "Driver Kit CD" is used ]
Select Start > Run, enter information as shown below, and click OK.
"d:\Win2008\UTILITY\MSM\Setup.exe"
* d stands for a CD/DVD drive.
4. Click Install when the following window opens.
2-24 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
The following progress window is displayed.
5. Click Yes when the following window opens.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-25
6. Click Next when the following window is displayed.
7. The License Agreement window opens. Select I accept the terms in
the license agreement and click Next.
2-26 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
8. The Customer Information window opens. Read the description on the
MSM usage privileges and click Next.
Select Only for current user if you use MSM only as Administrator.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-27
9. The screen for specifying MSM installation destination opens. Change the installation location as necessary and click Next.
The default installation destinations are as follows:
• 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
• 32bit OS:
C:\Program Files\MegaRAID Storage Manager
10. The Setup Type window opens. Confirm the installation details and click
Next.
For a management PC, check Custom Installation.
2-28 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
11. The detailed Setup Type window opens. Check Custom and click Next.
If you check Client here, real-time remote management will be disabled after installation.
12. The Custom Setup window opens. Select Server > Optional Utilities >
SNMP, select This feature will not be available, and click Next.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-29
13. The Ready to Install the Program window opens. Confirm the content and click Install.
Installation starts.
14. When the installation is finished, the InstallShield Wizard Completed window opens. Click Finish.
2-30
15. The installer is terminated, and an MSM icon is created on the desktop.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
16. Remove the CD/DVD from the drive, and restart the system unit.
Make sure that you restart the system unit after MSM installation.
MSM installation in the client format is completed.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-31
Linux: Installation in the standalone format (Recommended format)
To install MSM on Linux and use the functions described in this manual, do it in an environment where all selectable items in the
Linux installer have been selected for one of the Linux installation packages listed below.
The items marked by (*
1
) are not required if MSM is used only with
CUI.
In this case, the only MSM functions that can be used are event output to Linux (var/log/messages) and some functions that use
MegaCli (functions described in this manual such as consistency check). Therefore, we recommend that you install all of the following items:
[Red Hat Enterprise Linux 6]
• Desktop *
1
• General Purpose Desktop *
1
• X Window System *
1
• Base
• Compatibility library
[Red Hat Enterprise Linux 5]
• GNOME desktop environment *
1
• X Window System *
1
• Base
• Support of legacy software
If these items are not installed, MSM installation and functions described in this manual cannot be performed normally.
Disable SE Linux of the OS or set it to "Permissive".
When installed with the standalone format, MSM alone cannot realize centralized management from a management PC nor the centralized management of multiple servers by a management server, which also manages itself.
When you update MSM, remove the current MSM in the correct procedure, and then install a new version of MSM. To remove MSM, see the MSM manual that you have used for installation.
1. Start Linux, and logon as root.
If you install the MSM to Red Hat Enterprise Linux 6 (64-bit
x86_64), some libraries are required. Please refer to " Required libraries in
Red Hat Enterprise Linux 6 (64-bit x86_64) environment " on page 2-4
and install them.
2. Start X Windows.
# startx
* Not required for a CUI environment
2-32 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3. Insert the "Driver Kit" CD-ROM in the CD/DVD drive.
4. Start the terminal.
5. Mount the CD-ROM. This step is not required if the CD-ROM has been automatically mounted.
# mount /dev/cdrom /media/
If the above command does not mount the CD-ROM, try the command again appending any number (1, 2, 3, ...) to "cdrom", and then see if the CD has been mounted.
[Example: When the number is "2"]
# mount /dev/cdrom2 /media/
6. Copy "MSM_linux_installer-x.xx-xx.tar.gz" to any directory from "Driver
Kit" CD-ROM.
"MSM_linux_installer-x.xx-xx.tar.gz" is in \hitachi_utilities\msm directory.
* "x" in MSM_linux_installer-x.xx-xx.tar.gz varies depending on the MSM version.
Find out the actual file name.
7. Execute the following command.
# cd /copy-directory (the copy destination in step 6)
# tar -xvzf copy-file (the copy destination in step 6)
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-33
8. The disk directory and files are created.
9. Execute the MSM installation command.
Move to the directory in which the file has been uncompressed, and execute one of the following installation commands:
[Installation command: 1]
# cd /copy-directory (the copy destination in step 6) / disk
# ./msminstall.sh
[Installation command: 2]
# cd /copy-directory (the copy destination in step 6) / disk
# ./install.csh
We recommend [Installation command: 1]. After execution of the command, go to step 12.
To display the window for installation format specification, execute
[Installation command: 2], and then go to step 10.
2-34 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
The install.csh command has the following command options:
(When you have selected a command option, go to step 12.)
* Command options of install.csh:
# ./install.csh -(first argument) -ru (second argument)
•
First argument: a: Installation in the complete format (all MSM modules) s: Installation in the standalone format (all modules excluding MSM
Remote) c: Installation in the client format (only the MSM Client module)
•
Second argument: popup: When an event occurs, it is not displayed in a pop-up window (not supported). snmp: The SNMP module is not installed.
Select an appropriate installation in accordance with your operation.
The msminstall.sh command is equivalent to the standalone format installation by the install.csh command with the snmp specification.
#./install.csh -s -ru snmp
Do not specify popup of the second argument because it may prevent event outputs to Linux, which is not supported.
The message below during installation command execution indicates that the MSM installation has not been done successfully. The kernel may be incompatible with MSM. In this case, check if the environment of the target system unit is supported.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-35
MSM is installed in the following directory:
# /usr/local/MegaRAID Storage Manager
10. The license agreement description opens awaiting your response.
Read the license agreement, and enter Y or y and press Enter.
11. The window for specifying the installation format opens.
For the standalone format, enter 3 and press Enter.
Installation starts.
MSM is installed in the following directory:
# /usr/local/MegaRAID Storage Manager
2-36 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
12. Installation starts. After ending installation, unmount the CD-ROM, then remove the CD-ROM from the drive, and restart the system unit.
Make sure that you restart the system unit after MSM installation.
MSM installation in the standalone format is completed.
After installation, configure the disk array controller in accordance with your operation form with reference to "
" on page
.
This installation includes a command line program. The command line program is installed in the following directory:
/opt/MegaRAID/MegaCli
The name of the program to be executed varies depending on the OS.
• 64bit OS: MegaCli64
• 32bit OS: MegaCli
Various messages may be displayed during installation. See
for details.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-37
Linux: Installation in the complete format
(Installation on a management server or managed server)
To install MSM on Linux and use the functions described in this manual, do it in an environment where all selectable items in the
Linux installer have been selected for on of the Linux installation packages below.
[Red Hat Enterprise Linux 6]
• Desktop
• General Purpose Desktop
• X Window System
• Base
• Compatibility library
[Red Hat Enterprise Linux 5]
• GNOME desktop environment
• X Window System
• Base
• Support of legacy software
If these items are not installed, MSM installation and functions described in this manual cannot be performed normally.
Disable SE Linux of the OS or set it to "Permissive".
If you intend to manage the server without network connection, perform the procedure of "
Linux: Installation in the standalone format (Recommended format) " on page 2-32
.
Set the host name in the format conforming to the fully qualified domain name (FQDN). Remote monitoring does not work if a host name does not conform to the FQDN format.
When you update MSM, remove the current MSM in the correct procedure, and then install a new version of MSM. To remove MSM, see the MSM manual that you have used for installation.
1. Start Linux, and logon as root.
If you install the MSM to Red Hat Enterprise Linux 6 (64-bit
x86_64), some libraries are required. Please refer to " Required libraries in
Red Hat Enterprise Linux 6 (64-bit x86_64) environment " on page 2-4
and install them.
2. Start X Windows.
# startx
2-38 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3. Insert the "Driver Kit" CD-ROM in the CD/DVD drive.
4. Start the terminal.
5. Mount the CD-ROM. This step is not required if the CD-ROM has been automatically mounted.
# mount /dev/cdrom /media/
If the above command does not mount the CD-ROM, try the command again appending any number (1, 2, 3, ...) to "cdrom", and then see if the CD has been mounted.
[Example: When the number is "2"]
# mount /dev/cdrom2 /media/
6. Copy "MSM_linux_installer-x.xx-xx.tar.gz" to any directory from "Driver
Kit" CD-ROM.
"MSM_linux_installer-x.xx-xx.tar.gz" is in \hitachi_utilities\msm directory.
* "x" in MSM_linux_installer-x.xx-xx.tar.gz varies depending on the MSM version.
Find out the actual file name.
7. Execute the following command.
# cd /copy-directory (the copy destination in step 6)
# tar -xvzf copy-file (the copy destination in step 6)
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-39
8. The disk directory and files are created.
9. Execute the MSM installation command.
Move to the directory in which the file has been uncompressed, and execute one of the following installation commands:
[Installation command: 1]
# cd /copy-directory (the copy destination in step 6) / disk
# ./remsminstall.sh
[Installation command: 2]
# cd /copy-directory (the copy destination in step 6) / disk
# ./install.csh
We recommend [Installation command: 1]. After execution of the command, go to step 12.
To display the window for installation format specification, execute
[Installation command: 2], and then go to step 10.
2-40 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
The install.csh command has the following command options:
(When you have selected a command option, go to step 12.)
* Command options of install.csh:
# ./install.csh -(first argument) -ru (second argument)
•
First argument: a: Installation in the complete format (all MSM modules) s: Installation in the standalone format (all modules excluding MSM
Remote) c: Installation in the client format (only the MSM Client module)
•
Second argument: popup: When an event occurs, it is not displayed in a pop-up window (not supported). snmp: The SNMP module is not installed.
Select an appropriate installation in accordance with your operation.
The remsminstall.sh command is equivalent to the complete format installation by the install.csh command with the snmp specification.
#./install.csh -a -ru snmp
Do not specify popup of the second argument because it may prevent event outputs to Linux, which is not supported.
The message below during installation command execution indicates that the MSM installation has not been done successfully. The kernel may be incompatible with MSM. In this case, check if the environment of the target system unit is supported.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-41
MSM is installed in the following directory:
# /usr/local/MegaRAID Storage Manager
10. The license agreement description opens awaiting your response.
Read the license agreement, and enter Y or y and press Enter.
11. The window for specifying the installation format opens.
For the complete format, type 1 and press Enter.
Installation starts.
MSM is installed in the following directory:
# /usr/local/MegaRAID Storage Manager
2-42 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
12. Installation starts. After ending installation, unmount the CD-ROM, remove the CD-ROM from the drive, and restart the system unit.
Make sure that you restart the system unit after MSM installation.
MSM installation in the complete format is completed.
After installation, configure the disk array controller in accordance with your operation form with reference to "
" on page
.
This installation includes a command line program. The command line program is installed in the following directory:
/opt/MegaRAID/MegaCli
The name of the program to be executed varies depending on the OS.
• 64bit OS: MegaCli64
• 32bit OS: MegaCli
Various messages may be displayed during installation. See
for details.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-43
Linux: Installation in the client format (Installation on a management PC)
To install MSM on Linux and use the functions described in this manual, do it in an environment where all selectable items in the
Linux installer have been selected for on of the Linux installation packages below.
[Red Hat Enterprise Linux 6]
• Desktop
• General Purpose Desktop
• X Window System
• Base
• Compatibility library
[Red Hat Enterprise Linux 5]
• GNOME desktop environment
• X Window System
• Base
• Support of legacy software
If these items are not installed, MSM installation and functions described in this manual cannot be performed normally.
Disable SE Linux of the OS or set it to "Permissive".
Set the host name in the format conforming to the fully qualified domain name (FQDN). Remote monitoring does not work if a host name does not conform to the FQDN format.
When you update MSM, remove the current MSM in the correct procedure, and then install a new version of MSM. To remove MSM, see the MSM manual that you have used for installation.
1. Start Linux, and logon as root.
If you install the MSM to Red Hat Enterprise Linux 6 (64-bit
x86_64), some libraries are required. Please refer to " Required libraries in
Red Hat Enterprise Linux 6 (64-bit x86_64) environment " on page 2-4
and install them.
2. Start X Windows.
# startx
3. Insert the "Driver Kit" CD-ROM in the CD/DVD drive.
4. Start the terminal.
5. Mount the CD-ROM. This step is not required if the CD-ROM has been automatically mounted.
# mount /dev/cdrom /media/
2-44 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
If the above command does not mount the CD-ROM, try the command again appending any number (1, 2, 3, ...) to "cdrom", and then see if the CD has been mounted.
[Example: When the number is "2"]
# mount /dev/cdrom2 /media/
6. Copy "MSM_linux_installer-x.xx-xx.tar.gz" to any directory from "Driver
Kit" CD-ROM.
"MSM_linux_installer-x.xx-xx.tar.gz" is in \hitachi_utilities\msm directory.
* "x" in MSM_linux_installer-x.xx-xx.tar.gz varies depending on the MSM version. Find out the actual file name.
7. Execute the following command.
# cd /copy-directory (the copy destination in step 6)
# tar -xvzf copy-file (the copy destination in step 6)
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-45
8. The disk directory and files are created.
9. Execute the MSM installation command.
Move to the directory in which the file has been uncompressed, and execute one of the following installation commands:
# cd /copy-directory (the copy destination in step 6) / disk
# ./install.csh
2-46 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
The install.csh command has the following command options:
(When you have selected a command option, go to step 12.)
* Command options of install.csh:
# ./install.csh -(first argument) -ru (second argument)
•
First argument: a: Installation in the complete format (all MSM modules) s: Installation in the standalone format (all modules excluding MSM
Remote) c: Installation in the client format (only the MSM Client module)
•
Second argument: popup: When an event occurs, it is not displayed in a pop-up window (not supported). snmp: The SNMP module is not installed.
Select an appropriate installation in accordance with your operation.
Do not specify popup of the second argument because it may prevent event outputs to Linux, which is not supported.
The message below during installation command execution indicates that the MSM installation has not been done successfully. The kernel may be incompatible with MSM. In this case, check if the environment of the target system unit is supported.
MSM is installed in the following directory:
# /usr/local/MegaRAID Storage Manager
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-47
10. The license agreement description opens awaiting your response.
Read the license agreement, and type Y or y and press Enter.
11. The window for specifying the installation format opens.
For the client format, type 2 and press Enter.
Installation starts.
MSM is installed in the following directory:
# /usr/local/MegaRAID Storage Manager
2-48 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
12. Installation starts. After ending installation, unmount the CD-ROM, then remove the CD-ROM from the drive, and restart the system unit.
Make sure that you restart the system unit after MSM installation.
MSM installation with the client format is completed.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-49
Uninstallation
This subsection explains the MSM uninstallation procedure.
Use this procedure also for uninstallation from a management PC.
Uninstalling the Windows edition
MSM has its own uninstallation module.
Use this uninstallation module instead of a general application removal utility.
Before you start uninstallation of MSM, close the MSM Client
(including remote connections). Close other applications as well.
The pop-up message shown below may be displayed.
Click [Abort] when this pop-up is displayed.
Then close all applications and retry.
1. Start Windows and logon as Administrator.
2. For Windows Server 2012, select All apps after pressing Windows Logo key and Space key in this order. And select MegaRAID Storage
Manager > Uninstall.
For OS's other than Windows Server 2012, click Start > All Programs* >
MegaRAID Storage Manager > Uninstall.
* In the classic Start menu, click Programs.
2-50
Windows Server 2012 OS's other than Windows Server 2012
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3. The uninstallation start window opens. Click Yes.
Before you start uninstallation of MSM, close the MSM Client
(including remote connections). Close other applications as well.
The pop-up message shown below may be displayed.
Click [Abort] when this pop-up is displayed.
Then close all applications and retry.
4. Uninstallation starts.
The dialog box closes when the uninstallation is completed.
After the dialog box closes, the following pop-up massage may be displayed asking you to restart the system. Select No in such cases.
(Do not restart the system at this point.)
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-51
5. After step 4, check if the MSM installation directory still remains.
The default installation destinations are as follows:
• 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
• 32bit OS:
C:\Program Files\MegaRAID Storage Manager
If any of the above directories remains, remove it manually.
If you cannot remove it, restart the system unit and retry.
Uninstallation of the Windows edition of MSM is completed. Restart the system unit.
Make sure that you restart the system unit after MSM removal.
2-52 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Uninstalling the Linux edition
If the MSM SNMP module has been installed on Red Hat Enterprise
Linux 6, perform the following procedure at the time of MSM uninstallation. If you do not perform it, the MSM SNMP module becomes unable to be removed.
- Enable the run level of snmpd of Linux.
# chkconfig snmpd on
- Reboot the system unit.
- Uninstall MSM according to the procedure in this section.
- Disable the run level of snmpd of Linux.
# chkconfig snmpd off
- Reboot the system unit.
Before you start uninstallation of MSM, close the MSM Client
(including remote connections). Close other applications as well.
If MSM is running, MSM uninstallation cannot be performed.
1. Start Linux, and log on as root.
2. Start X Windows.
# startx
3. Click Application > System Tools > Uninstall MegaRAID Storage
Manager in the GUI menu.
Before you start uninstallation of MSM, close the MSM Client
(including remote connections). Close other applications as well.
MSM sometimes cannot be uninstalled. In such a case, close all applications and retry.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-53
4. Uninstallation starts.
Uninstallation completes in about a minute. Check Application > System
Tools again. If Uninstall MegaRAID Storage Manager has been deleted, uninstallation is completed. If not deleted after you wait several minutes, use the command line as explained in the Tip below.
MSM can be uninstalled from the command line.
Move to the MSM installation directory, and execute the following command:
# ./uninstaller.sh
Before you execute the above command, close the MSM Client
(including remote connections). Close other applications as well. MSM sometimes cannot be uninstalled with the message below.
In such a case, close all applications and retry.
MegaRAID Storage Manager is running. Please shutdown the process and retry.
Error: %preun (MegaRAID_Storage_Manager-xxxxxx.noarch) scriptlet failed. Exit status 1
(*
"x" varies depending on the MSM version.)
5. Uninstall the command line programs.
Enter the following command:
# rpm -ev MegaCli
The command is completed if the MegaRAID folder under #/opt has been deleted.
If the MegaRAID directory remains after execution of the above command, remove it manually.
6. Uninstall the utility library programs.
Enter the following command:
# rpm -ev Lib_Utils-xxx-xxx.noarch .... (Note 1) (Note 2) (Note 3)
# rpm -ev Lib_Utils2-xxx-xxx.noarch ... (Note 1) (Note 2) (Note 3)
2-54 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
The command is completed if the lsi folder under #/opt has been deleted.
If the lsi directory remains after execution of the above command, remove it manually.
Note 1: They are the same as the file names created under the disk directory expanded at the time of Linux installation. However, rpm is not required.
Note 2: These utility programs are not installed for Ver.3.04-08 or earlier.
Note 3: The following command displays utility programs currently installed:
# rpm -qa Lib_Utils*
Uninstallation of the Linux edition MSM is completed. Restart the system unit.
Make sure that you restart the system unit after MSM uninstallation.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-55
Activating MegaRAID Storage Manager
This section explains how to activate, log in, and exit MSM.
To be enough time whenever you start MSM after system unit activation.
Services MrMonitor and MrMonitor monitoring are not installed in MSM
Ver.11.08.XX.XX or later. Therefore, the following events recorded in the OS event log just after OS boot will not be collected.
[Windows OS, Linux OS]
Monitor has started successfully
[Only Windows] service monitor has started successfully
Activating MSM
1. Activate MSM in the following procedure:
• For Windows
For Windows Server 2012, select All apps after pressing Windows
Logo key and Space key in this order. And select MegaRAID Storage
Manager > StartupUI.
For OS's other than Windows Server 2012, click Start > All
Programs* > MegaRAID Storage Manager > StartupUI.
* In the classic Start menu, click Programs.
2-56
Windows Server 2012 OS's other than Windows Server 2012
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
You can start MSM also by double-clicking the MegaRAID Storage
Manager icon on the desktop.
• For Linux
With X Window running, click Application > System Tools >
MegaRAID Storage Manager StartupUI.
2. The server selection window opens.
Select and double-click a server displayed in the Remote servers window, or select the server and click Login.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-57
If the system unit is not connected to LAN, the Remote servers window is blank.
In this case, the window shown below opens.
To log in the local server, enter "127.0.0.1" in IP Address and click
Discover Host. Servers are displayed in the Remote servers window. Select and double-click a server, or select the server and click
Login.
Windows Server 2012 is indicated as "Windows NT(unknown)" in the
Operating System pane of this dialog box.
3. The login window opens.
Enter your user name and password in the User Name and Password fields, and click Login.
2-58 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Only one user can logon a managed server at a time with Login Mode set to Full Access. Simultaneous log on a managed server with Full
Access is not allowed.
When you logon the server with Login Mode of Full Access, you have to use the user name and password of the administrator account
(Windows: Administrator, Linux: root).
4. The main window opens.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-59
Starting MSM (for remote connection)
This section explains the case when MSM has been installed in the complete format
1. Activate MSM in the following procedure:
•
For Windows
For Windows Server 2012, select All apps after pressing Windows
Logo key and Space key in this order. And select MegaRAID Storage
Manager > StartupUI.
For OS's other than Windows Server 2012, click Start > All
Programs* > MegaRAID Storage Manager > StartupUI.
* In the classic Start menu, click Programs.
Windows Server 2012 OS's other than Windows Server 2012
You can start MSM also by double-clicking the MegaRAID Storage
Manager icon on the desktop.
2-60 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
•
For Linux
With X Window running, click Application > System Tool >
MegaRAID Storage Manager StartupUI.
2. The server selection window opens.
In the IP Address entry field, enter the IP address of the server to be started (192.168.1.2, for example), and click Discover Host.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-61
3. The server selection window opens.
The server specified in step 2 is displayed in Remote servers. Select and double-click the server, or select the server and click Login.
Windows Server 2012 is indicated as "Windows NT(unknown)" in the
Operating System pane of this dialog box.
4. The login window opens.
Enter your user name and password in the User Name and Password fields, and click Login.
2-62
Only one user can logon a managed server at a time with Login Mode set to Full Access. Simultaneous log on a managed server with Full
Access is not allowed.
When you logon the server with Login Mode of Full Access, you have to use the user name and password of the administrator account
(Windows: Administrator, Linux: root).
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
5. The main window opens.
6. You can log on a multiple server by repeating step 2 above.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-63
Displaying multiple connected servers
This section explains the case where multiple remote servers are connected
(installed in the complete format).
1. Activate MSM in the following procedure:
•
For Windows
For Windows Server 2012, select All apps after pressing Windows
Logo key and Space key in this order. And select MegaRAID Storage
Manager > StartupUI.
For OS's other than Windows Server 2012, click Start > All
Programs* > MegaRAID Storage Manager > StartupUI.
* In the classic Start menu, click Programs.
Windows Server 2012 OS's other than Windows Server 2012
You can start MSM also by double-clicking the MegaRAID Storage
Manager icon on the desktop.
2-64 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
•
For Linux
With X Window running, click Application > System Tool >
MegaRAID Storage Manager StartupUI.
2. The server selection window opens.
Click Configure Host.
Windows Server 2012 is indicated as "Windows NT(unknown)" in the
Operating System pane of this dialog box.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-65
3. The Configure Host window opens.
Select Display all the systems in the network of local server., and click Save Settings.
4. The Confirmation pop-up message is displayed.
Click Yes.
The connected servers are searched for.
5. The server selection window opens.
All the connected servers are displayed in the Remote servers list.
2-66 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Switching servers to be displayed (for remote connection)
Manage > Server cannot be used. Do not use this method.
To switch server to be displayed, close MSM and perform the
procedure " Starting MSM (for remote connection) " on page 2-60
.
1. In the main window, select Server from the Manage menu.
2. The server selection window opens.
Select and double-click the server to logon (to start), or select the server and click Login.
Windows Server 2012 is indicated as "Windows NT(unknown)" in the
Operating System pane of this dialog box.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-67
3. A switch warning pop-up massage is displayed.
Select Confirm, and click Yes.
4. The login window opens.
Enter your user name and password in the User Name and Password fields, and click Login.
Only one user can logon a managed server at a time with Login Mode set to Full Access. Simultaneous log on a managed server with Full
Access is not allowed.
When you logon the server with Login Mode of Full Access, you have to use the user name and password of the administrator account
(Windows: Administrator, Linux: root).
2-68 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
5. The main window of the selected server is displayed.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-69
Exiting MegaRAID Storage Manager
This section explains how to exit MSM.
1. Click at the upper right corner of the window, or select Exit from the
Manage menu. You can also click Log Off. (Note 1)
2-70
Note 1: When you click Log Off in Dashboard, the following pop-up massage is displayed.
Click Yes.
(Then the server selection window opens again. Click at the upper-right corner.)
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Initialization
Initialize the system unit in accordance with its operation form.
The table below lists the setting items.
Setting item Description Reference pages
Exception setting of network security
Event notification setting
Sets a network security exception for MSM.
Sets the conditions for event notifications for disk array events.
Configures Patrol Read, which runs in the background.
Patrol Read setting*
Hot spare setting* If a hot spare physical drive has been included in the purchased system unit, the hot spare is configured as a global hot spare at the time of shipment.
Change the setting to a dedicated hot spare as necessary.
* These cannot be used depending on the disk array controller type (including LSI Software RAID).
These cannot be used depending on the number of the maximum mark of the physical drive which can be carried in a system unit.
For setting details, see the page referenced in the table above.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-71
Screen configuration and descriptions of MegaRAID
Storage Manager
The MSM main window configuration is described below.
A
B
C
D
E
2-72
F
A Menu bar
Lists five menus: Manage, Go To, Log, Tools, and Help.
B Menu bar (graphical)
Lists six menus: Server, Refresh, Group show progress, Create
Virtual Drive, Exit, and Help.
C Log Off
Exits MSM.
D Tabs
Switches between the Dashboard, Physical, and Logical views.
E Configuration information
Displays the RAID (Dashboard), Physical, and Logical configuration information.
F Message window
Displays an event log.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
When you logon with Login Mode of View Only, the menu bar shows
Manage, Log, and Help only.
Menus
The MSM menu items are described below.
Manage: Manager menu
Menu item Description
Refresh F5
Server
Refreshes the controller and connected devices.
Switches the displayed server. (Not supported)
Check Consistency Performs a consistency check.
Show Progress Displays the status of running tasks (initialization of a virtual drive, rebuild, consistency check, and capacity expansion).
Go To: Execution menu
The Go To menu shows different menu items depending on the selected device (controller, physical drive, or virtual drive) in the Physical view or the
Logical view.
You can also display some of the operation menu items by right-clicking a target device.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-73
•
Main view
Menu item
Controller
Drive Group
Physical Drive
Virtual Drive
BBU
Description
Menu for RAID controller
Menu for expansion of the virtual drive capacity
Menu for physical drives
Menu for virtual drives
Menu for battery functions
Replacing or deleting the configuration data during disk array operation will erase all data of virtual drives that have been configured. Be careful during operation.
•
When Controller is selected in the Physical view or the Logical view
2-74
Menu item
Create Virtual Drive
Enable Alarm/Disable Alarm*
Start Patrol Read
Set Patrol Read Properties
Enable SSD Guard*
Scan Foreign Configuration*
Load Configuration
Description
Structures a new virtual drive
Configures the buzzer alarm (switching between
Enable and Disable).
Starts Patrol Read.
Sets the processing method of Patrol Read.
Configures SSD Guard
TM
. (Default: Disable)
Reads configuration information from a physical drive and sets it again.
Replaces the current configuration information with file content.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Menu item Description
Save Configuration
Clear Configuration
Saves configuration information.
Deletes configuration information.
Set Consistency Check Properties* Sets the consistency check processing method.
Set Adjustable Task Rates Sets the rates of various tasks.
Manage Power Save Settings*
Update Controller Firmware*
Manage MegaRAID Advanced
Software Options*
Manage Link Speed*
Sets the power-saving mode of physical drives.
Updates the firmware of the disk array controller.
Displays the advanced software options for MegaRAID.
Sets the transmission speed of a virtual drive.
Save TTY Log Saves the TTY log of the disk array controller.
* These menus may not be displayed depending on the disk array controller type (including LSI
Software RAID).
Do not use Load Configuration, Clear Configuration, or Scan
Foreign Configuration. All data on the drive will be erased by replacing or deleting configuration data.
Manage Power Save Settings, Manage MegaRAID Advanced
Software Options, Manage Link Speed, and Save TTY Log are not supported.
•
When Drive Group is selected in the Logical view
Menu item Description
Modify Drive Group* Menu for expansion of the virtual drive capacity
Manage Power Save Settings* Sets power-saving mode of virtual drives
* These menus may not be displayed depending on the disk array controller type (including
LSI Software RAID).
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-75
•
When Physical Drive is selected in the Physical or Logical view (When a physical drive included in a virtual drive is selected)
Menu item
Make Drive Offline /
Make Drive Online
Start Locating Drive
Stop Locating Drive
Description
Sets a physical drive to on-line or off-line.
(Switching between on-line and off-line)
Makes the LED of a physical drive blink.
Stops blinking the LED of a physical drive.
Do not use Make Drive Offline. Otherwise, a normal physical drive will be registered as an error, and isolated from the disk array.
Do not use Make Drive Online. Otherwise, the generation of a parity and mirror data will be started automatically, thus losing all data on the disk array.
The menu items Start Locating Drive and Stop Locating Drive are not supported for LSI Software RAID.
•
When Physical Drive is selected in the Physical or Logical view (When a physical drive configured as a hot spare is selected)
Menu item
Remove Hot Spare
Start Locating Drive
Stop Locating Drive
Description
Release a hot spare.
Makes the LED of a physical drive blink.
Stops blinking the LED of a physical drive.
The menu items Start Locating Drive and Stop Locating Drive are not supported for LSI Software RAID.
2-76 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
•
When Physical Drive is selected in the Physical view
(when an unused physical drive is selected)
Menu item Description
Assign Global Hot Spare
Assign Dedicated Hot Spare
Start Locating Drive
Stop Locating Drive
Sets a physical drive as a global hot spare drive.
Sets a physical drive as a dedicated hot spare drive.
Makes the LED of a physical drive blink.
Stops blinking the LED of a physical drive.
Prepare for Removal
Undo Prepare for Removal
Sets a physical drive off-line, and stops the motor.
Starts the motor of a physical drive that has been set off-line by Prepare for Removal so that the drive can be used.
Executes the Drive Erase function for a physical drive. Drive Erase*
* These menus may not be displayed depending on the disk array controller type (including LSI
Software RAID).
Do not use Prepare for Removal, Undo Prepare for Removal, or
Drive Erase. Only one of Prepare for Removal or Undo Prepare
for Removal is displayed depending on the current setting.
For hot spare setting, see " Configuring a hot spare " on page 2-125
.
The menu items Start Locating Drive and Stop Locating Drive are not supported for LSI Software RAID.
The menu items Prepare for Removal and Undo Prepare for
Removal are not displayed.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-77
•
When Virtual Drive is selected in the Logical view
Menu item Description
Rename Virtual Drive
Delete Virtual Drive
Set Virtual Drive Properties
Start Locating Virtual Drive
Renames a virtual drive.
Deletes a virtual drive.
Changes the setting of a virtual drive.
Makes the LED of a virtual drive blink.
Stop Locating Virtual Drive
Start Consistency Check
Start Initialization
Stops blinking the LED of a virtual drive.
Performs a consistency check.
Performs initialization.
Expand
Virtual Drive Erase*
Expands the capacity of a virtual drive.
Executes the Drive Erase function for a virtual drive.
* These menus may not be displayed depending on the disk array controller type (including LSI
Software RAID).
Virtual Drive Erase is not supported.
The menu item Expand is displayed only when there is a virtual drive that has not exhausted the capacity of the drive group. This item is not supported.
The menu items Start Locating Virtual Drive and Stop Locating
Virtual Drive are not supported for LSI Software RAID.
2-78 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
•
When BBU is selected in the Physical view
Menu item
Refresh Properties
Start Learn Cycle
Set Learn Cycle Properties
Description
Updates the property of the cache backup module.
Performs diagnosis (Learn Cycle).
Changes the setting of diagnosis (Learn Cycle).
This item is displayed only for disk array controllers (with cache backup)
Set Learn Cycle Properties is not supported. Avoid its use. Use the auto diagnosis with the default setting (Enable).
To check if the device is a disk array controller (with cache backup),
check BBU Present of " Controller " on page 2-88
. If the value is Yes, the device is a disk array controller (with cache backup).
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-79
Log: Log menu
Menu item
Save
Save as Text
Clear
Load
Rollback to Current Log
Description
Saves an event log.
Saves an event log in the text format.
Deletes an event log.
Opens a saved event log.
Closes Load, and displays the latest event.
(This item is added to the menu when Load is clicked.)
Do not use Clear. Otherwise, fault analysis may be affected.
Tools: Tool menu
Menu item
Monitor Configure Alerts
Help: Help menu
Description
Displays the event notification setting window.
Menu item Description
About MegaRAID Storage Manager Displays MSM version information.
Server Info Displays server details.
2-80 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Window icons
Menu item Description
Represents a server.
Represents a disk array controller.
Represents a port of a disk array controller.
Represents an enclosure device.
Represents a virtual drive group.
Represents a virtual drive.
Represents a RAID group.
Represents a physical drive.
Represents a global hot spare drive.
Represents a dedicated hot spare drive.
Represent a physical drive being rebuilt.
Represents degradation of a virtual drive.
Represents a device failure.
Represents a drive that was once used.
Represents a cache backup module.
The menu item Enclosure is not displayed for LSI Software RAID.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-81
Functions of MegaRAID Storage Manager
This section explains MSM functions.
The following table lists the major MSM functions:
Function Description
Display of properties Configures the properties (detailed information) of devices such as physical drives and virtual drives.
Structures new virtual drive(s). Creating new virtual drive(s)*
1
Changing the setting of virtual drive(s)*
1
Changes the setting of virtual drive(s).
Initialize of virtual drive(s)*
1
Initializes virtual drive(s).
Consistency check of virtual drive(s)
Configuration a hot spare*
1
Expanding virtual drive capacity*
1
Deleting virtual drive(s)*
1
Changing write cache* 1
Checks the consistency of virtual drive(s) of redundant configuration.
Creates and deletes a global hot spare or a dedicated hot spare.
Expands the capacity by adding a new physical drive to the existing virtual drive.
Blinking LEDs* 1
Changes the cache setting of the disk array controller.
There is restriction in write cache change. Make sure that you read the precaution in the page of the detailed description.
Makes LED of each physical drive blink.
Diagnoses the cache back module (BBU). Diagnosing cache back module (BBU)* 1 * 2
Enabling and disabling
SMART copyback*
1
Rescan
Event reference
Displaying task progress and terminating tasks
Updating firmware
Changes the enable/disable setting of SMART copyback.
* This function is configured with MegaCli.
Rescans a device.
References various events that occur in the disk array.
Displays the progress of running tasks such as rebuild and consistency check, and stops tasks.
Updates the firmware of the disk array controller.
Firmware update is not supported.
Do not execute the following:
[Firmware update]
Go To > Controller > Update Controller
Firmware
Setting network security exceptions
Sets a network security exception for MSM.
Setting an event notification
Sets the conditions for event notifications for disk array events.
Reference pages
-
2-82 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Function
Setting patrol Read*
1
Task rate setting
Setting of power-saving mode of physical drives
Setting of the consistency check schedule
Setting of the consistency check processing method
SSD GuardTM
Buzzer setting of the disk array controller
Description
Configures Patrol Read, which runs in the background.
Sets the rates of various tasks.
Task rate setting is not supported.
Do not execute the following:
[Task rate setting]
Go To > Controller > Set Adjustable Task
Rates
*Always set the task rate to the default value (30%)
Sets the power-saving mode of physical drives.
The power-saving mode setting for physical drives is not supported.
Do not execute the following:
[Setting of power-saving mode of physical drives]
Go To > Controller > Manage Power Save
Settings
Sets a consistency check schedule.
Make sure that you apply this setting for LSI Software
RAID.
For a RAID device other than LSI Software RAID, this setting is not required because Patrol Read runs periodically.
*This function is configured by MegaCli.
Sets a consistency check processing method.
Setting of the consistency check method is not supported.
Do not execute the following:
[Setting of the consistency check processing method]
Go To > Controller > Set Consistency Check
Properties
Configures SSD Guard
TM
. [Default: Disable]
SSD GuardTM is not supported.
Do not execute the following:
[SSD Guard
TM
setting]
Go To > Controller > Enable SSD Guard
, or
Go To > Controller > Disable SSD Guard
Configures the buzzer of the disk array controller.
Buzzer setting of disk array controllers is not supported.
Do not execute the following:
[Buzzer setting of the disk array controller]
Go To > Controller > Enable Alarm
, or
Go To > Controller > Disable Alarm
Reference pages
-
-
-
-
-
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-83
Details of each function are explained in the pages that follow.
Firmware update, task rate setting, setting of power-saving mode of physical drives, setting of the consistency check processing method,
SSD Guard, and buzzer setting of the disk array controller are not supported.
Function Description Reference pages
Restrictions
Precautions
Explains restrictions and precautions on use of MSM.
and
*1: These cannot be used depending on the disk array controller type (including LSI Software
RAID).
These cannot be used depending on the number of the maximum mark of the physical drive which can be carried in a system unit.
*2: This function can be used only for disk array controllers (with cache backup). To check if the
device is a disk array controller (with cache backup), check BBU Present of " Controller
" on
. If the value is Yes, the device is a disk array controller (with cache backup).
2-84 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Display of properties
This function enables you to reference the properties of devices that are displayed in the Physical view and Logical view of the main window.
The default view is the Dashboard view. You can switch between Physical and Logical views by operating the respective tab.
The Dashboard view displays the overall properties of the target RAID.
Do not use menu items other than Properties > View server profile and Background Operations > More details.
In addition to the content displayed in the Physical view, the Logical view displays information on the status of the logical drives built.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-85
Click the target device to display its properties.
•
Physical view
•
Logical view
2-86 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Properties of each drive are as follows:
Server
This screen displays the installation OS, the host name, the IP address, and other information of the servers.
Property Description
Host Name
IP Address
Operating System
OS Version
OS Architecture
Host name of the server
IP address of the server
Operating system (OS) installed in the server
Version of the OS installed in the server
Architecture of the OS installed in the server
In Windows Server 2012, Operating System is displayed as
"Windows NT(unknown)".
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-87
Controller
Displays the BIOS version and the firmware version of the disk array controller.
2-88
Property item
Product Name
Serial No
Vendor ID
SubVender ID
Device ID
Device Port Count
Host Interface
Metadata Size
Host Port Count
FRU
Alarm Present
Alarm Enabled* 1
Cache Flush Interval
Coercion Mode
Description
Vender's name of the disk array controller board
Serial number of the disk array controller board
Vendor ID of the disk array controller board
Sub-vendor ID of the disk array controller board
Device ID of the disk array controller board
Number of the SAS ports of the disk array controller board
Host interface of the disk array controller board
Meta data size of the disk array controller board
Number of the host ports of the disk array controller board
Customer-replaceable component number
* FRU is not supported.
Implementation status of the buzzer alarm
Enabled/disabled status of the buzzer alarm
Interval of cache memory flush
Capacity control setting of physical drives
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Property item Description
BBU Present
NVRAM Present
NVRAM Size*
1
BIOS Version* 1
Native Command Queuing
Flash Size*
1
Memory Size*
1
Chip Temperature*
1
Shield State Support
Implementation status of cache backup module
Implementation status of NVRAM
Size of NVRAM
BIOS version of disk array controller board
Enabled/disabled status of command queuing
Flash memory capacity of disk array controller board
Temperature of disk array controller
Diagnosis of the physical drives of disk array controller.
This function is disabled regardless of the setting.
Power-saving mode of unused physical drives Power savings on unconfigured drives
Power saving on hot spares
Power Save Policy for
Configured Drives* 1
Firmware Package Version
Firmware Version*
1
Firmware Build Time* 1
Power-saving mode setting of physical drives configured as hot spares
Power-saving mode setting of physical drives configured for virtual drives
Firmware package version of disk array controller board
Firmware version of disk array controller board
Time stamp of firmware of disk array controller board
Backend SAS Address 0 to 7 Back-end address of SAS device
Correctable Error Count*
1
Number of errors that can be corrected
Memory uncorrectable count*
1
Cluster Enable
Number of errors for which memory correction is disabled
Cluster setting
Cluster Active
SSD Guard
SSD Disk Cache Setting
Drive security capable
Rebuild Rate
Patrol Read Rate* 1
Reconstruction Rate*
1
Cluster operation status
Setting of SSD Guard
TM
Setting of SSD cache
Enabling/disabling of encryption
Priority of rebuild processing
Priority of Patrol Read processing
Priority of disk array configuration processing such as capacity expansion
BGI Rate
Consistency Check Rate
Global Hotspare for
Emergency*
1
Unconfigured Good for
Emergency*
1
Priority of background processing
Priority of consistency check
Availability of rebuild of a physical drive (global hot spare) of a different type (Not supported)
Availability of rebuild of a physical drive (not used) of a different type (Not supported)
Emergency for SMARTer* 1 Availability of SMART copyback of a physical drive (hot spare) of a different type (Not supported)
*1: These menus may not be displayed depending on the disk array controller type (including LSI
Software RAID).
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-89
Physical drive
Displays physical drive properties such as vendor name, device ID, and status.
Property item
Usable Capacity
Raw Capacity
Certified*
1
Product ID
Vendor ID
Device ID
Description
Configured capacity of a physical drive
Raw data size of a physical drive
Device recognition function (not supported)
Product name of a physical drive
Vendor name of a physical drive
Device ID of a physical drive
2-90 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Property item Description
Status
Drive Type* 1
Drive Speed
Negotiated Link Speed
SCSI Device Type
Transmission speed of a physical drive
Negotiated link speed for data transmission of a physical drive
SCSI device type
SAS Address x*
2
Temperature*
1
Temperature of a physical drive
Commissioned Hotspare* 1, * 3 (Not supported)
Power Status*
3
Emergency Hotspare*
1,
*
3
Revision Level
Media Error Count
Power status of a physical drive
Availability of the hot spare functionality for a virtual drive made up of physical drives of different types
Revision level of a physical drive
Number of media errors of a physical drive
Pred Fail Count
Enclosure ID*
2
Enclosure Model* 2
Enclosure Location*
2
Status of a physical drive including the following:
Online: Operating normally
Failed:
Failed and detached from the disk array.
The disk array controller detached the physical drive due to its fault.
Offline:
Failed and detached from the disk array.
The physical drive is detached from the disk array because the user registered a fault.
Unconfigured Bad:
Failed and detached from the disk array. Inconsistency has been identified in the disk array configuration data.
This happens, for example, when you insert a physical drive that has been used.
Rebuild: Being rebuilt
Unconfigured Good: The physical drive is not used.
Hot Spare:
The physical drive is configured as a hot spare (global or dedicated).
being replaced with <copy destination hot spare>:
SMART copyback is running, copying data from this physical drive, on which SMART error occurs, to the copy destination hot spare.
The physical drive becomes Unconfigured Bad when the
SMART copyback finishes.
replacing <copy source physical drive>:
SMART copyback is running, copying data from the drive on which SMART error occurs to this hot spare.
This hot spare becomes Online when the SMART copyback finishes.
Type of a physical drive
Number of received SMART reports
Model of an enclosure
Location of an enclosure
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-91
Property item Description
Connector*
2
Slot Number
Group of physical ports to which a physical drive is connected
Slot number on which a physical drive is mounted
Full Disk Encryption capable Availability setting of encryption for a physical drive
Encryption function of a physical drive (not supported) Secured* 1, * 2
Type*
1,
*
2
Data Protection
Device type of a physical drive
Encryption function of a physical drive (not supported)
*1: This item is not displayed depending on a type of a connected physical drive.
*2: This item is not displayed for LSI Software RAID.
*3: This item is not displayed depending on the status of a physical drive.
Media Error Count and Pred Fail Count are initialized when the power is switched on or off, or when the system unit is restarted.
The number displayed in " coincide with Device ID.
" (Physical Drive x) does not
Device ID and Slot Number do not coincide. Slot Number is recorded in the MSM log.
For a system unit with SATA physical drive installed, the following message may be displayed when you click a physical drive icon on
MSM. The message does not indicate a problem and you can ignore it.
Controller ID X: Unexpected sense: PD = X - Invalid field in
CDB,
CDB = 0x4d 0x00 0x4d 0x00 0x00 0x00 0x00 0x00 0x20 0x00 ,
Sense = 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00
0x00 0x24 0x00 0x00 0x00 0x00 0x00
2-92 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Virtual drive
Displays information on the configuration of a virtual drive.
Property item
RAID Level
Name*
1
Size
Mirror Data Size
Parity Size
Stripe Size
Virtual Disk State
Disk Cache Policy
Read Policy
IO Policy
Description
RAID level of a virtual drive
Volume name of a virtual drive
Capacity of a virtual drive
Mirroring size of a virtual drive (displayed only for RAID1 and
RAID10)
Parity size of a virtual drive (displayed only for RAID5 and RAID6)
Stripe size of a virtual drive
The operating status of a virtual drive including the following:
Optimal: Operating normally
Degraded:
The virtual drive is degraded. One physical drive (two physical drives for RAID6) of the virtual drive has failed. Or it is being rebuilt.
Partially Degraded:
Partially degraded. One physical drive of the RAID6 virtual drive has failed. Or it is being rebuilt.
This item is displayed only for RAID6.
Offline:
The virtual drive is inoperable. Multiple physical drives of the virtual drive have failed, or a physical drive of a non-redundant virtual drive has failed.
Cache policy of a physical drive
Read policy of a virtual drive
Data input and output policy of a virtual drive
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-93
Property item Description
Current Write Policy*
Default Write Policy
2
Current write policy of a virtual drive
(1) When Default Write Policy = "Write Through": Always "Write
Through"
(2) When Default Write Policy = "Always Write Back": Always
"Write Back"
(3) When Default Write Policy = "Write Back with BBU": "Write
Back" or "Write Through"
Default write policy of the configured virtual drive
Current Access Policy
Default Access Policy
Data access policy of the current virtual drive
Data access policy of the configured virtual drive
Default Power save policy* 3 Power-saving mode setting of the configured physical drive
Current Power save policy*
3
Power-saving mode of the current physical drives
*1: This item is not displayed for a virtual drive configured with MegaRAID WebBIOS.
*2: The following display and operation are made when Default Write Policy = "Write Back with
BBU":
- The value is changed to "Write Trough" for a RAID not supporting BBU.
At this time, "Reason for difference in write policy": "BBU is not installed" is displayed.
- The value is changed to "Write Trough" when the capacity is being expanded.
At this time, "Reason for difference in write policy": "Reconstruction is in progress" is displayed.
*3: These items may not be displayed depending on the disk array controller type (including LSI
Software RAID).
The number displayed in " coincide with Device ID.
" (Physical Drive x) does not
When the entire capacity of a drive group is not used, Total Free
Capacity is displayed. In this case, you can construct an additional virtual drive on the drive group.
The RAID level that can be used is the one currently constructed in the drive group.
2-94 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Enclosure
Displays enclosure information.
Property item
Vendor ID
Enclosure ID
Serial Number
Enclosure Model
Enclosure Location
Description
Vendor name of an enclosure
ID of an enclosure
Serial number of an enclosure
Model of an enclosure
Location of an enclosure
No enclosure device is displayed for LSI Software RAID
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-95
Enclosure (for expansion)
Displays information on an extension enclosure.
2-96
Property item
Vendor ID
Enclosure ID
Serial Number
Enclosure Model
Enclosure Location
Description
Vendor name of an enclosure
ID of an enclosure
Serial number of an enclosure
Model of an enclosure
Location of an enclosure
Number of Slots
Product Revision Level
Number of Fans
Number of Power Supplies
Number of Voltage Sensors
Number of slots
Revision level of the product
Number of fans
Number of power sources
Number voltage sensors
No enclosure device is displayed for LSI Software RAID.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Displays graphical information on an extension enclosure.
Information is not displayed on a real-time basis. Execute a rescan when an incident occurs. For how to rescan, see "
.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-97
Cache back module (BBU)
Displays information on the cache backup module (BBU)
Property item
BBU Battery Type
Full Capacity
Remaining Capacity
Description
Battery type
Maximum electric capacity
Remaining electric capacity
2-98
Capacitance Capacitance
Automatic Learn Cycles Automatic diagnosis setting
Auto Learn Period
Next Learn Cycle
Battery State
Battery Replacement
Automatic diagnosis interval (fixed number of days)
Date and time of the next automatic diagnosis
It is 28 days after the last diagnosis.
Battery state
Necessity of battery replacement (Not supported)
Battery Predictive Failure Necessity of battery replacement as a preventive action (Not supported)
This item is displayed only for disk array controllers (with cache backup).
To check if the device is a disk array controller (with cache backup), check BBU Present of "
. If the value is Yes, the device is a disk array controller (with cache backup).
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Creating new virtual drives
This section explains how to create a new virtual drive.
LSI Software RAID supports creation of virtual drives of only RAID0 and RAID1.
The maximum number of virtual drives created for each disk array controller is 24.
The maximum number of virtual drives created for each drive group is
16.
MSM does not support creation of a virtual drive that includes both
HDD and SSD.
If all of the following conditions are met, the entire capacity of a drive group may not be used. In such a case, a total free capacity of 2 MB or less remains. z
There are 1 or more virtual drives in the drive group. z
The remaining capacity of the drive group is 1 TB or more. z
When you try to use all the remaining capacity to create a virtual drive
The following table shows the number of physical drives required for creating virtual drives of different RAID levels.
However, you cannot configure virtual drive more than maximum number of physical drive in the system unit.
RAID level
RAID0
Number of physical drives required
at least 1 unit
RAID5
RAID6
RAID10 at least 3 units at least 4 units at least 4 units, a maximum of 16 units
To configure a hot spare, you need a separate physical drive in addition to physical drives required for each RAID level. You cannot configure a hot spare for RAID0.
There are two virtual drive configuration options: Simple and Advanced. Use only Advanced.
The overview of these options is as follow:
•
Advanced:
You can make only virtual drive configuration for any purpose. Select this option when you want to specify a physical drive to build or the capacity of a virtual drive.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-99
•
Simple:
This option allows you to interactively and easily configure a currently configurable virtual drive for any purpose. You can specify the RAID level and creation of a hot spare.
Do not create a virtual drive with the Simple option.
Do not create a new virtual drive when a task such as rebuilding is running.
MSM does not support a RAID6 configuration with 3 physical drives.
Avoid such a configuration.
MSM does not support a RAID1 configuration with 3 or more physical drives. Avoid such a configuration.
A RAID10 configuration must have 4 or more even-number physical drives. For example, a RAID10 configuration cannot be made up of 5 or 7 physical drives.
In the case where there are 1 or more virtual drives and a global hot spare, clear the global hot spare one and then reconfigure as a dedicated hot spare, if you are to create a new virtual drive using a physical drive with a different capacity. After that, create a new virtual drive. For how to set and remove a hot spare, see "
Configuring a hot spare " on page 2-125
.
If you create a virtual drive using a physical drive with a different capacity, the following pop-up error message is displayed:
Next we explain how to create a new virtual drive with the Advanced option.
In the following example, we describe the case where you create a RAID5 virtual drive with 3 physical drives. To create a RAID10 virtual drive, perform step 1 and step 2, and see "
Creating a RAID10 virtual drive " on page 2-107
.
2-100 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
1. With the Controller selected, click Go To > Controller > Create Virtual
Drive in the menu.
You can also right-click the Controller and click Create Virtual Drive.
The other way is to click in the graphical menu.
2. The Console mode window opens.
Select Advanced, and click Next.
Do not create a virtual drive with the Simple option.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-101
If there is a virtual drive that does not use the entire capacity of the drive group, clicking Next. The following selection window opens.
To create a new virtual drive in the existing drive group, select Use
free capacity on an existing drive group and select the target virtual drive, and then click Next to go to step 6.
To create a new virtual drive using a physical drive in the
Unconfigured Good state (not used), select Use Unconfigured
drives (create new drive group), and then click Next to go to step
3.
3. Selecting Advanced displays the Drive Group Settings window.
Select the desired RAID level (RAID5) from RAID level.
2-102 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
4. In the Select unconfigured drives window, select three physical drives to create while pressing Ctrl.
With three physical drives selected, click Add.
Make sure that Select power save mode is set to None.
This item may not be displayed depending on the disk array controller type (including LSI Software RAID).
If you have selected a wrong physical drive, click Cancel to exist from virtual drive creation and try to build a physical drive from the beginning.
5. Confirm whether the selected drives have moved to the Drive groups window or not.
After configuration, click Create Drive Group. Then, click Next.
You can also configure a dedicated hot spare when you create a virtual
.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-103
6. The Virtual drive settings window is displayed. Specify parameters for the new virtual drive, and click Create Virtual Drive.
The parameters for a new virtual drive are as follows:
Parameter Description
Virtual drive name Sets a volume name (voluntary)
Capacity Sets the capacity of a virtual drive
Initialization state
Stripe size
Sets an initialization method (Full Initialize is recommended.)
Sets a stripe size (only for RAID5 and RAID6) (Default: 64 KB
(recommended))
Read policy
Write policy
IO policy
Access policy
Disk cache policy
Sets a read policy.
No Read Ahead is recommended.
Sets write policy.
- For a disk array controller (with cache backup):
Default: Write Back with BBU is mandatory.
- For others:
Default: Write Through is recommended.
When a UPS is connected, Always Write Back can be selected.
Sets an IO policy. (Default: Direct IO (recommended))
Sets data access policy.
(Default: Read Write (recommended))
Sets a physical drive cache. (Disabled is recommended)
2-104 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Set each parameter to the required or recommended value.
Set "Write policy" in accordance with your environment with reference to the description in the above table.
"Write Back with BBU" can be selected only for disk array controllers
(with cache backup).
We cannot guarantee normal operation of the product if the recommend values are not used.
For LSI Software RAID, the parameters specified for the new virtual drive are applied to all virtual drives in the same drive group.
If you specify Always Write Back for LSI Software RAID, Write Back
with BBU is displayed after the restart of the system unit, but this is not a problem.
With Linux, only alpha-numeral characters are allowed for the volume name.
To check if the device is a disk array controller (with cache backup),
check BBU Present of " Controller " on page 2-88
. If the value is Yes, the device is a disk array controller (with cache backup).
7. The Write Through Selected pop-up window is displayed. Click Yes.
This pop-up message is displayed when Write policy is set to Write
Through. An attempt to set this parameter to another value displays the same pop-up message.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-105
8. The new virtual drive is displayed in Drive groups. Click Next.
9. The Summary window opens. Confirm the content and click Finish.
The virtual drive is created.
2-106
10. The pop-up window is displayed to notify you of the completion of the virtual drive creation. Click OK.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
11. Initialize the virtual drive.
Make sure that you initialize the virtual drive. See "
Initializing virtual drive " on page 2-116
for how to initialize a virtual drive.
If you have set Init State to Full Initialize, clicking Finish starts initialization of the virtual drive. You do not have to initialize the virtual drive again.
.
Creating a RAID10 virtual drive
1. Selecting Advanced displays the Drive Group Settings window.
Select the desired RAID level (RAID 10 Spanned drive group) from
RAID level.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-107
2. In the Select unconfigured drives window, select two physical drives to create while pressing Ctrl.
With two physical drives selected, click Add.
Make sure that Select power save mode is set to None. This item might not be displayed depending on the disk array controller type
(including LSI Software RAID).
If you have selected a wrong physical drive, click Cancel to exist from virtual drive creation and try to build a physical drive from the beginning.
3. Confirm whether the selected drives have moved to the Drive groups window or not.
After confirmation, click Create Span.
2-108 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
4. In the Select unconfigured drives window, select two physical drives to create while pressing Ctrl again.
With two physical drives selected, click Add.
You can also configure a dedicated hot spare when you create a virtual
.
5. Confirm that the selected drives have moved to the Drive groups window and there are two spans.
After confirmation, click Create Drive Group. Then, click Next.
6. The Virtual drive settings window is displayed. Specify parameters for the new virtual drive, and click Create Virtual Drive.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-109
The parameters for a new virtual drive are as follows:
Parameter
Virtual drive name
Capacity
Initialization state
Stripe size
Read policy
Write policy
IO policy
Access policy
Disk cache policy
Description
Sets a volume name (voluntary)
Sets the capacity of a virtual drive
Sets an initialization method (Full Initialize is recommended.)
Sets a stripe size (Default: 64 KB (recommended))
Sets a read policy (No Read Ahead is recommended.)
Sets a write policy.
- For a disk array controller (with cache backup):
Default: Write Back with BBU is mandatory.
- For others:
Default: Write Through is recommended.
When a UPS is connected, Always Write Back can be selected.
Sets an IO policy. (default: Direct IO (recommended))
Sets a data access policy.
(Default: Read Write (recommended))
Sets a physical drive cache. (Disabled is recommended)
Set each parameter to the required or recommended value.
Set "Write policy" in accordance with your environment with reference to the description in the above table.
"Write Back with BBU" can be selected only for disk array controllers
(with cache backup).
We cannot guarantee normal operation of the product if the recommend values are not used.
With Linux, only alpha-numeral characters are allowed for the volume name.
To check if the device is a disk array controller (with cache backup), check BBU Present of "
. If the value is Yes, the device is a disk array controller (with cache backup).
7. The Write Through Selected pop-up window is displayed. Click Yes.
2-110 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
This pop-up message is displayed when Write policy is set to Write
Through. An attempt to set this parameter to another value displays the same pop-up message.
8. The new virtual drive is displayed in Drive groups. Click Next.
9. The Summary window opens. Confirm the content and click Finish.
The virtual drive is created.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-111
10. The pop-up window is displayed to notify you that the virtual drive has been created. Click OK.
11. Initialize the virtual drive.
Make sure that you initialize the virtual drive. See "
Initializing virtual drive " on page 2-116
for how to initialize a virtual drive.
If you have set Init State to Full Initialize, clicking Finish starts initialization of the virtual drive. You do not have to initialize the virtual drive again.
To find the initialization progress, see "
Displaying task progress and terminating a task " on page 2-157
.
2-112 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Changing the setting of virtual drive(s)
Change the setting of a virtual drive in the procedure described below.
LSI Software RAID is not supported.
1. In the Logical view, select the virtual drive that you have created.
2. Right-click the virtual drive, and click Set Virtual Drive Properties.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-113
3. The following parameters are displayed:
Parameter Description
Name
Read Policy
Write Policy* 2
Sets a virtual drive name. (voluntary)
Sets a read policy.
No Read Ahead is recommended.
Sets a write policy setting
- For a disk array controller (with cache backup):
Default: Write Back with BBU is mandatory.
- For other cases:
Default: Write Through is recommended.
When a UPS is connected, Always Write Back can be selected
IO Policy*
1
Access Policy*
1
Sets an IO policy. (Default: Direct IO (recommended))
Sets a data access policy. (Default: Read Write (recommended))
Disk Cache Policy* 1
Background Initialization*
1
Sets a physical drive cache. (Disabled is recommended)
Sets background initialization (Disabled is recommended.)
*1: Use the default value for this parameter.
*2: Write Back with BBU can be selected only for disk array controllers (with cache backup).
4. Click Go after you have changed the setting.
2-114 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
5. The following pop-up message is displayed. Check Confirm and click Yes.
The setting is saved.
For how to change the write policy, see "
" on page
.
We cannot guarantee normal operation of the product if the recommend values are not used.
For LSI Software RAID, the parameters specified for the new virtual drive are applied to all virtual drives in the same drive group.
If you specify Always Write Back for LSI Software RAID, Write Back
with BBU is displayed after the restart of the system unit, but this is not a problem.
The setting value of Disk Cache Policy is not displayed for LSI
Software RAID.
To check if the device is a disk array controller (with cache backup),
check BBU Present of " Controller " on page 2-88
. If the value is Yes, the device is a disk array controller (with cache backup).
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-115
Initializing virtual drive(s)
Initialize a virtual drive in the procedure described below.
All data in a virtual drive are lost when the drive is initialized. Be extremely careful in initializing the drive. Make a backup of important data.
During initialization of virtual drive, do not restart, power on, or power off system unit. Processing stops and progress returns to 0%.
The period of time required for initializing a virtual drive is proportional to the capacity of a physical drive, not to the capacity of the virtual drive.
You can start initializing multiple virtual drives in a disk group, but the progress differs among different virtual drives. Simultaneous initialization of multiple virtual drives may take more time than
initializing them individually. See " Estimate of various processing time " on page 5-2
.
1. Click Manage > Initialize.
2-116 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2. The Group Initialization window opens.
If there are multiple disk array controllers, select a target one. (You do not have to select a disk array controller if there is only one.)
Then, select the target virtual drive and click Start.
Do not use Fast Initialization. Otherwise, MSM may not function normally.
Do not execute initialization if a consistency check is running for any other virtual drives of the same drive group.
A virtual drive with an OS installed does not appear in the Group
Initialization window.
3. The initialization confirmation dialog box opens. Click Yes.
Initialization starts.
.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-117
Consistency check of virtual drives
A consistency check reads data in all the areas of a target physical drive to check parity and mirror data consistency and to search for bad sectors. If any inconsistency is found, the parity or the mirror data is corrected.
Conduct periodical consistency checks for LSI Software RAID. If there is a bad sector during the rebuild operation in the event of a physical drive failure, the data in the sector will be lost. See "
Operation of Disk Arrays " on page 3-1
for details.
No consistency check is required for RAID devices other than LSI
Software RAID because Patrol Read is executed for periodically.
MSM: Consistency check of virtual drive(s)
Conduct a consistency check from MSM in the procedure described below.
When you conduct a consistency check for a RAID device other than
LSI Software RAID, stop Patrol Read beforehand. If you attempt a consistency check while Patrol Read is running, the system unit may
.
Check Consistency cannot be selected while rebuild or other task is running.
A consistency check is executable only for redundant virtual drives
(RAID1, RAID5, RAID6, or RAID10).
Do not execute a consistency check if initialization is running for any other virtual drive of the same drive group.
A consistency check is not applicable to a hot spare. Use Patrol Read to
check a hot spare. See " Setting Patrol Read " on page 2-179
for details.
1. Click Manage > Check Consistency in the menu.
2-118 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2. The Group Consistency Check window opens.
If there are multiple disk array controllers, select a target one. (You do not have to select a disk array controller if there is only one.)
Then, select the target virtual drive and click Start.
A consistency check starts.
To confirm the consistency check progress, see " Displaying task progress and terminating a task
" on page
.
If the virtual drive is not fully initialized, the following pop-up window opens. Click Yes.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-119
Command line: Consistency check of virtual drive(s)
This subsection explains how to execute a consistency check manually by entering a command on the command line or from a terminal. For LSI
Software RAID, incorporate this command in a batch file so that the command can be executed periodically according to an OS task schedule.
RAID devices other than LSI Software RAID are configured as factory default in such a manner that Patrol Read verifies their physical drives periodically to correct bad sectors. Therefore, you do not have to execute a periodical consistency check for RAID devices other than
LSI Software RAID.
When you execute a consistency check for a RAID device other than
LSI Software RAID, stop Patrol Read beforehand. If you attempt a consistency check while Patrol Read is running, the system unit may
.
Check Consistency is not selectable while a task such as rebuilding is running.
Consistency check is executable only for redundant virtual drives
(RAID1, RAID5, RAID6, or RAID10).
The command line can be used only for consistency check of virtual drives. Do not use the command line for any other purposes.
Otherwise, a malfunction may occur.
1. For Windows, start the command prompt.
For Linux, start the terminal.
2. For Windows, move to the MSM installation directory.
For Linux, move to the following directory:
/opt/MegaRAID/MegaCli
For Windows, MSM is installed in the following default directory:
- 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
- 32bit OS:
C:\Program Files\MegaRAID Storage Manager
2-120 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3. Enter the following commands:
For Windows:
# MegaCli -LDCC -Start -force -Lx -ax
For Linux:
# ./MegaCli -LDCC -Start -force -Lx -ax
- Lx: x is a virtual drive number.
0, 1, 2, ... ALL ("ALL" indicates all devices.)
-ax: x is a disk array controller number.
0, 1, 2, ... ALL ("ALL" indicates all disk array controllers.)
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
In Windows Server 2012, if you execute the above command, the message "No more interfaces" is output.
The following example specifies all virtual drives of disk array controller a0:
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-121
4. A consistency check starts.
If any processing, such as rebuilding or consistency check, is running in background, a message Check Consistency is not possible on Virtual
Drive ... at this time is displayed and no consistency check is performed.
The consistency check continues to be conducted even when you terminate the command line window or the terminal.
The start and end events are registered in the MSM event log and the
Windows application log.
.
2-122 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Preparation for consistency check: Stopping Patrol Read
When you execute a consistency check for a RAID device other than LSI
Software RAID, stop Patrol Read beforehand. If you attempt to perform a consistency check while Patrol Read is running, the system unit may shut down.
Stop Patrol Read in the procedure described below.
The schedule setting of Patrol Read stays effective after you stop
Patrol Read in the procedure described below.
That is, Patrol Read will be executed according to the factory default schedule even after you stop it.
You can start initialization of multiple virtual drives in a disk group, but the progress differs among different virtual drives. Simultaneous initialization of multiple virtual drives may take more time than each
individual process. See " Estimate of various processing time " on page
Stop Patrol one if running, before conducting a consistency check.
1. For Windows, start the command prompt.
For Linux, start the terminal.
2. For Windows, move to the MSM installation directory.
For Linux, move to the following directory:
/opt/MegaRAID/MegaCli
For Windows, MSM is installed in the following default directory:
- 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
- 32bit OS:
C:\Program Files\MegaRAID Storage Manager
3. Enter the following commands:
For Windows:
# MegaCli -AdpPR -Stop -ax
For Linux:
# ./MegaCli -AdpPR -Stop -ax
-ax: x is a disk array controller number.
0, 1, 2, ... ALL ("ALL" indicates all disk array controllers.)
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-123
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
In Windows Server 2012, if you execute the above command, the message "No more interfaces" is output.
To stop Patrol Read from MSM, select and right-click Controller and click Stop Patrol Read.
(Stop Patrol Read is not displayed when Patrol Read is not running.)
2-124
4. After execution of the command, confirm that one of the following messages is displayed:
Read the message and continue with a consistency check.
Execution results displayed when Patrol Read is stopped:
# No Patrol Read is in progress
# Exit Code: 0x00
Execution results displayed when Patrol Read is running:
# Adapter x: Patrol Read is stopped.
# Exit Code: 0x00
* "x" stands for a specified disk array controller number.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Configuring a hot spare
This section describes how a hot spare works and is to configured it.
A hot spare setting is applicable only to drives of the same type.
A hot spare setting is applicable only to virtual drives under the same controller.
About hot spare
The hot spare function protects virtual drives that have redundancy. If a single physical drive of a redundant virtual drive fails, rebuilding (reconfiguring data) is performed using a hot spare.
RAID5
If a drive fails
RAID5
RAID5
Hot spare
End of rebuilding
Hot spare
The hot spare is automatically rebuilt (reconfiguring the data).
The hot spare is included in the virtual drive.
Failed physical drive
In a system unit that supports hot swapping, a new physical drive is automatically configured as a hot spare during system operation when you replace the failed physical drive after completion of rebuilding.
There are two types of hot spares: global hot spare and dedicated hot spare.
A global hot spare can be used by any redundant virtual drive under the same disk array controller.
A dedicated hot spare is used only by a specified virtual drive under the same disk array controller
A global hot spare is displayed only in the Physical view. A dedicated hot spare is displayed in both the Physical and Logical views.
You need to pay attention to the operation of a hot spare if the same disk array controller is equipped with physical drives with a different capacity.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-125
Do not use a global hot spare if the disk array controller is equipped with physical drives with a different capacy. Use a dedicated hot spare for a virtual drive that consists of physical drives with the same capacity.
Rebuilding is executed for a hot spare whose capacity is larger than that of the failed physical drive. After completion of rebuilding, a new physical drive substituting the failed drive automatically becomes a hot spare. However, because the capacity of this hot spare is smaller than the one before, rebuilding cannot be executed in a next fault if the capacity of the failed physical drive is larger than the hot spare.
If physical drives with a different capacity exist, cancel a global hot spare once.
Then, configure a dedicated hot spare to a virtual drive that consists of physical drives with the same capacity. Cancel a global hot spare in the procedure described below.
1. For Windows, start the command prompt.
For Linux, start the terminal.
2. For Windows, move to the MSM installation directory.
For Linux, move to the following directory:
/opt/MegaRAID/MegaCli
For Windows, MSM is installed in the following default directory:
- 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
- 32bit OS:
C:\Program Files\MegaRAID Storage Manager
2-126 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3. Enter the following commands:
For Windows:
# MegaCli -PDHSP -Rmv -PhysDrv[?:Sx] -ax
For Linux:
# ./MegaCli -PDHSP -Rmv -PhysDrv[?:Sx] -ax
Sx: Sx is a slot number for a target global hot spare.
0, 1, 2, ...
-ax: x is a disk array controller number.
0, 1, 2, ... ALL ("ALL" indicates all disk array controllers.)
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
In Windows Server 2012, if you execute the above command, the message "No more interfaces" is output.
The global hot spare is cancelled.
In the above-mentioned procedure, use a dedicated hot spare for a system unit equipped with physical drives have the same capacity. That is, remove the global hot spare, and then configure a dedicated hot spare.
If a physical drive for hot spare use is mounted on the purchased system unit,
the hot spare is configured as a global hot spare before shipment.
Configuring a global hot spare
This subsection describes how to configure a hot spare for a current virtual drive (RIAD1, RIAD5, RAID6, or RAID10).
A hot spare is applicable only to redundant virtual drives (RAID1,
RAID5, RAID6, and RAID10). Hot spare setting for a RAID0 drive is not supported.
A global hot spare is displayed only in the Physical view, not in the
Logical view.
1. In the Physical view, select the physical drive that you want to configure as a global hot spare.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-127
2. Right-click the selected physical drive, and click Assign Global Hot Spare.
3. The drive is configured as a global hot spare.
Configuring a dedicated hot spare
This subsection describes how to configure a hot spare to a current virtual drive (RIAD1, RIAD5, RAID6, or RAID10).
A hot spare is applicable only to redundant virtual drives (RAID1,
RAID5, RAID6, and RAID10). Hot spare setting for a RAID0 drive is not supported.
Configure a dedicated hot spare only for a single drive group, not for multiple drive groups.
2-128 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Configuring a hot spare for an existing drive group
1. In the Physical view, select the physical drive that you want to configure as a dedicated hot spare.
2. Right-click the selected physical drive, and click Assign Dedicated Hot
Spare.
3. The window for configuring a dedicated hot spare opens.
Select a target drive group and click OK.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-129
4. The dedicated hot spare is configured.
In the Logical view, a hot spare is displayed for the target drive group.
2-130 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Configuring a dedicated hot spare when creating a virtual drive
You can configure a hot spare when you create a virtual drive (RAID1, RAID5,
RAID6, or RAID10). Follow the procedure described below after performing
steps 1 and 2 of " Functions of MegaRAID Storage Manager " on page 2-82
.
A dedicated hot spare cannot be configured in this procedure when you create a virtual drive in an existing drive group.
1. Selecting Advanced displays the Drive Group Settings window.
After setting the RAID level, select multiple physical drives while pressing
Ctrl in the Select unconfigured drives window.
With the target physical drives selected, click Add.
Make sure that Select power save mode is set to None.
This parameter may not be displayed depending on the disk array controller type (including LSI Software RAID).
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-131
2. Confirm whether the selected drives have moved to the Drive groups window or not.
Then, click Create Drive Group.
3. In the Select unconfigured drives window, reselect the physical drive to be configured as a hot spare window.
Next, select the drive group to which the hot spare is configured, and click
Add Hot Spare.
2-132 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
4. Confirm whether the physical drive configured as the dedicated hot spare has been moved to the Drive groups window, and click Next.
5. Create the virtual drive with reference to " Functions of MegaRAID Storage
.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-133
Removing a hot spare
This subsection explains how to remove a configured global hot spare.
This procedure is also applicable to removing a dedicated hot spare.
1. In the Physical view, select a physical drive set to the global hot spare that you want to remove.
2. Right-click the selected global hot spare, and click Remove Hot Spare in the menu.
Alternatively, you can click Go To > Physical Drive > Remove Hot
Spare.
3. A dialog box opens for confirming the deletion of the hot spare. Select
Confirm and click Yes.
The global hot spare is removed.
2-134 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Expansing virtual drive capacity
The capacity of a RAID5 or RAID6 virtual drive can be expanded without erasing data by adding an unused physical drive.
Follow the procedure described below. To prepare against any unexpected
risk, make a full system backup before expanding the capacity.
During capacity expansion, do not restart, power on, or power off the system unit. Do not stop the system until the expansion is completed. A failure to do so may cause loss of data.
Capacity expansion is not supported for the case where there are multiple virtual drives in the drive group or there is a virtual drive that is not using the entire capacity of the drive group.
During capacity expansion, the IO policy of all virtual drives under the disk array controller is temporarily set to Cached IO.
Capacity expansion for a disk array controller (with cache backup) sets the write policy of the virtual drive to Write Through (when set to
Write Back With BBU).
Background initialization is automatically executed after expansion of the capacity. (Background initialization takes about 1 minute per 10-
GB data of the prior-expansion virtual drive.)
To check if the device is a disk array controller (with cache backup),
check BBU Present of " Controller " on page 2-88
. If the value is Yes, the device is a disk array controller (with cache backup).
1. In the Logical view, click the drive group that contains the target virtual drive.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-135
2. Click Go To > Drive Group > Modify Drive Group in the menu.
Alternatively, right-click the drive group and click Modify Drive Group.
3. The confirmation dialog box opens to prompt you to back up data. After the backup, select Confirm and click Yes.
4. The Modify Drive Group window opens. Select the RAID level to be applied after expansion, and click Next.
2-136 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Select the same RAID level as the current one. Selecting a different
RAID level may cause unsuccessful capacity expansion or corruption of disk array data.
5. The Add drive to the current configuration window opens. Check the drive to be added and click Next.
6. The Summary window opens. Click Finish.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-137
7. The Confirmation window opens. Click Yes.
Capacity expansion starts.
.
2-138 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Deleting virtual drive(s)
This paragraph describes how to delete a virtual drive, and return all physical drives of the virtual drive to the unused state.
Follow the procedure described below.
All data in a virtual drive are lost when the drive is deleted. Be careful in deleting a drive. Backup important data.
1. In the Logical view, select the virtual drive to be deleted.
2. Click Go To > Virtual Drive > Delete Virtual Drive in the menu.
Alternatively, right-click the virtual drive and click Delete Virtual Drive.
3. A dialog box opens for confirming the deletion of the virtual drive. Select
Confirm and click Yes.
The virtual drive is deleted. The virtual drive is deleted also from the
Logical view.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-139
Within a drive group, it is only possible to delete the last virtual drive that you created.
To delete a virtual drive older than the last one, delete all the virtual drives from the last drive through the target one in descending order of creation date.
Changing write cache
MSM allows you to change the write cache setting for each virtual drive.
For controller boards other than disk array controllers (with cache backup), set the write policy to Always Write Back only when the system unit is connected to an uninterruptible power supply (UPS). If you set the write policy to Always
Write Back without connecting to a UPS, a power failure or instantaneous power loss may cause data corruption due to loss of data in the write cache.
Set the write policy of the disk array controller (with cache backup) board to
Write Back with BBU. If the write policy is not set to Write Back with BBU, a power failure or an instantaneous power loss may cause data corruption due to loss of data in the write cache of the disk array controller.
To check if the device is a disk array controller (with cache backup), check BBU Present of "
. If the value is Yes, the device is a disk array controller (with cache backup).
1. In the Logical view, select the virtual drive for which you want to change the write cache setting.
2. Right-click the selected virtual drive and click Set Virtual Drive
Properties in the menu.
2-140 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3. Select Write Policy, change the setting in accordance with the environment as described below, and click OK.
For the disk array controller (with cache backup):
Change the setting to Write Back with BBU.
For the system unit is connected to an uninterruptible power supply (UPS):
Change the setting to Always Write Back.
4. The pop-up window for confirming the write cache setting opens. Click Yes.
5. The cache change dialog box opens. Select Confirm and click Yes.
The write cache is configured for the virtual drive.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-141
6. Confirm that Write Policy is displayed as shown below.
When setting to Always Write Back:
Current Write Policy: Write Back
Default Write Policy: Always Write Back
When setting to Write Back with BBU
Current Write Policy: Write Back
Default Write Policy: Write Back with BBU
2-142 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Blinking LEDs
You can blink the LEDs on individual mounted physical drives and logical drives to confirm their location.
This paragraph describes a virtual drive as an example. The procedure also applies to physical drives.
LSI Software RAID is not supported.
Blinking LEDs
1. In the Logical view, select the virtual drive whose LEDs you want to blink
2. Click Go To > Virtual Drive > Start Locating Virtual Drive.
Alternatively, right-click the virtual drive and click Start Locating Virtual
Drive in the menu.
If you select a physical drive, click Start Locating Drive.
3. The LEDs on the physical drives that make up the virtual drive will blink.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-143
Stopping blinking LEDs
1. In the Logical view, select the virtual drive whose LEDs you want to stop blinking.
2. Click Go To > Virtual Drive > Stop Locating Virtual Drive.
Alternatively, right-click the virtual drive and click Stop Locating Virtual
Drive in the menu.
2-144 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Diagnosing cache back module (BBU)
The diagnostic function Learn Cycle performs one cycle of charging and discharging a cache back module to diagnose its status. Diagnosis can be performed in the procedure described below. However, automatic diagnosis is performed periodically.
This function can be used only for disk array controllers (with cache backup).
Set Learn Cycle Properties is not supported. Do not use this parameter. Use automatic diagnosis with factory default (Enable).
The diagnosis progress cannot be confirmed.
To check if the device is a disk array controller (with cache backup),
check BBU Present of " Controller " on page 2-88
. If the value is Yes, the device is a disk array controller (with cache backup).
The diagnosis time is about 5 minutes.
Automatic diagnosis is performed 28 days after the last diagnosis.
(For example, if automatic diagnosis is executed at 11 pm on May 10, the next one will be done at 11 pm on June 7.)
MSM: Execution of diagnosis
Execute diagnosis from MSM in the procedure described below.
1. Select BBU in the Physical view.
2. Right-click the selected BBU, and click Start Learn Cycle.
Diagnosis starts.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-145
2-146
MSM takes a log named Battery relearn started. when a diagnosis starts.
MSM takes a log called Battery relearn completed. when a diagnosis completes.
After you click Start Learn Cycle, preparation for diagnosis is made.
It may take about two minutes to start diagnosis.
Command line: Execution of diagnosis
This is the procedure for executing diagnosis manually by entering a command on the command line or from a terminal. To execute diagnosis periodically, include this command in a batch file so that it is executed by an OS task schedule. Set an interval of less than 28 days because automatic diagnosis is already scheduled for every 28 days.*
* The BBU property Next Learn Cycle indicates the date and time of next automatic diagnosis.
1. For Windows, start the command prompt.
For Linux, start the terminal.
2. For Windows, move to the MSM installation directory.
For Linux, move to the following directory:
/opt/MegaRAID/MegaCli
For Windows, MSM is installed in the following default directory:
- 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
- 32bit OS:
C:\Program Files\MegaRAID Storage Manager
3. Enter the following commands:
For Windows:
# MegaCli -AdpBbuCmd -BbuLearn -a0
For Linux:
# ./MegaCli -AdpBbuCmd -BbuLearn -a0
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
In Windows Server 2012, if you execute the above command, the message "No more interfaces" is output.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
4. Diagnosis starts.
The diagnosis continues to run after you terminate the command line window or the terminal.
Start and end events are registered in the MSM event log as well as in the Windows application log.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-147
SMART copyback
The SMART copyback function allows you to copy all data from a physical drive expected to fail from which SMART warning is issued to a hot spare drive.
(The physical drive is a part of a virtual drive which is created using RAID1,
RAID5, RAID6, or RAID10.)
Consequently, the function makes it possible to replace the physical drive safely with redundancy of the virtual drive retained.
In addition the function lowers the possibility for a degraded virtual drive to fail additionally with another physical drive failure during rebuild operation.
Since the SMART copyback operation copies all data of a physical drive expected to fail, system performance becomes lower when the operation runs than when it doesn't run.
This function is not supported on LSI Software RAID systems.
The SMART copyback function is disabled by default.
Use MegaCli on the command line to enable or disable the function.
During the SMART copyback operation, the physical drive from which the SMART warning occurs is marked as being replaced with <copy
destination hot spare> in the Physical view.
During the SMART copyback operation, the copy destination hot spare is marked as replacing <copy source physical drive> or Copyback
in progress in the Physical view.
The physical drive from which the SMART warning occurs becomes the
Unconfigured Bad status after the SMART copyback operation finishes.
If the SMART copyback operation is suspended before completion, the related physical drives revert to their original status.
.
2-148 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Enabling SMART copyback function
To enable SMART copyback:
1. For Windows, start the command prompt.
For Linux, start the terminal.
2. For Windows, move to the MSM installation directory.
For Linux, move to the following directory:
/opt/MegaRAID/MegaCli
For Windows, MSM is installed in the following default directory:
- 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
- 32bit OS:
C:\Program Files\MegaRAID Storage Manager
3. Execute the following command:
For Windows:
# MegaCli -AdpSetProp -CopyBackDsbl -0 -a0
For Linux:
# ./MegaCli -AdpSetProp -CopyBackDsbl -0 -a0
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
In Windows Server 2012, if you execute the above command, the message "No more interfaces" is output.
4. The following message is displayed:
Adapter 0: Set CopyBack to Enable success.
Exit Code: 0x00
5. Execute one of the following commands:
When enabling SMART copyback for a HDD:
For Windows:
# MegaCli -AdpSetProp -SMARTCpyBkEnbl -1 -a0
For Linux:
# ./MegaCli -AdpSetProp -SMARTCpyBkEnbl -1 -a0
When enabling SMART copyback for a SSD:
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-149
For Windows:
# MegaCli -AdpSetProp -SSDSMARTCpyBkEnbl -1 -a0
For Linux:
# ./MegaCli -AdpSetProp -SSDSMARTCpyBkEnbl -1 -a0
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
6. The following message is displayed:
When enabling SMART copyback for a HDD:
Adapter 0: Set Copyback on SMART error is Enable success.
Exit Code: 0x00
When enabling SMART copyback for a SSD:
Adapter 0: Set Copyback on SMART error for SSD device is Enable success.
Exit Code: 0x00
The procedure for enabling SMART copyback function is completed.
2-150 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Disabling SMART copyback
To disable SMART copyback:
1. For Windows, start the command prompt.
For Linux, start the terminal.
2. For Windows, move to the MSM installation directory.
For Linux, move to the following directory:
/opt/MegaRAID/MegaCli
For Windows, MSM is installed in the following default directory:
- 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager
- 32bit OS:
C:\Program Files\MegaRAID Storage Manager
3. Execute one of the following commands:
When disabling SMART copyback for a HDD:
For Windows:
# MegaCli -AdpSetProp -SMARTCpyBkEnbl -0 -a0
For Linux:
# ./MegaCli -AdpSetProp -SMARTCpyBkEnbl -0 -a0
When disabling SMART copyback for a SSD:
For Windows:
# MegaCli -AdpSetProp -SSDSMARTCpyBkEnbl -0 -a0
For Linux:
# ./MegaCli -AdpSetProp -SSDSMARTCpyBkEnbl -0 -a0
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
In Windows Server 2012, if you execute the above command, the message "No more interfaces" is output.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-151
4. The following message is displayed:
When disabling SMART copyback for a HDD:
Adapter 0: Set Copyback on SMART error is Disable success.
Exit Code: 0x00
When disabling SMART copyback for a SSD:
Adapter 0: Set Copyback on SMART error for SSD device is Disable success.
Exit Code: 0x00
5. Execute one of the following commands:
For Windows:
# MegaCli -AdpSetProp -CopyBackDsbl -1 -a0
For Linux:
# ./MegaCli -AdpSetProp -CopyBackDsbl -1 -a0
Distinguish between upper and lower case letters when you execute the above command on Linux.
If you execute the above command on 64 bit OS, replace the word
"MegaCli" with "MegaCli64".
6. The following message is displayed:
Adapter 0: Set CopyBack to Disable success.
Exit Code: 0x00
The procedure for disabling SMART copyback function is completed.
2-152 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Rescan
Rescan allows the system unit to recognize that you have added new physical drive during its operation.
Follow the procedure described below.
1. Click Manage > Refresh in the menu. Alternatively, click in the graphical menu.
Rescan starts.
Rescan finishes after a while.
Event reference
When you start MSM, the event log reported by managed servers is automatically displayed in the message window on the main screen.
You can store and delete the event log. You can also display the stored log.
Follow the procedures described below.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-153
Save
Saves the current event log.
1. Click Log > Save or Save as Text in the menu.
2. The window for saving the log opens.
Specify the saving location of the event log as well as the file name, and then click Save.
The event log is saved.
The maximum number of events in the current event log that can be saved is 3000. Save the event log before the number of events does not exceed 3000, and then delete the events.
See " Collecting/Operating event logs " on page 3-3 for details.
For Linux, only alphanumeric characters can be used for the name of a file to be saved.
2-154 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Clear
Deletes the event log that is currently displayed.
Do not use Clear. Otherwise, fault analysis may be affected.
1. Click Log > Clear in the menu.
2. The dialog box is displayed for confirming the deletion of the event log opens. Click Yes.
3. The dialog box for confirming whether or not to save the current event log opens.
Clicking Yes saves the event log. Specify the saving location and the file name as in the case of the Save function.
Clicking No deletes the event log without saving.
4. The event log displayed in the message window is deleted.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-155
Load
Loads and displays the saved event log.
1. Click Log > Load in the menu.
2. Select the event log file to be loaded, and then click Open.
3. The loaded event log is displayed in the message window.
After you have viewed the saved log, select Log > Rollback to
Current Log. The latest events are not displayed until you select
Rollback to Current Log.
2-156 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Displaying task progress and terminating a task
This function allows you to display the status of running tasks (initialization of a virtual drive, rebuild, consistency check, and capacity expansion). You can also stop a task.
Follow the procedures described below.
Suspend, Suspend All, and Suspend Patrol Read displayed in the task progress window are not supported and should not be used.
The progress displayed by Show Progress or Background
operation of Dashboard sometimes stops. In such a case, execute
Manage > Refresh. In the case of Show Progress, close the Show
Progress window before executing Manage > Refresh.
When Full Initialize is specified upon creation of a virtual drive, progress item Clear: displayed in Background operation of
Dashboard stays at 0%.
To erase this progress display, execute Manage > Refresh.
Displaying task progress
1. Click Manage > Show Progress in the menu. Alternatively, click More
details of Dashboard.
If there are multiple disk array controllers, select the target one. (You do not have to select a disk array controller if there is only one.)
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-157
• The progress of running tasks is displayed. The progress status windows of different tasks are shown below.
Initializing virtual drive(s)
• Rebuild • Consistency check
• Expending virtual drive capacity • Patrol Read
2-158 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
• SMART copyback*
1
*1: replacing <copy source physical drive> in the example window may be displayed as Copyback in progress.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-159
Terminating a task
During capacity expansion, do not restart, power on, or power off the system unit. Do not stop the system until a task is completed. Otherwise, data may be lost.
1. Click Abort in the task progress window.
To terminate all tasks, click Abort All.
Suspend, Suspend All, and Suspend Patrol Read displayed in the task progress window are not supported and should not be used.
2. The dialog box for confirming the termination of the task opens. Click Yes.
3. The task stops.
Patrol Read cannot be terminated in the task progress window.
Select the controller, and then select Go To > Controller > Stop
Patrol Read.
2-160 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Setting network security exceptions
This function sets network security exception for MSM.
Port number
MSM uses its reserved ports 3071 and 5571. These port numbers cannot be changed. When you introduce a network security feature, register these ports as exceptions.
3071: TCP, UDP; 5571: UDP
Port 5571 is not used by this version of MSM, hat is reserved for MSM.
If you introduce network security, please register this port number as an exception.
Do not use the MSM ports for any other applications.
Setting exceptions with Windows firewall function
When you install or start MSM with the Windows firewall function and popup message enabled, a pop-up message of Windows Security Alert opens.
Pop-up windows:
•
When you set up MSM after OS installation without closing the Windows
Server Post-Setup Security Updates window
•
When enabling the firewall function
Windows Server 2012 Windows Server 2008 R2
Windows Server 2008 Windows Server 2003 R2 /
Windows Server 2003
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-161
•
When you start MSM with the firewall function enabled
Windows Server 2012 Windows Server 2008 R2
2-162
Windows Server 2008 Windows Server 2003 R2 /
Windows Server 2003
To inhibit the pop-up display, set an exception in the procedure described below.
When a pop-up message is displayed
When the Windows Security Alert pop-up message is displayed and the program name is java or javaw, click Unblock to register the program as an exception.
For Windows Server 2012 / Windows Server 2008 R2, select both
Private Network and Public Network, and then click Allow
access.
Setting exceptions from the Windows firewall
When you enable the Windows firewall, follow the procedure described below to register the program as a firewall exception.
1. Click the Exceptions tab in the Windows firewall window.
For Windows Server 2012, select Allow an app or feature
through Windows Firewall.
For Windows Server 2008 R2, select Allow a program or feature
through Windows Firewall.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2. Click Add Program.
For Windows Server 2012, select Allow another app.
For Windows Server 2008 R2, select Allow another program.
Windows Server 2012 Windows Server 2008 R2
Windows Server 2008 Windows Server 2003 R2 /
Windows Server 2003
3. Click Browse, enter the program path, and click OK.
For Windows Server 2012 / Windows Server 2008 R2, click Browse, enter the program path, and click Add.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-163
Windows Server 2012 Windows Server 2008 R2
Windows Server 2008 Windows Server 2003 R2 /
Windows Server 2003
The program paths* are as follows:
* When MSM is installed in the default location. java:
• 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager\JRE\bin
• 32bit OS:
C:\Program Files\MegaRAID Storage Manager\JRE\bin javaw:
• 64bit OS:
C:\Program Files (x86)\MegaRAID Storage Manager\JRE\bin
• 32bit OS:
C:\Program Files\MegaRAID Storage Manager\JRE\bin
2-164 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
4. Confirm that these programs are added in the Exception tab and their check boxes are selected.
Set java and javaw for the program.
For Windows Server 2012, confirm that the program is added to
Allow apps and features and the checkbox of Name, Private, and Public are selected. Otherwise, select the unchecked the checkbox, and select OK.
For Windows Server 2008 R2, select Allow a program or feature
through Windows Firewall. Confirm in the window opened that the programs are added as allowed programs, and the check boxes
Name, Home/Work (Private), and Public are selected. If any of these check boxes is not selected, select it.
Exception programs for Ver.8.10-04, Ver.8.31-01 are javaw,
mrmonitor, and popup.
Exception programs for Ver.3.04-08 and earlier are javaw and
popup.
Windows Server 2012 Windows Server 2008 R2
Windows Server 2008 Windows Server 2003 R2 /
Windows Server 2003
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-165
Setting exceptions with the Red Hat Enterprise Linux firewall function
When the Red Hat Enterprise Linux firewall function is enabled, servers of other MSM instances cannot be viewed through the network. When you enable the firewall, register ports 3071 and 5571 as exceptions in the following procedure. (However, some functions such as progress windows are restricted.)
Centralized management is not possible when the firewall is enabled.
1. For Red Hat Enterprise Linux 6, click [System] > [Administration] >
[Firewall] in the Linux OS menu. (Close the [Firewall Configuration
Startup] window, which is displayed after selecting [Firewall].
For Red Hat Enterprise Linux 5, click [System] > [Administration] >
[Security Level and Firewall] in the Linux OS menu.
Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5
2-166 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2. For Red Hat Enterprise Linux 6, click [Other ports] in the menu on the left.
For Red Hat Enterprise Linux 5, select the [Firewall Options] tab and click [Other ports].
Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5
3. The following window is displayed: Click Add.
Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-167
4. The following window is displayed:
For Red Hat Enterprise Linux 6, select [User Defined], set [Port / Port
Range] to "3071" and [Protocol] to tcp, and then click OK.
For Red Hat Enterprise Linux 5, set [Port] to "3071" and [Protocol] to
tcp, and then click OK.
Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5
5. The port specified in step 4 is added in [Other ports].
2-168
Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5
6. Repeat steps 3 and 4 and add a port with the following.
Setting
(1) Port: 3071, Protocol: udp
(2) Port: 5571, Protocol: udp
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
7. Confirm that three setting items have been added in [Other ports].
For Red Hat Enterprise Linux 6, click [Apply].
For Red Hat Enterprise Linux 5, click OK.
Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5
8. The following pop-up massage is displayed.
Click Yes to apply the setting.
Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 5
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-169
In the CUI environment, add the following items in file
/etc/sysconfig/iptables to register exceptions:
In Red Hat Enterprise Linux 6
-A INPUT -m state --state NEW -m tcp -p tcp --dport 3071 -j
ACCEPT
-A INPUT -m state --state NEW -m udp -p udp --dport 3071 -j
ACCEPT
-A INPUT -m state --state NEW -m udp -p udp --dport 5571 -j
ACCEPT
In Red Hat Enterprise Linux 5
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport
3071 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp -dport 3071 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp -dport 5571 -j ACCEPT
Make sure that you restart the system after adding these items to the file.
2-170 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Setting event notification
This function sets an event notification when a disk array event occurs.
The following items can be set for an event notification:
Setting item
Customizing an event notification
Setting email
Description
Sets what kind of notification should be made for each event level.
Configures items required for email event notifications.
Clicking Tools > Monitor Configure Alerts in the menu displays the event notification setting window.
You cannot operate event notification setting from MSM Client of a management PC. Try this setting it from MSM Client of a managed server or a management server.
We recommend that you make a backup using Save Backup when you have made event notification setting. You can restore the setting to the original by Load Backup when you reconfigure the system unit.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-171
Customizing an event notification
Sets what kind of event notification should be made for each event level. The initial settings are as follows:
Severity level
Fatal (error)
Critical (error)
Warning
Information log)
Windows OS
Pop-up window (Popup)
Email notification (email)
Alert delivery method
Recorded in the OS event log (system
Output to the MSM message window
(MSM log)
Recorded in the OS event log (system log)
Output to the MSM message window
(MSM log)
Pop-up window (Popup)
Recorded in the OS event log (system log)
Output to the MSM message window
(MSM log)
Recorded in the OS event log (system log)
Output to the MSM message window
(MSM log)
Linux OS
Recorded in the OS event log (system log)
Output to the MSM message window
(MSM log)
Email notification (email)
Recorded in the OS event log (system log)
Output to the MSM message window
(MSM log)
Recorded in the OS event log (system log)
Output to the MSM message window
(MSM log)
Recorded in the OS event log (system log)
Output to the MSM message window
(MSM log)
For a non-GUI environment of Linux, pop-up window notification is not supported and should not be enabled.
MSM messages are recorded in the OS event log and displayed on pop-up windows not in a system unit which is remotely connected for management, but in a system unit where MSM events have occurred.
Use the MSM Log with the initial value.
2-172 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Change the setting in the following procedure as necessary.
1. Select a target severity level in the Alert Delivery Methods box of the
Alert Settings tab, and click Edit.
2. Change to any setting. Checking the box enables the selected function(s).
Setting item
MSM Log
System Log
Function
Outputs events to the MSM message window.
Records events in the OS event log
3. Click OK after you finish the setting.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-173
4. The event notification setting window opens again. Click OK.
Event notification setting is now completed.
You can also change the severity level and the alert delivery method for each event message. In this case, change the setting in the following procedure:
1. Click Change Individual Events of the Alert Settings tab.
The list of event messages is displayed.
2-174 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2. Click an event message.
To change the severity level, click Severity and select a level in the displayed pull-down menu.
To change the alert delivery method, select any setting in the Alert
Delivery Methods box.
3. Click OK when you finish the setting.
4. The event notification setting window opens again. Click OK.
The setting of severity level and the alert delivery methods are now completed.
Do not click Restore defaults in the event message list window.
Otherwise, the setting is initialized and some important event notifications may not be made.
If you have made a wrong setting, click Cancel. In this case, the following pop-up window opens. Click Yes.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-175
Setting email
Sets the items required for email event notifications.
When you want to receive event notifications from the MSM by email, open port 25 and port 7 in your SMTP server's firewall.
1. Click the Mail Server tab.
2. Enter information into each box.
Entry
Sender email Address
SMTP Server
User name
Password
Description
Enter the email address of the sender.
The address specified herein is used as the sender address of email.
Enter the SMTP server name or its IP address.
Enter the username registered for SMTP.* 1
Enter the password registered for SMTP.*
1
*1: When This server requires authentication is selected, AUTH-
LOGIN (LOGIN) is used as the authentication method of MSM.
2-176 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3. Click the Email tab.
4. Enter the email address of a sender in New recipient email address, and click Add.
5. Click OK when you finish the setting.
You can send an email test event by clicking Test. After setting, send a test event to confirm that email notification can be sent properly.
Title of transmitted email
The title of the transmitted email is as follows:
<Severify>: Vivaldi E-mail Notification: Event occurred on: <ServerName>
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-177
<Severity> stands for a severity level (INFO, WARNING, CRITICAL, or
STOP). <Server Name> stands for a server name where the event occurred.
The body of the email includes the event content and the date and time.
However, ignore for the time and date.
Example:
Title:INFO: Vivaldi E-mail Notification: Event occurred on: XXXXXX
Controller ID: 0 VD is now OPTIMAL VD 0
Generated on:Sat Jun 09 13:56:42 2007
2-178 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Setting Patrol Read
Patrol Read periodically verifies and repairs bad sectors of each physical drive.
Other normal functions take precedence in the IO processing, so that Patrol
Read has almost no impact on performance.
Do not disable Patrol Read while running. Stop Patrol Read first whenever you disable.
To stop Patrol Read, select the controller and click Go To > Controller
> Stop Patrol Read.
Patrol Read does not support LSI Software RAID. Disable Patrol Read.
Prerequisite
Patrol Read setting including schedule management is configured in the hardware before shipment. The default setting of the schedule is 3 days. (We recommend that you use the factory default setting for the schedule.)
If you start the system after the scheduled date and time of Patrol Read,
Patrol Read starts immediately even when you change the setting through
MSM.
If you have implemented centralized management, be sure to set Patrol Read on the target server.
Set the scheduler interval to 1 day or longer for this version.
Use the following command to reset the interval setting to the factory default:
MegaCli -AdpPR -SetDelay 72 -aALL
Apply Patrol Read to all virtual drives and hot spares.
1. Select the disk array controller in the Physical view or the Logical view.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-179
2. Click Go to > Controller > Set Patrol Read Properties.
3. The Patrol setting window opens.
2-180
Set Patrol Read in detail as described below.
•
Select Patrol Read mode:
Specifies the execution of Patrol Read.
Automatic: Executes Patrol Read automatically.
Manual: Executes Patrol Read manually.
Disable: Disables Patrol Read.
* We recommend that you execute Patrol Read by Automatic.
•
Maximum number of Physical drives allowed for Patrol Read concurrently:
Specifies the maximum number of physical drives for which Patrol Read is executed.
Use the default setting.
* The number of connected physical drives is displayed by default.
•
Available Virtual drives:
Displays the virtual drives for which Patrol Read can be executed.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
•
Included Virtual drives:
Displays the virtual drives for which Patrol Read can be executed.
* Typically, use Add All to set all virtual drives of Available Virtual drives to Included Virtual drives.
When you set Select Patrol Read mode to Disable, click OK and go to step 5.
4. Set an interval of executing Patrol Read.
• Patrol Read Interval:
• Hourly: Every hour
• Daily: Every day
• Weekly: Every week
• Monthly: Every month (30 days)
* Do not use (select) Run Patrol Read non-stop.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-181
•
Patrol Read Schedule:
Specifies a starting date and time of a schedule.
Selecting Perform Patrol Read when I press OK starts Patrol Read immediately regardless of the specified starting date and time of the schedule.
Set the starting date and time of the schedule to later than or equal to the current time.
Click OK.
2-182
Minutes are cut off in the time displayed as Patrol Read Schedule.
Therefore, the displayed time can be almost an hour earlier than the actual starting time.
5. The dialog box for confirming the setting opens. Click OK.
If you check Perform Patrol
Read when I press OK
If you do not check Perform
Patrol Read when I press OK
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
6. The starting event is obtained in the message window, and the Patrol Read starts.
Patrol Read does not start if disabled or already running.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-183
Restrictions
This section explains the restrictions on using MSM.
•
Do not use Go To > Controller > Load Configuration which is not supported.
•
Do not use Go To > Controller > Scan Foreign Configuration which is not supported.
•
RAID level change by Go To > Controller > Modify Drive Group is not supported. Only capacity expansion with the same RAID level is supported.
Do not use this item for any purpose other than capacity expansion.
•
Do not use Go To > Controller > Set Adjustable Task Rates which is not supported.
•
Do not use Go To > Controller > Power Settings which is not supported.
•
Do not use Go To > Controller > Schedule Consistency Check which is not supported.
•
Do not use Go To > Controller > Set Consistency Check Properties which is not supported.
•
Do not use Go To > Controller > Enable SSD Guard which is not supported.
•
Do not use Go To > Controller > Disable SSD Guard which is not supported.
•
Do not use Go To > Controller > Enable Alarm which is not supported.
•
Do not use Go To > Controller > Disable Alarm which is not supported.
•
Do not use Go To > Controller > Manage Link Speed which is not supported.
•
Do not use Go To > Controller > Save TTY Log which is not supported.
•
Do not use Go To > Controller > Drive Erase which is not supported.
•
Do not use Go To > Controller > Virtual Drive Erase which is not supported.
•
In an environment where centralized management is conducted, make sure that you stop the MSM of the management PC before you start or restart a managed server. Starting a managed server with MSM running may hang up the MSM of the management PC. If the network fails due to a LAN cable disconnection or other causes while MSM Client is running on a managed server or a management server, the MSM Client window may disappear or a pop-up massage is displayed to prompt you to logon again. In such cases, the array configuration and the array controller are not displayed after you logon or restart the MSM Client.
In such a case, check the network status and repair the fault. If the network connection status does not recover, restart the system unit before starting MSM Client.
2-184 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
•
For Linux, only the root has the administrator privileges. You cannot logon the system by assigning the root privilege to an ordinary user name.
•
Disable any unused LAN adapter of the system unit.
•
Do not try an operation prohibited or not described in this manual.
•
Otherwise, the disk array malfunction or data inconsistency can be caused.
•
MSM does not support the operation on a guest OS of Hyper-V®.
•
If you logon MSM with the View Only permission, you are restricted to the following capabilities:
•
Outputting an event notification configuration to a file
•
Outputting an event log to a file
•
Only displaying and viewing information regarding other functions
Logon with the View Only permission is allowed only for the accounts registered in the target server.
•
Logon with the Full Access permission is allowed only for the administrator accounts registered in a target server (For Windows:
Administrator privilege; for Linux: root).
•
For Linux, CUI installation of MSM is not supported except for the standalone format.
•
If MSM is installed in the CUI environment of Linux, the only MSM functions that can be used are event output to Linux (var/log/messages) and some functions that use MegaCli (functions described in this manual such as consistency check).
•
When you execute a consistency check for a RAID device other than LSI
Software RAID, stop Patrol Read beforehand. If you execute a consistency check while Patrol Read is running, the system unit may stop.
•
MSM does not support creation of a virtual drive that includes both HDD and SSD.
•
The maximum number of virtual drives created for a disk array controller is
24.
•
The maximum number of virtual drives created for a disk group is 16.
•
Within a drive group, it is only possible to delete the last virtual drive that you created.
To delete a virtual drive older than the last one, delete all the virtual drives from the last drive through the target one in descending order of creation.
•
Do not execute initialization if a consistency check is working for any other virtual drives in the same drive group.
•
Do not execute a consistency check if initialization is working for any other virtual drives in the same drive group.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-185
2-186
•
Capacity expansion is not supported for the case where there are multiple virtual drives in the drive group or there is a virtual drive that is not using the entire capacity of the drive group.
•
For a system unit with system memory of 4 GB or more, the following additional settings will improve the MSM performance.
The amount of system memory used by MSM increases a maximum of 1
GB than the standard setting.
[Windows]
(1) Move to the following folder:
64bit OS: C:\Program Files (x86)\MegaRAID Storage Manager
32bit OS: C:\Program Files\MegaRAID Storage Manager
(2) Open the file startupui.bat, and change as follows:
Before change: start JRE\bin\javaw -Duser.country.......................
After change: start JRE\bin\javaw -Xms1024m -Xmx1024m -
Duser.country....................
[Linux]
(1) Move to the following folder:
/usr/local/MegaRAID Storage Manager
(2) Open the file startupui.sh, and change as follows:
Before change:
LD_LIBRARY_PATH=$MSM_HOME/lib ./jre/bin/java -DVENUS=true....
After change:
LD_LIBRARY_PATH=$MSM_HOME/lib ./jre/bin/java -Xms1024m -
Xmx1024m -DVENUS=true....
•
In the following conditions, the event time in the MSM message window are displayed one day early. To find out the date and time of an MSM event occurrence, see the OS system log (var/log/messages):
•
Linux (UTC is not specified in the time zone setting of the system clock.)
• LSI Software RAID
•
The system has been started in the time period between 15:00:00 and
23:59:59.
•
The event is one of those that occur during system activation (for example, ID0: Firmware initialization started).
•
Do not use Suspend, Suspend All, and Suspend Patrol Read displayed in the task progress window which is not supported.
•
When you want to receive event notifications from the MSM by email, open port 25 and port 7 in your SMTP server's firewall.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Precautions
This section explains precautions on using MSM.
•
The following messages may be displayed during installation on Linux:
Warning: libstdc++34-3.4.0-1.i386.rpm: V3 DSA signature: NOKEY, key
ID 4f2a6fd2
The above message output does not have any impact.
•
The following messages are displayed during installation on Linux:
Can not find snmptrap in /usr/bin
Can not continue installation of LSI SAS Agent
Please install the net-snmp agent
The above messages indicate that the activation of the SNMP demon was not successful during MSM installation. You can ignore this message.
Check whether snmp of Linux has been installed.
•
MSM installation on Linux sometimes was not successful when the following message is displayed:
Example: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
This phenomenon happens when libstdc++.so.5 has not been installed because Legacy Software Development was not selected during Linux installation. Check whether Legacy Software Development is set as an installation option.
•
For Linux OS (AMD/Intel 64), we recommend that you install all packages by selecting System > Compatibility Arch Support > Multilib support
packages at the time of package installation.
•
Transmission of multicast packets
If you have installed MSM in the complete format, multicast packets of class D are transmitted. The IP address is 229.111.112.12.
If you do not conduct remote monitoring, we recommend that you install
MSM in the standalone format. See " Installing and removing MegaRAID
for details.
•
For both Windows and Linux, do not change the default setting for the
MSM service activation. With the default setting, MSM automatically starts when the OS is launched. We do not guarantee that the MSM service starts normally for an activation method other than the automatic activation during OS start.
•
Consistency check
Consistency check sometimes detects a data inconsistency. However, if both condition 1 and 2 below apply, the inconsistency does not affect the operation of the system unit. Ignore the warning in such a case.
Condition 1: The virtual drive is of RAID1 or RAID10.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-187
2-188
Condition 2: The virtual drive contains a partition to which Windows paging is made.
The Windows specification presents apparent data inconsistency in page files.
Windows sometimes updates the system memory before the RAID firmware finishes writing data in the physical drive of RAID1 (RAID10), and this causes data inconsistency.
In the event of such a case for user data or other data that requires consistency, Windows later issues a write command to recover the data consistency.
Thus the consistency for RAID1 (RAID10) is maintained, and the operation of the system unit is not affected.
•
During MSM operation, the MSM screen sometimes corrupts. In such a case, refresh the screen by minimizing and then maximizing the window for example.
•
MIB file
For MIB of Windows, use the following file included in the "Server installation and monitoring tool DVD" or "Driver Kit CD".
[ When "Server installation and monitoring tool DVD" is used ]
Execute the following MegaRAID Storage Manager installer file while referring to "Support_EN.html" as attachment in the "Server installation and monitoring tool DVD". The directory path of MSM is different according to the system unit and OS.
"d:(the target directory path)\lsi-adaptersas.mib"
[ When "Driver Kit CD" is used ]
"d:WIN2008\UTILITY\MSM\lsi-adaptersas.mib"
* d stands for the CD/DVD drive.
For Linux, use the following MIB file, which is expanded upon installation of SNMP.
"./etc/lsi_mrdsnmp/sas/LSI-AdapterSAS.mib"
•
When you start MSM right after OS activation, wait about five minutes and then boot the OS.
•
For a system unit with SATA physical drive installed, the following message may be displayed when you click a physical drive icon on MSM. The message does not indicate a problem and may be ignorable.
Controller ID: X Unexpected sense: PD = X - Invalid field in CDB, CDB =
0x4d 0x00 0x4d 0x00 0x00 0x00 0x00 0x00 0x20 0x00, Sense = 0x70
0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x24 0x00
0x00 0x00 0x00 0x00
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
•
If Failed of Audit Logon*
1
is enabled*
2
, a Fail Audit event is recorded in the security log of Windows Events when MSM logon fails (due to, for example, a wrong user name or password). An example of Fail Audit is shown below.
*1: The UI display may be different depending on the OS version and an environment.
*2: Depending on the OS version, the default value may be Enable.
*3: The account domain name sometimes is not displayed correctly.
Account unsuccessful in logon:
Security ID: XXXXXXXX
Account name: YYYYYYYY
Account domain: ZZZZZZZZ
•
OS warning log event: Write Cache Enabled
When the write policy is set to Write Back and the server is used as a domain controller, the following event may be recorded in the Windows system log:
Type
Source
Warning
Disk
Description
The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled. Data corruption may occur.
•
The check item Policy > Enable write caching on the device of disk drive properties of the device manager depends on the write policy setting.
The setting cannot be changed by changing this check item. To change the setting, change the write policy on MSM.
•
This disk array controller does not support SCSI commands that have the
FUA bit.
•
Services MrMonitor and MrMonitor monitoring are not installed in MSM
Ver.11.08.XX.XX or later.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-189
Replacing a physical drive
This section explains how to replace a physical drive in the event of a failure.
In replacing a physical drive, make sure that you also read the manual that accompanies the system unit.
If a system unit shuts down or reboots during the rebuild operation, the operation is suspended. The operation resumes from the point where the operation was suspended after the system unit is booted.
With a hot spare
If a physical drive fails in a virtual drive that has a hot spare configured, rebuild is automatically executed. During rebuild, the virtual drive is indicated by a yellow icon , and the physical drive icon becomes .
1. Wait until rebuilding is finished.
.
2. When rebuilding finishes, replace the failed physical drive.
A failed physical drive is indicated by a red icon in the Physical and
Logical views.
The LED of the failed physical drive turns on.
3. Wait 1 minute or more, and insert a new physical drive.
4. Confirm that the error LED turns off and the substituted physical drive is indicated by a hot spare icon in the Physical and Logical views.
2-190 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
Without a hot spare
If a fault occurs in a virtual drive, the virtual drive operates in the degraded mode. During the degraded operation, the virtual drive is indicated by a yellow icon , and the physical drive icon becomes red .
1. Replace the failed physical drive.
A failed physical drive is indicated by a red icon in the Physical and
Logical views.
The LED of the failed physical drive turns on.
2. Wait 1 minute or more, and insert a new physical drive.
3. The substituted physical drive is rebuilt.
It takes about 1 to 2 minutes until rebuilding starts.
While rebuilding is running, the physical drive is indicted by the icon , and the error LED changes to blinking.
4. After rebuilding is finished, confirm that the error LED turns off, and the substituted physical drive and the virtual drive are displayed as normal in the Physical and Logical views.
MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
2-191
2-192 MegaRAID Storage Manager
MegaRAID Storage Manager Instruction Manual
3
Operation of Disk Arrays
This section explains how to operate disk arrays.
Operation of Disk Arrays
MegaRAID Storage Manager Instruction Manual
3-1
Daily operation
Backup
Use of disk arrays improves the reliability, but it does not protect data perfectly. Therefore, as the minimum preventive action, backup the data
periodically. For details on how to make a backup, see the User's Guide
(Hitachi Compute Rack xxxx User's Guide) of the system unit.
As more data increases, it takes a longer time to back up the data. The backup time can be shortened by backing up only the difference files
(including updated files or new ones). For how to backup the difference file, see the manual of the backup program you use.
We recommend that you use four or five pieces of backup media and rotate them every day.
Periodical consistency check of LSI Software RAID virtual drives
If a bad sector (inaccessible area) is detected in a physical drive during data read or data write processing, replacement processing (replacement by a spare area) is automatically performed. This replacement processing, however, is not performed for a bad sector in the mirror data area or in an area that is not accessed in daily operation. If a physical drive fails in this status, rebuilding cannot be performed normally due to inability of reading the mirror data, resulting in loss of data of the bad sector.
To avoid this status, make sure that you perform a consistency check
periodically for LSI Software RAID. The consistency check reads data from all area of each physical drive to check if the mirror data is corrupted. For LSI
Software RAID, make sure that you perform a consistency check about
once a week.
We recommend that you perform a consistency check after business hours because of significant decrease in system (disk access) performance during the check. For how to perform consistency check of a virtual drive, see
" Consistency check of virtual drives " on page 2-118
.
RAID devices other than LSI Software RAID are configured as factory default so that Patrol Read verifies their physical drives periodically to correct bad sectors. Therefore, you do not have to execute a periodical consistency check for RAID devices other than LSI Software RAID.
3-2 Operation of Disk Arrays
MegaRAID Storage Manager Instruction Manual
Collecting/Operating event logs
The event log records information including disk array status and error causes/factors. Each log is classified into four levels: Fatal, Critical, Warning, and Information.
Collection of events makes it possible to locate the cause of an error early using the past log and take proper actions promptly, which minimizes the system down time.
Collect logs regularly considering the following preconditions and log collection guidelines.
Preconditions
•
Up to 3000 events can be saved in the current event log.
•
There are two logging methods: Save Log and Save Log Text.
The following table shows their features.
Logging method
Save Log
Save Log Text
Format
Xml
Text
Capacity for 3000 events (KB)
Approx. 2500
Approx. 500
Save time for 3000 Events
MSM server Management PC
Approx. 3 minutes
Approx. 2 minutes
Approx. 35 minutes
Approx. 2 minutes
Log collection guidelines
The number of events is calculated as follows with a system configuration and system operation under the following conditions:
•
Conditions
• Number of HDDs in the system: 8
•
Number of logical devices: 4
•
Patrol read execution frequency: Once a week
•
Consistency check execution frequency: Once a week for all logical devices
•
System shutdown/reboot execution frequency: Once a week
•
Number of events that occur weekly
•
Number of events at system startup due to system shutdown/reboot:
42
•
Number of patrol read events executed weekly: 6 maximum (1 time /3 days, 2 events/time)
•
Number of consistency check events executed weekly: 8 (2 [start/end] x 4 logical devices)
Operation of Disk Arrays
MegaRAID Storage Manager Instruction Manual
3-3
Total of events per week: 56
Total of events per year: 56 x 52 weeks = 2912
This calculation of the number of events assumes no error.
Therefore, semiannual log collection is recommended under the above conditions and operation. The Save Log Text logging method is also recommended.
After events are collected, clear them with the Clear Log menu.
The event log is registered as the Windows event viewer application log for
Windows or as the system log (/var/log/messages) for Linux.
3-4 Operation of Disk Arrays
MegaRAID Storage Manager Instruction Manual
4
In the Event of a Fault
This section explains the troubleshooting procedures against disk array faults.
In the Event of a Fault
MegaRAID Storage Manager Instruction Manual
4-1
Troubleshooting procedures
Checking the status of both disk array and physical drives
Check the status of both virtual drives and physical drives by MSM to verify what fault occurred.
Checking events
Check the event log in the MSM message window. If a fault-related event is recorded, contact the sales representative or call maintenance personnel.
Some events are displayed as pop-up messages at the occurrence of an event.
For Windows, before the pop-up notification window opens, the pop-up notification list is displayed as shown below.
4-2
Select the target pop-up notification from Alerts and click Open Item to display the pop-up notification window as shown below.
To close a pop-up notification window, click OK.
In the pop-up notification list, click Dismiss All and then Yes to close the window.
For Linux, pop-up windows are not displayed if no X Window has been launched.
If a drive group includes multiple virtual drives, a failure of a physical drive causes all virtual drives of the drive group to be in a degraded operation (Degraded or Partially Degraded).
In the Event of a Fault
MegaRAID Storage Manager Instruction Manual
Data backup
A failure of a physical drive can be recovered by replacing the physical drive.
However, if rebuilding is not successful for some reason, data may be completely lost. Make sure that you create a data backup if a fault occurs.
Contacting the maintenance company
If you confirm any fault in the current system status, contact the sales representative or call maintenance personnel.
In the Event of a Fault
MegaRAID Storage Manager Instruction Manual
4-3
4-4 In the Event of a Fault
MegaRAID Storage Manager Instruction Manual
Estimate of various processing time
5
Appendix
Appendix
5-1
MegaRAID Storage Manager Instruction Manual
Estimate of various processing time
This section provides an estimate of the time required for processing by the system unit in the unloaded state.
The processing time indication returns to 0 when it takes more than 18 hours to process task. In this case, estimated time of completion is not displayed correctly due to continue the progress rate.
The "unloaded state of the system unit" means the state in which you have installed on the system unit without only other applications, and the system unit is idle. The processing time given in this document is the processing when individual tasks run on the OS.
The system unit has the feature* that dynamically varies the task rate depending on the IO load.
This feature prioritizes IO processing over task processing, so that actual processing time can be 30 times or more the estimated processing time when the system is highly loaded. (It may take over a day.)
* This feature shortens the task processing time by raising the task rate when there is no IO processing.
Estimate of virtual drive initialization time (in the unloaded state of system unit)
Physical drive capacity
147 GB (SAS 2.5-inch)
250 GB (SATA 3.5-inch)
80 GB (SSD SATA 2.5-inch)
200 GB (SSD SATA 2.5-inch)
250 GB (SATA 3.5-inch) (LSI Software RAID (built-in SATA RAID))
Initialization time
Approx. 15 min
Approx. 300 min
Approx. 10 min
Approx. 20 min
Approx. 9 hours
The time required for initializing a virtual drive is proportional to the capacity of the physical drive, not to the capacity or the RAID level of the virtual drive.
We recommend that you execute tasks when IO processing is less active (for example, at night).
5-2 Appendix
MegaRAID Storage Manager Instruction Manual
Estimate of virtual drive consistency check time (in the unloaded state of system unit)
RAID level Virtual drive capacity
RAID 1
RAID1 (LSI Software RAID
(built-in SATA RAID))
RAID 5
RAID 6
RAID 10
147 GB (SAS 2.5-inch: 147-GB HDD × 2)
250 GB (SATA 3.5-inch: 250-GB HDD × 2)
80 GB (SSD SATA 2.5-inch: 80-GB SSD × 2)
200 GB (SSD SAS 2.5-inch: 200-GB SSD × 2)
250 GB (SATA 3.5-inch: 250-GB HDD × 2)
294 GB (SAS 2.5-inch: 147-GB HDD × 3)
500 GB (SATA 3.5-inch: 250-GB HDD × 3)
160 GB (SSD SATA 2.5-inch: 80-GB SSD × 3)
400 GB (SSD SAS 2.5-inch: 200-GB SSD × 3)
294 GB (SAS 2.5-inch: 147-GB HDD × 4)
500 GB (SATA 3.5-inch: 250-GB HDD × 4)
160 GB (SSD SATA 2.5-inch: 80-GB SSD × 4)
400 GB (SSD SAS 2.5-inch: 200-GB SSD × 4)
294 GB (SAS 2.5-inch: 147-GB HDD × 4)
500 GB (SATA 3.5-inch: 250-GB HDD × 4)
160 GB (SSD SATA 2.5-inch: 80-GB SSD × 4)
400 GB (SSD SAS 2.5-inch: 200-GB SSD × 4)
Consistency check time
Approx. 15 min
Approx. 25 min
Approx. 10 min
Approx. 20 min
Approx. 40 min
Approx. 15 min
Approx. 25 min
Approx. 10 min
Approx. 25 min
Approx. 15 min
Approx. 25 min
Approx. 10 min
Approx. 25 min
Approx. 15 min
Approx. 25 min
Approx. 15 min
Approx. 45 min
The time required for a consistency check of a virtual drive is proportional to the capacity of the virtual drive.
This does not apply to the case when you execute a consistency check for multiple virtual drives simultaneously in the same group.
We recommend that you execute tasks when IO processing is less active (for example, at night).
MegaRAID Storage Manager Instruction Manual
Estimate of rebuilding time (in the unloaded state of system unit)
RAID level Virtual drive capacity
RAID 1
RAID1 (LSI Software RAID
(built-in SATA RAID))
RAID 5
RAID 6
RAID 10
147 GB (SAS 2.5-inch: 147-GB HDD × 2)
250 GB (SATA 3.5-inch: 250-GB HDD × 2)
80 GB (SSD SATA 2.5-inch: 80-GB SSD × 2)
200 GB (SSD SAS 2.5-inch: 200-GB SSD × 2)
250 GB (SATA 3.5-inch: 250-GB HDD × 2)
294 GB (SAS 2.5-inch: 147-GB HDD × 3)
500 GB (SATA 3.5-inch: 250-GB HDD × 3)
160 GB (SSD SATA 2.5-inch: 80-GB SSD × 3)
400 GB (SSD SAS 2.5-inch: 200-GB SSD × 3)
294 GB (SAS 2.5-inch: 147-GB HDD × 4)
500 GB (SATA 3.5-inch: 250-GB HDD × 4)
160 GB (SSD SATA 2.5-inch: 80-GB SSD × 4)
400 GB (SSD SAS 2.5-inch: 200-GB SSD × 4)
294 GB (SAS 2.5-inch: 147-GB HDD × 4)
500 GB (SATA 3.5-inch: 250-GB HDD × 4)
160 GB (SSD SATA 2.5-inch: 80-GB SSD × 4)
400 GB (SSD SAS 2.5-inch: 200-GB SSD × 4)
The time required for rebuilding is proportional to the capacity of the physical drive, not to the capacity of the virtual drive. We recommend that you execute tasks when IO processing is less active (for example, at night).
Rebuild time
Approx. 15 min
Approx. 30 min
Approx. 10 min
Approx. 10 min
Approx. 50 min
Approx. 15 min
Approx. 25 min
Approx. 10 min
Approx. 10 min
Approx. 20 min
Approx. 50 min
Approx. 10 min
Approx. 10 min
Approx. 15 min
Approx. 25 min
Approx. 10 min
Approx. 10 min
5-4 Appendix
MegaRAID Storage Manager Instruction Manual
Estimate of virtual drive capacity expansion time (in the unloaded state of the system unit)
RAID level
Hard structure
RAID 0 SAS 2.5-inch: 147-
GB HDD × 3
SATA 3.5-inch: 250-
GB HDD × 3
SSD SATA 2.5-inch:
80-GB SSD × 3
SSD SAS 2.5-inch:
200-GB SSD × 3
RAID 5 SAS 2.5-inch: 147-
GB HDD × 3
SATA 3.5-inch: 250-
GB HDD × 3
SSD SATA 2.5-inch:
80-GB SSD × 3
SSD SAS 2.5-inch:
200-GB SSD × 3
RAID 6 SAS 2.5-inch: 147-
GB HDD × 4
SATA 3.5-inch: 250-
GB HDD x 4
SSD SATA 2.5-inch:
80-GB SSD x 4
SSD SAS 2.5-inch:
200-GB SSD x 4
Manner of capacity expansion
Virtual drive capacity before carrying out capacity extension
Virtual drive capacity after carrying out capacity extension
441 GB
750 GB
240 GB
600 GB
294 GB
500 GB
160 GB
400 GB
294 GB
500 GB
160 GB
400 GB
558 GB
(One set of 147-GB HDD is added )
1000 GB
(One set of 250-GB HDD is added )
320 GB
(One set of 80-GB SSD is added )
800 GB
(One set of 200-GB SSD is added )
441 GB
(One set of 147-GB HDD is added )
750 GB
(One set of 250-GB HDD is added )
240 GB
(One set of 80-GB SSD is added )
600 GB
(One set of 200-GB SSD is added )
441 GB
(One set of 147-GB HDD is added )
750 GB
(One set of 250-GB HDD is added )
240 GB
(One set of 80-GB SSD is added )
600 GB
(One set of 200-GB SSD is added )
Capacity expansion time
Approx.
100 min
Approx.
6 hours
Approx.
50 min
Approx.
70 min
Approx.
80 min
Approx.
4 hours
Approx.
35 min
Approx.
50 min
Approx.
80 min
Approx.
6 hours
Approx.
35 min
Approx.
50 min
The time required for capacity expansion is proportional to the capacity of the target virtual drive. It does not depend on the number of physical drives to be added.
We recommend that you execute tasks when IO processing is less active (for example, at night).
MegaRAID Storage Manager Instruction Manual
Events list
This section lists the events that are recorded in the MSM log and Windows
Event Viewer (or to the system log for Linux).
Some events are notified by pop-up messages.
For Windows, before the pop-up notification window appears, the pop-up notification list is displayed as shown below.
(For Linux, pop-up windows are not displayed if no X Window has been launched.)
Select the target pop-up notification from Alerts and click Open Item to display the pop-up notification window as shown below.
Events that occurred during the period between power-on and OS activation are not recorded in the event log.
All pop-up messages do not indicate faults. Confirm what event occurred.
To close a pop-up notification window, click OK.
On the pop-up notification list, click Dismiss All and then Yes to close the window.
For Linux, pop-up windows are not displayed if no X Window has been launched.
MSM registers events in Windows Event Viewer Application Log (or the system log for Linux).
5-6 Appendix
MegaRAID Storage Manager Instruction Manual
Events are registered in the log of the server on which MSM Server has been installed.
MSM registers events in Windows Event Viewer Application Log with source:
MR_MONITOR. This applies also for Linux.
Windows Server 2012 /
Windows Server 2008 R2 /
Windows Server 2008
Windows Server 2003 R2 /
Windows Server 2003
The following items are described in the list of event log below.
•
Event ID:
The identification number assigned to each event type
•
Level:
The severity of an event
•
Fatal
•
Critical
•
Warning
• Information
The following are the types of the events registered in Windows Event
Viewer Application Log:
1. Fatal, Critical
2. Warning
3. Information
•
Remarks
Added in Ver.x.xx-xx: Indicates that the event is supported from MSM version x.xx-xx.
("x" in x.xx-xx varies depending on the MSM version.)
MegaRAID Storage Manager Instruction Manual
Actions for event notification
As long as no hard disk is faulty, the system operation automatically recovers from events of Warning level and Caution level. In this case, no hard disk needs to be replaced.
However, if the same event occurs repeatedly, the relevant hard disk should be replaced.
To replace a hard disk, contact the dealer of purchase or call the maintenance personnel.
Note that the security of data at an error event is not guaranteed.
There are variable parts in a message as listed below.
Notation
<VDs>
<PDs>
Meaning
Logical drive number
Example: 0
Enclosure number and device ID connected to hard disk
[Enclosure number]: Displayed in the device ID format
Since enclosure number varies depending on the system condition, ignore it.
Example: 1:0
<rate>
<val>
Example: 1.02-0096
The value of newly set rate
Example: 30%
Newly set value
Example: 10
<date> Date time
Example: Aug 01 12:00:00 2007
<sec> Elapse time [seconds]
Example: 60
<location> Event occurrence location (address) [hexadecimal]
Example: 0x1000
<strip> Event occurrence stripe number [hexadecimal]
Example: 0x1000
<cdb>
Example: BGI: Enabled
<state> Status
Example: Optimal
Command issued to hard disk
Example: 0x28 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x80 0x00
<sense> Request sense data received from hard disk
Example: 0xf0 0x00 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x11 0x01
5-8 Appendix
MegaRAID Storage Manager Instruction Manual
List of MegaRAID Storage Manager events
Event
ID
Category Level Message Description and required action
0 CTRL Information
(PCI ID
0xXXXX/0xXXXX/0xXXXX/
0xXXXX)
1 CTRL Information
Disk array controller has started firmware initialization.
Action is not required.
7 CTRL Information Alarm disabled by user
The firmware version of disk array controller.
Action is not required.
Configuration information has been initialized.
Action is not required.
The user disabled the buzzer of disk array controller.
Action is not required.
8 CTRL
9 CTRL
Information Alarm enabled by user
Information changed <rate>
The user enabled the buzzer of disk array controller.
Action is not required.
The rate of background initialization has been changed.
Action is not required.
10 CTRL Warning Controller cache discarded due to memory/battery problems.
Power-off or reboot has been done inappropriately during write processing. Or power-off or reboot has been done during consistency check, rebuild, Patrol Read, or initialization. This is not a problem of cache memory or battery.
Action is not required.
If this event is registered during system activation made after a hang-up of the system unit, cache memory might have a problem. In this case, contact the sales representative or call maintenance personnel.
11 CTRL Fatal Unable to recover cache data due to configuration mismatch
There was a mismatch in the configuration data, so that the cache data could not be recovered.
Some data may have been lost.
We recommend that you reconfigure the disk array and restore the data from the backup.
12 CTRL Information Cache data recovered successfully
Succeeded in the recovery of cache data.
Action is not required.
Remarks
MegaRAID Storage Manager Instruction Manual
Event
ID
Category Level Message Description and required action
13 CTRL
14 CTRL
15 CTRL
Fatal
Fatal
Controller cache discarded due to firmware version incompatibility
Cache data was discarded due to incompatibility of the firmware version of disk array controller board.
Some data may have been lost.
We recommend that you reconfigure the disk array and restore the data from the backup.
Information Consistency Check rate changed
<rate>
Fatal firmware error : <code>
The rate of a consistency check has been changed.
Action is not required.
A fatal error has been detected in the firmware.
Contact the sales representative or call maintenance personnel.
16 CTRL
17 CTRL
Information Factory defaults restored
Warning
The hardware setting of disk array controller has been reset to the factory default.
Action is not required.
Flash downloaded image corrupt The firmware image used for update is corrupted.
Use a good firmware image.
18 CTRL Critical
19 CTRL
20 CTRL
21 CTRL
22 CTRL
23 CTRL
24 CTRL
Critical
Critical Flash error
Information Flashing
Critical
Critical
<version>
Information Flash of new firmware image(s) complete
Flash programming error
Flash timeout during programming
Initialization of flash memory failed.
Contact the sales representative or call maintenance personnel.
A timeout occurred during the initialization of the flash memory.
Contact the sales representative or call maintenance personnel.
Access to flash memory failed.
Contact the sales representative or call maintenance personnel.
Updating the firmware or other image.
Action is not required.
Update of disk array controller has been completed.
Action is not required.
Failed in writing into flash memory.
Contact the sales representative or call maintenance personnel.
A timeout occurred during writing data into flash memory.
Contact the sales representative or call maintenance personnel.
Remarks
5-10 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category Level Message Description and required action
25
26
27
CTRL
CTRL
CTRL
28 CTRL
29 CTRL
Critical
Critical
Critical
Flash chip type unknown
Flash command set unknown
Flash verify failure
Information Flush rate changed <val>
Seconds.
Information Hibernate command received from host
This flash memory is unknown.
Contact the sales representative or call maintenance personnel.
This flash command is unknown.
Contact the sales representative or call maintenance personnel.
An error occurred during flash memory verification.
Contact the sales representative or call maintenance personnel.
The cache flash timing rate of disk array controller has been changed.
Action is not required.
The host has issued the command to enter standby mode or hibernate mode.
Action is not required.
31 CTRL
32 CTRL
Information Event log wrapped
Fatal Multi-bit ECC error:
ECAR=<address>
The event log has wrapped in the disk array controller. No action is needed.
A multi-bit error has been detected in cache memory of disk array controller.
Contact the sales representative or call maintenance personnel.
33 CTRL
34 CTRL
Warning
Fatal
Single-bit ECC error:
ECAR=<address>
A single-bit error has been detected in cache memory of disk array controller.
The error should have been corrected and action is not required. However, if this error occurs frequently, contact the sales representative or call maintenance personnel.
Not enough controller memory A required memory space cannot be obtained in disk array controller.
Contact the sales representative or call maintenance personnel.
35 CTRL Information Patrol Read complete
36 CTRL
37 CTRL
38 CTRL
Information Patrol paused
Information Patrol Read Rate changed
<rate>
Information Patrol Read resumed
Patrol Read has been completed.
Action is not required.
Patrol Read has temporarily stopped.
Action is not required.
Patrol Read rate has been changed.
Action is not required.
Patrol Read has started again.
Action is not required.
Remarks
MegaRAID Storage Manager Instruction Manual
Event
ID
Category Level Message Description and required action
39
40
CTRL
CTRL
41 CTRL
42 CTRL
Information Patrol Read started
Information Rebuild rate changed <rate>
Information Reconstruction rate changed
<rate>
Information Shutdown command received from host
Patrol Read has started.
Action is not required.
The rebuilding rate has been changed.
Action is not required.
The rate of capacity expansion processing rate has been changed.
Action is not required.
The host issued a shutdown command.
Action is not required.
43 CTRL Information Test
44 CTRL Information Time established since power on
Time <date> <sec>Seconds.
This is a test event.
Action is not required.
The time point when disk array controller started and the time elapsed since then.
Action is not required.
45 CTRL
46 VD
47 VD
48 VD
Information User entered firmware debugger The firmware debugger has started.
Action is not required.
Warning Background Initialization aborted on VD <VDs>
The background initialization has stopped.
Action is not required if the user stopped it. If it stopped by a cause other than a user operation, check the physical drive for failures.
Information Background Initialization corrected medium error (<VDs>
Location <location>, PD <PDs>
Location <location>).
The medium error that occurred during background initialization has been repaired.
Action is not required.
Information Background Initialization completed on VD <VDs>
The background initialization has been completed.
Action is not required.
49 VD Warning Background Initialization completed with uncorrectable errors on VD <VDs>
50 VD
51 VD
Warning
Critical
Background Initialization detected uncorrectable multiple medium errors (PD <PDs>
Location <location> VD <VDs>
Location <location>)
Background Initialization failed on VD <VDs>
The background initialization has been completed, but there is an unrecoverable error.
Initialize (Full Initialize) the virtual drive.
The background initialization has been completed, but there is an unrecoverable medium error.
Initialize (Full Initialize) the virtual drive.
The background initialization has unsuccessfully terminated.
Check the physical drive for failures.
Remarks
5-12 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
53 VD
54 VD
56 VD
57 VD
58 VD
59 VD
60 VD
61 VD
Level Message Description and required action Remarks
Information Background Initialization started on VD <VDs>
The background initialization has started.
Action is not required.
Information Policy change on VD <VDs>
Previous = <setting> Current =
<setting>
Warning Consistency Check aborted on
VD <VDs>
Information Consistency Check corrected medium error (<VDs> Location
<location>, PD <PDs> Location
<location>).
Information Consistency Check done on VD
<VDs>
The policy of the virtual drive has been changed.
Action is not required.
The consistency check has stopped.
Action is not required if the user stopped it. If it was stopped by some other cause, contact the sales representative or call maintenance personnel.
A medium error was detected during consistency check, and it has been corrected.
Action is not required.
The consistency check has been completed.
Action is not required.
Information Consistency Check done with corrections on VD <VDs>
Warning
Critical
Consistency Check detected uncorrectable multiple medium errors (PD <PDs> Location
<location> VD <VDs>)
Consistency Check failed on VD
<VDs>
The consistency check has been completed, but an inconsistency has been detected.
No action is needed.
An unrecoverable medium error was detected during consistency check.
Medium errors have occurred at the same address in multiple physical drives. This phenomenon happens when a medium error occurs at the source drive during rebuild. We recommend that you initialize the virtual drive and restore the data from the backup.
The consistency check has unsuccessfully terminated.
Check the physical drive for faults.
If a fault has been detected, contact the sales representative or call maintenance personnel.
For RAID1 and RAID10, see
"Consistency check" of
"
for the action to be taken.
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
62 VD
63 VD
64 VD
66 VD
67 VD
68 VD
70 VD
71 VD
Level Message Description and required action Remarks
Warning Consistency Check completed with uncorrectable errors on VD:
The consistency check has finished, but an unrecoverable error has been detected.
Medium errors have occurred at the same address in multiple physical drives. This phenomenon happens when a medium error occurs at the source drive during rebuild. We recommend that you initialize the virtual drive and restore the data from the backup.
Warning Consistency Check found inconsistent parity on VD strip
(VD = <VDs>, strip = <strip>)
Data inconsistency has been detected in consistency check.
We recommend that you initialize the virtual drive and restore the data from the backup.
For RAID1 and RAID10, see
"Consistency check" of
" on page
for the action to be taken.
Warning Consistency Check inconsistency logging disabled, too many inconsistencies on VD <VDs>.
Consistency check has detected 10 or more locations of data inconsistency. Data inconsistency events will not be output anymore.
We recommend that you initialize the virtual drive and restore the data from the backup.
For RAID1 and RAID10, see
"Consistency check" of
" on page
for the action to be taken.
Information Consistency Check started on VD
<VDs>
The consistency check has started.
Action is not required.
Warning Initialization aborted on VD
<VDs>
Initialization of the virtual drive has stopped.
Action is not required if the user stopped it. If it was stopped by some other cause, contact the sales representative or call maintenance personnel.
Critical Initialization failed on VD <VDs> Initialization of the virtual drive has failed.
Check whether there is a fault in the physical drive. If you find a fault, contact the sales representative or call maintenance personnel.
Information Fast initialization started on VD
<VDs>
Initialization (fast mode) of the virtual drive has started.
Action is not required.
Information Full initialization started on VD
<VDs>
Initialization (full mode) of the virtual drive has started.
Action is not required.
5-14 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
72 VD
73 VD
74 VD
75 VD
76 VD
78 VD
79 VD
80 VD
81 VD
87 PD
88 PD
89 PD
Level Message Description and required action
Information Initialization complete on VD
<VDs>
Initialization of the virtual drive has been completed.
Action is not required.
Information Properties updated on <VDs>
Previous = <settings> Current =
<settings>
The properties of the virtual drive have been updated.
Action is not required.
Information Reconstruction complete on VD
<VDs>
Capacity expansion of the virtual drive has been completed.
Action is not required.
Fatal Reconstruction stopped due to unrecoverable errors VD <VDs>.
Capacity expansion of the virtual drive has stopped due to an unrecoverable error.
Contact the sales representative or call maintenance personnel.
Warning Reconstruct detected uncorrectable multiple medium errors (VD <VDs> Location
<location>,PD <PDs> Location
<location>)
Information Reconstruction resumed VD
Fatal
<VDs>
Medium errors have occurred at the same address in multiple physical drives during capacity expansion of the virtual drive. This phenomenon happens when a medium error occurs at the source drive during rebuild.
We recommend that you initialize the virtual drive and restore the data from the backup.
Capacity expansion processing has been started again.
Action is not required.
Reconstruction resume failed due to configuration mismatch
The capacity expansion could not be started again due to a configuration data mismatch.
We recommend that you initialize the virtual drive and restore the data from the backup.
Information Reconstructing started VD
<VDs>
Information State change on VD <VDs>
Critical
Previous = <state> Current =
<state>
Capacity expansion of the virtual drive has started.
Action is not required.
The state of the virtual drive has changed.
Action is not required.
An error has occurred in the physical drive.
Check the physical drive for failures. If you find a fault, contact the sales representative or call maintenance personnel.
Low level formatting has been completed.
Action is not required.
Low level formatting has started.
Action is not required.
Remarks
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
91 PD
92 PD
93 PD
95 PD
96 PD
97 PD
98 PD
99 PD
100 PD
101 PD
102 PD
Level Message Description and required action Remarks
Warning
Information Patrol Read corrected medium
Warning
Critical
PD is not supported: error: PD <PDs> Location
<location>
Patrol Read found an uncorrectable medium error PD
<PDs> Location <location>
The physical drive has been inserted.
Action is not required.
The device type is not supported.
Use a supported physical drive.
The medium error detected by
Patrol Read has been repaired.
Action is not required.
A medium error that cannot be repaired by Patrol Read has been detected.
Medium errors have occurred at the same address in multiple physical drives. This phenomenon happens when a medium error occurs at the source drive during rebuild. We recommend that you initialize the virtual drive and restore the data from the backup.
The physical drive reported a
SMART error. Replace the physical drive as a preventive action.
" on page
Information Puncturing bad block PD <PDs>
Warning
Location <location>
Rebuild aborted by user PD
<PDs>
Information Rebuild complete on <VDs>
A medium error has been created in the physical drive.
During rebuild, if a medium error occurs in the source drive or at the same address of multiple physical drives when writing data, a medium error is intentionally created to inhibit data access
(because the data integrity cannot be guaranteed).
We recommend that you initialize the virtual drive and restore the data from the backup.
Rebuilding has been stopped by user operation.
Execute rebuild again if necessary.
Rebuilding has been completed.
Action is not required.
Information Rebuild complete
Critical
Rebuilding has been completed.
Action is not required.
Rebuild failed due to source drive error PD <PDs>
Rebuilding failed due to an error at the source drive.
Contact the sales representative or call maintenance personnel.
Critical
Rebuild failed due to target drive error PD <PDs>
Rebuilding has failed due to an error at the target drive.
Contact the sales representative or call maintenance personnel.
5-16 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
104 PD
105 PD
106 PD
108 PD
109 PD
110 PD
111 PD
112 PD
113 PD
Level Message Description and required action Remarks
Information Rebuild resumed PD <PDs>
Information Rebuild started PD <PDs>
Rebuilding has started again.
Action is not required.
Rebuilding has started.
Action is not required.
Information Rebuild automatically started PD
<PDs>
Rebuilding has started automatically for the hot spare.
Action is not required.
Warning Reassign write operation failed: Failed in getting a substitute area for the physical drive.
Check the physical drive for failures. If you find a fault, contact the sales representative or call maintenance personnel.
Warning
Information Corrected medium error during
Warning
Warning
Unrecoverable medium error during rebuild: recovery PD <PDs> Location
<location>
Unrecoverable medium error during recovery PD <PDs>
Location <location>
PD removed <PDs>
A medium error has been detected during rebuild. Some data might have been lost.
We recommend that you initialize the virtual drive and restore the data from the backup.
The medium error has been repaired.
Action is not required.
A medium error has been detected, but it could not be repaired.
This message is output when a medium error occurs at the same address of physical drives or in a configuration without redundancy.
Initialization of the virtual drive and restoration of backup data are recommended.
The physical drive has been disconnected.
If you have intentionally removed the physical drive, action is not required.
In other cases, contact the sales representative or call maintenance personnel.
The level was corrected in
Ver.2.67-02.
"
.
Warning
Unexpected sense PD = <PDs>,
CDB = <cdb>, Sense = <sense>
Request sense data has been obtained from the physical drive.
Check the physical drive for failures. If no fault is found, this situation should have been handled properly, and action is not required.
For details on the request sense data, see "
" on page
.
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
114 PD
115 PD
118 PD
119 SAS
120 SAS
121 SAS
122 SAS
123 SAS
124 SAS
125 SAS
126 SAS
127 SAS
Level Message Description and required action Remarks
Information State change PD = <PDs>
Information State change by user:
Warning
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Previous = <state> Current =
<state>
Dedicated Hot Spare PD <PDs> no longer useful due to deleted array
SAS topology error: Loop detected
SAS topology error: Device not addressable
The status of the physical drive has changed.
Action is not required.
The status of the physical drive has changed.
Action is not required.
The dedicated hot spare configured for the deleted disk array has not been used for a long time.
Remove the hot spare once, and configure it again.
SAS topology error: A loop connection has been detected.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: The device could not be addressed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: Multiple ports to the same SAS address
SAS topology error: Expander error
SAS topology error: Multiple ports have the same SAS address.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: The expander has failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: SMP timeout SAS topology error: SMP timeout has occurred.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: Out of route entries
SAS topology error: An entry is out of route.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: Index not found
SAS topology error: The index cannot be found.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: SMP function failed
SAS topology error: SMP function has failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: SMP CRC error
SAS topology error: SMP has a
CRC error.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
5-18 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
128 SAS
129 SAS
130 SAS
131 PD
132 PD
133 PD
134 PD
135 PD
136 PD
137 PD
138 VD
139 VD
140 VD
141 BBU
Level Message Description and required action Remarks
Critical
Critical
SAS topology error: Multiple subtractive
SAS topology error: Table to table
Critical
Fatal
SAS topology error: Multiple paths
Unable to access device PD
<PDs>
SAS topology error: Multiple paths.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
The device cannot be accessed.
Use a supported physical drive. If this problem still happens with a supported physical drive, contact the sales representative or call maintenance personnel.
Information Dedicated Hot Spare created PD
<PDs>
The dedicated hot spare has been created.
Action is not required.
Information Dedicated Hot Spare disabled PD
<PDs>
The dedicated hot spare has been disabled.
Action is not required.
Critical
Dedicated Hot Spare <PDs> no longer useful for all arrays
The dedicated hot spare has not been used for a long time.
Action is not required.
Information Global Hot Spare created <PDs> The global hot spare has been created.
Action is not required.
Information Global Hot Spare disabled <PDs> The global hot spare has been disabled.
Action is not required.
Critical Global Hot Spare does not cover all arrays <PDs>
There is no virtual drive that can be protected by the global hot spare.
As a hot spare, use a physical drive whose capacity is the same as the physical drives of a virtual drive.
Information Created VD <VDs>
SAS topology error: Multiple subtractive
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
SAS topology error: Table to table
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Information Deleted VD <VDs>
Warning VD Marked inconsistent due to active writes at shutdown
The virtual drive has been created.
Action is not required.
The virtual drive has been deleted.
Action is not required.
The system has been shutdown during the write processing.
We recommend that you restore the data from the backup.
Information Battery Present Cache backup is enabled.
Action is not required.
Added in
Ver.8.31-01
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
142 BBU
143 BBU
144 BBU
145 BBU
146 BBU
147 BBU
148 BBU
149 BBU
150 BBU
151 BBU
152 BBU
Level
Warning
Message
Battery Not Present
Information New Battery Detected
Information Battery has been replaced
Warning
Warning
Fatal
Battery temperature is high
Battery voltage low
Information Battery started charging
Information Battery is discharging
Information Battery temperature is normal
Battery has failed and cannot support data retention. Please replace the battery.
Information Battery relearn started
Information Battery relearn in progress
Description and required action Remarks
Cache backup is disabled.
Check the cable connection of cache backup.
In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
A new cache backup module has been connected. Action is not required.
Added in
Ver.8.31-01
The cache backup module has been replaced.
Action is not required.
Added in
Ver.8.31-01
The cache backup module has high temperature.
Added in
Ver.8.31-01
If ID 149 is issued within one minute of this event, ignore this event.
Check the environmental temperature and the fan for any abnormality. In other cases, contact the sales representative or call maintenance personnel.
The voltage of the cache backup module is low.
If this event occurs repeatedly during system operation, contact the sales representative or call maintenance personnel.
When this event log is output after booting the system unit from the situation that the system unit was turned off, no action is needed.
Added in
Ver.8.31-01
The cache backup module has started battery charging. Action is not required.
Added in
Ver.8.31-01
The cache backup module is discharging. Action is not required.
Added in
Ver.8.31-01
The temperature of the cache backup module has returned to a normal level. Action is not required.
Added in
Ver.8.31-01
The cache backup module has failed and cannot hold data.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Ignore this event when this event occurs just after the system startup.
The diagnosis of the cache backup module has started. Action is not required.
Added in
Ver.8.31-01
The diagnosis of the cache backup module is in progress. Action is not required.
Added in
Ver.8.31-01
5-20 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
153 BBU
154 BBU
155 BBU
156 BBU
157 BBU
158 BBU
159 BBU
160 BBU
161 BBU
162 BBU
163 BBU
164 ENCL
165 ENCL
166 ENCL
Level Message Description and required action Remarks
Information Battery relearn completed The diagnosis of the cache backup module has been completed.
Action is not required.
Added in
Ver.8.31-01
Information Battery relearn timed out A timeout occurred during the diagnosis of the cache backup module. Action is not required.
Information Battery relearn pending: Battery is under charge
The diagnosis of the cache backup module is suspended. The cache backup module is being charged.
Action is not required.
Added in
Ver.8.31-01
Information Battery relearn postponed The diagnosis of the cache backup module has been postponed.
Action is not required.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Information Battery relearn will start in 4 days
The diagnosis of the cache backup module will start 4 days later.
Action is not required.
Added in
Ver.8.31-01
Information Battery relearn will start in 2 day The diagnosis of the cache backup module will start 2 days later.
Action is not required.
Added in
Ver.8.31-01
Information Battery relearn will start in 1 day The diagnosis of the cache backup module will start 1 day later.
Action is not required.
Added in
Ver.8.31-01
Information Battery relearn will start in 5 hours
The diagnosis of the cache backup module will start 5 hours later.
Action is not required.
Added in
Ver.8.31-01
Warning Battery The cache backup module has been disconnected. Check the cable connection of cache backup module. In other cases, contact the sales representative or call maintenance personnel.
Warning Current capacity of the battery is below threshold
The capacity of the cache backup module is below the threshold.
Action is not required.
Information Current capacity of the battery is above threshold
The capacity of the cache backup module is above the threshold.
Action is not required.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Information SES enclosure discovered:Port % A SES enclosure has been discovered.
Action is not required.
Information SAF-TE enclosure discovered:Port %
A SAF-TE enclosure has been discovered.
Action is not required.
Critical Communication lost on enclosure:Port %
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Communication with the enclosure has been lost.
Check whether the enclosure is properly connected and powered on. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
167 ENCL
168 ENCL
169 ENCL
170 ENCL
171 ENCL
172 ENCL
173 ENCL
174 ENCL
175 ENCL
176 ENCL
177 ENCL
Level Message Description and required action Remarks
Information Communication restored on enclosure:Port %
Critical Fan failed on enclosure:Port % % The fan of the enclosure has failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Information Fan inserted on enclosure:Port % %
The fan of the enclosure has been connected.
Action is not required.
Added in
Ver.8.10-04
Warning Fan removed on enclosure:Port % %
Communication with the enclosure has resumed.
Action is not required.
Added in
Ver.8.10-04
Critical
Power supply failed on enclosure:Port % Power supply %
The fan in the enclosure has been disconnected.
Check the connection and the power of the ESM unit. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
The power unit in the enclosure has failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Information Power supply inserted on enclosure:Port % Power supply %
Warning
Critical
Information ESM inserted on
Critical
Warning
Power supply removed on enclosure:Port % Power supply %
ESM failed on enclosure:Port % % enclosure:Port % %
SIM removed on enclosure:Port % %
Temperature sensor below warning threshold on enclosure:Port % %
The power unit in the enclosure has been connected.
Action is not required.
The power unit in the enclosure has been disconnected.
Check whether the enclosure is properly connected and powered on. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
The ESM unit in the enclosure has failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
The ESM unit in the enclosure has been connected.
Action is not required.
Added in
Ver.8.10-04
The SIM in the enclosure has been disconnected.
Added in
Ver.8.10-04
Check the connection and the power of the ESM unit. In other cases, contact the sales representative or call maintenance personnel.
The enclosure temperature is below the warning threshold of the temperature sensor.
Added in
Ver.8.10-04
Check the environmental temperature and the fan for any abnormality.
5-22 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
178 ENCL
179 ENCL
180 ENCL
181 ENCL
182 ENCL
183 ENCL
184 ENCL
185 ENCL
186 ENCL
Level Message Description and required action Remarks
Critical Temperature sensor below error threshold on enclosure:Port % %
The enclosure temperature is below the error threshold of the temperature sensor.
Check the environmental temperature and the fan for any abnormality. If there may be other abnormalities, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Warning Temperature sensor above warning threshold on enclosure:Port % %
The enclosure temperature is above the warning threshold of the temperature sensor.
Check the environmental temperature and the fan for any abnormality.
Added in
Ver.8.10-04
Critical Temperature sensor above error threshold on enclosure:Port % %
The enclosure temperature is above the error threshold of the temperature sensor.
Check the environmental temperature and the fan for any abnormality. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Critical
Warning Too many enclosures connected to port. Enclosure not supported;
Enclosures cannot be supported because the number of enclosure connections exceeds the supported number.
Added in
Ver.8.10-04
Check the number of enclosure connections. If the number of connections is normal, contact the sales representative or call maintenance personnel.
Critical Firmware mismatch on enclosure:
Warning Sensor bad on enclosure:
A firmware mismatch has happened in the enclosure.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
The sensor of the enclosure is abnormal.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Critical
Critical
Phy is bad on enclosure:
The enclosure has been shutdown.
Action is not required.
Added in
Ver.8.10-04
If the enclosure is not shutdown intentionally, contact the sales representative or call maintenance personnel.
The phy of the enclosure is abnormal.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
The sensor of the enclosure is abnormal.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
187 ENCL
188 ENCL
189 ENCL
190 ENCL
193 PD
194 BBU
195 BBU
196 PD
Level Message Description and required action Remarks
Critical
Critical
Critical
Hardware error on enclosure:
No response from enclosure:
A hardware error has occurred in the enclosure.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
The enclosure returns no responses.
Check whether the enclosure is properly connected and powered on. In other cases, contact the sales representative or call maintenance personnel.
SAS/SATA mixing not supported in enclosure; disabled PD <PDs>
Both SAS and SATA physical drives exists in the enclosure, so that they cannot be used.
Use a supported physical drive.
Information Unsupported hotplug was
Critical detected on SES enclosure:
PD too small to be used for autorebuild:
An unsupported hot plug has been detected in the SES enclosure.
Check the connections of the parts mounted on the enclosure.
Added in
Ver.8.10-04
The capacity of the substituted physical drive is too small for starting rebuild.
Replace with a physical drive of an adequate capacity.
Information BBU enabled; changing WT logical drives to WB
Warning
BBU disabled; changing WB logical drives to WT
The cache backup function has been enabled.
The write policy has been changed from WT to WB.
Action is not required.
Added in
Ver.8.31-01
The cache backup function has been disabled.
The write policy was changed from
WB to WT.
Added in
Ver.8.31-01
If this event repeatedly occurs not during the diagnosis of the cache backup module (ID 152), check the cable connection of the cache backup module. If the cable connection has no problems, contact the sales representative or call maintenance personnel.
When this event log is output after booting the system unit from the situation that the system unit was turned off, no action is needed.
Warning Bad block table is 80% full on PD
<PDs>
The remaining substitute area for bad blocks is running short.
Occurrence of a bad block without an available substitute area causes a disk fault.
Collect the backup data, and contact the sales representative or call maintenance personnel.
5-24 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
197 PD
200 BBU
201 CTRL
202 CTRL
203 CTRL
204 ENCL
205 ENCL
206 ENCL
207 ENCL
208 ENCL
Level Message Description and required action Remarks
Critical
Critical
Bad block table is full; unable to log block:
The substitute area for bad blocks has been exhausted.
Occurrence of a bad block without an available substitute area causes a disk fault.
Collect the backup data, and contact the sales representative or call maintenance personnel.
Battery/charger problems detected; SOH Bad
A fault was detected in the cache backup module.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Warning Single-bit ECC error; warning threshold exceeded
Critical
Critical
Warning
Single-bit ECC error; critical threshold exceeded
Single-bit ECC error; further reporting disabled
Power supply switched off for enclosure:Port % Power supply %
Information Power supply switched on for
Warning enclosure:Port % Power supply %
Power supply cable removed on enclosure:Port % Power supply %
Information Power supply cable inserted on enclosure:Port % Power supply %
Information Fan returned to normal on enclosure:
The number of single-bit errors detected in cache memory of the disk array controller has exceeded the threshold.
Contact the sales representative or call maintenance personnel.
The number of single-bit errors detected in cache memory of the disk array controller has exceeded the threshold.
Contact the sales representative or call maintenance personnel.
The number of single-bit errors detected in cache memory of the disk array controller has exceeded the threshold.
Contact the sales representative or call maintenance personnel.
The power to the enclosure has been turned off.
Action is not required. If the power-off is not intentional, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
The power for the enclosure has been turned on.
Action is not required.
Added in
Ver.8.10-04
The power cable in the enclosure has been disconnected.
Check whether the power cable has been removed. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
The power cable in the enclosure has been connected.
Action is not required.
Added in
Ver.8.10-04
The fan in the enclosure has been connected.
Action is not required.
Added in
Ver.8.10-04
MegaRAID Storage Manager Instruction Manual
Event
ID
Category Level Message Description and required action Remarks
218 CONFIG Information Foreign Configuration Detected Old configuration information has been deleted.
Action is not required.
219 CONFIG Information Foreign Configuration Imported Old configuration information has been imported.
Action is not required.
220 CONFIG Information Foreign Configuration Cleared Old configuration information has been cleared.
Action is not required.
223 SAS Warning Link lost on SAS wide port: {1}
PHY = {2}
The link of the SAS wide port has been lost.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
224 SAS Information Link restored on SAS wide port:
{1} PHY = {2}
225 SAS
226 PD
227 CTRL
228 ENCL
Warning
Information Bad block reassigned
Information Controller Hot Plug detected
Warning
Allowed error rate exceeded on
SAS port: {1} PHY = {2}
Controller[%] Temperature sensor differential detected on enclosure:PD %(c Port A/p1)
Sensor %
The link of the SAS wide port has been restored. Action is not required.
A bad block has been replaced.
Action is not required.
Added in
Ver.8.31-01
The error rate of the SAS port has exceeded the allowed value.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
A disk array controller has been hot-plugged.
Action is not required.
The temperature sensor has detected changes of ambient temperature in the enclosure.
No action is needed.
Added in
Ver.8.10-04
234 ENCL
235 ENCL
237 CTRL
238 CTRL
Information Firmware download in progress on enclosure
Warning
Information Dirty Cache data discarded by
Warning
Firmware download failed on enclosure user
PDs missing from configuration at boot
Firmware download is in progress on an enclosure.
Action is not required.
Added in
Ver.8.10-04
Firmware download to an enclosure has failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Dirty cache data has been discarded by the user.
Action is not required.
A physical drive has not been discovered during system activation.
If the removal is not intentional, contact the sales representative or call maintenance personnel.
5-26 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
239 CTRL
240 CTRL
241 CTRL
242 BBU
243 ENCL
244 PD
245 PD
246 ENCL
247 PD
248 PD
249 VD
Level Message Description and required action Remarks
Critical
Critical
VDs missing drives and will go offline at boot
VDs missing at boot <VDs>
A virtual drive has been put to offline because it was not discovered during system activation.
Contact the sales representative or call maintenance personnel.
A virtual drive has not been discovered during system activation.
If the removal is not intentional, contact the sales representative or call maintenance personnel.
Critical Previous configuration completely missing at boot
The previous configuration information has been lost during system activation.
Reconfigure virtual drives.
Information Battery charge complete
Information Fan speed changed on enclosure:Port % %
The charging of the cache backup module has been completed.
Action is not required.
Added in
Ver.8.31-01
The fan speed in the enclosure has been changed.
Action is not required.
Added in
Ver.8.10-04
Information Dedicated spare imported as global due to missing arrays
A dedicated hot spare has been changed to a global hot spare because the target virtual drive of the dedicated hot spare is missing.
Reconfigure a virtual drive and a dedicated hot spare as necessary.
Warning PD rebuild not possible as
SAS/SATA is not supported in an array
The substituted physical drive cannot be rebuilt because it is of a different type.
Use a physical drive of a correct type (SAS or SATA).
Information SEP has been rebooted as a part of enclosure firmware download.
SEP will be unavailable until this process completes.
The processor of the enclosure is restarting.
The processor will become operative when the restart is complete. Action is not required.
Information Device inserted
Warning Device
Added in
Ver.8.10-04
The device has been inserted.
Action is not required.
The physical drive has been disconnected.
If you have intentionally removed the physical drive, action is not required.
In other cases, contact the sales representative or call maintenance personnel.
The level was corrected in
Ver.2.67-02.
Information VD is now OPTIMAL The physical drive has become optimal.
Action is not required.
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
250 VD
251 VD
252 VD
253 BBU
257 PD
258 CTRL
259 CTRL
261 CTRL
263 CTRL
264 CTRL
265 CTRL
266 CTRL
267 CTRL
Level Message Description and required action Remarks
Warning
Critical
Fatal
Warning
VD is now PARTIALLY DEGRADED The virtual drive has become partially degraded.
Contact the sales representative or call maintenance personnel.
VD is now DEGRADED The virtual drive has become degraded.
Contact the sales representative or call maintenance personnel.
VD is now OFFLINE
Battery requires reconditioning; please initiate a LEARN cycle
Warning PD
The virtual drive has become offline.
Contact the sales representative or call maintenance personnel.
The cache backup module requires reconditioning. Execute diagnosis.
Added in
Ver.8.31-01
Warning
Warning
Puncturing of LBAs enabled
Puncturing of LBAs disabled
A device is missing.
If the removal is not intentional, contact the sales representative or call maintenance personnel.
The puncturing function is enabled.
Action is not required.
The puncturing function is disabled.
Action is not required.
Package version.
Action is not required.
Added in
Ver.2.29-00
Added in
Ver.2.29-00
Added in
Ver.2.29-00
Warning Foreign configuration table overflow
Warning
Partial foreign configuration imported,PDs not imported:
Information Connector is active:
Warning Command timeout on PD:
The array configuration table has overflowed.
An error occurred on the disk array controller.
Contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
The configuration information has been partially added. Not all physical drives have been added.
Check whether you have added a physical drive that was used in some other system unit.
If you have not done anything, contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
The connector is active.
Action is not required.
Board revision.
Action is not required.
Added in
Ver.2.29-00
Added in
Ver.2.29-00
Timeout occurred in a command on the device.
Contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
5-28 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
268 CTRL
269 CTRL
271 CTRL
272 CTRL
273 CTRL
274 CTRL
275 CTRL
276 PD
277 PD
278 PD
280 PD
281 PD
Level Message Description and required action Remarks
Warning PD Reset: The device was reset.
Action is not required. However, if this error occurs frequently, contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
Warning
Fatal
VD bad block table is 80% full: The remaining substitute area for bad blocks is running short.
Occurrence of a bad block without an available substitute area causes a disk fault.
Collect the backup data, and contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
Uncorrectable medium error logged:
Information VD medium error corrected:
An uncorrectable medium error has been logged.
Contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
A virtual drive medium error has been fixed.
Action is not required.
Added in
Ver.2.29-00
Warning
Warning
Fatal
PD Bad block table is 100% full: The substitute area for bad blocks has been exhausted.
Occurrence of a bad block without an available substitute area causes a disk fault.
Collect the backup data, and contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
VD Bad block table is 100% full: The substitute area for bad blocks has been exhausted.
Occurrence of a bad block without an available substitute area causes a disk fault.
Collect the backup data, and contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
Controller needs replacement since IOP is faulty
Information CopyBack started on PD: {1}
Warning
Source PD: {2}
CopyBack aborted on PD: {1}
Source PD: {2}
An IOP fault is suspected. The controller board of the disk array needs to be replaced.
Contact the sales representative or call maintenance personnel.
Added in
Ver.2.29-00
CopyBack has started. Action is not required.
CopyBack has stopped.
Action is not required if the user stopped it.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Information CopyBack completed on PD: {1}
Source PD: {2}
CopyBack has been completed.
Action is not required.
Information CopyBack resumed on PD: {1}
Source PD: {2}
Information CopyBack automatically started on PD: {1} Source PD: {2}
CopyBack has started again.
Action is not required.
CopyBack has started automatically. Action is not required.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Added in
Ver.8.31-01
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
282 PD
284 BBU
292 CTRL
293 PD
294 PD
295 PD
297 PD
298 PD
303 CTRL
304 CTRL
Level Message Description and required action Remarks
Critical CopyBack failed due to source drive error on PD: {1} Source
PD: {2}
Information BBU FRU is:
CopyBack failed due to an error at the source drive.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
FRU of the cache backup module has been loaded. Action is not required.
Added in
Ver.8.31-01
Warning Patrol Read can't be started, as
PDs are either not ONLINE, or are in a VD with an active process, or are in an excluded
VD
Patrol Read could not be started because there are no virtual drives that can be activated.
Added in
Ver.3.04-08
Check the virtual drives of the disk array controller, and then contact the sales representative or call maintenance personnel.
Information Copyback aborted by user on PD:
{1} Source PD: {2}
Copyback has been stopped by the user. Action is not required.
Added in
Ver.8.31-01
Critical Copyback aborted on the hot spare as hot spare needed for rebuild.
Hot Spare PD: {1} Source PD:
{2}
Copyback has aborted because the hot spare was needed for rebuild.
Added in
Ver.8.31-01
Action is not required.
Warning Copyback aborted as rebuild required in the array.
PD: {1} Source PD: {2}
Copyback has aborted because rebuild was requested.
Action is not required.
Added in
Ver.8.31-01
Warning Copyback cannot be started as drive is too small.
PD: {1} Source PD: {2}
The capacity of the substituted physical drive is too small for starting Copyback.
Check whether a correct physical drive is mounted.
If a correct physical drive is mounted, the physical drive has a fault.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Warning Copyback cannot be started as
SAS/SATA is not supported in an array.
PD: {1} Source PD: {2}
Copyback could not be started because the physical drive is of a different type.
Check whether a correct physical drive is mounted.
If a correct physical drive is mounted, the physical drive has a fault.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01 properties The controller properties have been changed.
Action is not required.
Information Patrol Read properties changed The Patrol Read properties have been changed.
Action is not required.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
5-30 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
306 BBU
307 BBU
327 CTRL
331 CTRL
332 ENCL
333 PD
334 PD
335 VD
336 CTRL
337 VD
338 CTRL
339 CTRL
346 CTRL
Level Message Description and required action Remarks
Information Battery properties changed The properties of the cache backup module have been changed. Action is not required.
Added in
Ver.8.31-01
Warning Periodic Battery Relearn is pending. Please initiate manual learn cycle as Automatic learn is not enabled.
Warning Consistency Check started on an inconsistent VD:
The diagnosis of the cache backup module is suspended. Start the diagnosis manually because automatic diagnosis is disabled. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Consistency check has been executed on a virtual drive that has not been initialized or whose capacity has been expanded.
Action is not required.
Added in
Ver.2.67-02
Information Power state change on The power status has been changed.
Action is not required.
Added in
Ver.8.31-01
Information Enclosure element status changed
The enclosure status has been changed.
Action is not required.
Information Rebuild is not allowed on PD as
HDD/SSD mix is not supported in
VDs. PD:
Rebuilding cannot be executed because the virtual drive is configured so as not to allow mixture of HDD and SSD. Check the type of the substituted drive.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.31-01
Information Copyback is not allowed on PD as
HDD/SSD mix is not supported in
VDs.
PD: {1} Source PD: {2}
Copyback cannot be executed because the virtual drive is configured so as not to allow mixture of HDD and SSD. Check the type of the spare drive.
Information VD Bad block table is Cleared.
VD:
A bad block table has been deleted.
Action is not required.
Critical SAS topology error:
Information VD cluster of medium error corrected:
An SAS topology error occurred.
Check the RAID setting of the enclosure.
A cluster medium error has been repaired.
Action is not required.
Information Controller requests a host bus rescan
Information Controller repurposed and factory defaults restored
The controller has requested rescan of a host bus.
Action is not required.
The controller has been redefined and the factory default has been restored.
Action is not required.
Information Snapshot enabled on A snapshot is enabled.
Action is not required.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.10-04
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
347 CTRL
348 CTRL
349 CTRL
350 CTRL
351 CTRL
352 CTRL
353 CTRL
354 CTRL
355 CTRL
356 CTRL
357 CTRL
358 CTRL
359 CTRL
360 CTRL
Level Message Description and required action Remarks
Information Snapshot disabled by the user on Snapshot has been disabled by the user.
Added in
Ver.8.10-04
Action is not required.
Critical Snapshot disabled on
Information Snapshot Point In Time created on
A snapshot is disabled.
Check whether the snapshot repository or the snapshot view is full. Enable snapshot again.
A snapshot has been created.
Action is not required.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Information Snapshot Point In Time deleted
Information Snapshot View created on
Information Snapshot View deleted on
Information Snapshot rollback started for
Fatal on
Point In Time on
Snapshot rollback internally aborted for Point In Time on
Information Snapshot rollback completed for
Point In Time on
A snapshot has been deleted.
(When automatically deleted) action is not required.
Added in
Ver.8.10-04
A snapshot view has been created.
Action is not required.
Added in
Ver.8.10-04
A snapshot view has been deleted.
Action is not required.
Added in
Ver.8.10-04
A snapshot rollback has started.
Action is not required.
Added in
Ver.8.10-04
A snapshot rollback has been aborted.
Study the past events to find out if the snapshot data is enabled. You cannot execute rollback if the snapshot data is disabled.
Reconfigure the snapshot in this case.
Added in
Ver.8.10-04
A snapshot rollback has been completed.
Action is not required.
Added in
Ver.8.10-04
Information Snapshot rollback progress on
Warning
Critical
Point In Time on
Snapshot repository 80% full on The snapshot repository has been used 80%.
Reconsider the area of the snapshot repository.
Snapshot repository full on
Snapshot rollback is in progress.
Action is not required.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Warning
Critical
Snapshot View 80% full on
Snapshot View full on
The snapshot repository has been exhausted.
Reconsider the area of the snapshot repository.
The snapshot view has been used
80%.
Reconsider the area of the snapshot view.
The snapshot view has been exhausted.
Reconsider the area of the snapshot view.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
5-32 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
361 VD
362 VD
363 CTRL
364 CTRL
365 CTRL
366 CTRL
367 PD
368 CTRL
369 VD
370 VD
371 VD
372 VD
373 VD
Level Message Description and required action Remarks
Critical
Warning
Critical
Repository lost for VD
Repository restored for VD
Snapshot encountered an unexpected internal error:
Information Auto Snapshot enabled on
Information Auto Snapshot disabled on
The snapshot repository for the virtual drive has been deleted.
Check if the repository has been intentionally deleted. If you cannot check it, set the snapshot repository to the virtual drive again.
Added in
Ver.8.10-04
The snapshot repository for the virtual drive has been restored.
Confirm that the correct data has been restored.
Added in
Ver.8.10-04
An unexpected internal error occurred in the snapshot.
Check if there are any other errors. Also check the snapshot settings.
Added in
Ver.8.10-04
Auto snapshot is enabled.
Action is not required.
Auto snapshot is disabled.
Action is not required.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Critical
Information COD on PD updated as it was stale. PD:
Warning
Configuration command could not be committed to disk, please retry.
Update of the configuration information has not been finished.
Retry the update.
Added in
Ver.8.10-04
Power state change failed on
The configuration data has been updated.
Action is not required.
Added in
Ver.8.10-04
Power state change has failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Warning VD is not available. VD:
Information VD is available. VD:
Information VD is used for Cachecade(TM).
VD:
Information VD is being cached in
Cachecade(TM). VD:
Information VD is no longer being cached in
Cachecade(TM). VD:
The virtual drive cannot be used.
Check the virtual drive settings.
Check if there are any other errors. If there are, take appropriate action. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Cache Cade or the virtual drive has become available.
Action is not required.
The Cache Cade function is assigned for the virtual drive.
Action is not required.
Added in
Ver.8.10-04
The Cache Cade function has stored the cache data of the virtual drive.
Added in
Ver.8.10-04
Action is not required.
The Cache Cade function cannot store the cache data of the virtual drive anymore.
Action is not required.
Added in
Ver.8.10-04
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
374 CTRL
375 CTRL
376 CTRL
377 VD
379 VD
380 VD
381 VD
383 CTRL
384 CTRL
385 CTRL
387 CTRL
388 CTRL
389 CTRL
Level Message Description and required action Remarks
Critical
Warning
Snapshot deleted due to resource constraints on
One of the snapshot data item has been deleted because of the exceedance of the snapshot data capacity.
Reconsider the area of the snapshot repository.
Added in
Ver.8.10-04
Auto Snapshot failed for Auto snapshot failed because it is set to "Stop taking snapshot" and the number of snapshots has reached the maximum number(8).
Added in
Ver.8.10-04
Check if there is any problem in the auto snapshot setting.
Warning Controller reset on-board expander
Warning Cachecade(TM) VD capacity changed VD:
The controller has reset the expander.
Action is not required. If this event occurs frequently, contact the sales representative or call maintenance personnel.
Added in
Ver.8.10-04
The capacity of the virtual drive for
Cache Cade has been changed.
Added in
Ver.8.10-04
Check if any constituting drive has been changed or has a fault. If there is any fault, contact the sales representative or call maintenance personnel.
Information Advanced Software Options Key was applied
Information Snapshot schedule properties
Information Snapshot scheduled action is
Information Advanced Software Options was
Information Advanced Software Options
Warning changed on VDs: due-Schedule timer expired on
VDs: transferred
Serial number:
Advanced Software Options
Serial number mismatched. Key vault Serial number is:
Information Power policy changed in VD:
The activation key has been authorized.
Action is not required.
The snapshot schedule has been changed.
Action is not required.
The term of the snapshot schedule has expired.
Added in
Ver.8.10-04
Action is not required.
Advanced Software Options have been transferred.
Action is not required.
Added in
Ver.8.10-04
Serial number.
Action is not required.
Serial number mismatch.
Perform re-hosting.
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Added in
Ver.8.10-04
Warning Cannot transition to max power savings on VD:
Information Host driver is loaded and operational
The power policy has been changed. Action is not required.
Added in
Ver.8.31-01
The power policy cannot become max power savings mode. Restore the power policy to the factory default.
Added in
Ver.8.31-01
The host driver has been normally loaded and is in operational. Action is not required.
Added in
Ver.8.31-01
5-34 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
392 SAS
393 SAS
394 BBU
395 BBU
397 BBU
403 CTRL
404 CTRL
407 CTRL
408 CTRL
409 CTRL
410 CTRL
411 CTRL
412 CTRL
413 CTRL
414 CTRL
415 CTRL
Level Message Description and required action Remarks
Warning Link failed on Wide Port {1} Link
{2}
The link of the wide port has been lost.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Information Link restored on Wide Port {1}
Link {2}
Information Memory module FRU is:
The link of the wide port has been restored. Action is not required.
The cache backup module has been loaded. Action is not required.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Critical Cache-Vault power pack is suboptimal. Please replace the pack.
The cache backup module has entered fault mode. Replace the cache backup module.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Warning Cache-Vault microcode update required.
The firmware of disk array controller and that of the cache backup module does not match.
Check if the firmware of disk array controller is supported. In other cases, contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Information Drive Cache settings enabled during rebuild on PD:
Information Drive Cache settings restored after rebuild on PD:
Rebuilding will be executed with the physical drive cache enabled.
Action is not required.
The physical drive cache will be restored to the original after rebuilding. Action is not required.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Information Consistency Check suspended on
VD : {1}
The consistency check has been suspended. Action is not required.
Added in
Ver.8.31-01
Information Consistency Check resumed on
VD : {1}
Information Background Initialization suspended on VD : {1}
Information Background Initialization resumed on VD : {1}
The consistency check has started again. Action is not required.
Added in
Ver.8.31-01
The background initialization has been suspended. Action is not required.
The background initialization has started again. Action is not required.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Information Reconstruction suspended on
VD : {1}
Information Reminder: Consistency Check suspended on VD : {1}
Capacity expansion processing has been suspended. Action is not required.
Added in
Ver.8.31-01
Information Rebuild suspended on PD : {1} Rebuilding has been suspended.
Action is not required.
Information Copyback suspended on PD : {1} Copyback has been suspended.
Action is not required.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Information Reminder: Background
Initialization suspended on VD :
{1}
Reminder: The consistency check has been suspended.
Action is not required.
Reminder: The background initialization has been suspended.
Action is not required.
Added in
Ver.8.31-01
MegaRAID Storage Manager Instruction Manual
Event
ID
Category
416 CTRL
417 CTRL
418 CTRL
419 CTRL
420 CTRL
421 CTRL
423 CTRL
424 CTRL
425 CTRL
426 CTRL
428 CTRL
Level Message Description and required action Remarks
Information Reminder: Reconstruction suspended on VD : {1}
Added in
Ver.8.31-01
Information Reminder: Rebuild suspended on
PD : {1}
Reminder: Rebuild has been suspended. Action is not required.
Added in
Ver.8.31-01
Information Reminder: Copyback suspended on PD : {1}
Information Reminder: Patrol Read suspended
Information Erase aborted on PD : {1}
Reminder: Copyback has been suspended. Action is not required.
Added in
Ver.8.31-01
Reminder: Patrol Read has been suspended. Action is not required.
Added in
Ver.8.31-01
The user has suspended the erase operation.
The original data has been deleted.
Restore the backup data as necessary.
Added in
Ver.8.31-01
Critical Erase failed on PD : {1} (Error
{2})
Reminder: Capacity expansion processing has been suspended.
Action is not required.
Information Erase started on PD : {1}
Information Erase completed on PD : {1}
Information Erase aborted on VD : {1}
Critical Erase failed on VD : {1}
Information Erase started on VD : {1}
The erase operation has stopped.
The physical drive may have failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Restore the backup data as necessary.
The erase operation has started.
After completion of the erase operation, restore the backup data as necessary.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
The erase operation has been completed.
The original data has been deleted.
Restore the backup data as necessary.
The user has suspended the erase operation.
The original data has been deleted.
Restore the backup data.
Added in
Ver.8.31-01
The erase operation has stopped.
The physical drive may have failed.
Contact the sales representative or call maintenance personnel.
Added in
Ver.8.31-01
Restore the backup data as necessary.
The erase operation has started.
After completion of the erase operation, restore the backup data as necessary.
Added in
Ver.8.31-01
5-36 Appendix
MegaRAID Storage Manager Instruction Manual
Event
ID
Category Level Message Description and required action Remarks
429 CTRL
430 CTRL
440 SAS
Information Erase complete on VD : {1}
Information Link speed changed on SAS port
{1} PHY = {2}
The erase operation has been completed.
The original data has been deleted.
Restore the backup data as necessary.
The link speed of SAS port has been changed. Action is not required.
Added in
Ver.8.31-01
Warning Potential leakage during erase on
VD : {1}
The original data may be readable during the erase operation.
After completion of the erase operation, restore the backup data as necessary.
Added in
Ver.8.31-01
Added in
Ver.8.31-01
Added in
Ver.8.31-01
445 CTRL Warning Patrol Read aborted on PD : {1} Patrol Read has stopped.
Action is not required if the user stopped it.
61440 MONITOR Information Monitor has started successfully. The RAID monitor service has started.
Action is not required.
61441 MONITOR Information Monitor has shutdown
61442 MONITOR Warning
NA NA NA successfully
The RAID monitor service has stopped.
Action is not required.
No controllers detected The disk array controller cannot be found.
Check whether a correct device driver is installed
Successful log on to the server You have logged on to the server successfully.
Action is not required.
NA NA NA
NA NA
NA NA
NA
NA
Successful log out from the server
You have logged out from the server.
Action is not required.
Full access denied on the server You have logged on to the server in full access mode.
Action is not required.
Server log cleared The server log has been cleared.
Action is not required.
MegaRAID Storage Manager Instruction Manual
Request sense data
The request sense data shown below is output following <CDB> to the event log.
CDB = xx xx xx
Sense = 0xf0 0x00 0x04 0x00 0x01 0x00 0x00 0x28 0x00 0x00 0x00
0x00 0xc4 0x00 0x00 0x00 0x00 0x00 0x20 0x28 0x00 0x21
0xb0 0x01 0x15 0x02 0x00 0x00 0x00 0x15 0x00 0x78 0x00
0x00 0x00 0x22 0x1f 0x40 0x00 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00
The first three bytes of the <Sense> data are "sense key" that indicates the main error code from the hard disk.
The following table describes each sense key:
Sense key Name Description
0x00
0x01
0x02
0x04
No Sense
Recovered
Error
Indicates that there is no particular sense key.
Indicates that the last command was executed successfully with device recovery processing.
Not Ready Indicates that the device is not accessible.
Indicates that an uncorrectable error was detected due to a media defect or stored-data error.
Hardware
Error
Indicates that an uncorrectable hardware error was detected during execution of command or self-diagnosis in the device.
Indicates that an invalid value was detected in the CDB or parameter transferred by the designation in the command.
0x06 Unit
Attention
Indicates that unit attention condition occurred.
Protect Indicates that violating access was attempted to data area of read/write-protected recording media.
Check Indicates that the write-once device or sequential-access device detected blank area or data end mark during read operation or the write-once device attempted to write data to a non-blank area.
0x09 (Reserved) -
Indicates that the Copy command, Compare command, or
CopyandVerify command abended due to an error in the source device or destination device.
Indicates that the target caused the command to abend. 0x0B Aborted
Command
0x0C Equal Indicates that the Search Data command ended successfully with data search condition Equal met.
Indicates that unwritten data is remaining in the buffer because media data area ended in the device with a buffer.
0x0E Miscompare Indicates that a mismatch was detected in the data compare command.
0x0F (Reserved) -
5-38 Appendix
MegaRAID Storage Manager Instruction Manual
List of services
MSM services are listed below.
Windows
•
MSMFramework
Linux
• msm_profile
• vivaldiframeworkd
• lsi_mrdsnmpd (daemon)
For both Windows and Linux, use the default setting values of MSM service startup.
(Services automatically start during the OS startup by default.)
List of processes
MSM processes are listed below.
Windows:
• cmd.exe
• javaw.exe
• popup.exe
•
VivaldiFramework.exe
Linux:
• sh /usr/local/MegaRAID Storage Manager/Framework/startup.sh
•
../jre/bin/java -classpath ../jre/lib/rt.jar:../jre/lib/jsse.jar:../jre/lib/ jce.jar:mail.jar:Framework.jar -Djava.library.path=.
Framework.FrameworkManager
•
. /bin/sh ./popup
•
/bin/sh /usr/local/MegaRAID Storage Manager/startupui.sh *
1
•
../jre/bin/java -classpath .:Popup.jar:../GUI.jar Popup.Communicator ajsgyqkj=71244
•
./jre/bin/java -Duser.country=US -Duser.language=en -DVENUS=true
-DGUI_VERSION=11.08.03.00 -classpath
.:GUI.jar:monitorgui.jar:DebugLog.jar:log4j-1.2.15.jar:jaxen-
1.1.jar:jdom-1.1.jar GUI.VivaldiStartupDialog ajsgyqkj=71244 *
1
•
/usr/sbin/lsi_mrdsnmpagent -c /etc/snmp/snmpd.conf
(When SNMP is enabled)
MegaRAID Storage Manager Instruction Manual
Port number
This section explains the port numbers used by MSM.
•
Port numbers
3071: protocol: TCP and UDP
5571: protocol: UID
49152 to 65535: Dynamic and/or Private Ports
Although Port 5571 is not used by this version of MSM but is reserved for MSM. If you introduce the network security, register the port number as an exception.
Do not use the MSM ports for other applications.
System log (in Linux)
This section explains how events are stored in different syslog files for Linux.
Linux syslog event output
To store events in different files based on their levels, add the lines listed below to one of the following log setting files:
For Red Hat Enterprise Linux 6: /etc/rsyslog.conf
For Red Hat Enterprise Linux 5: /etc/syslog.conf
The lines to be added are as follows:
• user.=info /var/log/user.info
• user.=crit /var/log/user.crit
• user.=warning /var/log/user.warning
• user.=emerg /var/log/user.emerg
Level
The correspondence between the above levels and the event levels used in this manual is as follows:
•
Information = info
•
Critical = crit
•
Warning = warning
•
Fatal = emerg
5-40 Appendix
MegaRAID Storage Manager Instruction Manual
MegaRAID Storage Manager Instruction Manual
MegaRAID Storage Manager Instruction Manual
Hitachi Data Systems
Corporate Headquarters
2845 Lafayette Street
Santa Clara, California 95050-2639
U.S.A. www.hds.com
Regional Contact Information
Americas
+1 408 970 1000 [email protected]
Europe, Middle East, and Africa
+44 (0) 1753 618000 [email protected]
Asia Pacific
+852 3189 7900 [email protected]
MK-90CRC010-01
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 1 Hitachi Compute Rack Series MegaRAID Storage Manager Instruction Manual
- 7 Preface
- 8 Intended Audience
- 8 Product Version
- 8 Release Notes
- 8 Document Revision Level
- 8 Document Organization
- 8 Abbreviation of Disk Array Management Utility
- 9 Version of MegaRAID Storage Manager
- 10 Document Conventions
- 11 Getting Help
- 11 Comments
- 13 Usage Precautions
- 14 RAID utility
- 14 MegaRAID Storage Manager
- 17 Restrictions on use of MegaRAID Storage Manager
- 17 With Remote monitoring
- 17 With Centralized management by Linux
- 17 When introducing network security
- 17 IP addresses
- 19 Changing an IP address, enabling or disabling a network, or connecting or disconnecting a TP line
- 21 MegaRAID Storage Manager of management PC and management server
- 22 System environment required for MegaRAID Storage Manager
- 23 LSI Software RAID
- 25 MegaRAID Storage Manager
- 26 Installing and removing MegaRAID Storage Manager
- 26 Installation
- 28 Required libraries in Red Hat Enterprise Linux 6 (64-bit x86_64) environment
- 29 Windows: Installation in the standalone format (Recommended format)
- 39 Windows: Installation in complete format (Installation on a management server or managed server)
- 48 Windows: Installation in client format (Installation on a management PC)
- 56 Linux: Installation in the standalone format (Recommended format)
- 62 Linux: Installation in the complete format(Installation on a management server or managed server)
- 68 Linux: Installation in the client format (Installation on a management PC)
- 74 Uninstallation
- 74 Uninstalling the Windows edition
- 77 Uninstalling the Linux edition
- 80 Activating MegaRAID Storage Manager
- 80 Activating MSM
- 84 Starting MSM (for remote connection)
- 88 Displaying multiple connected servers
- 91 Switching servers to be displayed (for remote connection)
- 94 Exiting MegaRAID Storage Manager
- 95 Initialization
- 96 Screen configuration and descriptions of MegaRAID Storage Manager
- 97 Menus
- 105 Window icons
- 106 Functions of MegaRAID Storage Manager
- 109 Display of properties
- 123 Creating new virtual drives
- 137 Changing the setting of virtual drive(s)
- 140 Initializing virtual drive(s)
- 142 Consistency check of virtual drives
- 149 Configuring a hot spare
- 149 About hot spare
- 151 Configuring a global hot spare
- 152 Configuring a dedicated hot spare
- 155 Configuring a dedicated hot spare when creating a virtual drive
- 159 Expansing virtual drive capacity
- 163 Deleting virtual drive(s)
- 164 Changing write cache
- 167 Blinking LEDs
- 169 Diagnosing cache back module (BBU)
- 172 SMART copyback
- 177 Rescan
- 177 Event reference
- 181 Displaying task progress and terminating a task
- 185 Setting network security exceptions
- 195 Setting event notification
- 203 Setting Patrol Read
- 208 Restrictions
- 211 Precautions
- 214 Replacing a physical drive
- 214 With a hot spare
- 215 Without a hot spare
- 217 Operation of Disk Arrays
- 218 Daily operation
- 218 Backup
- 218 Periodical consistency check of LSI Software RAID virtual drives
- 219 Collecting/Operating event logs
- 221 In the Event of a Fault
- 222 Troubleshooting procedures
- 222 Checking the status of both disk array and physical drives
- 222 Checking events
- 223 Data backup
- 223 Contacting the maintenance company
- 225 Appendix
- 226 Estimate of various processing time
- 230 Events list
- 232 Actions for event notification
- 233 List of MegaRAID Storage Manager events
- 262 Request sense data
- 263 List of services
- 263 List of processes
- 264 Port number
- 264 System log (in Linux)