Dear Expert,

Which VMware product is for Hot Standby for double servers?

thx!

Liu Wei

i have a dell server dell r730xd, i want to manage raid adapter h730p , how can i make it ?

yes, i can manage raid adapter through idrac,

thank you

Hi all,

I copied a VM from NetApp based datastore to local datastore (via Datastore browser in the vSphere web client). Source & destination ESXi Hosts have the same version 6.5.0.

ESX source system-> version 6.5.0 Build 4564106

ESX destination system-> version 6.5.0 Build 6765664

After the files have been transferred I registered the VM on the destination ESXi Host via VMWare Webclient and tried to start the VM some errors (several records with the same error message) occured:

"File system specific implementation of LookupAndOpen{file} failed
Cannot open the disk .... or one of the snapshot disks it depends on

Module "Disk" power on failed"

I also detected that my vDisks (originally "thin provisioned" ) apear now as "thick provisioned" on the destination ESXi host.

The VM doesn't start.

Can I fix this problem? Do you have some ideas?

Hello,

I just wanted to ask if there is by now a method to use a software-raid with the ESXI-Hypervisor. I am using the inbuild RAID-Funktion of the Fujitsu D3446-Mainboard with Intel C236 chipset and as far as I can say from my investigation it seems that it is not a hardware but a software RAID.

I already found some topics about this but wanted to make sure that:

1. Intel C236 chipset is actually using a software RAID and there is not any other problem with it (The current symptom is that whether I created a RAID 1 in the BIOS the ESXI 6.5 Installer shows two independend disks)
2. There is still no workaround to use a software raid, for example via adding the driver to the esxi-installer like I can do for windows based OS.

Thanks in advance,

Niklas

Hi,

I have a 6.5u1 standalone host with 10GB of RAM, and one VM on it. As there is a passthrough device assaigned I would like to reservate as much as possible RAM to this VM, but as soon I increase the reservation above 4048MB  following error appeares when trying to start the VM:

The available memory resources in the parent resource poolare insufficient for the operation

I tested this also with 8GB RAM, there I was only able to configure 3GB reservation.

So why is it not possible to assign more reservated ram to a VM?

Thanks,

Crispyduck

I'm running a student version of ESXi 6.5 u1 that is essentially the enterprise plus version, but limited to only 1 vhost and no license for vCenter.

I'm having issues with a virtual appliance that has 4 virtual NIC's installed. The vHost is connected to my physical switch with a trunk port that allows all configured VLAN's to traverse the trunk. In the virtual appliance, two NIC's are connected to the same VLAN and the last 2 are connected to different VLAN's for a total of 3 VLANS. When I look a the vswitch view and each VLAN, I see 2 connections in each of the 3 VLAN's and they are the same MAC address of the first two NIC's in the appliance, the last two do not show up at all.  If I delete 2 NIC's, the two remaining show in each assigned VLAN as expected. If I add 1 NIC for a total of 3, I get the same behavior. This is not just showing incorrectly, the virtual appliance is also not working as expected in each VLAN.  Thought this might just be the appliance having issues so tried an Ubuntu server VM that I created that already had 2 NIC's. When I added the third NIC, it exhibited the same issues.

Troubleshooting:

I have rebooted the appliance and the vhost several times, deleted and re-added the NIC's in various stages to isolate when the issue shows up, tried to upgrade to ESXi 6.7, but my vhost is not compatible with 6.7, reinstalled 6.5 with no difference in behavior and attempted to downgrade. Since a downgrade requires a complete reinstall, I've decided to ask here for options. Any suggestions that require a vCenter server is not an option since my license does not include that. That also means that I am not able to use the software update services unless there's a way to install an update manually (or it doesn't require vCenter Server), but then I'd also have to be able to download the update package(s).

This appears to be a bug in 6.5, but am hoping it's not and there's a fix for it. Any suggestions?

Update:

I've marked the answer from A.P. as the correct answer, but it's really only partially correct. Since my VM wasn't working, and I wasn't seeing the correct output, I assumed I was seeing the same issue. In reality, there were two issues, this one and a configuration issue with the VM itself.

For those that may come by this later, the VM is running GNS3 and I wasn't able to pass traffic on each NIC when configured on separate vlans. I was assigning them correctly, but since I wasn't seeing the correct assignments when I viewed the vSwitch, I assumed that was the issue. Once I enabled promiscuous mode on each NIC on the GNS3 VM, it started working as expected.

Hi,

     We are currently running vSphere Hypervisor 6.0.0 (free version)  and wish to go with the paid version to integrate vSphere server.  My question might be silly, do I just need to change the license key in the licenced Features on my hosts, or do I need to do a complete re-install of vsphere  esxi on my hosts?

Thanks.

Greetings,

     This is a lab environment. ESXi 6.7 version is running on Dell R710 SFF Server. We created a storage on another Dell R710 LFF with a capacity of 8 TB one volume and 5 TB one volume as virtual disks. Using 5 TB virtual disk and FreeNAS we created an iSCSI Target on top of it. Now we are trying to setup the iSCSI storage and datastore as one Dell R710 SFF is acting as initiator and other Dell R710 LFF acting as a target.

Initiator (10.39.130.35) Dell R710 SFF specifications:

vCPUs 12 with 96 GB RAM

VMKernal2 with MTU 9000 and vDS with MTU of 9000

Target (10.39.130.222 iqn.2005-10.org.freenas.ctl:all-esxi) Dell R710 LFF specifications:

vCPUs 8 and 128 GB RAM

FreeNAS with em1 and MTU of 9000

Issue: The iSCSI Target is getting timeout and Disk is getting ONLINE and OFFLINE intermittently

Below are the logs of esxi vmkernal.log

 

 

[root@esxi1:~] cat /var/log/vmkernel.log

2019-05-07T17:48:32.912Z cpu4:2247842)Vol3: 1255: Could not open device '5cc6f8b0-8e513860-6903-0026b93f7b73' for volume open: Failure

2019-05-07T17:48:32.912Z cpu4:2247842)LVM: 5919: Could not open device naa.6589cfc000000f7547481ec53d72549e:1, vol [5cc6f8b0-8e513860-6903-0026b93f7b73, 5cc6f8b0-8e513860-6903-0026b93f7b73, 1]: LVM device unreachable

2019-05-07T17:48:32.912Z cpu4:2247842)Vol3: 1255: Could not open device '5cc6f8b0-8e513860-6903-0026b93f7b73' for volume open: Failure

2019-05-07T17:48:32.912Z cpu4:2247842)LVM: 5919: Could not open device naa.6589cfc000000f7547481ec53d72549e:1, vol [5cc6f8b0-8e513860-6903-0026b93f7b73, 5cc6f8b0-8e513860-6903-0026b93f7b73, 1]: LVM device unreachable

2019-05-07T17:48:32.912Z cpu4:2247842)FSS: 6092: No FS driver claimed device '5cc6f8b0-8e513860-6903-0026b93f7b73': No filesystem on the device

2019-05-07T17:48:32.918Z cpu0:2098497)PLOG: PLOGOpenDevice:4346: Disk handle open failure for device naa.6782bcb05bcabf0021f7e31c06bb079d:2, status:Busy

2019-05-07T17:48:32.919Z cpu0:2098497)PLOG: PLOGInitAndAnnounceMD:7958: Successfully announced VSAN MD (naa.6782bcb05bcabf0021f7e31c06bb079d:2) with UUID: 5259f2c5-80bd-17b5-20c5-77b4fd68b317. kt 1, en 0, enC 0.

