Recovering From Offline Vdisks Using The Cli; What To Check After Running The System Recovery - IBM Storwize V7000 Unified Problem Determination Manual

If any errors are logged in the error log after the system recovery procedure
completes, use the fix procedures to resolve these errors, especially the errors
related to offline arrays.
If the recovery completes with offline volumes, go to "Recovering from offline
VDisks using the CLI."
After performing the storage system recovery procedure, contact IBM support for
assistance with recovering the file modules, so access to the file systems can be
restored.

Recovering from offline VDisks using the CLI

If a recovery procedure (T3 procedure) completes with offline volumes, you can
use the command-line interface (CLI) to access the volumes.
About this task
If you have performed the recovery procedure, and it has completed successfully
but there are offline volumes, you can perform the following steps to bring the
volumes back online. Any volumes that are offline and are not thin-provisioned
volumes are offline because of the loss of write-cache data during the event that
led both nodes to lose their hardened data. These volumes might need additional
recovery steps after the volume is brought back online.
Note: If you encounter errors in the error log after running the recovery procedure
that are related to offline arrays, use the fix procedures to resolve the offline array
errors before fixing the offline volume (VDisk) errors.
Example
Perform the following steps to recover an offline volume after the recovery
procedure has completed:
1. Delete all IBM FlashCopy function mappings and Metro Mirror or Global
Mirror relationships that use the offline volumes.
2. Run the recovervdisk or recovervdiskbysystem command.
You can recover individual volumes by using the recovervdisk command. You
can recover all the volumes in a clustered system by using the
recovervdiskbysystem command.
3. Recreate all FlashCopy mappings and Metro Mirror or Global Mirror
relationships that use the volumes.

What to check after running the system recovery

Several tasks must be performed before you use the system.
The recovery procedure performs a recreation of the old system from the quorum
data. However, some things cannot be restored, such as cached data or system data
managing in-flight I/O. This latter loss of state affects RAID arrays managing
internal storage. The detailed map about where data is out of synchronization has
been lost, meaning that all parity information must be restored, and mirrored pairs
must be brought back into synchronization. Normally this results in either old or
stale data being used, so only writes in flight are affected. However, if the array
had lost redundancy (such as syncing, or degraded or critical RAID status) prior to
the error requiring system recovery, then the situation is more severe. Under this
situation you need to check the internal storage:
Chapter 5. Control enclosure
263