Skip to main content

"Run list corrupted" when converting Acronis image to VHD

Thread needs solution

When trying to convert a specific backup image to VHD, it tries for 10 seconds, then errors. When checking the log, I found "Run list corrupted".

I originally imaged the disk using Acronis 2013 and also tried to convert the image in that product with the same failure.
I've tried to convert some of my other older (and much smaller) images, and they convert successfully. So this particular image, how it has been made, or what's on it, is causing the conversion error.

I have successfully validated the image in both 2013 and 2014. I can also successfully mount it using Acronis.

I don't understand why this particular (healthy-looking) image is causing an issue. I have two copies of it on separate drives (same MD5) and they both fail at converting it, so it's not a problem with the physical disk the image is stored on either.

The image is around 19GB. The only difference with this image in comparison to my others, is that it is split into 4.7GB DVD-size parts, around 5 parts currently. Could this affect the conversion to VHD?

0 Users found this helpful

There were reports about image backups that validate but fail with filesystem-related errors on restore (conversion to VHD is restore too). You may try to fix it by mounting it in read-write mode, runnig chkdsk on the mounted volume and unmounting it. It's possible that resulting incremental backup may be converted.

In tools & utilities, choose mount an image.

Run CMD and CHKDSK G: /r, results in:

"Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y

Chkdsk cannot dismount the volume because it is a system drive or
there is an active paging file on it. Would you like to schedule
this volume to be checked the next time the system restarts? (Y/N)"

So how can I run CHKDSK if the Acronis Image Mounter prevents it from being run? Use another image mounting tool other than Acronis?

Darn. How would there be an active paging file on it? I think the error must be something else.
Only option I can imaging is to restore the image to a spare disk, verify the disk is error free after that. At that point we will have eliminated the possibility there would be an error in the file system that was backed up. You could also at this point try to create a single TIB file and see if the conversion succeeds. It if succeeds, you would not that the splitting process was linked to the conversion failure.

Yes, that was the set of steps I was going to take before posting the topic on the forum. I just thought I'd check before I did that to see if anyone knew if this was a common problem that could have been quickly resolved.

If the paging error I do receive is not a red herring, what could be the root cause of that? An incompatibility bug in Acronis 17? I'm using Windows 8.1 and I'm sure that has nothing to do with it. I have VMWare Workstation 6 installed on this machine and Alcohol 52%. They are the only pieces of software that I can think of that could possibly conflict with Acronis.

Attempting to recover the image failed immediately:

"Run list corrupted. Error 0x7001c".

How can the recover fail, but when validating it says everything is ok? If this is the case, what's the point in the validation feature? Even worse, how do I know that all my other backup images aren't worthless?

The validation is telling you that the backup data has not degraded over time. The validation process recalculates the checksum points in the archive file and compare them with the checksum points calculated during the backup process and stored in the archive.
The run list corrupted is telling you that the data that has been backed up was corrupted.
There is no silver bullet to be 100% you can restore a backup file until you have to do it for real. Validation, mounting images are ways to increase the confidence.

I'm sorry but the fact remains that the validation remains useless. If it is indeed a separate entity only to checksum the image process, then that is no good. As in a software tester's terminology (my profession), Acronis also needs a 'Verify' feature to make sure that the backup that is actually being made (i.e. the actual data) is not corrupted in the first place BY the backup. In other words, what it should backup, it should be able to restore.

So what is the remedy to fix this problem what Acronis started?

Chris,

I am afraid there is no way to fix this archive. When in Windows, can you double click on it and open it? This might help you retrieve some content.
Otherwise, your only path is to consider the backup lost. If you do a new one, run chkdsk X: /R on each X partition of the disk you are backing up. If you have hidden partitions, assign them a drive letter temporarily for the purpose of running chkdsk /R on it.
Then do your backup without splitting it.

Unfortunately, I do not have the time to waste on building another system from bare metal and back it up though Acronis with no guarantee of the backup not having the same problem as before. I have no faith in the Acronis products available and will happily rely on virtualisation through a combination of VMWare and Hyper-V products.