Hello guys,

I just install a fresh ESXi 6.0 on my new server but in dmesg i got spam like this:

2018-04-07T11:57:07.608Z cpu5:33150)ScsiDeviceIO: 2636: Cmd(0x43b5c0870240) 0x85, CmdSN 0x103 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T12:27:07.626Z cpu4:32916)ScsiDeviceIO: 2636: Cmd(0x43b5c08528c0) 0x4d, CmdSN 0x10d from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T12:52:21.148Z cpu1:34192)ScsiDeviceIO: 2636: Cmd(0x43b5c088bfc0) 0x1a, CmdSN 0x110e from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T13:27:07.657Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c08daec0) 0x85, CmdSN 0x11b from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T13:57:07.681Z cpu5:33288)ScsiDeviceIO: 2636: Cmd(0x43b5c083bfc0) 0x1a, CmdSN 0x11c4 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T14:22:22.030Z cpu6:33480)ScsiDeviceIO: 2636: Cmd(0x43b5c0850340) 0x1a, CmdSN 0x11fd from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T15:01:01.192Z cpu3:32916)ScsiDeviceIO: 2636: Cmd(0x43b5c084d740) 0x1a, CmdSN 0x126c from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T15:57:07.741Z cpu7:33044)ScsiDeviceIO: 2636: Cmd(0x43b5c085a740) 0x85, CmdSN 0x140 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T15:57:07.748Z cpu7:32863)ScsiDeviceIO: 2636: Cmd(0x43b5c085a740) 0x1a, CmdSN 0x12f5 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T16:32:23.323Z cpu7:32785)ScsiDeviceIO: 2636: Cmd(0x43b5c0846e80) 0x1a, CmdSN 0x135e from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T17:27:07.802Z cpu1:32867)ScsiDeviceIO: 2636: Cmd(0x43b5c0835900) 0x85, CmdSN 0x158 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T17:27:07.816Z cpu1:32836)ScsiDeviceIO: 2636: Cmd(0x43b5c0835900) 0x4d, CmdSN 0x15d from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T18:02:24.194Z cpu5:33226)ScsiDeviceIO: 2636: Cmd(0x43b5c07bddc0) 0x1a, CmdSN 0x144d from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T18:57:07.865Z cpu5:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08bbcc0) 0x1a, CmdSN 0x172 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T18:57:07.875Z cpu5:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08bbcc0) 0x1a, CmdSN 0x14d0 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T19:42:25.184Z cpu5:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08bac40) 0x1a, CmdSN 0x1542 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T20:27:07.943Z cpu3:33044)ScsiDeviceIO: 2636: Cmd(0x43b5c08d0e00) 0x1a, CmdSN 0x18a from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T20:57:07.961Z cpu3:33143)ScsiDeviceIO: 2636: Cmd(0x43b5c07e25c0) 0x1a, CmdSN 0x1601 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T21:12:26.060Z cpu2:33290)ScsiDeviceIO: 2636: Cmd(0x43b5c083d940) 0x1a, CmdSN 0x1631 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T21:57:07.984Z cpu7:32836)ScsiDeviceIO: 2636: Cmd(0x43b5c07c2b00) 0x85, CmdSN 0x1a3 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T22:27:08.004Z cpu7:32803)ScsiDeviceIO: 2636: Cmd(0x43b5c08709c0) 0x4d, CmdSN 0x1ad from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T22:52:27.109Z cpu3:32771)ScsiDeviceIO: 2636: Cmd(0x43b5c0883880) 0x1a, CmdSN 0x1726 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-07T23:27:08.027Z cpu5:33733)ScsiDeviceIO: 2636: Cmd(0x43b5c0892e00) 0x85, CmdSN 0x1bb from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-07T23:57:08.072Z cpu5:32838)ScsiDeviceIO: 2636: Cmd(0x43b5c0880100) 0x1a, CmdSN 0x17dc from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T00:22:28.016Z cpu2:33226)ScsiDeviceIO: 2636: Cmd(0x43b5c080a1c0) 0x1a, CmdSN 0x1815 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T01:01:01.761Z cpu7:33454)ScsiDeviceIO: 2636: Cmd(0x43b5c085c6c0) 0x1a, CmdSN 0x1884 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T01:57:08.157Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c07f3b80) 0x85, CmdSN 0x1e0 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-08T01:57:08.173Z cpu6:33275)ScsiDeviceIO: 2636: Cmd(0x43b5c07f3b80) 0x1a, CmdSN 0x190d from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T02:32:29.338Z cpu1:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c0845680) 0x1a, CmdSN 0x1976 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T03:27:08.211Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c0894000) 0x85, CmdSN 0x1f8 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-08T03:27:08.213Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c0894000) 0x4d, CmdSN 0x1fd from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-08T04:02:30.247Z cpu3:34200)ScsiDeviceIO: 2636: Cmd(0x43b5c0814a40) 0x1a, CmdSN 0x1a65 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T04:57:08.264Z cpu7:33043)ScsiDeviceIO: 2636: Cmd(0x43b5c08516c0) 0x1a, CmdSN 0x212 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T04:57:08.280Z cpu7:33043)ScsiDeviceIO: 2636: Cmd(0x43b5c08516c0) 0x1a, CmdSN 0x1ae8 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T05:42:31.261Z cpu3:33164)ScsiDeviceIO: 2636: Cmd(0x43b5c08be9c0) 0x1a, CmdSN 0x1b5a from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T06:27:08.391Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c0802b00) 0x1a, CmdSN 0x22a from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T06:57:08.407Z cpu2:34414)ScsiDeviceIO: 2636: Cmd(0x43b5c081a800) 0x1a, CmdSN 0x1c19 from world 0 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T07:12:32.127Z cpu2:33276)ScsiDeviceIO: 2636: Cmd(0x43b5c07eb200) 0x1a, CmdSN 0x1c49 from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2018-04-08T07:57:08.442Z cpu7:33219)ScsiDeviceIO: 2636: Cmd(0x43b5c08581c0) 0x85, CmdSN 0x243 from world 34414 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-08T08:27:08.472Z cpu3:32863)ScsiDeviceIO: 2636: Cmd(0x43b5c0898640) 0x4d, CmdSN 0x24d from world 34414 to dev "naa.600605b00cd0cf6022439b0b2a9c2622" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-04-08T08:30:20.129Z cpu7:32984)ScsiDeviceIO: 2636: Cmd(0x43b5c0858640) 0x1a, CmdSN 0x1d2f from world 0 to dev "naa.600605b00cd0cf6022439b052a3716ef" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

