Rawdisk problem on startup

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Hal-
Posts: 1
Joined: 28. Nov 2015, 02:26

Rawdisk problem on startup

Post by Hal- »

I was able to create a vmdk that pointed to a raw disk without a problem.
When I start up the VM however, Windows begins it's normal startup process... I see the Windows 7 logo spinning and so forth.. it says "Starting Windows" and then....

Code: Select all

An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium "ahci-0-0" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error
I've been searching the forums for a solution and the only thing that I have come up with so far was to use IDE instead of SATA. I tried this and the result is Windows generates a BSOD while booting and gets into a boot loop. I should add there is plenty of space on the disks and it's a Windows 7 Host with a Windows 7 VM

Anyone have any pointers on this?

Thanks!
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Rawdisk problem on startup

Post by mpack »

Hal- wrote:I've been searching the forums for a solution and the only thing that I have come up with so far was to use IDE instead of SATA.
You can't have searched very hard. People have been asking about permissions problems accessing raw disks ever since Vista introduced the feature of blocking sector level access to the disk (XP had no protection at all). In Vista the problem has no solution (block can't be turned off), but in Win7 and later it does, provided the disk isn't currently mounted in the host.

Enabling raw access to Win7 and later disks.

p.s. The SATA vs IDE suggestion is not relevant. You have a permissions problem on the host, not incorrect controller drivers in the guest.
Post Reply