Solved

Cannot mount container with ESX as hypervisor

  • 22 June 2021
  • 1 reply
  • 417 views

Hello,

 

I am trying to deploy Nutanix CE on a Dell T7600. It is working fine when using AHV as hypervisor. But when using ESXi, i am not able to mount containers.

I receive error message : 

There was an error while mounting the datastore for storage container 'default-container-11071639353873'


In vmkernel.log i can see :
 

2021-06-22T14:36:46.848Z cpu17:2099496 opID=7bd90377)World: 12556: VC opID 738348c2 maps to vmkernel opID 7bd90377
2021-06-22T14:36:46.848Z cpu17:2099496 opID=7bd90377)NFS: 162: Command: (mount) Server: (192.168.5.2) IP: (192.168.5.2) Path: (/default-container-11071639353873) Label: (default-container-11071639353873) Options: (None)
2021-06-22T14:36:46.848Z cpu17:2099496 opID=7bd90377)StorageApdHandler: 960: APD Handle 732ec6b0-3763e7bf Created with lock[StorageApd-0x4316fd802900]
2021-06-22T14:36:46.849Z cpu17:2099496 opID=7bd90377)SunRPC: 1095: Destroying world 0x201ac2
2021-06-22T14:36:46.849Z cpu17:2099496 opID=7bd90377)SunRPC: 1095: Destroying world 0x201ac3
2021-06-22T14:36:46.850Z cpu17:2099496 opID=7bd90377)SunRPC: 1095: Destroying world 0x201ac4
2021-06-22T14:36:46.850Z cpu17:2099496 opID=7bd90377)NFS: 1526: NFS FSINFO failed with NFS status 10008 (File system timeout (Ok to retry)) on Server (192.168.5.2) Path (/default-container-11071639353873)
2021-06-22T14:36:46.850Z cpu17:2099496 opID=7bd90377)SunRPC: 1095: Destroying world 0x201ac5
2021-06-22T14:36:46.850Z cpu17:2099496 opID=7bd90377)StorageApdHandler: 1046: Freeing APD handle 0x4316fd802900 [732ec6b0-3763e7bf]
2021-06-22T14:36:46.850Z cpu17:2099496 opID=7bd90377)StorageApdHandler: 1130: APD Handle freed!
2021-06-22T14:36:46.850Z cpu17:2099496 opID=7bd90377)NFS: 223: NFS mount 192.168.5.2:/default-container-11071639353873 status: Unable to query remote mount point's attributes
2021-06-22T14:36:53.184Z cpu1:2097972)NMP: nmp_ThrottleLogForDevice:3858: Cmd 0x12 (0x45b9223ffa80, 0) to dev "naa.50014ee6b1450442" on path "vmhba1:C1:T0:L0" Failed:
2021-06-22T14:36:53.184Z cpu1:2097972)NMP: nmp_ThrottleLogForDevice:3866: H:0x2 D:0x0 P:0x0 . Act:EVAL. cmdId.initiator=0x4538cd71bca8 CmdSN 0x1420
2021-06-22T14:36:53.184Z cpu1:2097972)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.50014ee6b1450442" state in doubt; requested fast path state update...
2021-06-22T14:36:53.184Z cpu1:2097972)ScsiDeviceIO: 4219: Cmd(0x45b9223ffa80) 0x12, CmdSN 0x1420 from world 0 to dev "naa.50014ee6b1450442" failed H:0x2 D:0x0 P:0x0
2021-06-22T14:36:53.202Z cpu8:2097580)WARNING: VMW_SATP_LOCAL: satp_local_updatePath:807: Marking path vmhba0:C0:T0:L0 as STANDBY
2021-06-22T14:36:53.202Z cpu8:2097580)vmw_psp_fixed: psp_fixedSelectPathToActivateInt:439: Switching to preferred path vmhba0:C0:T0:L0 in STANDBY state for device mpx.vmhba0:C0:T0:L0.
2021-06-22T14:36:53.202Z cpu8:2097580)WARNING: vmw_psp_fixed: psp_fixedSelectPathToActivateInt:464: Selected current STANDBY path vmhba0:C0:T0:L0 for device mpx.vmhba0:C0:T0:L0 to activate. This may lead to path thrashing.
2021-06-22T14:36:53.202Z cpu8:2097580)vmw_psp_fixed: psp_fixedSelectPathToActivateInt:439: Switching to preferred path vmhba0:C0:T0:L0 in STANDBY state for device mpx.vmhba0:C0:T0:L0.
2021-06-22T14:36:53.202Z cpu8:2097580)WARNING: vmw_psp_fixed: psp_fixedSelectPathToActivateInt:464: Selected current STANDBY path vmhba0:C0:T0:L0 for device mpx.vmhba0:C0:T0:L0 to activate. This may lead to path thrashing.
2021-06-22T14:36:53.202Z cpu8:2097580)WARNING: VMW_SATP_LOCAL: satp_local_tryToActivatePath:1415: Checking TUR on STANDBY path vmhba0:C0:T0:L0

 

Any idea ?
 

icon

Best answer by VincentD 22 June 2021, 19:55

View original

This topic has been closed for comments

1 reply

cluster destroy -force=yes

cluster -s 192.168.1.61  --redundancy_factor=1 create

 

has fixed the issue.

 

was build with  --redundancy_factor=2