3.0 corrupt HDD files

Setting the Ignore Ownership in this volume (Get Info for the external drive), solved my problem. (somehow). It seems that paralells has a problem with permissions even when you can write/read on the drive; in my case it worked with the original user and not with mine (I am admin too). I had to do a Fast User Switch.
When I started ignoring permissions on the drive, it worked again.

Hope this helps.

 

Same problem even though the XML looks fine

I tried to retrieve an older hdd image from backup (this was created with an earlier version of parallels) but after a conversion to the new format that image was also inaccessible.

Any suggestions would be appreciated.

Florian

 

Solved for me

I solved the problem by duplicating my disk and selecting that image in Parallels.

Even though this is annoying, the upside is that your disk images are probably not corrupt, I think this is just a permission problem.

I hope this works for somebody else.

Florian

Ps: the only problem I have now is that my mouse doesn't work in Parallels. Ung.

Pps: Re-installing Parallels tools fixed that.

 

Rescue my files?

All I want is my files. Any way of getting just a few files out of my image? I really don't care for the whole installation - just some files I didn't get a chance to backup

What is worse is that Parallels support won't reply.

I contacted Paralllels support and they recommended I try creating a new disk of the same size. I told them I had tried this more than once without any results. The DiskDescriptor.XML file was completely empty in my case - and creating a new disk of identical size and replacing the GUID with the correct one from my original installation does not work. I still get the corrupt/missing disk image message.

I am not quite sure that creating a 8GB file works identically in versions 2 and 3 - because the actual contents inside the images are very different.

My disk image worked fine in 2.0 and I really regret purchasing and upgrading to 3.0.

 

Will the update fix the problem (which I also am now having), or will it just prevent it from happening again in the future?

 

garneaum,

The update just prevents the new possible file corruption.

andrewh1112,

You were advised to create new 3.0 hdd image exactly to replace your blank diskdescriptor.xml. Please check this KB article - http://kb.parallels.com/entry/459 and see if it helps.

 

And that is exactly what I did and like I said it does not work. I understand what and why I am doing it - but it doesn't work with my image.

Now I just want a few files extracted from the image so I can work - but I won't keep any important files in the image in the future.

 

Well, count me in. I upgraded to the latest build 4560 from 4128 and I got the same problem. I tried the method EXACTLY as described in the suggested workaround listed on the Parallels support site and it still doesn't work. HELP!!!!!!!!!!! Should I try to re-install 4128 and see if it works. I really hope there is some utility in the works to fix this without having to rebuild my WinXP installation. It took me forever to set it up and I had to re-register Windows XP 2 times (calling into their tech support). ~Mike Rench~

 

Well, I've tried now 3 times and no luck. I have been using Parallels for almost a year solid with no issues. I even paid to upgrade from 2.0 to 3.0. Now I can't get to my WinXp installation. Please fix this fast. I know that I can do another reinstall BUT I do not have the hours to dedicate to another WinXP install and updates and reinstall of my Windows apps just because I decided to upgrade.

~Mike Rench~

 

mrench01, hmm.. what concrete problem you have? Your fresh HDD corrupted again? Or Parallels not restored your HDD?

 

Hi Ynot, I would love to hear of a working solution to the corrupted XML-file problem if any.. Or could you maybe suggest a way of retrieving my files from the image?

I wish Parallels would solve this issue quickly or at least talk to us! For my money I would have expected more - and VMWare is seriously looking good to me now.

 

The concrete problem is that I get the message that the winxp.hdd image is corrupted when I try to start the VM. This happened directly after I upgraded to the latest build 4560 from 4128. It never was able to launch my VM of WinXP and it completely crashes my Intel Mac Mini to the point where I have to press and hold the power button to force a reboot. I can't be any more "concrete" or direct about the issue.

