I recently performed an SRM failover and 1 of the 6 VM's in question wouldn't power up after.
On inspection of the .vmx file, I saw that it seemed to lose a mapping of one of it's hard disks. Thankfully I had a copy of the original .vmx so it was relatively easy to identify the correct Disk mapping.
I'm wondering why this may have happened ?
The first few Hard Disks were mapped as follows and were all ok after the SRM,
scsi1.virtualDev = "pvscsi"
scsi1.present = "TRUE"
scsi1:0.deviceType = "scsi-hardDisk"
scsi1:0.fileName = "myservername02_1.vmdk"
scsi1:0.present = "TRUE"
scsi1:1.deviceType = "scsi-hardDisk"
scsi1:1.fileName = "myservername02_2.vmdk"
scsi1:1.present = "TRUE"
scsi1:2.deviceType = "scsi-hardDisk"
scsi1:2.fileName = "myservername02_3.vmdk"
scsi1:2.present = "TRUE"
The last Disk should have been mapped as follows after the SRM
scsi2.virtualDev = "pvscsi"
scsi2.present = "TRUE"
scsi2:0.deviceType = "scsi-hardDisk"
scsi2:0.fileName = "/vmfs/volumes/VMFS_SharedStorage_3154_BPM_LOG1_3696/myservername02/myservername02.vmdk"
scsi2:0.present = "TRUE"
instead it was mapped as
scsi2:0.fileName = "/vmfs/volumes/565fc9d6-4eb63031-9ce1-0025b506011e/myservername02/myservername02.vmdk"
Does anyone know why this may have happened and more importantly, what could be done to prevent it from happening again ?
Unfortunately, a different Team looks after Storage so I'm not able to directly answer any Storage related questions you may have
thanks
