Unfortunately very often VMware problem is too complicated to figure why it is happening. Did you have this issue the very first time you connect to SQL use this cloned Linux?

    If yes, maybe you can try this

1).  Disconnect the first Linux from SQL, and use only the second Linux, see if you have any issue? If no issue, then somehow the SQL does not like cloned VMs to connect to it at the same time. I had such issue twice (Windows AD account can't be setup to manage vcenter; can't setup VDP,  I have two win2008 server, cloned from each other, one was vcenter, one was DC), either bogged me down for 3-5 days.

2). Is it feasible to set up a new Linux from scratch and try this?  I know this is painful, but.................

    I myself this afternoon got into a situation when cluster was migrated from vDS1 to vDS2, but for one host, vDS1 was persistent and can't be deleted, even after I changed the timeout-for-locked-dvport , it kept telling me WinXP1 was in the defunct dPort, finally I used administrator@vsphere.local to login into vSphere client, and deleted vDS1 from host no.1  

Good luck

I am having two issues

When trying to install Vcenter 6 I get the following msg

The user group "NT Service\All SERVICES does not have the "log on as a service" user right. What am I adding into the GPO? I do not see this group in AD.

Also I have a separate SQL server. On the server I am trying to install Vcenter (windows server 2008 R2) I created a DSN and successfully tested the connection to the database. However when I get to the part to find the DSN in the installation it doesnt find anything. I am not sure what I am doing wrong.

The accompanying log indicates the problem I have since upgraded to 6.0 esxi
Can someone help me out what to do about it

2015-06-25T10:00:32.712Z cpu4:32795)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12579 microseconds to 253893 microseconds.

2015-06-25T10:00:34.048Z cpu4:32795)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12586 microseconds to 517602 microseconds.

2015-06-25T10:00:42.790Z cpu5:32796)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12601 microseconds to 1040631 microseconds.

2015-06-25T10:00:43.991Z cpu4:32795)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12606 microseconds to 2285662 microseconds.

2015-06-25T10:00:48.037Z cpu5:32796)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12702 microseconds to 944142 microseconds.

2015-06-25T10:00:48.176Z cpu5:32796)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12707 microseconds to 1944411 microseconds.

2015-06-25T10:00:50.866Z cpu6:32797)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12728 microseconds to 858876 microseconds.

2015-06-25T10:00:50.930Z cpu6:32797)WARNING: ScsiDeviceIO: 1243: Device naa.60014050099f4f1d930ad3999d85f1d5 performance has deteriorated. I/O latency increased from average value of 12728 microseconds to 1800284 microseconds.

2015-06-25T10:02:07.795Z cpu4:32795)WARNING: ScsiDeviceIO: 1243: Device t10.ATA_____WDC_WD1001FALS2D00J7B1________________________WD2DWMATV2213307 performance has deteriorated. I/O latency increased from average value of 11645 microseconds to 35$

2015-06-25T16:34:20.399Z cpu0:87682)WARNING: Heartbeat: 493: One or more PCPUs didn't perform a heartbeat check for 93 seconds.

2015-06-25T16:34:30.404Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue: vmhba37:CH:0 T:1 L:0 : Task mgmt "Abort Task" with itt=0x16531d (refITT=0x16531c) timed out.

2015-06-25T16:34:41.107Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)

2015-06-25T16:34:41.107Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000001 TARGET: iqn.2000-01.com.synology:ds214plus.target-1.8b0573ad70 TPGT: 0 TSIH: 0]

2015-06-25T16:34:41.107Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.2.150:54195 R: 192.168.1.214:3260]

2015-06-25T16:34:41.107Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue: vmhba37:CH:0 T:1 L:0 : Task mgmt "Abort Task" with itt=0x16531f (refITT=0x16531c) timed out.

2015-06-25T16:34:41.107Z cpu0:32810)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:41.866Z cpu0:32786)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:42.831Z cpu0:35481)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:43.862Z cpu0:35471)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:44.124Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba37:CH:0 T:0 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)

2015-06-25T16:34:44.124Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000001 TARGET: iqn.2000-01.com.synology:ds212.esxi TPGT: 0 TSIH: 0]

2015-06-25T16:34:44.124Z cpu5:33251)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.2.150:10632 R: 192.168.2.201:3260]

