VMware Cloud Community
Jerry_W1
Contributor
Contributor

rescan storage adapter timeout

I have vmware 3.0.2 installed. When I tried to scan the storage adapter, it first times out. Then it came back after a long time and showed as tasked completed. When I tried to run script to scan manually I got the following errror:

  1. perl rescan.pl

Error: SysinfoException: NodeId(1017) ; Status(195887138)= SCSI reservation conflict; Message= Unable to Get Instance List

The following HBAs were detected on this system:

vmhba0

vmhba1

vmhba2

vmhba3

vmhba4

Rescanning vmhba0...done.

On scsi0, removing: 0:0 1:0 6:0.

On scsi0, adding: 0:0 1:0 6:0.

Rescanning vmhba1...done.

On scsi1, removing:.

On scsi1, adding:.

Rescanning vmhba2...done.

On scsi2, removing: 0:0 0:1 0:2 0:3 0:4.

On scsi2, adding: 0:0 0:1 0:2 0:3 0:4.

Rescanning vmhba3...done.

On scsi3, removing:.

On scsi3, adding:.

Rescanning vmhba4...done.

On scsi4, removing:.

On scsi4, adding:.

The script I used is:

  1. cat rescan.pl

#!/usr/bin/perl -w

#Filename: rescan-hbas.pl

#No warranty is provided with this script

use strict;

my @hbas = `/usr/sbin/esxcfg-info \| grep vmkernel -i \| grep hba \| awk -F\. \{\'print \$29\'\}`;

print "The following HBAs were detected on this system:\n";

print "\t@hbas";

foreach my $hba (@hbas) {

system("/usr/sbin/esxcfg-rescan $hba");

}

Any one knows a workaround to avoid the rescan delay? Thanks!

0 Kudos
2 Replies
BenConrad
Expert
Expert

I think there was a patch released in fall 2007 that addresses some HBA rescan issues.

Ben

0 Kudos
Jerry_W1
Contributor
Contributor

I already applied patch ESX-1002974.tgz. But I still got reservation conflict error in the message file.

0 Kudos