ESXi 8.0.3 fail creating datastore on iSCSI LUN on PetaSAN

Ste
133 Posts
March 28, 2025, 5:16 pmQuote from Ste on March 28, 2025, 5:16 pmI was hoping to solve this issue by upgrading PetaSAN to the latest 3.3.0 version, but unfortunately it was not the case. 
I'm experiencing issues when attempting to create VMFS datastores on iSCSI LUNs provisioned by PetaSAN (RBD, replicated pool) using ESXi 8.0.3. The same LUNs can be successfully formatted and used as datastores on ESXi 6.7 hosts, but fail consistently on ESXi 8.0.3 hosts, and this happens on two different PetaSAN 3.3.0 clusters (it happened also with version 3.2.1). Tried different LUN sizes (80GB to 2TB). The Error shown during datastore creation is:
Cannot change the host configuration.
Failed to update disk partitions for /vmfs/devices/disks/naa.6001405dafc5a1200017000000000000
Disk geometry on ESXi 8.0.3 is reported as:
partedUtil getptbl → unknown
Size: 4294967297 sectors (2TB + 512B), invalid geometry
VAAI status on ESXi 8.0.3:
ATS Status: supported
Clone Status: supported
Zero Status: supported
Delete Status: unsupported
I got some hint saying that this could be due to the iSCSI target implementation in PetaSAN, specifically related to:
-
Handling of SCSI-3 Persistent Reservations
-
INQUIRY, REPORT LUNS, and READ CAPACITY command responses
-
Disk geometry returned for RBD-backed LUNs (e.g., 2^32+1 sectors → invalid)
Is this analysis true ? Is there a way to make ESXi 8.0 work with PetaSAN ?
Thanks and bye, Ste
I was hoping to solve this issue by upgrading PetaSAN to the latest 3.3.0 version, but unfortunately it was not the case. 
I'm experiencing issues when attempting to create VMFS datastores on iSCSI LUNs provisioned by PetaSAN (RBD, replicated pool) using ESXi 8.0.3. The same LUNs can be successfully formatted and used as datastores on ESXi 6.7 hosts, but fail consistently on ESXi 8.0.3 hosts, and this happens on two different PetaSAN 3.3.0 clusters (it happened also with version 3.2.1). Tried different LUN sizes (80GB to 2TB). The Error shown during datastore creation is:
Cannot change the host configuration.
Failed to update disk partitions for /vmfs/devices/disks/naa.6001405dafc5a1200017000000000000
Disk geometry on ESXi 8.0.3 is reported as:
partedUtil getptbl → unknown
Size: 4294967297 sectors (2TB + 512B), invalid geometry
VAAI status on ESXi 8.0.3:
ATS Status: supported
Clone Status: supported
Zero Status: supported
Delete Status: unsupported
I got some hint saying that this could be due to the iSCSI target implementation in PetaSAN, specifically related to:
-
Handling of SCSI-3 Persistent Reservations
-
INQUIRY, REPORT LUNS, and READ CAPACITY command responses
-
Disk geometry returned for RBD-backed LUNs (e.g., 2^32+1 sectors → invalid)
Is this analysis true ? Is there a way to make ESXi 8.0 work with PetaSAN ?
Thanks and bye, Ste

admin
2,958 Posts
March 28, 2025, 5:24 pmQuote from admin on March 28, 2025, 5:24 pmwe have users running without version 8 problem.
we have users running without version 8 problem.
Last edited on March 28, 2025, 5:26 pm by admin · #2

admin
2,958 Posts
March 28, 2025, 5:34 pmQuote from admin on March 28, 2025, 5:34 pmcan you try setting Fast-diff on the disks and setting the drives as active/passive on vmware side and test.
can you try setting Fast-diff on the disks and setting the drives as active/passive on vmware side and test.

