MFT Bitmap error, Windows 10 ATI 2019
I made a full backup of my 120 GB SSD prior to updating my display driver via Windows Device Manager. Windows updated the driver, but I was not happy with the result. I then used a bootable rescue USB drive, created as Simple on this laptop, to restore the "C" partition only. TI 2019 gave me this notice "This section partition contains the following error: MFT Bitmap Corrupted. Please note that you cannot change the file system and size of this partition. It is recommended that you check the partitions after recovery with your operating system tool". I continued with the restore and the laptop appears to run fine. The full backup validates, and check disk does not find any errors. What is this MFT bitmap error telling me? Bad disk or bad backup? Or that something changed with partition size a few hours after creating the full backup, perhaps from the updated driver installation? I mainly want to know if I should be concerned about my C drive.


- Log in to post comments

Thank you Steve, I'll leave it at that. I was not aware that I could save a log file when using bootable media. If it happens again I definitely will.
- Log in to post comments

If you are using an NTFS filesystem I would run chkdsk /b against all NTFS partitions on the drive. This will remove any clusters that are marked as bad and might resolve the error for you.
- Log in to post comments

Bob, is CHKDSK /b still advised for SSD drives or only for spinning HDD's?
- Log in to post comments

Steve,
chkdsk /b includes the functionality of /r but, it re-scans looking for areas on disk marked as $BadClus and evaluates if these marked areas can be released back to general use or not. If it finds the area on drive is usable it will clear the mark from the area on disk so that that area can be used again. This in turn can correct MFT bitmap errors.
In general an SSD needs only the chkdsk /f run because the drive controller itself does all other maintenance chores Normally the controller will take care of any areas on disk marked $BadClus so using chkdsk is not necessary. If however Windows has marked such an area, and then a backup or clone of the disk after that fact happens to a new or different disk, the mark can be carried over to the new disk.
True Image runs scans on disk prior to clone/restore operations so such errors can be exposed thus the warning noted by the OP and the suggestion to " check the partitions after recovery with your operating system tool". So to insure that such marks are cleared chkdsk /b is the best option.
chkdsk /b only applies to NTFS filesystems.
- Log in to post comments

Thanks for the clarification Bob - helpful as always!
- Log in to post comments

My pleasure :)
- Log in to post comments