2015-06-25T16:34:44.838Z cpu0:32836)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:45.830Z cpu0:35481)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:46.872Z cpu0:35859)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:47.866Z cpu0:35479)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:48.837Z cpu0:37018)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:49.866Z cpu0:35471)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:50.842Z cpu0:32785)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.60014050099f4f1d930ad3999d85f1d5" state in doubt; requested fast path state update...

2015-06-25T16:34:51.129Z cpu0:35479)WARNING: NMP: nmp_IssueCommandToDevice:4431: I/O could not be issued to device "naa.60014050099f4f1d930ad3999d85f1d5" due to Not found

2015-06-25T16:34:51.129Z cpu0:35479)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2015-06-25T16:34:51.129Z cpu0:35479)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014050099f4f1d930ad3999d85f1d5" is blocked. Not starting I/O from device.

2015-06-25T16:34:51.826Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d806a1840

2015-06-25T16:34:51.826Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:34:51.826Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:34:52.826Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d806a1840

2015-06-25T16:34:52.826Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:34:52.826Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:35:21.108Z cpu2:32995)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014050099f4f1d930ad3999d85f1d5" is blocked. Not starting I/O from device.

2015-06-25T16:35:21.108Z cpu0:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: Timeout:

2015-06-25T16:35:21.108Z cpu0:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:21.108Z cpu7:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:21.108Z cpu7:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:21.826Z cpu3:87762)WARNING: NMP: nmpDeviceAttemptFailover:566: Retry world restore device "naa.60014050099f4f1d930ad3999d85f1d5" - no more commands to retry

2015-06-25T16:35:21.840Z cpu2:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:21.840Z cpu2:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:24.888Z cpu7:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:24.888Z cpu7:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:27.835Z cpu0:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:27.835Z cpu0:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:30.835Z cpu0:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:30.835Z cpu0:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:33.835Z cpu0:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:33.835Z cpu0:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:36.835Z cpu2:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:36.835Z cpu2:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:39.835Z cpu0:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:39.835Z cpu0:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:42.835Z cpu0:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:42.835Z cpu0:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:45.835Z cpu2:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:45.835Z cpu2:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:48.835Z cpu0:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:48.835Z cpu0:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:51.835Z cpu0:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:51.835Z cpu0:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:54.835Z cpu2:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:54.835Z cpu2:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:35:57.835Z cpu0:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:35:57.835Z cpu0:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:36:00.835Z cpu0:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:36:00.835Z cpu0:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:36:03.835Z cpu2:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:36:03.835Z cpu2:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:36:06.835Z cpu0:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:36:06.835Z cpu0:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:36:09.835Z cpu0:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:36:09.835Z cpu0:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:36:12.835Z cpu0:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:36:12.835Z cpu0:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:36:32.212Z cpu4:34580)WARNING: NMP: nmp_IssueCommandToDevice:4431: I/O could not be issued to device "naa.60014050099f4f1d930ad3999d85f1d5" due to Not found

2015-06-25T16:36:32.212Z cpu4:34580)WARNING: Vol3: 2427: Failed to refresh FS 53785dce-fff67823-650b-0025b302c14c descriptor: No connection

2015-06-25T16:36:32.212Z cpu4:34580)WARNING: NMP: nmp_IssueCommandToDevice:4431: I/O could not be issued to device "naa.60014050099f4f1d930ad3999d85f1d5" due to Not found

2015-06-25T16:36:40.828Z cpu7:32948)WARNING: NMP: nmp_IssueCommandToDevice:4431: I/O could not be issued to device "naa.60014050099f4f1d930ad3999d85f1d5" due to Not found

2015-06-25T16:36:40.828Z cpu7:32948)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2015-06-25T16:36:40.828Z cpu7:32948)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014050099f4f1d930ad3999d85f1d5" is blocked. Not starting I/O from device.

2015-06-25T16:36:41.827Z cpu0:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d80641d40

2015-06-25T16:36:41.827Z cpu0:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:36:41.827Z cpu0:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:36:42.827Z cpu2:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d80641d40

2015-06-25T16:36:42.827Z cpu2:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:36:42.827Z cpu2:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:37:12.827Z cpu7:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d80641d40

2015-06-25T16:37:12.827Z cpu7:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:37:12.827Z cpu7:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:37:20.829Z cpu2:32995)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014050099f4f1d930ad3999d85f1d5" is blocked. Not starting I/O from device.

2015-06-25T16:37:21.828Z cpu3:87910)WARNING: NMP: nmpDeviceAttemptFailover:566: Retry world restore device "naa.60014050099f4f1d930ad3999d85f1d5" - no more commands to retry