Ste
133 Posts
March 29, 2025, 3:56 pmQuote from Ste on March 29, 2025, 3:56 pmOk i created a new iscsi disk, with both Trim/Discard and fast-diff enabled, here is the check:
root@petaIBIS01:~# rbd info image-00006 -p Solo_su_HDD
rbd image 'image-00006':
size 1 TiB in 262144 objects
order 22 (4 MiB objects)
snapshot_count: 0
id: 6bc986e6eef722
block_name_prefix: rbd_data.6bc986e6eef722
format: 2
features: layering, exclusive-lock, object-map, fast-diff <<<------
op_features:
flags:
create_timestamp: Sat Mar 29 16:34:39 2025
access_timestamp: Sat Mar 29 16:34:39 2025
modify_timestamp: Sat Mar 29 16:34:39 2025
then tried both MRU (the already configured default option) and fixed multipathing (also tried with both paths available), but i always get the error
Cannot change the host configuration. Failed to update disk partitions for /vmfs/devices/disks/naa.60014053f19b7ff00006000000000000.
I checked also all the advanced option of the iSCSI software adapter of the ESXi hosts, and they are exactly the same for ESXi 6.7 and 8.0.3.
What could be the problem ?
Ok i created a new iscsi disk, with both Trim/Discard and fast-diff enabled, here is the check:
root@petaIBIS01:~# rbd info image-00006 -p Solo_su_HDD
rbd image 'image-00006':
size 1 TiB in 262144 objects
order 22 (4 MiB objects)
snapshot_count: 0
id: 6bc986e6eef722
block_name_prefix: rbd_data.6bc986e6eef722
format: 2
features: layering, exclusive-lock, object-map, fast-diff <<<------
op_features:
flags:
create_timestamp: Sat Mar 29 16:34:39 2025
access_timestamp: Sat Mar 29 16:34:39 2025
modify_timestamp: Sat Mar 29 16:34:39 2025
then tried both MRU (the already configured default option) and fixed multipathing (also tried with both paths available), but i always get the error
Cannot change the host configuration. Failed to update disk partitions for /vmfs/devices/disks/naa.60014053f19b7ff00006000000000000.
I checked also all the advanced option of the iSCSI software adapter of the ESXi hosts, and they are exactly the same for ESXi 6.7 and 8.0.3.
What could be the problem ?
Last edited on March 29, 2025, 4:01 pm by Ste · #4

