KB Datastore renaming fails when the Virtual Infrastructure Client is connected directly to ESX host (1004845)

Datastore renaming fails when the Virtual Infrastructure Client is connected directly to ESX host (1004845)

Details

When the Virtual Infrastructure (VI) Client is connected directly to an ESX host, renaming a datastore fails.

Solution

To rename the datastore:

1. Log in to the VirtualCenter Server using the Virtual Infrastructure Client.
2. Select Host > Configuration > Storage.
3. Right-click on the datastore and select Rename, or click the datastore name directly.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Vmware Cluster datastore path dead

Symptoms:

1. have 4 esxi5.1 hosts (esxi01-04) in vmware cluster, VM in two specific datastore cannot start up on esxi01 host
2. checked the iSCSI Network adapter should be fine as only two datastore have issue
3. checked the LUN mapping is fine
4. Try rescan and refresh datatstore didn't solve the issue
5. Try to disconnect and re-mount the datastore on esxi01 didn't solve the problem . 
6. For a reason to resume service asap, migrate all VMs to TEMP datastore, unmount and detach the datastore for all esxi host
7. unmaping LUN on storage side, rescan datastore on vmware cluster the problem LUN should be disappear.
8. Remap LUN to esxi hosts, add to datasore cluster again, re-signature and format the LUN, put VM on it for testing 

Search through esxi logs and get result below:

standard input)-2014-05-xxT03:09:31.297Z cpu6:8198)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a9800037536d72502444xxxxxxxxb" state in doubt; requested fast path state update...
(standard input)-2014-05-xxT03:09:31.594Z cpu4:8401)ALERT: NMP: vmk_NmpVerifyPathUID:1167:The physical media represented by device naa.60a9800037536d72502444xxxxxx (path vmhba32:C0:T0:L13) has changed. If this is a data LUN, this is a critical error. Detect
(standard input)-2014-05-xxT03:09:31.594Z cpu4:8401)WARNING: ScsiDevice: 1422: Device :naa.60a9800037536d72502444xxxxxxx has been removed or is permanently inaccessible.
(standard input):2014-05-xxT03:09:32.410Z cpu4:8196)WARNING: HBX: 1548: HB failed due to no connectivity on [HB state abcdef02 offset 4059136 gen 17 stampUS 1847607014728 uuid 535950b3-29e2ce5d-488a-0025b501011f jrnl <FB 70200> drv 14.58] on vol 'XXXXXXX'
(standard input)-2014-05-xxT03:10:50.461Z cpu10:8202)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a9800037536d72502xxxxxxxx" state in doubt; requested fast path state update...
(standard input)-2014-05-xxT03:16:42.380Z cpu15:10515)WARNING: Vol3: 1717: Failed to refresh FS 535daf66-4b90cce6-fa7c-0025b50100ee descriptor: Device is permanently unavailable
(standard input)-2014-05-xxT03:16:42.661Z cpu15:10515)WARNING: Vol3: 1717: Failed to refresh FS 535daf66-4b90cce6-fa7c-0025b50100ee descriptor: Device is permanently unavailable

not sure whether this KB describe the exact issue but at least they got similar symptoms

VMFS Resignature causes thrashing between multiple VMware ESXi 4.x/5.x and ESX 4.x hosts (1026710

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026710

Unmounting a LUN or detaching a datastore/storage device from multiple VMware ESXi 5.x hosts (2004605)
This article provides steps to unmount a LUN from an ESXi 5.x host, which includes unmounting the file system and detaching the device. These steps must be performed for each ESXi host.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004605

IBM x86 technote for SAS storage

IBM ServeRAID Adapter Quick Reference

http://www.redbooks.ibm.com/abstracts/tips0054.html#m5110

 ServeRAID M5210 and M5210e SAS/SATA Controllers
The ServeRAID M5210 and M5210e SAS/SATA controllers for IBM System x are part of the IBM ServeRAID M Series family that offers a complete server storage solution consisting of RAID controllers, cache/flash modules, energy packs, and software feature upgrades in an ultra-flexible offerings structure. These products are optimized to deliver the performance that is demanded by the ever-growing I/O requirements of today's enterprises. M5210 comes as a small form factor PCIe adapter, and M5210e comes integrated with the IBM System x3650 M4 HD server. They also share a common set of upgrades, simplifying inventory management.

IBM 6 Gb SAS Host Bus Adapter for System x

 

 

 

 

 

http://www.redbooks.ibm.com/abstracts/tips0776.html

The PCIe small form-factor IBM 6 Gb SAS HBA is based on the LSI SAS2008 controller and can handle medium to large capacity server storage applications by connecting an 8-lane PCI Express adapter with one external x4 SFF-8088 connector and four internal SATA connectors.
6 Gbps SAS 2.0 technology has been introduced to address data off-load bottlenecks in the direct-access storage environment. This new throughput doubles the transfer rate of the previous generation. SAS 2.0 is designed for backward compatibility with 3 Gbps SAS as well as with 3 Gbps SATA hard drives and tape drives.

One external x4 SFF-8088 connector