
7.
RAID 1 STORAGE
The system is delivered with a hardware RAID 1 implementation, which consists of one
controller on the motherboard and 2 450GB SAS-disks. These two disks make, together
one 450GB storage device. With RAID 1, a storage device contains 2 disks, which are
identical mirrored. Thus when one disk fails, then the other disk takes over the control of
the data.
The hardware RAID controller offers a storage device to the machine. This means that
the operating system (Linux) doesn’t see what physically is “behind” the controller. Thus it
only offers about 450GB of storage. Thus this means that the operating system: Linux,
can’t see what the real status is of the physical disks.
Although the utility: “kinfocenter”, supplied with RHEL distribution, is able to show the
disks behind the disk/raid-controller, it cannot see the status and the configuration of the
volume.
[pg@a217 pg]~> kinfocenter
7.1.
sas2ircu
Login as root and check the raid-
status with “sas2ircu”.
[root@a217 ~]# sas2ircu 0 status
LSI Corporation SAS2 IR Configuration Utility.
Version 15.00.00.00 (2012.11.08)
Copyright (c) 2009-2012 LSI Corporation. All rights reserved.
Background command progress status for controller 0...
IR Volume 1
Volume ID : 323
Current operation : None
Volume status : Enabled
Volume state : Optimal
Volume wwid : 0401f828ab027aaa
Physical disk I/Os : Not quiesced
SAS2IRCU: Command STATUS Completed Successfully.
SAS2IRCU: Utility Completed Successfully.
See also:
[root@a217 ~]# sas2ircu
To check the rai
d status periodically automatically, the file “sas2ircu.cron” is executed on
a daily base automatically in the directory /etc/cron.daily by the cron-daemon. Any
“Volume state” unequal to “Optimal” generates an email to the “root”-user. You can fill in
the header of this file any preferred email address:
ADMIN="root"
7.2.
Failing disk
When determined one disk has failed for whatever reason, replace the failed disk with a
disk which is at least as large as the original disk. The disks are hot swappable. Use the
utility: sas2ircu to see the percentage of synchronisation:
[root@a217 ~]# sas2ircu 0 status
See Appendix A to get into the BIOS of the RAID-controller and do the required
managements.