Acer AcceleRAID 352 用户手册
AcceleRAID 352 Error Messages
Manual No. 775051
C-3
persists, it most likely indicates a genuine failure and needs to be corrected.
To correct it, boot and run the on-board BIOS Configuration Utility, RAID
EzAssist (see Chapter 3). For more information, refer to the RAID EzAssist
Configuration Utility User Reference Guide or RAID EzAssist Configuration
Utility Quick Configuration Guide.
To correct it, boot and run the on-board BIOS Configuration Utility, RAID
EzAssist (see Chapter 3). For more information, refer to the RAID EzAssist
Configuration Utility User Reference Guide or RAID EzAssist Configuration
Utility Quick Configuration Guide.
With Firmware 6.x, if the BIOS displays a mismatch in the Configuration on
Disk (COD) on all drives, then there will be an “install abort”-- no drives
will be installed. Normally this error will not be displayed. If it is, boot and
run RAID EzAssist, the on-board Mylex Disk Array Configuration Utility
(see Chapter 3) to recover from the error. For more information, refer to the
RAID EzAssist Configuration Utility User Reference Guide or RAID
EzAssist Configuration Utility Quick Configuration Guide.
Disk (COD) on all drives, then there will be an “install abort”-- no drives
will be installed. Normally this error will not be displayed. If it is, boot and
run RAID EzAssist, the on-board Mylex Disk Array Configuration Utility
(see Chapter 3) to recover from the error. For more information, refer to the
RAID EzAssist Configuration Utility User Reference Guide or RAID
EzAssist Configuration Utility Quick Configuration Guide.
System Reboot or Power Down
Status messages may also be available from LED indicators connected to the
controller. The Cache Dirty indicator is especially important when preparing
to power-down the system.
controller. The Cache Dirty indicator is especially important when preparing
to power-down the system.
The AcceleRAID 352 controller is a caching controller with 32MB, 64MB,
or 128MB of cache memory, data may still be in the cache waiting to be
written to the disk drives, when the system reports that a write command was
completed. It is very important to make sure that all data is written to the
disk before rebooting or powering down the system, or you may lose data. It
is always a good idea to wait for 60 seconds or until all activity stops before
resetting or rebooting the system.
or 128MB of cache memory, data may still be in the cache waiting to be
written to the disk drives, when the system reports that a write command was
completed. It is very important to make sure that all data is written to the
disk before rebooting or powering down the system, or you may lose data. It
is always a good idea to wait for 60 seconds or until all activity stops before
resetting or rebooting the system.