I had the same issue, but after rebooting it worked.ok so I havent' been able to do this particular update because I keep getting a not responding issue to App Store AND App Store Web Content.
Yeah, right after allowing Trim for 3rd party devices, they'll prevent using 3rd party devices at all...They'll put a stop to this soon.![]()
Someone over at Ars Technica posted a warning about using TRIM with certain hard drives. I'll quote it here:
I haven't looked into it too heavily and I know that plenty of people use TRIM with these drives with no issues (I did in the past), but given that I use a Samsung 840, it gives me pause about enabling this feature. Just figured I'd put it out there for everyone else to see.
I haven't looked into it too heavily and I know that plenty of people use TRIM with these drives with no issues (I did in the past), but given that I use a Samsung 840, it gives me pause about enabling this feature. Just figured I'd put it out there for everyone else to see.
Actually there are. Essentially though the bug seems to only affect queued TRIM commands which Linux and OS X use - in Windows it sends TRIM commands every once in a while along with data and flushes the queue to prevent issues. Linux and OS X on the other hand expect the drive to manage its own queue properly, which as it turns out, a lot of Samsung SSDs don't do.What a load of nonsense. There are no TRIM bugs with Samsung 8xx SSDs, or indeed any SSD manufactured in the last 4-5 years.
Think, I will avoid any possible problems and just stick with the Trim Enabler by Oskar Groth (Cindori.org), that I've been using for the past 2 plus some years. Using a 240GB Kingston Hyper-X 3K SSD. Haven't had any issues.
But, nice to know there is a built in option now.
Typically with the 3rd party utils you had to reapply after every major or minor version of the OS.
So I would suspect 10.11.0 and 10.10.5 will require you to run the util again.
about time.
too bad my boot drive SSD is connected to my 2012 macmini via usb3.0
Someone over at Ars Technica posted a warning about using TRIM with certain hard drives. I'll quote it here:
I haven't looked into it too heavily and I know that plenty of people use TRIM with these drives with no issues (I did in the past), but given that I use a Samsung 840, it gives me pause about enabling this feature. Just figured I'd put it out there for everyone else to see.
TRIM is an ATA command.why? is not suppose to work on all connected drives? i also have my boot SSD on USB3...
I see no evidence that OS X uses or supports queued TRIM commands, even if the device firmware says that it supports queued TRIM commands. It is therefore impossible that the device firmware has a problem with queued TRIM commands.Actually there are. Essentially though the bug seems to only affect queued TRIM commands which Linux and OS X use - in Windows it sends TRIM commands every once in a while along with data and flushes the queue to prevent issues. Linux and OS X on the other hand expect the drive to manage its own queue properly, which as it turns out, a lot of Samsung SSDs don't do.
/*
* Validation Routine to verify that the TRIM list maintained by the journal
* is in good shape relative to what we think the bitmap should have. We should
* never encounter allocated blocks in the TRIM list, so if we ever encounter them,
* we panic.
*/
trim_validate_bitmap
; Routine: hfs_unmap_free_extent
;
; Function: Make note of a range of allocation blocks that should be
; unmapped (trimmed). That is, the given range of blocks no
; longer have useful content, and the device can unmap the
; previous contents. For example, a solid state disk may reuse
; the underlying storage for other blocks.
;
; This routine is only supported for journaled volumes. The extent
; being freed is passed to the journal code, and the extent will
; be unmapped after the current transaction is written to disk.