Hi.
Thanks for those who have taken the time to reply.
JD: One of those articles refers to NFS - this is a local raid-5 sas disk array - there is no shared storage on this box. The other seems to relate to just esx 5.0 according to the affected versions list. We're running 4.0i
We're certainly still having a storage issue. However as far as I can see, the hardware is responding as expected. All the sensor lights on the health check page are green, and i have successfully dumped both the partition table and the vmfs header from the disk using hexdump. I must conclude, therefore, that any remaining issues are down to the volume going unexpectedly offline.
It appears to me that the volume itself has been resignatured. The signature 6568d47d-05ab4816-8126-3d11cd68a24c seems to be the disk before the failure and i have read the signature 4bc4a1b9-c664892e-03ad-0025b3ded4d2 from the volume header.
The error VMWARE SCSI Id: Could not get disk id for vmhba0:C0:T0:L0 appears to be a bit strange, as lun 0 is actually the system volume. If this was unavailable then I would not expect the host to boot at all. The volume with the issue is on Lun 1.
Again, i appreciate those who've taken the time to assist thus far.