"Recovered device not found after HBA rescan" during SRM Test Recovery due to iSCSI connectivity timeout.
search cancel

"Recovered device not found after HBA rescan" during SRM Test Recovery due to iSCSI connectivity timeout.

book

Article ID: 430319

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms:

When executing a Site Recovery Manager (SRM) Test Recovery plan, the operation fails during the storage mounting phase. The following symptoms are observed:

  • Error Message: "Failed to recover datastore '<DATASTORE_NAME>'. VMFS volume residing on recovered devices '<DEVICE_ID>' cannot be found. Recovered device not found after HBA rescan. Operation timed out: 300 seconds."
  • SRM UI reports a failure to rescan HBAs on the recovery host.
  • VMware Site Recovery Manager with Software iSCSI adapters (e.g., vmhba68) and PowerStore storage arrays.

Environment

VMware Live Recovery 9.0.3

Cause

The recovery failure is caused by a lack of network path availability between the Recovery ESXi host and the target storage array. The Software iSCSI adapter is unable to establish a session over Port 3260, resulting in zero active paths and zero devices detected during the HBA

Validation:

Login to the target site and check the storage adapter being used for iSCSI:

Login to the target host and check the iSCSI connectivity to port 3260

Perform a vmkping test to the target along with the MTU size.

 

Resolution

To resolve this issue, network connectivity for iSCSI traffic must be restored between the recovery host and the storage target.

  1. Test connectivity to the target array from the recovery host over the iSCSI port: nc -zv <TARGET_IP> 3260
  2. Perform a vmkping test using the specific VMkernel interface assigned to iSCSI (e.g., vmk1) to ensure the path is routable: vmkping -I vmk1 <TARGET_IP>
  3. Ensure MTU settings are consistent across the VMkernel port, physical switches, and storage processors (e.g., testing with vmkping -d -s 1472 <TARGET_IP> if standard MTU is used).
  4. Work with the network team to ensure TCP Port 3260 is open and not blocked by intermediate firewalls or Access Control Lists (ACLs)
  5. Once network connectivity is confirmed, perform a manual HBA rescan on the recovery host: esxcli storage core adapter rescan --adapter=vmhba<ID>
  6. After the devices are visible on the host, re-run the SRM Test Recovery plan.