"So far there is no evidence indicating that the issue exists outside Linux. The operating system barks back a long and potentially scary message about how using trimforce may cause 'unintended data. OS X 10.10.4's new 'trimforce' command is entered through the Terminal: sudo trimforce enable.
There are plenty of users running Samsung SSDs in Macs with TRIM enabled and I've yet to hear a single data loss issue." While kext signing is still Yosemite's law of the land, 10.10.4 introduces a new 'trimforce' command that enables trim on SSDs. All 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." The bug is not dependent on queued TRIM, it happens even when using the non-queued version. HEED THE DATA LOSS WARNING! 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. No more dangerous experiments with third party software necessary. OS X provides since 10.10.4 a new tool called trimforce, allowing users to activate TRIM also on unsupported disks. A similar procedure should work for anything that turned on trim.
#Trimforce vs trim enabler how to#
"Someone over at Ars Technica posted a warning about using TRIM with certain hard drives. If you are using Trim Enabler, this article describes how to recover. Aren't you afraid about the concerns using TRIM with samsung pro/evo ssd? I have a samsung ssd too but i'm a little confuse about trim activation.
0 kommentar(er)