2019-05-07T17:48:32.922Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:32.922Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:32.922Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16b2 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:32.933Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:32.933Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:32.933Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16b4 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:32.942Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:32.942Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:32.942Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16b6 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:32.954Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:32.954Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:32.954Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16b8 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:32.965Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:32.965Z cpu9:2247840)WARNING: NFS: 1227: Invalid volume UUID mpx.vmhba1:C0:T0:L0

2019-05-07T17:48:32.965Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:32.965Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16ba from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:32.976Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:32.977Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:32.977Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16bc from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:32.995Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:32.995Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:32.995Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16be from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:33.005Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:33.005Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:33.005Z cpu4:2097199)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16c5 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:33.017Z cpu4:2097199)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:33.017Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:33.017Z cpu9:2097204)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16c7 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:33.026Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:33.026Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:33.026Z cpu9:2097204)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16c9 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:33.038Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:33.038Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:33.038Z cpu9:2097204)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16cb from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:33.047Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:33.047Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x9e (0x459b98d365c0, 0) to dev "mpx.vmhba1:C0:T0:L0" on path "vmhba1:C0:T0:L0" Failed: H:0x7 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:48:33.047Z cpu9:2097204)ScsiDeviceIO: 3082: Cmd(0x459b98d365c0) 0x9e, CmdSN 0x16cd from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x7 D:0x0 P:0x0 Invalid sense data: 0x73 0x65 0x20.

2019-05-07T17:48:33.055Z cpu9:2097204)NMP: nmp_ThrottleLogForDevice:3727: last error status from device mpx.vmhba1:C0:T0:L0 repeated 2 times

2019-05-07T17:48:33.059Z cpu4:2247840)FSS: 6092: No FS driver claimed device 'mpx.vmhba1:C0:T0:L0': No filesystem on the device

2019-05-07T17:48:34.438Z cpu1:2097196)ScsiDeviceIO: 3068: Cmd(0x459b98d97dc0) 0x1a, CmdSN 0x1716 from world 0 to dev "t10.SanDisk00Ultra_USB_3.00000004C530000261203102470" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2019-05-07T17:48:34.543Z cpu4:2100460 opID=46e20a1f)VC: 4616: Device rescan time 10157 msec (total number of devices 6)

2019-05-07T17:48:34.543Z cpu4:2100460 opID=46e20a1f)VC: 4619: Filesystem probe time 1628 msec (devices probed 5 of 6)

2019-05-07T17:48:34.543Z cpu4:2100460 opID=46e20a1f)VC: 4621: Refresh open volume time 4 msec

2019-05-07T17:49:04.106Z cpu13:2097835)NMP: nmp_ResetDeviceLogThrottling:3569: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x2 0x3a 0x1 from dev "mpx.vmhba1:C0:T0:L0" occurred 1 times(of 1 commands)

2019-05-07T17:49:19.107Z cpu2:2098823)SunRPC: 1099: Destroying world 0x224cfe

2019-05-07T17:49:34.107Z cpu7:2097507)ScsiVmas: 804: Inquiry for VPD page 00 to device naa.6589cfc000000f7547481ec53d72549e failed with error No connection

2019-05-07T17:49:34.963Z cpu6:2097201)ScsiDeviceIO: 3068: Cmd(0x459b8aafa700) 0x1a, CmdSN 0x1722 from world 0 to dev "mpx.vmhba1:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2019-05-07T17:50:22.108Z cpu1:2098823)SunRPC: 1099: Destroying world 0x224dfd

2019-05-07T17:51:17.038Z cpu17:2097726)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1197: vmhba65:CH:0 T:1 CN:0: Connection tx notifying failure: Network Send Error. State=Online

2019-05-07T17:51:17.038Z cpu17:2097726)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1198: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:51:17.038Z cpu17:2097726)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1199: Conn [CID: 0 L: 10.39.130.35:10848 R: 10.39.130.222:3260]

2019-05-07T17:51:17.038Z cpu16:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:699: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)

2019-05-07T17:51:17.038Z cpu16:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:700: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:51:17.038Z cpu16:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:701: Conn [CID: 0 L: 10.39.130.35:10848 R: 10.39.130.222:3260]

2019-05-07T17:51:17.041Z cpu18:2097547)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue:633: vmhba65:CH:0 T:1 L:70 : Task mgmt "Abort Task" with itt=0xa47 (refITT=0xa3e) timed out.

2019-05-07T17:51:17.041Z cpu18:2097547)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x89 (0x459a40c1d280, 2097185) to dev "naa.6589cfc0000002975052862c22403cca" on path "vmhba65:C0:T1:L70" Failed: H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:51:17.041Z cpu18:2097547)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6589cfc0000002975052862c22403cca" state in doubt; requested fast path state update...

2019-05-07T17:51:17.041Z cpu16:2097705)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x28 (0x45a37d996b40, 2098280) to dev "naa.6589cfc0000002975052862c22403cca" on path "vmhba65:C0:T1:L70" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:51:17.041Z cpu18:2097547)ScsiDeviceIO: 3082: Cmd(0x459a40c1d280) 0x89, CmdSN 0x6d from world 2097185 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x35 0x20.

2019-05-07T17:51:17.041Z cpu16:2097705)ScsiDeviceIO: 3047: Cmd(0x45a37d996b40) 0x28, CmdSN 0x6c from world 2098280 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x78 0x32 0x20.

2019-05-07T17:51:17.042Z cpu16:2097211)ScsiDeviceIO: 3047: Cmd(0x459b98c86580) 0x28, CmdSN 0x6e from world 2100138 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x9 0x1a 0x45.

2019-05-07T17:51:17.106Z cpu16:2097705)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 10 times

2019-05-07T17:51:17.110Z cpu8:2097505)LVM: 5748: Received APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 17)

2019-05-07T17:51:17.110Z cpu8:2097505)LVM: 5356: Handling APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 17, cur apd state UNKNOWN, cur dev state 1)

2019-05-07T17:51:17.110Z cpu8:2097505)HBX: 6287: APD EventType: APD_START (3) for vol 'SAN-PRODUCTION'

2019-05-07T17:51:17.110Z cpu8:2097505)ScsiDevice: 5978: Device state of naa.6589cfc0000002975052862c22403cca set to APD_START; token num:1

2019-05-07T17:51:17.110Z cpu8:2097505)StorageApdHandler: 1203: APD start for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:51:17.110Z cpu0:2097490)StorageApdHandler: 419: APD start event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:51:17.110Z cpu0:2097490)StorageApdHandlerEv: 110: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has entered the All Paths Down state.

2019-05-07T17:51:17.112Z cpu2:2098234)WARNING: NMP: nmp_IssueCommandToDevice:5082: I/O could not be issued to device "naa.6589cfc0000002975052862c22403cca" due to Not found

2019-05-07T17:51:17.112Z cpu2:2098234)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2019-05-07T17:51:17.112Z cpu2:2098234)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:51:18.040Z cpu12:2097547)ScsiDeviceIO: 3082: Cmd(0x459b98ce9f40) 0x89, CmdSN 0x6f from world 2097185 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x18 0x4 0x43.

2019-05-07T17:51:18.040Z cpu12:2097547)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:51:18.040Z cpu9:2097204)ScsiDeviceIO: 3032: Cmd(0x45a37d996b40) 0x28, CmdSN 0x6c from world 2098280 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x8 D:0x0 P:0x0

2019-05-07T17:51:18.041Z cpu9:2097204)ScsiDeviceIO: 3032: Cmd(0x459b98c86580) 0x28, CmdSN 0x6e from world 2100138 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x8 D:0x0 P:0x0

2019-05-07T17:51:18.041Z cpu12:2098281)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:51:18.041Z cpu12:2098281)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24703934162 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:51:18.110Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:603: Retry world restore device "naa.6589cfc0000002975052862c22403cca" - no more commands to retry

2019-05-07T17:51:19.331Z cpu11:2248652)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:51:19.331Z cpu11:2248652)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24703934162 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:51:20.146Z cpu22:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430bd54cc9f0 network resource pool netsched.pools.persist.iscsi associated

2019-05-07T17:51:20.146Z cpu22:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430bd54cc9f0 network tracker id 45045162 tracker.iSCSI.10.39.130.222 associated

2019-05-07T17:51:20.398Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "ONLINE"

2019-05-07T17:51:20.398Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:51:20.398Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 10.39.130.35:56605 R: 10.39.130.222:3260]

2019-05-07T17:51:20.541Z cpu2:2100195)WARNING: NMP: nmp_IssueCommandToDevice:5082: I/O could not be issued to device "naa.6589cfc0000002975052862c22403cca" due to Not found

2019-05-07T17:51:20.541Z cpu2:2100195)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2019-05-07T17:51:20.542Z cpu2:2100195)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:51:21.114Z cpu5:2097505)ScsiDevice: 6000: Setting Device naa.6589cfc0000002975052862c22403cca state back to 0x2

2019-05-07T17:51:21.114Z cpu5:2097505)LVM: 5748: Received APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 18)

2019-05-07T17:51:21.114Z cpu5:2097505)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 18, cur apd state APD_START, cur dev state 1)

2019-05-07T17:51:21.114Z cpu5:2097505)ScsiDevice: 6021: Device naa.6589cfc0000002975052862c22403cca is Out of APD; token num:1

2019-05-07T17:51:21.114Z cpu0:2097255)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (locked, gen 18, cur apd state APD_START, cur dev state 1)

2019-05-07T17:51:21.114Z cpu1:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459a40d93740

2019-05-07T17:51:24.463Z cpu16:2097211)NMP: nmpCompleteRetryForPath:327: Retry world recovered device "naa.6589cfc0000002975052862c22403cca"

2019-05-07T17:51:25.110Z cpu0:2098823)SunRPC: 3303: Synchronous RPC abort for client 0x4305cc2271c0 IP 10.39.115.222.0.111 proc 3 xid 0x439cd42c attempt 3 of 3

2019-05-07T17:51:25.110Z cpu0:2098823)SunRPC: 1099: Destroying world 0x224fd9

2019-05-07T17:51:29.332Z cpu1:2248652)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:51:29.332Z cpu1:2248652)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24703934162 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:51:33.390Z cpu13:2098820)WARNING: LSOM: LSOMVsiGetVirstoInstanceStats:800: Throttled: Attempt to get Virsto stats on unsupported disk52256481-aa44-4783-d2f0-625461b41dfe

2019-05-07T17:51:39.335Z cpu1:2248652)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:51:39.335Z cpu1:2248652)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24703934162 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:51:46.272Z cpu20:2097729)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1197: vmhba65:CH:0 T:1 CN:0: Connection tx notifying failure: Network Send Error. State=Online

2019-05-07T17:51:46.272Z cpu20:2097729)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1198: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:51:46.272Z cpu20:2097729)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1199: Conn [CID: 0 L: 10.39.130.35:56605 R: 10.39.130.222:3260]

2019-05-07T17:51:46.272Z cpu18:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:699: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)

2019-05-07T17:51:46.272Z cpu18:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:700: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:51:46.272Z cpu18:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:701: Conn [CID: 0 L: 10.39.130.35:56605 R: 10.39.130.222:3260]

2019-05-07T17:51:46.281Z cpu18:2097707)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6589cfc0000002975052862c22403cca" state in doubt; requested fast path state update...

2019-05-07T17:51:46.281Z cpu18:2097707)ScsiDeviceIO: 3047: Cmd(0x459a40cde840) 0x28, CmdSN 0x73 from world 0 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x43.

2019-05-07T17:51:46.281Z cpu18:2097707)ScsiDeviceIO: 3047: Cmd(0x459b98d932c0) 0x12, CmdSN 0x1782 from world 0 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x43.

2019-05-07T17:51:46.394Z cpu18:2097707)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 20 times

2019-05-07T17:51:46.645Z cpu18:2097707)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 40 times

2019-05-07T17:51:47.111Z cpu0:2097505)LVM: 5748: Received APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 19)

2019-05-07T17:51:47.111Z cpu0:2097505)LVM: 5356: Handling APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 19, cur apd state APD_START, cur dev state 1)

2019-05-07T17:51:47.111Z cpu0:2097505)WARNING: LVM: 5375: Pre-existing unhandled APD event for device <naa.6589cfc0000002975052862c22403cca:3>: type APD_EXIT (gen 18)

2019-05-07T17:51:47.111Z cpu0:2097505)StorageApdHandler: 1315: APD exit for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:51:47.111Z cpu0:2097505)HBX: 6287: APD EventType: APD_START (3) for vol 'SAN-PRODUCTION'

2019-05-07T17:51:47.111Z cpu0:2097505)ScsiDevice: 5978: Device state of naa.6589cfc0000002975052862c22403cca set to APD_START; token num:2

2019-05-07T17:51:47.111Z cpu0:2097505)StorageApdHandler: 1218: APD bounce-start for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca], no event transition

2019-05-07T17:51:47.118Z cpu18:2098469)WARNING: NMP: nmp_IssueCommandToDevice:5082: I/O could not be issued to device "naa.6589cfc0000002975052862c22403cca" due to Not found

2019-05-07T17:51:47.118Z cpu18:2098469)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2019-05-07T17:51:47.118Z cpu18:2098469)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:51:48.111Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459a40cde840

2019-05-07T17:51:48.111Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:51:48.111Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:51:49.044Z cpu22:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430bd5546e80 network resource pool netsched.pools.persist.iscsi associated

2019-05-07T17:51:49.044Z cpu22:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430bd5546e80 network tracker id 45045162 tracker.iSCSI.10.39.130.222 associated

2019-05-07T17:51:49.111Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459a40cde840

2019-05-07T17:51:49.111Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:51:49.111Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:51:49.298Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "ONLINE"

2019-05-07T17:51:49.298Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:51:49.298Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 10.39.130.35:37059 R: 10.39.130.222:3260]

2019-05-07T17:51:49.339Z cpu3:2248652)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:51:49.339Z cpu3:2248652)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24703934162 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:51:50.113Z cpu10:2097505)ScsiDevice: 6000: Setting Device naa.6589cfc0000002975052862c22403cca state back to 0x2

2019-05-07T17:51:50.113Z cpu10:2097505)LVM: 5748: Received APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 20)

2019-05-07T17:51:50.113Z cpu10:2097505)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 20, cur apd state APD_START, cur dev state 1)

2019-05-07T17:51:50.113Z cpu10:2097505)ScsiDevice: 6021: Device naa.6589cfc0000002975052862c22403cca is Out of APD; token num:1

2019-05-07T17:51:50.114Z cpu16:2098023)NMP: nmpCompleteRetryForPath:327: Retry world recovered device "naa.6589cfc0000002975052862c22403cca"

2019-05-07T17:51:53.614Z cpu4:2097255)LVM: 5425: Async handling of event APD_EXIT for device <naa.6589cfc0000002975052862c22403cca:3> took too long - bailing (my gen 18, cur gen 20, cur state APD_START)

2019-05-07T17:51:53.614Z cpu4:2097255)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (locked, gen 20, cur apd state APD_START, cur dev state 1)

