Ste
125 Posts
Quote from Ste on June 10, 2022, 4:08 pm
Hi all,
i created this iSCSI disk to use it in vSphere 6.7 cluster, but the datastore creation fails. When I issue these commads in ESX host shell I get en error saying it cannot write on the device. Any idea about the reason ? Everything else is working fine (petasan cluster, network, vsphere hosts,...), also no problem attaching petasan disks to Win2016 server.
[root@EsxTetradeca-6:/dev/disks] partedUtil mklabel /dev/disks/naa.6001405dafc5a1200015000000000000 msdos
Error: Connection timed out during write on /dev/disks/naa.6001405dafc5a1200015000000000000
WriteNewPtable: Unable to commit to device /dev/disks/naa.6001405dafc5a1200015000000000000
The only strange thing is that the Petasan LUN was first detected as Flash disk. After the first fail I forced it to HDD, hoping that was the issue, but I get the same result.
Bye, Ste
Hi all,
i created this iSCSI disk to use it in vSphere 6.7 cluster, but the datastore creation fails. When I issue these commads in ESX host shell I get en error saying it cannot write on the device. Any idea about the reason ? Everything else is working fine (petasan cluster, network, vsphere hosts,...), also no problem attaching petasan disks to Win2016 server.
[root@EsxTetradeca-6:/dev/disks] partedUtil mklabel /dev/disks/naa.6001405dafc5a1200015000000000000 msdos
Error: Connection timed out during write on /dev/disks/naa.6001405dafc5a1200015000000000000
WriteNewPtable: Unable to commit to device /dev/disks/naa.6001405dafc5a1200015000000000000
The only strange thing is that the Petasan LUN was first detected as Flash disk. After the first fail I forced it to HDD, hoping that was the issue, but I get the same result.
Bye, Ste
admin
2,930 Posts
Quote from admin on June 10, 2022, 5:41 pm
Not sure about the cli commands re disk partitioning, but typically you do not need to do this, from the vmware ui you need to add a datastore frm the iscsi disk and it will partition and format the raw disk into a VMFS datastore. We have a guide for this you can download. Is this you first attempt to sue iscsi disks on vmware ? if not, have you been using the cli commands before ? did they work before with older disks ? anything different with this disk ?
Not sure about the cli commands re disk partitioning, but typically you do not need to do this, from the vmware ui you need to add a datastore frm the iscsi disk and it will partition and format the raw disk into a VMFS datastore. We have a guide for this you can download. Is this you first attempt to sue iscsi disks on vmware ? if not, have you been using the cli commands before ? did they work before with older disks ? anything different with this disk ?
Ste
125 Posts
Quote from Ste on June 13, 2022, 8:46 am
Hello, yes I obviously first tried to add the datastore via the vSphere UI (i did it hundred of times...), but i got the generic error "cannot write on the device", that's why I turned to cli to investigate further. Never had problems in adding datastores from iscsi volumes on othen SANs, it even works from another Petasan cluster, but not from this one. How can I find what is wrong here ? Petasan iSCSI volumes works perfectly even when mounted on Windows Server 2016.
PetaSAN version 3.0.1
Thanks, Ste
Hello, yes I obviously first tried to add the datastore via the vSphere UI (i did it hundred of times...), but i got the generic error "cannot write on the device", that's why I turned to cli to investigate further. Never had problems in adding datastores from iscsi volumes on othen SANs, it even works from another Petasan cluster, but not from this one. How can I find what is wrong here ? Petasan iSCSI volumes works perfectly even when mounted on Windows Server 2016.
PetaSAN version 3.0.1
Thanks, Ste
Ste
125 Posts
Quote from Ste on June 13, 2022, 10:43 am
In the meanwhile I updated PetaSAN to 3.1.0, just to check if it might be a version related issue, but the result is exactly the same. Here is a screenshot oh the vSphere web client error:
I also attach the dmesg output from the ESX host: what could be the reason for the iscsi connection to be marked OFFLINE ?
In the meanwhile I updated PetaSAN to 3.1.0, just to check if it might be a version related issue, but the result is exactly the same. Here is a screenshot oh the vSphere web client error:
I also attach the dmesg output from the ESX host: what could be the reason for the iscsi connection to be marked OFFLINE ?
admin
2,930 Posts
Quote from admin on June 13, 2022, 11:55 am
You mean you cannot add a datastore from vSphere UI ? If so i would double check your setup, test in a lab or a different environment.
You mean you cannot add a datastore from vSphere UI ? If so i would double check your setup, test in a lab or a different environment.
Ste
125 Posts
Quote from Ste on June 13, 2022, 12:29 pm
Ok, I try to explain myself better: the vSphere cluster works fine since years, my first petasan cluster works fine exporting iscsi volumes to windows servers, my second petasan cluster works fine with everything, even with vSphere cluster (but I cannot use this one in production with vSphere because it is supposed to serve an Openstack cluster).
Now my question is: is there a way to know why my "first" petasan cluster does not allow the vSphere hosts to create datastore on it ? It seems to be a communication issue, as the iscsi connection goes OFFLINE at a certain point...
Ok, I try to explain myself better: the vSphere cluster works fine since years, my first petasan cluster works fine exporting iscsi volumes to windows servers, my second petasan cluster works fine with everything, even with vSphere cluster (but I cannot use this one in production with vSphere because it is supposed to serve an Openstack cluster).
Now my question is: is there a way to know why my "first" petasan cluster does not allow the vSphere hosts to create datastore on it ? It seems to be a communication issue, as the iscsi connection goes OFFLINE at a certain point...
admin
2,930 Posts
Quote from admin on June 13, 2022, 4:20 pm
Yes this is my point, you have one that works but not the other, we also have a lot of users and do our internal tests without issue. It is likely a setup issue with this specific cluster. i would recheck connections/ips/vmware nic and switch setups..
Yes this is my point, you have one that works but not the other, we also have a lot of users and do our internal tests without issue. It is likely a setup issue with this specific cluster. i would recheck connections/ips/vmware nic and switch setups..
Ste
125 Posts
Quote from Ste on June 17, 2022, 9:13 am
Ok, finally I solved the problem: it was an issue related to port binding and the vSphere hosts version.
Bye
Ok, finally I solved the problem: it was an issue related to port binding and the vSphere hosts version.
Bye
dh0253
15 Posts
Quote from dh0253 on June 26, 2022, 5:43 pm
Ste,
Can you provide some specific information in your resolution? I am running into the same issue with vSphere ESXi 6.7U3. May I ask how you assign the port bindings and/or vSwitch?
Thank you
Ste,
Can you provide some specific information in your resolution? I am running into the same issue with vSphere ESXi 6.7U3. May I ask how you assign the port bindings and/or vSwitch?
Thank you
Ste
125 Posts
Quote from Ste on July 1, 2022, 3:52 pm
Hi dh0253,
the issue was that the 2 vmkernel nics were on the same subnet, and vSphere requires them to be configured with port binding, otherwise their behaviour can be unpredictable. In fact, they worked fine for years with an Equallogic SAN, but had the issue with my first Petasan cluster, while working fine with the second Petasan cluster.
Anyway the official documents to correctly set the configuration are:
Bye, Ste
Hi dh0253,
the issue was that the 2 vmkernel nics were on the same subnet, and vSphere requires them to be configured with port binding, otherwise their behaviour can be unpredictable. In fact, they worked fine for years with an Equallogic SAN, but had the issue with my first Petasan cluster, while working fine with the second Petasan cluster.
Anyway the official documents to correctly set the configuration are:
Bye, Ste
