Intermittent Error: Unable to connect to Hard Disk 1

E

EQB

Bit poster
Hey guys,

I'm experiencing some odd intermittent errors from PD6. Every now and then (but so far only while my bootcamp VM was running and I wasn't actively using the computer) an error will pop up (in OS X) stating:


Unable to access Hard Disk 1

An error occurred when accessing the hard disk. Error ID: Invalid argument.
Click to expand...


Which I find somewhat odd. The VM itself (Windows 7 64bit bootcamp) doesn't hiccup or error, and everything appears to run normally both before and after the error occurs.

Now, some configuration information:

Physical Machine:

Core i7 15" Macbook Pro 6,2 (late 2010)

8 GB DDR3 Memory (Tested with Memtest 86+ v4, and found to be in good working order)

256 GB Crucial RealSSD C300 CTFDDAC256MAG-1G1 connected internally using an MCE Optibay Adapter
Hybrid GUID/MBR partition table created with Bootcamp Assistant
Partition 1: OS X Snow Leopard running on HFS+ filesystem
Partition 2: Win7 x64 running on NTFS Filesystem

500GB Hitachi HTS725050A9A362 Connected internally in the standard manufacturer location
MBR partition table
Partition 1: OSX Data Partition using HFS+ filesystem
Partition 2: Win Data Partition using NTFS filesystem
Click to expand...


Boy, was that ever a booger to configure too. Didn't realize you couldn't boot to the Windows 7 DVD via a USB optical drive on Macs, so I ended up taking the machine apart twice.

Virtual Machine Configuration:

2 CPU cores
2 GB memory
HDD0: Bootcamp partition on physical machine's SSD
HDD1: Windows Data partition on physical machine's HDD
Click to expand...


The error in the log is as follows:


10-01 22:15:28.058 F /disp:497:6703/ Hardware Configuration was changed !
10-01 22:15:28.059 F /disp:497:6703/ On enter : dev_type = 0 dev_name = event_code = 0
10-01 22:15:28.078 F /disp:497:6703/ On exit : dev_type = 0 dev_name = event_code = 0
10-01 22:15:28.080 F /gui:4153:207/ localhost: received event PET_DSP_EVT_HW_CONFIG_CHANGED, code = [100202]
10-01 22:15:28.081 F /gui:4153:207/ localhost: sending [DspCmdUserGetHostHwInfo] request...
10-01 22:15:28.081 F /disp:497:a8ef/ Processing command 'DspCmdUserGetHostHwInfo' 2051
10-01 22:15:28.107 F /gui:4153:207/ localhost: received result for [DspCmdUserGetHostHwInfo]. RC = [PRL_ERR_SUCCESS]
10-01 22:15:28.115 F /gui:4153:207/ recreate actions for usb device was called
10-01 22:15:28.116 F /gui:4153:207/ recreating actions for usb device
10-01 22:15:45.756 W /hid:4153:207/ [CHIDMacHook::CreateIgnoreActionList] action already exists (vk_code 00000032 vk_mod 00000900 prl_key 00000031 prl_mod 400000f0)
10-01 22:15:45.759 F /hid:4153:207/ [CHIDHostHook] Key action passed here is invalid.
10-01 22:15:45.760 F /hid:4153:207/ [CHIDHostHook] Action exists, but rewrite not allowed.
10-01 22:18:31.108 F /disp:497:9407/ Recieved event PET_DSP_EVT_VM_MESSAGE (100502) from vm {4552ce2e-01db-460d-960a-b71ac83beec2} (name='Windows 7')
10-01 22:18:31.113 F /gui:4153:207/ localhost: received event PET_DSP_EVT_VM_MESSAGE, code = [100502]
10-01 22:18:31.114 F [MESSAGE_MNG] /gui:4153:207/ Failed to extract job from event. RC = 80000007
10-01 22:18:31.114 W [MESSAGE_MNG] /gui:4153:207/
Message id: {be4af848-654a-4457-bd60-da5dd68bd8a7}
10-01 22:18:31.114 W /gui:4153:207/
Message data:
>> Issuer id = {4552ce2e-01db-460d-960a-b71ac83beec2}
>> Code = PRL_WARN_HDD_ERROR
>> Type = Critical
>> Short Message = "Unable to access Hard Disk 1"
>> Long Message = "An error occurred when accessing the hard disk. Error ID: Invalid argument."
>> Details = ""
>> Spontanous = 1
>> Can be hidden = 0
>> Force show = 0
>> Use active = 0
>> Event handle = 67080
>> Answers: [OK] [] []
>> Default button number: 1
..>> Message hint: 0x0
10-01 22:18:31.114 F [MESSAGE_MNG] /gui:4153:207/ Showing message box. Type = [Critical, PRL_WARN_HDD_ERROR]. Id = {4552ce2e-01db-460d-960a-b71ac83beec2}.
10-01 22:18:31.406 F /disp:497:9407/ Recieved event PET_DSP_EVT_VM_MESSAGE (100502) from vm {4552ce2e-01db-460d-960a-b71ac83beec2} (name='Windows 7')
10-01 22:18:31.409 F /gui:4153:207/ localhost: received event PET_DSP_EVT_VM_MESSAGE, code = [100502]
10-01 22:18:31.410 F [MESSAGE_MNG] /gui:4153:207/ Failed to extract job from event. RC = 80000007
10-01 22:18:31.410 W [MESSAGE_MNG] /gui:4153:207/
Message id: {d9e259f8-a735-4af6-96ce-37c970bf0993}
10-01 22:18:31.410 W /gui:4153:207/
Message data:
>> Issuer id = {4552ce2e-01db-460d-960a-b71ac83beec2}
>> Code = PRL_WARN_HDD_ERROR
>> Type = Critical
>> Short Message = "Unable to access Hard Disk 1"
>> Long Message = "An error occurred when accessing the hard disk. Error ID: Invalid argument."
>> Details = ""
>> Spontanous = 1
>> Can be hidden = 0
>> Force show = 0
>> Use active = 0
>> Event handle = 67088
>> Answers: [OK] [] []
>> Default button number: 1
..>> Message hint: 0x0
10-01 22:18:31.410 F [MESSAGE_MNG] /gui:4153:207/ Message should be suspended.
10-01 22:18:31.410 F [MESSAGE_MNG] /gui:4153:207/ Adding message of type PRL_WARN_HDD_ERROR to the message queue...
10-01 22:18:31.410 F [MESSAGE_MNG] /gui:4153:207/ The same message is already shown. The message was merged.
10-01 22:18:53.225 F [MESSAGE_MNG] /gui:4153:207/ Closing message box. Type = [Critical, PRL_WARN_HDD_ERROR]. Id = {4552ce2e-01db-460d-960a-b71ac83beec2}.
10-01 22:18:53.230 W /hid:4153:207/ [CHIDMacHook::CreateIgnoreActionList] action already exists (vk_code 00000032 vk_mod 00000900 prl_key 00000031 prl_mod 400000f0)
10-01 22:18:53.232 F /hid:4153:207/ [CHIDHostHook] Key action passed here is invalid.
10-01 22:18:53.232 F /hid:4153:207/ [CHIDHostHook] Action exists, but rewrite not allowed.
10-01 22:20:28.063 F /disp:497:6703/ Hardware Configuration was changed !
10-01 22:20:28.063 F /disp:497:6703/ On enter : dev_type = 0 dev_name = event_code = 0
10-01 22:20:28.087 F /disp:497:6703/ On exit : dev_type = 0 dev_name = event_code = 0
10-01 22:20:28.088 F /gui:4153:207/ localhost: received event PET_DSP_EVT_HW_CONFIG_CHANGED, code = [100202]
10-01 22:20:28.089 F /gui:4153:207/ localhost: sending [DspCmdUserGetHostHwInfo] request...
10-01 22:20:28.089 F /disp:497:a8ef/ Processing command 'DspCmdUserGetHostHwInfo' 2051
10-01 22:20:28.114 F /gui:4153:207/ localhost: received result for [DspCmdUserGetHostHwInfo]. RC = [PRL_ERR_SUCCESS]
10-01 22:20:28.121 F /gui:4153:207/ recreate actions for usb device was called
10-01 22:20:28.122 F /gui:4153:207/ recreating actions for usb device
Click to expand...

