Unable to connect to Hard Disk 0

D

DavidVT

Bit poster
One of my users cannot access their Parallels PVM. It seems Windows crashed, and corrected the hdd file. I get the errors shown in the attached screen. I dug in a bit, and used "Show Package Contents" on the PVM and HDD files. In the HDD package, I see two files: Windows 8.1-0.hdd, and a second file (name not noted), that is something like Windows 8.1-0.[bunch of letters and numbers].hds.

The hdd file is 0 bytes, and the hds file is the size the virtual drive should be. I tried moving and renaming the files, and it didn't help, so I put everything back the way it was. I am sure the data is there, and the drive can be restored, but I just can't figure out the process. Has anyone encountered this?

Thank you!
Screen Shot 2016-02-29 at 4.09.28 PM.png Screen Shot 2016-02-29 at 4.09.51 PM.png Screen Shot 2016-02-29 at 4.10.43 PM.png
 
Hi David,
Stop the virtual machine by clicking on Actions(from the Apple menu bar) > Stop.
Quit Parallels Desktop.
Open Disk Utility (Finder>Applications>Utilities) > Select the Mac hard drive > Run Fast Aid.
Reboot the Mac > Try to start Parallels Desktop and Windows.
 
Hello DavidVT,
please generate a technical data/problem report data, sent it to parallels and share its ID here.
Also you can look at parallels.log file inside the VM bundle and guess error code/reason while attempting to access to hdd image.
 
Thank you Dhruba. Before I read your email, I tried removing the virtual machine, saving all files, then restoring the virtual machine. That worked, and I was able to start the Windows partition. Then, I thought to be safe, I would create a snapshot. The snapshot failed, and crashed Windows. I saw your suggestion while I was waiting, so I ran Disk First Aid, and restarted. I'm back to where I started: no hard drive found. Interestingly, the Windows 8.1-0.hdd now seems to be normal and shows as 117GB.

Mmika, the errors I am getting do not seem to give me the option to generate a problem report! However, I accessed the parallels.log file, and found the following.

Thanks to both of you for trying to help.

StartTime: 521778740
03-01 08:24:16.516 F /vm:929:66055/ VCPU1 state(VcpuStateUninitialized): enqueued 'VcpuCmdRun'(1) command
Initializing VCPU #0... done
03-01 08:24:16.516 F /vm:929:66055/ VM state(VmStateRunning): enqueued 'VmLocalEventCpuInitialized'(20033) command
03-01 08:24:16.517 F /vm:929:66055/ VCPU0 state(VcpuStateInitializing): changed to VcpuStateTransition
03-01 08:24:16.517 F /vm:929:66055/ VCPU0 state(VcpuStateTransition): changed to VcpuStateRunning
03-01 08:24:16.517 F /vm:929:66055/ VCPU0 state(VcpuStateRunning): completed 'VcpuCmdRun'(1) command with result 0x0
03-01 08:24:16.517 F /vm:929:66307/ VCPU1 state(VcpuStateUninitialized): changed to VcpuStateInitializing
03-01 08:24:16.517 F /vm:929:31491/ VM state(VmStateRunning): completed 'VmLocalEventCpuInitialized'(20033) command with result 0x80000001
Initializing VCPU #1...
Initializing VCPU #1... done
03-01 08:24:16.517 F /vm:929:66307/ VM state(VmStateRunning): enqueued 'VmLocalEventCpuInitialized'(20033) command
03-01 08:24:16.517 F /vm:929:66307/ VCPU1 state(VcpuStateInitializing): changed to VcpuStateTransition
03-01 08:24:16.517 F /vm:929:66307/ VCPU1 state(VcpuStateTransition): changed to VcpuStateRunning
03-01 08:24:16.517 F /vm:929:31491/ VM state(VmStateRunning): completed 'VmLocalEventCpuInitialized'(20033) command with result 0x80000001
03-01 08:24:16.517 F /vm:929:66307/ VCPU1 state(VcpuStateRunning): completed 'VcpuCmdRun'(1) command with result 0x0
PhyMemRemoveGuestPhyPagesRange(b0) for non-existent range
PhyMemRemoveGuestPhyPagesRange(b8) for non-existent range
PhyMemRemoveGuestPhyPagesRange(b0) for non-existent range
PhyMemRemoveGuestPhyPagesRange(b8) for non-existent range
PhyMemRemoveGuestPhyPagesRange(b0) for non-existent range
PhyMemRemoveGuestPhyPagesRange(b8) for non-existent range
PhyMemRemoveGuestPhyPagesRange(b0) for non-existent range
PhyMemRemoveGuestPhyPagesRange(b8) for non-existent range
[AHCI] Enable Command Queue Acceleration
[SATA0] controller reset
Enable AHCI mode
03-01 08:24:16.602 F /vm:929:66055/ Virtual machine is ready to boot!
03-01 08:24:17.136 F /vm:929:20227/ VM state(VmStateRunning): enqueued 'DspVmStateInfo'(3028) command
03-01 08:24:17.137 F /vm:929:31491/ VM state(VmStateRunning): completed 'DspVmStateInfo'(3028) command with result 0x0
03-01 08:24:17.268 F /IOCommunication:929:68879/ TCP_NODELAY setting failed
03-01 08:24:17.270 W /IOLocalDesktop:929:68879/ DynRes: sendStatesOnAttach. state=0
03-01 08:24:17.324 W DYNRESHOST /vm:929:68879/ Startup information. Host has hidpi display: 0
03-01 08:24:17.498 F /vm:929:20227/ VM state(VmStateRunning): enqueued 'DspCmdVmInitiateDevStateNotifications'(1024) command
03-01 08:24:17.508 F /vm:929:31491/ VM state(VmStateRunning): completed 'DspCmdVmInitiateDevStateNotifications'(1024) command with result 0x0
03-01 08:24:17.910 F /vm:929:20227/ VM state(VmStateRunning): enqueued 'DspEvtNotifyVm'(3014) command
03-01 08:24:17.910 F /vm:929:31491/ VM state(VmStateRunning): completed 'DspEvtNotifyVm'(3014) command with result 0x0
03-01 08:24:50.049 F /vm:929:66055/ Sending question = PRL_WNG_NO_OPERATION_SYSTEM_INSTALLED
 
