virtualbox.org

Hello

We are working on virtual guest machine after that machine was stuck suddenly.
i went to virtual box console tried to start but machine was not up.

After that i tried a clone but getting the error.Guest machine disk shown inaccessible.rest of the others machines are working fine on same machine.

We faced the same problem many time. please let me know if you have any solution.

Look in the folder that has the guest and you should see *.vbox and *.vbox-prev.
See if the *.vbox file is empty or near empty. If so the replace it with the *.vbox-prev and see if it will boot.

Dear

Both files are same size.

root@Virtual4:~/VirtualBox VMs/KNOWLUS-Testing (10.60.20.37)# du -sh KNOWLUS-Testing\ \(10.60.20.37\).vbox
8.0K KNOWLUS-Testing (10.60.20.37).vbox
root@Virtual4:~/VirtualBox VMs/KNOWLUS-Testing (10.60.20.37)# du -sh KNOWLUS-Testing\ \(10.60.20.37\).vbox-prev
8.0K KNOWLUS-Testing (10.60.20.37).vbox-prev
root@Virtual4:~/VirtualBox VMs/KNOWLUS-Testing (10.60.20.37)#

Frankly, I think that a much better description of this problem is needed. Meaning precise error messages. Also post the .vbox file and a directory list of the VM folder and its Snapshots subfolder. (Post files as .zip or similar compressed attachment pls).

HI

Please find the location of Virtual disk and also find the the vbox and prev box files. kadmin@Virtual4:~/VirtualBox VMs/KNOWLUS-Testing (10.60.20.37)$ ls -al
total 50759316
drwxrwxr-x 3 kadmin kadmin 4096 2013-01-10 20:05 .
drwx------ 7 kadmin kadmin 4096 2013-01-10 18:43 ..
-rwxrwxr-x 1 kadmin kadmin 7078 2013-01-08 17:10 KNOWLUS-Testing (10.60.20.37).vbox
-rwxrwxr-x 1 kadmin kadmin 7078 2013-01-08 17:00 KNOWLUS-Testing (10.60.20.37).vbox-prev
-rwxrwxr-x 1 kadmin kadmin 29454630912 2013-01-08 16:12 KNOWLUS-Testing_1.vmdk
-rwxrwxr-x 1 kadmin kadmin 22531801088 2012-12-11 16:53 KNOWLUS-Testing.vmdk
drwxrwxr-x 2 kadmin kadmin 4096 2013-01-08 16:50 Logs

Thanks, now all we need is the precise error message. If the "inaccessible" legend is the only message then please post a picture of it. I want to know if it's the VM or its disks which can't be accessed, e.g. I'm not an expert on Linux hosts, but does "kadmin" in the directory listing mean that you need admin rights to access this folder?

kadmin is sudoers user they have all admin right .Rest of all guest machine is working with kadmin rights.

Please find the attachment of log details:

When we open the guest host got the following error:
Failed to open a session for the virtual machine KNOWLUS-Testing (10.60.20.37).

Could not open the medium '/home/kadmin/VirtualBox VMs/KNOWLUS-Testing (10.60.20.37)/KNOWLUS-Testing_1.vmdk'.

VMDK: inconsistency between grain table and backup grain table in '/home/kadmin/VirtualBox VMs/KNOWLUS-Testing (10.60.20.37)/KNOWLUS-Testing_1.vmdk' (VERR_VD_VMDK_INVALID_HEADER).

VD: error VERR_VD_VMDK_INVALID_HEADER opening image file '/home/kadmin/VirtualBox VMs/KNOWLUS-Testing (10.60.20.37)/KNOWLUS-Testing_1.vmdk' (VERR_VD_VMDK_INVALID_HEADER).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Medium
Interface: IMedium {29989373-b111-4654-8493-2e1176cba890}


Vbox.log details::

VirtualBox VM 4.2.4 r81684 linux.amd64 (Oct 26 2012 18:51:18) release log
00:00:00.472864 Log opened 2013-01-12T06:26:47.223180000Z
00:00:00.472869 OS Product: Linux
00:00:00.472871 OS Release: 2.6.32-21-generic
00:00:00.472873 OS Version: #32-Ubuntu SMP Fri Apr 16 08:09:38 UTC 2010
00:00:00.472902 DMI Product Name:
00:00:00.472934 DMI Product Version:
00:00:00.472946 Host RAM: 7927MB total, 3404MB available
00:00:00.472950 Executable: /usr/lib/virtualbox/VirtualBox
00:00:00.472951 Process ID: 2803
00:00:00.472953 Package type: LINUX_64BITS_UBUNTU_10_04
00:00:00.518439 Installed Extension Packs:
00:00:00.518452 None installed!
00:00:00.525367 Using XKB for keycode to scan code conversion
00:00:00.620100 Power up failed (vrc=VINF_SUCCESS, rc=NS_ERROR_FAILURE (0X80004005))

Ah ok, the precise error message makes all the difference: it's saying that your VMDK is corrupted. You need to replace it from a good backup. I see that there was another VMDK in the folder, perhaps you ran out of disk space while cloning a VMDK.

Hi Mpack

what is the reason VMDK is corrupted.Our disk was not run out from space.we have no backup of VDMK.when disk was stuck i had make same clone for the same.
After that i run and i got the same probelm.

If any solution please let me know.

we have faced the same problem many time.I think virual box is unused in production enviroment .We should go for the another virtualzation.

Sorry, I was not there to see how or when it happened. I can only tell you what the error message indicates now.