What Can I Do When an Exception Occurs in Using SmartKit to Add a New Controller Enclosure?

Prerequisites

• This section applies only to controller expansion by adding controller enclosures.
• If SmartKit pauses unexpectedly when adding controller enclosures, you must confirm the fault information and troubleshoot the fault accordingly.
• All faults before the Capacity Expansion step of the controller expansion wizard are considered preparation exceptions. They are not covered in this section.

Troubleshooting Flowchart

Procedure

1. Confirm the fault information on SmartKit.
   • If any expansion item fails and the system reports "The communication is abnormal or the system is busy", the connection between SmartKit and the storage system is interrupted. Go to 2.
   • If any expansion item is paused unexpectedly, a fault occurs during the expansion. Rectify the fault according to the suggestions provided by SmartKit and then click Re-Execute. If the item is paused again, the fault still exists. Go to 8.

2. Log in to the original controller of the storage system using the management network port. If this is your first login after the fault occurred, the controller may be powering up and you need to wait for about 10 minutes before the login. Then check whether you can access the CLI.
   • If yes, go to 3.
   • If no, go to 4.

3. Run change user_mode current_mode user_mode=developer to enter the developer mode. Then run minisystem to switch to the minisystem mode. Run sys.sh showflowstatus and check whether the original controllers of the storage system are normal.
   • If yes, go to 7.
   • If no, go to 8.

4. Check whether the controller can be logged in to and is powering up.
   • If you can log in to the controller, run minisystem to enter the minisystem mode and then run showsystrace 8 to check the controller status. If the controller status is NODE_POWER_ON: Wait PCIe switch up, the controller is powering up. Wait for about 25 minutes and then perform 2 again.

   • If you can log in to the controller but it is not powering up, rectify the fault according to the suggestions provided by the tool and go to 5. If no suggestion is provided, go to 8.
   • If you cannot log in to the controller, go to 8.

5. After the fault is rectified, log in to the new controller using the serial port or management network port. If this is your first login, the controller may be powering up and you need to wait for about 10 minutes before the login. Then check whether you can access the CLI.
   • If yes, go to 6.
   • If no, go to 8.

6. Run change user_mode current_mode user_mode=developer to enter the developer mode. Then run minisystem to switch to the minisystem mode. Run sys.sh showflowstatus and check whether the new controllers are normal.
   • If yes, go to 7.
   • If no, go to 8.

7. Click Re-Execute at the lower left corner of SmartKit to continue the expansion.
8. Collect logs of the original and new controllers and contact technical support for assistance.

   To quickly restore the controllers, refer to How Do I Roll Back If Controller Expansion Is Paused Unexpectedly?

   To collect system logs:

   • Log in to DeviceManager. If you can access the console, choose Settings > Export Data. Select All logs under System Log and click Log List. The system starts collecting logs.
   • If Failed to start the system is displayed when you log in to DeviceManager, click Download Log to download system logs.
   • If a controller fails to be powered on, log in to the controller and enter the minisystem mode. Then run os_backup_info.sh to collect logs and access the log path to obtain the logs.