VMware Cloud Community
bittrekker
Contributor
Contributor

scsi disconnect on one ESXi 5x host but not second

Searching through the forums, it appears that the issue that I'm having has been experienced by others after they upgraded to esxi5, addded a software iscsi, or restarted management agents; however, the esxi server hasn't been touched by anyone in ages, so I'm posting a new thread. Most of all, I want to make sure that I don't lose everything on all of these Windows servers.

Two separate ESXi 5 hosts connected to a SAN. On one of them, I can connect using vSphere and all of the guests are up. The problem host, however, I can only connect using SSH (and of course I can ping the host). vsphere on that host returns error An unknown  connection  error occurred. The request failed because of a connection  failure.  (Unable to connect to the remote server). And as mentioned, the guests aren't showing up on the network.

One more note, I'm trying to do this remotely since the office building is locked up. I can't reboot the server, even with reboot -f. I assume this is because esxi still wants to control the shutdown processes with the images that it cannot connect to?

Here's all the info that I've been able to get:

/sbin/services.sh restart returned:

Errors:
Not all VMFS volumes were updated; the error encountered was 'IO was  aborted by VMFS via a virt-reset on the device'.
Errors:
Not all VMFS  volumes were updated; the error encountered was 'IO was aborted by VMFS via a  virt-reset on the device'.
Errors:
Rescan complete, however some dead  paths were not removed because they were in u se by the system. Please use the  'storage core device world list' command to see the VMkernel worlds still using  these paths.
Error while scanning interfaces, unable to continue. Error was  Not all VMFS volu mes were updated; the error encountered was 'No  connection'.

esxcfg-scsidevs -l
mpx.vmhba0:C0:T0:L0
   Device Type: CD-ROM
   Size: 0 MB
   Display Name: Local MATSHITA CD-ROM (mpx.vmhba0:C0:T0:L0)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0
   Devfs Path: /vmfs/devices/cdrom/mpx.vmhba0:C0:T0:L0
   Vendor: MATSHITA  Model: DVD-ROM UJ890     Revis: WAA3
   SCSI Level: 5  Is Pseudo: false Status: on
   Is RDM Capable: false Is Removable: true
   Is Local: true  Is SSD: false
   Other Names:
      vml.0005000000766d686261303a303a30
   VAAI Status: unsupported
mpx.vmhba32:C0:T0:L0
   Device Type: Direct-Access
   Size: 1944 MB
   Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
   Devfs Path: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
   Vendor: SMART     Model: USB-IBM           Revis: 8989
   SCSI Level: 2  Is Pseudo: false Status: on
   Is RDM Capable: false Is Removable: true
   Is Local: true  Is SSD: false
   Other Names:
      vml.0000000000766d68626133323a303a30
   VAAI Status: unsupported
naa.60080e50001bd200000001804d594a8a
   Device Type: Direct-Access
   Size: 1126400 MB
   Display Name: IBM Serial Attached SCSI Disk (naa.60080e50001bd200000001804d594a8a)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/disks/naa.60080e50001bd200000001804d594a8a
   Devfs Path: /vmfs/devices/disks/naa.60080e50001bd200000001804d594a8a
   Vendor: IBM       Model: 1746      FAStT   Revis: 1070
   SCSI Level: 5  Is Pseudo: false Status: dead
   Is RDM Capable: true  Is Removable: false
   Is Local: false Is SSD: false
   Other Names:
      vml.020001000060080e50001bd200000001804d594a8a313734362020
   VAAI Status: unknown
naa.60080e50001bd378000001854d594aca
   Device Type: Direct-Access
   Size: 1689600 MB
   Display Name: IBM Serial Attached SCSI Disk (naa.60080e50001bd378000001854d594aca)
   Multipath Plugin: NMP
   Console Device: /vmfs/devices/disks/naa.60080e50001bd378000001854d594aca
   Devfs Path: /vmfs/devices/disks/naa.60080e50001bd378000001854d594aca
   Vendor: IBM       Model: 1746      FAStT   Revis: 1070
   SCSI Level: 5  Is Pseudo: false Status: dead
   Is RDM Capable: true  Is Removable: false
   Is Local: false Is SSD: false
   Other Names:
      vml.020002000060080e50001bd378000001854d594aca313734362020
   VAAI Status: unknown

~ # esxcfg-scsidevs -a
vmhba0 ata_piix link-n/a sata.vmhba0 (0:0:31.2) Intel  Corporation ICH10 4 port SATA IDE Controller
vmhba1 ata_piix link-n/a  sata.vmhba1 (0:0:31.5) Intel Corporation ICH10 2 port SATA IDE  Controller
vmhba2 megaraid_sas link-n/a unknown.vmhba2 (0:1:0.0) LSI /  Symbios Logic MegaRAID SAS SKINNY Controller
vmhba3 mpt2sas link-n/a  sas.500605b0027bc860 (0:26:0.0) LSI Logic / Symbios Logic LSI2008
vmhba4  mpt2sas link-n/a sas.500605b0027b96a0 (0:36:0.0) LSI Logic / Symbios Logic  LSI2008
vmhba32 usb-storage link-n/a usb.vmhba32 () USB
vmhba33 ata_piix  link-n/a sata.vmhba33 (0:0:31.2) Intel Corporation ICH10 4 port SATA IDE  Controller
vmhba34 ata_piix link-n/a sata.vmhba34 (0:0:31.5) Intel  Corporation ICH10 2 port SATA IDE Controller

