virtualbox.org

Hi Everyone,

I using VDI with VM, but it showed inaccessible error since last week and I was released it and trying add again, but no luck.
Any idea?

Post the following :-

1. A VM log file - right click VM, select "Show Log", save the "VBox.log" file (ignore the others).
2. The contents of the <vm name>.vbox file from your VirtualBox VMs\<vm name> folder.
3. The contents of your <vm name> folder and <vm name/Snapshots subfolder.

Pack all that into a zip file and attach here.

Hi,

The screenshot of error here:

I see nothing noteworthy in the logs etc except that there are no disks attached, so this log was captured after you released the VDI?

What exactly is the context of the error picture you have provided? I.e. which controller were you trying to attach the VDI to?

Have you made any significant changes since this VM last worked? For example, did you delete any other VMs? Did you delete or merge any files from this VM? Did you clone or resize anything? Did you rename anything? (including renaming an extension).

What happens if you tell CloneVDI to clone your VDI file? I expect it will give you an error message, but what is it?

mpack wrote:I see nothing noteworthy in the logs etc except that there are no disks attached, so this log was captured after you released the VDI?

may be as I was removed & create again this VM for fixing

mpack wrote:What exactly is the context of the error picture you have provided? I.e. which controller were you trying to attach the VDI to?

SATA control with AHCI type

mpack wrote: What happens if you tell CloneVDI to clone your VDI file? I expect it will give you an error message, but what is it?

the screenshot below:

MSDN wrote: ERROR_CRC - 23 (0x17)
Data error (cyclic redundancy check).

CRC errors are an indication of physical damage to a part of your host disk, i.e. bad sectors. So I'm afraid it looks like the VDI file has landed on a damaged part of the disk, and it must be affecting the VDI header if CloneVDI is showing that message before you've even told it to do anything.

You should do a thorough disk check to see if the bad sectors can be marked and isolated. The VDI itself is probably not recoverable without a backup.

I sympathize, having gone through a similar problem a couple of weeks ago. A drive was developing bad sectors, I eventually decided that I had to replace it rather than risk my data any further. In my case it was also a VDI which was affected, which isn't really a coincidence since the larger a file is, the greater the chance that it will intersect a bad sector.

Thanks so much, with your advise I was checked & repaired this error. Everything is ok now