No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Unable to Power on the S5300 Due to a Faulty Controller

Publication Date:  2012-07-20 Views:  74 Downloads:  0
Issue Description
At a commercial deployment, the customer's equipment room encounters unexpected power-off. After the power supply is recovered, the management network port of the S5300 cannot be pinged through, and the OSM cannot be logged in to. Meanwhile, only the global fault indicator on the front panel lights red. No enclosure ID is displayed on both controller modules. By executing the showsys command in CLI mode, the controller software version but not the product name can be detected. By executing the showallver command, the SES version cannot be detected.
Alarm Information
Handling Process
1. For the login failure of the serial port: During an attempt of logging in to controller A through the serial port, users encounter error messages stating incorrect password or persistent unresponsiveness after entering the correct user name and password. The same symptom occurs during an attempt of logging in to controller B. The problem is probably caused by the power-on failure. Forcibly power off the S5300 by removing the BBU module. Wait for approximately five minutes and then power on the S5300. The S5300 can be accessed through the serial port. 2. For the power-on failure: Log in to controller A, and switch to the debug mode and then the mml mode. Execute the sys status command to view the storage system status. spu ui>sys status Double Or Single : [ single ] Master Or Slave : [ master ] Local Controller Status : [ normal ] Peer Controller Status : [ abnormal ] System Running Status : [ power on ] System error reason : [ master DEV start VAULT failed ] spu ui>dev failreason initiator did not notify events. spu ui>ini sn 20 port index is wrong The port error occurs during an attempt of accessing the DE4 chip. Therefore, the DE4 chip of controller A is faulty. 3. Solution: By removing the questionable controller A and then removing and inserting controller B, the S5300 can be properly powered on.
Root Cause
The controllers are not properly powered on.
For S5000 and earlier, both controllers must stay in the normal state for proper start of the storage device. In this case, the storage device encounters the power-on failure due to a faulty controller.