The following screen is an example of what you see during an upgrade on the server console when a cluster-enabled volume is offline or a cluster node just failed and the volume is in the process of failing over to another node in the cluster.
If the cluster-enabled volume is offline, bring the volume online and retry the upgrade process.
If the cluster node just failed and the volume is in the process failing over to another node in the cluster, wait for the failover to complete and retry the upgrade process.
The following screen is an example of what you see on the server console when the Pool objects for the volumes listed in the error message have not yet been added to NDS®.
Pool objects not being added to NDS are generally related to three causes:
If you suspect this is the cause, wait and retry the upgrade process.
If you suspect this is the cause, run NSS /PoolRebuild on the volume or volumes that failed. This command rebuilds the volume and creates the pool associated with the volume.
After running NSS /PoolRebuild, add the newly created pool to NDS via the Media tab in ConsoleOne®.
If you suspect this is the cause, go to NDS and Time Synchronization Problems to check NDS health and time synchronization.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.