2015-06-25T16:37:21.828Z cpu6:33161)WARNING: NMP: nmp_IssueCommandToDevice:4431: I/O could not be issued to device "naa.60014050099f4f1d930ad3999d85f1d5" due to Not found

2015-06-25T16:37:21.828Z cpu6:33161)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2015-06-25T16:37:21.828Z cpu6:33161)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014050099f4f1d930ad3999d85f1d5" is blocked. Not starting I/O from device.

2015-06-25T16:37:22.827Z cpu7:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d80641d40

2015-06-25T16:37:22.827Z cpu7:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:37:22.827Z cpu7:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:37:23.827Z cpu5:87910)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d80641d40

2015-06-25T16:37:23.827Z cpu5:87910)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:37:23.827Z cpu5:87910)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:37:53.827Z cpu4:87910)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - issuing command 0x439d80641d40

2015-06-25T16:37:53.827Z cpu4:87910)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014050099f4f1d930ad3999d85f1d5" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:37:53.827Z cpu4:87910)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014050099f4f1d930ad3999d85f1d5": awaiting fast path state update...

2015-06-25T16:38:00.831Z cpu2:32995)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014050099f4f1d930ad3999d85f1d5" is blocked. Not starting I/O from device.

2015-06-25T16:38:00.831Z cpu7:32948)WARNING: NMP: nmp_IssueCommandToDevice:4431: I/O could not be issued to device "naa.60014057364b892d53e6d3961d8141d4" due to Not found

2015-06-25T16:38:00.831Z cpu7:32948)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.60014057364b892d53e6d3961d8141d4": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2015-06-25T16:38:00.831Z cpu7:32948)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014057364b892d53e6d3961d8141d4" is blocked. Not starting I/O from device.

2015-06-25T16:38:01.827Z cpu0:87910)WARNING: NMP: nmpDeviceAttemptFailover:566: Retry world restore device "naa.60014050099f4f1d930ad3999d85f1d5" - no more commands to retry

2015-06-25T16:38:01.827Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - issuing command 0x439d80641d40

2015-06-25T16:38:01.827Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:38:01.827Z cpu3:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014057364b892d53e6d3961d8141d4": awaiting fast path state update...

2015-06-25T16:38:02.827Z cpu1:87910)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - issuing command 0x439d80641d40

2015-06-25T16:38:02.827Z cpu1:87910)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:38:02.827Z cpu1:87910)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014057364b892d53e6d3961d8141d4": awaiting fast path state update...

2015-06-25T16:38:32.828Z cpu4:87910)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - issuing command 0x439d80641d40

2015-06-25T16:38:32.828Z cpu4:87910)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:38:32.828Z cpu4:87910)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014057364b892d53e6d3961d8141d4": awaiting fast path state update...

2015-06-25T16:38:40.833Z cpu0:32995)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014057364b892d53e6d3961d8141d4" is blocked. Not starting I/O from device.

2015-06-25T16:38:41.828Z cpu6:33162)WARNING: NMP: nmpDeviceAttemptFailover:566: Retry world restore device "naa.60014057364b892d53e6d3961d8141d4" - no more commands to retry

2015-06-25T16:38:41.828Z cpu1:33161)WARNING: NMP: nmp_IssueCommandToDevice:4431: I/O could not be issued to device "naa.60014057364b892d53e6d3961d8141d4" due to Not found

2015-06-25T16:38:41.828Z cpu1:33161)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.60014057364b892d53e6d3961d8141d4": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2015-06-25T16:38:41.828Z cpu1:33161)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014057364b892d53e6d3961d8141d4" is blocked. Not starting I/O from device.

2015-06-25T16:38:42.828Z cpu7:87910)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - issuing command 0x439d80641d40

2015-06-25T16:38:42.828Z cpu7:87910)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:38:42.828Z cpu7:87910)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014057364b892d53e6d3961d8141d4": awaiting fast path state update...

2015-06-25T16:38:43.828Z cpu5:33162)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - issuing command 0x439d80641d40

2015-06-25T16:38:43.828Z cpu5:33162)WARNING: NMP: nmpDeviceAttemptFailover:678: Retry world failover device "naa.60014057364b892d53e6d3961d8141d4" - failed to issue command due to Not found (APD), try again...

2015-06-25T16:38:43.828Z cpu5:33162)WARNING: NMP: nmpDeviceAttemptFailover:728: Logical device "naa.60014057364b892d53e6d3961d8141d4": awaiting fast path state update...