2019-05-07T17:51:59.043Z cpu0:2097255)HBX: 6287: APD EventType: APD_EXIT (4) for vol 'SAN-PRODUCTION'

2019-05-07T17:51:59.043Z cpu0:2097255)LVM: 5487: Device <naa.6589cfc000000f7547481ec53d72549e:1> APD handler with closeOnAPDExit - attempting close.

2019-05-07T17:51:59.045Z cpu8:2098161)HBX: 312: 'SAN-PRODUCTION': HB at offset 3407872 - Reclaimed heartbeat [Timeout]:

2019-05-07T17:51:59.045Z cpu8:2098161)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24744936741 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:51:59.045Z cpu8:2098161)StorageApdHandler: 1315: APD exit for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:51:59.045Z cpu8:2098161)HBX: 5509: Completed APD/PDL event processing on vol 'SAN-PRODUCTION'.

2019-05-07T17:51:59.045Z cpu0:2097490)StorageApdHandler: 507: APD exit event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:51:59.045Z cpu0:2097490)StorageApdHandlerEv: 117: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has exited the All Paths Down state.

2019-05-07T17:52:04.114Z cpu4:2097835)NMP: nmp_ResetDeviceLogThrottling:3569: Error status H:0x0 D:0x2 P:0x0 Sense Data: 0x5 0x24 0x0 from dev "mpx.vmhba1:C0:T0:L0" occurred 1 times(of 1 commands)

2019-05-07T17:52:26.114Z cpu2:2098823)SunRPC: 1099: Destroying world 0x2250fb

2019-05-07T17:52:34.112Z cpu8:2097835)NMP: nmp_ResetDeviceLogThrottling:3575: last error status from device naa.6589cfc0000002975052862c22403cca repeated 73 times

2019-05-07T17:52:58.437Z cpu14:2097918)ScsiDeviceIO: 3068: Cmd(0x45a24068ac40) 0x1a, CmdSN 0x17b8 from world 0 to dev "naa.6782bcb05bcabf0021f7e31c06bb079d" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2019-05-07T17:53:19.373Z cpu0:2248652)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:53:19.373Z cpu0:2248652)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24811934158 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:53:24.048Z cpu12:2097547)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue:633: vmhba65:CH:0 T:1 L:70 : Task mgmt "Abort Task" with itt=0xb3c (refITT=0xb3b) timed out.

2019-05-07T17:53:24.048Z cpu17:2097726)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1197: vmhba65:CH:0 T:1 CN:0: Connection tx notifying failure: Network Send Error. State=Online

2019-05-07T17:53:24.048Z cpu17:2097726)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1198: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:53:24.048Z cpu17:2097726)iscsi_vmk: iscsivmk_ConnTxNotifyFailure:1199: Conn [CID: 0 L: 10.39.130.35:37059 R: 10.39.130.222:3260]

2019-05-07T17:53:24.048Z cpu23:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:699: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)

2019-05-07T17:53:24.048Z cpu23:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:700: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:53:24.048Z cpu23:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:701: Conn [CID: 0 L: 10.39.130.35:37059 R: 10.39.130.222:3260]

2019-05-07T17:53:24.052Z cpu12:2097547)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue:633: vmhba65:CH:0 T:1 L:70 : Task mgmt "Abort Task" with itt=0xb3d (refITT=0xb3b) timed out.

2019-05-07T17:53:24.052Z cpu12:2097547)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x89 (0x459a40c8cf40, 2097185) to dev "naa.6589cfc0000002975052862c22403cca" on path "vmhba65:C0:T1:L70" Failed: H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:53:24.052Z cpu12:2097547)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6589cfc0000002975052862c22403cca" state in doubt; requested fast path state update...

2019-05-07T17:53:24.052Z cpu23:2097218)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x28 (0x459b98d37c40, 2100138) to dev "naa.6589cfc0000002975052862c22403cca" on path "vmhba65:C0:T1:L70" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:53:24.052Z cpu12:2097547)ScsiDeviceIO: 3082: Cmd(0x459a40c8cf40) 0x89, CmdSN 0xae from world 2097185 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x35 0x20.

2019-05-07T17:53:24.052Z cpu23:2097218)ScsiDeviceIO: 3047: Cmd(0x459b98d37c40) 0x28, CmdSN 0xad from world 2100138 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x78 0x32 0x20.

2019-05-07T17:53:24.052Z cpu8:2097697)ScsiDeviceIO: 3047: Cmd(0x459b98d76d00) 0x28, CmdSN 0xaf from world 0 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x2 0x80 0x41.

2019-05-07T17:53:24.114Z cpu1:2097505)LVM: 5748: Received APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 21)

2019-05-07T17:53:24.114Z cpu1:2097505)LVM: 5356: Handling APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 21, cur apd state UNKNOWN, cur dev state 1)

2019-05-07T17:53:24.114Z cpu1:2097505)HBX: 6287: APD EventType: APD_START (3) for vol 'SAN-PRODUCTION'

2019-05-07T17:53:24.114Z cpu1:2097505)ScsiDevice: 5978: Device state of naa.6589cfc0000002975052862c22403cca set to APD_START; token num:1

2019-05-07T17:53:24.114Z cpu1:2097505)StorageApdHandler: 1203: APD start for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:53:24.114Z cpu0:2097490)StorageApdHandler: 419: APD start event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:53:24.114Z cpu0:2097490)StorageApdHandlerEv: 110: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has entered the All Paths Down state.

2019-05-07T17:53:24.120Z cpu8:2097183)WARNING: NMP: nmp_IssueCommandToDevice:5082: I/O could not be issued to device "naa.6589cfc0000002975052862c22403cca" due to Not found

2019-05-07T17:53:24.120Z cpu8:2097183)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2019-05-07T17:53:24.120Z cpu8:2097183)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:53:25.114Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459b98d76d00

2019-05-07T17:53:25.114Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:53:25.114Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:53:26.113Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459b98d76d00

2019-05-07T17:53:26.114Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:53:26.114Z cpu0:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:53:26.559Z cpu12:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430bd5546e80 network resource pool netsched.pools.persist.iscsi associated

2019-05-07T17:53:26.559Z cpu12:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430bd5546e80 network tracker id 45045162 tracker.iSCSI.10.39.130.222 associated

2019-05-07T17:53:26.811Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "ONLINE"

2019-05-07T17:53:26.811Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:53:26.811Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 10.39.130.35:31611 R: 10.39.130.222:3260]

2019-05-07T17:53:27.117Z cpu3:2097505)ScsiDevice: 6000: Setting Device naa.6589cfc0000002975052862c22403cca state back to 0x2

2019-05-07T17:53:27.117Z cpu3:2097505)LVM: 5748: Received APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 22)

2019-05-07T17:53:27.117Z cpu3:2097505)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 22, cur apd state APD_START, cur dev state 1)

2019-05-07T17:53:27.117Z cpu3:2097505)ScsiDevice: 6021: Device naa.6589cfc0000002975052862c22403cca is Out of APD; token num:1

2019-05-07T17:53:27.117Z cpu0:2097255)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (locked, gen 22, cur apd state APD_START, cur dev state 1)

2019-05-07T17:53:27.117Z cpu15:2098023)NMP: nmpCompleteRetryForPath:327: Retry world recovered device "naa.6589cfc0000002975052862c22403cca"

2019-05-07T17:53:27.347Z cpu8:2098161)HBX: 312: 'SAN-PRODUCTION': HB at offset 3407872 - Reclaimed heartbeat [Timeout]:

2019-05-07T17:53:27.347Z cpu8:2098161)  [HB state abcdef02 offset 3407872 gen 37 stampUS 24833007489 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 4> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:53:28.113Z cpu0:2098823)SunRPC: 1099: Destroying world 0x2252a2

2019-05-07T17:53:33.286Z cpu0:2097255)HBX: 6287: APD EventType: APD_EXIT (4) for vol 'SAN-PRODUCTION'

2019-05-07T17:53:33.286Z cpu0:2097255)StorageApdHandler: 1315: APD exit for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:53:33.286Z cpu0:2097255)HBX: 5509: Completed APD/PDL event processing on vol 'SAN-PRODUCTION'.

2019-05-07T17:53:33.286Z cpu0:2097255)LVM: 5487: Device <naa.6589cfc000000f7547481ec53d72549e:1> APD handler with closeOnAPDExit - attempting close.

2019-05-07T17:53:33.286Z cpu2:2097490)StorageApdHandler: 507: APD exit event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:53:33.286Z cpu2:2097490)StorageApdHandlerEv: 117: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has exited the All Paths Down state.

2019-05-07T17:54:04.114Z cpu2:2097835)NMP: nmp_ResetDeviceLogThrottling:3575: last error status from device naa.6589cfc0000002975052862c22403cca repeated 5 times

2019-05-07T17:54:08.519Z cpu15:2097918)ScsiDeviceIO: 3068: Cmd(0x45a240703b40) 0x1a, CmdSN 0x1819 from world 0 to dev "naa.6782bcb05bcabf00ff0000380397ca71" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

2019-05-07T17:54:30.115Z cpu2:2098823)SunRPC: 1099: Destroying world 0x2253c2

2019-05-07T17:54:34.115Z cpu7:2097507)ScsiVmas: 804: Inquiry for VPD page 00 to device naa.6589cfc000000f7547481ec53d72549e failed with error No connection

2019-05-07T17:55:31.118Z cpu11:2098823)SunRPC: 1099: Destroying world 0x225593

2019-05-07T17:56:32.120Z cpu2:2098823)SunRPC: 1099: Destroying world 0x2256a8

2019-05-07T17:56:33.387Z cpu16:2098820)WARNING: LSOM: LSOMVsiGetVirstoInstanceStats:800: Throttled: Attempt to get Virsto stats on unsupported disk52256481-aa44-4783-d2f0-625461b41dfe

2019-05-07T17:56:41.760Z cpu20:2098023)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic:517: vmhba65:CH:0 T:1 CN:0: Failed to receive data: Connection closed by peer

2019-05-07T17:56:41.760Z cpu20:2098023)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic:525: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:56:41.760Z cpu20:2098023)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic:526: Conn [CID: 0 L: 10.39.130.35:31611 R: 10.39.130.222:3260]

2019-05-07T17:56:41.760Z cpu20:2098023)iscsi_vmk: iscsivmk_ConnRxNotifyFailure:1235: vmhba65:CH:0 T:1 CN:0: Connection rx notifying failure: Failed to Receive. State=Online

2019-05-07T17:56:41.760Z cpu20:2098023)iscsi_vmk: iscsivmk_ConnRxNotifyFailure:1236: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:56:41.760Z cpu20:2098023)iscsi_vmk: iscsivmk_ConnRxNotifyFailure:1237: Conn [CID: 0 L: 10.39.130.35:31611 R: 10.39.130.222:3260]

2019-05-07T17:56:41.760Z cpu16:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:699: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)

2019-05-07T17:56:41.760Z cpu16:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:700: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:56:41.760Z cpu16:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:701: Conn [CID: 0 L: 10.39.130.35:31611 R: 10.39.130.222:3260]

2019-05-07T17:56:41.766Z cpu0:2097195)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x28 (0x459a40d3e9c0, 2100138) to dev "naa.6589cfc0000002975052862c22403cca" on path "vmhba65:C0:T1:L70" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:56:41.766Z cpu0:2097195)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6589cfc0000002975052862c22403cca" state in doubt; requested fast path state update...

2019-05-07T17:56:41.766Z cpu0:2097195)ScsiDeviceIO: 3047: Cmd(0x459a40d3e9c0) 0x28, CmdSN 0x6d from world 2100138 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x20 0x44.

2019-05-07T17:56:41.908Z cpu0:2097195)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 10 times

2019-05-07T17:56:42.049Z cpu0:2097689)ScsiDeviceIO: 3047: Cmd(0x459a40cbc880) 0x89, CmdSN 0x6e from world 2097185 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x40 0x80 0x41.

2019-05-07T17:56:42.119Z cpu4:2097505)LVM: 5748: Received APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 23)

2019-05-07T17:56:42.119Z cpu4:2097505)LVM: 5356: Handling APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 23, cur apd state UNKNOWN, cur dev state 1)

2019-05-07T17:56:42.119Z cpu4:2097505)HBX: 6287: APD EventType: APD_START (3) for vol 'SAN-PRODUCTION'

2019-05-07T17:56:42.119Z cpu4:2097505)ScsiDevice: 5978: Device state of naa.6589cfc0000002975052862c22403cca set to APD_START; token num:1

2019-05-07T17:56:42.119Z cpu4:2097505)StorageApdHandler: 1203: APD start for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:56:42.119Z cpu1:2097490)StorageApdHandler: 419: APD start event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:56:42.119Z cpu1:2097490)StorageApdHandlerEv: 110: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has entered the All Paths Down state.

2019-05-07T17:56:42.121Z cpu0:2101764)WARNING: NMP: nmp_IssueCommandToDevice:5082: I/O could not be issued to device "naa.6589cfc0000002975052862c22403cca" due to Not found

2019-05-07T17:56:42.121Z cpu0:2101764)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2019-05-07T17:56:42.121Z cpu0:2101764)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:56:43.119Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459a40cbc880

2019-05-07T17:56:43.119Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:56:43.119Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:56:44.119Z cpu4:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459a40cbc880

2019-05-07T17:56:44.119Z cpu4:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:56:44.119Z cpu4:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:56:44.667Z cpu22:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430bd554eaa0 network resource pool netsched.pools.persist.iscsi associated

2019-05-07T17:56:44.667Z cpu22:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430bd554eaa0 network tracker id 45045162 tracker.iSCSI.10.39.130.222 associated

2019-05-07T17:56:44.921Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "ONLINE"

2019-05-07T17:56:44.921Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:56:44.921Z cpu22:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 10.39.130.35:49504 R: 10.39.130.222:3260]

2019-05-07T17:56:45.122Z cpu9:2097505)ScsiDevice: 6000: Setting Device naa.6589cfc0000002975052862c22403cca state back to 0x2

2019-05-07T17:56:45.122Z cpu9:2097505)LVM: 5748: Received APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 24)

2019-05-07T17:56:45.122Z cpu9:2097505)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 24, cur apd state APD_START, cur dev state 1)

2019-05-07T17:56:45.122Z cpu9:2097505)ScsiDevice: 6021: Device naa.6589cfc0000002975052862c22403cca is Out of APD; token num:1

2019-05-07T17:56:45.122Z cpu0:2097255)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (locked, gen 24, cur apd state APD_START, cur dev state 1)

2019-05-07T17:56:45.123Z cpu16:2098023)NMP: nmpCompleteRetryForPath:327: Retry world recovered device "naa.6589cfc0000002975052862c22403cca"

2019-05-07T17:56:51.630Z cpu0:2097255)HBX: 6287: APD EventType: APD_EXIT (4) for vol 'SAN-PRODUCTION'

2019-05-07T17:56:51.630Z cpu0:2097255)StorageApdHandler: 1315: APD exit for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:56:51.630Z cpu0:2097255)HBX: 5509: Completed APD/PDL event processing on vol 'SAN-PRODUCTION'.

