Unable to connect Hard Disk 0

G

GustavoD

Bit poster
I am trying to upgrade to Parallels 11 from and use my old virtual machine file from Parallels (version 4 or 5, I don't remember).

When I try to run my Win XP virtual machine under Parallels 11, I get this error:

"Unable to connect Hard Disk 0.

A file or device required for the operation of Hard Disk 0 does
not exist or is used by another process, or you have no
permission to access it. The virtual machine will continue
running, but the device will be disconnected"

And then the PC startup process fails with a "No boot device available."

I am aware on another thread about "Unable to connect Hard Disk 1", but in my case it is 0 instead of 1.

I am attaching the log file inside my virtual machine file:
/Users/lmaita/Documents/Parallels/Microsoft Windows XP.pvm/parallels.log

My guess is that the relevant lines in the log are:

01-02 23:46:08.273 F /dimg:6978:28675/ Error 0x80021029 when opening the disk. Releasing image.
01-02 23:46:08.273 F /vdisk:6978:28675/ Can't open uid {d0bb0d50-214d-44d3-bbf2-918ab254923c} name /Users/lmaita/Documents/Parallels/Microsoft Windows XP.pvm/winxp.hdd/winxp.hdd.0.{d0bb0d50-214d-44d3-bbf2-918ab254923c}.hds Error 0x80021029
01-02 23:46:08.274 F /vdisk:6978:28675/ OpenDisk() returned error 0x80021029
01-02 23:46:08.274 F /LocalDevices:6978:28675/ [AppHDD] Can't open requested image [0x80021029].
01-02 23:46:08.277 F /vm:6978:28675/ Sending question = PRL_WARN_UNABLE_OPEN_DEVICE

I would really appreciate if anyone could help me sort this out.

Regards,

Gustavo Delfino
 

Attachments

Hi Gustavo, please let us know the size of the .pvm file and also check if you are able to mount the .pvm file with Parallels mounter. To mount, locate the .pvm file > right click > Mount with Parallels mounter.
 
The pvm file is 76.08 GB (details at http://pasteboard.co/wuW4ox2.png)
When I try to open it with Parallels mounter, I get this message:

"Unable to get write access to the virtual hard disk.
Do you want to open it in the read-only mode?

To be able to modify the hard disk contents, you must
have read-write permissions for its file" ​

When I click OK, I get this other message:

"Parallels Mounter is unable to browse the virtual hard disk.

Make sure that the virtual disk in not corrupt and is not in use by Parallels Desktop or another application"​

This looks like a permissions problem. The .pvm file and most files inside it have permissions read&write for the owner and read only for staff & everyone. The only file with different permissions is VmInfo.pvi. For this file only, the owner is "system" instead of me.

Dhruba, thank you for your help.

Regards,

Gustavo
 
We believe that the virtual machine is corrupted. Have you taken any backups in Time Machine so that we restore it and try opening it?
 
I am trying to restore a TimeMachine backup, but I keep getting a -36 error when restoring the .pvm file. The hard disks involved are fine according to DiskUtility. I will continue trying.
 
GustavoD said:
I am trying to restore a TimeMachine backup, but I keep getting a -36 error when restoring the .pvm file. The hard disks involved are fine according to DiskUtility. I will continue trying.
Click to expand...
Please let us know that if you can retrieve it on a different Mac as well as check for errors on the hard drive of the Mac as well as the external hard drive.
 
I have tried many things like restoring the backup on a different machine and using disk utilities like DiskWarrior 5 and nothing has worked. I think that I will have to start from scratch with a new virtual machine.

Anyway, I would like to document here the specific file inside the .pvm that is giving trouble. I suspect that is is an essential file, but I don't know that for sure. I have used the tmutil command line program to restore the files from TimeMachine as it gives a los move feedback and control:

MacPro51:~ gdelfino$ sudo tmutil restore -v /Volumes/VERBATIM/Backups.backupdb/mac\ mini\ 7/2013-12-03-005439/Macintosh\ HD/Users/lmaita/Documents/Parallels/Microsoft\ Windows\ XP.pvm /Volumes/Archive\ HD/Luisa/
Copying file ./.DS_Store ...
Copying file ./.Microsoft Windows XP.pvs.lock ...
6148 bytes for ./.DS_Store
Copying file ./config.pvs ...
19 bytes for ./.Microsoft Windows XP.pvs.lock
Copying file ./config.pvs.backup ...
20575 bytes for ./config.pvs
Copying file ./parallels.log ...
20575 bytes for ./config.pvs.backup
Copying file ./Snapshots/{39047f8a-3a53-4c00-8ef8-140609e79152}.pvc ...
Copying file ./Snapshots/{39047f8a-3a53-4c00-8ef8-140609e79152}.pvc.backup ...
37616427 bytes for ./parallels.log
Copying file ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.mem ...
13599 bytes for ./Snapshots/{39047f8a-3a53-4c00-8ef8-140609e79152}.pvc
13599 bytes for ./Snapshots/{39047f8a-3a53-4c00-8ef8-140609e79152}.pvc.backup
Copying file ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.png ...
Copying file ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.pvc ...
306556992 bytes for ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.mem
Copying file ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.sav ...
1041356 bytes for ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.png
14010 bytes for ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.pvc
Copying file ./Snapshots/{ca19aa16-a2e4-4704-aa80-43ca6102655f}.pvc ...
Copying file ./Snapshots/{ca19aa16-a2e4-4704-aa80-43ca6102655f}.pvc.backup ...
6680336 bytes for ./Snapshots/{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.sav
13483 bytes for ./Snapshots/{ca19aa16-a2e4-4704-aa80-43ca6102655f}.pvc
Copying file ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.mem ...
13483 bytes for ./Snapshots/{ca19aa16-a2e4-4704-aa80-43ca6102655f}.pvc.backup
Copying file ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.png ...
Copying file ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.pvc ...
465145920 bytes for ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.mem
Copying file ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.sav ...
465040 bytes for ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.png
13972 bytes for ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.pvc
Copying file ./Snapshots.xml ...
Copying file ./statistic.log ...
7252432 bytes for ./Snapshots/{d0bb0d50-214d-44d3-bbf2-918ab254923c}.sav
2126 bytes for ./Snapshots.xml
Copying file ./unattended.fdd ...
1104725 bytes for ./statistic.log
Copying file ./VmInfo.pvi ...
Copying file ./Windows Disks/C ...
Copying file ./Windows Disks/D ...
Copying file ./Windows Disks/E ...
Copying file ./winxp.hdd/DiskDescriptor.xml ...
1474560 bytes for ./unattended.fdd
Copying file ./winxp.hdd/DiskDescriptor.xml.Backup ...
21733 bytes for ./VmInfo.pvi
Copying file ./winxp.hdd/winxp.hdd ...
10 bytes for ./Windows Disks/C
10 bytes for ./Windows Disks/D
10 bytes for ./Windows Disks/E
Copying file ./winxp.hdd/winxp.hdd.0.{39047f8a-3a53-4c00-8ef8-140609e79152}.hds ...
3002 bytes for ./winxp.hdd/DiskDescriptor.xml
3002 bytes for ./winxp.hdd/DiskDescriptor.xml.Backup
0 bytes for ./winxp.hdd/winxp.hdd
Copying file ./winxp.hdd/winxp.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds ...
8112739328 bytes for ./winxp.hdd/winxp.hdd.0.{39047f8a-3a53-4c00-8ef8-140609e79152}.hds
Copying file ./winxp.hdd/winxp.hdd.0.{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.hds ...
8963329536 bytes for ./winxp.hdd/winxp.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds
Copying file ./winxp.hdd/winxp.hdd.0.{ca19aa16-a2e4-4704-aa80-43ca6102655f}.hds ...
16287341056 bytes for ./winxp.hdd/winxp.hdd.0.{afe4dbad-2187-409e-a606-1cf6aa1a96b0}.hds
Copying file ./winxp.hdd/winxp.hdd.0.{d0bb0d50-214d-44d3-bbf2-918ab254923c}.hds ...
26227027456 bytes for ./winxp.hdd/winxp.hdd.0.{ca19aa16-a2e4-4704-aa80-43ca6102655f}.hds
Error (-36) (SrcErr:YES) Copying '/Volumes/VERBATIM/Backups.backupdb/mac mini 7/2013-12-03-005439/Macintosh HD/Users/lmaita/Documents/Parallels/Microsoft Windows XP.pvm/winxp.hdd/winxp.hdd.0.{d0bb0d50-214d-44d3-bbf2-918ab254923c}.hds' to '(null)'
Total copied: 64003.03 MB (67112043704 bytes)
Items copied: 33
MacPro51:~ gdelfino$
 
Since we need to investigate deeper, please email us the issue description along with the file and screenshot to cs(at)parallels(.)com, so we can check it for you.
 
Hello. Is there an update on this thread? I have the latest version of Parallels but am having the same problem as GustavoD.
 
Sorry for the delay in reply - busy week.

The size of the PVM file is 79.57 GB. Thanks for any help you can provide!
 
I cleared the flags and it's still not booting up properly. It gets stuck on "trying to boot from Stata Drive 1". I should mention this whole issue started happening after I tried to delete an old snapshot.
 
Hi, having the same problem after trying to delete 2 previous snapshots. Windows 10 crashed and giving me the same messages as mentioned above. .pvm file size is 33.57 GB. All was working perfectly until I tried deleting the snapshots..
 
Hi,
I have the same situation after cloning a .pvm.
Made a clone from a linked clone. Then, I tried to make a linked clone and I got and error about not having enough space (which I had). Now I have the same problem.
I am running the latest Parallels and macOs versions.
 
ZAFRIRK said:
Hi, having the same problem after trying to delete 2 previous snapshots. Windows 10 crashed and giving me the same messages as mentioned above. .pvm file size is 33.57 GB. All was working perfectly until I tried deleting the snapshots..
Click to expand...
Hello,
Accidentally you might have delete the original snapshot and that resulted with this error. If you've a time machine backup, restore the PVM file and then merge all the snapshots together to reduce the space consumption.
 
Osmin said:
Hi,
I have the same situation after cloning a .pvm.
Made a clone from a linked clone. Then, I tried to make a linked clone and I got and error about not having enough space (which I had). Now I have the same problem.
I am running the latest Parallels and macOs versions.
Click to expand...
Hello @Osmin ,
Please check if you're able to mount the PVM file on finder. If it's not getting mounted, then the virtual hard disk could be damaged or corrupted.
 
Dinesh@Parallels said:
Hello @Osmin ,
Click to expand...
Dinesh@Parallels said:
Please check if you're able to mount the PVM file on finder. If it's not getting mounted, then the virtual hard disk could be damaged or corrupted.
Click to expand...
I followed the solutions posted before in this thread, including mounting the virtual hard disk, but I had the same output as OP.

Since I had no backup for the external hard drive I was working on and no solution seem to have worked, I ended up re-deploying my VM again.
 
You must log in or register to reply here.
Back
Top