ESXi machine: "The parent virtual disk has been modified since the child was created"

One of my virtual servers gives me this error when I start it:

"A general system error occurred: The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child"

These are the files in its folder:

SIA-KB-01-000001-delta.vmdk  SIA-KB-01.vmxf
SIA-KB-01-000001.vmdk        vmware-10.log
SIA-KB-01-Snapshot1.vmsn     vmware-11.log
SIA-KB-01-flat.vmdk          vmware-12.log
SIA-KB-01.nvram              vmware-13.log
SIA-KB-01.vmdk               vmware-14.log
SIA-KB-01.vmsd               vmware-15.log
SIA-KB-01.vmx                vmware.log


Can I do something to fix it?
LVL 1
ltpittAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have you started this VM without the attached snapshot?

You will need to adjust the CID values in the the vmdk files.

See this VMware KB Article

Resolving the CID mismatch error: The parent virtual disk has been modified since the child was created (1007969)

However, there is a possibility of disk corruption, and a corrupt VM or data disk.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ltpittAuthor Commented:
Yes I've tried and sadly it lead me to an unbootable machine (I had backupped before trying so I tried accurately inserting correctly CID values various times)

Sadly yes: the VM was started directly from the main disk instead of using the snapshot disk :(
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you start the VM without the snapshot attached, there is a risk of corruption, when the parent and child do not match.
0
ltpittAuthor Commented:
I was able to get the "original" parent from a backup and, after restoring it, I've started the VM using the snapshot disk: PERFECT! :D
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.