There are several more of the 100202 errors repeating over and over again.
 
Last edited:
I also get the error in Parallels 6.

There are two threads on this topic, but the more the merrier!

I don't think it is version related, as you get this in P4, and I in P6.
 
Still getting error

Hi guys, what is the expected response time for an issue here?

I am still getting an intermittent dialog box coming up from parallels 6 on MAC OS X.

It does not seem to do anything but display the dialog, is there a workaround for this.

I can use all features of the parallels product, its just this annoying dialog box.

Regards,
 
Does the partitions listed in the MBR match the partitions listed in the GPT? Use the fdisk and gpt commands to find out. If gpt gives a bogus map error then they probably don't match. Use the gdisk command in that case.

http://forum.parallels.com/showthread.php?t=88729
http://forum.parallels.com/showthread.php?p=426817

If you restarted your Mac since the last time you ran the virtual machine, and you have more than one hard disk, then you might need to reselect the hard disk in the virtual machine's hardware configuration hard disk settings.
 
I got a suspicious error after the sudo gpt -r show -l /dev/disk0 command:

gpt show: /dev/disk0: Suspicious MBR at sector 0

start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
 
Suspicious MBR is normal for Boot Camp disks because they are formatted as GUID partition table (gpt) but have a hybrid MBR so that Windows can use the partitions. Please post the entire results of the commands (diskutil, gpt, fdisk, gdisk) here.
 
Output of gpt and fdisk command

Computername:~ username$

sudo gpt -r show -l /dev/disk0
gpt show: /dev/disk0: Suspicious MBR at sector 0
start size index contents
0 1 MBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - "EFI system partition"
409640 303824896 2 GPT part - "Customer"
304234536 264152
304498688 86222848 3 GPT part - "Untitled"
390721536 399
390721935 32 Sec GPT table
390721967 1 Sec GPT header

Computername:~ username$ sudo fdisk /dev/rdisk0
Disk: /dev/rdisk0 geometry: 24321/255/63 [390721968 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 303824896] HFS+
*3: 07 1023 254 63 - 1023 254 63 [ 304498688 - 86222848] HPFS/QNX/AUX
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
 
I see no problems in your GPT or MBR.

You could try recreating the hard disk settings. Remove Hard Disk 1 from the configuration. Then add a new Hard Disk 1 and point it at the Boot Camp disk.

Does your parallels.log contain the same "Invalid argument" errors that EQB found?
/Library/Logs/parallels.log

The virtual machine .pvm file has it's own parallels.log file at:
~/Documents/Parallels/YourVirtualMachine.pvm/parallels.log

Maybe you can turn on "Use detailed log messages" in Parallels Desktop -> Preferences -> Advanced, reproduce the error, note the time that the error message appeared, use the "Report a Problem" menu option in the Help menu when the error message appears, send the report to Parallels, then examine the log files. Find the latest error message in /Library/Logs/parallels.log that occurred at the time you noted, then look in the virtual machine's log file for stuff that occurred just before time.
 
Still hard disk not found error

I deleted and added the hard disk again, but still no luck.

The logfile shows:

>> Issuer id = {2c9d9436-0b21-4ba9-8c3e-09ba7a5d7162}
>> Code = PRL_WARN_HDD_ERROR
>> Type = Critical
>> Short Message = "Unable to access Hard Disk 1"
>> Long Message = "An error occurred when accessing the hard disk. Error ID: Invalid argument."

What makes me think:

Everytime I startup Windows 7 I got the error it was not correctly shut down. I can't imagine why that is...

Because of that access issue?? I didn't get that message when I rebooted my mac and started Windows only (so not into the virtual environment of Parallels)
 
have the same solid state drive as EQB, so maybe it has an issue with that particular ssd. (I also get the popup intermittently)
 
You must log in or register to reply here.
Back
Top