CLI Guide

CAUTION:
1. Do not use the trust command when the storage system is unstable. For example, if
there are many power or topology-change events.
2. The trust command can be run on a quarantined-offline or offline disk group. In
many cases the disk group will be automatically dequarantined. If you cannot resolve
the issue that caused the disk to become quarantined such that it is automatically
dequarantined, and if the trust operation is applicable to your situation, then proceed
to trust.
NOTE: The best practice is to dequarantine the disk group and then proceed to trust the
offline disk group. If the dequarantine command fails then contact technical support for
assistance.
CAUTION: Performing trust on a quarantined-offline disk group can cause data
corruption because it will bring a disk with stale data back into the disk group.
3. Never update controller-module, expansion-module, or disk firmware when the disk
group is offline.
4. Never clear unwritten data cache when a disk group is offline.
5. Do not use the trust command on a disk group that failed during disk-group
expansion.
6. Do not use the trust command on a disk group with status CRIT. Instead, add spares
and let the system reconstruct the disk group.
The trust command must be used in CLI console mode.Steps for running the trust command:
1. Disable background scrub of disks and disk group to avoid running scrubs automatically.
2. Identify the cause for the disk group becoming offline.
3. If an external issue (power, cabling, and so forth) caused the disk group to fail, fix the external
issue before continuing to the next step.
4. Disable host access to the failed disk group. In a single-controller configuration, disconnect the
host-port cables. In a dual-controller configuration:
a. Determine the owning controller of the failed disk group.
b. As a precautionary measure, remove the host-port cables of the owning controller of the
offline disk grou.p
5. Unseat the spare disks associated with the disk group to prevent reconstruction.
CAUTION:
It is recommended to avoid reconstruction after using the trust command.
Reconstruction causes heavy usage of disks that were already reporting errors. This
usage could cause the disks to fail during reconstruction, which can cause data to be
unrecoverable.
6. Enable the trust command.
7. Run the trust command on the disk group.
8. If the trust command determines that it would be unsafe to proceed, it will fail. If this happens
you can either:
● Contact Support for further assistance. This is recommended.
● Proceed by re-enabling trust and running trust with the unsafe parameter. This is not
recommended because in most cases it will result in an unstable disk group with data
corruption.
After running the trust command
1. Reinsert the host-port cables.
2. Perform a complete backup of the disk group.
3. Delete the disk group.
4. Replace the failed disks with new disks.
5. Re-create the disk group.
6. Restore the data from the backup performed in step 2.
7. Restore original disk-group ownership.
8. Re-enable background scrub operations.
Minimum role
manage
276 Alphabetical list of commands