Oracle E5-APP-B Alarms And Maintenance page 100

Alarms and Maintenance
md1 : active raid1 sda3[0] sdb3[1]
262080 blocks super 1.0 [2/2] [UU]
md3 : active raid1 sdb1[1] sda1[0]
442224640 blocks super 1.1 [2/2] [UU]
bitmap: 1/4 pages [4KB], 65536KB chunk
unused devices: <none>
• On a system where one of the drive modules is healthy and one is corrupt, only the healthy
drive module is displayed:
sudo cat /proc/mdstat
$
Personalities : [raid1]
md2 : active raid1 sdb2[1]
26198016 blocks super 1.1 [2/1] [_U]
bitmap: 1/1 pages [4KB], 65536KB chunk
md1 : active raid1 sdb3[1]
262080 blocks super 1.0 [2/1] [_U]
md3 : active raid1 sdb1[1]
442224640 blocks super 1.1 [2/1] [_U]
bitmap: 3/4 pages [12KB], 65536KB chunk
unused devices: <none>
In this example, the mdstat output shows only sdb, which indicates that sda is corrupt.
3. Log in as admusr and run the failDisk command to mark the appropriate drive module to be
replaced.
If you are replacing a healthy drive module with a higher capacity drive module, the force option
is required. The force option is not required when replacing a corrupt drive module.
• Replacing a corrupt drive module:
$ sudo /usr/TKLC/plat/sbin/failDisk <disk to be removed>
For example:
$ sudo /usr/TKLC/plat/sbin/failDisk /dev/sda
• Replacing a healthy drive module with a higher capacity drive module:
$ sudo /usr/TKLC/plat/sbin/failDisk --force <disk to be removed>
For example:
$ sudo /usr/TKLC/plat/sbin/failDisk --force /dev/sda
4. After failDisk runs successfully, remove the drive module assembly.
Removing a Drive Module
See
5. Insert the new drive module assembly.
E76220 Revision 1, July 2016
Assembly.
Field Replaceable Units
100