Purple Screen ESXi 6.0.0

[SupportScriba]

Hello all,

I have this purple screen on my ESXi.

Can you tell me more of this ? because i can t find information...

Thanks for you r answer,

Best regards.

[bluefirestorm · Accepted solution]

Looks like you are on build 3620759

ESXi 6.0 patch 3 build 4192238 looks to have resolve a similar PSOD when LSI SAS controllers.

https://kb.vmware.com/kb/2145664

ESXi 6.0 hosts that use mpt2sas or mptsas drivers might fail with a purple diagnostic screen containing entries similar to the following:

@BlueScreen: #PF Exception 14 in world 33513:tq:tracing IP 0xnnnnnnnn addr 0xnnnnnnnn

0xnnnnnnnn:[0xnnnnnnnn]Panic_Exception@vmkernel#nover+0x258

0xnnnnnnnn:[0xnnnnnnnn]IDTReturnPrepare@vmkernel#nover+0x174

0xnnnnnnnn:[0xnnnnnnnn]gate_entry_@vmkernel#nover+0x0

0xnnnnnnnn:[0xnnnnnnnn]VmkDrv_WakeupAllWaiters@vmkernel#nover+0xc6

0xnnnnnnnn:[0xnnnnnnnn]VmkTimerQueueWorldFunc@vmkernel#nover+0x21f

0xnnnnnnnn:[0xnnnnnnnn]CpuSched_StartWorld@vmkernel#nover+0x

[naresh_mca82]

Hello,

PSOD ( Purple Screen of Death) When you get starting login to ESXi host make sure that the below Information's.

Are seems to Good in hand while trouble shooting then raise a Hardware call for failures.

Below issues were addressed as part of this latest HPSA driver version

• Fixed a memory leak associated with device rescans resulting in out of memory conditions and a potential PSOD.
• Fixed a null pointer dereference in error handling code that can cause a PSOD in rare cases when device inquiries fail.
• Restore LUN numbering policy to start with 1 instead of 0, avoiding potential issues with Raw Device Maps.
• Enable 64bit DMA mapping instead of default 32bit mapping.
• Improve null pointer checks in device rescanning code, avoiding a potential PSOD.
• Restore maximum outstanding command count, removing artificial limitation that could impact performance.
• Restore support for legacy HP Smart Array P700m controller.

To identify the current version of HPSA driver installed with your ESXi 5.5 host, execute the below command:

~ # vmkload_mod -s hpsa | grep Version
Version: Version 5.5.0.58-1OEM, Build: 1331820, Interface: 9.2 Built on: Dec16 2013

Driver Version: HP HPSA Driver (v 5.5.0.58-1OEM)” meant the affected software driver was used.

How to Install the latest HPSA driver for ESXi 5.5:

Download the HPSA driver vib file (scsi-hpsa-5.5.0.60-1OEM.550.0.0.1331820.x86_64.vib) for vSphere 5.5 and upload it in your ESXi host datastore

1.Place your ESXi host into Maintenance Host

2.Install the hpsa driver VIB using the below following command:

esxcli software vib install -v /tmp/scsi-hpsa-5.5.0.60-1OEM.550.0.0.1331820.x86_64.vib

3.Reboot the ESXi host for the changes to take effect

4.Verify the HPSA driver version after the installation using the below command:

~ # vmkload_mod -s hpsa | grep Version
Version: Version 5.5.0.60-1OEM, Build: 1331820, Interface: 9.2 Built on: May 15 2014

5.Exit your ESXi host from the Maintenance mode

Thats it!!. No more PSOD on your ESXi host. I hope this is informative for you. Thanks for Reading!!! Be Social and share it in social media, if you feel worth sharing it.

[SupportScriba]

Thanks

It's ok for me !

[minhdt12291]

Hi all,

I had issue, too.

If I upgrade to VMWare ESXI 6.5. Can I resolve issue?