2015-06-25T16:39:04.127Z cpu7:32959)WARNING: NMP: nmp_DeviceStartLoop:725: NMP Device "naa.60014057364b892d53e6d3961d8141d4" is blocked. Not starting I/O from device.

2015-06-25T16:39:04.828Z cpu0:87910)WARNING: NMP: nmpDeviceAttemptFailover:566: Retry world restore device "naa.60014057364b892d53e6d3961d8141d4" - no more commands to retry

2015-06-25T16:40:42.197Z cpu5:87696)WARNING: Vol3: 2427: Failed to refresh FS 53785dce-fff67823-650b-0025b302c14c descriptor: No connection

2015-06-25T16:41:12.838Z cpu4:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:41:12.838Z cpu4:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:46:12.840Z cpu4:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:46:12.840Z cpu4:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:51:12.843Z cpu0:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:51:12.843Z cpu0:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T16:56:12.845Z cpu0:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T16:56:12.845Z cpu0:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T17:01:12.848Z cpu1:32810)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T17:01:12.848Z cpu1:32810)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T17:06:12.850Z cpu3:32811)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T17:06:12.850Z cpu3:32811)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

2015-06-25T17:11:12.853Z cpu0:32809)WARNING: HBX: 3278: 'DS214plus': HB at offset 3969024 - Reclaiming timed out HB failed: No connection:

2015-06-25T17:11:12.853Z cpu0:32809)WARNING: [HB state abcdef02 offset 3969024 gen 143 stampUS 77765009680 uuid 558afd87-d3f58c7e-c8d6-6805ca0fedec jrnl <FB 2405421> drv 14.61 lockImpl 3]

0:00:00:06.362 cpu0:32768)WARNING: VMKAcpi: 754: No IPMI PNP id found

2015-06-25T17:16:11.612Z cpu0:33128)WARNING: LinuxSignal: 541: ignored unexpected signal flags 0x2 (sig 17)

I've been attempted to update the STS on a fresh installation of the VCSA 6 to replace it with custom enterprise signed certs per http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.security.doc/GUID-62981EA9-FEDD-4803-9CB6-29552FE703B1.html?resultof=%2522%2573%2574%2573%2522%2520%2522%2573%2574%2522%2520.

Following the same procedures I did for 5.1, the JKS uploads fine but whenever I reboot the VCSA after uploading the JKS the majority of my vCenter services come back in an unknown state. I'm guessing my procedures for creating the JKS may not be valid anymore. Is there documentation anywhere for a preferred method of generating a JKS to replace the STS cert? I've been generating a PFX file using an enterprise signed cert with OpenSSL and then creating a JKS using my local keytool (Java 8_45) and then adding my root/intermediate cert to the JKS.

Thanks!

Everybody is good:

Hang up my esxi server in the iscsi storage, when iscsi storage is damaged, I can't unload to uninstall the iscsi storage, have been out of the I/o control tips, please indicate how to uninstall the iscsi storage, virtual machine if I didn't run on the storage, but the system prompt esxi host also were associated with iscsi, I always did not find reasons to.

So I just tested in the lab...the storage groups only replicate AppStacks, not writable volumes. Well that's a bummer. So that drawing I made is just completely wrong then.

Hi

I would like to check how I can create a GRE tunnel interface that are able to deencapsulate the GRE packet generated from EXSi 6.I tried to use the same method indicated in this link Decapsulation ERSPAN Traffic With Open Source Tools | Brezular's Blog ,but it failed.

Below diagram is the sample packet that I captured in the linux host without gre interface. When gre interface is presented, no packet is found on the gre interface. Strange! please help!

Hi all,

My server IBM x3650 M4 with 7 SAS 600GB, 64GB RAM

- I setup 2 HDD with raid 1-datastore1 (ESXi host, virtual machine OS as: Windows server 2008( SQL), Centos) --> Raid Stripe size for best performance ?

- I setup 4 HDD with raid 10-datastore2 for database SQL virtual disk( about 80GB ) --> Raid Stripe size for best performance ?

Thansk all.

and it appears VSA was discontinued as of April 1, 2014, anyway

VMware vSphere Storage Appliance (VSA) for Shared Storage | United States

The default amount of time before a rebuild takes place is still 60 minutes. On my lab setup I would occasionally forget to bring a host out of maintenance, or leave it off too long doing working on hardware.

The setting to change is "VSAN.ClomRepairDelay"

