Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

vmhba no longer has device /dev association?

$
0
0

 

HW/SW: HP DL585G2 - 2x Qlogic QLE-2460 - ESX 3.0.1 - VC 2.5u2:

 

 

I have a situation where : esxcfg-vmhbadevs -q  returns a list of vmhba & /dev - with one exception. #34 in this list does not have an associated device.  This situation has left me with an ESX host that will not enter maintenance mode, but I am able to manually move the VM's off the host with vmotion, one at a time.

 

 

Therefore, for now, I've put DRS into full conservative and have begun to move VM's off this host.

 

 

If run esxcfg-vmhbadevs -q on another node in the cluster, all vmhba's have anassoicated device, and everything is as expected.

 

 

Has anyone solved this with a simple rescan?  I'll consider trying rescans and such after I get the remaining VM's off this host.

 

 

 

For your observation: output of esxcfg-vmhbadevs -q on the problem host, and some entrie from vmkwarning which indicate addtional storage trouble on other LUNs.

 

 

vmhba0:0:0 /dev/sda

vmhba0:0:1 /dev/sdb

vmhba0:0:2 /dev/sdm

vmhba0:0:3 /dev/sdx

vmhba0:0:4 /dev/sdah

vmhba0:0:5 /dev/sdas

vmhba0:0:6 /dev/sdat

vmhba0:0:7 /dev/sdau

vmhba0:0:8 /dev/sdav

vmhba0:0:9 /dev/sdaw

vmhba0:0:10 /dev/sdc

vmhba0:0:11 /dev/sdd

vmhba0:0:12 /dev/sde

vmhba0:0:13 /dev/sdf

vmhba0:0:14 /dev/sdg

vmhba0:0:15 /dev/sdh

vmhba0:0:16 /dev/sdi

vmhba0:0:17 /dev/sdj

vmhba0:0:18 /dev/sdk

vmhba0:0:19 /dev/sdl

vmhba0:0:20 /dev/sdn

vmhba0:0:21 /dev/sdo

vmhba0:0:22 /dev/sdp

vmhba0:0:23 /dev/sdq

vmhba0:0:24 /dev/sdr

vmhba0:0:25 /dev/sds

vmhba0:0:26 /dev/sdt

vmhba0:0:27 /dev/sdu

vmhba0:0:28 /dev/sdv

vmhba0:0:29 /dev/sdw

vmhba0:0:30 /dev/sdy

vmhba0:0:31 /dev/sdz

vmhba0:0:32 /dev/sdaa

vmhba0:0:33 /dev/sdab

vmhba0:0:34

vmhba0:0:35 /dev/sdac

vmhba0:0:36 /dev/sdad

vmhba0:0:37 /dev/sdae

vmhba0:0:38 /dev/sdaf

vmhba0:0:39 /dev/sdag

vmhba0:0:40 /dev/sdai

vmhba0:0:41 /dev/sdaj

vmhba0:0:42 /dev/sdak

vmhba0:0:43 /dev/sda

 

 

 

 

 

/var/log/vmkwarning shows the following as a result, which shows trouble on other vmhba as well, but nothing for 34:

 

 

SCSI: 5646: status I/O error, rstatus 0xc0de00 for vmhba0:0:30. residual R 999, CR 80, ER 3

Swap: vm 1418: 5550: Swap sync read retry failed: status=195887114, retry=2

 

 

SCSI: 5646: status I/O error, rstatus 0xc0de00 for vmhba0:0:47. residual R 999, CR 80, ER 3

Swap: vm 1632: 5537: Swap sync read failed: status=195887114, retrying...

 

 

SCSI: 5646: status I/O error, rstatus 0xc0de00 for vmhba0:0:47. residual R 999, CR 80, ER 3

Swap: vm 1632: 5550: Swap sync read retry failed: status=195887114, retry=1

 

 

SCSI: 5646: status I/O error, rstatus 0xc0de00 for vmhba0:0:35. residual R 999, CR 80, ER 3

Swap: vm 1558: 5537: Swap sync read failed: status=195887114, retrying...

 

 

SCSI: 5646: status I/O error, rstatus 0xc0de00 for vmhba0:0:35. residual R 999, CR 80, ER 3

Swap: vm 1558: 5550: Swap sync read retry failed: status=195887114, retry=1

 

 

 

 

 


Viewing all articles
Browse latest Browse all 60069

Trending Articles