Windows and Nobara Dual Boot: Save Files Before Repairing a Damaged NTFS Master File Table
Protect the files before making another NTFS or boot repair attempt. In this Windows 11 and Nobara recovery case on Reddit, an Acer Swift 3 has a 512GB Kingston NVMe SSD, a roughly 371GB Windows NTFS partition, and a Nobara Linux installation. Windows Startup Repair and System Restore have failed; chkdsk /f terminates with “Master File Table damaged.” The user also needs the personal files and Steam library, but only has a 68GB USB drive for backup.
The 68GB USB Is Not a Full-Disk Image Destination
An uncompressed sector-by-sector image of the entire 512GB SSD requires roughly the full disk's addressable capacity on a different healthy storage device; the spare 68GB USB is not sufficient. The USB can be used for a bootable recovery environment or small verified exports, but not as the destination for the whole source disk image. Do not create an image file anywhere on the damaged SSD itself.
If you cannot get a large enough external HDD/SSD immediately, power the laptop off rather than repeatedly booting Windows or modifying partitions. If files are still readable from a separate trusted environment, a read-only, targeted copy of irreplaceable documents to independent storage may be a contingency, but it is not equivalent to a complete preservation image.
Why CHKDSK and SMART Do Not Settle the Problem
Microsoft's CHKDSK documentation confirms that /f attempts to change file-system structures to correct errors. It already terminated on the MFT in this case, so do not repeat it or try rebuilding the MFT on the only original until there is a protected copy. A SMART overall status of PASSED does not prove that NTFS metadata is sound or rule out all drive/controller problems. Nobara's reported Btrfs checksum errors must also be investigated separately; do not claim both file systems failed for the same reason without evidence.
Data-First Decision
- Obtain enough independent storage: make a raw or controlled image/clone of the complete source SSD when it can be read reliably. Use an imaging workflow that records errors rather than forcing repeated direct scans.
- Inspect a copy: identify the actual NTFS partition and recover personal files and saves to a different healthy drive; verify that representative files open.
- Only after the data is safe: investigate Windows boot configuration, NTFS repair, or an OS reinstall on a working copy or replacement storage. Rebuilding a boot loader is not a substitute for restoring a damaged MFT.
If the imaged NTFS volume remains accessible to a recovery program, Recoverit Hard Drive Recovery may help recover files from the readable disk or a supported image. This is conditional; it does not guarantee repair of the original Windows installation or of a damaged NVMe device.