System information

Troubleshooting
6-1
Chapter 6: Troubleshooting
6.1 General Guidelines
When you encounter issues, the most essential troubleshooting is to check the event log of your RAID system and carry
out the suggested actions offered in the Appendix D. In addition, you may need to check the system log of the operating
system at your host computers.
Because there are a wide variety of hardware and software combinations, use the following checklist for problem
determination:
• Check all cables to make sure they are connected properly
• Check all hardware units are powered on and working properly
• Check any recent changes in hardware, software, or configurations
• Verify that the latest version of firmware and software are used
• Verify that the latest version of BIOS and device driver of HBA are used
• Verify that the operating systems, HBAs, switches, transceivers, and hard disks are in the compatibility list
• Check how to reproduce the problems
Before you call support, please collect the related information above to assist the support staff in identifying the problems.
It is also required to acquire the following three log files:
(1) RAID system user-level event log in human-readable form (.csv or .txt).
(2) RAID system diagnostic-level event log (.bin).
(3) the log file at operating system.
6.2 Beeper
When the Beeper Control is set to On (see 2.9.5 Miscellaneous on page 2-47), the system will turn on the beeper
alarm if one of the following occurs. If the user mutes the beeper via CLI, LCD, or GUI, the system temporarily mutes the
beeper until a new failure or error occurs.
• Voltage failure or error
• Power supply failure or error
• Fan failure or error
• Temperature failure or error
• BBM failure or error (when BBM is connected)
• Disk SMART warning
• Disk bad block over threshold warning
• Disk group with degraded logical disk and no disk for rebuilding
• Disk group with faulty logical disks
• UPS failure or error (when UPS control is on, see 2.9.4 UPS on page 2-47)
• Controller failure or removed
• Dual controllers fail to boot up because of configuration conflict
• Controller failback cannot proceed
Note
The .bin log file is stored on hard disks, so please keep your hard disks in the system when
downloading the log file. For redundant-controller systems, you’re required to download the .bin
log file for each controller.