I am running esxi 6.5 with the latest patches and vmware tools 10.1.5

I am having very inconsistent performance issues with both of my hosts. Basically the windows 2016/windows 10 guests are sluggish at times. nothing will load and the os is basically unresponsive when interacting with the gui. The issue seems to be stemming from disk performance but I am not 100% certain that this is the cause, it may be a side affect.

What I have noticed is that some vms show a average response time for the disk of about 2000ms. Yet if i check the performance monitor at a host level the disk and datastores are all showing sub 1ms response time. I am not able to explain the inconsistencies there.

I have a local ssd datastore on each host as well as a rather fast nvme iscsi san that is connected via 100gb mellanox connectx4 cards. I see the issue with both hosts and both datastores. The issue seems to be worse now with the most recent patches and vmware tools drivers. I am using vmxnet3 network cards and paravirtual scsi controllers on all vms.

I have run disk benchmarks on the vms and the resutls vary. I have already seen it where i run a disk benchmark on a guest, get horrible results, vmotion it to the other host, and benchmarks to the san are fine, and then i vmotion the guest back to the original host and the results are fine the second time I run it.

here is an example of a bad test, the reads are terrible:

-----------------------------------------------------------------------

CrystalDiskMark 5.2.0 x64 (C) 2007-2016 hiyohiyo

                           Crystal Dew World : http://crystalmark.info/

-----------------------------------------------------------------------

* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]

* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 2) :     0.655 MB/s

  Sequential Write (Q= 32,T= 2) :  5384.173 MB/s

  Random Read 4KiB (Q= 32,T= 2) :     0.026 MB/s [     6.3 IOPS]

Random Write 4KiB (Q= 32,T= 2) :   617.822 MB/s [150835.4 IOPS]

         Sequential Read (T= 1) :     2.306 MB/s

        Sequential Write (T= 1) :  1907.004 MB/s

   Random Read 4KiB (Q= 1,T= 1) :    53.942 MB/s [ 13169.4 IOPS]

  Random Write 4KiB (Q= 1,T= 1) :    52.104 MB/s [ 12720.7 IOPS]

  Test : 50 MiB [C: 5.2% (15.6/299.5 GiB)] (x1)  [Interval=5 sec]

  Date : 2017/03/25 20:29:18

    OS : Windows 10 Enterprise [10.0 Build 14393] (x64)

a few seconds later on the same setup i get perfectly fine results:

-----------------------------------------------------------------------

CrystalDiskMark 5.2.0 x64 (C) 2007-2016 hiyohiyo

                           Crystal Dew World : http://crystalmark.info/

-----------------------------------------------------------------------

* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]

* KB = 1000 bytes, KiB = 1024 bytes

   Sequential Read (Q= 32,T= 2) :  6655.386 MB/s

  Sequential Write (Q= 32,T= 2) :  5654.851 MB/s

  Random Read 4KiB (Q= 32,T= 2) :   695.193 MB/s [169724.9 IOPS]

Random Write 4KiB (Q= 32,T= 2) :   609.216 MB/s [148734.4 IOPS]

         Sequential Read (T= 1) :  1810.393 MB/s

        Sequential Write (T= 1) :  1626.112 MB/s

   Random Read 4KiB (Q= 1,T= 1) :    53.266 MB/s [ 13004.4 IOPS]

  Random Write 4KiB (Q= 1,T= 1) :    54.289 MB/s [ 13254.2 IOPS]

  Test : 50 MiB [C: 5.2% (15.7/299.5 GiB)] (x1)  [Interval=5 sec]

  Date : 2017/03/25 20:32:21

    OS : Windows 10 Enterprise [10.0 Build 14393] (x64)

I have my ESXi 6.5 server up for about 3 months without issue. Starting a few days ago an error occurs on login. If I choose "reload" I'm returned to logon splash seems to be in a loop. If I use the browser refresh ( found this out by accident) instead of the reload button it makes to the navigation page. Do I need to rebuild my server?

Hi there

I have recently installed and setup a new installation of ESXi 6.0U3 on a PowerEdge R740 and am having issues with the disks speeds being appallingly slow.

I have made a datastore on the host and have tried it with both a RAID 5 configuration and non-RAID as well but both are very slow.  When doing an SCP transfer to the disk is usually sits around 20-50 K/s and trying to run a VM to install an OS loading the Windows 10 ISO takes over an hour.

