CHKDSK fails to repair MFT mirror and volume bitmap corruption on an NTFS drive

Supreme boy 20 Reputation points
2026-07-24T14:50:20.7666667+00:00

Hi,

I was trying to install WSL2 on my G: drive.

I have a 500GB HDD with two partitions:

  • G: → My personal data (images, photos, etc.)
  • F: → A complete Windows installation (alternative system)

I decided to move my WSL2 Ubuntu installation to my G: drive. First, I installed Ubuntu and WSL2 on my C: drive.

I ran these commands: wsl -l -v, wsl --shutdown, mkdir G:\WSL

Then I tried to export Ubuntu to my G: drive:

wsl --export Ubuntu-24.04 G:\WSL\ubuntu.tar

However, the export was extremely slow. It only reached around 2048 MB after 1 hour and 30 minutes, so I cancelled it.

After that, I tried importing Ubuntu using the official rootfs file instead:

wsl --import Ubuntu G:\WSL C:\Users\myname\Downloads\ubuntu-noble-wsl-amd64-wsl.rootfs.tar.gz --version 2

But I received this error:

The request could not be completed because of an input/output (I/O) device error.

Error code: Wsl/Service/RegisterDistro/0x8007045d

At this point, I did know my drive had a problem.

I then ran:

chkdsk /x /f

CHKDSK completed stages 1, 2, and 3, but during the final stage I got these messages:

Stage 3: Examining security descriptors...

Security descriptor verification completed.

3361 data files processed.

Correcting errors in the master file table (MFT) mirror.

Correcting errors in the volume bitmap.

An unspecified error occurred (6e74667363686b2e 15bc).

An unspecified error occurred (6e74667363686b2e 17b4).

CHKDSK was unable to complete the repair and I dont want to format the disk (unless it is necessary)

The drive is an internal 500GB HDD using the NTFS file system.

Could someone help me understand what is causing this issue and what I should do next?

Is this likely to be NTFS corruption, a failing HDD, or something else?

Thank you.

Windows for home | Windows 10 | Files, folders, and storage
0 comments No comments

Answer accepted by question author
Rosillo, Victor 80 Reputation points
2026-07-24T14:59:43.7+00:00

Summary of the Issue:

  • You tried moving WSL2 Ubuntu to your G: drive.

Export was very slow, then import failed with error 0x8007045d (I/O device error).

Running CHKDSK showed corruption in the MFT mirror and volume bitmap.

CHKDSK could not repair the errors.

What this means:

The errors point to serious NTFS corruption.

The I/O error strongly suggests the HDD is failing (bad sectors or mechanical wear).

It’s not WSL2 causing this—the drive itself is the problem.

What to do next:

Stop writing to the G: drive to avoid further damage.

Back up important files immediately using tools like robocopy or recovery software.

Check SMART health with CrystalDiskInfo or similar.

If SMART shows problems, clone the drive to a healthy disk before repairs.

After backup, you can try chkdsk /r or recovery tools like TestDisk.

Be prepared to replace the HDD—it’s very likely failing.

Bottom line: This is more than just NTFS corruption. The HDD is probably failing. Focus on data recovery first, then consider repair or replacement.Summary of the Issue:

You tried moving WSL2 Ubuntu to your G: drive.

Export was very slow, then import failed with error 0x8007045d (I/O device error).

Running CHKDSK showed corruption in the MFT mirror and volume bitmap.

CHKDSK could not repair the errors.

What this means:

The errors point to serious NTFS corruption.

The I/O error strongly suggests the HDD is failing (bad sectors or mechanical wear).

It’s not WSL2 causing this—the drive itself is the problem.

What to do next:

Stop writing to the G: drive to avoid further damage.

Back up important files immediately using tools like robocopy or recovery software.

Check SMART health with CrystalDiskInfo or similar.

If SMART shows problems, clone the drive to a healthy disk before repairs.

After backup, you can try chkdsk /r or recovery tools like TestDisk.

Be prepared to replace the HDD—it’s very likely failing.

Bottom line: This is more than just NTFS corruption. The HDD is probably failing. Focus on data recovery first, then consider repair or replacement.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.