Accusys ExaRAID A16U-IS - Manual (Page 36)

Accusys A16R/A16U-IS
34
• 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.
• Controller failure or removed.
• Dual controllers fail to boot up because of configuration conflict.
• Controller failback cannot proceed.
Solutions
See the table below for the solutions for the most common problems.
Problem Cause Solution
Hard disks cannot be
recognized by the
RAID controller.
If a hard disk cannot be
ready within a specific period
of time during the
initialization, the RAID control-
ler will force the hard disks
enter faulty state and you
cannot see any model
information of hard disks.
To ensure hard disks have enough
time for power-on, you may extend
the delay time when boot-up of the
RAID controller.
Hard disks are offline
unexpected.
Internal component failure or
reserved space for meta-
data (RAID configurations)
can not be written.
1. Use SMART check or DST
(Device Self-Test) to test the hard
disks in question.
2. Check the number of bad blocks
and warning events reported by
the RAID controller.
Exceptional hard
disks behaviors.
Hardware is not setup
properly.
Adjust hard disk settings such as:
• Extend Disk I/O Timeout to
accommodate slow disk operation.
• Increase Disk I/O Retry Time to try
I/O more times before giving up.
• Reduce Transfer Speed to miti-
gate bad signal quality of disks.
• Disable I/O Queue to avoid
problematic NCQ support of disks.
• Disable Disk Standby Mode to
avoid problematic sleep support of
disks.
• Extend Disk Access Delay Time to
allow longer time for disk spin-up.