Skip to main content

How to solve VMware View Virutal Machine deployment fails with a purple diagnostic screen and the error: PF Exception 14 - GFCPutSectionHeader (2076931)?

By
When using VMware ESXi 5.5 to deploy VMware View machine with SE spare disk:
  • Host fails with a purple diagnostic screen as below and
  • You see this backtrace in the purple diagnostic screen and in the system logs as below

What will you do then?



Logs:
2015-01-06T15:09:07.842Z cpu3:32848)@BlueScreen: #PF Exception 14 in world 32848:CmdCompl-3 IP 0x41802f0a5db1 addr 0x6c
PTEs:0x88cf47e023;0x88cf47f023;0x8077b72023;0x0;
2015-01-06T15:09:07.842Z cpu3:32848)Code start: 0x41802e400000 VMK uptime: 137:10:13:26.272
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141da00:[0x41802f0a5db1]GFCPutSectionHeader@esx#nover+0x1 stack: 0x41240141da80
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141daa0:[0x41802f0b7332]SEResource_UnlockResources@esx#nover+0x13a stack: 0x41240141dae0
2015-01-06T15:09:07.843Z cpu3:32848)0x41240141dac0:[0x41802f0bb60d]SETxnGTEFaultCleanupCompletionArgs@esx#nover+0x65 stack: 0x0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db00:[0x41802f0bb65e]SETxnGTEFaultCompletion@esx#nover+0x4e stack: 0x410a7bd54cc0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db40:[0x41802f0ace4f]SESparseCheckAndReleaseLocks@esx#nover+0x10b stack: 0x41240141dbc0
2015-01-06T15:09:07.844Z cpu3:32848)0x41240141db70:[0x41802f0afa6f]SESparseAsyncDataDone@esx#nover+0x43 stack: 0x4132c1e7d2c0
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dba0:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x410c3f360fb0
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dbd0:[0x41802e6ce2c2]FS_IOAccessDone@vmkernel#nover+0x56 stack: 0x412ec00e8b18
2015-01-06T15:09:07.845Z cpu3:32848)0x41240141dc00:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x412ec1b31480
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc30:[0x41802e42d48f]AsyncCompleteOneIO@vmkernel#nover+0x16b stack: 0x412ec23e6080
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc60:[0x41802e42d29f]AsyncPopCallbackFrameInt@vmkernel#nover+0xe7 stack: 0x41240141dc90
2015-01-06T15:09:07.846Z cpu3:32848)0x41240141dc90:[0x41802e6fe241]FDSAsyncTokenIODone@vmkernel#nover+0xdd stack: 0x1022
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141dd90:[0x41802e7214c3]SCSICompleteDeviceCommand@vmkernel#nover+0x46f stack: 0x410a7bd32488
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141ddc0:[0x41802ed0bebe]nmp_CompleteCommandForDevice@com.vmware.vmkapi#v2_2_0_0+0x82 stack:
2015-01-06T15:09:07.847Z cpu3:32848)0x41240141ded0:[0x41802ed0c18e]nmp_CompleteCommandForPath@com.vmware.vmkapi#v2_2_0_0+0x12a stack: 0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141df60:[0x41802e742475]SCSICompletePathCommand@vmkernel#nover+0x2a5 stack: 0x41240141dfa0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141dfd0:[0x41802e7552c0]SCSICommandCompletionWorld@vmkernel#nover+0x19c stack: 0x0
2015-01-06T15:09:07.848Z cpu3:32848)0x41240141dff0:[0x41802e653532]CpuSched_StartWorld@vmkernel#nover+0xfa stack: 0x0
2015-01-06T15:09:07.853Z cpu3:32848)base fs=0x0 gs=0x418040c00000 Kgs=0x0

No need to worry so much about that.

VMware already mentioned that is well known issue for all versions of VMware ESXi 5.5 prior to Patch 02.

By updating to Patch 02 will resolve the issue.

Cheer!

For more details, please read articles from VMware below,

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2076931

Have a good day.
(Be knowledgeable, pass it on then)
Labels:

Comments

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Link Aggregating with Synology NAS and Cisco Switch

By
I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f...
35 comments
Read more