The host is using a Lewisburg SATA AHCI Controller.

Can anyone help me troubleshoot this issue?

Thanks in advance.

vcenter 6, build 6855219, ESXi 6.0.0 build 7967664

Host profile failed on one out of 16 hosts in the same cluster.

Unexpected error checking compliance: 'NoneType' object has no attribute 'config'

Hi experts,

I am getting strange behavior for ESXI6.5 (installed as test at my home clone server). Like i have installed 2 SSD, one is Intel M.2 and another is transcend SATA III SSD. from both SSD i have created datastore. But i am getting different speed on the 2 SSD like on intel i am getting full speed but on transcend i am getting only 16mbps speed. tried to search google, but didnt got any solution. my ESXI is installed on intel M.2 SSD.

Pls find the speed diff (2.02 vs 22.77 MB/s) t10.ATA is transcend and NVMe is Intel M.2

Pls suggest what to do.

My server config:

Processor: Intel(R) Core(TM) i7-6800K

RAM: 128GB

Motherboard : GA-X99-Ultra Gaming

No RAID

I am using cisco E160D M2 and trying to upgrade using cisco custom zip

/vmfs/volumes/5601fe4b-f537c738-d337-f872ea9f3d18 # esxcli software vib install -d /vmfs/volumes/sha-esxi1-vmfs/Vmware-ESXi-6.5d.0-5310538-Custom-Cisco-6.5.0.4.zip

[DependencyError]

VIB LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

/vmfs/volumes/5601fe4b-f537c738-d337-f872ea9f3d18 #

any idea why? Should i force the installation with -f?

Hi Friends,

                 for couple of hours an alarm has showing "vmware vfabric postgres service health alarm"

Hello,

I'm trying to install updates from a zip file but always gives the same error. "No Space Left On Device"

But there is a plenty of space on Device.

When i try to run

esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201703001.zip

it gives that error:

[InstallationError]

[Errno 28] No space left on device

       vibs = VMware_bootbank_misc-drivers_6.0.0-3.57.5050593

Please refer to the log file for more details.

And in the log file:

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:50Z esxupdate: BootBankInstaller.pyc: WARNING: Cannot remove staging directory: [Errno 16] Device or resource busy: '/tmp/stagebootbank'

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:51Z esxupdate: root: ERROR: Traceback (most recent call last):

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 462, in <module>

2017-04-02T00:13:51Z esxupdate: root: ERROR:     main()

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 453, in main

2017-04-02T00:13:51Z esxupdate: root: ERROR:     ret = CMDTABLE[command](options)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 362, in VibInstallCmd

2017-04-02T00:13:51Z esxupdate: root: ERROR:     checkacceptance=checkacceptance)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 250, in InstallVibsFromSources

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 356, in _installVibs

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 399, in _validateAndInstallProfile

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 710, in Stage

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 483, in _download_and_stage

2017-04-02T00:13:51Z esxupdate: root: ERROR: InstallationError: ('VMware_bootbank_vsanhealth_6.0.0-3000000.3.0.3.58.5224738', '[Errno 28] No space left on device')

"vdf -h" Output

Ramdisk                   Size      Used Available Use% Mounted on

root                       32M      244K       31M   0% --

etc                        28M      204K       27M   0% --

opt                        32M        0B       32M   0% --

var                        48M      428K       47M   0% --

tmp                       256M       20K      255M   0% --

iofilters                  32M        0B       32M   0% --

hostdstats                303M        2M      300M   0% --

As you can see %0 is used on /tmp i dont know why gives that error.

How can i fix this problem ? I cant update my esxi 3620759 to 5224934.

hi All

I installed ESXi on a Asrock X99 Extreme6 mainboard. Everything works fine except the Atheros network interface.

I allready tried the Atheros AR8161 VIB Driver and

• net-atl1: Attansic/Atheros L1 Gigabit Ethernet driver
• net-atl1e: Driver for Atheros(R) AR8121/AR8113/AR8114/AR8131/AR8132/AR8152 PCI-E Ethernet NICs

Does anyone has a VIB driver file for the atheros ar8171 interface?

Thanks,

Stefan

Hello,

vSphere 6.7

vSphere Replication Appliance 8.1.0.6060 Build 8744176

We have host1 in datacenter1, and host2 in datacenter2.

