5 ms·

I didn't experience any failures with exFAT yet, but I had lots of failures with FAT16, FAT32 and NTFS. FATs were fixable and most data recoverable. NTFS - not

by M95D 4y ago

I didn't experience any failures with exFAT yet, but I had lots of failures with FAT16, FAT32 and NTFS. FATs were fixable and most data recoverable. NTFS - not at all - everything lost. I think that implementation bugs are the cause for most errors. This is not a popular filesystem used in datacenters, so testing would be minimal by comparison.

mdaniel 4y ago
> NTFS - not at all - everything lost. Is that only using Microsoft's tooling, or did you try ntfs3g from a Linux boot stick? I am grateful that I've never tried to recover borked NTFS, but my mental model is those utilities have explored more "off the beaten path" than Microsoft may want to bother with. And, in the worst(?) case, you can patch the utilities to do any kind of extra debugging you may need
- forgotpwd16 4y ago
  The ntfs3g's ntfsfix is fairly limited and, besides some basic repairs, it will schedule the drive for checking on Windows.
  - pantalaimon 4y ago
    ntfs3g is also obsolete and not really developed much anymore. Use the new in-kernel ntfs3 driver. https://www.kernel.org/doc/html/latest/filesystems/ntfs3.html https://www.kernel.org/doc/html/latest/filesystems/ntfs3.htm...
    - forgotpwd16 4y ago
      Regardless of driver utilized, the ntfs3g project contains the ntfsprogs userspace utilities such as aforementioned ntfsfix.
- M95D 4y ago
  MS only. I wasn't using linux at the time.
forgotpwd16 4y ago
>NTFS - not at all - everything lost. This is not my experience. Had many times chkdsk repair a corrupted NTFS just fine. Even when by mistake overwrote (run r/w badblocks detection) part of the partition, testdisk could recover data.