2019-05-07T17:56:51.630Z cpu0:2097255)LVM: 5487: Device <naa.6589cfc000000f7547481ec53d72549e:1> APD handler with closeOnAPDExit - attempting close.

2019-05-07T17:56:51.630Z cpu4:2097490)StorageApdHandler: 507: APD exit event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:56:51.630Z cpu4:2097490)StorageApdHandlerEv: 117: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has exited the All Paths Down state.

2019-05-07T17:57:09.724Z cpu20:2250615)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:57:09.724Z cpu20:2250615)  [HB state abcdef02 offset 3407872 gen 41 stampUS 25045933439 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 8388614> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:57:18.052Z cpu14:2097547)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue:633: vmhba65:CH:0 T:1 L:70 : Task mgmt "Abort Task" with itt=0xe98 (refITT=0xe97) timed out.

2019-05-07T17:57:19.727Z cpu14:2250615)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:57:19.727Z cpu14:2250615)  [HB state abcdef02 offset 3407872 gen 41 stampUS 25045933439 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 8388614> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:57:28.054Z cpu14:2097547)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue:633: vmhba65:CH:0 T:1 L:70 : Task mgmt "Abort Task" with itt=0xe99 (refITT=0xe97) timed out.

2019-05-07T17:57:29.731Z cpu13:2250615)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:57:29.731Z cpu13:2250615)  [HB state abcdef02 offset 3407872 gen 41 stampUS 25045933439 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 8388614> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:57:33.348Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StopConnection:699: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)

2019-05-07T17:57:33.348Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StopConnection:700: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:57:33.348Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StopConnection:701: Conn [CID: 0 L: 10.39.130.35:49504 R: 10.39.130.222:3260]

2019-05-07T17:57:33.352Z cpu12:2097207)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 20 times

2019-05-07T17:57:33.352Z cpu12:2097207)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6589cfc0000002975052862c22403cca" state in doubt; requested fast path state update...

2019-05-07T17:57:33.352Z cpu12:2097207)ScsiDeviceIO: 3047: Cmd(0x459b98daa240) 0x28, CmdSN 0x7f from world 2100138 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x1a 0x45.

2019-05-07T17:57:33.352Z cpu14:2097547)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue:633: vmhba65:CH:0 T:1 L:70 : Task mgmt "Abort Task" with itt=0xe9b (refITT=0xe97) timed out.

2019-05-07T17:57:33.352Z cpu14:2097547)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x89 (0x459a40deb580, 2097185) to dev "naa.6589cfc0000002975052862c22403cca" on path "vmhba65:C0:T1:L70" Failed: H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:57:33.352Z cpu14:2097547)ScsiDeviceIO: 3082: Cmd(0x459a40deb580) 0x89, CmdSN 0x80 from world 2097185 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x5 D:0x0 P:0x0 Invalid sense data: 0x78 0x35 0x20.

2019-05-07T17:57:33.352Z cpu8:2097697)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x28 (0x459b98d0b3c0, 0) to dev "naa.6589cfc0000002975052862c22403cca" on path "vmhba65:C0:T1:L70" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-05-07T17:57:33.352Z cpu8:2097697)ScsiDeviceIO: 3047: Cmd(0x459b98d0b3c0) 0x28, CmdSN 0x81 from world 0 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x30 0x20 0x50.

2019-05-07T17:57:33.498Z cpu8:2097697)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 10 times

2019-05-07T17:57:33.786Z cpu8:2097697)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 20 times

2019-05-07T17:57:34.121Z cpu2:2097505)LVM: 5748: Received APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 25)

2019-05-07T17:57:34.121Z cpu2:2097505)LVM: 5356: Handling APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 25, cur apd state UNKNOWN, cur dev state 1)

2019-05-07T17:57:34.121Z cpu2:2097505)HBX: 6287: APD EventType: APD_START (3) for vol 'SAN-PRODUCTION'

2019-05-07T17:57:34.121Z cpu2:2097505)ScsiDevice: 5978: Device state of naa.6589cfc0000002975052862c22403cca set to APD_START; token num:1

2019-05-07T17:57:34.121Z cpu2:2097505)StorageApdHandler: 1203: APD start for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:57:34.121Z cpu4:2097490)StorageApdHandler: 419: APD start event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:57:34.121Z cpu4:2097490)StorageApdHandlerEv: 110: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has entered the All Paths Down state.

2019-05-07T17:57:34.121Z cpu8:2098823)SunRPC: 1099: Destroying world 0x22586e

2019-05-07T17:57:34.133Z cpu8:2097900)WARNING: NMP: nmp_IssueCommandToDevice:5082: I/O could not be issued to device "naa.6589cfc0000002975052862c22403cca" due to Not found

2019-05-07T17:57:34.133Z cpu8:2097900)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2019-05-07T17:57:34.133Z cpu8:2097900)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:57:35.120Z cpu4:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459b98d0b3c0

2019-05-07T17:57:35.120Z cpu4:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:57:35.120Z cpu4:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:57:36.120Z cpu2:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459b98d0b3c0

2019-05-07T17:57:36.121Z cpu2:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:57:36.121Z cpu2:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:57:36.121Z cpu13:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430bd563c320 network resource pool netsched.pools.persist.iscsi associated

2019-05-07T17:57:36.121Z cpu13:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430bd563c320 network tracker id 45045162 tracker.iSCSI.10.39.130.222 associated

2019-05-07T17:57:36.375Z cpu13:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "ONLINE"

2019-05-07T17:57:36.375Z cpu13:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:57:36.375Z cpu13:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 10.39.130.35:15542 R: 10.39.130.222:3260]

2019-05-07T17:57:37.124Z cpu5:2097505)ScsiDevice: 6000: Setting Device naa.6589cfc0000002975052862c22403cca state back to 0x2

2019-05-07T17:57:37.124Z cpu5:2097505)LVM: 5748: Received APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 26)

2019-05-07T17:57:37.124Z cpu5:2097505)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 26, cur apd state APD_START, cur dev state 1)

2019-05-07T17:57:37.124Z cpu5:2097505)ScsiDevice: 6021: Device naa.6589cfc0000002975052862c22403cca is Out of APD; token num:1

2019-05-07T17:57:37.124Z cpu0:2097255)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (locked, gen 26, cur apd state APD_START, cur dev state 1)

2019-05-07T17:57:37.125Z cpu12:2098023)NMP: nmpCompleteRetryForPath:327: Retry world recovered device "naa.6589cfc0000002975052862c22403cca"

2019-05-07T17:57:37.343Z cpu1:2098161)HBX: 312: 'SAN-PRODUCTION': HB at offset 3407872 - Reclaimed heartbeat [Timeout]:

2019-05-07T17:57:37.343Z cpu1:2098161)  [HB state abcdef02 offset 3407872 gen 41 stampUS 25083008142 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 8388614> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:57:42.573Z cpu7:2097255)HBX: 6287: APD EventType: APD_EXIT (4) for vol 'SAN-PRODUCTION'

2019-05-07T17:57:42.573Z cpu7:2097255)StorageApdHandler: 1315: APD exit for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:57:42.573Z cpu7:2097255)HBX: 5509: Completed APD/PDL event processing on vol 'SAN-PRODUCTION'.

2019-05-07T17:57:42.573Z cpu7:2097255)LVM: 5487: Device <naa.6589cfc000000f7547481ec53d72549e:1> APD handler with closeOnAPDExit - attempting close.

