How to Troubleshoot the Power-on Failure During the Oceanspace S2300 Deployment Process?

Publication Date:  2012-07-22 Views:  268 Downloads:  0
Issue Description
The Oceanspace S2300 fails to be powered on during its deployment. A power-on failure alarm is generated on the Alarm page of the OSM.
Alarm Information
None
Handling Process
The following three methods are recommended to perform with priority. If the fault persists, the system logs need to be analyzed to further locate the fault.
  1. Run the cleancofferdb command on the CLI to clear the DB information stored in coffer disks. Note the following when running this command:
    • In a dual-controller system, the command can be executed only on the primary controller.
    • Running this command will clear all configuration data in the storage system. Use this command with caution.
    • After running this command, you are required to enter the password. The default password is 654321.
The operation procedure is as follows:
  1. Log in to the S2300 by using the serial port.
  2. Enter the admin mode, and run the cleancofferdb command.
The following messages are displayed:
OceanStor: admin> cleancofferdb
Enter Password:
this operation will lead to clean up the DB configuration!
do you want to continue? y or n: y
  1. Enter y for confirmation. The DB information is cleared, and then the storage system automatically restarts.
  1. During the initial deployment of the S2300, hard disks in slots 0 to 3 can be replaced with hard disks in other slots. In this way, the system DB information is cleared as well. Comparing with the first method, this method is easier to operate.
During the power-on process, the information of the dual controllers needs to be synchronized. If one controller is powered on but the other fails, the power-on of the whole storage system fails. To avoid this failure, it is recommended to power on the dual controllers in sequence: Remove one controller from the controller enclosure. Power on the other controller. Insert the first controller after its peer is successfully powered on. The information of controller A and that of controller B is automatically synchronized.
Root Cause
The cause of the system power-on failure varies, including the information synchronization failure between controller A and controller B or the incorrect DB information.
Suggestions
During the deployment process, some quick solutions need to be learned about to shorten the deployment process and reduce unnecessary troubles.

END