Content
Question
What Information Do I Need to Gather to Allow GSC to Diagnose a HNAS Boot Loop?
Environment
- Hitachi Network Attached Storage (HNAS)
- 3100/3200
- 3080/3090
- 4000 series
- 5000 series
Answer
If a HNAS is stuck in a "boot loop" where it completes so far through the startup process and then keeps resetting then we will require as much of the following information as possible:
- A set of HNAS diagnostics for the node (if it stays up long enough for them to be downloaded.)
- Capture the output of the serial console port for several of the loops.
- If the system is a HNAS 3100/3200 then this information will be required for all three boards:
- NIM
- FSA/FSX
- SIM
- For the FSA/FSX and SIM a special dongle is required to connect to the console port which will have to be shipped to site.
- If the system is a HNAS 3080/3090 or 4000 series:
- You can also connect a monitor to the console video port. Obviously this doesn't allow you to easily capture output except perhaps using a camera phone or similar.
- If the system is a HNAS 3100/3200 then this information will be required for all three boards:
- Additionally for 3080/3090 or 4000 series:
- The output of nas-getlogs.
Customer Article
An archive of the debug log directory on the impacted node.
If you have the choice, capturing via session logging serial terminal program is the best option since this allows cutting and pasting console output as-is to search for defects and thus is less prone to error/more successful.
CXone Metadata
Tags: Diagnosis,Q&A,boot loop
PageID: 8436