This is a server with 2x SSD and 2x HDD i create 2x RAID1 from this all 4 devices.

[root@esx03:~] lspci |grep -i raid

0000:06:00.0 Mass storage controller: Avago (LSI / Symbios Logic) MegaRAID SAS Fusion Controller [vmhba1]

Anyone can tell me what`s that mean and how to disable this spam in dmesg?

Best Regards

TaKeN

Hello All,

I am currently using ESXi 6.5.0 Update 3 (Build 16576891) and each time I login to my ESXi client I get the following alert:

Sensor: System Board 8 Memory -- 0.7.8.43

Health: Yellow

SEL entries: 0

Current reading: 65 error

Category: Memory

In vSphere (Version 6.5.0, Build: 9451637) it shows it as:

    <group HealthState="10" name="Memory">

      <CIM_NumericSensor key="0.7.8.43">

        <Name>System Board 8 Memory</Name>

        <HealthState>10</HealthState>

        <CurrentReading>65</CurrentReading>

        <UnitModifier>0</UnitModifier>

        <BaseUnits/>

        <RateUnits>0</RateUnits>

        <ElementName>System Board 8 Memory</ElementName>

      </CIM_NumericSensor>

I am running this on an HP Proliant DL360 G6 Server. I have tried all of the memory diagnostic tools and I updated the firmware for the server and still no luck. Any ideas what this means?

Any advice or feedback would be greatly appreciated. Thank you!

Hi Everyone,

I just retrieve a DL 380 G6 server, with some disks and RAM. I wanted to Install ESXI 6.5.0 on it (with a special edited image).

When installing ESXI, i've got no problem, it boot normally etc...
The problem appears when i'm installing a OS on a Guest (whatever, Ubuntu, Debian or Windows). It start the installation and freeze after that, showing me this "beautiful" PSOD.

I did a memtest86 but there is no error.

It doesn't came from the ESXI image but of the server itself, cause i tried with other OS (Proxmox, debian, ubuntu) and all of them have problems at the installation.

So the PSOD is my only way to solve all this problems.

Here is a OCR of the screen, and the screen itself in case of bad recognation.

Thank you in advance everybody !

Muare ES)(i 6.5.0 [Releasebuild-5310538 x86_64]

LINT1/NMI (motherboard nonmaskable interrupt), undiagnosed. This may be a hardware problem; please contact your hardware vendor

r04Ix8001003d cr241x430000f80000 cr341xdf622000 cr441x216c

*PCPUO:70231/fssA10-27-7

PCPU 0: SUUSUSSV

ode start: 0x41801c800000 VMK uptime: 0:04:07:18.265

0x438040002c60J0x41801c8ec931]PanicvPanicInt0vmkernelltnover+0x545 stack: 0x41801c8ec931

0x438040002d00J0x41801c8ec9bd]Panic_MoSave@vmkernelltnover+0x4d stack: 0x438040002d60

0x438040002d60J0x41801c8e9c8e]MMICheckLintAvmkernelltnover+0x19a stack: 0x0

0x438040002e20J0x41801c8e9d24MMI_Interrupt0vmkernelltnover+0x94 stack: 0x0

0x438040002ea0J0x41801c92bb111IDTMMIWork0vmkernelltnover+0x99 stack: 0x0

0x438040002f20:I0x41801c92cfa1]Int2_MMI0vmkernelltnover+0x19 stack: 0x418040000000

0x438040002f40J0x41801c93c044]gate_entry_Pvmkernelltnover+0x0 stack: 0x0

0x439152b9bc70:I0x41801c88aec2Power_ArchSetCStatePvmkernelltnover+0x106 stack: 0x7fffffffffffffff

0x439152b9bca0J0x41801cac44b3]CpuSchedIdleLoopInt@vmkernelltnover+0x39b stack: 0x1

0x439152b9bd10:[0x41801cac6d6a]CpuSchedDispatch0vmkernelltnover+0x114a stack: 0x410000000001

0x439152b9be40:[0x41801cac7fe2]CpuSchedWait0vmkernelltnover+0x27a stack: 0x100430372f20080

0x439152b9bec0J0x41801cac8350]CpuSchedTimedWaitInt@vmkernelltnover+0xa8 stack: 0x206300002001

0x439152b9bf30:[0x41801cac8546]CpuSched_EventQueueTimedWait0vmkernelltnover+0x36 stack: 0x430372f20080

0x439152b9bf50:[0x41801c8c949c]helpFunc0vmkernelltnover+0x564 stack: 0x430078ff3050

0x439152b9bfe0J0x41801cac8c95]CpuSched_StartWorldPvmkernelltnover+0x99 stack: 0x0

lase fs=0x0 gs=0x418040000000 Kgs=0x0

'020-07-28T13:47:27.5477 cpu4:66541)Logs are stored on non-persistent storage. Consult product documentation to configure a sy

log server or a scratch partition.

oredump to disk. Slot 1 of 1 on device naa.600508b1001037383941424344450a00:9.

DiskDump: FAILED: Timeout

No file configured to dump data.

No vsan object configured to dump data.

No port for remote debugger. —Escape— for local debugger.

ESXI 6.5 U3 updated from 6.0 U3 reports this to me:

The Small Footprint CIM Broker Daemon (SFCBD) is running, but no data has been reported. You may need to install a CIM provider for your storage adapter.

on my Dell R710, maybe ESXI is not compatible with 6.5 but if any of you can give me a solution I would be grateful

An abstract of my vmkernel.log

We had storage incidents (crashes for unresolved bugs, being a readcache merge problem and a backend driver issue) on Unity 650F.

Dell is writing on a 'custom' fix on both issues. In the mean time we were asked to mitigate the controller autoresets, and upgrade to OE 5.0.3 which they agreed upon will not resolve the current controller resets. After complaints from our side, they digged into every component of our infra, to mitigate on the impact/issues on their storage. The following SCSI sense codes were found in the vmkernel log and we are referred to further seek host support to suppress 'illegal scsi commands'

These according to them are to addressed as they are contributing problems to crashe of a controller node , as target reset attempts are being made by the hosts (as seen from the storage side persfective)

2020-08-17T01:49:15.677Z cpu108:65805)ScsiDeviceIO: 3015: Cmd(0x439e4341dfc0) 0xfe, CmdSN 0xbbc2e5 from world 65687 to dev "naa.60060160e8004b00e2ca985c1400127d" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2020-08-17T01:49:15.677Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e4368a5c0, 65687) to dev "naa.60060160e8004b007e9d9a5cf732ff8e" on path "vmhba2:C0:T11:L47" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2020-08-17T01:49:15.677Z cpu65:3876714)ScsiDeviceIO: 3015: Cmd(0x439e43720dc0) 0xfe, CmdSN 0x719b30 from world 65687 to dev "naa.60060160e8004b007e9d9a5cf732ff8e" failed H:0x8 D:0x0 P:0x0 Invalid sense data: 0x80 0x41 0x0.

2020-08-17T01:49:15.677Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e435e02c0, 65687) to dev "naa.60060160e8004b0058fbdc5d4a63c4ba" on path "vmhba3:C0:T10:L102" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2020-08-17T01:49:15.677Z cpu65:3876714)ScsiDeviceIO: 3015: Cmd(0x439e43502940) 0xfe, CmdSN 0x382ef0 from world 65687 to dev "naa.60060160e8004b0058fbdc5d4a63c4ba" failed H:0x8 D:0x0 P:0x0 Invalid sense data: 0x80 0x41 0x0.

2020-08-17T01:49:15.877Z cpu65:3876714)NMP: nmp_ThrottleLogForDevice:3630: Cmd 0xf1 (0x439e435079c0, 65687) to dev "naa.60060160e8004b00de1a995cd70e3c6a" on path "vmhba3:C0:T12:L30" Failed: H:0x8 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

I entred those value to

https://www.virten.net/vmware/esxi-scsi-sense-code-decoder/?host=8&device=0&plugin=0&sensekey=80&asc=41&ascq=0&opcode=

so according to this, the HBA does a reset of the target, which in this case is a DELL EMC Unity FC port.

And now what ?

dev "naa.6006" is DELL EMC Storage, in my case Dell EMC Unity 650f running OE 4.5.1 (UWDC01) & OE 5.0.3 (UWDC02)

Current Dell EMC Unity Target code is OE 5.0.3

[root@esx070:~] esxcfg-scsidevs -m | grep "naa.60060160de004b005f5d2a5fbbcad438"

naa.60060160de004b005f5d2a5fbbcad438:1                                     /vmfs/devices/disks/naa.60060160de004b005f5d2a5fbbcad438:1                                     5f2a5df1-f99059c6-eed8-20040ff4978e  0  UWDC01_IT-PROD-WDC_V005

[root@esx070:~] esxcfg-scsidevs -m | grep "naa.60060160e8004b00e595255ec02cf074"

naa.60060160e8004b00e595255ec02cf074:1                                     /vmfs/devices/disks/naa.60060160e8004b00e595255ec02cf074:1                                     5e2596ab-2bec8188-f141-20040ff4978e  0  UWDC02_IT-PROD-WDC_V103

[root@esx070:~] vmkchdev -l | grep vmhba

0000:00:11.5 8086:a1d2 1734:1230 vmkernel vmhba0

0000:00:17.0 8086:a182 1734:1230 vmkernel vmhba1

0000:17:00.0 1077:2261 1077:029b vmkernel vmhba2 ----------------> FC HBA

0000:6d:00.0 1077:2261 1077:029b vmkernel vmhba3 ----------------> FC HBA

[root@esx070:~] /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -d

Dumping all key-value instance names:

Key Value Instance:  vmhba3/qlogic

Key Value Instance:  vmhba2/qlogic

Key Value Instance:  vmhba1/vmw_ahci

Key Value Instance:  vmhba0/vmw_ahci

Key Value Instance:  MOD_PARM/qlogic

[root@esx070:~] /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -l -i vmhba2/qlogic
Listing keys:
Name:   ADAPTER
Type:   string
value:
QLogic 16Gb 1-port FC to PCIe Gen3 x8 Adapter for QLE2690:
        FC Firmware Version: 8.05.61 (d0d5), Driver version 2.1.73.0

Host Device Name vmhba2

BIOS version 3.61
FCODE version 4.11
EFI version 6.11
Flash FW version 8.05.61
ISP: ISP2261, Serial# RFD1722T35676
MSI-X enabled
Request Queue = 0x4309f6548000, Response Queue = 0x4309f6569000
Request Queue count = 2048, Response Queue count = 512
Number of response queues for CPU affinity operation: 4
CPU Affinity mode enabled
Total number of MSI-X interrupts on vector 0 (handler = 23) = 26676
Total number of MSI-X interrupts on vector 1 (handler = 24) = 2186
Total number of MSI-X interrupts on vector 2 (handler = 25) = 1090148738
Total number of MSI-X interrupts on vector 3 (handler = 26) = 583007145
Total number of MSI-X interrupts on vector 4 (handler = 27) = 2055128386
Total number of MSI-X interrupts on vector 5 (handler = 28) = 1406005796
Device queue depth = 0x8
Number of free request entries = 1271
FAWWN support: disabled
FEC support: Disabled
Total number of outstanding commands: 0
Number of mailbox timeouts = 0
Number of ISP aborts = 0
Number of loop resyncs = 29
Host adapter:Loop State = [READY], flags = 0x20ae200
Link speed = [16 Gbps]

Dpc flags = 0x0
Link down Timeout =  010
Port down retry =  010
Login retry count =  010
Execution throttle = 2048
ZIO mode = 0x6, ZIO timer = 1
Commands retried with dropped frame(s) = 297

Product ID = 4953 5020 2261 0001

NPIV Supported : Yes
Max Virtual Ports = 254

SCSI Device Information:
scsi-qla0-adapter-node=20000024ff149042:160a00:0;
scsi-qla0-adapter-port=21000024ff149042:160a00:0;

Name:   TARGET
Type:   string
value:
Driver version 2.1.73.0

Host Device Name vmhba2

FC Target-Port List:
scsi-qla0-target-0=500000e0da81df29:122300:0:Online;
scsi-qla0-target-1=500000e0da81df39:142300:1:Online;
scsi-qla0-target-2=5006016249e4121e:140000:2:Online;
scsi-qla0-target-3=5006016349e0121e:120000:3:Online;
scsi-qla0-target-4=5006016849e4121e:140100:4:Online;
scsi-qla0-target-5=5006016a49e4121e:120200:5:Online;
scsi-qla0-target-6=5006016249e415ff:0e0000:6:Online;
scsi-qla0-target-7=5006016349e015ff:100000:7:Online;
scsi-qla0-target-8=5006016849e415ff:100100:8:Online;
scsi-qla0-target-9=5006016a49e415ff:0e0100:9:Online;
scsi-qla0-target-10=5006016249e41688:0e0500:a:Online;
scsi-qla0-target-11=5006016349e01688:100200:b:Online;
scsi-qla0-target-12=5006016849e41688:100300:c:Online;
scsi-qla0-target-13=5006016a49e41688:0e0300:d:Online;

Name:   NPIV
Type:   string
value:
Driver version 2.1.73.0

Host Device Name vmhba2

NPIV Supported : Yes

Looking at the Qlogic Site (Marvell Nowadays) and looing for the QL2690, we are at version -1 compared to the latest

QLogic / Marvell Driver Download

README

                   Read1st for Cavium Flash Image Package

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

                   **** ONLY FOR 268x/269x/27xx Series Adapters ****

1. Contents Of Flash Package

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

The files contained in this Flash image package are zipped into a file that

will expand to provide the following versions for the 268x/269x/276x Series Adapters.

*  Flash Image Version 01.01.91

   BK010191.BIN contains:

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

     Bootcode FC

       FC BIOS       v3.62

       FC FCode      v4.11  (Initiator)

       FC FCode      v4.10  (Target)

       FC EFI        v7.00  (Signed)

     FC Firmware   v8.08.231

     MPI Firmware  v1.00.19

     PEP Firmware(Quad-port)        v1.0.27

     PEP Firmware(Single/Dual port) v2.0.12

     PEP SoftROM(Quad port)         v1.0.16

     PEP SoftROM(Single/Dual port)  v2.0.11

     EFlash tool  v1.18

My company recently upgraded our enterprise backup solution so we have a data domain just sitting there spinning with no real purpose. I decided to mount this data domain to an ESXi host purposed for Development.

My question is: Has anyone out there done this before and how was the performace? I would have to imagine that the perfomance is terrible since the data domain must try and dedupe every block read/written. Not sure how that works..

Thanks!

I am working with a Managed Services IT Provider, and we are trying to determine the most efficient method of applying patches and updates to VMWare ESXi servers, and VCenter servers and appliances.  As of now, we manually apply updates to each server, but with hundreds and possibly thousands of servers at our various customers throughout the world, doing so in a timely manner is nearly impossible.

Does VMWare have a solution for managed service providers to allow this to happen in an efficient manner?  What is the best way for us to go about this, for all of our customers, without taking up a tremendous amount of time, and also allowing for this to happen on a routine basis, so our customer's VMWare servers are regularly patched?

Morning,

We run ESXi 5.1 U1 on IBM hosts and I would like to know as to whether it's possible to remove the vSwitch called USB0 which has an attached port group of IMM_Network0

So I suppose I have two questions:

Question1: Is it possible to remove the vSwitch and Port Group?

Question2: If it is possible then is it okay to do it?

Many thanks

So i managed to passthrough the Intel UHD p630 from my e2278g to windows server 2019, by setting svga.present =false and setting pihole value.

Thing is, the screen is blank in dashboard, and the only way to get display is through rdesktop now, which isnt' ideal for 24/7 server.

Is there any other way to keep IGPU and at the same time active display in the dashboard ?

Rdesktop sometimes fail me and IPMI (or in this case dashboard console) has been a huge help so far.

1- My esxi host has been restarted yesterday, Is that possible see the cause root of this problem in vmware logs ? Which Log can help me about this issue ?

2 - Actually I open syslog.log and vmkernel.log but the log is just for today and cannot see previous logs for example yesterday . How can see yesterday logs ?

BR

I have a couple of hosts that I am unable to remediate.  

A few I cannot consolidate due to lock files.  When I go to find the owner of the lock I get ioctl errors.

Secondly, the other VM shoots me this error "An error occurred while consolidating disks: The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child." 

I've run through KBs and gotten nowhere.  Any pointers would be appreciated.

This morning the host had an error loading state.tgz "insufficient resources", I decided to restart using the install usb and selected to upgrade 6.7(current) to the same 6.7, I figured this would fix the corrupt file.

But its been upgrading for over 4 hours, progress bar gets to 100% and starts again from 0.I don't know if is because its upgrading each file or if is looping over and over.

I don't want to interrupt because I'm afraid it would create more problems.

Does anybody have any experience with this situation?

the host has 2 VM's one is a DC and the second a File server, the file server is the biggest with about 600GB of files.

Update command:

# esxcli software profile update -p ESXi-6.7.0-20190402001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[OSError]

[Errno 28] No space left on device

Please refer to the log file for more details.

Swap config:

All swap is on, datastore use datastore1 and more than 100G space.

Please see the /var/log/esxupdata.log below:

2019-04-16T00:41:48Z esxupdate: 2099451: Ramdisk: INFO: Unmounting manual tardisk /tardisks.noauto/esxupdt-2099451^@
2019-04-16T00:41:48Z esxupdate: 2099451: Ramdisk: INFO: Unmounting manual tardisk /tardisks.noauto/weaselin-2099451^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: Traceback (most recent call last):^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 470, in <module>^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:     main()^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 461, in main^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:     ret = CMDTABLE[command](options)^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 213, in ProfileUpdateCmd^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:     nohwwarning=opts.nohwwarning)^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esx
image/Transaction.py", line 375, in UpdateProfileFromDepot^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/tmp/esx-update-2099451/usr/lib/vmware/weasel/util/upgrade_precheck.py", line 2161, in cliUpgradeAction^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/tmp/esx-update-2099451/usr/lib/vmware/weasel/util/upgrade_precheck.py", line 997, in _parseVmwareVersion^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 514,
 in getoutput^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 495,
 in getstatusoutput^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 316,
 in check_output^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 383,
 in run^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 676,
 in __init__^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR:   File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 1228
, in _execute_child^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: OSError: [Errno 28] No space left on device

On a vmware ESXi 6.7.0 Update 1 (Build 10302608):

# esxcli software vib remove --vibname vibpacketname

[LiveInstallationError]

Error in running ['/etc/init.d/vibpacketname', 'stop', 'remove']:

Return code: 1

Output: Service not running

This vib-package isn't working anymore, that's why we want to remove it, but since esxcli tries to stop a non-running process it fails.

(adding -f parameter makes no difference)

Is there any way to remove the package manually?

i can't download vmware esxi server 6.7 and above

Hi,

We have two hosts in a datacentre and want to link them so they can be seen as one network.

The DC staff have connected vmNIC1 between each host via a VLAN across the datacentre. vmNIC0 on each is a connection to the internet.

Could someone help with how we now connect the two hosts so they are part of the same internal network?

Thanks in advance.

Hello,

iv'e got troubles login in to ESXi. It was working normally, but today I'm receiving this kind of output:

What's the issue here?

BR

M.

Hello Everyone ,

Installed Esxi 6.7 and whenever i try to start it, i do get this error message : 

" Shutting down Firmware Services

Page allocation error :  Out of resources

Failed to shutdown the booot services.

Unrecoverable error.

Any help would be apprecited.

Dear all,

in my configuration there is an ESXi 6.7U2 server and I'd like to pass through an NVIDIA NVS310 to my VMs. The GPU card is a PCIe x16 and it is installed on the PCIe x8 slot in my HPe Proliant Microserver Gen10.

The GPU card is recognized by the ESXi and is also visible in the vSphere GUI. When I enable GPU PCIe passthrough it is active/ reboot necessary. In the esx.conf it is visible that passthrough for the GPU card is enabled. The passthrough is only possible when the audio HD also is passed through.

/device/00000:003:00.0/owner = "passthru"

/device/00000:003:00.0/device = "107d"

/device/00000:003:00.0/vendor = "10de"

/device/00000:003:00.1/vendor = "10de"

/device/00000:003:00.1/device = "e08"

/device/00000:003:00.1/owner = "passthru"

After rebooting the server the GPU card is in the disabled state again and the configuration is not visible in the esx.conf anymore.

What can be done to keep the GPU card enabled after reboot?

Hey all,

I've run into a situation where after installing ESXi, I put in my IP information and then reboot the server.  After the host comes back online all settings including the password are gone.  Has anyone run into this before?  I'm looking at hostd.log for help, any other logs that might help?

TIA.