Can't access hard drive after upgrade to build 18608

  • Thread starter Thread starter Parallels User
  • Start date Start date
P

Parallels User

Anybody else find that their virtual machine died upon upgrade to Build 18608?

After I upgraded, my Windows XP VM can no longer access its hard drive. I get the error message: "An error occurred while accessing the Hard Disk 0 used by <virtual machine name>. ... Error ID: PRL_ERR_DISK_READ_FAILED (80021029), errno=35 (Resource temporarily unavailable)."

I couldn't find any reference to errno 35 in these forums.
 
I have the same problem after I upgraded to Build 18608.
I am working with Windows 7
I get the message " no boot device is available"

jjchoi said:
Anybody else find that their virtual machine died upon upgrade to Build 18608?

After I upgraded, my Windows XP VM can no longer access its hard drive. I get the error message: "An error occurred while accessing the Hard Disk 0 used by <virtual machine name>. ... Error ID: PRL_ERR_DISK_READ_FAILED (80021029), errno=35 (Resource temporarily unavailable)."

I couldn't find any reference to errno 35 in these forums.
Click to expand...
 
At least for me, it's not clear that this is Build 18608's fault. Shortly after the upgrade, my Macbook Air's SSD hard drive started acting erratically, and then OS X refused to even boot. I tried reinstalling the OS, but the installer couldn't find the hard drive, and my Mac couldn't even erase the drive. So I think my problems came from a dying hard drive, although I suppose one can't rule out the possibility that 18608 killed my hard drive!
 
My Hard drive works without any problem, and fortunately OS X work without any problem.
But Parallels Desktop doens'nt find the Virtual disk...


jjchoi said:
At least for me, it's not clear that this is Build 18608's fault. Shortly after the upgrade, my Macbook Air's SSD hard drive started acting erratically, and then OS X refused to even boot. I tried reinstalling the OS, but the installer couldn't find the hard drive, and my Mac couldn't even erase the drive. So I think my problems came from a dying hard drive, although I suppose one can't rule out the possibility that 18608 killed my hard drive!
Click to expand...
 
I had contact with The Parallels Support Team, who did take control of my Mac to fix the problem.
The only solution finded was to recuperate a virtual disk copy from a Time Machine back-up...
And it works.
 
You must log in or register to reply here.
Back
Top