2019-05-07T17:57:42.573Z cpu4:2097490)StorageApdHandler: 507: APD exit event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:57:42.573Z cpu4:2097490)StorageApdHandlerEv: 117: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has exited the All Paths Down state.

2019-05-07T17:57:55.833Z cpu22:2098023)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic:517: vmhba65:CH:0 T:1 CN:0: Failed to receive data: Connection closed by peer

2019-05-07T17:57:55.833Z cpu22:2098023)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic:525: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:57:55.833Z cpu22:2098023)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic:526: Conn [CID: 0 L: 10.39.130.35:15542 R: 10.39.130.222:3260]

2019-05-07T17:57:55.833Z cpu22:2098023)iscsi_vmk: iscsivmk_ConnRxNotifyFailure:1235: vmhba65:CH:0 T:1 CN:0: Connection rx notifying failure: Failed to Receive. State=Online

2019-05-07T17:57:55.833Z cpu22:2098023)iscsi_vmk: iscsivmk_ConnRxNotifyFailure:1236: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:57:55.833Z cpu22:2098023)iscsi_vmk: iscsivmk_ConnRxNotifyFailure:1237: Conn [CID: 0 L: 10.39.130.35:15542 R: 10.39.130.222:3260]

2019-05-07T17:57:55.833Z cpu22:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:699: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:6)

2019-05-07T17:57:55.833Z cpu22:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:700: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:57:55.833Z cpu22:2097688)WARNING: iscsi_vmk: iscsivmk_StopConnection:701: Conn [CID: 0 L: 10.39.130.35:15542 R: 10.39.130.222:3260]

2019-05-07T17:57:55.838Z cpu2:2097197)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6589cfc0000002975052862c22403cca" state in doubt; requested fast path state update...

2019-05-07T17:57:55.838Z cpu2:2097197)ScsiDeviceIO: 3047: Cmd(0x459b98dd7d80) 0x28, CmdSN 0x95 from world 2100138 to dev "naa.6589cfc0000002975052862c22403cca" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x1a 0x45.

2019-05-07T17:57:56.065Z cpu2:2097197)NMP: nmp_ThrottleLogForDevice:3710: last error status from device naa.6589cfc0000002975052862c22403cca repeated 40 times

2019-05-07T17:57:56.121Z cpu2:2097197)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6589cfc0000002975052862c22403cca" state in doubt; requested fast path state update...

2019-05-07T17:57:56.121Z cpu5:2097505)LVM: 5748: Received APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 27)

2019-05-07T17:57:56.121Z cpu5:2097505)LVM: 5356: Handling APD EventType: APD_START (3) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 27, cur apd state UNKNOWN, cur dev state 1)

2019-05-07T17:57:56.121Z cpu5:2097505)HBX: 6287: APD EventType: APD_START (3) for vol 'SAN-PRODUCTION'

2019-05-07T17:57:56.121Z cpu5:2097505)ScsiDevice: 5978: Device state of naa.6589cfc0000002975052862c22403cca set to APD_START; token num:1

2019-05-07T17:57:56.121Z cpu5:2097505)StorageApdHandler: 1203: APD start for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:57:56.121Z cpu6:2097490)StorageApdHandler: 419: APD start event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:57:56.121Z cpu6:2097490)StorageApdHandlerEv: 110: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has entered the All Paths Down state.

2019-05-07T17:57:56.135Z cpu2:2099067)WARNING: NMP: nmp_IssueCommandToDevice:5082: I/O could not be issued to device "naa.6589cfc0000002975052862c22403cca" due to Not found

2019-05-07T17:57:56.135Z cpu2:2099067)WARNING: NMP: nmp_DeviceRetryCommand:133: Device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update for failover with I/O blocked. No prior reservation exists on the device.

2019-05-07T17:57:56.135Z cpu2:2099067)WARNING: NMP: nmp_DeviceStartLoop:729: NMP Device "naa.6589cfc0000002975052862c22403cca" is blocked. Not starting I/O from device.

2019-05-07T17:57:57.122Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459b98dd7d80

2019-05-07T17:57:57.122Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:57:57.122Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:57:58.123Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - issuing command 0x459b98dd7d80

2019-05-07T17:57:58.123Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:715: Retry world failover device "naa.6589cfc0000002975052862c22403cca" - failed to issue command due to Not found (APD), try again...

2019-05-07T17:57:58.123Z cpu5:2097836)WARNING: NMP: nmpDeviceAttemptFailover:765: Logical device "naa.6589cfc0000002975052862c22403cca": awaiting fast path state update...

2019-05-07T17:57:58.851Z cpu12:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430bd5399020 network resource pool netsched.pools.persist.iscsi associated

2019-05-07T17:57:58.851Z cpu12:2098046)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430bd5399020 network tracker id 45045162 tracker.iSCSI.10.39.130.222 associated

2019-05-07T17:57:59.104Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba65:CH:0 T:1 CN:0: iSCSI connection is being marked "ONLINE"

2019-05-07T17:57:59.104Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2005-10.org.freenas.ctl:all-esxi TPGT: 1 TSIH: 0]

2019-05-07T17:57:59.104Z cpu12:2098046)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 10.39.130.35:47878 R: 10.39.130.222:3260]

2019-05-07T17:57:59.124Z cpu0:2097505)ScsiDevice: 6000: Setting Device naa.6589cfc0000002975052862c22403cca state back to 0x2

2019-05-07T17:57:59.124Z cpu0:2097505)LVM: 5748: Received APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (gen 28)

2019-05-07T17:57:59.124Z cpu0:2097505)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (unlocked, gen 28, cur apd state APD_START, cur dev state 1)

2019-05-07T17:57:59.124Z cpu0:2097505)ScsiDevice: 6021: Device naa.6589cfc0000002975052862c22403cca is Out of APD; token num:1

2019-05-07T17:57:59.124Z cpu7:2097255)LVM: 5356: Handling APD EventType: APD_EXIT (4) for device <naa.6589cfc0000002975052862c22403cca:3> (locked, gen 28, cur apd state APD_START, cur dev state 1)

2019-05-07T17:58:02.946Z cpu17:2097212)NMP: nmpCompleteRetryForPath:327: Retry world recovered device "naa.6589cfc0000002975052862c22403cca"

2019-05-07T17:58:09.744Z cpu14:2250615)HBX: 3033: 'SAN-PRODUCTION': HB at offset 3407872 - Waiting for timed out HB:

2019-05-07T17:58:09.744Z cpu14:2250615)  [HB state abcdef02 offset 3407872 gen 41 stampUS 25108932940 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 8388614> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:58:11.157Z cpu7:2097255)HBX: 6287: APD EventType: APD_EXIT (4) for vol 'SAN-PRODUCTION'

2019-05-07T17:58:11.157Z cpu7:2097255)LVM: 5487: Device <naa.6589cfc000000f7547481ec53d72549e:1> APD handler with closeOnAPDExit - attempting close.

2019-05-07T17:58:11.157Z cpu8:2098234)ScsiDeviceIO: 4536: Command 0x89 (CmdSN 0xa3, World 2097185) to device naa.6589cfc0000002975052862c22403cca timed out: expiry time occurs 2105ms in the past

2019-05-07T17:58:11.157Z cpu8:2098234)WARNING: ScsiVmas: 3021: Failed to issue command on device "naa.6589cfc0000002975052862c22403cca": Timeout

2019-05-07T17:58:11.476Z cpu1:2098161)HBX: 312: 'SAN-PRODUCTION': HB at offset 3407872 - Reclaimed heartbeat [Timeout]:

2019-05-07T17:58:11.476Z cpu1:2098161)  [HB state abcdef02 offset 3407872 gen 41 stampUS 25117052859 uuid 5cd16571-5dd95f1e-0244-782bcb396c1f jrnl <FB 8388614> drv 24.82 lockImpl 4 ip 172.16.0.35]

2019-05-07T17:58:11.476Z cpu1:2098161)StorageApdHandler: 1315: APD exit for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:58:11.477Z cpu1:2098161)HBX: 5509: Completed APD/PDL event processing on vol 'SAN-PRODUCTION'.

2019-05-07T17:58:11.477Z cpu6:2097490)StorageApdHandler: 507: APD exit event for 0x4304183eeea0 [naa.6589cfc0000002975052862c22403cca]

2019-05-07T17:58:11.477Z cpu6:2097490)StorageApdHandlerEv: 117: Device or filesystem with identifier [naa.6589cfc0000002975052862c22403cca] has exited the All Paths Down state.

2019-05-07T17:58:34.122Z cpu10:2097835)NMP: nmp_ResetDeviceLogThrottling:3575: last error status from device naa.6589cfc0000002975052862c22403cca repeated 4 times

2019-05-07T17:58:36.123Z cpu8:2098823)SunRPC: 1099: Destroying world 0x225a09

[root@esxi1:~]

iqn.2005-10.org.freenas.ctl:all-esxi

Just did a fresh install of ESXi 5.1 U1 to a brand new Dell Poweredge R520, but have some issues with this one.

When i try to create a new Datastore i get the following error "Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "217.61.87.25" failed."

I tried the solution found on Google with the partedUtil mklabel "drive" msdos command, but got the following result:

Error: Read-only file system during write on /dev/disks/naa.6b8ca3a0f469cb0019cecc656d7ba589

WriteNewPtable: Unable to commit to device /dev/disks/naa.6b8ca3a0f469cb0019cecc656d7ba589

Fdisk -l:

Disk /dev/disks/naa.6b8ca3a0f469cb0019cecc656d7ba589: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks  Id System
/dev/disks/naa.6b8ca3a0f469cb0019cecc656d7ba589p2               6         528     4193280   6 FAT16
Partition 2 does not end on cylinder boundary
/dev/disks/naa.6b8ca3a0f469cb0019cecc656d7ba589p3             528         542      112640  fc VMKcore
Partition 3 does not end on cylinder boundary

partedUtil get:

510238 255 63 8196980736

2 80325 8466884 6 0

3 8466885 8692164 252 0

How to resolve this issue, cannot do anything without any datastore

Hello trying to instal hypervisor 6.0 on a Dell R710

As per KB i updated BIOS to latest 6.4.0 and all firmware.

I keep getting this error:

This programs has encountered and error"

Error:

partedutil failed with message: Error: invalid partition table on /dev/disks/naa..... -- wrong signature 1800.

Unable to read partition for device

Thank you.

/vmfs/devices/disk/naa...

Hi!

I recently successfully updated a single Fujitsu RX350 ESXi from 5.1.0 to 6.0 Update 2. When trying to upgrade from 6 to 6.5 following error appears:

CONFLICTING_VIBS ERROR: Vibs on the host are conflicting with vibs in metadata. Remove the conflicting vibs or use Image Builder to create a custom ISO providing newer versions of the conflicting vibs.

"Emulex_bootbank_scsi_lpfc820_8.2.4 151.65-1OEM.500.0.0.472560"

I already found a solution: simply remove the vib from the old system. If I understood correctly, then the command

"esxcli software vib remove --vibname XXXX"

removes a conflicting driver from the system? If I do that what are the consequences in this case? Does the setup still recognize the installed system and the datastore with VM's?

What if the setup fails - how can I undo that step?

Many thanks in advance!

I have installed Esxi 6.7 in USB drive and I did Raid 5 on 3 disks SAS 15 krpm 300GB, I can see my 3 disks as one drive but when I try to create the second datastore I find the link of create new data store grayed out after creation of the first datastore despite the space availability.

Also when I go to Storage --> DataStores I find New Datastore link enabled but the wizard give me "No devices with free space"

I noticed the Smart Array P440ar status is Unknown, Is it normal or something wrong with drivers ?

I have spent around 5 days digging into Internet pages without success. Any Idea's ?

My server is HP Proliant DL-380

See pictures

I have a bad feeling you all will tell me I am out of Luck but I have run into an issue.

I have an ESXi Hypervisor running at home.  It is the free version running on an older Dell PC I have.  I only really have 2 active VM's.  Several Months ago I installed 6.5 on this newer older Dell and moved my disks to the new system.  I got most things set up just like under 6.0 and left it alone.  I was going to show my son something in the ESXi interface when I tried to log in as root I could not.  I am 99.999% sure I have not been hacked and I have not changed the password.  When I looked online I see the issue of expiring password.  I assume that is what happened to the root account.  I am hoping there is a way to get into the box.  When I am at the console and hit the F2 key it prompts for a login.  My root password does not work there.  Any ideas?  I really do not want to lose my VM's and I know that one of the VM's is on the same drive as the boot drive.  Any recommendations or help would be greatly appreciated.   

When trying to install vSphere Hypervisor (ESXi 5.5.0), the system consistently hangs on the yellow screen at Initializing storage stack...  Has anyone seen this, or have any idea what may be causing it?

I'm installing it bare metal from a burnt CD using a Shuttle SZ77, i5-3470S GPU, 32GB RAM, a 2TB SATA drive, a 120GB SATA SSD, and a SATA CD/DVD ROM.  The disks were working with a Linux installation on it.

Unfortunately, I don't have a serial header to hook up a serial console.

-Paul

Hi,

I am a vmware newbie. I want to set rx ring buffer size on a physical nic in my vmware server.  Currently I use the command "ethtool -G vmnic0 rx 4096" to increase the rx ring size; but I have to execute the command anytime the server reboots.  Is there any command that allows to set the buffer size persistently?

If not can I set the buffer size from vSphere Client instead from esxi shell?  I am using HyperVisor 5.0

Thanks alot!

Hi,

does the firewall in the free version of VMware Hypervisor 5 work or do I need the paid version for that feature?

I have restricted the ports for SSH and the vSphere client to a single IP address but I am still able to connect from everywhere. Even denying access to the ports completely does not prevent a connection. Only stopping the SSH demon works, but even then I get "connection refused" and not a timeout.

best regards,

Walter

Hi Anyone has seen this error

The migration was canceled because the amount of changing memory for the virtual machine was greater than the available network bandwidth. Attempt the migration again when the virtual machine is not as busy or more network bandwidth is available.

Failed to start the virtual machine.

Module Migrate power on failed.

vMotion migration [168378376:1391062685293888] failed reading stream completion: Connection closed by remote host, possibly due to timeout

Its a vcops analytic vm move with drs

Thanks

The above is one of the limitation with ESXI 6.

What does this actually mean?

If I have a 4 physical CPU server with 16 cores each, can I assign all processors and cores to a single machine

or am I limited to a multiplier of xCPU with yCores that equals 8?

Thanks!

I understand it in general but I can't comprehend how it exactly utilizes the space. What I meant. For example, I am having a limitation of 256GB for guest VM hard disk. If I am going to create a new hard disk and will indicate it's size as 256GB (MAXIMUM) and will indicate it's provisioning as THIN then will it expand the size of this hard disk if the content of this hard disk will grow more than 256GB? Please explain it to me. Thanks in advance!

I am getting this error:

Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. I am trying to upload a OVF to my host.

I have my ESXi host connected to a switch with VLANS. How do I fix this?