It's a well-known bug for those that work heavily with SSDs.
If it was happening to everyone 100% of the time, people would be screaming bloody murder. Just because you haven't seen the data loss bug yourself doesn't mean the data loss bug isn't there (it is). The worst part is that Samsung repeatedly says they refuse to fix a bug in their firmware because the drive is being used on Linux. You can see some of them are linked in the Ubuntu bug report. The list itself was created by people filing bugs about extreme data loss. It's not exactly clear to me who came up with this list, if it's entirely comprehensive, or if OSX will end up having the same kind of problem (these drives all work fine with TRIM in Windows). The Linux kernel has a blacklist to deal with this problem, which presumably contains all the drives currently known to be affected: It just happens that significantly more TRIM commands are sent if queued TRIM is available (probably due to no longer needing to determine the "best time" to send the non-queued TRIM without adversely affecting performance) Every TRIM command sent to the drive carries a risk it'll trigger the bug. As mentioned on that blog post, it is not limited to queued TRIM. Note that that thread gives the incorrect impression the bug is only triggered when using the queued TRIM command. The blog post only mentions Pro, is there confirmation that the EVO is affected? The bug is not dependent on queued TRIM, it happens even when using the non-queued version.Īll the Samsung SSDs beginning with a "8" (840 and 850, both EVO and Pro) are known to have the data-destroying TRIM bug and TRIM is blacklisted on those drives on other platforms. There are a number of extremely buggy SSD models out there (like almost all the Samsung 8* and various Crucial models) that will permanently delete the wrong data when issuing TRIM commands. We’ve enabled it on a pair of older Macs in the Orbiting HQ with aftermarket SSDs in them, and so far we’ve had no issues-giant scary warning notwithstanding. Called trimforce, the utility can be executed from the OS X terminal, and it requires a reboot to start working.
ENABLE TRIM MAC OS INSTALL
With today’s OS X 10.10.4 update, however, Apple has added a command line utility that can be used to enable TRIM on third-party SSDs without having to download and install anything. If you took a Mac that originally came with a spinning disk and installed an aftermarket SSD in it yourself, the operating system wouldn’t use TRIM on the disk-at least, not unless you resorted to third-party tools. The lone exception to that list has been Apple’s OS X, which-at least until today-only supported TRIM on its OEM SSDs. Pretty much every operating system in use these days supports TRIM-a special ATA command that the OS sends along to an SSD when deleting files on that SSD. Further Reading Ask Ars: “My SSD does garbage collection, so I don’t need TRIM… right?”