Encryption process died at 1% on a kali guest and now no bootable medium can be found
Posted: 14. Feb 2017, 18:24
Hello Oracles,
I have a pretty major trouble in that for some reason I had 2btc on a kali vm and tried to encrypt it when it was already LVM encrypted... but I trusted Vbox! But hence, vbox froze at 1% encrypting and now when I try to boot the vm I get a no bootable medium found error.
I found this thread talking about changing the *.vmdk to *-backup.vmdk and replacing *-flat.vmdk with *.vmdk,
[I'm not allowed to post links
]
I tried this but I got an error
But then I found a thread talking about header recovery and I am hoping that maybe the headers were simply corrupted very early on and only a few lines have been modified because the other OP had encrypted, well, he doesn't say, but I'm guessing it was more than 1%.
I have backed up my kali.vmdk and kali-flat.vmdk but otherwise there is nothing I can do from here, so I am hoping you might be able to help.
The kali-flat which I renamed to kali is the same size as it was before the crash so I think all the data is there, I remember the encryption phrase too if that is needed at some point but only 1% was encrypted.
I don't actually know how to access the headers of a .vmdk but I use Mint 17.x and am pretty proficient at sudo nano x and mv and cp so let me know what I have to do.
Yes, please, thank you, it's late now in Australia.
Good night
PS: I tried following this guide [not allowed to post links ]
But I cannot find a single sudo find / -name *.vmx on my computer so I can't get the SCSI type for that step.
tyty
I have a pretty major trouble in that for some reason I had 2btc on a kali vm and tried to encrypt it when it was already LVM encrypted... but I trusted Vbox! But hence, vbox froze at 1% encrypting and now when I try to boot the vm I get a no bootable medium found error.
I found this thread talking about changing the *.vmdk to *-backup.vmdk and replacing *-flat.vmdk with *.vmdk,
[I'm not allowed to post links
]I tried this but I got an error
Code: Select all
Failed to open a session for the virtual machine kali.
Could not open the medium '/home/ggg/VirtualBox VMs/kali/kali.vmdk'.
VMDK: descriptor does not start as expected in '/home/ggg/VirtualBox VMs/kali/kali.vmdk' (VERR_VD_VMDK_INVALID_HEADER).
VD: error VERR_VD_VMDK_INVALID_HEADER opening image file '/home/ggg/VirtualBox VMs/kali/kali.vmdk' (VERR_VD_VMDK_INVALID_HEADER).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
I have backed up my kali.vmdk and kali-flat.vmdk but otherwise there is nothing I can do from here, so I am hoping you might be able to help.
The kali-flat which I renamed to kali is the same size as it was before the crash so I think all the data is there, I remember the encryption phrase too if that is needed at some point but only 1% was encrypted.
I don't actually know how to access the headers of a .vmdk but I use Mint 17.x and am pretty proficient at sudo nano x and mv and cp so let me know what I have to do.
Yes, please, thank you, it's late now in Australia.
Good night
PS: I tried following this guide [not allowed to post links
]But I cannot find a single sudo find / -name *.vmx on my computer so I can't get the SCSI type for that step.
tyty
I think anyway, not to be an ego