And to avoid restarting the host after modification you can manually restart the "clomd" daemon with:

%$ /etc/init.d/clomd restart

Cheers

Hello VMware,

When I open Fusion 7 and check for updates, the progress window appears at the bottom left corner of the screen.  If an update is available, the release notes appear in the bottom left corner of the screen.  No matter how many times I move the window, the next time I open Fusion and check for updates it goes back to the bottom left corner of the screen.  Since I am using a 30 inch, 2560x1600 monitor, this bottom left positioning looks absolutely awkward and ridiculous.  I don't want to keep looking down at the bottom left corner of the screen to read things.  Please fix Fusion so the software update progress and release notes appear in the center of the screen.

My problem is:"A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. the shutdown state can be reached by incorectly configuring the virtual machine, a bug in the guest operating system, or a problem in vmware workstation.........."

I try to change my hiren's boot cd from 10.0 to 15.0. It's done.

Hope this try can help some one solve their's problem like this!

Thanks, maybe I'll try to install a new VM from scratch.

Thanks.  I got a similar response from my Dell support engineer.  While he didn't say there was anything wrong per se with the Dell ISOs, he did say a lot of what Hogan writes about, and that in the end, the H730 controller firmware is still from Dell; VMware just certifies it.  So, Dell would still support us, and even if the Dell support rep (if we were to call in with an issue) were to say "You should upgrade to the latest driver to solve your problem", it wouldn't be the first time that's happened to us.  Moreover, in this case, we have a specific reason we couldn't upgrade to the latest.

My Dell guy did say it's an ongoing issue, and they're working on it.  From the end of Hogan's article, it also looks like they're at least trying

yes it is possible to identify the Zombie disk . if the vmdk is associated with VM or not.

Use a free tool called Rvtool from roboware .. Its a easy and simple tool.. Run that and in the last column you a get a health tab which displays the list of Zombie disk that are present in data store but not associated with VM.

Hi,

Getting this error:

https://vrm.vmware.domain.local:5480/service/hms/cgi/health.py

gives green

