virtualbox.org

Hello, I've just encountered a problem with my VM that booted fine yesterday, but now wont.

I went to open virtual box, to see that the VM in question said it was inaccessible, I attempted to just remove and re-add again, the very first time I tried this the .vbox file did exist, however it failed to add properly. I can't remember now whether it added it again as inaccessible, or if it just failed straight away. Anyway, after another attempt at re-adding the VM, the .vbox file was no longer present, only a .vbox-prev file.

I tried to copy this file in fear of causing further damage, so I could either rename it to .vbox or something else. Unfortunately this file seems to be corrupt, as when trying to paste it, I receive the error

Code: Select all

An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the code to search for help with this problem.

Error 0x80070571: The disk structure is corrupted and unreadable

I've recently installed a new SSD and have 2 instances of Win 10 now running, with the intention of retiring the old one once the new one is fully set up.
I was running the old one today with the VM running just fine. The VM files are stored on a 3rd hard drive that both installations are able to access. I was attempting to run the VM on the new system when this issue occurred, I can only guess that there's something in the configuration that simply does not like the VM being added and loaded on separate Windows installations which is why this has occurred.

I've attempted to run the CloneVDI program by mpack as I still have what seems to be an in tact .vdi file however the Validation result shows that the source file is not a recognised VDI format.

Is there anything else I can try to fix this? If all else fails I have a .ova export of the machine from some months ago which I can work with, it's just fairly out of date now.
could I maybe use this to import a new VM and use the .vbox file from that? I have no idea what the .vbox file contains so this could be a stupid thing to suggest...

OK so I took the old .ova export and imported that and have a running VM albeit out of date. This is the .vbox file it generated

Code: Select all

<?xml version="1.0"?>
<!--
** DO NOT EDIT THIS FILE.
** If you make changes to this file while any VirtualBox related application
** is running, your changes will be overwritten later, without taking effect.
** Use VBoxManage or the VirtualBox Manager GUI to make changes.
-->
<VirtualBox xmlns="######" version="1.15-windows">
  <Machine uuid="{b3129aea-b239-460d-b9d2-771e9e8e8c8b}" name="CentOS - New" OSType="RedHat_64" snapshotFolder="Snapshots" lastStateChange="2020-06-05T08:32:56Z">
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid="{a736da0e-11ac-4059-8f2b-afeeae2dea0c}" location="24-03-2020-disk001.vdi" format="vdi" type="Normal"/>
      </HardDisks>
    </MediaRegistry>
    <ExtraData>
      <ExtraDataItem name="GUI/LastCloseAction" value="PowerOff"/>
      <ExtraDataItem name="GUI/LastNormalWindowPosition" value="593,363,721,443"/>
      <ExtraDataItem name="GUI/RestrictedRuntimeDevicesMenuActions" value="HardDrives"/>
      <ExtraDataItem name="GUI/RestrictedRuntimeMachineMenuActions" value="SaveState,PowerOff"/>
      <ExtraDataItem name="GUI/StatusBar/IndicatorOrder" value="HardDisks,OpticalDisks,FloppyDisks,Network,USB,SharedFolders,Display,VideoCapture,Features,Mouse,Keyboard"/>
    </ExtraData>
    <Hardware>
      <CPU count="4">
        <PAE enabled="true"/>
        <LongMode enabled="true"/>
        <HardwareVirtExLargePages enabled="true"/>
      </CPU>
      <Memory RAMSize="8000"/>
      <Paravirt provider="Default"/>
      <Display VRAMSize="12"/>
      <VideoCapture screens="1" file="." fps="25"/>
      <RemoteDisplay enabled="false"/>
      <BIOS>
        <IOAPIC enabled="true"/>
      </BIOS>
      <Network>
        <Adapter slot="0" enabled="true" MACAddress="080027A80B7F" cable="true" type="82540EM">
          <DisabledModes>
            <InternalNetwork name="intnet"/>
            <NATNetwork name="NatNetwork"/>
          </DisabledModes>
          <BridgedInterface name="Intel(R) Ethernet Connection (7) I219-V"/>
        </Adapter>
      </Network>
      <LPT>
        <Port slot="1" enabled="false" IOBase="0x378" IRQ="7"/>
      </LPT>
      <AudioAdapter codec="AD1980" driver="DirectSound" enabled="false"/>
      <RTC localOrUTC="UTC"/>
      <Clipboard/>
      <GuestProperties>
        <GuestProperty name="/VirtualBox/HostInfo/GUI/LanguageID" value="en_US" timestamp="1591345976795772100" flags=""/>
        <GuestProperty name="/VirtualBox/HostInfo/VBoxRev" value="137981" timestamp="1591344184210612502" flags="TRANSIENT, RDONLYGUEST"/>
        <GuestProperty name="/VirtualBox/HostInfo/VBoxVer" value="6.1.8" timestamp="1591344184210612500" flags="TRANSIENT, RDONLYGUEST"/>
        <GuestProperty name="/VirtualBox/HostInfo/VBoxVerExt" value="6.1.8" timestamp="1591344184210612501" flags="TRANSIENT, RDONLYGUEST"/>
      </GuestProperties>
    </Hardware>
    <StorageControllers>
      <StorageController name="IDE" type="PIIX4" PortCount="2" useHostIOCache="true" Bootable="true"/>
      <StorageController name="SATA" type="AHCI" PortCount="1" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
        <AttachedDevice type="HardDisk" hotpluggable="false" port="0" device="0">
          <Image uuid="{a736da0e-11ac-4059-8f2b-afeeae2dea0c}"/>
        </AttachedDevice>
      </StorageController>
    </StorageControllers>
  </Machine>
</VirtualBox>

Could I edit this and update things like the uuid's and locations of the hard drive of the broken one? If so, how might I go about getting the uuid from the broken one?

It appears that there is only one disk in the VM, so you can use the guest's Storage settings in the main Virtualbox window to disconnect the imported disk file and attach the old disk file. Don't edit the XML, use the main Virtualbox window.

virtualbox.org

Missing .vbox and potentially corrupt .vbox-prev

Missing .vbox and potentially corrupt .vbox-prev

Re: Missing .vbox and potentially corrupt .vbox-prev

Re: Missing .vbox and potentially corrupt .vbox-prev