VMware Communities
shift7
Contributor
Contributor

Windows 2016 server corrupted no boot - virtual disk error

After upgrading Player and Workstation to v16, my Win10 VM stopped booting. it repeatedly got stuck at "preparing automatic repair"  When I tried to boot to Win10 ISO image (press F8, select CDROM boot ) the machine got stuck at the windows logo.  Together with several misleading fail messages, vm log file had the message "Disklib_GetStorageBlockSizes failed to get storage block sizes"

I ran vmware-vdiskmanager -R  for each of the vmdk files.  like this

vmware-vdiskmanager -R  c:\vm\mycomputer-win10-1-f001.vmdk
vmware-vdiskmanager -R  c:\vm\mycomputer-win10-1-f002.vmdk

The only message displayed was the misleading

vmware vixlib failed to initialize phonehome library

 

Then I created a new VM using existing (and copied) VMDK files in the same fixed allocation configuration. I selected upgrade to V16 compatible format.  The new guest started well with just one Windows message warning of requirement to run auto repair (I ignored). 

So I am thinking I have missed an important instruction when upgrading.

0 Kudos
0 Replies