Hi all!
I have a 2x TrueNAS scale server implementation with iSCSI VMFS6 datastores configured for ESXi. Both servers are running the latest Scale release (22.02 RC2). Due to something completely unrelated to VMWare, I wound up rebuilding one of the servers and re-configured everything from scratch. I configured the iSCSI share identically to the way they were before, and identically to how they are configured on the second server. The ESXi hosts can connect to and read the volumes just fine, but when I try to partition and format with VMFS6, it fails (both through the vSphere GUI and the CLI). Oddly, I can format the partition with VMFS5.
For reference, here is the command I'm trying to execute on one of the hosts:
vmkfstools -C vmfs6 -S Sequoia-1 /vmfs/devices/disks/naa.6589cfc000000848faaf347d35569687:1
create fs deviceName:'/vmfs/devices/disks/naa.6589cfc000000848faaf347d35569687:1', fsShortName:'vmfs6', fsName:'Sequoia-1
deviceFullPath:/dev/disks/naa.6589cfc000000848faaf347d35569687:1 deviceFile:naa.6589cfc000000848faaf347d35569687:1
Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Scanning for VMFS-3/VMFS-5 host activity (512 bytes/HB, 2048 HBs).
Creating vmfs6 file system on "naa.6589cfc000000848faaf347d35569687:1" with blockSize 1048576, unmapGranularity 1048576, unmapPriority default and volume label "Sequoia-1".
Failed to create VMFS on device naa.6589cfc000000848faaf347d35569687:1
Usage: vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: Invalid argument
I've come across some similar issues on the VMWare forums, check out this thread for reference: https://communities.vmware.com/t5/E...see-VMkernel-log-for-more/m-p/2885426#M279552
It looks like most of those issues were related to incorrectly configured iSCSI shares using file-based extents rather than zVol's - which isn't the issue here. As mentioned above, the configuration is identical to the other server that's working just fine. Could this be something specific to the latest TrueNAS release?
Please let me know if there's anything else I can provide. Thank you in advance for any assistance!
I have a 2x TrueNAS scale server implementation with iSCSI VMFS6 datastores configured for ESXi. Both servers are running the latest Scale release (22.02 RC2). Due to something completely unrelated to VMWare, I wound up rebuilding one of the servers and re-configured everything from scratch. I configured the iSCSI share identically to the way they were before, and identically to how they are configured on the second server. The ESXi hosts can connect to and read the volumes just fine, but when I try to partition and format with VMFS6, it fails (both through the vSphere GUI and the CLI). Oddly, I can format the partition with VMFS5.
For reference, here is the command I'm trying to execute on one of the hosts:
vmkfstools -C vmfs6 -S Sequoia-1 /vmfs/devices/disks/naa.6589cfc000000848faaf347d35569687:1
create fs deviceName:'/vmfs/devices/disks/naa.6589cfc000000848faaf347d35569687:1', fsShortName:'vmfs6', fsName:'Sequoia-1
deviceFullPath:/dev/disks/naa.6589cfc000000848faaf347d35569687:1 deviceFile:naa.6589cfc000000848faaf347d35569687:1
Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Scanning for VMFS-3/VMFS-5 host activity (512 bytes/HB, 2048 HBs).
Creating vmfs6 file system on "naa.6589cfc000000848faaf347d35569687:1" with blockSize 1048576, unmapGranularity 1048576, unmapPriority default and volume label "Sequoia-1".
Failed to create VMFS on device naa.6589cfc000000848faaf347d35569687:1
Usage: vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: Invalid argument
I've come across some similar issues on the VMWare forums, check out this thread for reference: https://communities.vmware.com/t5/E...see-VMkernel-log-for-more/m-p/2885426#M279552
It looks like most of those issues were related to incorrectly configured iSCSI shares using file-based extents rather than zVol's - which isn't the issue here. As mentioned above, the configuration is identical to the other server that's working just fine. Could this be something specific to the latest TrueNAS release?
Please let me know if there's anything else I can provide. Thank you in advance for any assistance!