VirtualBox

Ticket #2541 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

VHD corrupted beypnd repair

Reported by: CrpfBU Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 2.0.4 Keywords:
Cc: Guest type: other
Host type: other

Description

Booting W2K3 + install new additions + shutdown. Takes ages. Reboot: missing registry hives. Mount VHD as secondary drive in virtual pc + boot XP as primary drive. Registry hives appear corrupted. chkdsk:

CHKDSK is verifying files (stage 1 of 3)...
Deleting corrupt attribute record (128, "")
from file record segment 37635.
Deleting corrupt attribute record (128, "")
from file record segment 37636.
Deleting corrupt attribute record (128, "")
from file record segment 37638.
Deleting corrupt attribute record (128, "")
from file record segment 37642.
Deleting corrupt attribute record (128, "")
from file record segment 37650.
Deleting corrupt attribute record (128, "")
from file record segment 37651.
Deleting corrupt attribute record (128, "")
from file record segment 37678.
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Inserting an index entry into index $O of file 25.
Deleting index entry vgapnp.sys in index $I30 of file 37671.
Index verification completed.
CHKDSK is recovering lost files.
Recovering orphaned file Sun (37633) into directory file 3775.
Recovering orphaned file VBoxService.exe (37654) into directory file 29.
Recovering orphaned file VBoxSF.sys (37655) into directory file 31.
Recovering orphaned file VBoxMRXNP.dll (37656) into directory file 29.
Recovering orphaned file VBoxHook.dll (37658) into directory file 29.
Recovering orphaned file 0000 (37661) into directory file 10189.
Recovering orphaned file oem7.inf (37665) into directory file 45.
Recovering orphaned file LastGood (37666) into directory file 28.
Recovering orphaned file oem7.PNF (37670) into directory file 45.
Recovering orphaned file oem8.CAT (37678) into directory file 3433.
Recovering orphaned file oem8.PNF (37679) into directory file 45.
Recovering orphaned file oem9.inf (37684) into directory file 45.
Recovering orphaned file oem9.PNF (37687) into directory file 45.
Recovering orphaned file VBoxMouse.sys (37688) into directory file 31.
Recovering orphaned file Sun xVM VirtualBox Guest Additions (37689) into directo
ry file 9982.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Replacing invalid security id with default security id for file 37656.
Replacing invalid security id with default security id for file 37658.
Security descriptor verification completed.
Inserting data attribute into file 37635.
Inserting data attribute into file 37636.
Inserting data attribute into file 37638.
Inserting data attribute into file 37642.
Inserting data attribute into file 37650.
Inserting data attribute into file 37651.
Inserting data attribute into file 37678.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

Attachments

VBox.log.2 Download (45.1 KB) - added by CrpfBU 5 years ago.
VBox.log.1 Download (43.8 KB) - added by CrpfBU 5 years ago.

Change History

Changed 5 years ago by CrpfBU

Changed 5 years ago by CrpfBU

comment:1 Changed 5 years ago by frank

So, did I understand you correct that you previously created a .vhd file with VirtualPC and VirtualBox corrupted that image?

comment:2 Changed 5 years ago by CrpfBU

This vhd ran fine under virtual pc 2007, build 192. I was able to boot it with vbox 2.0.4 (I was unable to boot it with 2.0.2) + install the vbox additions. After reboot it hang. Then I started another virtual machine (vpc2007) to check the crashed volume... From chkdsk log I gather the additions where at least partially copied (e.g. "Recovering orphaned file VBoxService.exe").

comment:3 Changed 5 years ago by CrpfBU

issue looks like the one posted under  http://www.virtualbox.org/ticket/2585

comment:4 Changed 5 years ago by CrpfBU

Tested again today (starting from a pristine copy of the working vhd) with vbox 2.1.0: after installing additions + reboot windows doesn't find registry. I can't boot even in safe mode so I guess the voume has been corrupted.

comment:5 Changed 5 years ago by CrpfBU

comment:6 Changed 5 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in 2.1.2 afaik. If not please reopen.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use