•Reconnect hdisk0, close the casing, and turn the key to normal mode.
•Power on NodeF then verify that the rootvg logical volumes are no longer stale (lsvg
6.2.4.2 7135 Disk Failure
Perform the following steps in the event of a disk failure:
•Check, by way of the verification commands, that all the Nodes in the cluster are up and running.
•Optional: Prune the error log on NodeF (errclear 0).
•Monitor cluster logfiles on NodeT if HACMP has been customized to monitor 7135 disk failures.
•Mark a shared disk failed through smit ( smit raidiant; RAIDiant Disk
Array Manager
•The amber light on the front of the 7135 comes on, and can also be seen in SMIT (smit raidiant; RAIDiant Disk Array Manager
•Verify that all sharedvg file systems and paging spaces are accessible ( df and lsps
•If using RAID5 with Hot Spare, verify that reconstruction has completed to the Hot Spare, then
•If using RAID5 without Hot Spare, mark the failed disk Optimal (smit raidiant; RAIDiant Disk Array Manager
•Verify that the reconstruction has completed ( smit raidiant;RAIDiant Disk Array Manager
•Verify that all sharedvg file systems and paging spaces are accessible (df and lsps
6.2.4.3 Mirrored 7133 Disk Failure
•Check, by way of the verification commands, that all the Nodes in the cluster are up and running.
•Optional: Prune the error log on NodeF (errclear 0).