Parallels 7 snapshots totally jacked up - can't boot

I'm hoping someone can help me. I'm getting pretty irritated. I (for various reasons) recently recovered my .pvm Windows 7 image from Time Machine and Parallels refuses to boot it.

The relevant entries in the Parallels log entries show that it is complaining about a missing .hds image;

Code:

11-08 09:41:37.861 F /vdisk:34687:3b17/ Can't open uid {5fbaabe3-6958-40ff-92a7-860e329aab41} name /Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd/Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds Error 0x80021014
11-08 09:41:37.861 F /AbstractFile:34687:3b17/ Error opening file /Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd/Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds with error 2 in handle pool
11-08 09:41:37.861 F /dimg:34687:3b17/ OpenFile(/Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd/Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds) failed!: 2
11-08 09:41:37.861 F /dimg:34687:3b17/ Init: Can't open file 0x80021014
11-08 09:41:37.861 F /dimg:34687:3b17/ Error initializing for the /Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd/Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds
11-08 09:41:37.861 F /dimg:34687:3b17/ Error 0x80021014 when opening the disk. Releasing image.
11-08 09:41:37.861 F /vdisk:34687:3b17/ OpenDisk() returned error 0x80021014

I also see this;

Code:

11-08 09:41:37.860 F /LocalDevices:34687:3b17/ [hdd::sata:0] Connecting device "/Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd"
11-08 09:41:37.860 F /HddUtils:34687:3b17/ hdd: fops 0
11-08 09:41:37.861 F /AbstractFile:34687:3b17/ Error opening file /Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd/Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds with error 2 in handle pool
11-08 09:41:37.861 F /dimg:34687:3b17/ OpenFile(/Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd/Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds) failed!: 2
11-08 09:41:37.861 F /dimg:34687:3b17/ Init: Can't open file 0x80021014
11-08 09:41:37.861 F /dimg:34687:3b17/ Error initializing for the /Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd/Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds
11-08 09:41:37.861 F /dimg:34687:3b17/ Error 0x80021014 when opening the disk. Releasing image.

So, like a good soldier I opened up a case with Parallels support and have not heard a word from them, not a peep. So, I tried to fix this myself.

I observe that the .hds image being complained about, in fact, does not exist in my .hdd bundle. So, I tried to do a "touch" on the filename, but of course that didn't fix it.

Next I tried to edit my disk descriptor xml file, to remove the offending entries, but then Parallels log shows that snapshots are messed up (duh) and it still does not boot the disk image. Does anyone have any other ideas? I've tried recovering TM backup files going back as far as six months and I still can't find an image file that Parallels will boot, this is getting very frustrating. I think there are bugs/problems in Parallels snapshot management.

Here's the Disk Descriptor XML file;

Code:

<?xml version='1.0' encoding='UTF-8'?>
<Parallels_disk_image Version="1.0">
    <Disk_Parameters>
        <Disk_size>134217728</Disk_size>
        <Cylinders>262144</Cylinders>
        <Heads>16</Heads>
        <Sectors>32</Sectors>
        <Padding>0</Padding>
        <Encryption>
            <Engine>{00000000-0000-0000-0000-000000000000}</Engine>
            <Data></Data>
        </Encryption>
        <UID>{4712a71a-8c04-4545-a86d-1842d3d488f3}</UID>
        <Name>Windows 7 VM-0</Name>
        <Miscellaneous>
            <CompatLevel>level2</CompatLevel>
            <Bootable>1</Bootable>
            <GuestToolsVersion>7.0.15107</GuestToolsVersion>
            <SuspendState>0</SuspendState>
        </Miscellaneous>
    </Disk_Parameters>
    <StorageData>
        <Storage>
            <Start>0</Start>
            <End>134217728</End>
            <Blocksize>512</Blocksize>
            <Image>
                <GUID>{a2d61b71-5924-4ddd-a5cc-a094a7f8cbdb}</GUID>
                <Type>Compressed</Type>
                <File>Windows 7 VM-0.hdd.0.{a2d61b71-5924-4ddd-a5cc-a094a7f8cbdb}.hds</File>
            </Image>
            <Image>
                <GUID>{02a7a02a-f117-45c7-bf57-36cd86adcba3}</GUID>
                <Type>Compressed</Type>
                <File>Windows 7 VM-0.hdd.0.{02a7a02a-f117-45c7-bf57-36cd86adcba3}.hds</File>
            </Image>
            <Image>
                <GUID>{228c5edb-a5d5-43ff-8c41-bb087dd059b3}</GUID>
                <Type>Compressed</Type>
                <File>Windows 7 VM-0.hdd.0.{228c5edb-a5d5-43ff-8c41-bb087dd059b3}.hds</File>
            </Image>
            <Image>
                <GUID>{5fbaabe3-6958-40ff-92a7-860e329aab41}</GUID>
                <Type>Compressed</Type>
                <File>Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds</File>
            </Image>
        </Storage>
    </StorageData>
    <Snapshots>
        <Shot>
            <GUID>{5fbaabe3-6958-40ff-92a7-860e329aab41}</GUID>
            <ParentGUID>{228c5edb-a5d5-43ff-8c41-bb087dd059b3}</ParentGUID>
        </Shot>
        <Shot>
            <GUID>{a2d61b71-5924-4ddd-a5cc-a094a7f8cbdb}</GUID>
            <ParentGUID>{00000000-0000-0000-0000-000000000000}</ParentGUID>
        </Shot>
        <Shot>
            <GUID>{02a7a02a-f117-45c7-bf57-36cd86adcba3}</GUID>
            <ParentGUID>{a2d61b71-5924-4ddd-a5cc-a094a7f8cbdb}</ParentGUID>
        </Shot>
        <Shot>
            <GUID>{228c5edb-a5d5-43ff-8c41-bb087dd059b3}</GUID>
            <ParentGUID>{02a7a02a-f117-45c7-bf57-36cd86adcba3}</ParentGUID>
        </Shot>
    </Snapshots>
