VMware Cloud Community
ben2355
Contributor
Contributor

"An Invalid snapshot configuration was detected" errors taken new snapshot

We were able to one snapshot before make two changes

1: removed one of the two Virtual HD

2: added a new smaller Virtual HD

How when trying to take a snapshot we get "An Invalid snapshot configuration was detected" errors taken new snapshot

also the first isn't showing up in snapshot manager

Thanks

Reply
0 Kudos
9 Replies
ronzo
Hot Shot
Hot Shot

Did you make the hardware changes while you had snapshots?

thanks

ronzo

Reply
0 Kudos
ben2355
Contributor
Contributor

Yes.. we removed a virtual hard drive

then added a smaller one

Reply
0 Kudos
ronzo
Hot Shot
Hot Shot

If you removed and changed the disk config, while the VM had a snapshot, then it probably got confused.

I'm going to have to try that here in our labs....

"I'll be back"

thanks

ron

Reply
0 Kudos
chrisbuzby
Enthusiast
Enthusiast

This is my first post so don't flame me too bad Smiley Wink

okay here are my thoughts on what you did.

Step 1:

Server state to start

2 hard drives (C and D for lack of better names)

Step 2:

Create Snapshot (neither drive was set to independent)

Step 3:

D Drive was deleted (just removed from the vmx? or delete from the server?)

Did you just resize the existing drive or create completely new drive?

So at this point...

The 2 files to modify/be concerned with are the vmx and vmsd (in the server's directory)

I am guessing the vmx was correctly modified as you made changes most likely through the gui. so you can start the machine. But now the vmsd is hosed cause it is looking for drives etc. that do not match up. So if you paste in the vmsd we can probably tell you what it should look like etc...

The easiest if you want to revert to pre snapshot configuration would be to delete both disk from the gui re add the base drives (should be the only 2 you can see from the gui) then delete all the info in the vmsd. I would also delete the "-000001-delta.vmdk"s files and -000001.vmdk

BUT NOTE this will take you back to that first snapshot... going anywhere else is impossible after those files are deleted.

Let us know how it works out...

- Chris

Reply
0 Kudos
nicebud
Enthusiast
Enthusiast

I have the same error...

Dec 13 13:19:35.382: vmx| SNAPSHOT:Unable to find all files for SCO507.vmdk

Dec 13 13:19:35.382: vmx| SNAPSHOT:SnapshotConfigInfoExpandDisks: Error 7

Dec 13 13:19:35.382: vmx| SNAPSHOT:SnapshotConfigInfoExpand: Error 7

I can't recreate the drive because this one is importing from dev team...

this file have any relation with a *-flat.vmdk maybee is the error

Reply
0 Kudos
nextlevel
Contributor
Contributor

Loosing the snapshots may be heavy.

Any way by editing the \*snapshot*.vmsn file to fix it?

I found that there are entries corresponding to the removed drives, but there is also non-ASCII at the end of the file.....

Reply
0 Kudos
nextlevel
Contributor
Contributor

I my case, cloning the machine to a new one let me save the changes in the snapshots and gives me back a functional VM.

Reply
0 Kudos
ben2355
Contributor
Contributor

thank for all the helpful(needed)support

Reply
0 Kudos
billymcc
Contributor
Contributor

How, did you "clone" the servers did you do it though the ESX gui some how?

I know the workstation products have a "clone" feature but ive not seen that in the ESX tools?

Billy

Reply
0 Kudos