I tried the procedure, (KB article - http://kb.parallels.com/entry/459) 3 times of creating a new virtual hdd and copying the .XML file to the one that parallels says is corrupted. I followed this exactly!!! It still won't open the original hard disk image file.

I have a "normal" Parallels installation on a 8Gb partition (that Parallels compacted) image created by Parallels. It is located on the main internal Mac hard drive. I have been using this disk image since last August (almost 1 yr) when I first bought my Intel Mac Mini. I have never had any issues before. It even worked perfectly after upgrading from 2.0 to 3.0 a couple months ago. It was only when I installed the update from 3.0 build 4128 to build 4560 that this became an issue.

My Mac Specs Are (if it helps):

Intel Core Duo Mac Mini, 80Gb Hard Drive, Super Disk, 2Gb RAM.

For the record I still love the product. I consider this a bug and will continue to be an advocate of Parallels. I still need to get this fixed though.

~Mike Rench~

 

mrench01, thanks for that report. Ok, can you send me your DiskDescriptor.xml file and list of files in your HDD bundle via private message? Also send me snapshots.xml from your virtual machine directory.

 

Hi all,
I have upgraded from the initial 3.0 release to Build 4560 2 hours ago and do have the same problems as mrench01 in getting a kernel panic when starting the selected VM:

Using a newly generated DiskDescriptor.XML hasn't solved the problem for me.
A reinstallation of Build 4560 or using backuped images hasn't changed the problem.

Any further help is appreciated.




panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 13=general protection), registers:
CR0: 0x80010033, CR2: 0x3698beb8, CR3: 0x01790000, CR4: 0x000006e0
EAX: 0x25d8bad6, EBX: 0x00000000, ECX: 0x04faba2c, EDX: 0x05d6ef04
CR2: 0x25d8baa4, EBP: 0x25d8bab8, ESI: 0xbfffdee0, EDI: 0x05d6ef04
EFL: 0x00010206, EIP: 0x3f0f8a84, CS: 0x00000004, DS: 0x0000000c

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25d8b908 : 0x128d08 (0x3cc0a4 0x25d8b92c 0x131de5 0x0)
0x25d8b948 : 0x1a4a55 (0x3d24b8 0x1 0xd 0x3d1cc8)
0x25d8ba58 : 0x19aeb4 (0x25d8ba70 0x50 0x400000 0x1992a3)
0x25d8bab8 : 0x3f0f8ab6 (0x25d8bad6 0x25d8badc 0x25d8bba8 0x19aeb4)
0x25d8bae8 : 0x3f0f6923 (0x25d8bb48 0x0 0x0 0x0)
0x25d8bb18 : 0x3f0f6d55 (0x5d6ef04 0xbfffdee0 0x50 0x17f)
0x25d8bbd8 : 0x3f0f74d4 (0x5d6ef04 0x25d8beb8 0x18 0x0)
0x25d8bd38 : 0x3f0f393b (0x5d6ef04 0xc0185401 0x25d8beb8 0x6)
0x25d8bd68 : 0x1f1668 (0xd000000 0xc0185401 0x25d8beb8 0x81)
0x25d8bda8 : 0x1e84a2 (0x25d8bdd0 0x297 0x25d8be08 0x4fa93e8)
0x25d8be08 : 0x1e02a3 (0x5cd5b58 0xc0185401 0x25d8beb8 0x81)
0x25d8be58 : 0x332ac8 (0x52670e0 0xc0185401 0x25d8beb8 0x4fa93e8)
0x25d8be88 : 0x350e24 (0x52670e0 0xc0185401 0x25d8beb8 0x4fa93e8)
0x25d8bf58 : 0x37ad83 (0x4fa93e8 0x4f3e848 0x4f3e88c 0x0)
0x25d8bfc8 : 0x19b28e (0x4f6a724 0x0 0x19e0b5 0x43bb1cc) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffdf78
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x3f0f2000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

Model: Macmini1,1, BootROM MM11.0055.B08, 2 processors, Intel Core Duo, 1.66 GHz, 2 GB
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 1.1.8.5
Network Service: Ethernet (integriert), Ethernet, en0
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: ST98823AS, 74.53 GB
Parallel ATA Device: MATSHITADVD-R UJ-846
USB Device: USB2.0 Hub Controller, NEC Corporation, Up to 480 Mb/sec, 500 mA
USB Device: USB Device, Up to 1.5 Mb/sec, 500 mA
USB Device: Generic USB Hub, Chicony, Up to 12 Mb/sec, 500 mA
USB Device: PFU-65 USB Keyboard, Chicony, Up to 12 Mb/sec, 210 mA
USB Device: Cinergy T², TerraTec GmbH, Up to 480 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
FireWire Device: External HDD Button & Lights, WD, Up to 400 Mb/sec
FireWire Device: External HDD Button & Lights, WD, Up to 400 Mb/sec

 