LookupService Address: vcenter.vmware.domain.local (and it's pingable from ssh @ vrm.vmware.domain.loca, DNS is set in networkingl)
SSO Admin: Administrator@vmware.domain.local (Such SSO domain exists in vcenter and I can login in vcenter web UI with vmware.domain.local\Administrator)

VRM Host: vrm.vmware.domain.local (also pinged from multiple hosts)

VRM Site Name: VRM NPB
vcenter Server Address: vcenter.vmware.domain.local

vcenter server port: 80

If I click Start VRM Service, it gets into

VRM service is started and quickly reverts to

VRM service is stopped

Installation of vcenter and vrm is done from ISO appliances

Inside /opt/vmware/hms/logs/hms-configtool.log I see a lot of messages like ERROR: relation "users_privileges" does not exist

inside vcenter web client services com.vmware.vcHms.label (vcenter.vmware.domain.local) - Unknown - I see that Failed to request health status from https://vrm.vmware.domain.local:5480/service/hms/cgi/health.py

What can be done?

I even debugged the script the VRM UI sends

http GET https://vrm.vmware.domain.local:5480/service/hms/cgi/hms.py?cmd=checklscert&ls=vcenter.vmware.domain.local&lsthumbpr…

{

   "result":{

      "vc":{

         "uuid":"56d6e005-2229-4bc6-99e9-7969c8883efd",

         "notBefore":"26 Jun 2015 12:56:47 GMT",

         "notAfter":"20 Jun 2025 12:56:47 GMT",

         "valid":"Certificate validation error",

         "thumbprint":"8D:E6:70:13:D2:4A:2D:D6:D7:27:21:C3:FA:36:48:56:F3:EA:91:EA",

         "subject":{

            "C":"US",

            "CN":"vcenter.vmware.domain.local",

            "L":"Unknown",

            "O":"Unknown",

            "ST":"Unknown",

            "OU":"Unknown"

         },

         "issuer":{

            "C":"US",

            "CN":"CA",

            "DC":"vmware",

            "L":"Unknown",

            "O":"vcenter.vmware.domain.local",

            "ST":"Unknown",

            "OU":"Unknown"

         }

      },

      "result":"ok",

      "ls":{

         "notBefore":"26 Jun 2015 12:56:47 GMT",

         "notAfter":"20 Jun 2025 12:56:47 GMT",

         "valid":"true",

         "thumbprint":"8D:E6:70:13:D2:4A:2D:D6:D7:27:21:C3:FA:36:48:56:F3:EA:91:EA",

         "subject":{

            "C":"US",

            "CN":"vcenter.vmware.domain.local",

            "L":"Unknown",

            "O":"Unknown",

            "ST":"Unknown",

            "OU":"Unknown"

         },

         "issuer":{

            "C":"US",

            "CN":"CA",

            "DC":"vmware",

            "L":"Unknown",

            "O":"vcenter.vmware.domain.local",

            "ST":"Unknown",

            "OU":"Unknown"

         }

      }

   },

   "error":null

}

If I'm trying to unregister the appliance I get this error: The appliance has to be configured correctly for unregister to work.

So it's a dead end I love AWS so much better ... this is crazy

thanks

Pass the VCIX-NV with only 300.

PowerCLI

vSphere Documentation Center

can someone please help with this error. I am in vrealize application services and trying to deploy a out of the box app but keep runnning into this error

I got the same result.... Cross-linked files on drive C:  but no problems on drive E:

This was found just doing the "lightweight" chkdsk /f

Due to that I'm not going to bother doing a 6-hour long  /f /r on the copied VM.

Onward to Windows 7 Extra-disk cold cloning, and if that too fails, then I'm going to have to do the traditional route: build a new server, migrate via robocopy.

==============================

Checking file system on E:

The type of the file system is NTFS.

Volume label is Vol1.

A disk check has been scheduled.

Windows will now check the disk.                    

CHKDSK is verifying files (stage 1 of 3)...

  1837056 file records processed.  

File verification completed.

  290 large file records processed.

0 bad file records processed.

0 EA records processed.

0 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...

  2159740 index entries processed.

Index verification completed.

  0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...

  1837056 file SDs/SIDs processed.

Cleaning up 1 unused index entries from index $SII of file 0x9.

Cleaning up 1 unused index entries from index $SDH of file 0x9.

Cleaning up 1 unused security descriptors.

Security descriptor verification completed.

  161343 data files processed.

CHKDSK is verifying Usn Journal...

  121504 USN bytes processed.

Usn Journal verification completed.

Windows has checked the file system and found no problems.

877261823 KB total disk space.

672696176 KB in 1252608 files.

    493516 KB in 161344 indexes.

        0 KB in bad sectors.

  1933363 KB in use by the system.

    65536 KB occupied by the log file.

202138768 KB available on disk.

      4096 bytes in each allocation unit.

219315455 total allocation units on disk.

  50534692 allocation units available on disk.

Internal Info:

00 08 1c 00 4c 93 15 00 94 1c 1f 00 00 00 00 00  ....L...........

e6 18 01 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

================================

Checking file system on C:

The type of the file system is NTFS.

A disk check has been scheduled.

Windows will now check the disk.                      

CHKDSK is verifying files (stage 1 of 3)...

Attribute record of type 0x80 and instance tag 0x4 is cross linked starting at 0x3c58 for possibly 0x1 clusters.

Some clusters occupied by attribute of type 0x80 and instance tag 0x4 in file 0x78bc is already in use.

Deleting corrupt attribute record (128, "") from file record segment 30908.

  199936 file records processed. 

File verification completed.

  892 large file records processed.

0 bad file records processed.

0 EA records processed.

104 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...

  262100 index entries processed.

Index verification completed.

  0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 3)...

  199936 file SDs/SIDs processed.  

Cleaning up 21 unused index entries from index $SII of file 0x9.

Cleaning up 21 unused index entries from index $SDH of file 0x9.

Cleaning up 21 unused security descriptors.

Security descriptor verification completed.

Inserting data attribute into file 30908.

  31084 data files processed.

CHKDSK is verifying Usn Journal...

  1171544 USN bytes processed.

Usn Journal verification completed.

CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.

  70936575 KB total disk space.

  58966664 KB in 152713 files.

    94372 KB in 31084 indexes.

        0 KB in bad sectors.

    271215 KB in use by the system.

    65536 KB occupied by the log file.

  11604324 KB available on disk.

      4096 bytes in each allocation unit.

  17734143 total allocation units on disk.

  2901081 allocation units available on disk.

Internal Info:

00 0d 03 00 02 ce 02 00 ed 1d 05 00 00 00 00 00  ................

d9 00 00 00 68 00 00 00 00 00 00 00 00 00 00 00  ....h...........

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.

Please wait while your computer restarts.