Solution when disks are about to fail (half life)


Solution when disks are about to fail (half life):
The storage system determines the health status of disks by detecting internal parameters of disks. If the health status of disks drops to a threshold, an alarm indicating that disks are about to fail is reported, which shows that disks have potential risks. If such an alarm is reported and extra hot spare disks are available in the system, pre-copy is enabled automatically to migrate data on disks that are about to fail to hot spare disks.
Recommended action:
If pre-copy has been enabled, replace disks that are about to fail after pre-copy is completed.

Other related questions:
Solution when a disk failure occurs
Solution when a disk failure occurs: Troubleshooting: 1. If the disk is not removed and inserted, collect the S.M.A.R.T information of the disk and send the information to the R&D for analysis. 2. Apply for spare parts and replace the faulty disk.

Solution if importing licenses fails
Solution if importing licenses fails: The failure of importing licenses may occur due to an incompatible tool version, incorrect license file, incorrect network, or incorrect gateway. To rectify the fault, perform the following operations: 1. Upgrade the tool version to the required one. 2. Ensure that the license file is correct and the SN used is consistent with that of the storage device. 3. If the PC is connected to several networks, disconnect or disable network ports that are not used for deployment. 4. Ensure that the gateway vendor is correct: Log in as user support to the file engine using the IP address of the file engine's management network port and execute cat/opt/HS/conf/product.ini to ensure that vendor is huawei and gateway is yes. If the gateway vendor remains incorrect, execute /opt/HS/factory/scripts/ on each node and set the gateway vendor to HWG using the serial ports. Then restart all nodes and perform the previous operation again.

Problem and solution when a KVM fails
Possible cause: The problem occurs when the power supply is unstable and has transient breaks after the reconstruction of the UPS. Solution: 1. Reinsert the USB cable. 2. If the problem persists, restart the KVM. 3. Replace the faulty keyboard and mouse or the KVM. 4. If the problem persists, restart the SVP.

Solution when installing UltraPath fails on CentOS
Solution when installing UltraPath fails on CentOS: This failure occurs because the host is installed with the multipathing software of RDAC, which cannot coexist with Huawei UltraPath. You need to suspend service operations and perform the following steps: 1. Run rpm -e --allmatches UltraPath to uninstall UltraPath completely. 2. Uninstall the multipathing software of RDAC (performed by the customer's maintenance engineer). 3. Restart the host and install UltraPath.

Problem and solution when disk isolation occurs
You can perform the following operations when disk isolation occurs: The following causes may result in disk isolation: Bit error Reinserting disks repeatedly Disk power connection problem 1. Bit error Check the bit error of back-end SAS disks. Search keywords err inc and disable disk phy in the SES log. Note: phy:9 phymon***disable disk phy in the log shows that disk phy 9 is isolated. That is, the disk in slot 9 is isolated (phy0 to phy23 corresponds to disk 0 to 23). Troubleshooting 1. Before removing a faulty disk, collect S.M.A.R.T. information. 2. If conditions permit, insert the isolated disk to other slots to check whether isolation is caused by the disk or the slot. If isolation is caused by the disk, apply for disk replacement. If isolation is caused by the slot, check whether the slot has any foreign objects. Check the bit error on Fibre Channel disks. Search keyword lcv that is Fibre Channel bit errors in the SES log. If HD 0 and lcv ffff are displayed, the information indicates that a large quantity of bit errors are produced in slot 0 and cause disk isolation. The back-end Fibre Channel bit errors can spread from the port to the disk. If a Fibre Channel disk is isolated, check whether bit errors occur on the port by using the following methods: Check on the ISM. Enter fc allinfo in MML mode. Note: If any information displayed is not 0, bit errors exist. If bit errors are detected on the port, verify whether bit error are generated in the link. For details about how to verify, see the troubleshooting cases for a single link failure of the Fibre Channel enclosure disk caused by bit errors. Troubleshooting: If only one disk fails, verify the failure by using the above method. If a link fails, replace the optical module and optical cables and verify the failure. If a link does not fail, use the same method as one carried out on the SAS disk. If multiple disks are faulty, refer to the troubleshooting cases for a single link failure of the Fibre Channel enclosure disk caused by bit errors. 2. Reinserting disks repeatedly Note: A drive can isolate the disk from other ones if intermittent disconnections occur on the disk. Reinserting disks repeatedly may lead to disk isolation. Verify whether the disk is reinserted many times within a short period. If such a case exists, reinserting disk may result in disk isolation. Troubleshooting: Reinsert the disk. 3. Disk power connection problem Note: If the disk enclosure is affected by violent shaking, disk power may be insecurely connected and the disk is isolated. Troubleshooting: Contact R&D engineers for further analysis.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top