Skip to main content

mft bitmap corrupted

Thread needs solution
Beginner
Posts: 1
Comments: 2

There are umpteen references to this malfunction in the KB and in the forums. I can't get any of the offered solutions to work for me. The facts are:-
Windows Vista home premium SP2 on a Dell Inspiron 1525
Western Digital 160gb hdd scorpio
I am trying to clone this disk to a new WD 320Gb hdd scorpio blue.
I have downloaded True Image WD from the WD website onto the 160Gb disk. I have run TI from this disk and from a bootable CD.

1. Clone from computer to USB caddy with the 320Gb disk. Fails.
2. Clone from 160Gb disk in the USB caddy to the 320Gb disk mounted in the computer using a bootable CD to run Acronis true image. fails.
3. Clone from 160Gb disk in a USB caddy to the 320Gb disk in a USB caddy using a bootable CD with True Image WD. fails.
4. I have downloaded and installed snapAPI.dll 584. And re-tried 1-3 above. All fail.

Each failure has the identical error message. "mft bitmap corrupted".
5. I have run chkdsk c: /r. Early on in the time wasting fiasco. all fail.

I have two error reports which are attached. One is using True Image on a bootable CD the other running it on the Wvista OS.

Any ideas as to what I am supposed to try now?
John

0 Users found this helpful
Forum Hero
Posts: 87
Comments: 9259

Did you try the disk and partition backup method? Use the recovery CD to do your backup and your restore. Make sure to include your entire disk in the backup (all partitions). Restore one partition at a time in the same order they were on the smaller disk. Only resize the C:\system partition. Don't forget to mark the right partition active.

See this thread for the SSD case. Applies here as well, just ignore the optimizations for SS.

http://forum.acronis.com/forum/26162

Forum Star
Posts: 27
Comments: 1940

You need /f chkdsk argument to fix filesystem errors. /r detects physically damages sectors.

Beginner
Posts: 1
Comments: 2

Thanks Pat.
I haven't used this method - yet. I was rather hoping to avoid it on the grounds that clone disk does it all in one go, whereas the method you suggest has two major steps and many little tiny but doubtless important ones.

However if I decide to cut my losses please could you confirm which are the SSD tweaks. Are they those which you list at the end - only or are there some in the middle too?

Why is it necessary to leave 1mb at the beginning of the new system disk? Is it obvious how to achieve that in restore process?

And finally where do I find "windows disk management" in Vista and indeed WXp? I probably know it but not by that name.
John Blackie

Beginner
Posts: 1
Comments: 2

Problem solved!
I took the source disk out of the original computer and put it in a caddy. I then did CHKDSK disk: /f suggested by dev-anon above for both the OS partition and the recovery partition. Both operations found some kind of error and claimed to have corrected it. Something about bits of empty space not being properly accounted for.

Having done that I did the clone; that is USB source disk to original computer mounted destination disk booting from the TI CD I made earlier (USB->SATA). It sailed through, no errors, no little displays of grief, just went through 6 operations of which 4 was by far the longest (an hour and a bit).

The computer, realising now that it had a new double sized disk, installed a driver for it and followed by a straightforward re-boot. All done. Thanks to all above for your valued interest in this problem without which I could not have solved it.

btw I used a separate computer to do the chkdsk because the source disk was not doing anything other than being checked by chkdsk disk: /f and so was inert whilst the check was in progress.
John Blackie

Forum Hero
Posts: 87
Comments: 9259

The 1MB is necessary to align the disk, which is very important for SSD and raid-disks.