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>Search

Reminder

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

upgrade

Huawei V2 and V3 Server RAID Controller Card User Guide 36

This document describes the appearances and features of the redundant array of independent disks (RAID) controller cards, how to configure properties for the RAID controller cards, and how to install drivers. The RAID controller cards include the LSI SAS2208, LSI SAS2308, LSI SAS3008, LSI SAS3108, LSI SoftRAID, PM8060, and PM8068.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Hard Drive Fault

Hard Drive Fault

Symptoms

A hard drive is faulty if any of the followings occurs:

  • The hard drive fault indicator is on.
  • After the server is powered on, the hard disk indicator is off.
  • A hard drive fault alarm was generated.

Solution

  1. Determine the slot number of the faulty drive.

    If a hard drive in JBOD mode is faulty, the Fault indicator on the drive will not be lit and the BMC will not generate an alarm.

    • Locate the faulty drive based on the fault indicator, which is steady orange. For details, see the drive numbering section in the user guide of the server you use.
    • Locate the faulty drive based on the iMana/iBMC drive alarm information. For details, see iMana/iBMC Alarm Handling.
    • Locate the faulty drive using the RAID controller card GUI. For details, see PD Mgmt Tab or Drive Management.
    • Locate the faulty drive using the RAID controller card CLI tool. For details, see Querying RAID Controller Card/RAID Array/Physical Drive Information.

  2. Check for and delete the Preserved Cache data from the server.

    • If the RAID array containing the Preserved Cache data is invalid (the number of faulty drives in the RAID array exceeds the maximum number of faulty drives supported by the RAID array), the RAID array will be deleted when PreservedCache data is deleted.
    • If the hard drive fault is caused by manual removal and installation of the hard drive in the RAID array, remove the hard drive and then delete the Preserved Cache data. By doing this, the RAID array will not be deleted.
    • To clear the Preserved Cache data on the GUI, perform the following steps:

      On the VD Mgmt screen, move the cursor to SAS3108 (Bus 0x01, Dev 0x00) and press F2.

      • If Manage Preserved Cache is available, as shown in Figure 8-142, the Preserved Cache data exists. Delete the Preserved Cache data by referring to Discarding Preserved Cache.
        Figure 8-142 Checking for Preserved Cache data
      • If Manage Preserved Cache is not available, the Preserved Cache data does not exist. In this case, go to 3.
    • To clear the Preserved Cache data through the CLI, perform the following steps:
      1. Run the storcli64/c0 show preservedcache command to check whether a preserved cache exists.

        In this example, Preserved Cache data exists in VD 0 managed by controller 0.

      2. Run the ./storcli64/call/vall delete preservedCache force command to clear the Preserved Cache.

  3. Replace the drive.

    • Before removing a drive, determine its location. If a hard drive is removed by mistake, the RAID array will fail. For details, see 1. If the drive fault is caused by manual removal and installation of the drive, set the drive to Unconfig Good and restore the RAID array. For details, see Importing or Deleting a Foreign Configuration.
    • If the faulty drive is a pass-through drive or belongs to a RAID array without redundancy (for example, RAID 0), the drive data cannot be restored.
    • If the faulty drive belongs to a RAID array with redundancy and the number of faulty drives does not exceed the maximum number of faulty drives supported by the RAID array, the RAID array data will not be lost. Otherwise, RAID group data will be lost. For details about the maximum number of faulty drives supported by RAID arrays, see Table 8-3.
    • After a faulty drive is disconnected from its backplane, wait 30 seconds before removing it. The alarm will not be cleared immediately after a new drive is installed. It will be cleared after the RAID array is rebuilt. Do not hot remove and install drives frequently.
    • The newly inserted drive should not contain RAID information. If the installed drive has RAID information, delete the RAID information from the RAID controller card of the same model as the original RAID controller card or perform low-level formatting on the drive. For details, see the user guide of the RAID controller card you use.

    Remove the faulty drive and install a new drive. The new drive can be restored in the following ways based on the RAID configuration of the faulty drive:

    • If the RAID array has a hot spare drive, copyback will be performed after the hot spare drive is rebuilt. After data is copied to the new drive, the hot spare drive restores to the hot backup state.
    • If the RAID array has redundancy feature and has no hot spare drive, the newly installed drive automatically rebuilds data. If the number of faulty drives in a RAID group exceeds 1, replace the faulty drives one by one based on the drive fault time. Replace the next drive only after the current drive data is rebuilt.
    • If the faulty drive is a pass-through drive, replace it.
    • If the faulty hard drive belongs to a RAID array without redundancy (RAID 0), create RAID 0 again.

Translation
Download
Updated: 2019-11-01

Document ID: EDOC1000004186

Views: 713714

Downloads: 20606

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next