Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Extracting a core dump file from the diagnostic partition following a purple diagnostic screen error (1002769)

Last Updated: 3/10/2017Categories: How toTotal Views: 24190Language:
Chinese (Simplified)JapaneseEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Details

This article provides information on extracting a core dump file from the diagnostic partition following a purple diagnostic screen error.

During a purple diagnostic screen, ESXi/ESX attempts to write a VMkernel core dump to a previously-configured VMKCore (type 0xFC) partition. This file is normally created during start up or while collecting vm-support logs.

In ESXi 5.5 and higher, a VMkernel core dump may be written to a dump file, either in addition or instead of a partition. For such cases, see Generating a VMkernel zdump manually from a dump file in ESXi (2081902).

For more information on related topics, see:

Setup: Configuring an ESXi/ESX host to capture a VMkernel coredump from a purple diagnostic screen (1000328)

Collection: Collecting diagnostic information from an ESX or ESXi host that experiences a purple diagnostic screen (1004128)

Investigation: Interpreting an ESXi/ESX host purple diagnostic screen (1004250)

vSphere 6.5, support bundles can include encrypted information from an ESXi host. For more information, see Data collected when gathering diagnostic information from vSphere products (2147388).

Solution

The command line utility for extracting a VMkernel core dump differs between versions of ESXi/ESX.
vSphere 4.0 and higher

Use command-line tools on the ESXi host to identify the diagnostic partition and copy its contents to a file.

Log in to the ESXi/ESX host:

For ESX classic, log into the service console as root. For more information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807).

For ESXi, log in using Tech Support Mode. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).

For ESXi or ESX, log into your vMA appliance as vi-admin and run this command:

vifpinit host

Note: In vMA, the vifpinit command is replaced with the vifptarget command.

Determine the device identifiers for the diagnostic partition(s) by running one of these commands:

esxcli system coredump partition list

esxcfg-dumppart -t

You see output mentioning a device name and full path to the partition (

mpx.vmhba1:C0:T0:L0:7 /vmfs/devices/disks/mpx.vmhba1:C0:L0:7

A core dump file is between 100 and 300 MB in size. Change to a directory with sufficient space to store the core dump file, such as on a Datastore.

For example:

cd /vmfs/volumes/DatastoreName/

Copy the partition contents to a file by running the esxcfg-dumppart command, specifying the full path from step 2:

esxcfg-dumppart --copy --devname "/vmfs/devices/disks/identifier" --zdumpname /vmfs/volumes/datastore1/filename.1

For example:

esxcfg-dumppart --copy --devname "/vmfs/devices/disks/mpx.vmhba2:C0:T0:L0:2" --zdumpname /vmfs/volumes/datastore1/hostname-date-zdump

Use the Datastore Browser or scp to retrieve the produced zdump file, and share it with VMware Support.

ESXi/ESX 3.x

To generate a core dump file on ESXi/ESX 3.x:

Log into the ESXi/ESX host:

For ESX classic, log into the service console as root. For more information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807).

For ESXi, log in using Tech Support Mode. For more information, see Tech Support Mode for Emergency Support (1003677).

Determine the device identifiers for the core partition(s) by running the command:

esxcfg-dumppart -t

You see one of these outputs:

vmhba1:0:0:7 /vmfs/devices/disks/vmhba1:0:0:7

naa.600508b1001030374543433532300700:7 /vmfs/devices/disks/naa.600508b1001030374543433532300700:7

naa.6d4ae520a23d1500178db21c1837fead:7 /vmfs/devices/disks/naa.6d4ae520a23d1500178db21c1837fead:7
naa.600508b1001030374543433532300700:7 /vmfs/devices/disks/naa.600508b1001030374543433532300700:7

If there is no output in step 2, set one of the volumes as the dump partition using the command:

esxcfg-dumppart -s naa.ID

Activate the partition using the command:

# esxcfg-dumppart -a
Dump Partition activated.

Change to a directory with sufficient space to store the core dump file.

For example:

cd /vmfs/volumes/DatastoreName/

Dump the partition contents to a file by running the command:

vmkdump --devname "identifier"

Where identifier is the value recorded in step 2.

For example:

vmkdump --devname "/vmfs/devices/disks/vmhba1:0:0:0:7"

Additional Information

For translated versions of this article, see:

日本語: エラーが発生して紫色の診断画面が表示された後で、VMKCore 診断パーティションからコア ダンプ ファイルを抽出する (2080855)

简体中文: 在出现紫色诊断屏幕（紫屏）错误后从 VMKCore 诊断分区提取核心转储文件 (2081811)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant