Check Consistency fails:
Is virtual disk "Degraded"?
Replace the failed hard disk drive with new one, then perform Rebuild.
→
Is RAID0 configured for virtual disk?
RAID0 has no data redundancy, therefore, Check Consistency is disabled in the
→
RAID0 configuration.
Cannot set Write-Back for cache mode:
The current cache mode of RAID controller is displayed on [Virtual Disks] -
→
[Properties] - [Policies] - "Write". If additional battery is faulty, is not connected,
or insufficiently charged, the cache mode is changed to "WThru (Write Through)"
even if you specify "WBack (Write Back)". See Chapter 4 for details.
Event ID129:
The following message appears on Windows Event Log.
Source:
Event ID:
Type:
Description:
Retry by OS has succeeded. It is not the problem in operating the system.
→
Event ID317:
The following message may be registered in RAID log in Universal RAID Utility and OS
log (Event Log or Windows, syslog of Linux).
Source:
Event ID:
Type:
Description:
Single-shot message indicates the successful retry even if the message above is
→
registered. If this message is repeatedly registered, physical device may be faulty.
Contact your service representative.
Access LED flashes:
Access LED flashes frequently even while the hard disk drive is not accessed.
The Access LED flashes if Patrol Read is running. With SATA hard disk drive, the
→
LED may stay on.
msas2k3
129
Warning
Information about Event ID (129) (Source: msas2k3) is not found.
-----
Raidsrv
317 (8000013D)
Warning
<RU0317>[CTRL: %1 PD:%2(%3) %4 %5] An error of warning level
occurred on physical device.
Error code: %6
Troubleshooting 8-41