> Filesystems keep checksums of every block of data.
False. A limited number of filesystems keep checksums of data - most notably ZFS and btrfs. Some like ext4 and APFS will do it for metadata only. One of the most commonly used filesystems, NTFS, does not for either data or metadata.
> Typically it's done at the filesystem level or higher, including when using self-encrypting drives.
I don’t know where you got this idea from, but it’s basically the opposite of true.
> If single bits are flipped then they can be corrected.
Also false. Most checksums are used for error detection, not correction. CRCs as are typically used for filesystems are not particularly well suited for error correction.
Those filesystems (ZFS, BTRFS) have robust error correction, but every modern filesystem has checksums for every block. Checkdisk isn't powered by magic.
Also, look into TCG Pyrite. Almost all consumer drives with SED features are Pyrite.
> but every modern filesystem has checksums for every block.
At least 2 people have informed you that you’re wrong. Now it’s up to you if you choose to educate yourself on this topic or remain a fool.
> Checkdisk isn't powered by magic.
What is “checkdisk”?
If you’re talking about chkdsk, or Check Disk, or fsck like tools - none of those require checksums to do what they do. At a basic level they check the integrity of on disk data structures - the actual connectivity, valid counts, etc. How in your mind does a checksum contribute to this task?
Chkdsk exists for FAT32, which you already seem to admit has no checksums. How do you think it works?
> Also, look into TCG Pyrite. Almost all consumer drives with SED features are Pyrite.
What does this have to do with anything - it certainly isn’t filesystem level encryption.
False. A limited number of filesystems keep checksums of data - most notably ZFS and btrfs. Some like ext4 and APFS will do it for metadata only. One of the most commonly used filesystems, NTFS, does not for either data or metadata.
> Typically it's done at the filesystem level or higher, including when using self-encrypting drives.
I don’t know where you got this idea from, but it’s basically the opposite of true.
> If single bits are flipped then they can be corrected.
Also false. Most checksums are used for error detection, not correction. CRCs as are typically used for filesystems are not particularly well suited for error correction.