You are able to power on VMs on some hosts of the cluster but not others.
The datastore where the VM resides is mounted on some hosts but not others
The storage array responded to several commands with a write protect sense code in the past, and you can see in the vmkernel logs of the ESXi host errors as the example below: 2024-09-01T13:05:56.091Z cpu59:33773)NMP: nmp_ThrottleLogForDevice:3333: Cmd 0x89 (0x43be1e8451c0, 81679675) to dev "naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" on path "vmhba1:C0:T0:L2" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x7 0x27 0x0. Act:NONE 2024-09-01T13:05:56.091Z cpu59:33773)In (182) vmkernel: cpu29:2088560 opID=3b99302b) LVM: 17308: Failed to open device naa.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:1 : Read only
Cause
The storage array responded to several commands with a write protect sense code 0x7 0x27 and this condition does not allow the host to mount the datastore.
The condition on the array was temporary, and some hosts were able to mount the datastore.
Resolution
Do a storage rescan on all hosts on the cluster to allow hosts to mount the datastore after the write protect condition is solved.
If any assistance is needed to check/change the presentation mode on the lun, please engage with your storage vendor.