Upgraded to 5, "Unable to connect to Hard Disk 1"

J

JonathanG

Bit poster
I just upgraded to Ver. 5. I'm very sorry I did. I tried to open my VM that ran fine under ver. 4. I get the message "Unable to connect to Hard Disk 1". Here are my facts: Macbook 17" 2.93 GHz, running 10.6.1. Memory 4GB. Parallels Desktop 5 build 5.0.9220. The VM used to run the latest update to Windows XP home. I ran "Cocktail" to check out my Mac. Disk is fine, permissions are fine, etc.

Please Help!
 
Tried that...

Hi,

Okay this just gets stranger every minute.

Let me try to tell you this in order of events so maybe it can help you guys fix the (apparently) plethora of problems with 5...

I tried what you suggested (making new virtual machine based on existing image file) yesterday and the old machine was grayed out and couldn't be selected. I also tried a lot of other things suggested on these forums. I rebooted several times and ran Disk Utility. Nothing worked.

So I gave up and went back in time machine and found an old version of the same machine to see if that would work. It would not. So I went back in time machine and found an even older version of a different VM I used a long time ago. That one worked! I had to update windows and Kapersky and download back up files for my work in there, but it all worked.

Cut to now -- I get your email and decide, out of curiosity, to try making the new machine again following the exact directions (there is still stuff in there I need). But when I started Parallels it opened the VM I couldn't open yesterday! Explain that! All I can figure is that the conversion of my really old VM must have changed some setting somewhere that made it all work.

Strange.

Best,

Jonathan
 
I asked about this error in an existing thred already last week without response: http://forum.parallels.com/showpost.php?p=390428&postcount=36. Probably the smart support folks are serving this forum LiFo?

I checked this threads suggestions but think situation is different for me. My hdd files specs are already an even multiple of the sectors (63), in the logfile the error seems always recorded like this:

11:35:43.228 F /vm:96776:B0289000/ VMFiniMemory completed successfully
11:35:43.230 F /IOLocalDesktop:96776:B0B88000/ Video mem is zero!
11:35:43.230 F /vm:96776:B0289000/ VM successfully stopped.
11:35:43.397 F /vm:96776:B0289000/ Driver opened
11:35:43.398 F /vm:96776:B0289000/ [Profile] Event Loop initialization (driver open) time is 165 msecs
11:35:43.488 F /vm:96776:B0289000/ [Profile] Networking initialization time is 89 msecs
11:35:43.491 F /AbstractFile:96776:B0289000/ flock() supported but errorneous 35
11:35:43.491 F /vdisk:96776:B0289000/ Error locking file /Users/whirsch/Documents/My Virtual Machines/WHU-Mobile-02.pvm/winxp.hdd/winxp.hdd [35]
11:35:43.492 F /vdisk:96776:B0289000/ Couldn't lock disk: 0x80021037
11:35:43.493 F /vdisk:96776:B0289000/ OpenDisk() returned error 0x80021037
11:35:43.494 F /vm:96776:B0289000/ BootableCheck: Failed to open disk image
11:35:43.496 F /vm:96776:B0289000/ IsBootable=0
11:35:43.496 F /vm:96776:B0289000/ VM Compatibility Level is 0xfffffff
11:35:43.497 F /vm:96776:B0289000/ VmInitMemory
11:35:43.498 F /vm:96776:B0289000/ Initing VM Memory
11:35:43.499 F /vm:96776:B0289000/ Loading Monitor
11:35:43.500 F /vm:96776:B0289000/ Monitor Module: 64-bit Assertions: Off
11:35:43.500 F /vm:96776:B0289000/ Using embedded monitor binary.
11:35:43.582 F /ioctl:96776:B0289000/
/mon/ Memory initialized (available: 512 mb, VESA: 256 mb, swap: 768 mb)
/mon/ [HpcMonitorOpen] Opened successfully
/drv/ HypIoctls.c:675 Parallels hypervisor inited (cpus=2 vtx=Enabled vtd=NO svm=NotPresent phy=PAE lin=x32 mem=4096)

The VM works perfectly, just that disk access error is poping up at start of VM several times and later from time to time while VM is up.

Regards,

Winfried
 
Hello,

You were just facing the problem as the correct location of the Harddisk was not selected in the virtual machine. But after you upgraded again, the correct path was selected and your vm started running properly.
 
Not quite the same issue

I had MacBook Pro running Vista and XP under Parallels 4. I routinely used Time Machine to backup the Mac without problem.
On upgrading to Parallels 5, both Vista and XP both work fine but Time Machine stops after 26.16GB (out of 76.6GB) on the nose every time. System log shows "Waiting for index 9,0".
Personal Backup 4X clones Mac OS and XP but tries Vista, fails and then deletes the attempted Vista backup.
Acronis True Image Home backs up XP (from inside XP, of course) but fails to backup Vista.
Parallels will successfully clone Vista but the resulting VM won't boot. "System32/Load.exe missing or corrupt"
Running chkdsk from inside Vista trundles along and then 55% through stage 4 (of 5) reports "Unable to access Hard Disk 1". This report is from Parallels not Widows. How can Windows Vista work flawlessly and yet be unable to access Hard disk 1? It's as if Parallels 5 has encrypted Vista. It knows the key but nothing outside Parallels can access the disk.
I can't go back to Parallels 4 backup since I deleted it expecting a working Parallels 5 setup to backup ok - silly boy!!
 
I have had the same problem for over a week. I've tried everything I have seen in the forums with no success. I get emails from technical support every few days recommending something I have already tried. When I respond I have to wait two to three days to get a response back. In the past I have been impressed by the technical support I have received from Parallels but the support I have received concerning this issue has been dismal.
 
No solution

Hi,

Yes, I received no help either. I had to give up and delete my Vista VM. It is an awful nuisance because on recreating the Vista VM using my original disk, Microsoft now complains that this version of Vista is registered to another computer. Anyway, after wrestling with Microsoft I now have a working Vista VM which Time M/C can handle BUT I'm now stuck with the dreaded "Windows Desktop Manager is not working". I never had that with version 4 (but 4 didn't support Aero, at least not on my MacBook Pro).

I also created a Windows 7 VM (32 bit) which has the same problem.

I would give up totally on Parallels 5 except for the one very useful upgrade (for me, anyway) which is the vastly improved support for DirectX - that's the only aspect of version 5 worth having.

However, I am still looking for support this issue.

Best Regards,
Norman
 
Try This Solution **IT WORKED FOR ME**

I had this exact problem. Vexing, indeed.

Try and move your .pvm file over to \users\shared\parallels and see if that works. IT WORKED FOR ME.

Please note, I also used the parallels image tool to increase drive space, but i don't believe that had anything to do with it.

Please advise if this works for you.
 
Thanks for your offer to help but that was a long time ago. I had to rebuild from scratch.
However, I do have a new problem. I can no longer compress the virtual disk for my Windows 7 virtual machine. The compression program seems to hang for a while and then terminates and reports the same x.y GB.
 
You must log in or register to reply here.
Back
Top