Company X may have a bad SSD that Apple won't use, but it still buys memory chips from X, for example. Publicly, Apple would never issue a list of BAD drives that's not their responsibility, and they have complex relationships with component manufacturers they have to protect. So after testing and finding out the brands they would NOT use in their machines, Apple decided the safe approach was only enable TRIM on the drives that passed their testing. Apple did not want people turning on TRIM with other drives, and then be accused of data loss or issues which were outside of their control, and be BLAMED for it, as people would automatically assume based on their experience with rotational drives that 'it can't be the drive, it must be Apple'. This has been confirmed now in early drives using Sandforce controllers in which live data could be incorrectly marked and deleted by using TRIM. Apple no doubt tested all kinds of brands and manufacturers when deciding who to use in their own machines, and likely found that many had bugs in their implementation TRIM. I've updated without issues.Īs for all the conspiracy theories about why Apple did not enable trim support for non Apple branded SSDs, until now, this is a perfect example.
Disk sensei el capitan update#
Read more about this SEPARATE PROBLEM UNRELATED TO THE LINUX PROBLEM HERE:įirmware update is provided as an ISO bootable CD image that will boot Macs or Windows PC., using a Linux micro kernel, that locates and updates the drive. This problem affects the drive regardless of OS, so highly recommended you update the firmware. The latest firmware from Apfixes this by periodically 'refreshing' in the background all the data on the drive to keep the charge strong, even data that isn't accessed. This problem is not OS specific and deals with the actual physical nature of the drive itself. HOWEVER, there is ANOTHER issue with Samsung EVO related to reading data that is 'old' (not been accessed for a long time) where the charge may degrade, requiring multiple attempts to read the data. Windows and OS X ignore this bit because as of now, they only support 'normal' sequential TRIM, so is unaffected BY THIS ONE PARTICULAR PROBLEM.
The incorrect bit says that EVO supports beyond normal sequential queued TRIM commands (it does not) and then Linux attempts to implement (which does support more than sequential) and runs in to problems. One problem, related to the drives having an incorrect bit set that tells the OS what type of NCQ queing command it supports. Not true, there are actually TWO critical issues discovered so far with the EVO drives, one Linux related, the other NOT. Some users are insisting the problem is only with Linux, and you don't need a firmware update. There is a lot of confusion about the multiple issues with the Samsung and the need for firmware update.
Disk sensei el capitan install#
IF YOU OWN A SAMSUNG EVO OR EVO PRO, 840 OR 850, be sure to install the latest firmware before turning on TRIM support
0 kommentar(er)