When I do a vMotion from host1 to host2, the vMotion works fine.

But when i do a replication from host1 to host2, i get error:

No host can be used to access datastore path '[datastore2]'.

Why replication does not work?

Hello,

vSphere 6.7

We have host with two NIC:

nic0 (vmk0, vswitch0) - public IP settings (get via provider DHCP)

nic1 (vmk1, vswitch1) - private IP settings (manually set)

How to set my private DNS server address in this configuration?

hello,

is it possible to install esxi 6.5 on realtek 8168 nic motherboard..

is it correct that - In order to configure vcenter HA should i keep different vcenter hostname (OS) names  from their inventory names? 

in guides i find - HA handles itself all the cloning process. So i think it does not matter that if i keep hostname and inventory names same of vcenter.

should i keep my vcenter hostname different from inventory names in vcenter inventory or it does not matter -

any idea and any guide you can point me.

how do I attach a vmnic directly to a network mornitoring appliance? I need this foir monitoring

We are getting very similar results as this thread.

Repeated com.vmware.vcHms messages to install vr2c-firewall.vib

As all our hosts are attempting to install this firewall VIB ever 4 hours (according to the esxupdate.log file on the host).

The vSphere Console is showing the following. install followed by update SSL thumbprint registry.

I am trying to determine what the install is, why it happens so often and if it is an issue or not.

Below you will find a selection of the esxupdate.log file edited with our IP Addresses and domain name out.

2015-11-13T16:34:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetTimeout']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRetries']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-q', '-g', '/UserVars/EsximageNetRateLimit']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:28Z esxupdate: esxupdate: INFO: ---

Command: update

Args: ['update']

Options: {'nosigcheck': None, 'retry': 5, 'loglevel': None, 'cleancache': None, 'viburls': ['https://vRA IP ADDRESS:8043/vib/vr2c-firewall.vib'], 'meta': None, 'proxyurl': 'dalvsphere01.contoso.com:80', 'timeout': 30.0, 'cachesize': None, 'hamode': True, 'maintenancemode': None}

2015-11-13T16:34:29Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:29Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:29Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_6.0.0-1.17.3029758 to ImageProfile (Updated) HP-ESXi-6.0.0-iso-600.9.1.39

2015-11-13T16:34:29Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:29Z esxupdate: downloader: DEBUG: Downloading from https://vRA IP ADDRESS:8043/vib/vr2c-firewall.vib...

2015-11-13T16:34:29Z esxupdate: Transaction: INFO: Skipping installed VIBs VMware_bootbank_vr2c-firewall_6.1.0.10819-3051487

2015-11-13T16:34:29Z esxupdate: Transaction: INFO: Final list of VIBs being installed:

2015-11-13T16:34:29Z esxupdate: HostImage: DEBUG: Staging image profile [(Updated) HP-ESXi-6.0.0-iso-600.9.1.39]

2015-11-13T16:34:29Z esxupdate: HostImage: DEBUG: VIBs in image profile: VMware_bootbank_sata-sata-sil_2.3-4vmw.600.0.0.2494585, VMware_bootbank_lsi-mr3_6.605.08.00-7vmw.600.1.17.3029758, VMware_bootbank_scsi-ips_7.12.05-4vmw.600.0.0.2494585, Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.12-1OEM.550.0.0.1331820, Hewlett-Packard_bootbank_char-hpcru_6.0.6.14-1OEM.600.0.0.2159203, Hewlett-Packard_bootbank_hponcfg_6.0.0.04-00.13.17.2159203, VMware_bootbank_ipmi-ipmi-devintf_39.1-4vmw.600.0.0.2494585, Hewlett-Packard_bootbank_hpssacli_2.0.23.0-5.5.0.1198610, VMware_bootbank_sata-sata-promise_2.12-3vmw.600.0.0.2494585, VMware_bootbank_net-bnx2x_1.78.80.v60.12-1vmw.600.0.0.2494585, VMware_bootbank_sata-sata-nv_3.5-4vmw.600.0.0.2494585, VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_scsi-mptsas_4.23.01.00-9vmw.600.0.0.2494585, VMware_bootbank_sata-sata-svw_2.3-3vmw.600.0.0.2494585, VMwa

