VDD Inaccesible after Blue Screen

[schinken77]

Hey,
I just wanted to install firefox on my virtual machine (win7 64 bit), but while installing i got a blue screen

Kernel_data_inpage error

Well windows automaticly checked the disk for errors and at the end my HDD is fine but the virtual Disk is as said inaccesible.

I attached a screenshot of the Error.

Can it be restored or do i have to really do everything from the beginning.

[mpack]

A bluescreen inside the guest will not cause this. The bluescreen was in the guest right, not the host?

It's a shame that you selected such an obscure disk format for your VM, it's one of the few I don't know the structure of offhand. Why would a Windows Host user select the format from a Mac VM platform? Why didn't you choose VDI, the native and default format?

Anyway, please provide a VM log file: Minimum information needed for assistance.

I should warn that this doesn't look good. "VERR_EOF" implies that it ran out of host disk space or something like that. Or maybe hit a bad sector - it might be worth you running a disk check on the host. Even if it can't boot, it may be possible to attach the hdd to another VM and get any important files off it.

I assume you have no backup.

Edit:  It may also be useful to have a full directory listing of the VM folder and Snapshots subfolder. I particularly want to see file sizes. And report free space.

[loukingjr]

A bluescreen inside the guest will not cause this. The bluescreen was in the guest right, not the host?

It's a shame that you selected such an obscure disk format for your VM, it's one of the few I don't know the structure of offhand. Why would a Windows Host user select the format from a Mac VM platform? Why didn't you choose VDI, the native and default format?

just a guess but I imagine someone gave him a Mac VM which was created in Parallels Desktop without first removing the Parallels guest tools. And he's trying to set it up in VB.

[mpack]

How would the "I was just installing Firefox..." thing fit into that? - implies VM was already working on this host.

[loukingjr]

How would the "I was just installing Firefox..." thing fit into that? - implies VM was already working on this host.

I don't know. I haven't had my coffee yet.

[loukingjr]

technically he did say...

I just wanted to install firefox on my virtual machine

[loukingjr]

How would the "I was just installing Firefox..." thing fit into that? - implies VM was already working on this host.

I think I have a better answer now. Many people are very "loose" with their descriptions of what they are doing or what they have or have not done. As a moderator I would think you have to take them literally. I usually do but often I find that what they were saying isn't what they meant. So on occasion I try and "guess" what they "really" meant.

I don't envy your position at all. I certainly wouldn't want to be a moderator.

[schinken77]

Hey

First of all sorry for the lack of information.
Both my Host and my Guest System is Windows 7 64bit.

However, The bluscreen happend on my hostsystem, not on the virtual one.
Honestly I just run the standart dynamicly allocated HDD as virtual disk,
not that i specificlly changed something, therefore i have no clue what you are talking about with MAC VM

The Virtual Os also worked fine it was pretty recently installed, as said i just were going to install the standart stuff, in this case Firefox.

probably im better of creating a new virtuall Hdd and install the OS again since nothing important has been on there yet.

And here is the information provided by the cmd command.

[loukingjr]

if you do create a new guest you are better off creating a .vdi dynamic hard drive since that is VirtualBox's native format.

[mpack]

It would probably be useful to start again, this time stick with dynamic VDI as the disk format, for a Win7 guest you probably want around a 50GB drive.

I'm still lacking information I asked for re how full the relevant host disk is, what filesystem it uses etc. I also asked for a VM log file - in fact I gave you a link to the information required to help you.

A classic mistake would be to install the VM on a FAT formatted external drive: that will not work if the media tries to grow beyond 4GB.