Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 207710

SSD tagging error

$
0
0

I'm trying to tag a IBM SSD in one of our IBM HS21 blades, i've followed the steps as outlined in http://pubs.vmware.com/vsphere-50/index.jsp?topic=/com.vmware.vsphere.storage.doc_50/GUID-8AE88758-20C1-4873-99C7-181EF9ACFA70.html

 

But i'm receving errors on this step/command:

 

 

~ # esxcli storage core claiming unclaim --type device --device naa.600508e000000000cd969d347feb5003
Unable to perform unclaim. Error message was : Unable to unclaim all requested paths. Some paths were busy or were the last path to an in use device.  See VMkernel logs for more information.
~ #

 

Below is the last few lines of the vmkernel log:

 

2011-09-10T13:08:17.624Z cpu3:50764)Vol3: 647: Couldn't read volume header from control: Invalid handle

 

2011-09-10T13:08:17.624Z cpu3:50764)FSS: 4333: No FS driver claimed device 'control': Not supported

 

2011-09-10T13:08:17.630Z cpu3:50764)VC: 1449: Device rescan time 7 msec (total number of devices 5)

 

2011-09-10T13:08:17.630Z cpu3:50764)VC: 1452: Filesystem probe time 17 msec (devices probed 4 of 5)

 

2011-09-10T13:08:54.545Z cpu4:50765)ScsiDevice: 3283: Can't unregister device naa.600508e000000000cd969d347feb5003 because it is in use.  OpenCount:2 InternalOpenCount:0 RefCount:3 FilterCount:0

 

2011-09-10T13:08:54.545Z cpu4:50765)ScsiDevice: 3294: Device naa.600508e000000000cd969d347feb5003 was in use by worldId 0

 

2011-09-10T13:08:54.545Z cpu4:50765)ScsiDevice: 3290: Device naa.600508e000000000cd969d347feb5003 is in use by world idle0 worldId 2056

 

2011-09-10T13:08:54.545Z cpu4:50765)WARNING: NMP: nmpUnclaimPath:1505:NMP device "naa.600508e000000000cd969d347feb5003" quiesce state change failed: Busy

 

2011-09-10T13:08:54.545Z cpu4:50765)ScsiPath: 4710: Path vmhba1:C1:T1:L0 could not be unclaimed from plugin, status Busy. Continue path unclaiming

 

2011-09-10T13:08:54.545Z cpu4:50765)ScsiPathClaimVsi: 990: Unclaim operation failed with 'Busy' for plugin type 1

 

2011-09-10T13:08:54.566Z cpu3:2819)Vol3: 647: Couldn't read volume header from control: Invalid handle

 

2011-09-10T13:08:54.566Z cpu3:2819)FSS: 4333: No FS driver claimed device 'control': Not supported

 

2011-09-10T13:08:54.573Z cpu3:2819)VC: 1449: Device rescan time 7 msec (total number of devices 5)

 

2011-09-10T13:08:54.573Z cpu3:2819)VC: 1452: Filesystem probe time 17 msec (devices probed 4 of 5)


Viewing all articles
Browse latest Browse all 207710

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>