2015-11-13T16:34:29Z esxupdate: re_bootbank_lsu-lsi-megaraid-sas-plugin_1.0.0-2vmw.600.0.11.2809209, Hewlett-Packard_bootbank_hp-conrep_6.0.0.1-0.0.13.2159203, VMware_bootbank_scsi-adp94xx_1.0.8.12-6vmw.600.0.0.2494585, VMware_bootbank_esx-tboot_6.0.0-0.0.2494585, VMware_bootbank_uhci-usb-uhci_1.0-3vmw.600.0.0.2494585, Brocade_bootbank_scsi-bfa_3.2.3.0-1OEM.550.0.0.1198610, VMware_bootbank_cpu-microcode_6.0.0-0.0.2494585, VMware_bootbank_xhci-xhci_1.0-2vmw.600.1.17.3029758, VMware_bootbank_scsi-fnic_1.5.0.45-3vmw.600.0.0.2494585, VMware_bootbank_net-tg3_3.131d.v60.4-1vmw.600.0.0.2494585, VMware_bootbank_scsi-bnx2i_2.78.76.v60.8-1vmw.600.0.11.2809209, VMware_bootbank_scsi-bnx2fc_1.78.78.v60.8-1vmw.600.0.0.2494585, VMware_bootbank_scsi-qla4xxx_5.01.03.2-7vmw.600.0.0.2494585, VMware_bootbank_lsu-hp-hpsa-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_rste_2.0.2.0088-4vmw.600.0.0.2494585, VMware_bootbank_sata-ahci_3.0-22vmw.600.

2015-11-13T16:34:29Z esxupdate: 1.17.3029758, VMware_bootbank_block-cciss_3.6.14-10vmw.600.0.0.2494585, VMware_bootbank_misc-cnic-register_1.78.75.v60.7-1vmw.600.0.0.2494585, VMware_bootbank_ata-pata-sil680_0.4.8-3vmw.600.0.0.2494585, VMware_bootbank_net-forcedeth_0.61-2vmw.600.0.0.2494585, VMware_bootbank_nmlx4-en_3.0.0.0-1vmw.600.0.0.2494585, VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.600.0.0.2494585, VMware_bootbank_ata-pata-via_0.3.3-2vmw.600.0.0.2494585, VMware_bootbank_vr2c-firewall_6.1.0.10819-3051487, VMware_bootbank_esx-base_6.0.0-1.20.3153772, VMware_bootbank_emulex-esx-elxnetcli_10.2.309.6v-0.0.2494585, VMware_locker_tools-light_6.0.0-1.17.3029758, VMware_bootbank_ata-pata-atiixp_0.4.6-4vmw.600.0.0.2494585, VMware_bootbank_net-mlx4-core_1.9.7.0-1vmw.600.0.0.2494585, VMware_bootbank_net-cnic_1.78.76.v60.13-2vmw.600.0.0.2494585, VMware_bootbank_net-e1000_8.0.3.1-5vmw.600.0.0.2494585, Hewlett-Packard_bootbank_hp-ams_60

2015-11-13T16:34:29Z esxupdate: 0.10.1.0-32.2159203, VMware_bootbank_ata-pata-cmd64x_0.2.5-3vmw.600.0.0.2494585, VMware_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.600.0.0.2494585, VMware_bootbank_net-vmxnet3_1.1.3.0-3vmw.600.0.0.2494585, VMware_bootbank_ima-qla4xxx_2.02.18-1vmw.600.0.0.2494585, VMware_bootbank_lsu-lsi-lsi-mr3-plugin_1.0.0-2vmw.600.0.11.2809209, VMware_bootbank_lsi-msgpt3_06.255.12.00-8vmw.600.1.17.3029758, VMware_bootbank_vmware-fdm_6.0.0-2656760, VMware_bootbank_lsu-lsi-mpt2sas-plugin_1.0.0-4vmw.600.1.17.3029758, VMWARE_bootbank_mtip32xx-native_3.8.5-1vmw.600.0.0.2494585, VMware_bootbank_net-ixgbe_3.7.13.7.14iov-20vmw.600.0.0.2494585, VMware_bootbank_nvme_1.0e.0.35-1vmw.600.1.17.3029758, Hewlett-Packard_bootbank_hpacucli_9.20-9.0, VMware_bootbank_nmlx4-core_3.0.0.0-1vmw.600.0.0.2494585, VMware_bootbank_esx-xserver_6.0.0-0.0.2494585, VMware_bootbank_sata-ata-piix_2.12-10vmw.600.0.0.2494585, VMware_bootbank_qlnativ

