Table 120. Upgrade error codes and recommended actions (continued)
Error
Code Explanation Action
01D3 Could not determine if backups are
running.
1. Attempt to stop backups.
2. Type lsjobstatus -j backup;echo $?.
If the return code is 0, start the
upgrade again.
3. If the return code is any other
number, contact IBM Remote
Technical Support.
01D5 Storwize V7000
stalled_non_redundant.
Refer to Storwize V7000 documentation.
01D6 Storwize V7000 System stalled. Refer to Storwize V7000 documentation.
01D8 CTDB cluster is unhealthy.
1. See “Checking CTDB health” on page
187.
2. Use lshealth or RAS procedures to
determine unhealthy components.
3. Contact IBM Remote Technical
Support.
01DA GPFS system is unhealthy.
1. See “Checking the GPFS file system
mount on each file module” on page
189.
2. Use lsnode -r to confirm GPFS is
unhealthy. If node GPFS is healthy,
restart the upgrade.
3. Contact IBM Remote Technical
Support.
01DB Failed to stop performance center. Contact IBM Remote Technical Support.
01DC Failed to configure performance
center.
Contact IBM Remote Technical Support.
01DD Failed to start performance center. Contact IBM Remote Technical Support.
01DE Unable to communicate with
passive management node.
1. Ensure that the active mgmt node can
communicate with the passive
management node before restarting
the upgrade.
2. Contact IBM Remote Technical
Support.
01DF Upgrade must be resumed from the
other management node.
Restart upgrade from other management
node. This might require that a failover
be issued first.
01E0 HSM upgrade failed. Contact IBM Remote Technical Support.
01E1 mmchconfig Failed Contact IBM Remote Technical Support.
01E2 mmauth Failed Contact IBM Remote Technical Support.
01E3 mmlsfs Failed Contact IBM Remote Technical Support.
01E3 mmchfs Failed Contact IBM Remote Technical Support.
01E4 Disable HSM failed Contact IBM Remote Technical Support.
01E5 Enable HSM failed Contact IBM Remote Technical Support.
424 Storwize V7000 Unified: Problem Determination Guide 2073-720