Action to be taken to replace a drive that is subject to frequent response delays (Bare metal)

Virtual Storage Platform One SDS Block and SDS Cloud Troubleshooting Reference

Version
1.19.x
Audience
anonymous
Part Number
MK-24VSP1SDS029-04
ft:lastEdition
2026-07-06

If you want to replace a drive that is subject to frequent response delays (for example, if the drive is repeatedly experiencing drive failures due to drive response delays and drive auto recovery), take action according to the following procedure.

  1. Verify the ID of the drive to be replaced and the ID of the storage node where the drive is installed.

    Also, note down the WWID of the drive to be replaced. This will be used to identify the target drive to be replaced.

    REST API: GET /v1/objects/drives

    CLI: drive_list

  2. Turn on the locator LED of the drive to be removed.

    Run either of the following commands with "TurnOn" specified for the operationType parameter (operation_type in the case of CLI).

    REST API: POST /v1/objects/drives/<id>/actions/control-locator-led/invoke

    CLI: drive_control_locator_led

    Note:
    • When drives are configured with NVMe Drive Direct Attach, locator LED operation from VSP One SDS Block is unavailable even in a configuration listed in the VSP One SDS Block Bare Metal Hardware Compatibility Reference.

      If you are using Hitachi Advanced Server HA800 series, HA800 G2 series, HA800 G3 series, or HA800 G6 series, use an iLO to turn on or off the locator LED. For detailed operations, see the hardware documentation.

      If you are using physical servers other than Hitachi Advanced Server HA800 series, HA800 G2 series, HA800 G3 series, or HA800 G6 series, see the server vendor documentation for details about locator LED operation.

    • If the locator LED cannot be turned on or a configuration differs from those described in the VSP One SDS Block Bare Metal Hardware Compatibility Reference, confirm the location of the drive to be removed by performing the following.

      Find the drive that matches the WWID of the replaced drive recorded in step 1 and the WWN or EUI value of the drive recorded at the time of expansion. Confirm the location in which the drive recorded in association with the WWN or EUI is installed.

    • If the value recorded at the time of drive addition was a WWN, there might be a difference in the last 1 to 3 digits of the right-side 16-digit part of the WWID recorded in step 1.

  3. On the server, find the drive whose locator LED is lit and confirm its mounting position.
  4. See Performing maintenance blocking for storage nodes in the VSP One SDS Block and SDS Cloud System Administration to perform maintenance blocking for the target storage node.
  5. Remove the faulty drive from the server.

    For details about how to detach a drive, see the applicable server vendor documentation.

  6. Make a note of the correlation among the installation location, drive SKU, and WWN or EUI written on the label of all the actual drives to be added.

    See this note when removing or replacing drives. Furthermore, when you enable Data at rest encryption, also see this note when auditing encryption key information.

  7. Insert the drives you want to add into the intended storage node.

    For details about how to insert a drive, see the applicable server vendor documentation.

    Note:
    • When performing drive addition, connect the user data drives after confirming the following points for failure point distribution and load sharing.

      • When connecting user data drives to disk controllers:

        Verify the connection to the disk controller where only user data drives are connected, then install the user data drive in any available drive slot. However, if multiple disk controllers are available for connecting user data drives, connect the user data drives so that the number of user data drives connected to each disk controller is equal.

      • When connecting user data drives with NVMe Drive Direct Attach:

        After verifying the wiring between each drive slot and the CPU, connect the user data drives so that the number of user data drives connected to each CPU is equal.

    • To change the mounting position of a user data drive that has already been installed, perform storage node maintenance blocking or stop the storage cluster. Then, with the storage node containing the target user data drive stopped, move the user data drive to a different drive slot.

      After changing the mounting position, perform storage node maintenance recovery or start the storage cluster to restore the system to its original state.

      Note that user data drives can only be changed within the same storage node. They cannot be moved to a different storage node.

  8. See Performing maintenance recovery for storage nodes in the VSP One SDS Block and SDS Cloud System Administration to perform maintenance recovery for the storage node.
  9. Perform steps 1 to 5 for the created drive according to Expanding a storage pool in the VSP One SDS Block and SDS Cloud System Administration.
  10. Perform steps 6 to 12 for the drive to be replaced according to Removing drives (Bare metal) in the VSP One SDS Block and SDS Cloud System Administration.