2015-11-13T16:34:29Z esxupdate: efc_2.0.12.0-5vmw.600.0.0.2494585, Hewlett-Packard_bootbank_hp-smx-provider_600.03.07.00.23-2159203, VMware_bootbank_lsu-lsi-mptsas-plugin_1.0.0-1vmw.600.0.0.2494585, VMware_bootbank_ohci-usb-ohci_1.0-3vmw.600.0.0.2494585, VMware_bootbank_misc-drivers_6.0.0-1.17.3029758, VMware_bootbank_ata-pata-serverworks_0.4.3-3vmw.600.0.0.2494585, VMware_bootbank_net-nx-nic_5.0.621-5vmw.600.0.0.2494585, VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585, VMware_bootbank_sata-sata-sil24_1.1-1vmw.600.0.0.2494585, Hewlett-Packard_bootbank_hp-esxi-fc-enablement_550.2.1.8-1198610, VMware_bootbank_ata-pata-amd_0.3.10-3vmw.600.0.0.2494585, VMware_bootbank_net-bnx2_2.2.4f.v60.10-1vmw.600.0.0.2494585, VMware_bootbank_scsi-megaraid2_2.00.4-9vmw.600.0.0.2494585, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.600.0.0.2494585, Emulex_bootbank_ima-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820, QLogic_bootbank_net-qlcnic_5.5.190-

2015-11-13T16:34:29Z esxupdate: 1OEM.550.0.0.1331820, Emulex_bootbank_scsi-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820, Hewlett-Packard_bootbank_hpnmi_600.2.3.14-2159203, VMware_bootbank_net-mlx4-en_1.9.7.0-1vmw.600.0.0.2494585, VMware_bootbank_nmlx4-rdma_3.0.0.0-1vmw.600.0.0.2494585, Hewlett-Packard_bootbank_hp-esx-license_1.0-05, VMware_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.600.0.0.2494585, Hewlett-Packard_bootbank_char-hpilo_600.9.0.2.8-1OEM.600.0.0.2159203, VMware_bootbank_lpfc_10.2.309.8-2vmw.600.0.0.2494585, Hewlett-Packard_bootbank_hp-build_600.9.1.39-2159203, VMware_bootbank_scsi-megaraid-sas_6.603.55.00-2vmw.600.0.0.2494585, VMware_bootbank_net-igb_5.0.5.1.1-5vmw.600.0.0.2494585, VMware_bootbank_scsi-aacraid_1.1.5.1-9vmw.600.0.0.2494585, VMware_bootbank_scsi-mptspi_4.23.01.00-9vmw.600.0.0.2494585, Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-90OEM.550.0.0.1331820, Hewlett-Packard_bootbank_hpbootcfg_6.0.0.02-01.00.11.2159203, H

2015-11-13T16:34:29Z esxupdate: ewlett-Packard_bootbank_vmware-esx-hp_vaaip_p2000_2.1.0-2, VMware_bootbank_esx-dvfilter-generic-fastpath_6.0.0-0.0.2494585, VMware_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.600.0.0.2494585, VMware_bootbank_elxnet_10.2.309.6v-1vmw.600.0.0.2494585, VMware_bootbank_scsi-aic79xx_3.1-5vmw.600.0.0.2494585, Hewlett-Packard_bootbank_hptestevent_6.0.0.01-00.00.8.2159203, VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.600.0.0.2494585, VMware_bootbank_vsanhealth_6.0.0-3000000.2.0.1.17.2972216, VMware_bootbank_net-enic_2.1.2.38-2vmw.600.0.0.2494585, VMware_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.600.0.0.2494585, VMware_bootbank_scsi-hpsa_6.0.0.44-4vmw.600.0.0.2494585

2015-11-13T16:34:29Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/usr/sbin/vsish', '-e', '-p', 'cat', '/hardware/bios/dmiInfo']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:29Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/smbiosDump']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2015-11-13T16:34:29Z esxupdate: imageprofile: DEBUG: VIB VMware_locker_tools-light_6.0.0-1.17.3029758 is being removed from ImageProfile (Updated) HP-ESXi-6.0.0-iso-600.9.1.39