I'll have to do that when I get home (@ work right now). Also I am not super technical when it comes to this so please bear with me and specify exactly which files you want. Are these the ones located in my home directory user library in the Parallels folder?

Thanks for the help!

~Mike Rench~

 

I now have 2 Macs having the same issue!!!

I just tried to launch build 4560 of Parallels (upgraded last night) on my 2nd Mac (Intel Core 2 Duo, 2Ghz iMac 17") with the exact same result. I get the error that the winxp.hdd image is corrupted and my iMac crashes. I tried the .XML descriptor procedure (again!) for the iMac and no luck. My iMac is for work and now I am really screwed!

I would highly suggest that the 4560 build be somehow suspended or withdrawn until this issue gets resolved. The only reason my Mac Mini and iMac were both upgraded was because I got the pop up message about the update when I launched Parallels. I am suprised that there haven't been more people with this issue.


~Mike Rench~

 

I would just like to point out that Parallels support (Ynot) solved my problem with the corrupted 3.0 image!

From what I understand the problem I had in addition to a blank XML-file was that the snapshot-file also needed to be replaced/created!

 

how did he solve your problem?

I am still having the issue with one of my images having a black diskdescriptor xml and I can't seem to fix it no matter what. It complicates things since the original image has been compressed a few times by parallels and I don't have a duplicate xml to use. Can someone release another solution?

does the new release fix the problem?

This is big I have lost a lot of files because of this!!

Help!

 

Fixed

Ynot kindly helped me with a tiny "dummy" 1MB .hds file to replace the missing snapshot-file inside the .HDD. And then I replaced the blank XML-file with the text below.

I had two .hds-files inside my original .HDD package. One of them was not working/missing. This way I finally got my XP working again

I updated to the latest release (#4560) hoping it would solve the problem - but it does not automatically fix the problem.

P.S. Edited for spelling and clarity.

Code:

<Parallels_disk_image Version="1.0" >
    <Disk_Parameters>
        <Disk_size>16384032</Disk_size>
        <Cylinders>16254</Cylinders>
        <Heads>16</Heads>
        <Sectors>63</Sectors>
        <Miscellaneous/>
    </Disk_Parameters>
    <StorageData>
        <Storage>
            <Start>0</Start>
            <End>16384032</End>
            <Blocksize>63</Blocksize>
            <Image>
                <GUID>{5fbaabe3-6958-40ff-92a7-860e329aab41}</GUID>
                <Type>Compressed</Type>
                <Flags/>
                <File>winxp.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds</File>
            </Image>
            <Image>
                <GUID>{b39970ca-9344-455a-8099-a58d8d650494}</GUID>
                <Type>Compressed</Type>
                <Flags/>
                <File>winxp.hdd.0.{b39970ca-9344-455a-8099-a58d8d650494}.hds</File>
            </Image>
        </Storage>
    </StorageData>
    <Snapshots>
        <Shot>
            <GUID>{5fbaabe3-6958-40ff-92a7-860e329aab41}</GUID>
            <ParentGUID>{b39970ca-9344-455a-8099-a58d8d650494}</ParentGUID>
        </Shot>
        <Shot>
            <GUID>{b39970ca-9344-455a-8099-a58d8d650494}</GUID>
            <ParentGUID>{00000000-0000-0000-0000-000000000000}</ParentGUID>
        </Shot>
    </Snapshots>
</Parallels_disk_image>

 

I don't think I have any snapshots to use. Since I recently upgraded to 3.0, I don't think I took the time to make one on either Mac. I hope this doesn't mean I am out of luck.

I do appreciate the help and I will send those files just as soon as I get home from work. I have to box up my iMac so I can work on it from home (since I now have 2 sick Parallels / Macs to deal with).

Is anyone with Parallels pointing to a Boot Camp partition having this issue or is it only with the .hdd image that Parallels creats? I think if I have to resort to re-installing WinXP then I will do it from a Boot Camp partition. At least I can run it native. I am really hoping that I won't have to do this because of the data loss on my current .hdd images.

~Mike Rench~