Asus DS300j G2 Series User Manual page 225

Reported Event
Battery
Battery is inserted
Battery charging has failed
Battery reconditioning has started
Battery reconditioning has been terminated
The write policy of writeback logical drive
switched from writeback to writethru
The write policy of writeback logical drive
switched from writethru to writeback
Battery is charging in high temperature
Battery cannot function with the enclosure or
with the attached battery board
Logical drive writeback cache maybe enabled
without battery support
Battery is fully charged
Battery is not present
Battery is not accessible
BBU
BBU flushing has started
BBU flushing has ended
BBU flushing has failed
Blade Server
Blade Server Inserted
Blade Server Removed
Cache
Not available
Controller
The controller parameter(s) are changed by
user
The controller is reset by Watch Dog timer
The controller has new crash information
The controller's heart beat has started
The controller's heart beat has stopped
The partner controller's heart beat has started
The partner controller's heart beat has
stopped
The partner controller's heart beat has
skipped
219
Corrective Action
No action is required.
Replace the battery.
No action is required.
Replace the battery.
Check the event log to see whether battery is re-
conditioning.
No action is required.
Monitor the condition. Contact Tech Support if the
problem persists.
Wrong battery installed. Contact Tech Support for
assistance.
No action required.
Install a battery or verify that the battery is properly
connected.
Connect the battery properly or replace the battery.
No action is required.
Contact Tech Support if the condition persists.
No action is required.
Contact Tech Support.
No action is required.
Result of a firmware update. If the condition persists,
replace the controller.
Contact Tech Support.
No action is required.
The controller's main scheduler has frozen
Controller has entered maintenance mode
since configured physical disk seen by
partner controller is not seen here
Controller has entered maintenance mode due
to mismatch of physical disks types
Controller has entered maintenance mode due
to mismatch of physical disk WWN
Controller has entered maintenance mode due
to mismatch of SATA Disks
Controller has entered maintenance mode due
to mismatch of Disk IDs
Controller has entered maintenance mode
since no physical disks are seen as seen by
Partner controller
Controller is started
Controller is set to Active Mode
Controller is set to Standby Mode
Controller Failed Over as partner is removed
Controller Failed Over as heart beat stopped
Controller Firmware mismatch with that of the
partner controller
Controller set to Maintenance Mode because
of hardware mismatch with partner (controller)
Controller set to Maintenance Mode because
of firmware mismatch with partner controller
Controller set to Maintenance Mode because
Firmware is flashing in the partner controller
Controller set to Maintenance Mode because
of flash image version mismatch with partner
(controller)
Controller has been set to Maintenance mode
because there is a mismatch in the Controller
Model or Hardware version with that of the
partner controller
Controller has been set to Maintenance mode
because there is a mismatch in the memory
size with that of the partner controller
Partner Controller has entered maintenance
mode to protect user data since one of the
configured physical drives was disconnected
in the partner controller
DS300f G2 Series User Manual
Contact Tech Support if the condition persists.
Verify that all SATA drives have an SAS-to-SATA
adapter installed.
Check and correct SAS cabling and connections as
needed.
Update to the latest firmware. If the condition persists,
replace the controller.
Check and correct data cabling and connections as
needed.
No action is required.
Verify that the partner controller is properly installed
and all cables are connected.
Auto Firmware synchronization upgrades or
downgrades the firmware.
Compare controller types and amount of memory
installed. Correct or update as needed.
Update this controller to the same firmware version as
the partner controller.
Exit out of Maintenance mode after firmware flashing
is complete.
Update this controller to the same flash image version
as the partner controller.
Replace this controller with the same Model and
Hardware version as the partner controller.
Replace this controller's memory with the same
memory size as the partner controller
Check and correct cable connections to external JBOD
enclosures. Rebuild any critical logical drives. Back up
array data. Replace the physical drive. Bring controller
out of maintenance mode.