admin
2,958 Posts
March 30, 2025, 7:10 pmQuote from admin on March 30, 2025, 7:10 pmWe will try to test v 8.0.3 ourselves, probably within the coming month. as i understand we have user running on version 8 with no issues.
We will try to test v 8.0.3 ourselves, probably within the coming month. as i understand we have user running on version 8 with no issues.
ESXi 8.0.3 fail creating datastore on iSCSI LUN on PetaSAN
Ste
133 Posts
Quote from Ste on March 28, 2025, 5:16 pmI was hoping to solve this issue by upgrading PetaSAN to the latest 3.3.0 version, but unfortunately it was not the case.
I'm experiencing issues when attempting to create VMFS datastores on iSCSI LUNs provisioned by PetaSAN (RBD, replicated pool) using ESXi 8.0.3. The same LUNs can be successfully formatted and used as datastores on ESXi 6.7 hosts, but fail consistently on ESXi 8.0.3 hosts, and this happens on two different PetaSAN 3.3.0 clusters (it happened also with version 3.2.1). Tried different LUN sizes (80GB to 2TB). The Error shown during datastore creation is:
Cannot change the host configuration.
Failed to update disk partitions for /vmfs/devices/disks/naa.6001405dafc5a1200017000000000000Disk geometry on ESXi 8.0.3 is reported as:
partedUtil getptbl → unknown
Size: 4294967297 sectors (2TB + 512B), invalid geometryVAAI status on ESXi 8.0.3:
ATS Status: supported
Clone Status: supported
Zero Status: supported
Delete Status: unsupportedI got some hint saying that this could be due to the iSCSI target implementation in PetaSAN, specifically related to:
Handling of SCSI-3 Persistent Reservations
INQUIRY, REPORT LUNS, and READ CAPACITY command responses
Disk geometry returned for RBD-backed LUNs (e.g., 2^32+1 sectors → invalid)
Is this analysis true ? Is there a way to make ESXi 8.0 work with PetaSAN ?
Thanks and bye, Ste
I was hoping to solve this issue by upgrading PetaSAN to the latest 3.3.0 version, but unfortunately it was not the case.
I'm experiencing issues when attempting to create VMFS datastores on iSCSI LUNs provisioned by PetaSAN (RBD, replicated pool) using ESXi 8.0.3. The same LUNs can be successfully formatted and used as datastores on ESXi 6.7 hosts, but fail consistently on ESXi 8.0.3 hosts, and this happens on two different PetaSAN 3.3.0 clusters (it happened also with version 3.2.1). Tried different LUN sizes (80GB to 2TB). The Error shown during datastore creation is:
Cannot change the host configuration.
Failed to update disk partitions for /vmfs/devices/disks/naa.6001405dafc5a1200017000000000000
Disk geometry on ESXi 8.0.3 is reported as:
partedUtil getptbl → unknown
Size: 4294967297 sectors (2TB + 512B), invalid geometry
VAAI status on ESXi 8.0.3:
ATS Status: supported
Clone Status: supported
Zero Status: supported
Delete Status: unsupported
I got some hint saying that this could be due to the iSCSI target implementation in PetaSAN, specifically related to:
-
Handling of SCSI-3 Persistent Reservations
-
INQUIRY, REPORT LUNS, and READ CAPACITY command responses
-
Disk geometry returned for RBD-backed LUNs (e.g., 2^32+1 sectors → invalid)
Is this analysis true ? Is there a way to make ESXi 8.0 work with PetaSAN ?
Thanks and bye, Ste
admin
2,958 Posts
Quote from admin on March 28, 2025, 5:24 pmwe have users running without version 8 problem.
we have users running without version 8 problem.
admin
2,958 Posts
Quote from admin on March 28, 2025, 5:34 pmcan you try setting Fast-diff on the disks and setting the drives as active/passive on vmware side and test.
can you try setting Fast-diff on the disks and setting the drives as active/passive on vmware side and test.
Ste
133 Posts
Quote from Ste on March 29, 2025, 3:56 pmOk i created a new iscsi disk, with both Trim/Discard and fast-diff enabled, here is the check:
root@petaIBIS01:~# rbd info image-00006 -p Solo_su_HDD
rbd image 'image-00006':
size 1 TiB in 262144 objects
order 22 (4 MiB objects)
snapshot_count: 0
id: 6bc986e6eef722
block_name_prefix: rbd_data.6bc986e6eef722
format: 2
features: layering, exclusive-lock, object-map, fast-diff <<<------
op_features:
flags:
create_timestamp: Sat Mar 29 16:34:39 2025
access_timestamp: Sat Mar 29 16:34:39 2025
modify_timestamp: Sat Mar 29 16:34:39 2025then tried both MRU (the already configured default option) and fixed multipathing (also tried with both paths available), but i always get the error
Cannot change the host configuration. Failed to update disk partitions for /vmfs/devices/disks/naa.60014053f19b7ff00006000000000000.
I checked also all the advanced option of the iSCSI software adapter of the ESXi hosts, and they are exactly the same for ESXi 6.7 and 8.0.3.
What could be the problem ?
Ok i created a new iscsi disk, with both Trim/Discard and fast-diff enabled, here is the check:
root@petaIBIS01:~# rbd info image-00006 -p Solo_su_HDD
rbd image 'image-00006':
size 1 TiB in 262144 objects
order 22 (4 MiB objects)
snapshot_count: 0
id: 6bc986e6eef722
block_name_prefix: rbd_data.6bc986e6eef722
format: 2
features: layering, exclusive-lock, object-map, fast-diff <<<------
op_features:
flags:
create_timestamp: Sat Mar 29 16:34:39 2025
access_timestamp: Sat Mar 29 16:34:39 2025
modify_timestamp: Sat Mar 29 16:34:39 2025
then tried both MRU (the already configured default option) and fixed multipathing (also tried with both paths available), but i always get the error
Cannot change the host configuration. Failed to update disk partitions for /vmfs/devices/disks/naa.60014053f19b7ff00006000000000000.
I checked also all the advanced option of the iSCSI software adapter of the ESXi hosts, and they are exactly the same for ESXi 6.7 and 8.0.3.
What could be the problem ?
admin
2,958 Posts
Quote from admin on March 30, 2025, 7:10 pmWe will try to test v 8.0.3 ourselves, probably within the coming month. as i understand we have user running on version 8 with no issues.
We will try to test v 8.0.3 ourselves, probably within the coming month. as i understand we have user running on version 8 with no issues.