Справочник Пользователя для Acer DAC960PJ
Installation Abort
C-2
DAC960PG and DAC960PJ Installation
During the initialization, if the firmware fails to respond to the BIOS inquiry
within two minutes, the following message displays:
within two minutes, the following message displays:
DAC960P
n
not responding--no drives installed.
The BIOS then inquires the firmware for its version number and other
information, and prints out the following message:
information, and prints out the following message:
DAC960P
n
firmware version x.xx
One or more of the following messages will be displayed if the firmware
reports the following conditions:
reports the following conditions:
Warning: X system drives are offline
Warning: X system drives are critical
Warning: The following SCSI devices are dead--chn
x, tgt y...
No system drives found: None installed
X system drives installed
The BIOS repeats the same process for additional RAID controllers present
in the system. Then it proceeds to boot, if possible, from the first system
drive on the first controller.
in the system. Then it proceeds to boot, if possible, from the first system
drive on the first controller.
Installation Abort
With Firmware 4.x, the installation aborted message is displayed when the
BIOS finds that the configuration of the disk drives, as stored in the
NVRAM and configuration on disk, is different from what it senses at boot
time. When this happens (and a brand new installation is not being
attempted), the cause is often a faulty cable or drive, or a loose connection.
Check all of the connectors, cables, drives, and try to boot. If the error
persists, it most likely indicates a genuine failure and needs to be corrected.
To correct it, boot and run the on-board Mylex Disk Array Configuration
Utility (see Chapter 4). For more information, refer to the RAID EzAssist
Configuration Utility User Reference Guide, available on CD-ROM, or
RAID EzAssist Configuration Utility Quick Configuration Guide.
BIOS finds that the configuration of the disk drives, as stored in the
NVRAM and configuration on disk, is different from what it senses at boot
time. When this happens (and a brand new installation is not being
attempted), the cause is often a faulty cable or drive, or a loose connection.
Check all of the connectors, cables, drives, and try to boot. If the error
persists, it most likely indicates a genuine failure and needs to be corrected.
To correct it, boot and run the on-board Mylex Disk Array Configuration
Utility (see Chapter 4). For more information, refer to the RAID EzAssist
Configuration Utility User Reference Guide, available on CD-ROM, or
RAID EzAssist Configuration Utility Quick Configuration Guide.