[Problem Information]
Table 1 Basic information about the problem
Information Name Information Content
Storage Type Centralized Storage
Product Version V5 Kunpeng
Fault type: The controller cannot be powered on after being replaced.
Keyword controller, powering on
[Symptom]
The Kunpeng controller of the 5300 V5 is faulty. After the controller is replaced with another device, the controller cannot be powered on.
[Troubleshooting Roadmap]
1. Log in to the CLI of the main control board, access the minisystem, and run the showsystrace 11 command to check the step where the standby controller fails to be powered on. If the step is getnodeinfo, run the cache.sh clearcoffer command on the new controller and restart the controller.
2. If the fault occurs at NtfClsUtil(CCDB/DLM/C-CLS), perform the following operations to restore the fault:
1) Run the following command on the new controller:
ccdb.sh -c clearccdb local (Note that this step will stop the ccdb service of the entire cluster, affecting configuration services.)
2) Log in to all other controllers and run the ccdb.sh -c startccdb local command to restart the CCDB.
3. Run the cmm.sh -c setmrfi command on the new controller, and then run the rebootsys command to restart the controller.
4) If the fault persists, collect logs and contact R&D engineers for analysis.
[Cause]
The controller removed from another device has residual data of other devices. As a result, the verification on the current storage device fails.
[Solution]
Refer to the locating method.
[Post-Recovery Check]
The system can be started normally.
[Suggestion and Summary]
None
[Applicability]
V3R6C20, V5R7C10 and later, and V6 storage
