Code: Select all
Could not get the storage format of the medium 'E:\FixBrokenUbuntu\broken.vdi' (VERR_NOT_SUPPORTED).
Result Code:
VBOX_E_IPRT_ERROR (0x80BB0005)
Component:
MediumWrap
Interface:
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee:
IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC:
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
This happened since I was trying to open Photoshop, though it said it couldn't open, since there's only 5GB free on my C: drive...so I decided to copy the VDI file in windows explorer to another drive since it was taking up a lot of space...I guess that didn't work though I then searched online and saw I needed to use the move option in the virtualbox GUI...I tried that, but the progress bar was percentage value were just stuck at 0% for like 15 minutes...so I then clicked the "x" arrow to stop it...it seems it didn't stop and and eventually returned saying "error" (at the time, I was just going to try again, so I didn't copy the error code or anything) said the ~70GB vdi was copied to my new drive...when I looked in my new drive, I saw the vdi had been moved there, though since I clicked on the "x" button to cancel, I assumed the original would still be on the C: drive...so I deleted the version of the D: drive...but then I checked back in my C: drive and of course that file had been deleted...
So eventually I found some file recovery software that seemed to find the file on the D: drive (though that was the version the "move" command returned "error" for...the original on the C: drive, I've not been able to get...so it makes me think this version that I've been able to 'recover' is a copy of a corrupted version...assuming the file recovery software even recovered it correctly (since I honestly thought the vdi was either 67 or 69GB...so when the recovered version was 70GB, that was strange...now, whether that's simply my bad memory or the recovery software copied extra sectors or something, I don't know)
Here is a screenshot of the start of my VDI file...it looks complete f*cked, to be honest
i.imgur. com/YLMfNud.png (remove the space between the ". com") - my account is too new to post links...)
And here are the first 200400 bytes of that same file (I just saved two versions as a .vdi and another as a .bin...not sure if that's correct? The 4MB file is too big to upload as an attatchment)
files .fm/f/7udtqku8p (<-- again...remove the space between the ". fm")
Does anyone know what might be the problem? And is there any chance of getting it working again?
Also, why does VirtualBox delete the original in the "move" command (I realise that is the definition of "move"...but wouldn't it be safer make it to simply copy the vdi to a new location first...then let the user delete the old version themselves, once they've verified the moved version is working?). Afterall, I guess I and many others are used to the default behaviour on windows...where dragging a file into a windows explorer window that's a different drive will actually copy the file...which is safer than just deleting the original, considering the copy could fail for a variety of reasons...
Afterall, even in assembly, "mov" really means "copy"...since the original isn't deleted...I will make a feature request about this, to see what others think...afterall, it's far safer...and I don't think many users mind having to manually delete the original
If anyone is able to help me out though, I'd really appreciate it...I have many 100s of hours of work on this thing...I possibly have a backup for some old stuff, though not for a few new projects