Support > Knowledge Base

Knowledge Base

Search the Knowledge Base:

Guided Search

Products:

Search In:

Unable to Recognize New SAN LUNs After Command Line Rescan

Details

Additional storage has been added to the SAN, but a rescan results in an error message that states Disk vmhba0:0:12 is inaccessible. Could not load partition table. Please rescan.

What is the proper method to rescan the SAN from the command line?

Solution

After you scan the SAN for the currently presented LUNs, the service console needs to be made aware of the LUN changes.

If your ESX Server version is less than 2.5, you need to perform the following three steps. If your ESX Server version is 2.5 or greater, you need to perform only the third step.

The first step flushes the cache in the HBA (fiber host bus adapter). The second step scans the SAN for presented LUNs. The third step creates device nodes required to partition the available LUNS into VMFS volumes.

Note: The first step applies to QLogic HBAs only, not to Emulex HBAs.

If you have Emulex HBAs, skip this step. Otherwise, for QLogic HBAs only, run wwpn.pl with the -s option for each HBA through which the LUN is accessed. For example:
wwpn.pl -s vmhba1
Run vmkfstools with the -s option for each HBA through which the LUN is accessed. For example:
vmkfstools -s vmhba1
Run cos-rescan.sh on the same HBA as in the step above. For example:
cos-rescan.sh vmhba1

Keywords

1352; fiber; fibre; channel; host; bus; adaptor; brocade; qlogic; emulex; hp; agilent; vmfstool

Feedback

Actions

KB Article: 1352
Updated: Aug 14, 2009

Products:
VMware ESX
Product Versions:
VMware ESX 2.0.x
VMware ESX 2.1.x
VMware ESX 2.5.x

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)