User Tools

Site Tools


storage:v7k_replace_disk

This is an old revision of the document!


IBM V3700-V5000-v7000 disk replacement

From the V7000's command line:

1- Login to the Management node as “root” user

2- Login to the V7000's command line

  ssh superuser@<IP> 

Now you will be executing steps 1 through 6 of the instructions above

3- Identify and list the disk to replace. ID=54

3.1 - Identify the drive physically in the enclosure, it will lit the LED so you can see exactly which one to pull

IBM_Storwize:V7_00_1:superuser> chenclosureslot -identify yes -slot 17 3

3.2 List the drive

IBM_Storwize:V7_00_1:superuser> svcinfo lsdrive 54

  id 54
  status offline
  error_sequence_number 507
  use failed
  UID 5000cca01638b2e0
  tech_type sas_hdd
  capacity 837.9GB
  block_size 512
  vendor_id IBM-207x
  product_id HUC109090CSS60
  FRU_part_number 00Y2684
  FRU_identity 11S49Y7449YXXXKPH05N6F
  RPM 10000
  firmware_level J2E6
  FPGA_level
  mdisk_id
  mdisk_name
  member_id
  enclosure_id 3
  slot_id 17
  node_id
  node_name
  quorum_id
  port_1_status offline
  port_2_status offline

3.3 Checking for any dependency the disk may have is not in the step, but is good to do IBM_Storwize:V7_00_1:superuser> lsdependentvdisks -drive 54

Note: Notice the disk is identified by the id, enclosure and slot.

4- Take the drive offline (in this example the drive is already offline but will still show the command)

  IBM_Storwize:V7_00_1:superuser> chdrive -use failed 54

4.1 List the drive again to verify that the drive is offline (repeat #3)

5- Mark the drive unused

  IBM_Storwize:V7_00_1:superuser> chdrive -use unused 54

6- Now you can replace the disk. Pull the the old disk and wait between 2 to 5 minutes, then insert the new one

  Note: Contact the SSR to verify that they are looking at the correct V7000 and can see the drive with the LED on. The SSR will ask for the MTM and Serial Number of the enclosure and the rack location.
  See the following URL for instructions for physically replacing a drive:
  V7000 Gen1
  https://www.ibm.com/support/knowledgecenter/en/ST3FR7_7.6.0/com.ibm.storwize.v7000.760.doc/tbrd_rmv24carrier_1948dx.html
  V7000 Gen2:
  https://www.ibm.com/support/knowledgecenter/en/ST3FR7_7.6.0/com.ibm.storwize.v7000.760.doc/fab1_rplc_25_drv_assembly.html

7- The drive will come back as online / unused.

  IBM_Storwize:V7_00_1:superuser> svcinfo lsdrive

8- If IBM PureData for Operational Analytics v1.1 mark the disk as “spare”.

IBM_Storwize:V7_00_1:superuser> chdrive -use spare 54

If you are in v1.0 environment, mar the disk as a candidate. Then the disk will become a member and the array will begun to use it.

IBM_Storwize:V7_00_1:superuser> chdrive -use candidate 54

After this step the array begun to use the disk and it will go into rebuild. If that does not happen, then you set it to spare. See command above.

You can check the progress by running the following command:

IBM_Storwize:V7_00_1:superuser> lsarraymemberprogress

This report the task “rebuild”, the array name, the estimated time for completion and others.

storage/v7k_replace_disk.1639221987.txt.gz · Last modified: 2021/12/11 12:26 by manu