VTrak event log IDs, descriptions, severity, cause and corrective actions.
Updated March 26, 2008
|
ID |
Severity |
Log |
Description |
Cause |
Action |
|
0x00010000 |
major |
ram, nvram, buzzer, popup |
Battery temperature is above the threshold |
Enviroment is too hot or battery may be malfuctioning |
Replace battery or increase air flow |
|
0x00010001 |
info |
ram, nvram, popup |
Battery temperature is normal |
Battery temperature is normal |
No action required |
|
0x00010002 |
warning |
nvram, buzzer, popup |
BBU is not able to retain data in cache memory for more than 72 hrs |
Three possible causes: 1. The battery is drained. 2. The battery is being reconditioned. 3. The combination of battery and host memory is improper |
If the battery is drained or being reconditioned, allow it to recharge normally. If the wrong battery is installed, replace it with the correct one for your system or accept less than 72 hours of retention time |
|
0x00010003 |
info |
ram, popup |
Battery capacity is normal |
Battery capacity is normal |
No action required |
|
0x00010004 |
info |
ram, nvram, popup |
Battery is discharging |
Battery is re-conditioning |
No action is required |
|
0x00010005 |
info |
ram, popup |
Battery is charging |
Battery is charging |
No action is required |
|
0x00010006 |
info |
ram, popup |
Battery reconditioning is completed |
Battery reconditioning is completed |
No action is required. |
|
0x00010007 |
major |
ram, nvram, buzzer, popup |
Battery is malfunctioning |
Battery is malfunctioning |
Try reconditioning again, or replace battery or replace battery charging circuit in fan box |
|
0x00010008 |
info |
ram, nvram, popup |
Battery has been reconditioned successfully |
Battery has been reconditioned |
No action is required |
|
0x00010009 |
major |
ram, nvram, buzzer, popup |
Battery reconditioning has failed |
Battery is malfunctioning |
Replace battery |
|
0x0001000A |
warning |
ram, nvram, buzzer, popup |
Battery is reaching the end of life |
Battery drains too many times |
Replace battery |
|
0x0001000B |
warning |
ram, popup |
Battery is removed |
Battery is removed |
Insert battery back |
|
0x0001000C |
info |
ram, popup |
Battery is inserted |
Battery is inserted |
No action is required |
|
0x0001000D |
warning |
ram, nvram, buzzer, popup |
Battery charging has failed |
Battery is malfuntioning |
Replace battery |
|
0x0001000E |
info |
ram, nvram, popup |
Battery reconditioning has started |
Battery reconditioning started |
No action is required |
|
0x0001000F |
warning |
ram, nvram, popup |
Battery recondition has been terminated |
Probable Battery removal or Battery malfunction |
Replace battery and try again |
|
0x00010011 |
warning |
ram, nvram, popup |
The write policy of writeback logical drive switched from writeback to writethru |
Battery is re-conditioning or battery is malfuntioning |
Check the event log to see whether battery is re-conditioning |
|
0x00010012 |
info |
ram, nvram, popup |
The write policy of writeback logical drive switched from writethru to writeback |
Battery holds the charge that can sustain the power to the DRAM for 72 hours and more |
No action is required |
|
0x00010013 |
warning |
ram, nvram, popup |
Battery is charging in high temperature |
Input cause string here |
Input action string here |
|
0x00010014 |
major |
ram, nvram, popup |
Battery cannot function with the enclosure or with the attached battery board |
Battery and battery board do not belong to this enclosure or battery cannot work with the battery board |
Input action string here |
|
0x00010015 |
info |
ram, nvram, popup |
Logical drive writeback cache maybe enabled w/o battery support |
Users send the command to force the enclosure/system switched from write through to write back mode |
No action is required |
|
0x00010016 |
info |
ram, popup |
Battery is fully charged |
Battery is fully charged |
No action is required |
|
0x00010017 |
warning |
ram, popup |
Battery is not present |
No battery is detected on the controller or cooling unit during boot time |
Install the battery, or check if the battery is properly connected |
|
0x00010018 |
critical |
ram, popup |
Battery is not accessible |
The battery has failed or it is not connected properly |
Connect the battery properly or replace it |
|
0x00020000 |
info |
ram, popup |
Not available |
Input cause string here |
Input action string here |
|
0x00020001 |
info |
ram, popup |
BBU flushing has started |
The system cache flushing is started |
No action is required |
|
0x00020002 |
info |
ram, popup |
BBU flushing has ended |
The system cache flushing is complete |
No action is required |
|
0x00020003 |
critical |
ram, nvram, popup |
BBU flushing has failed |
The system cache flushing is stopped because error |
No action is required |
|
0x00030000 |
info |
ram, popup |
Redundancy check is started |
User started dedundancy check or BGA scheduler started it |
No action required |
|
0x00030001 |
info |
ram, popup |
Redundancy check is completed |
Redundancy check is completed |
No action required |
|
0x00030002 |
info |
ram, popup |
Redundancy check is paused |
User paused it, or BGA scheduler paused it, or other higer priority BGA activity paused it |
No action required |
|
0x00030003 |
info |
ram, popup |
Redundancy check is resumed |
User resumed it, or BGA scheduler resumed it, or other higer priority BGA is completed or stopped, or resumed after reboot |
No action required |
|
0x00030004 |
info |
ram, popup |
Redundancy check is stopped |
User stopped it, or BGA scheduler stopped it, or the logical drive is deleted, or critical, or offline |
No action required |
|
0x00030006 |
critical |
ram, nvram, buzzer, popup |
Redundancy check is aborted due to an internal error |
System resource is not available |
Reduced system load or reboot |
|
0x00030007 |
major |
ram, nvram, buzzer, popup |
Redundancy check encountered inconsistent block(s) |
Temporary hardware malfunction |
Check the data on the specified block(s) in inconsistent block table of the logical drive |
|
0x00030008 |
info |
ram, popup |
Redundancy check task is queued |
Input cause string here |
Input action string here |
|
0x00030009 |
info |
ram, popup |
Redundancy check is in progress |
Input cause string here |
Input action string here |
|
0x0003000A |
info |
ram, popup |
Redundancy check task is stopped internally |
LD is not online |
No action required |
|
0x0003000B |
info |
ram, popup |
Redundancy check is started on unsynchronized logical drive |
The user issued Redundancy check on an unsynchronized logical drive |
No action required |
|
0x00040000 |
info |
ram, popup |
Event logging is enabled |
Event logging enabled |
None |
|
0x00040001 |
info |
ram, popup |
Event logging is disabled |
Event logging disabled |
None |
|
0x00040002 |
info |
ram, nvram, popup |
Event log buffer is cleared in RAM |
Event log buffer cleared |
None |
|
0x00040003 |
info |
ram, nvram, popup |
Event log buffer is cleared in NVRAM |
Event log buffer cleared in NVRAM |
None |
|
0x00040004 |
info |
ram, nvram, popup |
Event log buffer is cleared in MDD |
Event log buffer cleared in MDD |
None |
|
0x00040005 |
info |
ram, nvram, popup |
The system is started |
System has been started |
None |
|
0x00040006 |
info |
ram, nvram, popup |
The system is stopped |
System has been stopped |
None |
|
0x00040007 |
info |
ram, popup |
The controller parameter(s) are changed by user |
The controller parameter(s) are changed by user |
None |
|
0x00040008 |
major |
ram, nvram, popup |
The controller is reset by Watch Dog timer |
The Watch Dog hardware has reset the controller because of problems |
Update to the new firmware. If persisting, replace the controller |
|
0x00040009 |
info |
ram, nvram, popup |
The controller has new crash information |
New crash information is found because of controller crash in the previous boot |
Contact support with the crash information to help analyze the cause of the crash |
|
0x00040010 |
info |
ram, popup |
The controller's heart beat has started |
Partner controller has joined the clique |
None |
|
0x00040011 |
info |
ram, popup |
The controller's heart beat has stopped |
Partner controller has been removed from the clique |
None |
|
0x00040012 |
info |
nvram, popup |
The partner controller's heart beat has started |
Partner controller has joined the clique |
None |
|
0x00040013 |
info |
ram, nvram, popup |
The partner controller's heart beat has stopped |
Partner controller has been removed from the clique |
None |
|
0x00040014 |
warning |
ram, nvram, popup |
The partner controller's heart beat has skipped |
Sequence of heart beat has skipped, heart beat transport may not be reliable |
None |
|
0x00040015 |
warning |
ram, nvram, popup |
The controller's main scheduler has frozen |
There may be hardware or firmware fault |
None |
|
0x00040016 |
warning |
nvram, popup |
Controller has entered maintenance mode since configured physical disk seen by partner controller is not seen here |
Single ported drives may be present |
None |
|
0x00040017 |
warning |
nvram, popup |
Controller has entered maintenance mode due to mismatch of physical disks types |
SAS cabling may not be correct |
None |
|
0x00040018 |
warning |
nvram, popup |
Controller has entered maintenance mode due to mismatch of physical disk WWN |
There may be hardware or firmware fault |
Update to the new firmware. If persisting, replace the controller |
|
0x00040019 |
warning |
nvram, popup |
Controller has entered maintenance mode due to mismatch of SATA Disks |
There may be cabling or hardware or firmware fault |
None |
|
0x00040020 |
warning |
nvram, popup |
Controller has entered maintenance mode due to mismatch of Disk IDs |
There may be SAS cabling or hardware or firmware fault |
None |
|
0x00040021 |
warning |
nvram, popup |
Controller has entered maintenance mode since no physical disks are seen as seen by Partner controller |
There may be SAS cabling hardware or firmware fault |
Fix the SAS cabling if applicable |
|
0x00040022 |
info |
nvram, buzzer, popup |
Controller is started |
Controller is started |
None |
|
0x00040023 |
info |
nvram, popup |
Controller is set to Active Mode |
Controller is set to Active Mode |
None |
|
0x00040024 |
info |
nvram, popup |
Controller is set to Standby Mode |
Controller is set to Standby Mode |
None |
|
0x00040025 |
critical |
ram, nvram, buzzer, popup |
Controller Failed Over as partner is removed |
Controller removed or shutdown by user or is bad |
Check controller if not removed or shutdown by user |
|
0x00040026 |
critical |
ram, nvram, buzzer, popup |
Controller Failed Over as heart beat stopped |
Controller removed or shutdown by user or is bad |
Check controller if not removed or shutdown by user |
|
0x00040027 |
critical |
ram, nvram, buzzer, popup |
Controller set to Maintenance Mode because of hardware mismatch with partner |
Controller hardware is different from that of the partner controller |
Check if this controller is of same Hardware model/configuration as the partner controller |
|
0x00040028 |
critical |
ram, nvram, buzzer, popup |
Controller Firmware mismatch with that of the partner controller |
The Controller Firmware is of different version than the partner controller |
Auto Firmware synchronization will kick in to upgrade or downgrade the firmware |
|
0x00040029 |
critical |
ram, nvram, buzzer, popup |
Controller set to Maintenance Mode because Firmware is flashing in the partner controller |
Controller set to Maintenance Mode because Firmware is flashing in the partner controller |
Exit out of Maintenance mode once Firmware flashing is complete on the partner controller |
|
0x0004002A |
info |
ram, nvram, popup |
Controller failed over to Partner controller for Firmware flashing this controller |
User initated Non Disruptive Firmware flashing has forced the failover |
none |
|
0x0004002B |
critical |
ram, nvram, popup |
Partner Controller was placed on reset during Fail Over processing |
Partner Controller was reset to avoid split brain scenario |
none |
|
0x0004002C |
critical |
ram, nvram, popup |
Controller was placed on reset during Fail Over processing |
Partner Controller was reset to avoid split brain scenario |
none |
|
0x0004002D |
critical |
ram, nvram, popup |
Controller set to Maintenance Mode because of flash image version mismatch with partner |
Controller flash image version is different from that of the partner controller |
Update this controller to the same flash image version as the partner controller |
|
0x0004002E |
critical |
ram, nvram, popup |
Controller was reset as it was not able to join the running partner controller |
The running partner controller is busy or faulty or the communication to it is faulty |
Please check the partner controller and if required replace it |
|
0x00040030 |
critical |
ram, nvram, popup |
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 Controller Model or Hardware version with that of the partner controller |
Replace this controller with the same Model and Hardware version as that of the other partner controller |
|
0x00040031 |
critical |
ram, nvram, popup |
Controller has been set to Maintenance mode because there is a mismatch in the Controller Memory size with that of the partner controller |
Controller has been set to Maintenance mode because there is a mismatch in the Controller Memory size with that of the partner controller |
Replace this controller's memory with the same memory size as that of the other partner controller |
|
0x00040032 |
critical |
nvram, popup |
Partner Controller has entered maintenance mode to protect user data since one of the configured physical drives was disconnected in the partner controller |
A configured physical drive was detected as removed from one of the controllers. The physical drive belongs to an array that has at least one non-redundant or critical logical drive |
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. See product manual for more information |
|
0x00040033 |
major |
ram, nvram, popup |
The controller has reset because it encountered a firmware problem |
The controller has reset because it encountered a firmware problem |
If resets happen frequently, update to new firmware or replace the controller |
|
0x00050000 |
info |
ram, popup |
PSU fan or blower is turned on |
fans or blowers start because either high temperature or power on default |
No action is required |
|
0x00050001 |
info |
ram, nvram, popup |
PSU fan or blower is turned off |
fans or blowers stop because temperature dropped or stopped by users |
No action is required |
|
0x00050002 |
info |
ram, popup |
PSU fan or blower speed is increased |
Either controller or enclosure temperature is above warning threshold |
No action is required |
|
0x00050003 |
info |
ram, popup |
PSU fan or blower speed is decreased |
Both controller and enclosure temperature is below warning threshold |
No action is required |
|
0x00050004 |
major |
ram, nvram, buzzer, popup |
PSU fan or blower is malfunctioning |
PSU fan is malfunctioning |
Replace PSU |
|
0x00050005 |
info |
ram, nvram, popup |
PSU fan or blower is inserted |
PSU fan is inserted |
No action is required |
|
0x00050006 |
warning |
ram, nvram, popup |
PSU fan or blower is removed |
PSU fan is removed |
No action is required |
|
0x00050007 |
info |
ram, nvram, popup |
PSU fan or blower is functioning normally |
PSU fan or blower is functioning normally |
No action is required |
|
0x00050008 |
warning |
ram, nvram, buzzer, popup |
PSU fan or blower is NOT installed |
The firmware does not detect the device existence |
Check fans or blowers |
|
0x00050009 |
warning |
ram, popup |
PSU fan or blower status is unknown |
Can not get information from PSU fan or blower |
If persistent, replace PSU |
|
0x00060000 |
warning |
ram, nvram, buzzer, popup |
SEP is NOT found |
SEP is NOT present or malfuntioning |
Insert or replace SEP hardware |
|
0x00060002 |
info |
ram, popup |
SEP is found |
SEP is present or is functional |
No action is required |
|
0x0006000c |
info |
ram, popup |
JBOD system connected |
JBOD system is detected |
None |
|
0x0006000d |
critical |
ram, nvram, buzzer, popup |
JBOD system either is removed or malfunctioned |
Bad connection or users remove the connection |
Check Expander firmware and connction |
|
0x0006000e |
warning |
ram, nvram, buzzer |
SEP I2C device access failure |
Cannot access SEP I2C device |
None |
|
0x0006000f |
info |
ram, nvram |
SEP I2C device access recovered from failure |
An SEP I2C device access recovered |
If the condition persistents, replace the controller |
|
0x00070000 |
major |
ram, nvram, buzzer, popup |
Host interface controller has detected parity error |
Input cause string here |
Input action string here |
|
0x00070001 |
warning |
ram, buzzer, popup |
Host interface controller has detected data parity error |
Input cause string here |
Input action string here |
|
0x00070002 |
warning |
ram, buzzer, popup |
Host interface controller has detected command parity error |
Input cause string here |
Input action string here |
|
0x00070003 |
info |
ram, popup |
Host interface controller has detected bus reset |
Input cause string here |
Input action string here |
|
0x00070004 |
major |
ram, nvram, buzzer, popup |
Host interface controller has encountered an unrecoverable error |
Input cause string here |
Input action string here |
|
0x00070005 |
warning |
ram, buzzer, popup |
Host interface controller has received "abort task" command |
Input cause string here |
Input action string here |
|
0x00070006 |
warning |
ram, buzzer, popup |
Host interface controller has received "abort task set" command |
Input cause string here |
Input action string here |
|
0x00070007 |
warning |
ram, buzzer, popup |
Host interface controller has received "clear ACA" command |
Input cause string here |
Input action string here |
|
0x00070008 |
warning |
ram, buzzer, popup |
Host interface controller has received "clear task set" command |
Input cause string here |
Input action string here |
|
0x00070009 |
info |
ram, popup |
Host interface controller has received "LUN reset" command |
Input cause string here |
Input action string here |
|
0x0007000A |
warning |
ram, buzzer, popup |
Host interface controller is informed that the initiator has detected an error |
Input cause string here |
Input action string here |
|
0x0007000B |
warning |
ram, buzzer, popup |
Host interface controller has received illegal secondary identification |
Input cause string here |
Input action string here |
|
0x0007000C |
warning |
ram, buzzer, popup |
Host interface controller has received a message parity error |
Input cause string here |
Input action string here |
|
0x0007000D |
info |
ram, popup |
Host interface controller has recieved a bus reboot |
Input cause string here |
Input action string here |
|
0x0007000E |
info |
ram, popup |
Host interface link is up |
Input cause string here |
Input action string here |
|
0x0007000F |
info |
ram, popup |
Host interface link is down |
Input cause string here |
Input action string here |
|
0x00070010 |
warning |
ram, popup |
Host interface controller has encountered an unknown error |
Input cause string here |
Input action string here |
|
0x00070011 |
warning |
ram, popup |
Host interface controller has encountered a system error |
Input cause string here |
Input action string here |
|
0x00070012 |
fatal |
ram, nvram, buzzer, popup |
Host interface controller has encountered a fatal error |
Input cause string here |
Input action string here |
|
0x00070013 |
info |
ram, popup |
Host interface controller settings have changed |
Input cause string here |
Input action string here |
|
0x00070014 |
warning |
ram, popup |
Host interface controller has received "WARM reset" command |
WARM RESET task management function is initiated from initiator, most likely initiator is trying to recover from errors or timeout period expired |
Input action string here |
|
0x00070015 |
warning |
ram, popup |
Host interface controller has received "COLD reset" command |
COLD RESET task management function is initiated from initiator, most likely initiator is trying to recover from errors or timeout period expired |
Input action string here |
|
0x00070060 |
warning |
ram, nvram, buzzer, popup |
Host Interface controller MU handshake failed |
Input cause string here |
Input action string here |
|
0x00070061 |
critical |
ram, nvram, buzzer, popup |
Host Interface controller , HMU has stopped |
Input cause string here |
Input action string here |
|
0x00070062 |
info |
ram, popup |
Host Interface controller , FMU has unloaded |
Input cause string here |
Input action string here |
|
0x00070080 |
info |
ram, popup |
Fibre Channel host interface controller has detected bus reset |
Input cause string here |
Input action string here |
|
0x00070081 |
info |
ram, popup |
Fibre Channel host interface controller has received "LUN reset" command |
Input cause string here |
Input action string here |
|
0x00070082 |
fatal |
ram, nvram, buzzer, popup |
Fibre Channel host interface controller has encountered a fatal error |
Input cause string here |
Input action string here |
|
0x00070083 |
info |
ram, popup |
Fibre Channel host interface controller link is up |
Input cause string here |
Input action string here |
|
0x00070084 |
info |
ram, popup |
Fibre Channel controller link is down |
Input cause string here |
Input action string here |
|
0x00070085 |
info |
ram, popup |
Fibre Channel host interface controller settings have changed |
Input cause string here |
Input action string here |
|
0x000700A0 |
info |
ram, nvram, popup |
SCSI host interface controller settings have changed |
Input cause string here |
no action required |
|
0x000700A6 |
info |
ram, popup |
External bus reset has occurred |
Input cause string here |
Input action string here |
|
0x000700A7 |
info |
ram, popup |
IOC bus reset has occurred |
Input cause string here |
Input action string here |
|
0x000700A8 |
warning |
ram, nvram, popup |
Parity error is detected during command phase |
Input cause string here |
Input action string here |
|
0x000700A9 |
warning |
ram, nvram, popup |
Parity error is detected during message out phase |
Input cause string here |
Input action string here |
|
0x000700AA |
warning |
ram, nvram, popup |
CRC error is detected while receiving CMD information unit |
Input cause string here |
Input action string here |
|
0x000700AB |
warning |
ram, nvram, popup |
Initiator sent message for detecting an error |
Input cause string here |
Input action string here |
|
0x000700AC |
warning |
ram, nvram, popup |
Parity error is detected during Data Out phase |
Input cause string here |
Input action string here |
|
0x000700AD |
warning |
ram, nvram, popup |
CRC error is detected during Data Out phase |
Input cause string here |
Input action string here |
|
0x000700AE |
warning |
ram, nvram, popup |
Unknown priority reason is detected |
Input cause string here |
Input action string here |
|
0x000700C0 |
warning |
ram, nvram, popup |
Zoning permission settings with the expander has been reset to defaults |
NA |
No action required |
|
0x000700C1 |
warning |
ram, nvram, popup |
Zoning expander has been rebooted. |
NA |
No action required |
|
0x000700C2 |
warning |
ram, nvram, popup |
Zoning permission settings with the expander different than expected |
Internal Zoning Permission settings exported by the expander differ from the last known setting with the SCM. |
The valid settings have been updated correctly. |
|
0x00080000 |
info |
ram, nvram, popup |
Logical drive Initialization has started |
Logical drive Initialization was started by User |
None |
|
0x00080001 |
info |
ram, nvram, popup |
Logical drive initialization has completed |
User requested Logical drive initialization has completed |
None |
|
0x00080002 |
info |
ram, nvram, popup |
Logical drive initialization has paused |
Logical drive initialization has paused either internally or by user |
None |
|
0x00080003 |
info |
ram, nvram, popup |
Logical drive initialization has resumed |
Logical drive initialization has resumed internally or by user |
None |
|
0x00080004 |
info |
ram, nvram, popup |
Logical drive initialization has stopped |
Logical drive initialization has been stopped by user |
None |
|
0x00080005 |
warning |
ram, nvram, buzzer, popup |
Logical drive initialization marks the logical drive offline |
Logical drive initialization marks the logical drive offline due to drive errors |
None |
|
0x00080006 |
warning |
ram, nvram, buzzer, popup |
Logical Drive Initialization is aborted due to an internal error |
Logical Drive Initialization has stopped due to an internal error |
None |
|
0x00080007 |
info |
ram, nvram, popup |
Quick Logical drive initialization has started |
Quick Logical drive initialization was started by user |
None |
|
0x00080008 |
info |
ram, nvram, popup |
Quick Logical drive initialization has completed |
User requested Quick Logical drive initialization has completed |
None |
|
0x00080009 |
info |
ram, nvram, popup |
Quick Logical drive initialization has paused |
Quick Logical drive initialization has paused either internally or by user |
None |
|
0x0008000A |
info |
ram, nvram, popup |
Quick Logical drive initialization has resumed |
Quick Logical drive initialization has resumed either internally or by User |
None |
|
0x0008000B |
info |
ram, nvram, popup |
Quick Logical drive initialization has stopped |
Quick Logical drive initialization has been stopped by User |
None |
|
0x0008000C |
warning |
ram, nvram, buzzer, popup |
Quick Logical drive initialization marks the logical drive offline |
Quick Logical drive initialization marks the logical drive offline due to drive errors |
None |
|
0x0008000D |
warning |
ram, nvram, buzzer, popup |
Quick Logical Drive Initialization is aborted due to an internal error |
Quick Logical Drive Initialization has stopped due to an internal error |
None |
|
0x0008000E |
info |
ram, nvram, popup |
Logical Drive Initialization is queued |
Logical Drive Initialization is queued |
None |
|
0x0008000F |
info |
ram, nvram, popup |
Quick Logical Drive Initialization is queued |
Quick Logical Drive Initialization is queued |
None |
|
0x00080010 |
info |
ram, popup |
Logical Drive Initialization is in progress |
Logical Drive Initialization was started by User |
None |
|
0x00090000 |
info |
ram, popup |
A new Logical drive has been created |
A logical drive has been added by the user to the array |
None |
|
0x00090001 |
info |
ram, popup |
Logical drive has been deleted |
A logical drive has been deleted by the user |
None |
|
0x00090002 |
info |
ram, popup |
Logical drive has been placed online |
All the physical drives of the array are online |
None |
|
0x00090003 |
major |
ram, nvram, buzzer, popup |
Logical drive has been placed offline. Possible Data Loss |
One or more of the Physical Drives of the array are Offline |
Check the state of the physical drives, replace any bad drives |
|
0x00090004 |
major |
ram, nvram, buzzer, popup |
Logical drive has been set to critical |
One or more of the Physical Drives of the array are Offline |
Check the state of the physical drives in array and rebuild the failed physical drive |
|
0x00090005 |
info |
ram, popup |
Logical drive axle has been placed online |
None |
None |
|
0x00090006 |
info |
ram, nvram, popup |
Rebuild marks the logical drive synchronized upon rebuild completion |
Rebuilding process made the logical drive synchronized |
None |
|
0x00090007 |
info |
ram, nvram, popup |
Logical Drive Settings has been changed through a user command |
The User wished to change some Logical Drive Settings |
None |
|
0x0009000C |
major |
ram, nvram, buzzer, popup |
Logical drive has been set to degrade |
One of the Physical Drives in RAID6 LD of the array is Offline |
Check the state of the physical drives in array and rebuild the failed physical drive |
|
0x0009000D |
major |
ram, nvram, popup |
One of the Error Table (Read Check Table (RCT), Write Check Table (WCT) or Inconsistent Block Table (IBT)) of a logical drive has been cleared by the user |
User has cleared the Error Table |
None |
|
0x000B0000 |
info |
ram, popup |
Media patrol is started |
User or BGA scheduler started it |
No action required |
|
0x000B0001 |
info |
ram, popup |
Media patrol is completed |
Media patrol is completed |
No action required |
|
0x000B0002 |
info |
ram, popup |
Media patrol is paused |
User or BGA scheduler or other higer priority BGA activity paused it |
No action required |
|
0x000B0003 |
info |
ram, popup |
Media patrol is resumed |
User or BGA scheduler or other higer priority BGA is completed or stopped |
No action required |
|
0x000B0004 |
info |
ram, popup |
Media patrol is stopped |
User stopped it, or BGA scheduler stopped it, or all array(s) and spare(s) with media patrol enabled are deleted |
No action required |
|
0x000B0006 |
critical |
ram, nvram, buzzer, popup |
Media Patrol is aborted due to an internal error |
System resource is not available |
Reduced system load or reboot |
|
0x000B0007 |
info |
ram, popup |
Media Patrol is queued |
Input cause string here |
Input action string here |
|
0x000B0008 |
info |
ram, popup |
Media Patrol is stopped internally |
All array with MP enabled is deleted / removed |
No action required |
|
0x000B0009 |
info |
ram, popup |
Media Patrol is in progress |
Input cause string here |
No action required |
|
0x000C0000 |
info |
ram, nvram, popup |
RAID migration has started |
Input cause string here |
Input action string here |
|
0x000C0001 |
info |
ram, nvram, popup |
RAID migration has completed |
Input cause string here |
Input action string here |
|
0x000C0002 |
info |
ram, nvram, popup |
RAID migration has paused |
Input cause string here |
Input action string here |
|
0x000C0003 |
info |
ram, nvram, popup |
RAID migration has resumed |
Input cause string here |
Input action string here |
|
0x000C0004 |
info |
ram, nvram, popup |
RAID migration has stopped |
Input cause string here |
Input action string here |
|
0x000C0005 |
warning |
ram, nvram, buzzer, popup |
RAID migration has encountered a physical disk error |
Input cause string here |
Input action string here |
|
0x000C0006 |
warning |
ram, nvram, buzzer, popup |
RAID migration is aborted due to an internal error |
Input cause string here |
Input action string here |
|
0x000C0007 |
info |
ram, nvram, popup |
RAID migration is queued |
Input cause string here |
Input action string here |
|
0x000C0008 |
info |
ram, nvram, popup |
Migration has detected Stale NV Watermark |
Input cause string here |
Input action string here |
|
0x000C0009 |
info |
ram, nvram, popup |
Migration has cleared Stale NV Watermark |
Input cause string here |
Input action string here |
|
0x000C000A |
info |
ram, nvram, popup |
Array was made Incomplete due to missing NV Watermark |
Input cause string here |
Input action string here |
|
0x000C000B |
info |
ram, nvram, popup |
User has accepted Incomplete Array. (caused by missing NV Watermark) |
Input cause string here |
Input action string here |
|
0x000C000C |
info |
ram, popup |
RAID migration is in progress |
Input cause string here |
Input action string here |
|
0x000D0000 |
info |
ram, popup |
Physical Disk is marked online |
Physical Disk was used to create the configuration |
No Action required |
|
0x000D0001 |
info |
ram, popup |
Physical Disk is marked offline |
Physical Disk was marked offline by user or internally due to errors |
Replace the physicla disk with a new disk |
|
0x000D0002 |
major |
ram, nvram, buzzer, popup |
Physical Disk is marked as DEAD |
Physical Disk is marked as DEAD due to drive errors |
Replace the physical disk with a new disk |
|
0x000D0003 |
info |
ram, popup |
Physical Disk has been reset |
Physical Disk has been reset due to command time out |
Replace the physical disk with a new disk |
|
0x000D0004 |
info |
ram, popup |
Physical Disk is assigned as a global spare |
Physical Disk is assigned as a global spare |
No action required |
|
0x000D0005 |
info |
ram, popup |
Global Spare has been deleted |
Global Spare has been deleted |
None |
|
0x000D0006 |
info |
ram, popup |
Physical Disk is no longer assigned as a global spare |
Physical Disk was used as data member to rebuild one of the members of the array |
None |
|
0x000D0007 |
info |
ram, popup |
Physical Disk is assigned as a dedicated spare |
Physical Disk is assigned as a dedicated spare by User |
None |
|
0x000D0008 |
info |
ram, popup |
Dedicated Spare has been deleted |
Dedicated Spare has been deleted by User |
None |
|
0x000D0009 |
info |
ram, popup |
Physical Disk is no longer assigned as a dedicated spare |
Physical Disk was used as data member to rebuild one of the members of the dedicated array |
None |
|
0x000D000A |
info |
ram, popup |
Physical Disk has been inserted |
Physical Disk has been inserted by User |
None |
|
0x000D000B |
info |
ram, popup |
Physical Disk has been removed |
Physical Disk has been removed by User |
Insert a new physical disk |
|
0x000D000C |
info |
ram, popup |
Command on phyiscal disk has been re-tried |
Command on phyiscal disk has been re-tried due to drive not responding to the command |
None |
|
0x000D000D |
minor |
ram, nvram, buzzer, popup |
Physical disk ECC error is detected |
Physical disk ECC error is detected due to bad medium on the disk |
Replace the physical disk with a new disk |
|
0x000D000E |
minor |
ram, nvram, buzzer, popup |
Physical disk CRC error is detected |
Physical Disk CRC error is detected due to bad medium on the disk |
Replace the physical disk with a new disk |
|
0x000D000F |
minor |
ram, nvram, buzzer, popup |
Bad sector is found on physical disk |
Bad sector is found on physical disk due to medium errors on the disk |
Replace the physical disk with a new disk |
|
0x000D0010 |
minor |
ram, nvram, buzzer, popup |
Error is detected in remap sectors |
Error is detected in remap sectors due to medium errors in the disk |
None |
|
0x000D0011 |
minor |
ram, nvram, buzzer, popup |
Command times out on physical disk |
Command times out on physical disk |
Replace the physical disk with a new disk |
|
0x000D0012 |
warning |
ram, buzzer, popup |
Physical disk negotiation speed is decreased |
Physical disk negotiation speed is decreased as the disk does not support higher speed |
None |
|
0x000D0013 |
warning |
ram, popup |
Previously configured disk is no longer found |
Previously configured disk is no longer found as that disk is not present |
Insert the previously configured disk in to the system |
|
0x000D0014 |
warning |
ram, nvram, popup |
A physical disk has encountered an unknown (non-ECC) media error |
A physical disk has encountered an unknown (non-ECC) media error |
Replace the physical disk with a new disk |
|
0x000D0015 |
warning |
ram, nvram, popup |
A physical disk has encountered PFA condition |
A physical disk has encountered PFA condition |
Replace the physical disk with a new disk |
|
0x000D0016 |
info |
ram, popup |
A configured dead physical disk has been inserted |
A configured dead physical disk has been inserted |
Replace the physical disk with a new disk |
|
0x000D0017 |
warning |
ram, nvram, popup |
A physical disk Page 0 settings has changed |
A physical disk Page 0 settings was changed by User |
None |
|
0x000D0018 |
warning |
ram, nvram, popup |
Physical disk page 1 (SATA related) settings have changed |
Physical disk page 1 (SATA related) settings was changed by User |
None |
|
0x000D001A |
major |
ram, nvram, buzzer, popup |
Physical Disk is marked as DEAD due to removal |
Physical Disk is marked as DEAD due to removal |
Insert a new physical disk in to the slot |
|
0x000D001b |
major |
ram, nvram, buzzer, popup |
Physical Disk is marked as DEAD due to the failure of Reassign sectors comand to the disk |
Physical Disk is marked as DEAD due to the failure of Reassign sectors comand to the disk |
Replace the disk with new physical disk |
|
0x000D001c |
major |
ram, nvram, buzzer, popup |
Physical Disk is marked as DEAD due to PFA condition of the disk |
>Physical Disk is marked as DEAD due to PFA condition of the disk |
Replace the disk with new physical disk |
|
0x000D001d |
major |
ram, nvram, buzzer, popup |
Physical Disk is marked as DEAD due to forced offline state |
Physical Disk is marked as DEAD due to forced offline state by User |
Replace the disk with new physical disk |
|
0x000D001e |
warning |
ram, nvram, popup |
One of The Physical disk Path has failed |
One of The Physical disk Path has failed |
None |
|
0x000D001f |
warning |
ram, nvram, popup |
Physical disk page 3 (SAS related settings) have changed |
Physical disk page 3 (SAS related settings) was changed by User |
None |
|
0x000D0020 |
warning |
ram, nvram, popup |
Physical disk seen by partner controller not seen here |
Possibly single ported drives present or incorrect SAS Cabling |
Fix the SAS cabling if not single ported drives |
|
0x000D0021 |
warning |
ram, nvram, popup |
Single Ported Physical disk seen by Partner controller not seen here |
Possibly single ported drives present |
None |
|
0x000D0022 |
warning |
ram, nvram, popup |
Physical Disk reported not ready |
Physical Disk reported not ready |
Replace the physical disk with a new disk |
|
0x000E0000 |
warning |
ram, buzzer, popup |
PSU is NOT inserted |
PSU is NOT inserted |
Insert PSU |
|
0x000E0001 |
warning |
ram, nvram, buzzer, popup |
PSU is off |
PSU is turned off or power cable is unplugged |
Turn on power or plug in power cable |
|
0x000E0002 |
info |
ram, nvram, buzzer, popup |
PSU is on |
PSU is on |
No action is required |
|
0x000E0003 |
info |
ram, nvram, popup |
PSU is installed and turned on |
PSU is installed and is switched on |
No action is required |
|
0x000E0004 |
warning |
ram, nvram, popup |
PSU is installed and turned off |
PSU is installed but it is switched off |
Check PSU switch |
|
0x000E0005 |
info |
ram, nvram, popup |
PSU is functional and turned on |
PSU is operational and is switched on |
No action is required |
|
0x000E0006 |
warning |
ram, nvram, popup |
PSU is functional and turned off |
PSU is operational but is switched off |
Check PSU switch |
|
0x000E0007 |
major |
ram, nvram, popup |
PSU is malfunctioning and turned on |
PSU is malfunctional with power switched on |
Replace PSU |
|
0x000E0008 |
major |
ram, nvram, popup |
PSU is malfunctioning and turned off |
PSU is malfunctional with power switched off |
Replace PSU |
|
0x000E0009 |
warning |
ram, nvram, popup |
PSU has been removed |
The firmware does not detect the specific PSU existence |
Check PSU |
|
0x000E0010 |
critical |
ram, nvram, buzzer, popup |
PSU 12V power is out of the threshold range |
The firmware detects 12V power is out of range |
Replace PSU |
|
0x000E0011 |
critical |
ram, nvram, buzzer, popup |
PSU 5V power is out of the threshold range |
The firmware detects 5V power is out of range |
Replace PSU |
|
0x000E0012 |
critical |
ram, nvram, buzzer, popup |
PSU 3.3V power is out of the threshold range |
The firmware detects 3.3V power is out of range |
Replace PSU |
|
0x000E0013 |
info |
ram, nvram, popup |
PSU 3.3V power is within the normal range |
The firmware detects 3.3V power is within the range |
No action is required |
|
0x000E0014 |
info |
ram, nvram, popup |
PSU 5V power is within the normal range |
The firmware detects 5V power is within the range |
No action is required |
|
0x000E0015 |
info |
ram, nvram, popup |
PSU 12V power is within the normal range |
The firmware detects 12V power is within the range |
No action is required |
|
0x000E0016 |
critical |
ram, nvram, popup |
PSU is critical. This may cause instability of the system |
Unsupported PSU or unstable power |
Check the power to the PSU, or replace the PSU with the supported model |
|
0x000F0000 |
info |
ram, nvram, popup |
Rebuild is started |
User started rebuild, or auto-rebuild is started |
No action required |
|
0x000F0001 |
info |
ram, nvram, popup |
Rebuild is completed |
Rebuild is completed on the physical drive |
No action required |
|
0x000F0002 |
warning |
ram, popup |
Rebuild is paused |
User paused it |
Resume rebuild as soon as possible |
|
0x000F0003 |
info |
ram, popup |
Rebuild is resumed |
User resumed it or rebuild is resumed after reboot |
No action required |
|
0x000F0004 |
warning |
ram, nvram, popup |
Rebuild is stopped |
User stopped it, or array is deleted |
If user stopped it, restart rebuild as soon as possible |
|
0x000F0007 |
critical |
ram, nvram, buzzer, popup |
Rebuild is aborted |
System resource is not available |
Reduce system load or reboot |
|
0x000F0009 |
info |
ram, nvram, popup |
Rebuild is queued |
Input cause string here |
Input action string here |
|
0x000F000A |
info |
ram, nvram, popup |
Transition is started |
User started it or auto-transition started |
No action required |
|
0x000F000B |
info |
ram, nvram, popup |
Transition is completed |
Transition is completed |
No action required |
|
0x000F000C |
info |
ram, popup |
Transition is paused |
User paused it or other higher priority BGA scheduler is running |
User resume as needed |
|
0x000F000D |
info |
ram, popup |
Transition is resumed |
User resumed it,or it is resumed after reboot |
No action required |
|
0x000F000E |
info |
ram, nvram, popup |
Transition is stopped |
User stopped it |
No action required |
|
0x000F000F |
info |
ram, nvram, popup |
Transition is switched to rebuild |
Source physical drive is removed or dead |
No action required |
|
0x000F0010 |
warning |
ram, nvram, popup |
Auto rebuild can not start |
The capacity of unconfigured physical drive is not capable of rebuild |
Replace a drive with proper capacity |
|
0x000F0011 |
warning |
ram, nvram, popup |
Rebuild stopped internally |
Logical drive is offline |
No action required |
|
0x000F0012 |
info |
ram, popup |
Rebuild is in progress |
Input cause string here |
No action required |
|
0x000F0013 |
info |
ram, popup |
Transition is in progress |
Input cause string here |
No action required |
|
0x00100000 |
minor |
ram, nvram, buzzer, popup |
SMART error is received |
Input cause string here |
Input action string here |
|
0x0011000A |
info |
ram, popup |
Subsystem parameter(s) are changed by user |
Subsystem parameter(s) are changed by user |
None |
|
0x0011000B |
info |
ram, popup |
System is set to Redundant mode |
A partner controller has joined to form High Availability |
None |
|
0x0011000C |
major |
ram, nvram, buzzer, popup |
System is set to Critical mode |
The partner controller is no longer accessible |
Check the partner controller |
|
0x0011000D |
info |
ram, popup |
System is set to Non-Redundant mode |
Only one controller is present in the system |
None |
|
0x0011000E |
info |
ram, nvram, popup |
The Subsystem is started |
The Subsystem has started |
None |
|
0x0011000F |
info |
ram, nvram, popup |
The Subsystem is stopped |
The Subsystem has stopped |
None |
|
0x00120000 |
info |
ram, popup |
Synchronization is started |
The logical drive is created |
No action is required |
|
0x00120001 |
info |
ram, popup |
Synchronization is completed |
Synchronization is completed |
No action is required |
|
0x00120002 |
info |
ram, popup |
Synchronization is paused |
Higher priority BGA activity such as PDM or RC on the logical drive(s) on the same array is running |
No action required |
|
0x00120003 |
info |
ram, popup |
Synchronization is resumed |
Higher priority BGA activity is completed or it is resumed after reboot |
No action required |
|
0x00120004 |
info |
ram, popup |
Synchronization is stopped |
Logical drive is deleted, or critical, or offline. It could be also initialization or migration started |
No action required |
|
0x00120005 |
critical |
ram, nvram, buzzer, popup |
Synchronization is aborted due to an internal error |
System resource is not available |
Reduce system load or reboot |
|
0x00120006 |
info |
ram, popup |
Synchronization is queued |
Sync is already running on some other LD in same array |
None |
|
0x00120008 |
info |
ram, popup |
Synchronization is stopped internally |
LD not online or Higher priority task like LDI is started or delete LD/array |
None |
|
0x00130000 |
info |
ram, popup |
New disk array has been created |
A new disk array has been created by the user |
None |
|
0x00130001 |
info |
ram, popup |
Disk array has been deleted |
A disk array has been deleted by the user |
None |
|
0x00130002 |
info |
ram, popup |
Disk array has been added |
A new disk array has been added to the controller by adding new Physical drives to the enclosure |
None |
|
0x00130003 |
warning |
ram, buzzer, popup |
Disk array has been removed |
A disk array has been removed from the controller by removing Physical Drives from the enclosure |
If the drives were not intentionally removed, check to see if the drives are properly inserted in the enclosure |
|
0x00130004 |
info |
ram, popup |
Disk array settings have been changed |
Disk array settings have been changed through user intervention |
None |
|
0x00130005 |
info |
ram, nvram, popup |
Disk array is transport ready |
User requested to make a disk array transport ready |
Disk array is ready for transport. Remove Physical drives in disk array and move them to a different subsystem. To cancel Transport Ready Status, remove and reinsert the drives in the disk array. |
|
0x00140000 |
info |
ram, popup |
Drive interface controller is found |
Input cause string here |
Input action string here |
|
0x00140001 |
info |
ram, popup |
Drive interface controller is NOT found |
Input cause string here |
Input action string here |
|
0x00140002 |
info |
ram, popup |
Drive interface diagnostics has passed |
Input cause string here |
Input action string here |
|
0x00140003 |
info |
ram, nvram, popup |
Drive interface diagnostics has failed |
Input cause string here |
Input action string here |
|
0x00140004 |
info |
ram, nvram, popup |
Drive interface controller has generated a general parity error |
Input cause string here |
Input action string here |
|
0x00140005 |
info |
ram, nvram, popup |
Drive interface controller has generated a data parity error |
Input cause string here |
Input action string here |
|
0x00150000 |
info |
ram, nvram, popup |
Online Capacity Expansion has started |
Input cause string here |
Input action string here |
|
0x00150001 |
info |
ram, nvram, popup |
Online Capacity Expansion has completed |
Input cause string here |
Input action string here |
|
0x00150002 |
info |
ram, nvram, popup |
Online Capacity Expansion has paused |
Input cause string here |
Input action string here |
|
0x00150003 |
info |
ram, nvram, popup |
Online Capacity Expansion has resumed |
Input cause string here |
Input action string here |
|
0x00150004 |
info |
ram, nvram, popup |
Online Capacity Expansion has stopped |
Input cause string here |
Input action string here |
|
0x00150005 |
fatal |
ram, nvram, buzzer, popup |
Online Capacity Expansion has encountered a physical disk error |
Input cause string here |
Input action string here |
|
0x00150006 |
fatal |
ram, nvram, buzzer, popup |
Online Capacity Expansion is aborted due to an internal error |
Input cause string here |
Input action string here |
|
0x00150007 |
info |
ram, nvram, popup |
Online Capacity Expansion is queued |
Input cause string hereOnline Capacity Expansion task is queued |
Input action string here |
|
0x00160000 |
info |
ram, nvram, popup |
RAID Level Migration has started |
Input cause string here |
Input action string here |
|
0x00160001 |
info |
ram, nvram, popup |
RAID Level Migration has completed |
Input cause string here |
Input action string here |
|
0x00160002 |
info |
ram, nvram, popup |
RAID Level Migration has paused |
Input cause string here |
Input action string here |
|
0x00160003 |
info |
ram, nvram, popup |
RAID Level Migration has resumed |
Input cause string here |
Input action string here |
|
0x00160004 |
info |
ram, nvram, popup |
RAID Level Migration has stopped |
Input cause string here |
Input action string here |
|
0x00160005 |
fatal |
ram, nvram, buzzer, popup |
RAID Level Migration has encountered a physical disk error |
Input cause string here |
Input action string here |
|
0x00160006 |
fatal |
ram, nvram, buzzer, popup |
RAID Level Migration is aborted due to an internal error |
Input cause string here |
Input action string here |
|
0x00160007 |
info |
ram, nvram, popup |
RAID Level Migration is queued |
Input cause string here |
Input action string here |
|
0x00170000 |
info |
ram, nvram, popup |
Stripe Level Migration has started |
Input cause string here |
Input action string here |
|
0x00170001 |
info |
ram, nvram, popup |
Stripe Level Migration has completed |
Input cause string here |
Input action string here |
|
0x00170002 |
info |
ram, nvram, popup |
Stripe Level Migration has paused |
Input cause string here |
Input action string here |
|
0x00170003 |
info |
ram, nvram, popup |
Stripe Level Migration has resumed |
Input cause string here |
Input action string here |
|
0x00170004 |
info |
ram, nvram, popup |
Stripe Level Migration has stopped |
Input cause string here |
Input action string here |
|
0x00170005 |
fatal |
ram, nvram, buzzer, popup |
Stripe Level Migration has encountered a physical disk error |
Input cause string here |
Input action string here |
|
0x00170006 |
fatal |
ram, nvram, buzzer, popup |
Stripe Level Migration is aborted due to an internal error |
Input cause string here |
Input action string here |
|
0x00170007 |
info |
ram, nvram, popup |
Stripe Level Migration is queued |
Input cause string here |
Input action string here |
|
0x00190000 |
info |
ram, popup |
Resource is NOT available |
Input cause string here |
Input action string here |
|
0x00190001 |
info |
ram, popup |
Resource is NOT available |
Input cause string here |
Input action string here |
|
0x00190002 |
info |
ram, popup |
Resource is NOT available |
Input cause string here |
Input action string here |
|
0x00190003 |
info |
ram, popup |
Resource is NOT available |
Input cause string here |
Input action string here |
|
0x001A0000 |
info |
ram, popup |
Blowers or PSU fans have started |
The firmware starts blowers or PSU fans |
No action is required |
|
0x001A0001 |
info |
ram, popup |
Blowers or PSU fans have stopped |
The firmware stops blowers or PSU fans |
No action is required |
|
0x001A0002 |
info |
ram, popup |
Blower or PSU fan speed is increased |
Temperatures Increased |
No action is required |
|
0x001A0003 |
info |
ram, popup |
Blower or PSU fan speed is decreased |
Temperatures dropped back to normal |
No action is required |
|
0x001A0004 |
minor |
ram, nvram, buzzer, popup |
Blowers or PSU fans are NOT functioning |
The firmware detects blowers or PSU fans with a speed of 0 or out of control |
Replace blower or PSU fans |
|
0x001A0005 |
info |
ram, popup |
Blowers or PSU fans have been inserted |
The firmware detects the specific blowers or PSU existence |
No action is required |
|
0x001A0006 |
info |
ram, popup |
Blowers or PSU fans have been removed |
The firmware is not able to detect the existence of the blower or the PSU fan, but exist in the previous status |
Check blowers or PSU fans |
|
0x001A0007 |
info |
ram, nvram, popup |
Blowers or PSU fans are functioning normally |
The blower or the PSU fan are detected with good status |
No action is required |
|
0x001A0008 |
warning |
ram, nvram, buzzer, popup |
Blowers or PSU fans are NOT installed |
The firmware does not detect existenc of blowers or PSU fans |
Check blowers or PSU fans |
|
0x001A0009 |
warning |
ram, nvram, buzzer, popup |
Blower or PSU fan status is unknown |
The firmware is not able to read blowers or PSU fans information but detects the existence |
Check blowers or PSU fans |
|
0x001B0000 |
info |
ram, nvram, popup |
PDM is started |
User started it or the drive in the array has PFA condition |
No action required |
|
0x001B0001 |
info |
ram, nvram, popup |
PDM is completed |
PDM is completed |
None |
|
0x001B0002 |
info |
ram, popup |
PDM is paused |
User paused it or higher priority BGA activity started |
If user paused, resumed it |
|
0x001B0003 |
info |
ram, popup |
PDM is resumed |
User resumed it or higher priority BGA activity is completed or it is resumed after rebooted |
No action required |
|
0x001B0004 |
info |
ram, popup |
PDM is stopped |
User stopped it or destination physical drive is removed or dead |
No action required |
|
0x001B0009 |
info |
ram, nvram, popup |
PDM is swtiched to rebuild |
Source drive is removed or dead |
No action required |
|
0x001B000a |
info |
ram, popup |
PDM is stopped internally |
Destination drive is removed or used for rebuild |
No action required |
|
0x001B000B |
info |
ram, popup |
PDM is in progress |
Input cause string here |
No action required |
|
0x001D0000 |
info |
ram, popup |
Spare check started on the given spare drive |
Spare check started either manually by the user or started by SW scheduler |
No action required |
|
0x001D0001 |
info |
ram, popup |
Spare check completed successfully on the given spare drive |
Spare check completed successfully on the given spare array |
No action required |
|
0x001e0000 |
critical |
ram, nvram, buzzer, popup |
Enclosure temperature is above the threshold |
The system temperature is above the preset threshold |
Check blowers and fans |
|
0x001e0001 |
critical |
ram, nvram, buzzer, popup |
Enclosure temperature is above the critical threshold |
The system temperature is above enclosure critical threshold |
Check blowers and fans |
|
0x001e0002 |
warning |
ram, nvram, buzzer, popup |
Enclosure temperature is above the warning threshold |
The enclosure temperature is above enclosure warning threshold |
Check blowers and fans |
|
0x001e0003 |
info |
ram, nvram, popup |
Enclosure temperature is within the normal range |
The system temperature drops below the enclosure warning threshold |
No Action is required |
|
0x001e0004 |
critical |
ram, nvram, buzzer, popup |
Controller temperature is above the critical threshold |
The controller temperature is above controller critical threshold |
Check blowers and fans |
|
0x001e0005 |
warning |
ram, nvram, buzzer, popup |
Controller temperature is above the warning threshold |
The controller temperature is above controller warning threshold |
Check blowers and fans |
|
0x001e0006 |
info |
ram, nvram, popup |
Controller temperature is within the normal range |
The controller temperature drops below the controller warning threshold |
No action is required |
|
0x001e0007 |
critical |
ram, nvram |
Shut down PSUs due to enclosure or controller temperature over threshold |
The PSUs shut down because temperatures exceed the protection threshold |
Refer to the troubleshooting section of the product manual |
|
0x001F0000 |
info |
ram, popup |
Firmware update is started |
Firmware update is started |
No action required |
|
0x001F0001 |
info |
ram, popup |
Firmware update is complete |
Firmware update is complete |
No action required |
|
0x001F0002 |
warning |
ram, popup |
Firmware update is fail |
Firmware update is fail |
No action required |
|
0x001F0003 |
info |
ram, nvram, popup |
Backend expander firmware upgrade is completed |
NA |
No action required |
|
0x001F0004 |
info |
ram, nvram, popup |
Frontend expander firmware upgrade is completed |
NA |
No action required |
|
0x001F0005 |
major |
ram, nvram, popup |
Backend expander firmware upgrade failed |
Backend (Interposer) upgrade cannot be completed successfully |
Retry the firmware upgrade |
|
0x001F0006 |
major |
ram, nvram, popup |
Frontend expander firmware upgrade failed |
Frontend expander upgrade cannot be completed successfully |
Retry the firmware upgrade |
|
0x001F0007 |
info |
ram, nvram, popup |
Backend expander firmware upgrade is started |
NA |
No action required |
|
0x001F0007 |
info |
ram, nvram, popup |
Frontend expander firmware upgrade is started |
NA |
No action required |
|
0x00220000 |
info |
ram |
Blade Server Inserted |
Blade Server was plugged in |
No action required |
|
0x00220001 |
info |
ram |
Blade Server Removed |
Blade Server was plugged out |
No action required |
©2008 Promise Technology, Inc. All Rights Reserved.
No part of this document may be reproduced or transmitted in any form without the expressed, written permission of Promise Technology, Inc.
