HNAS performance perceived to be poor

To get started on troubleshooting these issues please refer to these knowledgebase articles:

• What Are Common Causes of Performance Problems in HNAS Systems
• What Information Do I Need to Gather to Allow GSC to Diagnose an HNAS Performance Problem

HNAS perceived to be non-responsive/hung

The procedure for what diagnostic data etc. needs to be gathered to give us the best chance of diagnosing a HNAS perceived to be non-responsive/hung is documented in the following knowledgebase article:

• What Information Do I Need to Gather to Allow GSC to Diagnose a Hung HNAS System

HNAS node has reset or repeatedly resetting

If the node has only been rebooted once (due to the reset) then a standard set of diagnostics should be sufficient to begin diagnosis of the problem.  The procedure for collecting diagnostics is documented in the manual or at the following knowledgebase article:

• Hitachi NAS (HNAS) Platform Data Collection

If the HNAS has since been rebooted (or has reset more than once) then we will also need historical logs for the diagnosis.  The procedure for collecting historical logs is documented in the following knowledgebase article:

• How To Collect Historical Logs from HNAS

If the HNAS node is repeatedly resetting ("boot-looping") then the following knowledgebase article describes what information to gather in this case:

• What Information Do I Need to Gather to Allow GSC to Diagnose a HNAS Boot Loop

Once you have the diagnostic data required open a case and upload the gathered diagnostic data to TUF against the case.