virtualbox.org

Hello all,

This is my first topic and write, because I'm going into panic!!

So thank you all for your help, because I have to deliver a job and I have all the information inside a virtual machine unbootable!

But going by parts
1
S.O HOST - Windows 7 Pro 64-bit
S.O GUEST - FREEBSD 9.1
VIRTUALBOX - 4.2.6

2
Until today everything worked properly, but today, the virtual machine decided not to start, given the following error:
"Can not work out diskwe Which are booting from."
"Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0:"

Do not know if it is related, but the last time I used this virtual machine made ​​a critical update required by FREEBSD.

Already tried creating a new virtual machine, starting from the same file VDI, but still gives the same error.

Already goggled a lot, but didn't find any solution.

Just ask your help to be able to put the machine to boot up or to get the desired files extract of VDI.

Grateful for answers.

Windows Host does not seem relevant, so moved to "Linux Guests".

As a workaround, you can easily get files off the drive by attaching the disk to another VM. What filesystem does the disk use?

On the meaning of the error and potential for repairing it - I think you would do better to ask that in a FreeBSD forum. If the problem was triggered by a FreeBSD update then its likely IMHO that VirtualBox is not the problem. Perhaps other FreeBSD users found the same problem.

mpack wrote:As a workaround, you can easily get files off the drive by attaching the disk to another VM. What filesystem does the disk use?

On the meaning of the error and potential for repairing it - I think you would do better to ask that in a FreeBSD forum. If the problem was triggered by a FreeBSD update then its likely IMHO that VirtualBox is not the problem. Perhaps other FreeBSD users found the same problem.

Thanks mpack by the answer!

I´ve created another VM and attached the "old" VDI as a IDE slave and already have access to the files! For me is just fine!!

After this I can conclude that the problem is not with VirtualBox, but with FreeBSD!