How to Fix a Windows NTFS Drive That Won’t Work on Linux

If Linux will not open a Windows-formatted hard drive, first confirm it is an NTFS partition and that the device itself is healthy. For some NTFS metadata problems, Linux’s ntfsfix utility can make limited repairs and request a fuller check the next time Windows starts. It is not a Linux version of CHKDSK, and it cannot repair failing hardware or recover lost files. Back up any readable data before making changes; if the drive clicks, disconnects, or reports I/O errors, stop and prioritize copying or imaging the data.

Install the NTFS repair utility

ntfsfix comes with the NTFS utilities. Package names vary across Linux distributions, and some distributions split the driver and utilities into separate packages. Install from your release’s official repositories:

Package availability can differ by release, especially on openSUSE Leap. If your package manager cannot find the utility, check your distribution’s package index before adding another repository. The ntfsfix manual documents the utility, while the Ubuntu ntfs-3g package, Fedora ntfsprogs package, and Arch ntfsprogs package show how packaging is organized.

Identify the NTFS partition carefully

Connect the drive, open a terminal, and run:

lsblk -f

Look at the FSTYPE, LABEL, and MOUNTPOINTS columns. Choose the partition whose filesystem is listed as ntfs. A disk may appear as /dev/sdb with a partition such as /dev/sdb1; NVMe partitions use names such as /dev/nvme0n1p3. The repair command must target the NTFS partition, not the whole disk. Never copy the example device name below without checking your own output.

Unmount it and run a no-write check

Replace /dev/sdX1 in the commands with the exact NTFS partition you identified. Check whether Linux has mounted it:

findmnt --source /dev/sdX1

If it is mounted, close files and windows using the drive, then unmount it:

sudo umount /dev/sdX1

If the command says the target is busy, close the programs using it and try again. Do not continue while the partition is mounted. You can then ask ntfsfix to report what it would do without writing changes:

sudo ntfsfix --no-action /dev/sdX1

This is a useful preview, not a full diagnostic or a guarantee that repair will succeed. If the selected partition is not NTFS, stop and recheck the device list.

Run the limited NTFS repair

After confirming the device and unmounting it, run:

sudo ntfsfix /dev/sdX1

Read the output and wait for the command to finish. ntfsfix addresses a limited set of common NTFS inconsistencies, resets the NTFS journal, and schedules an NTFS consistency check for the first Windows boot. A message that the Linux command completed does not mean every filesystem problem has been repaired.

Finish the check in Windows

Safely disconnect the drive if needed, reconnect it to a Windows computer, and let any scheduled file-system check run. If Windows still reports errors, open Command Prompt as an administrator and run chkdsk X: /f, replacing X: with the drive letter shown in Windows. Microsoft documents that /f fixes logical file-system errors; if the volume is in use, Windows may ask to schedule the check for the next restart. Back up important files first, because repairs change filesystem metadata.

If the volume is read-only after Windows use, it may still be hibernated or affected by Fast Startup. The NTFS-3G manual explains that this can leave internal NTFS partitions read-only or inconsistent. Boot Windows and perform a full shutdown before trying again; do not force a writable mount of a hibernated volume.

Do not use the extra flags as general fixes

The old --clear-bad-sectors advice is easy to misread: it clears NTFS’s recorded bad-sector list, which the manual describes as useful after cloning an older disk onto a new one. It does not repair physically damaged sectors or a failing drive. Likewise, --clear-dirty changes the volume’s dirty flag; it is not a substitute for checking the filesystem. Avoid these options unless you understand why the metadata needs to change.

If the disk is missing from lsblk, repeatedly drops offline, or produces read errors, ntfsfix is not the right tool. Check the cable, port, or enclosure only if doing so is safe, and protect the data before attempting further repairs. For normal filesystem errors, use ntfsfix only as a first aid step and complete the check in Windows with CHKDSK.