2015-11-13T16:34:29Z esxupdate: HostImage: INFO: Nothing for LiveImageInstaller to do, skipping.

2015-11-13T16:34:29Z esxupdate: imageprofile: DEBUG: VIB VMware_locker_tools-light_6.0.0-1.17.3029758 is being removed from ImageProfile (Updated) HP-ESXi-6.0.0-iso-600.9.1.39

2015-11-13T16:34:29Z esxupdate: HostImage: INFO: Nothing for BootBankInstaller to do, skipping.

2015-11-13T16:34:29Z esxupdate: HostImage: INFO: Nothing for LockerInstaller to do, skipping.

2015-11-13T16:34:29Z esxupdate: HostImage: DEBUG: Host is remediated by installer:

2015-11-13T16:34:29Z esxupdate: esxupdate: DEBUG: <<<

[root@adsesx16:/var]

Dear all,

after updating one host to the latest build 6.7.0 (Build 9214924) VEEAM BACKUP Cannot detect the storages with the below error.

processing DC01 Error: NFC storage connection is unavailable.

I have restarted the management agents but the issue is still exisiting.

Can someone please point me to right direction how to get this fixed ?

After updating to the latest BIOS 3.0(4i), I encounter the error below.

How should I troubleshoot on this ?

We have ESXi version: Esxi5.5.0, 8934887 on Dell PE R630 server

With the commands below we have the error report.

Looks like VOMA does not able to check the partition.

Anybody could you please help to resolve the problem?

Full output log is attached here.

# voma -m vmfs -f check -d /vmfs/devices/disks/naa.61866da0a6d9c80022da06c20f21310d:3

Checking if device is actively used by other hosts

Initializing VMFS Checker..|Scanning for VMFS-3/VMFS-5 host activity (512 bytes/HB, 2048 HBs).

Running VMFS Checker version 1.0 in check mode

Initializing LVM metadata, Basic Checks will be done

Phase 1: Checking VMFS header and resource files

   Detected VMFS file system (labeled:'esxi43bg_datastore_os') with UUID:5b475391-63c355f6-75bb-246e962bf144, Version 5:60

ON-DISK ERROR: Unexpected 'resourceSize' 8192, expected 65536

ON-DISK ERROR: Unexpected 'clusterGroupSize' 33619968, expected 268500992

ON-DISK ERROR: <FD c0 r4> : Invalid zla type 0x1

ON-DISK ERROR: Block count mismatch(0): PBA cow 0 cnum 0 rnum 0

ON-DISK ERROR: Block count mismatch(1): PBA cow 0 cnum 0 rnum 0

ON-DISK ERROR: Block count mismatch(2): PBA cow 0 cnum 0 rnum 0

...

ON-DISK ERROR: Block count mismatch(249): PBA cow 0 cnum 0 rnum 0

ON-DISK ERROR: Block count mismatch(250): PBA cow 0 cnum 0 rnum 0

         ERROR: Resource file values has been guessed wrong.

         May be because of wrong minor version in disk

         Number of blocks for system file 502 (expected 2001) mismatch.

ON-DISK ERROR: Corruption too severe in resource file [SB]

         ERROR: Failed to check sbc.sf.

ON-DISK ERROR: VMFS Checker has found severe errors in volume esxi43bg_datastore_os. We strongly recommend you backup your data externally and then recreate a new volume.

   VOMA failed to check device : Severe corruption detected

Total Errors Found:           255

I'm not sure if this is the right place to post this, but I couldn't find a bug tracker for ESXi.

The host has been running ESXi 6.0 and now 6.7 without issue for a couple years. After reboot, it's all back to normal; so, I don't think it's a hardware problem. I wasn't doing anything in particular when this happened. I.e., no easy repro.

Host: VMkernel esxi2 6.7.0 #1 SMP Release build-8169922 Apr  3 2018 14:48:22 x86_64 x86_64 x86_64 ESXi

Stack trace:

Line prefix: 2018-05-24T00:44:53.953Z, cpu13:2097958)

@BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4924 - Usage error in dlmalloc

Code start: 0x41801cc00000 VMK uptime: 28:20:55:23.811

0x451a0a79b470:[0x41801cd08ca5]PanicvPanicInt@vmkernel#nover+0x439 stack: 0x7520676e69726f6e

0x451a0a79b510:[0x41801cd08ed8]Panic_NoSave@vmkernel#nover+0x4d stack: 0x451a0a79b570

