Had the same problem, and it was the Change Block Tracking file that was pointing outside the boundaries of the logical disk in the vmdk file. The solution was to disable cbt end re-enable it using the nsrvadp_modify_vm command.
I haven't seen this error before. Have a look in C:\mnt to see if there's anything suspicious in there. Check to see if VSphere Client reports any errors for this VM also.
So has there ever been a permanent solution to this issue? Or do we have to continue to disable / reenable the cbt to get this to work. I ask, simply becasue we are seeing this on, minimum a weekly basis.
ToreE
1 Message
847
0
Posted June 25th, 2012 23:00
Hi,
Had the same problem, and it was the Change Block Tracking file that was pointing outside the boundaries of the logical disk in the vmdk file. The solution was to disable cbt end re-enable it using the nsrvadp_modify_vm command.
Regards
Tore