5mall5nail5
Dabbler
- Joined
- Apr 29, 2020
- Messages
- 14
Hi all -
I have two ESXi hosts in a cluster that had been pointing to this same physical TrueNAS/FreeNAS box (was FreeNAS, then TrueNAS core, now TrueNAS Scale) which has Chelsio 10 GbE NICs setup in separate VLANs for MPIO and the same with the ESXi hosts each having two vmkernels in matching VLANs as the TrueNAS scale host for MPIO. This was operational for like..... 5 years on various versions of FreeNAS/TrueNAS core. I've now upgraded to TrueNAS Scale and it worked... until I rebooted my hosts.
First, I noticed my rebooted ESXi host came up and the two paths to the iSCSI devices were marked dead. I had setup claimrules targeting TrueNAS iSCSI Disks to uses iops policy and iops=1 for VMware best practive round robin (this worked great in FreeNAS/TrueNAS core). The claimrule persisted after the TrueNAS Scale upgrade, but the hosts had not rebooted so I guess it just reconnected and things were working. Once I rebooted, paths down. I removed the claimrules, rebooted hosts, and I have paths back! I had storage vmotion'd my VMs off from a host yet to be rebooted and got them onto NFS storage outside of TrueNAS Scale. I deleted my zvol, pool, iscsi extents, etc. and rebuilt the storage pool and while I now see two paths to the device, when I go to create a VMFS6 datastore in vCenter I get:
In vmkernel.log on an affected host I see:
I've played with presenting it as 512 logical block size, disable physical block size reporting, and my extents are enabled, etc. I see the device, just cannot work with it - so odd.
Update: I forgot TrueNAS saves boot environments. I simply reverted to my TrueNAS Core environment, of course my pools were offline, recreated those, iSCSI extents/etc. and it works as expected. So something up in TrueNAS Scale with iSCSI and vSphere.
Thanks for reading all!
I have two ESXi hosts in a cluster that had been pointing to this same physical TrueNAS/FreeNAS box (was FreeNAS, then TrueNAS core, now TrueNAS Scale) which has Chelsio 10 GbE NICs setup in separate VLANs for MPIO and the same with the ESXi hosts each having two vmkernels in matching VLANs as the TrueNAS scale host for MPIO. This was operational for like..... 5 years on various versions of FreeNAS/TrueNAS core. I've now upgraded to TrueNAS Scale and it worked... until I rebooted my hosts.
First, I noticed my rebooted ESXi host came up and the two paths to the iSCSI devices were marked dead. I had setup claimrules targeting TrueNAS iSCSI Disks to uses iops policy and iops=1 for VMware best practive round robin (this worked great in FreeNAS/TrueNAS core). The claimrule persisted after the TrueNAS Scale upgrade, but the hosts had not rebooted so I guess it just reconnected and things were working. Once I rebooted, paths down. I removed the claimrules, rebooted hosts, and I have paths back! I had storage vmotion'd my VMs off from a host yet to be rebooted and got them onto NFS storage outside of TrueNAS Scale. I deleted my zvol, pool, iscsi extents, etc. and rebuilt the storage pool and while I now see two paths to the device, when I go to create a VMFS6 datastore in vCenter I get:
I know TrueNAS Scale is still young, but kind of surprised because my storage had been working after the reboot of TrueNAS Core into TrueNAS Scale, but here I am. I have iSCSI working to a synology from the same ESXi hosts and nothing has changed in vmnic/vmkernel/iscsi configuration on the ESXi host side and I have not changed ESXi versions in any manner between it having worked and not.
In vmkernel.log on an affected host I see:
...
I've played with presenting it as 512 logical block size, disable physical block size reporting, and my extents are enabled, etc. I see the device, just cannot work with it - so odd.
Update: I forgot TrueNAS saves boot environments. I simply reverted to my TrueNAS Core environment, of course my pools were offline, recreated those, iSCSI extents/etc. and it works as expected. So something up in TrueNAS Scale with iSCSI and vSphere.
Thanks for reading all!
Last edited:
