confused Virtual Disks

[ma_js]

Hi @ll,

as I run out of diskspace in June, I moved the *.vmdk to an other disk (maybe at least, I thought I had moved it ...)
I'm quite sure, that it worked and the *.vmdk was updatet in September an existing *.vdi was not updatet
Before deleting the original one (on c;) I tried to export with *.ova - that didn't work (cancelled with an error I can't remember). But for some other things I needed this diskspace and deletet the whole directory containing the VMs)

Now - what do I have:

• the *.vmdk within the data I now need
• backup of the deleted machine (as a copy)
• an old *.ova (not containing the data, which was created on end of August)

Now trying to assamble the VM with the *.vmdk it results in error: 0x800040005 (VERR_UNRESOLVED_ERROR) AHCI: Failed to attach drive to Port0)

Recent Logfile is attached

I am not native english - pls apologize

Thanks for Help

[scottgus1]

As I see, you're trying to boot from the .vmdk:

00:00:07.932312 [/Devices/ahci/0/LUN#0/Config/] (level 5)
00:00:07.932316   Path       <string>  = "D:\VMs\sxs_WIN7-bkp_Kopie.vmdk" (cb=31)

The errors are complaining:

00:00:16.349974 VMSetError: VD: error VERR_UNRESOLVED_ERROR opening image file 'D:\VMs\sxs_WIN7-bkp_Kopie.vmdk'

The file cannot be opened. It has apparently got corrupted.

FWIW the "WIN7" implies this guest was a Windows 7 guest. You're booting it as Windows 10 with EFI:

00:00:07.881226 Guest OS type: 'Windows10_64'
00:00:07.932366 [/Devices/efi/] (level 2)

Are you sure this is correct?

FWIW2: the .vmdk is not the guest. The entire guest folder is the guest. The guest folder contain's a .vbox file, which is the recipe of the guest and tells Virtualbox what "motherboard" to use. Without the "motherboard", all you have is a disk. Can't run a computer with just a disk. See Moving a VM for future moves.

-backup of the deleted machine (as a copy)

This may be your saving grace. What, precisely, is in this backup?

[ma_js]

Hi Scottgus

the directory contains :
sxs_win7-bkp.vbox
sxs_win7-bkp.vbox-prev
sxs_win7-bkp.vdi (from May)
and directory named Logs

I just copied the .vbox again - changed now nothing - an started the VM again (failed). This .log is named .log_now

the last log from the backup is named .log_bkup

THX a lot

[scottgus1]

OK, the backup seems to contain the entire guest. Copy that backup to a suitable hard drive in your PC. Double-click the new copy's .vbox file. This will register the guest with your Virtualbox.

If you run into any errors registering this new guest, post the exact error message you get. If you see a Copy button in the error message, use it to copy and post the error message as text. If the error message must be a picture, use the forum's Upload Attachment tab. Crop & resize the picture to get under the forum's 128kB size limit. PNG is best.

Once we get the guest registered and running, we can try attaching the old .vmdk as a second drive and see if the guest will boot.

[ma_js]

Hi again,

first: could not ... because same machine name already exist
deleted the "old" from manager
also removed the old *.vdmk in virtualdiskmgr.

the result starting th vm is

Für die virtuelle Maschine sxs_WIN7-bkp konnte keine neue Sitzung eröffnet werden.

Could not open the medium 'D:\VMs\sxs_WIN7-bkp_Kopie.vmdk'.

VD: error VERR_FILE_NOT_FOUND opening image file 'D:\VMs\sxs_WIN7-bkp_Kopie.vmdk' (VERR_FILE_NOT_FOUND).

Fehlercode:E_FAIL (0x80004005)
Komponente:MediumWrap
Interface:IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

BTW: D:\VMs\sxs_WIN7-bkp_***Kopie***.vmdk (the name is different - is it just a filename or does this matter?

[scottgus1]

first: could not ... because same machine name already exist

Yes, you can't have two machines with the same name.

is it just a filename or does this matter?

Yes the file name does matter.

Do you see the difference in these two quotes?

first: could not ... because same machine name already exist
deleted the "old" from manager
also removed the old *.vdmk in virtualdiskmgr.

If you run into any errors registering this new guest, post the exact error message you get.

You did not post the exact error message ('same machine name already exist' is hardly an exact error message). And you started doing things before we told you what to do. Not a good idea, because now we don't know the state of your Virtualbox or what's going on, and we can't help.

Please run this command in a command prompt window:

"C:\Program Files\Oracle\VirtualBox\vboxmanage" list vms

Copy and post the command output as text, in

Code: Select all

 tags here on the forum.

Also, zip and post the backup's .vbox file, using Upload Attachment.

[ma_js]

sorry...

here's the output

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\vi3admin>c:\programme\oracle\virtualbox\vboxmanage list vms
"VirtBox_sxs-vmINT" {9aaa25da-cc30-4146-9b13-7e4b0827bf77}
"sxs_WIN7-bkp" {515f803a-e1b3-462e-80c8-932b403dd62e}

the two files attached - one (now) is out from the Virtaul-Machine-directory
(ORIBKP) is the original Copy from July

thx a lot

[ma_js]

... I'm really in trouble

[socratis]

Let's focus on the VMDK first, that's the most important part, because it contains your data. And if it's the data that you're looking after you can forget about recreating your original VM for the moment. You can always create a new VM and attach that VMDK as a second virtual hard drive and retrieve it from there.

So, your VMDK is the "D:\VMs\sxs_WIN7-bkp_Kopie.vmdk" one? If yes, then post the output of the command:

• 
  VBoxManage showmediuminfo "D:\VMs\sxs_WIN7-bkp_Kopie.vmdk"

If your VMDK is corrupt, there's no point in recreating your VM, you can't build on something that's corrupt to begin with...

[ma_js]

Hi and thx so far...

here's the output:

C:\Programme\oracle\VirtualBox>vboxmanage showmediuminfo "d:\temp\sxs_win7-bkp\s
xs_win7-bkp_kopie.vmdk
UUID:           fa2d2dae-4739-4225-baa3-86664eed4efa
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       d:\temp\sxs_win7-bkp\sxs_win7-bkp_kopie.vmdk
Storage format: VMDK
Format variant: dynamic default
Capacity:       122880 MBytes
Size on disk:   28992 MBytes
Encryption:     disabled

C:\Programme\oracle\VirtualBox>

... doesn't look so bad...

[scottgus1]

That output doesn't look bad to me either.

Try a fresh test install of a new Windows guest. Don't bother activating, this is a throw-away guest. After the OS is installed, shut down the test guest, add the .vmdk as a second drive, and restart the guest. See if your data is on it. Note that if the OS asks to format the disk, something is wrong, don't format.

If you can see and access your data, and you don't need the original VM, then you're good to go.

If you can't see the data, try Mpack's CloneVDI and see if you can make a .vdi clone of the .vmdk. CloneVDI can check for and possibly repair some issues with the drive file. Then see if the test guest can access the clone.

[ma_js]

... bad news.....

Source Drive Information
Validation Result: Source file corrupt - block map contains errors

Do you have some magic?

[scottgus1]

Where did that error message come from?

[ma_js]

If you can't see the data, try Mpack's CloneVDI and see if you can make a .vdi clone of the .vmdk. CloneVDI can check for and possibly repair some issues with the drive file. Then see if the test guest can access the clone.

I've got a running Win10 Guest - this was the first ... how do you say, when creating an .OVA file ... I can't attach the .vmdk either to this one

is there any tool, I can treat the VMDK-file with?

scrennshot

2019-11-11 08_24_15Clonevdi.png (13.61 KiB) Viewed 4492 times

[scottgus1]

If CloneVDI can't do anything with that .vmdk, then I don't think anything can. Sorry to have to say it, but I think your data is gone. Others may have ideas though. I would try asking Mpack on his CloneVDI post, put a link to this thread. He may have an idea.

For the future, when making a copy of important files, verify the backup before deleting the source. The FC command in a command window is good for this. I also like Winmerge for Windows PCs for confirming backups of whole folder chains.