03-01 11:39:40.310 F /PrlGui:256:5643/ Showing message box. Type = [Warning, PRL_WARN_UNABLE_OPEN_DEVICE]. Id = {2a9541e4-68da-474b-9431-c263c5cccf17}.
03-01 11:39:40.338 F /disp:605:51531/ Recieved event PET_DSP_EVT_VM_MESSAGE (100502) from vm {2a9541e4-68da-474b-9431-c263c5cccf17} (name='Windows 8.1')
03-01 11:39:40.599 F /disp:605:51531/ Recieved event PET_VM_EVT_CEP_ENGINE_WRITE (101601) from vm {2a9541e4-68da-474b-9431-c263c5cccf17} (name='Windows 8.1')
03-01 11:39:40.726 F /disp:605:51531/ Recieved event PET_DSP_EVT_VM_DEBUGGER_EVENT (100083) from vm {2a9541e4-68da-474b-9431-c263c5cccf17} (name='Windows 8.1')
03-01 11:39:40.920 F /prl_client_app:256:5643/ localhost: received PET_DSP_EVT_VM_DEV_STATE_CHANGED. [Hard Disk 0: Disconnected, Image File]
03-01 11:39:40.921 F /prl_client_app:256:5643/ localhost: received event PET_DSP_EVT_VM_MESSAGE, code = [100502]
03-01 11:39:40.921 F /Std:256:5643/ Unknown PRL_RESULT code 0x6
03-01 11:39:40.921 F [MESSAGE_MNG] /prl_client_app:256:5643/ Failed to extract job from event. RC = 80000007
03-01 11:39:40.921 W [MESSAGE_MNG] /PrlGui:256:5643/
Message id: {72ec3de5-840e-47da-82d2-274c470c04ed}
03-01 11:39:40.921 W /PrlGui:256:5643/
Message data:
>> Issuer id = {2a9541e4-68da-474b-9431-c263c5cccf17}
>> Code = PRL_WARN_UNABLE_OPEN_DEVICE
>> Type = Warning
>> Short Message = "Unable to connect Hard Disk 0."
>> Long Message = "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."
>> Details = ""
>> Spontanous = 1
>> Can be hidden = 0
>> Force show = 0
>> Use active = 0
>> Event handle = 64848
>> Answers: [OK] [] []
>> Default button number: 1
>> Message hint: 0x0
>> report generated message: 0
 
I cloned the VM and was able to boot from the clone. I'd still love to fix the issue, so it doesn't recur, but for now I am up and running.
 
You must log in or register to reply here.
Back
Top