Da kann ein TRIM durchaus zu Datenverlust führen. Unter anderem die Samsung
SSDs mit 8 am Anfang der Modellnummer:

https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/
» At this moment we finally got a complete picture of what was going on. The
» system was issuing a TRIM to erase empty blocks, the command got
» misinterpreted by the drive and the controller erased blocks it was not
» supposed to. Therefore our files ended-up with 512 bytes of zeroes, files
» smaller than 512 bytes were completely zeroed.
»
» […]
»
» Broken SSDs:
» • SAMSUNG MZ7WD480HCGM-00003
» • SAMSUNG MZ7GE480HMHP-00003
» • SAMSUNG MZ7GE240HMGR-00003
» • Samsung SSD 840 PRO Series
» recently blacklisted for 8-series blacklist
» • Samsung SSD 850 PRO 512GB
» recently blacklisted as 850 Pro and later in 8-series blacklist


Die sind zum Beispiel auch im Linux-Kernel auf der Blacklist und bekommen dort
kein TRIM:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/ata/libata-core.c#n4227
» /* devices that don't properly handle queued TRIM commands */
» { "Micron_M500_*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
» ATA_HORKAGE_ZERO_AFTER_TRIM, },
» { "Crucial_CT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
» ATA_HORKAGE_ZERO_AFTER_TRIM, },
» { "Micron_M5[15]0*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |
» ATA_HORKAGE_ZERO_AFTER_TRIM, },
» { "Crucial_CT*M550*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |
» ATA_HORKAGE_ZERO_AFTER_TRIM, },
» { "Crucial_CT*MX100*", "MU01", ATA_HORKAGE_NO_NCQ_TRIM |
» ATA_HORKAGE_ZERO_AFTER_TRIM, },
» { "Samsung SSD 8*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
» ATA_HORKAGE_ZERO_AFTER_TRIM, },