</Parallels_disk_image>

And lastly here's an output of the files on disk;

Code:

Jasons-iMac:Hard Drive.hdd Jason$ pwd
/Users/Jason/Documents/Parallels/Windows 7 VM.pvm/Hard Drive.hdd
Jasons-iMac:Hard Drive.hdd Jason$ ls -ltr
total 69987896
-rw-rw-rw-  1 Jason  staff            0 Dec 16  2011 Windows 7 VM-0.hdd
-rw-rwxrwx  1 Jason  staff   2586574848 Sep 28 14:08 Windows 7 VM-0.hdd.0.{02a7a
02a-f117-45c7-bf57-36cd86adcba3}.hds
-rw-rwxrwx  1 Jason  staff  29796859904 Oct  5 10:28 Windows 7 VM-0.hdd.0.{a2d61
b71-5924-4ddd-a5cc-a094a7f8cbdb}.hds
-rw-rwxrwx  1 Jason  staff   3450339328 Oct 15 19:06 Windows 7 VM-0.hdd.0.{228c5
edb-a5d5-43ff-8c41-bb087dd059b3}.hds
-rw-rwxrwx  1 Jason  staff         2634 Oct 30 21:40 DiskDescriptor.xml
-rw-rwxrwx  1 Jason  staff        24064 Oct 30 21:42 Windows 7 VM-0.hdd.drh
-rw-rw-rw-  1 root   staff            0 Nov  8 09:08 Hard Drive.hdd
-rw-r--r--  1 Jason  staff            0 Nov  8 09:41 Windows
-rw-r--r--  1 Jason  staff            0 Nov  8 09:41 VM-0.hdd.0.{5fbaabe3-6958-4
0ff-92a7-860e329aab41}.hds
-rw-r--r--  1 Jason  staff            0 Nov  8 09:41 7

 

Can anyone at least tell me how to configure the .xml files so that I can try to force a boot off of the largest HD file, and just disregard all of the snapshot data?

 

Hi jmpage2, is output for "ls -ltr" valid?
The files in directory do not seemed good.

The broken file is:
VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds

It should be called:
Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds

Parallels couldn't find it and told about it.
Another problem that this file has zero size.
This means that you will able to use your hdd only from a last snapshot state.
Because current data stored within this file was lost somehow.
How it could be done? Why this file contains truncated name and size?

So rename file at first and try to revert to last snapshot then.

If this won't help you, add a new hard disk to VM configuration exactly with same size
(as I see there is default 64GB HDD). The new disk will be called something like
Windows 7 VM-1.hdd. So just copy Windows 7 VM-1.hdd/Windows 7 VM-1.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds file to original hdd directory as
Windows 7 VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds.
I.e. execute
cd /Users/Jason/Documents/Parallels/Windows\ 7\ VM.pvm/
cp Windows\ 7\ VM-1.hdd/Windows\ 7\ VM-1.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds HardDrive.hdd/Windows\ 7\ VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds

From this point I see no problems which can prevent reverting to snapshot.

 

Unfortunately I gave up before I saw your response, and ended up going back to a much older version of the image that did not have the problem.

The ls output you see in my response is after I tried to create the missing snapshot image. Additionally I tried various things I found from other troubleshooting threads including renaming the disk image file and then trying to configure the VM to use that copied/re-named file. All of those efforts failed.

Parallels support also (eventually, after almost 4 business days) contacted me about the issue and seemed to have an idea of what to do to try to resurrect it (involved the exact instructions for editing the xml file for the disc I was looking for here)... but by that time I had restored the very old version and updated my data so it was not worth attempting.

If I had not already blown away that older disk image version I would attempt those procedures and document them for others in a similar predicament.