Table 120. Upgrade error codes and recommended actions (continued)
Error
Code Explanation Action
019D Check the system health.
1. Use lsnode to check the status of
CTDB and GPFS for the nodes.
Reboot the unhealthy node and wait
for the node to be up again. Then,
again check the health of the node
with lsnode.
2. Contact IBM Remote Technical
Support.
019E Internal error - cluster or node not
provided.
Contact IBM Remote Technical Support.
019F CIM restart failed. Contact IBM Remote Technical Support.
01A0 Failed to reboot. Determine the cause of the failed reboot:
1. Check console of system if able. See if
the system is hung in BIOs or during
boot.
2. Check cabling of system.
3. Check light path diagnostic for error
indications. .
4. Reboot the system from console and
restart upgrade.
5. Contact IBM Remote Technical
Support.
01A1 Internal upgrade error. Contact IBM Remote Technical Support.
01A2 A GPFS command has failed. Contact IBM Remote Technical Support.
01A3 Unable to uninstall CNCSM
callbacks.
Contact IBM Remote Technical Support.
01A4 Unable to stop backup jobs.
1. Check the status of the backups by
typing lsjobstatus -j backup.
2. Attempt to stop backups by typing
stopbackup --all.
3. Contact IBM Remote Technical
Support.
01A5 Backup cron jobs are running.
1. Check the condition of tasks by
typing lstask -t cron.
2. Attempt to remove the backup by
typing rmtask StartBackupTSM.
3. Contact IBM Remote Technical
Support.
01A6 Unable to install CNCSM callbacks. Contact IBM Remote Technical Support.
01A7 Internal vital product data (VPD)
error.
Contact IBM Remote Technical Support.
01A8 Check the health of management
service.
1. Attempt to start the management
service with startmgtsrv on active
management node
2. Contact IBM Remote Technical
Support.
420 Storwize V7000 Unified: Problem Determination Guide 2073-720