tail -f /var/log/vmkernel.log

2013-04-18T06:06:47.657Z cpu3:4568628)NMP:  nmp_DeviceUpdatePathStates:547: Activ ated path "NULL" for NMP device  "naa.60080e50001bd200000001804d594a8a".
2013-04-18T06:06:47.657Z  cpu2:2196)NMP: nmp_DeviceUpdatePathStates:547: Activate d path "NULL" for NMP  device "naa.60080e50001bd378000001854d594aca".
2013-04-18T06:06:47.657Z  cpu3:4568628)WARNING: VMW_SATP_LSI: satp_lsi_pathIsUsin  gPreferredController:714:Failed to get volume access control data for path "vmhb  a4:C0:T0:L1": No connection
2013-04-18T06:06:47.657Z cpu2:2196)WARNING:  VMW_SATP_LSI: satp_lsi_pathIsUsingPr eferredController:714:Failed to get volume  access control data for path "vmhba4: C0:T0:L2": No  connection
2013-04-18T06:06:48.657Z cpu8:6222374)WARNING: VMW_SATP_LSI:  satp_lsi_pathIsUsin gPreferredController:714:Failed to get volume access control  data for path "vmhb a4:C0:T0:L1": No connection
2013-04-18T06:06:48.657Z  cpu8:6222374)NMP: nmp_DeviceUpdatePathStates:547: Activ ated path "NULL" for NMP  device "naa.60080e50001bd200000001804d594a8a".
2013-04-18T06:06:48.657Z  cpu8:4568630)WARNING: VMW_SATP_LSI: satp_lsi_pathIsUsin  gPreferredController:714:Failed to get volume access control data for path "vmhb  a4:C0:T0:L2": No connection
2013-04-18T06:06:48.657Z cpu8:4568630)NMP:  nmp_DeviceUpdatePathStates:547: Activ ated path "NULL" for NMP device  "naa.60080e50001bd378000001854d594aca".
2013-04-18T06:06:48.657Z  cpu8:6222374)WARNING: VMW_SATP_LSI: satp_lsi_pathIsUsin  gPreferredController:714:Failed to get volume access control data for path "vmhb  a4:C0:T0:L1": No connection
2013-04-18T06:06:48.657Z cpu8:4568630)WARNING:  VMW_SATP_LSI: satp_lsi_pathIsUsin gPreferredController:714:Failed to get volume  access control data for path "vmhb a4:C0:T0:L2": No  connection
2013-04-18T06:06:49.657Z cpu8:6151314)WARNING: VMW_SATP_LSI:  satp_lsi_pathIsUsin gPreferredController:714:Failed to get volume access control  data for path "vmhb a4:C0:T0:L2": No connection
2013-04-18T06:06:49.657Z  cpu1:6123000)WARNING: VMW_SATP_LSI: satp_lsi_pathIsUsin  gPreferredController:714:Failed to get volume access control data for path "vmhb  a4:C0:T0:L1": No connection
2013-04-18T06:06:49.657Z cpu8:6151314)NMP:  nmp_DeviceUpdatePathStates:547: Activ ated path "NULL" for NMP device  "naa.60080e50001bd378000001854d594aca".
2013-04-18T06:06:49.657Z  cpu1:6123000)NMP: nmp_DeviceUpdatePathStates:547: Activ ated path "NULL" for NMP  device "naa.60080e50001bd200000001804d594a8a".
2013-04-18T06:06:49.657Z  cpu1:6123000)WARNING: VMW_SATP_LSI: satp_lsi_pathIsUsin  gPreferredController:714:Failed to get volume access control data for path "vmhb  a4:C0:T0:L1": No connection
2013-04-18T06:06:49.657Z cpu8:6151314)WARNING:  VMW_SATP_LSI: satp_lsi_pathIsUsin gPreferredController:714:Failed to get volume  access control data for path "vmhb a4:C0:T0:L2": No  connection
2013-04-18T06:06:50.601Z cpu8:6223351)ScsiDeviceIO: 2309:  Cmd(0x4124003ae840) 0x 16, CmdSN 0x2bb9a from world 0 to dev  "naa.60080e50001bd378000001854d594aca" fai led H:0x5 D:0x0 P:0x0 Possible sense  data: 0x0 0x0 0x0.

Tags (4)
Reply
0 Kudos
2 Replies
bittrekker
Contributor
Contributor

Had to hardboot and it reconnected. Couldn't run command reboot -f to restart. Of course, there were typical issues with some of the servers appearing not to come up right away because some were in recovery mode; restart services, etc. Not a lot of fun, but I'm glad it was an easy "repair" with no damage.

Reply
0 Kudos
code131415
Contributor
Contributor

出现了此情况改怎么处理

Reply
0 Kudos