Home

Troubleshooting Guide - Rorke Data

1. Troubleshooting 45 5 Service LED on Models that Come with an LED Side Panel The service LED is available with the Galaxy series JBOD expansion enclosures SBOD JBOD The service LED can be enabled by a single click on the GAM screen icon from a remote site to identify which subsystem needs attention For example an administrator receives component failure event and turns on the enclosure service LED using the GAM GUI so that an engineer on the installation site can easily locate the faulty component When turned on the corresponding subsystem LED will also be lit on the GAM GUI screen A mouse click on the service LED in the GAM screen lights the service LED Enclosure View RAID JBOD Top of LED Front Panel Information Summary Device Controller CPU PPC750FX Cache 256MB ECC DDR Firmware 3 516 13 Bootrecorc Channel Channel 0 Host Fibre Speed es Channel Channel 1 Host Fibre Speed 1 Logical Drive ID 7B6CS5B00 NRAID 34812MB E i nanira Drive INAM RACAN RAIN 1 19nNMR The Services LED helps you locate a specific enclosure in a complex configuration consisting of multiple enclosures A RAID administrator can be notified by component failure event via a variety of notification methods GUI screen Enclosure View RAID 480010 JBOO211 RAID enclosure NYMNYT Expansion enclosures SL Email Administrator T b 46 Galaxy DS An administrator may initi
2. What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do SES CO 10 UPS 2 UPS Power Back On Line UPS 2 connected through SES interface reports power back online Press ESC to clear this message NOTICE CPU Cold Temperature Back To Normal Cold temperature has risen up back to the normal range Press ESC to clear this message Controller Cold Temperature Back To Normal sensor no Cold temperature has risen up back to the normal range Reading from a sensor on controller board Press ESC to clear this message ASIC Cold Temperature Back To Normal sensor no Cold temperature has risen up back to the normal range Reading from a sensor on ASIC Press ESC to clear this message IO chip Cold Temperature Back To Normal sensor no Cold temperature has risen up back to the normal range Reading from a sensor on IO chip Press ESC to clear this message Peripheral Set X Device NOTICE Backplane Temperature Back to Normal The Peripheral Set number indicates the location where the event occurred e g O RAID enclosure 1 attached JBOD Sensor on a backplane reports normal temperature reading Press ESC to clear this message Peripheral Set X Device Notice Backplane Temperature is Present The Peripheral Set number i
3. SANWatch Maat Host Storage Area Network Direct attached 4 The Notification Manager within GAM can be configured to deliver system events using various methods including Email Fax LAN broadcast MSN SMS and SNMP traps An administrator can also isolate a problem using GAMs graphical display Please refer to the Galaxy Array Manager User s Manual for more details If system faults occur the faults will be indicated by the LED display status summary and the system events 8 Galaxy DS System Action U enie Gat xt array 102 168 57 LED display amp Erciosure View 7 Tasks Unser Process Lopical Drive information Fp Lopical Voksne information E systom intormanon NU Statienes amp S maintenance Status Summary s X coemguraton Controller CPUSPCTSORYFL Cache 512M8 ECC COR Fimware 3 49A J oww Charnel 0 Hest OCSI Speed Negotiated to F0DMB jeme Ful Duges Fi ened harrei Most SCSI Speed Negotisted to 100M sec Full Oupiex Event Log F togestone IDZNF7TA8 NEAIO 7627796 T rogealtrve 10 7C6220 NRAID 23821400 Bu IH 10 SCSI 100 UUNO tun TEH ma sest 100 wueno 2003 03 17 17 00 46 Kontroler tbakzation Comgieted a 2003 03 17 17 0807 NOTICE ARAN Factory De sus Restored L 7 n OHT ob Conniaher intidkestion Comgieted 3 200 0717 171701 10122467838 Logical Orive NOTICE Starting Crestion 3
4. lt 2002 06 09 15 58 03 gt Esc Exit Ctri L Refresh Screen Event messages are also displayed on the LCD screen You can check the event message and system LEDs to verify and then correct the faults UPS Power Failure Detected 10 Galaxy DS 4 Event Messages and Corrective Actions The controller events can be categorized as follows according to the severity levels Critical Errors that need to attend to immediately Warning Errors Notification Command processed message sent from Firmware The RAID subsystem records all system events from power on temporarily record them in cache with up to 1 000 entries To power off or to reset the controller will cause an automatic deletion of all the recorded event logs Firmware rev 3 61 enables an event log to be saved into logical drives 256MB reserved space and hence users can also see the events after a system reset The GAM manager can be used to record events on multiple subsystems especially when a controller reset or power off is an expected action The events can also be seen from GAMs Notification Manager Associated details can be found in the GAM users manual and online help Ble Lanos Heb s iQ R gt lala Ro Ge Connection Views Model Gx4i 2840R8 16F8 Name Capacity M concen Total Capacity 305 GB IP 192 168 4 78 Controller ID 834574 carry 0 204016 1256 IP 192 168 4 210 c onfigurations korenie dj Controller 1 E Logic
5. ID may have failed or been disconnected Make sure all channels are properly connected and topological configurations properly set What to Do Check cabling and system installation Contact your supplier if no connection errors could be found Message Slot X Drive WARN Excessive Bad Block Advisory 0 0 What Happened Multiple instances of bad blocks have been found on a disk drive The disk drive can be faulty and causing drag to LD performance If the situation worsens this drive can be considered as an Exiled drive and disbanded from a logical drive What to Do You may consider replacing an unreliable drive using the Copy and Replace function or use the Drive Performance Monitor utility in GAM to check a drive s read write latency If a drive member produces high latency you can consider replacing it 4 2 3 Notification Message Invalid trunking configuration for Slot X CHX What Happened Incongruent settings on system host ports and Ethernet switch ports The most probable reason is that switch ports have not been configured into corresponding trunked ports You might as well have configured MC S Multiple Connections per Session that does not match your trunk setting e g CHO amp CH1 into MC S group whereas you configure CHO CH3 into a trunk group What to Do Check trunk Link Aggregation settings on your Ethernet switch Message CHL ID NOTICE Media Error Recovered 0xD8001C7C What Happened Data once stor
6. What to Do Press ESC to clear the message Message NOTICE Media Scan of CHL X ID XXX Completed What Media Scan on a specific disk drive on CHLX IDXXX is completed Happened What to Do Press ESC to clear the message Message LG X NOTICE Media Scan of CHL X ID XXX Completed What Media Scan on a specific member of Logical Drive X on CHLX and Happened IDXXX is completed Logical Drive Migrate process started Troubleshooting 21 What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE CHL X ID XXX Continue Clone Operation What The target logical drive has been restored to its previous status Happened e g a failed drive is restored and the cloning process can continue What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE CHL X ID XXX Starting Clone What Cloning process started on one of the members of Logical Drive X Happened What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE CHL X ID XXX Copy and Replace Completed What Copy and replace is completed with a specific member of Logical Happened Drive X The original member drive is replaced by another disk drive What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE CHL X ID XXX Clone Completed What Cloning is completed with a specific member of Logical Drive 0 Happened whether it is replaced Copy and Replace or cloned Perpetual Clone to a spare
7. 1 Rebuild and host write command For example in a RAID 5 configuration one member drive failed and media errors are found on another member drive 2 Disk clone and Add Drive Concurrent occurrences of media errors are found on the same stripe across two member drives What to Do The data affected by data blocks failure will be lost The host computer will return media error messages if host accesses fall within the affected blocks Restoring data from a backup source is recommended Message LG X Logical Drive ALERT UNPROTECTED Block Marked 000000084 What Media errors are found in an unprotected array e g RAIDO The Happened affected data blocks will be marked bad What to Do The data affected by data blocks failure will be lost The host computer will return media error messages if host access falls within the affected blocks Restoring data from a backup source is recommended Message LG X Logical Drive ALERT Bad Data Block Encountered 000000084 What Data blocks previously marked Bad are re encountered during host Happened I O access or certain operations such as Media Scan The marked logical blocks will cause the firmware to return media error status to host What to Do The data affected by data blocks failure is lost Restoring data from a backup source is recommended The host computer will return media error messages if host access falls within the affected blocks Message LG X ALERT Inconsistent Parity Encount
8. Drive etc What to Do The target disk drive may have become physically unreliable The data in the target LD could have been corrupted please restore the data from backup Contact system vendor for help Message LG X Logical Drive ALERT Logical Drive Bad Block Table BAD What System failed to generate a bad block table Logical drive may have Happened generated serious integrity problems What to Do The data in the target LD could have been corrupted please execute the Regenerate Parity function and restore data if instances of inconsistent parity are found Contact system vendor for help Message LG X Logical Drive ALERT Logical Drive On Line Init Table Bad What When an LD is still under an online initialization process and the Happened system reboots for some reasons the system will not be able to generate a correct On line Init table at boot time The logical drive may have encountered serious integrity problems What to Do Execute regenerate parity operation and ignore the inconsistent parity event if occurred Contact system vendor for help Message LG X Logical Drive ALERT Bad Data Block Marked 000000084 What During write operations including rebuild host write commands Happened disk cloning and Add Drive media errors may cause data 14 Galaxy DS inconsistency System cannot regenerate the data by RAID parity calculation The affected data blocks are marked bad The situation may result from the following
9. For some OEM version the choice between proceeding or ending a Media Scan operation depends on the integrity of an LD If the LD status is not good e g a member drive fails and enters a degraded mode then the Media Scan operation will pause for healthy members of the target LD When the LD restores its good status e g a faulty drive replaced and the LD is successfully rebuilt then firmware will resume the Media Scan operation Media Scan on the replacement drive will start from the beginning Message LG X Logical Drive ALERT Degraded What Happened Degraded mode means a logical drive has one or more members missing e g 1 in RAID5 or 2 in RAID6 The LD is still operational However rebuild is immediately necessary if you do not have a hot spare Even when you have a hot spare and it already joined the rebuild it is recommended that you replace the failed drive and configure the replacement drive as a hot spare in case that another drive may fail while system is still performing a rebuild What to Do Replace the failed drive to begin a manual rebuild or configure a hot spare as a precaution against yet another drive failure Message What Happened What to Do Message What LG X ALERT Missing Drive s The LD member drive could have been accidentally removed or drive connection problems occurred before system boot up This could result from a defective drive or simply when a drive tray is not properly insta
10. This applies when you want to physically move a logical drive to another enclosure What to Do Press ESC to clear the message Message LG X Logical Drive SEV Member drives restored What This event is shown when all members of a logical drive are moved Happened to another enclosure and that enclosure recognize the presence of all members What to Do Press ESC to clear the message Message LG X Logical Drive SEV Undeleted What An accidentally deleted logical drive can be rescued from the LD list Happened queue as long as its members are still present not been used to create another logical drive and their 256MB reserved space has not been removed What to Do Press ESC to clear the message 24 Galaxy DS 4 2 Channel and lndividual Drive Events 4 2 1 Critical Message CHL ID ALERT Media Error Unrecoverable 0xD8001C7C What Happened Drive surface media errors found and after rewrites the drive sectors are determined as physically damaged and unusable What to Do Data will be reassigned to other drive sectors Host writes should continue without problems 4 2 2 Warning Message CHL ID Target WARN Unexpected Select Timeout What Happened Drive target select timeout The specified hard drive cannot be selected by the RAID controller subsystem Whether the drive has been removed or the cabling termination canister is out of order What to Do This could occur if a disk drive is not properly installed or acc
11. can either use the Restore Default button or the LCD keypad panel The easiest way to check the type of firmware defaults is through the View and Edit Logical Drives menu on Mar 07 26 51 2008 MN Z CE HO Cache Status Cle lt Main Menu gt drives w and edit logical Volumes and edit Hos A and edit and edit and edit and edit Functi LITT T Tt 14 Hall mA ra A o K Arrow Keys Mo lt Work Procedures Case 1 Upgrade memory in a single controller system 2GB to 4GB 1 1 Shut down host computer s 1 2 Power OFF the RAID system 1 3 Remove the RAID controller and replace its memory with a 1GB or 2GB DIMM 1 4 Restore firmware defaults using the Restore Default button or the LCD keypad panel 1 5 Power ON the RAID system and check in Main Menu gt View and Edit Logical Drives to see whether the supported number of LD has become 32 1 6 Power on host computer s Case 2 Upgrade memory in a Redundant controller system 2GB to 4GB 2 1 Shut down host computer s 2 2 Power OFF the RAID system 2 3 Remove the RAID controllers and replace their memory with a 1GB or 2GB DIMM Troubleshooting 49 Case 3 2 5 2 6 3 1 3 4 Restore firmware defaults using the Restore Default button or the LCD keypad panel You should restore controller defaults each at a time by removing a controller from chassis Power ON the RAID system and check in Main Menu
12. controller hardware problems Please contact your RAID system supplier for a replacement controller Message ALERT Controller FAN 0 Low Speed Detected _RPM What Happened This only applies to controller fans in the certain Galaxy series Low rotation speed detected What to Do Contact your RAID system supplier for a replacement Message Controller ALERT Redundant Controller Failure Detected What Happened One RAID controller in a controller pair failed This message indicates that its partner has taken the workload and managed the failover operation The fault can result from the following 1 A RAID controller failure 2 The partner controllers cannot communicate with each other The other major reason can be the failure of the inter controller communication channels It could result from the defects of one or both RAID controllers or that of the backplane What to Do Contact your RAID system supplier for a replacement controller and restore the dual active configuration Message Controller PCI Bus Parity Errors Detected 40 Galaxy DS What Happened Serious system faults have occurred What to Do Stop host I Os immediately to prevent further data integrity errors and contact your RAID system supplier Message ALERT Controller BBU Failure Detected error code What Happened BBU battery cell pack has failed or is accidentally removed When a new module is installed reset the subsystem for the configuration to take ef
13. drive What to Do Press ESC to clear the message Message LG X Logical Drive NOTIFY Bad Data Block Recovered 000000084 What Host writes fall onto the data blocks previously marked bad and Happened overwrite the drive sectors What to Do Press ESC to clear the message Message LG X NOTICE CHL X ID XXX Media Scan Failed What Media Scan failed to carry on with scanning drive s for certain Happened reasons e g a logical drive or a disk drive has fatally or physically failed What to Do Media Scan on a failed disk drive will stop but the scan on healthy members of a target LD will continue For some OEM version the choice between proceeding or ending a Media Scan operation depends on the integrity of an LD If the LD status is not good e g a member drive fails and enters a degraded mode then the Media Scan operation will pause for healthy members of the target LD When the LD restores its good status e g a faulty drive replaced and the LD is successfully rebuilt then firmware will resume the Media Scan operation Media Scan on the replacement drive will start from the beginning Message NOTICE CHL X ID XXX Media Scan Failed What Media Scan failed to carry on with scanning drive s for certain Happened reasons e g a logical drive or a disk drive has fatally or physically 22 Galaxy DS What to Do failed Media Scan on a failed disk drive will stop but the scan on healthy members of a target LD will continue
14. force this operation to stop 3 Irrecoverable parity inconsistency may also cause a halt to the operation by user s configuration operation errors What to Do If the Check Regenerate Parity Failure is caused by a drive failure replace the faulty drive and rebuild the LD Then execute the check parity operation again 12 Galaxy DS If the Check Regenerate Parity Failure results from the discovery of inconsistent parity users have to change the firmware check parameters if users wish to complete the whole check parity operation Message LG X Logical Drive ALERT Creation Aborted What Logical drive creation process manually aborted or that some Happened system integrity problems forced the subsystem to abort logical drive creation process What to Do Check proper system working conditions Message LG X Logical Drive ALERT Creation Failed What Logical drive creation process failed when one or more drive Happened members failed or have been accidentally removed Drive abnormality may also be the cause of the problems What to Do Check proper system working conditions and drive connection Replace the faulty drives and repeat the creation process Message LG X Logical Drive ALERT Initialization Failed What Logical drive initialization failed It could result from one of the Happened following reasons 1 Off Line Initialization Failed Logical drive initialization failed This event can result from one member drive fai
15. gt View and Edit Logical Drives to see whether the supported number of LD has become 32 Power on host computer s Replacing a failed controller in a redundant controller RAID system equipped with 1G 2G size cache memory Check through the firmware configuration utility gt Main Menu gt View and Edit Logical Drives to see whether the supported number of LD is 32 If the screen shows 32 logical drive indexes then the firmware running on the surviving controller supports the 2 1GB defaults NOTE If the firmware screen shows 16 indexes you may refer to the Case 2 procedure if you prefer enlarging the number of logical configurations Install a 1G or 2G memory size identical to that on the surviving controller to the replacement controller Restore the replacement s defaults using the Restore Default button or the LCD keypad panel See Appendices for details You should use another RAID system to restore the defaults on the replacement controller Replace the failed controller with the replacement The replacement should be brought online after a short while 50 Galaxy DS Appendix B Firmware Automated Synchronization Background for this feature In the event of RAID controller failure a replacement controller usually comes with a firmware of a different revision than that running on the surviving controller If partner controllers run different firmware configuration errors can occur Benefi
16. message Message LG X Logical Drive NOTICE Off Line Expansion of Logical Drive Completed What Logical drive off line expansion completed The added capacity will Happened appear as a new partition and this partition may require being associated with a separate ID LUN on the host bus What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Continue Add Drive Operation What The target logical drive has been restored to its previous status Happened e g power off or media errors and the add drive operation can continue What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Continue Migrate Operation What The target logical drive has been restored to its previous status Happened e g power off or media errors and the migration operation can continue What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting Add Drive Operation What Add drive expansion process started Happened What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting Migrate Operation 20 Galaxy DS What Happened What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Add Drive Operation Paused What The add drive expansion process is halted by Happened 1 Logical drive expansion is cancelled by a user 2 One of the member drives failed during logical drive expansion 3 Media errors are found on one or more of th
17. the message After the cloning process you may consider replacing the defective drive with a good one and configure it as a spare drive in case drive failure might happen in the future Predictable Failure Detected Starting CHL _ WARN Fibre Channel Loop Failure Detected Fibre Channel loop integrity warning Lack of bypass or nodes on a loop caused a Fibre loop to fail Check host or drive side connection Contact your RAID system supplier CHL _ WARN Redundant Loop for CHL _ Failure Detected One of the dual loop members may have failed or been disconnected Make sure all channels are properly connected and topological configurations properly set Check cabling and system installation Contact your supplier if no connection errors could be found CHL _ WARN Redundant Path for CHL _ ID _ Expected but Not Found One of the dual loop members may have failed or been disconnected This event is regenerated in the event when one of the dual loop connections to an expansion enclosure can not be found after power up Make sure all channels are properly Troubleshooting 29 connected and topological configurations properly set What to Do Check cabling and system installation A manual Issue LIP command may restore the connection Contact your supplier if no connection errors could be found Message CHL ID WARN Redundant Path for CHL ID Failure Detected What Happened One of the dual loop members connecting device CHL
18. 2006 03 17 17172 lo 224 7E48 Logical Orive NOTICE Creabon of Logeal Drive Completed Ca J 2008 017 1717 12 NO C62200E Lopcal Orive NOTICE Stating Creation 7 J 2006 03 17 17 17 19 110 7C62203E al Orive NOTICE Creston c togeai Dive Comelatad ol 2008 09 20 14 29 17 Kontroler Iisakzstion Completed Event Log List Configuration List If managing multiple RAID systems using the GAM s portal screen a system having a system fault will be indicated by a warning sign on its system icon Note that if continuous monitoring is necessary the GAM service agents should be enabled on a server running 24 7 service Model Gx4 218S4 16I1 Nz IP 0 0 0 0 Ce Configurations Controller JBOD Total Disk Spare Disk Advanced Features An event log is also available by checking a terminal console with a RAID system Pressing the Space key reveals detailed information of each event Troubleshooting 9 Cache status 62 Dirty Event Logs Controller Initialization Completed Event Index 90 ID tialization Date Jun 10 13 34 56 2002 ID Severity Notification Drive Completed Event Type Controller Event ID Description Controller Initialization Completed controller Initialization Completed lt 2002 06 09 19 30 15 gt controller Initialization Completed lt 2002 06 09 19 18 40 gt Controller Initialization Completed lt 2002 06 09 18 54 29 gt controller Initialization Completed
19. D enclosure s ID DIP switches should normally not be changed Please refer to the hardware manual that came with your array Ensure that all enclosures in a RAID JBOD configuration is configured with a unique enclosure ID Message ALERT Enclosure IDX Invalid Drive Configuration What Happened Incorrect enclosure ID setting with the shown ID may be a conflict with attached enclosures What to Do Check ID rotary switch at the front of RAID or SBOD enclosures Some enclosures e g Galaxy Fibre drive models have related DIP switches that might have been accidentally flipped to wrong configuration A RAID enclosure s ID DIP switches should normally not be changed Please refer to the hardware manual that came with your array Ensure that all enclosures in a RAID JBOD configuration is configured with a unique enclosure ID 4 3 2 Notification Message Peripheral Set X Device NOTICE PSUX Back On Line What Happened The Peripheral Set number indicates the location where the event occurred e g O RAID enclosure 1 attached JBOD A PSU has been successfully replaced or re installed What to Do Press ESC to clear this message Message Peripheral Set X Device NOTICE PSUX is Present What Happened The Peripheral Set number indicates the location where the event occurred e g O RAID enclosure 1 attached JBOD A PSU once missing is now present in the module bay What to Do Press ESC to clear this message Message Peripheral
20. EEA 40 AA 2 NV AUT PEREA EET A T E E A T T T 42 44 3 Notification ee a ee rn aa nn nan 43 5 Service LED on Models that Come with an LED Side Panel ecceeseeseeeeeeeeneeeeeeeeneeeeeeseeeeeneeseneenaees 46 Appendix A Concerns for Replacing a Failed Controller eeecsesceeeceeeeeeeeeeeeneeeeeeeeneseaeesseeeeneesaas 48 Appendix B Firmware Automated Synchronization ceccceecceeceeeeeeseneeeeeeeeeeeeeeeeaeeseeeeeeeseaeeeaeeseeeeeneeseaeesaees 51 Revision History Rev 1 0 Initial release Rev 1 1 h Updated Galaxy LED definitions 2 Galaxy DS 1 Buzzer System Faults and Buzzer Sound Patterns During controller initialization BOD FA RAID enclosure fault conditions ae l condition Buzzer Sound via RAID behavior patterns Controller initialization RAID ON 1 JBOD controller ig not ready failed n l SON j Disk drive failure Disk drive failure RAID ON 2 Logical drive rebuild failure or manually gt RAID ON 3 aborted UPS functions AC connection failure f low battery charge BBU is absent M PAUSON 2 Cooling fan failure Cooling fan RAID ON 2 failure PSU failure PSU failure RAID ON 2 Temperature sensor failure temperatis RAID ON 2 sensor failure Rebuilding a logical drive RAID ON 2 Regenerating array parity RAID ON 3 Adding drive RAID ON 3 One controller fails in a redundant pair RAID ON 1 Disk command is b
21. HORKE An Avnet Company DATA ISO 9001 2008 ISO 13485 2003 Certified MODELS GX4AL XXX XX Galaxy RAID Subsystem Single amp Dual Controller www rorke com Galaxy HDX RAID 7th Generation RAID With over 10 000 Galaxy units in the field Rorke Data s award winning RAID products provide the performance protection and expansion capabilities for diverse customer environments PLEASE READ BEFORE INSTALLATION An Avnet Company Gal_DS_Tshoot_v1 1h Contact Information Americas Rorke Data an Avnet company 7626 Golden Triangle Drive Eden Prairie MN 55344 USA Tel 1 800 328 8147 Fax 1 952 829 0988 rorkesales avnet com rorkesupport avnet com http www rorke com Copyright 2011 This Edition First Published 2011 All rights reserved This publication may not be reproduced transmitted transcribed stored in a retrieval system or translated into any language or computer language in any form or by any means electronic mechanical magnetic optical chemical manual or otherwise without the prior written consent of Rorke Data Disclaimer Rorke Technology makes no representations or warranties with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose Furthermore Rorke Data reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation to notif
22. Set X Device NOTICE PSUX Back On Line 5 0V 36 Galaxy DS What Happened The Peripheral Set number indicates the location where the event occurred e g O RAID enclosure 1 attached JBOD The 5 0V line from PSU is now successfully restored What to Do Press ESC to clear this message Message NOTICE Fan Module X Back On Line FANO _RPM What Happened A once missing or failed cooling fan is restored This message is reported through an I2C serial bus with RPM reading What to Do Press ESC to clear this message Message NOTICE Controller FAN X Back On Line _ RPM What Happened A once missing or failed cooling fan is restored This message is reported through an 12C serial bus with RPM reading What to Do Press ESC to clear this message Message Peripheral Device NOTICE Fan Back On Line What Happened An I2C serial bus message indicating a once missing or failed cooling fan is restored What to Do Press ESC to clear this message Message Peripheral Set X Device NOTICE Cooling fanX Back On Line What Happened An individual cooling fan once missing or failed is restored What to Do Press ESC to clear this message Message Peripheral Set X Device NOTICE FAN X is Present What Happened An individual cooling fan once missing or failed is restored What to Do Press ESC to clear this message Message Peripheral Set X Device NOTICE Cooling fanX Back On Line _RPM What Happened An individual cooling fan once missi
23. To Normal _ _V What Happened 12V voltage dropped back within preset thresholds Troubleshooting 43 What to Do Check proper working condition and press ESC to clear the message Message NOTICE 12V Lower Voltage Back to Normal V What Happened 12V voltage dropped back within preset thresholds What to Do Check proper working condition and press ESC to clear the message Message Memory is Now Sufficient to Fully Support Current Config What Happened Memory of a sufficient capacity is installed and the subsystem should work properly This event could prompt after replacing a controller DIMM module or upgrading from a 512MB DIMM to a 1GB DIMM With 1GB DIMM you can create 1024 LUNs and 32 logical drives etc on an HDX2 RAID system With 512MB DIMM you may not be able to create the max supported LUNs etc What to Do Check proper working condition and press ESC to clear the message Message Controller NOTICE NVRAM Factory Defaults Restored What Happened _ The factory defaults for system configuration profile are restored What to Do Press ESC to clear the message Message NOTICE NVRAM Restore From File is Completed What Happened The factory defaults are restored from a file saved on a host computers system drive What to Do Press ESC to clear the message Message NOTICE NVRAM Restore From Disk is Completed What Happened The factory defaults are restored from a copy saved in logical drive s res
24. action For example 2 of the 3 PSUs in a 4U Galaxy failed or an elevated temperature is detected controller firmware will force the controller to enter a non responsive shutdown state Note that the system does not electronically shut down What to Do Check proper working condition and press ESC to clear the message Message ALERT Force Controller Shutdown Complete What Happened System shutdown is complete Cache is clean and you can manually turn off the system power or reset the system What to Do Press ESC to clear the message Message Fatal Power exhausted while backup to EBU cached data might be lost What Happened Insufficient charge in battery to supply the transmission of data from cache memory to CBM backup module Troubleshooting 41 What to Do Battery might not be able supply enough electricity Replace the battery Battery charger defects may also cause the insufficient charge Change the battery every 3 years Message Fatal EBU Cached Data Read error What Happened Read errors occurred with the CBM module Cached data can be lost What to Do Contact technical support for help 4 4 2 Warning Message Firmware synchronization started What Happened Refer to Appendix B for more information What to Do Check if firmware synchronization is properly processed You may need to reset the system later Message WARN Memory Not Sufficient to Fully Support Current Config What Happened The installed mem
25. al Volume ol jiad gt 192 160 478 z a JBOD 4 Logical Drive 2 Z Total Disk 16 4 Total Partition 7 Reentguwa 305 0 S Avatanie 0 4 Spare Disk 0 Unused Partition 2 Event Status E tun mapping 3 A coment o Advanced Features A wan g 2 10 70418060 Loga Drive NOTICE Rarting Party I 2008 01 07 09 02 18 10 70418060 Logcal Drive NOTICE Party Regene Descriptions below may contain abbreviations Abbreviations and Capitalized letters are preserved for the coherency with the event messages shown on the terminal session Troubleshooting 11 4 1 Logical Drive Events 4 1 1 Critical Message LG X Logical Drive ALERT CHL 0 ID 132 Drive Missing What The LD member drive could have been accidentally removed or Happened drive connection problems occurred before system boot up What to Do The drive could have been accidentally removed or drive connection problems occurred in the boot time Check drive connection and related enclosure status Message LG X Logical Drive ALERT CHL 0 ID 132 Drive Failure What The specified hard drive in the specified logical drive has failed Happened What to Do When a system is running removing any LD member disk or member disk failure will be recognized as disk failure event For example RAID controller cannot access a member disk and decides this drive has failed If a spare is available the subsystem will proceed with an automatic rebuild If there is no spare r
26. ate the Service ID by clicking on the LED icon in GAMs Enclosure View so that he can easily locate the faulty drive later Monitor Management Administrator La Initiates Service LED An engineer can then locate and replace the failed drive on the installation site Service LED O Locate amp Replace After servicing the subsystem the administrator should turn off this service LED by manually pressing the service button on the chassis or remotely using the GAM management software Troubleshooting 47 Appendix A Concerns for Replacing a Failed Controller There is a 1GB parameter threshold for NVRAM defaults in earlier Galaxy disk array firmware The 1GB threshold determines whether your RAID supports a standard or a large number of logical configurations by the size of cache memory NOTE that the 1GB threshold no longer applies to all HDX4 models ASIC667 All HDX4 models come with max numbers of logical configurations e g 32 LDs and 1024 LUNs The supported numbers by different DIMM sizes are shown below Posture Default Value lt 1GB DIMM gt 1GB DIMM 64 bitL BA Support gt 27B Yes Yes Number of LDs 16 Max 32 Max Number of LVs 8 Max 16 Max Number ofP artitions per LD 16 Max 64 Max Number of LUNs per Channel ID 8 32 Max 8 32 Max Number of LUNs 128 Max 1024 Max Optimization Mode Sequential 1 0 Caching Mo
27. ation with the SES remote device monitoring What to Do Check proper module installation and contact your RAID system supplier Message Peripheral Device ALERT CPU Cold Temperature Detected X X C error code What Happened Temperature below the lower CPU threshold is detected Improper installation site condition might have caused the situation Always acclimate a system to an appropriate room temperature before powering up What to Do Correct your installation site condition Contact your RAID system supplier Troubleshooting 33 Message Peripheral Device ALERT Elevated Temperature Alert What Happened High temperature threshold violated and detected through an I2C serial bus Insufficient cooling at the installation site or cooling fan failure might have caused the situation What to Do Correct your installation site ambient condition and cooling fan failure Contact your RAID system supplier if a replacement is necessary Message Peripheral Set 0 Device ALERT Backplane Temperature Failure Detected error code What Happened Temperature sensor on the backplane has failed or reported erroneous readings What to Do Contact your RAID system supplier Message Peripheral Set 0 Device ALERT Backplane Temperature Not Present error code What Happened IIC bus lost contact with the backplane sensor What to Do Contact your RAID system supplier Message Peripheral Set 0 Device ALERT Temperature Sensor 0 Not Prese
28. begun to Happened generate parity sectors and readying member drives The On line initialization mode takes a longer time to complete and allows the logical drive to receive host I Os immediately if appropriate host ID LUN mapping has been applied What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE On Line Initialization of Logical Drive Completed What Logical drive on line initialization completed Happened What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting Off Line Initialization What Creation process is completed initialization process has begun to Happened generate parity sectors and readying member drives The Off line initialization mode takes place immediately after the creation of a logical drive and does not allow host I Os to be distributed to the logical drive at the same time What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Off Line Initialization of Logical Drive Completed What Logical drive off line initialization completed The logical drive is Happened now ready for host ID LUN mapping and then receiving host I Os What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting On Line Expansion What Start expanding the logical drive s added or free capacity Happened previously not included when system find appropriate time after The parity regeneration process on logical drive _ is com
29. clear this message Message Peripheral Set 0 Device NOTICE PSUO 12V is Present What Happened Power supply module 0 restored normal 12V voltage range What to Do Press ESC to clear this message Message Peripheral Set 0 Device NOTICE PSUO 12V Back On Line 5 0V What Happened Power supply module 0 restored normal 12V voltage range What to Do Press ESC to clear this message Message SES CO 10 Power Supply X Power Supply Back On Line What Happened Power supply module 2 once missing or failed is now restored What to Do Press ESC to clear this message Message NOTICE UPS Connection Detected What Happened The COM2 serial link to UPS device is now valid What to Do Press ESC to clear this message Message NOTICE UPS AC Power Restored What Happened _ UPS reports AC power source is now restored What to Do Press ESC to clear this message Message NOTICE PS Battery Restored to Safe Level What Happened UPS battery is charged to a safe level able to protect cached data during system operation What to Do Press ESC to clear this message Message Peripheral Set X Device NOTICE UPS X AC Power Back On Line What Happened UPS 2 AC power source restored What to Do Press ESC to clear this message Message Peripheral Set X Device NOTICE UPS X Battery Back On Line What Happened UPS 2 Battery charge or battery failure restored What to Do Press ESC to clear this message 38 Galaxy DS Message What Happened
30. contact your RAID supplier Message Peripheral Set 0 Device ALERT Low Voltage Detected 5V error code What Happened Low voltage detected from the power supply Power supply may have become unstable What to Do Check proper module installation and contact your RAID supplier for a replacement module Message Peripheral Set 0 Device ALERT Cooling FanX Failure Detected error code What Happened Cooling fan failure detected through an 12C serial bus What to Do Check the Cooling Fan Status LED on the front rear panel of RAID SBOD system If the Amber LED is lit constantly that indicates at least one cooling fan within a module has failed Check your hardware manual for LED locations Contact your RAID supplier for a replacement module Message Peripheral Set 0 Device ALERT Cooling FanX Not Present error code What Happened No cooling fan module is installed in the expected module slot What to Do Check proper module installation or contact your RAID supplier for a replacement module Message Peripheral Set 0 Device ALERT Low Speed Detected XXXX RPM error code What Happened Low rotation speed detected on cooling fan This is a fault detected through an I2C serial bus What to Do Check proper module installation or contact your RAID supplier for a replacement module Message SES CO 10 Cooling Fan X Device Not Supported What Happened Unrecognizable device type This event may result from an incorrect configur
31. ct technical support for help Message Warning Incorrect unique ID d d for EBU data restored What Happened The flash module might have been installed to another controller causing problems with data transmission What to Do Contact technical support for help Message Warning Backed up Cached Data was stalled What Happened Cached data cannot be successfully distributed to flash memory What to Do Contact technical support for help 4 4 3 Notification Message NOTICE Force Controller Write Through on Trigger Cause What Happened Preset conditions e g elevated temperature or component failure has forced the subsystem to adopt a more conservative operating mode by disabling the Write Back caching What to Do Check proper working condition and correct system faults Press ESC to clear the message Message NOTICE Controller Default Write Policy Restore What Happened Controller write caching policy has been forcefully changed to a conservative Write through policy to avoid risk of losing data When the fault conditions have been corrected e g temp back to normal or voltage readings become normal the original Write Policy will return to normal What to Do Check if firmware synchronization is properly processed Message Firmware synchronization completed What Happened Refer to Appendix B for more information What to Do Check if firmware synchronization is properly processed Message NOTICE 12V Upper Voltage Back
32. de Default Write Back Stripe size O ptimization for Sequential Os RAID 5 128KB Auto assign Global Spare Disable Max LD capacity Optimization for Sequential 1 0 s 647 B Max No ofMedia Scan TaskSchedules 16 Max Max No of members per DIMM size RAID5 128 drives max 512MB Note that these numbers can be slightly different across different firmware revisions and in most situations 16 logical drive entries will be sufficient This parameter threshold however can cause problems if users upgrade DIMM modules to a larger size especially when combining two RAID controllers without knowing their NVRAM defaults The fault can also occur when replacing a faulty controller in a redundant controller configuration Fault Scenarios 1 Field side Upgrade 1 1 Customers upgrade controller DIMM modules e g from 2GB to 4GB 1 2 Combine controllers into a redundant configuration One retains the 1GB defaults while the other the gt 2GB defaults 2 Replacing a Failed Controller 2 1 Branch office acquires a replacement controller and upgrades its memory to the size of surviving controller 48 Galaxy DS 2 2 Though with the same memory size the replacement still retains the incongruous defaults The RAID system will report a Redundant Controller Failure event and the controllers will not work coherently Remedy Restore firmware defaults after installing changing the DIMM module You
33. e Abnormal LED Temp LED Abnormal temperature reading is detected the temperature is above the preset threshold setting Color Amber Behavior Steady On 6 Galaxy DS 4 Cache Backup Module LED CBM Status LED Off The BBU is not installed Steady On LED indicates that the CBM failed either BBU or Flash Backup Module or both failed Amber In redundant models it also indicates that no BBU Color and or Flash Backup Module are found Steady On LED indicates that the CBM is ready and Green the BBU and Flash Backup Module are both present Fast Blink LED indicates that the BBU is charging Behavior Steady On Fast Blink Off 5 Host Channel Busy LED Color Green The host port is busy there are activities Behavior Fast Blink 4Hz 6 Drive Channel Busy LED Color Green The drive port is busy there are activities Behavior Fast Blink 4Hz F W Restore Default LED Color Green The restore factory default handshake is ready Behavior Steady On For the definitions of LEDs on interface connectors and the LEDs of system modules please refer to the Hardware Manuals that came with your systems Troubleshooting 3 Fault Indication by Galaxy Array Manager GAM and Other Interfaces Event messages Remote console Email LAN broadcast SNMP traps
34. e logical drive members 4 System faults have occurred 5 If an LD is manually shut down or the controller is reset Add Drive will also be halted When the LD is re started or the controller is successfully rebooted the Add Drive Paused event will prompt reminding you of the incomplete process Also the same event will prompt if Parity Regeneration or Rebuild took place before an LD was manually shutdown or the controller was reset What to Do Carefully identify and replace the faulty drive and correct system faults The add drive expansion should continue once the faults are corrected Message LG X Logical Drive NOTICE Add Drive to Logical Drive Completed What The add drive expansion process is completed Happened What to Do Press ESC to clear the message Please remember to rearrange the added capacity which will appear as a new partition volume Message LG X Logical Drive NOTICE Migrate to Logical Drive Completed What The logical drive migration process is completed Happened What to Do Press ESC to clear the message Message NOTICE CHL X ID XXX Starting Media Scan What Media Scan is manually or automatically started by the preset Task Happened Schedules on a specific disk drive What to Do Press ESC to clear the message Message LG X NOTICE CHL 0 ID 1 32 Starting Media Scan What Media Scan is manually or automatically started by the preset Task Happened Schedules on a specific member drive of Logical Drive X
35. ed on bad drive sectors has been successfully re conducted from adjacent data blocks stripes onto the original drive blocks or distributed onto other healthy sectors Galaxy firmware translates SATA error codes into SCSI standard sense keys and sense codes That s the error codes at the end of message What to Do Press ESC to clear the message Message CHL _ NOTICE Fibre Channel Loop Connection Restored What Happened Specific Fibre Channel loop connection restored What to Do Check proper host or drive side activities Press ESC to clear the message 30 Galaxy DS Message CHL ID NOTICE Redundant Path for CHL Restored What Happened Redundant path one of the drive side loop members for CHL ID _ is restored What to Do Check proper host or drive side activities Press ESC to clear the message Message CHL NOTICE Redundant Path for CHL ID Restored What Happened The redundant path CHL _ connecting drive CHL _ ID _ is restored What to Do Check proper host or drive side activities Press ESC to clear the message Message CHL _ Host Channel Notification Bus Reset Issued What Happened Bus reset on the CHL host channel What to Do Check proper host or drive side activities Press ESC to clear the message Message CHL ID Drive NOTICE Scan Drive Successful What Happened A new drive or a replacement drive has been successfully scanned recognized by the subsystem What to Do Press ESC to clear t
36. eplace the faulty drive using a drive that is known to be good and rebuild will be automatically initiated provided that a replacement drive can be recognized by the subsystem For example in a SCSI based subsystem a manual Scan Drive command should be executed In subsystems using other types of disk drives drive swap auto detection should be enabled on the drive channels If all disk drives are lost inside an enclosure please check the related power supply status or backplane power connection Message LG X Logical Drive ALERT Rebuild Aborted Failed What Logical drive rebuild aborted It could result from the one of the Happened following reasons 1 The rebuild has been manually canceled by a user 2 The replacement drive used for a rebuild may have failed during the rebuild or the drive contains immanent defects 3 System faults for example an LD fatally failed occurred Another member disk failed in a rebuild process What to Do Carefully identify and replace the faulty drive and perform logical drive rebuild again It is best to stop host I Os temporarily to this logical drive Message LG X Logical Drive ALERT Parity Regeneration Aborted Failed What It could result from one of the following reasons Happened 1 The regenerate operation has been manually canceled by a user 2 System faults or integrity problems forced system to abandon the operation For example any single member disk failed ina LD will
37. ered Block 000000084 What Users execute regenerate parity operation and a parity Happened inconsistency is encountered Problematic block address is shown at the end of the message What to Do Parity inconsistency means the data is corrupted or invalid across some data blocks We recommend users to restore specific data from their routine backup Message LG X ALERT Inconsistent Parity Block 000000084 Regenerated What Users execute regenerate parity operation and a parity Happened inconsistency is encountered and regenerated Problematic block address is shown at the end of the message What to Do Parity inconsistency means the data is corrupted or invalid across some data blocks This message shows an inconsistent instance has been corrected Message LG X Logical Drive ALERT Cache Data Purged Troubleshooting 15 What Happened What to Do Message What Happened What to Do There can be two causes for a RAID system to purge its cached data that belongs to a specific LD 1 A fatal failure occurred on a specific LD the related cached data becomes useless and will be purged 2 Cached data is missing when system powers up e g in the event of power outage and the battery backup was not able to Support cached data System will check for the cached data and issue an alert event by each LD if the cache data is gone Data inconsistency may occur if power outage occurs when unfinished writes are still cached in mem
38. erved space What to Do Press ESC to clear the message Message NOTICE Controller BBU is Charging What Happened Once a new BBU is installed or BBU charge drops below a preconfigured level the subsystem will start charging its batteries What to Do Press ESC to clear the message All batteries have a limited life expectancy If this message appears too frequently the BBU may have gradually lost its ability to hold charge Message NOTICE Controller BBU is Present What Happened ABBU once missing or removed is now electrically connected to the subsystem What to Do Check proper working condition and press ESC to clear the message Message NOTICE Controller BBU Back On Line What Happened A BBU once missing or removed is now restored to its normal 44 Galaxy DS working condition What to Do Check proper working condition and press ESC to clear the message NOTICE Controller BBU Fully Charged Message What Happened What to Do A BBU is fully charged Check proper working condition and press ESC to clear the message NOTICE Redundant Controller Firmware Updated Message What Happened What to Do Firmware updated on a redundant controller RAID subsystem Resetting the subsystem may be required for the new firmware to take effect Updating firmware on a complex system configuration is recommended for experienced engineers only Unless for bug fixing updating firmware is not always necessary
39. fect What to Do Check proper installation of the module or contact your RAID system supplier for a replacement module Message WARN BBU Charger entered Self protection state error code What Happened The following conditions will cause the charger circuits to enter a low power and self protection state 1 The temperature sensor on the charger circuit reports elevated temperature reading gt 45 degree Celsius 2 The BBU battery cell pack has been charged for over 14 3 hours The BBU charger will enter a timer fault state What to Do 1 Check proper ventilation within the subsystem You may also check the readings from other sensors within the enclosure Airflow might have been disrupted by the absence of one or several major modules or the failure of a cooling fan Once the thermal condition is improved charging will resume automatically 2 If a new or totally discharged battery module has been charged for over 14 3 hours and this event is issued you may remove and re install the battery module An empty battery module may take more than 14 3 hours to be fully charged There is a timer embedded with the charger doing so can reset the timer Charging will resume automatically 3 Ifa BBU has been left unused for a long time it will be totally discharged and its usability may become a problem Message ALERT Force Controller Shutdown Start What Happened System start to shutdown triggered by user or other configured event
40. h the display of I2C error codes 1 Hardware module peripheral device failures such as those for PSU and cooling fans will not have an error code attached to the end of event messages 2 Peripheral Device Warning diicc indicates I2C bus communication errors Where Device Types lt d gt can be Voltage V PSU P FAN F Temperature T and BBU B lt li gt is Component index lt cc gt is the bus error type including 01 12C command NoAck 02 12C command timeout and 03 I2C command arbitration lost 3 lt NOTICE gt Peripheral Device Notification dii indicates I2C bus communication errors have been recovered 4 3 1 Critical Message Peripheral Set 0 Device ALERT PSUX Failure Detected error code What Happened Power supply failure detected through an 12C serial bus What to Do Check the Power Supply Status LED on the front panel of system or check the PSU Status LED on the power supply unit on the rear panel If the Amber LED is lit constantly that indicates that a power supply has failed 32 Galaxy DS If the LED is off check the power cord is connected correctly or the corresponding AC is intact Contact your RAID supplier for a replacement module Message Peripheral Set 0 Device ALERT PSUX Not Present error code What Happened No power supply module is installed in the expected module slot What to Do Check proper module installation If an installed module can not be detected
41. he message Message CHL ID Drive NOTIFY Block Successfully Reassigned 0 10B What Happened Writes conducted retried and media errors were discovered Writes will then be re directed to other drive sectors What to Do Press ESC to clear the message If this message becomes frequent the target disk drive might have developed serious media errors Message CHL ID Drive SEV Media Error Encountered What Happened Media errors are encountered in a hard drive What to Do Press ESC to clear the message If this message becomes frequent the target disk drive might have developed serious media errors Troubleshooting 31 4 3 General Target Events k IMPORTANT Firmware revision 3 63 added event strings for I2C slave devices The I2C device error is indicated by a bracketed message such as FANO status Failure Detected 2 by the end of a peripheral device event The cause of an error can be an I2C bus arbitration error bus timeout or a slave device content error NOTE In the event of dual PSU failure of a 4U RAID enclosure both the RAID controller and logical drives will enter a shutdown state for lack of wattage When the PSU failure is corrected users should manually power cycle the system to re activate system operation Error Code Definitions Exp Peripheral Set 0 Device ALERT PSUX Failure Detected error code Error codes are related to I2C bus communication errors Below are the conditions wit
42. identally removed or when cable links backplane traces connection become unreliable Check cabling and drive installation and contact your RAID system supplier Message CHL _ Drive Channel WARN Unexpected Select Timeout What Happened Drive Channel target select timeout The specified drive channel cannot be selected by the RAID controller subsystem Faults might have occurred with the cabling termination internal data paths What to Do Check cabling and drive installation and contact your RAID system supplier Message CHL _ RCC Channel WARN Gross Phase Signal Error Detected What Happened Phase signal abnormality detected on the specific RCC channel What to Do Rare occurrence of phase signal error could be recovered by firmware retry Contact your RAID system supplier Message CHL RCC Channel WARN Unexpected Select Timeout What Happened Phase signal abnormality detected on the specific RCC channel What to Do Rare occurrence of phase signal error could be recovered by firmware retry Contact your RAID system supplier Message CHL ID 0 Target WARN Gross Phase Signal Error Detected What Happened Phase signal abnormality detected with a specific target disk drive What to Do Check proper installation of disk drives or cabling and contact your RAID system supplier Message CHL _ Drive Channel WARN Gross Phase Signal Error Detected What Happened Phase signal abnormality detected on the specific drive channel T
43. irmware Check disk drive connection and contact your RAID system supplier Message CHL Drive Channel WARN Unit Attention Received 10B What Happened Drive side target unit attention received on a drive channel CHL What to Do Rare occurrence of these errors can be managed by firmware Check proper installation and contact your RAID system supplier Message CHL ID Drive WARN Aborted Command 00B What Happened Aborted command reported from a disk drive CHL ID _ What to Do Rare occurrence of these errors can be managed by firmware This can indicate a drive failure Contact your RAID system supplier for a replacement drive Message CHL ID Drive WARN Unexpected Sense Received 00B What Happened Drive side target unexpected sense received on a disk drive CHL ID What to Do Check drive side cabling installation working conditions This may result from bad signal guality or poor connection Contact your RAID system supplier Message CHL ID Drive WARN Block Reassignment Failed 0 10B What Happened Data regeneration and reassignment failed The Bad Block Table is full Too many bad blocks have been found on the disk drive The adjacent data blocks on other member drives might have also been damaged What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL RCC Channel WARN Data Overrun Underrun Detected What Happened Data overrun underrun err
44. is available since firmware revision 3 64P 2 This feature only works with redundant controllers running firmware revision 3 64P or later 52 Galaxy DS HORKE An Avnet Company DATA D www rorke com An Avnet Company
45. lashes blue Off indicates there is no activities on the disk drive A drive error may not be detected before the RAID system firmware access the disk drive or before I Os are distributed to it Drive Ready When lit green the drive bay is populated and the drive is healthy When lit ready faults have occurred to the disk drive the drive is not ready Troubleshooting 5 2 3 Controller LEDs Galaxy HDX4 series Ethernet port FC port LEDs ve me Restore default Controller LEDs button LED RAID Subsystem LED Definition 1 Controller Status LED Ctrl Status LED Green The controller is active and operating normally Color The controller is going through the initialization process Amber Or The controller is not ready for operation Behavior Steady On 2 Cache Dirty LED C_Dirty LED Off No data is in the cache memory The BBU unit can sustain memory in case of power loss Steady On LED indicates the followings There is data in the cache memory An error has occurred in the cache memory ECC errors Color Cached data is being sustained by the BBU Amber Battery voltage is lower than 2 5V Battery temperature is abnormal The BBU is not present Fast Blink LED indicates that data in the cache memory is being written to the Flash Backup Module during power outage Steady On Fast Blink Behavior Off 3 Temperatur
46. le disk failure The expansion operation will not continue after Troubleshooting 13 the rebuild is completed Users have to start the expand process again Message LG X Logical Drive ALERT CHL 0 ID 132 Clone Failed Aborted What Drive cloning failed It could result from one of the following Happened reasons 1 Cloning has been canceled by a user 2 The LD contains the source drive is fatal failed during the cloning process 3 The source drive used for cloning has failed during the cloning process 4 The target drive used for cloning has failed during the cloning process What to Do If the Logical Disk has fatally failed then the cloning operation stops If the source drive fails then system firmware will proceed with the following 1 If a spare drive is available then LD will stop cloning and begins a rebuild using the available spare drive 2 If no spare drive is available then LD will stop cloning and start rebuild using the target drive the target drive was originally a spare drive If the target drive fails then cloning will stop Carefully identify and replace the faulty drive Then restart the cloning operation Message LG X Logical Drive ALERT Logical Drive Bad Block Table FULL What There are too many damaged sectors and firmware used up the Happened available bad block table entries Bad blocks have been discovered and marked by write operations including host write commands disk clone Add
47. lled The drive could have been accidentally removed or drive connection problems occurred in the boot time Check drive connection and related enclosure status LG X ALERT CHL 0 ID 132 Media Scan Aborted Media Scan operation is aborted for certain reasons e g it has Happened been manually canceled What to Do Check disk drive and system operation status The following events are related to the Shutdown Restart Logical Drive function a k a LD Roaming Message What Happened What to Do Message What Happened LG X Logical Drive SEV State change from on line to off line Event shown when a logical drive is manually pulled off lined Then its members can be moved to another enclosure and then the logical drive restarted Note that you must note the slot numbers of member drives so that you will not swap the wrong drives Press ESC to clear the message LG X Logical Drive SEV State change from off line to on line Event shown when a logical drive is manually brought on line When all its members are present a shutdown off line logical drive can be brought on line You should then perform LUN mapping to the logical drive if it has been moved from other enclosure to the present location Troubleshooting 23 What to Do Press ESC to clear the message Message LG X Logical Drive SEV Remove member drives complete What Event shown when all members of a shutdown logical drive are Happened removed
48. locked by controller During controller initialization iy SON a FW download completed RAID ON 4 Any logical drive stated as not GOOD __ RAID ON 4 Replacing a faulty controller will silence the currently sounded buzzer Troubleshooting Buzzer Sound Patterns Pattern 1 Repeat until process is done SY SY SD ess 250ms 250ms 250ms 250ms 250m Pattern 2 Repeat until any failure is corrected Repeat until any failure is corrected Repeated twice Pattern 5 Buzzer is sounded continuously Buzzer On 4 Galaxy DS 2 Fault Indication by LEDs 2 1 LCD Panel LEDs During the boot up process the ATTEN LED will light up for several seconds After the power on self test the LED should go off if no fault is detected When the boot up process is finished and the Galaxy enclosure if functioning normally e The PWR LED should light constantly blue e The ATTN LED should remain off e The BUSY LED lights up when the system is processing I Os Any system faults from a component failure to a reading exceeding the preset threshold will trigger the ATTN LED NOTE For some specialized models that come without LCD panel please refer to its Hardware manual for LED definitions 2 2 Drive Tray LEDs Drive Ready k Drive Busy Drive Busy When a disk drive is spinning servicing host I O requests the LED f
49. lure during initialization for all types of RAID configuration RO 1 3 5 6 2 On Line Initialization Failed This event can result from fatal failure of a logical drive for example two disk drives failed during the initialization process fora RAID 5 LD and three disk drives failed for a RAID 6 LD What to Do For off line initialization carefully identify and replace the faulty drive and perform create logical drive again For on line initialization reboot system and check the LD 1 If LD can be restored to the degraded mode then the initialization process will continue 2 If the LD cannot be restored then you have to replace the failed disks recreate the LD and restore data from a previous data backup Message LG X Logical Drive ALERT Expansion Aborted Failed What Logical drive expansion failed It could result from one of the Happened following reasons 1 The expansion has been canceled by a user 2 For On line expansion an expansion operation is terminated when the target LD fatally fails 3 For Off line expansion an expansion operation fails when any of its member drives fails What to Do Carefully identify and replace the faulty drive and perform logical drive rebuild first For an online expansion the expansion operation should continue with a single drive failure When the LD rebuild process is completed the LD will resume the expansion process For an off line expansion the expansion will be discontinued by a sing
50. nd contact your RAID system supplier Message SES CO 10 Temp Sensor X Device Not Supported What Happened Unrecognizable device type This event may result from an incorrect configuration with the SES remote device monitoring What to Do Check proper module installation and contact your RAID system supplier Message SES CO 10 UPS X ALERT Device Not Supported What Happened Unrecognizable device type This event may result from an incorrect configuration with the SES remote device monitoring What to Do Check proper module installation and contact your RAID system supplier The type of attached UPS may not be supported Message SES CO 10 UPS 2 Device Not Supported What Happened Unrecognizable device type This event may result from an incorrect configuration with the SES remote device monitoring What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do Message Check proper module installation and contact your RAID system supplier ALERT UPS Connection Is Absent The COM2 link to a UPS device is absent Check cabling to the UPS device If hardware faults occurred contact your RAID system supplier ALERT UPS AC Power Loss Detected UPS AC power loss reported through the COM2 serial port connection Contact your UPS supplier ALERT UPS Battery Low __ UPS battery charge low may not be able to
51. ndicates the location where the event occurred e g O RAID enclosure 1 attached JBOD Sensor is now present on the backplane Press ESC to clear this message Troubleshooting 39 4 4 Controller Events 4 4 1 Critical Message License key data consistency check failed What This could occur when installing a HDX HDX2 or HD X3 controller Happened to an HDX4 enclosure The license key verifies system serial number against the applied features This may also occur when the license key is due What to Do Contact Galaxy s technical support and provide them with the information of current firmware revision Message License key not supported by install FW What This could occur when you apply Galaxy HDX4 DS firmware to an Happened enclosure running earlier HDX HDX2 or HDX3 firmware RAID controllers cannot be swapped between different storage models including Galaxy HDX HDX2 HDX3 and HDX4 What to Do Contact Galaxy s technical support and provide them with the information of current firmware revision Message ALERT 3 3V Low Voltage Detected V error code What Happened The detected 3 3V voltage source is lower than the preset voltage threshold What to Do 1 Check power supply working condition 2 Check voltage threshold settings if you do not know the appropriate threshold value for voltage monitoring please use the default setting for voltage threshold 3 If the alert still occurs then it can result from
52. ned What to Do data blocks Restoring data from a backup is recommended LG X Logical Drive ALERT Media Error During Check Parity Recovered 000000000 Data blocks affected by Media errors are recovered by comparing and regenerating data from otner members of a logical drive If the Media Errors and Recovery events appear too often on a specific disk drive that drive might have become unreliable You may consider replacing it using the Copy and Replace function 4 1 2 Notification Message LG X Logical Drive NOTICE Continue Rebuild Operation What The target logical drive has been stored to its previous Happened one drive failed status and the rebuild operation is automatically resumed by firmware This may occur when the system is powered off or reset during the rebuild process or that media errors have been discovered and corrected during the rebuild What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting Rebuild What The rebuild process has begun Happened What to Do This is the message displayed when a stand by spare is available when a member drive fails or when a faulty drive is physically replaced The subsystem should automatically detect a drive for rebuild if the hot swap detection mechanism has been enabled Message LG X Logical Drive NOTICE Rebuild of Logical Drive Completed What The subsystem has successfully rebuilt a logical drive Happened What to Do Press ESC to clea
53. ng or failed is restored and the PRM reading displays This applies to enclosure implementations using cooling fans capable of reporting rotation speed What to Do Press ESC to clear this message Message SES CO 10 Cooling Fan X Fan Back On Line What Happened A cooling fan once missing or failed is restored This message is reported through an SES monitoring device What to Do Press ESC to clear this message Message Peripheral Set 1 Device NOTICE Temperature 1 Back To Non Critical LVs What Happened Temperature sensor 1 reports operating temperature is now within normal temperature range What to Do Press ESC to clear this message Message Peripheral Set 1 Device NOTICE Temperature 1 is Present What Happened Temperature sensor 1 once missing and is now present on the serial bus What to Do Press ESC to clear this message Troubleshooting 37 Message SES CO 10 Temp Sensor X Temperature Back to Non Critical LVs What Happened Temperature sensor 1 reports operating temperature is now within normal temperature range What to Do Press ESC to clear this message Message NOTICE Power Supply X Back Online What Happened Power supply module 0 is back online Shown when a failed PSU is replaced or re installed What to Do Press ESC to clear this message Message Peripheral Set 0 Device NOTICE PSUO 12V Back On Line What Happened Power supply module 0 restored normal 12V voltage range What to Do Press ESC to
54. nt What Happened Temperature sensor failed or serial bus configuration connection faults occurred What to Do Contact your RAID system supplier Message Peripheral Set 0 Device ALERT Cold Detected X X C error code What Happened Temperature dropped below the lower system threshold detected Improper installation site condition might have caused the situation What to Do Correct your installation site condition Contact your RAID system supplier Message Peripheral Set 0 Device ALERT Hot Detected X X C error code What Happened Temperature rises above the higher system threshold detected Improper installation site condition or cooling fan failure might have caused the situation What to Do Correct your installation site condition Contact your RAID system supplier Message SES CO 10 Power Supply X Device Not Supported What Happened Unrecognizable device type This event may result from an incorrect configuration with the SES remote device monitoring You might have inserted a wrong type of PSU from a similar Galaxy model PSUs for different Galaxy models may look similar What to Do Check proper module installation and contact your RAID system supplier Message SES CO 10 Cooling Fan X Device Not Supported 34 Galaxy DS What Happened Unrecognizable device type This event may result from an incorrect configuration with the SES remote device monitoring What to Do Check proper module installation a
55. o member disks are back then LD will be rebuilt If the LD cannot be restored then you have to replace the failed 16 Galaxy DS Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do disks recreate the LD and restore data from a backup source LG X Logical Drive ALERT Add Drive Operation Paused The Add Drive expansion process is paused The reason could be 1 User cancelled the add drive process 2 Thedrive to be added is faulty 3 The drive to be added has incongruous drive size e g smaller than the LD members 4 The logical drive into which the drive will be added has a drive that just failed Check drive and LD status replace a failed drive or re start the add drive process if you manually cancelled it LG X Logical Drive ALERT Migrate Operation Paused The logical drive migration process is paused The reason could be 1 User cancelled the migration process 2 One drive involved has failed 3 The target logical drive has fatally failed 4 Insufficient no of LD size e g when migrating from RAID5 to RAID6 another member drive is required for the additional parity You should expand the logical drive first by adding another member 5 The logical drive to be migrated has a failed drive The process can re enacted after a successful rebuild Check drive and LD status replace a failed dri
56. ors detected on the RCC channel CHL What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL ID Target WARN Data Overrun Underrun Detected What Happened Data overrun underrun errors detected on a disk drive CHL _ ID What to Do Rare occurrence of these errors can be managed by firmware Troubleshooting 27 Contact your RAID system supplier Message CHL _ Drive Channel WARN Data Overrun Underrun Detected What Happened Data overrun underrun errors detected on the drive channel CHL What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL _ RCC Channel WARN Negotiation Error Detected What Happened Negotiation errors occurred on the RCC channel CHL _ What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL ID Target WARN Negotiation Error Detected What Happened Negotiation errors occurred with the communications with a disk drive CHL _ ID _ The event could also occur with drive target data bus sync wide negotiation abnormality What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL _ Drive Channel WARN Negotiation Error Detected What Happened Negotiation errors occurred with the communications over a drive channel CHL _ The event could also occur with d
57. ory If this event occurs it means the cached data for this LD could have been corrupted or invalid The LD will be put into an off line state Users have to manually check the integrity of data and try to recover data before proceeding with any actions It is recommended to restore data from your routine backup LG X Logical Drive ALERT Fatal Fail Invalid Array Incomplete arra Fatal failure or incomplete array means that the LD has lost the protection by RAID configuration If system cannot find some member disks for a specific LD at boot time the LD will be considered as incomplete If some member disks of a specific LD fail during operation the LD will be considered as fatally failed The possible causes include 1 For RAID 5 two member disks have failed or are missing 2 For RAID 6 three member disks have failed or are missing 3 For RAID 1 two member disks have failed or are missing in the same mirror pair The locations of mirrored drives are somehow difficult to decipher Shown below is an example of mirror pair relationship which shows a RAID1 made of six members ig E e 112 13 4 5 6 RAID1 Oo M 112 3 x 5 6 7 RAID 1 hot spare joined a rebuild 4 One disk failed or missing in a RAID O NRAID configuration The LD is not available at boot time or running time If an LD has fatally failed you may try to restart the RAID system and check if the system detects the failed disks If one or tw
58. ory size does not support current configuration Try using a DIMM module of a larger size What to Do Check proper installation of the module or contact your RAID system supplier for a certified module Message WARN Controller Memory ECC Multi bits Error Detected 1 no _ slot 1 onboard What Happened Mostly results from cache memory faults What to Do Contact system supplier for a replacement DIMM module Message WARN Controller Memory ECC Single bit Error Detected 1 What Happened _ Data bus signal errors What to Do Contact technical support for help Message Warning Wrong EBU inserted What Happened A wrong type of EBU is installed to controller What to Do Contact and verify with your system vendor for a replacement Message Warning Restore EBU data failed What Happened Data kept in EBU also known as CBM during power outage has failed What to Do Contact technical support for help Message Warning Firmware cannot recognize the format of backed up Cached data What Happened Data comparison errors occur with data saved to the CBM flash 42 Galaxy DS module Data inconsistency could have occurred when data is distributed to flash module in a power outage What to Do Contact technical support for help Message Warning Inconsistent Installed Memory for Cached Data MB Restored What Happened Inconsistent DIMM module type or size that does not allow data retrieval from flash module What to Do Conta
59. pleted selecting to expand its capacity The On Line mode allows the added capacity of a logical drive to appear immediately as a usable Troubleshooting 19 What to Do Message partition and ready for host I Os This partition may require being associated with a separate ID LUN on the host bus Response to host I Os will be slower because the expansion process requires distributing data blocks and parity data across new drive sectors Press ESC to clear the message LG X Logical Drive NOTICE On Line Expansion of Logical Drive Completed What Logical drive on line expansion completed The added capacity will Happened appear as a new partition and this partition may require being associated with a separate ID LUN on the host bus Adjustments should also be made through the host OS volume management utility What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting Off Line Expansion What Start expanding the logical drive s added or free capacity Happened previously not included when system find appropriate time after selecting to expand its capacity The Off Line mode does not allow the added capacity of a logical drive to be immediately available for host I Os This partition can only be associated with a separate ID LUN on the host bus after the expansion process is completed Access to the data already stored on the logical drive is not affected What to Do Press ESC to clear the
60. r the message Message LG X Logical Drive NOTICE Continue Parity Regeneration Operation What The parity regeneration process continues to execute Happened What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting Parity Regeneration What Start regenerating parity of a logical drive Happened What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Parity Regeneration of Logical Drive Completed 18 Galaxy DS What Happened What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting Creation What Logical drive creation process started Note that the creation and Happened initialization processes are separated Creation of a logical drive only takes a second while the initialization may take hours with the arrays containing numerous large capacity drives What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Creation of Logical Drive Completed What A logical drive is created Note that the initialization runs in the Happened background If a logical drive is created using the Online mode you can continue with the host LUN mapping etc Yet you cannot proceed with Add Drive or Parity Regeneration until the background initialization is completed What to Do Press ESC to clear the message Message LG X Logical Drive NOTICE Starting On Line Initialization What Creation process is completed initialization process has
61. rive target data bus sync wide negotiation abnormality What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL _ RCC Channel WARN Invalid Status Sense Data Received What Happened Invalid status sense data received on the RCC channel CHL _ What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL ID Target WARN Invalid Status Sense Data Received 10B What Happened _ Invalid status sense data received by a disk drive CHL ID What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL _ Drive Channel WARN Invalid Status Sense Data Received What Happened Invalid status sense data received on the drive channel CHL _ What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL _ WARN Redundant Loop Connection Error Detected on ID What Happened One of the dual loop members might have failed or been disconnected Make sure all cabling are properly connected and topological configurations properly set What to Do Check cabling and channel bus working conditions If the problem does not result from cabling problems contact your RAID system supplier 28 Galaxy DS Message What Happened What to Do Message What Happened What to Do Message What Happened CHL Hos
62. roubleshooting 25 What to Do Contact your RAID system supplier Message CHL RCC Channel WARN Timeout Waiting for I O to Complete What Happened __ O timeout on specific RCC channel What to Do Contact your RAID system supplier Message CHL ID Target WARN Timeout Waiting for I O to Complete What Happened Drive side target I O timeout Possible drive side cabling termination and canister connection abnormal or drive malfunctioning What to Do Check drive side cabling termination canister disk drive connections and contact your RAID system supplier Message CHL Drive Channel WARN Timeout Waiting for I O to Complete What Happened O timeout on specific drive channel What to Do Contact your RAID system supplier Message CHL RCC Channel WARN Parity CRC Error Detected What Happened RCC channel parity or CRC errors detected What to Do Rare occurrence of these errors can be managed by firmware Contact your RAID system supplier Message CHL ID Host Channel WARN Parity CRC Error Detected What Happened Parity or CRC errors detected through host channel ID CHL_ ID What to Do Occurrences of these faults usually can be negotiated between RAID subsystems and application servers If occurrences become frequent contact your RAID system supplier Message CHL _ Host Channel WARN Parity CRC Error Detected What Happened Host channel parity or CRC errors detected Problems with HBA or host link cables may al
63. so result in this event What to Do Parity and CRC faults can often be negotiated between application servers and RAID subsystems Contact your RAID system supplier if this occurs too frequently Message CHL ID Drive WARN Unexpected Drive Not Ready 00B What Happened Unexpected drive not ready returned from a disk drive on CHL _ ID What to Do Check proper installation of disk drives or cabling connection This event often occurs when hot swapping disk drives and may be caused by signal glitches When swapping a disk drive always be careful and gentle If the disk drive fails to respond the subsystem should consider the disk drive as a failed drive when the timeout threshold is reached Contact your RAID system supplier Message CHL ID Drive WARN Drive HW Error 00B What Happened Drive hardware error returned from a disk drive on CHL ID What to Do The target disk drive may have failed Contact your RAID system supplier for a replacement 26 Galaxy DS Message CHL RCC Channel WARN Unit Attention Received What Happened Unit attention received from RCC channel CHL What to Do Rare occurrences of these errors can be managed by firmware If the problem is not resolved contact your RAID system supplier Message CHL ID Target WARN Unit Attention Received 10B What Happened Drive side target unit attention received on a disk drive CHL _ ID What to Do Rare occurrence of these errors can be managed by f
64. support subsystem during a power outage Wait for the UPS to recharge or you may use the Event Triggered mechanisms implemented with firmware These mechanisms use conservative write through caching mode to reduce the chance of data loss in the event of power outage Contact your UPS supplier Peripheral Set 0 Device ALERT UPS X AC Power Failure Detected AC power source failure reported by UPS and to the subsystem firmware through an 12C serial bus Check your power source connection or contact your RAID system supplier Peripheral Set 0 Device ALERT UPS X Battery Failure Detected Troubleshooting 35 What Happened UPS battery failure reported by UPS and to the subsystem firmware through an 12C serial bus What to Do Contact your UPS supplier Message ALERT Redundant Controller Failure Detected What Happened One RAID controller in a controller pair has failed Check if the failover process runs smoothly You may need to reduce the workload on the storage system having a single controller failure because the surviving controller takes over all the workload on the failed controller What to Do Contact your system supplier for a replacement Message ALERT Enclosure ID Conflict Invalid What Happened Incorrect enclosure ID setting What to Do Check ID rotary switch at the front of RAID or SBOD enclosures Some enclosures have related DIP switches that might have been accidentally flipped to wrong configuration A RAI
65. t Channel WARN Channel Failure Host channel CHL link failure or disconnection occurred Check proper cabling connection and host HBA link connection devices etc Contact your RAID system supplier WARN SMART Slot _ Predictable Failure Detected Clone Failed Hard drive s report SMART detected defects A spare drive is commenced to clone or replace the member drive showing defects The cloning operation failed The member drive suspected of errors might have failed or the clone process has been interrupted e g yet another member has failed or the spare drive used for cloning has shown immanent faults Carefully check drive status and replace the unstable failed drive Contact your RAID system supplier WARN SMART Slot _ Predictable Failure Detected Hard drive slot reported SMART detected errors e g abnormal rotation speed seek time delay etc What to Do Carefully check drive status and replace the unstable failed drive Contact your RAID system supplier Message What Happened What to Do Message What Happened What to Do Message What Happened What to Do Message What Happened WARN SMART Slot _ Clone One or more hard drive s reports SMART detected defects Starts using a pre defined spare drive to clone the member drive suspected of inherent errors This happens when SMART detection is enabled with the Copy amp Replace or Perpetual Clone reaction schemes Press ESC to clear
66. ts Automated Synchronization eliminates the needs to manually upgrade or downgrade firmware of a replacement in order to comply with firmware on a running system Synchronization Flow Online Replacement Off line Replacement SlotA A SlotA A SlotB B SlotB B T Controller Replaced Controller E T boot SlotA SlotA SlotA Slot B Slot B Slot B ctrl FW replaces Slot A ctrl FW replaces 1 If Slot A ctrl comes 1 If Slot B ctrl comes Slot A FW Slot B FW with new FW with new FW Slot A ctrl FW replaces Slot B ctrl FW replaces Slot B FW Slot A FW If Slot A ctrl comes Ctrl B becomes Primary with same FW Slot A If system is reset later reclaims Primary role Ctrl Aresumes the Primary role More Details 1 Online Replacement When the synchronization process is completed the replacement controller will automatically restore defaults and reset itself to complete the process 2 Status Indication 2 1 On a terminal screen the redundant controller status will be indicated as Firmware synchronizing in the View and Edit Peripheral Device sub menu 2 2 The Controller Status LED will blink Green and Amber during the synchronization process Troubleshooting 51 Ctrl status LED 2 3 The corresponding LED icon will also blink on the GAM Embedded RAIDWatch Enclosure View 3 The LED will turn solid Green when the process is completed Limitations 1 This feature
67. ve or re start the process if you manually cancelled it CHL ID ALERT Media Error Unrecoverable 0x0 Media errors are found during read operations and the errors can or cannot be recovered The causes include 1 Media errors are found in an unprotected array e g a RAIDO and NRAID configuration 2 Media errors are found in a degraded array e g a RAID 5 array with a failed disk Drive failure and the media errors on other members failed the recovery attempt 3 Concurrent occurrences of media errors found on the same stripe across two member drives Host receives a media error response for the specific logical block address related to the physical bad block The data affected by data blocks failure will be lost The host computer will return media error messages if host access falls on the affected data blocks Restoring data from a backup source is recommended LG X ALERT Media Error Encountered During Check Parity 000000000 Media errors are found during parity regeneration process and the errors can or cannot be recovered If data blocks and parity are intact on other members of a logical drive the errors can be corrected by regenerating and writing data to other disk sectors If the data blocks on the bad media can not be regenerated the data affected by media errors will be lost The host computer will return media error messages if host access falls on the affected Troubleshooting 17 Message What Happe
68. y any person of such revisions or changes Product specifications are also subject to change without prior notice Trademarks Galaxy and the Galaxy logo are registered trademarks of Rorke Data All other names brands products or services are trademarks or registered trademarks of their respective owners Troubleshooting 1 Table of Contents Contact Information s a Z NTN NI I TA EE nave E E EE EE E Copyright 2010 00o0onnnnnnnonnnnnnnnn This Edition First Published 2010 Disclaimer Trademarks Table of Contents T BUZZ e aare aa n rea aa 4 4 4 4 1 2 Aas 2 Fault Indication by LEDs aD 5 5 6 8 2 1 LCD Panel LEDs 2 2 Drive Tray LEDs 2 3 Controller LEDs 3 Fault Indication by Galaxy Array Manager GAM and Other Interfaces 4 Event Messages and Corrective ACtiONS cecceeeceeeseeeneeceneeseeeeeeeeceaeesaeeeeaeeceaeesaeeseaeeseeeseeesiaeereeeen 11 4 1 Logical Drive Events 4 1 1 Critical AiO Critical nasa oll NI Aa eee Deets 25 AO O NV AMINO ratio I E A b odp in ON o nora ro va 25 4 23 NAt ICAtiON zi ie zos NEON NTN TN NE UNA 30 4 3 General Target EVeMmts sie piret r rn nan a ran ln r 32 4 3 A Gritical ku ON BR a 32 4 3 2 Notification Jaslene ee orn eta Ea ae aa aE a aaas 36 4 4 Controller Events soooooonosnn on tn RE 40 AA TA ie estenayed EE Ae EE E Ea A NEETER UET

Troubleshooting Guide - Rorke Data

Contents

Download Pdf Manuals

Related Search

Related Contents