RESUMING VIRTUAL DISK FAILED (RESTARTING VM)

[signtnight]

Hi. I have converted .TIB to VHD. I dont have problem with new VM and everything works fine. When I restart the VM I get this message. I checked general settings but I couldnt find reason.

[continuum]

You have a vmss-file and a vmsd-file and a snapshot-chain that does not match the current environment in which you want to start the VM.
We need a list of all involved files with date and size and the latest 2 or 3 vmware.logs

[signtnight]

I added latest log files. I hope it helps.

[continuum · Accepted solution]

WS 16.2 has a bug that prevent that vmdks run in nonpersistant mode.
As you use a VHD directly you probably need nonpersistant mode.
Did this VM with the VHD attached as CDrom ever work in a pre WS 16.2 version.
Also you assigned a scsi-buslogic disk to ide1:1 - you should use
scsi0:0.fileName = "path to VHD"

Anyway - for a decent suggestion I need the filelist.

[signtnight]

There is no problem with this in previous version such 15 ?

1.Nonpersistent mode solved problem and restart normally but it will be problem for me not to keep files while power off/restart. 

2.For second suggestion I shouldnt use CDROM?

3.I changed SCSI when creating VM from VHD file but it gives blue screen. You mean different thing?

[signtnight]

As you said earlier version of Vmware doesnt have this problem and it works well. I think it should be updated.

[continuum]

CDroms are born readonly, then live a short and miserable live still in readonly and finally they end their live on the same trashpile with their remote cousins: vmdks in read and write mode.

VHDs are readonly third party objects - normally operating systems assume writeable disks.
Previous versions of WS knew that VHDs are an alien format and used some tricks to work around it.

Your current versions realises that you use a VHD, but it cant deal with it and so uses a homeless error messages that was sleeping under a bridge.
Only thing it got right was figureing out that you use the VHD as IDE1:1 - so it reported the device as readonly and went back to sleep.

So either:
- use WS 15 or better (older)
- assign the VHD to a scsi-port with buslogic controller and check wether that helps.

Still waiting for the filelist ...