0x451a0a79b570:[0x41801cd512c2]DLM_free@vmkernel#nover+0x657 stack: 0x431c091f1fb0

0x451a0a79b590:[0x41801cd4e4b0]Heap_Free@vmkernel#nover+0x115 stack: 0x451a0a79b630

0x451a0a79b5e0:[0x41801df056ca]CbtAsyncIODone@(hbr_filter)#<None>+0x2b stack: 0x459a40a26800

0x451a0a79b610:[0x41801ccc89a2]AsyncPopCallbackFrameInt@vmkernel#nover+0x4b stack: 0x451a0a79b670

0x451a0a79b640:[0x41801df072a9]Lwd_IssuePendingIO@(hbr_filter)#<None>+0x9a stack: 0x431c09235c50

0x451a0a79b670:[0x41801defa413]DemandLogReadTokenCallback@(hbr_filter)#<None>+0x1a4 stack: 0x41801cf76149

0x451a0a79b7a0:[0x41801ccc89a2]AsyncPopCallbackFrameInt@vmkernel#nover+0x4b stack: 0x459a40a0d000

0x451a0a79b7d0:[0x41801ccc89a2]AsyncPopCallbackFrameInt@vmkernel#nover+0x4b stack: 0x459a40b16b80

0x451a0a79b800:[0x41801cface08]VSCSI_FSVirtAsyncDone@vmkernel#nover+0x59 stack: 0x17eda3ffe77b66

0x451a0a79b810:[0x41801ccc89a2]AsyncPopCallbackFrameInt@vmkernel#nover+0x4b stack: 0x459a40a55398

0x451a0a79b840:[0x41801cc4d96b]FS_IOAccessDone@vmkernel#nover+0x68 stack: 0x1

0x451a0a79b860:[0x41801ccc89a2]AsyncPopCallbackFrameInt@vmkernel#nover+0x4b stack: 0x459a5d587d00

0x451a0a79b890:[0x41801cc678e8]FDSAsyncTokenIODone@vmkernel#nover+0x91 stack: 0x459a5a861900

0x451a0a79b8c0:[0x41801cf65b2a]SCSIDeviceCmdCompleteInt@vmkernel#nover+0x6f stack: 0x459a410ba240

0x451a0a79b930:[0x41801cf66a17]SCSIDeviceCmdCompleteCB@vmkernel#nover+0x2bc stack: 0x41801d8be5c4

0x451a0a79ba10:[0x41801cf68a2e]SCSICompleteDeviceCommand@vmkernel#nover+0xa7 stack: 0x0

0x451a0a79bb10:[0x41801d883fa0]nmp_CompleteCommandForDevice@com.vmware.vmkapi#v2_5_0_0+0x39 stack: 0x459a5b8cb340

0x451a0a79bb70:[0x41801d884468]nmp_CompleteCommandForPath@com.vmware.vmkapi#v2_5_0_0+0x61 stack: 0x418043400d40

0x451a0a79bcc0:[0x41801cf888c4]SCSICompletePathCommand@vmkernel#nover+0x1f5 stack: 0x430469218180

0x451a0a79bd90:[0x41801cf77849]SCSICompleteAdapterCommand@vmkernel#nover+0x13e stack: 0x900000200

0x451a0a79be20:[0x41801d5f1978]SCSILinuxWorldletFn@com.vmware.driverAPI#9.2+0x3f1 stack: 0x430874ce72e0

0x451a0a79bf80:[0x41801cd3e694]WorldletFunc@vmkernel#nover+0xf5 stack: 0x0

0x451a0a79bfe0:[0x41801cf081f2]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0

base fs=0x0 gs=0x418043400000 Kgs=0x0

Lemme know if you need more info.

Hi.

I installed a ESXi 6.5 server and moved my VM's from old server (5.5) to the new one.

The new server runs from a USB stick and my datastores is on a SSD drive.

In one VM i use som USB-adapters, so i connect the usb-adapters I use to the VM.

But that is not without problems.

firsh I head this problem: https://labs.vmware.com/flings/esxi-embedded-host-client/bugs/116

Then I head this problem: (unable to dismount USB devices) https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2068645

But what is I buy a new PCI-Express USB-conroller card and then use PCI-Passthrough  to it, will that work, og will I have the same problems?