Pillar Axiom: How to remove incomplete PdsCompCmReadBrickConsole Tasks

Asset ID:	1-71-2075537.1
Update Date:	2018-04-25
Keywords:

Solution Type Technical Instruction Sure

Solution 2075537.1 : Pillar Axiom: How to remove incomplete PdsCompCmReadBrickConsole Tasks

Applies to:

Pillar Axiom 600 Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

This document provides the necessary steps to address incomplete PdsCompCmReadBrickConsole tasks under the Pillar Axiom Storage Services Manager (GUI) for R5.

Solution

Users might see under the Tasks window (after clicking on the Tasks button on the bottom right of the Graphical User Interface) one or multiple PdsCompCmReadBrickConsole tasks not progressing/completing after a while.

Example 1:

First example of PdsCompCmReadBrickConsole tasks

Example 2:

2nd example of PdsCompCmReadBrickConsole tasks

The error is from a null pointer on the Pilot Software that is created after accessing the brick console via the GUI. It is very likely to be observed after running Support tools like SMART_DATA_R5.exe and Check_Bad_Blocks_R5.exe as they use commands to access the brick console.

This is a cosmetic issue and it can be safely ignored until the next upgrade: during an upgrade, the user needs to tick the "Ignore Current Requests" box otherwise the upgrade will fail if the task(s) are listed. The tasks will be cleared after the upgrade.

Another workaround is to perform a Pilot Failover using PilotFailover_R5.exe (attached to this Knowledge article) to clear these tasks if necessary.

References

<BUG:17329171> - STALLED PDSCOMPCMREADBRICKCONSOLE TASK

Attachments

This solution has no attachment