fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

SSD and yosemite question

More
29 Nov 2014 15:10 - 29 Nov 2014 15:16 #56638 by dkag7
Hi,
I have read online many articles related to yosemite and 3rd party SSD but the more I read, the more confused I seem to get..(about the kext issues)

The question I have is this..

If I installed Yosemite on a HDD, and then clone it to a SSD, is there anything I need to do or will it work as if I cloned to another HDD?

I do keep many backups, so loosing things is not really an issue, but the speed and life of a SSD is what I am getting at..

Should I still install Trim Enabler 3.3 on a cloned SSD (cloned from a HDD where yosemite was installed on top of Mavericks)

thanks for any help!!

Kurt

I forgot to add to this...
All this is only related to a boot drive correct?
If I use a SSD for media then the kext issue does not apply..?
Last edit: 29 Nov 2014 15:16 by dkag7.

Please Log in to join the conversation.

More
29 Nov 2014 16:58 #56644 by VidGreg
Replied by VidGreg on topic SSD and yosemite question
Hi Kurt.
If you use a 3rd party ssd as a boot drive, you need to use a terminal command in Yosemite to turn off verify kext signatures, otherwise you will not be able to boot.

Trim enabler inserts unsigned kext(s) into System files.

AFAIK each time you update Yosemite, it will default to only allowing signed kexts to boot routine. So look out!
This is a new security measure to prevent malware.

Yes this only applies to the boot drive, you can still use 3rd party ssds for media files.

Hope this helps, Greg

Please Log in to join the conversation.

More
29 Nov 2014 17:05 - 30 Nov 2014 00:26 #56645 by BenB
Replied by BenB on topic SSD and yosemite question
Some 3rd party SSD drives work fine, but verify with the manufacturer first.
My fellow trainer Larry Jordan has a great article about this subject, very worth reviewing.
www.larryjordan.biz/caution-ssd-drives-and-yosemite/

I know a couple of system that got in trouble by simply turning off kext, as it can effect other drivers written for it. Very risky thing to do, IMHO.
Last edit: 30 Nov 2014 00:26 by BenB.

Please Log in to join the conversation.

More
29 Nov 2014 17:50 #56648 by Tom Wolsky
Just to reiterate what was omitted in Larry's conclusion: This only applies to SSD boot drives, not to any third party drive used in any other way, as a media or backup or transfer drive.

Please Log in to join the conversation.

More
29 Nov 2014 18:24 #56651 by VidGreg
Replied by VidGreg on topic SSD and yosemite question
Thanks Ben for the link.

It can be a complicated issue like the SandForce controllers not needing Trim.
Also how you use your ssd makes a difference as to trim and garbage collection importance.
There are lots of fun technical discussions going on about this issue.

That said, up until Yosemite, Apple did not require kext signing. If you are careful about where you download applications, then you are as safe in Yosemite with verify kext signatures turned off as you are running Mavericks and all prior OSs.

By the way, you can't turn off all kexts. Extensions are required to run any computer. You can modify them and that is essential in hacking. Adding kexts back in for some older devices, adding or altering to allow older computers to run newer OS, GPUs etc…

Have not heard of anyone having issues by running trim enablers or turning off verification, and having that affect other drivers, but maybe. Or maybe they are also affected some way by kext signatures now required in Yosemite.

I totally agree that Apple should enable Trim and Garbage collection for all ssds. Have filed this as a request to Apple in the past. Now that this is becoming more of an issue, hopefully Apple will do this. Apple cannot expect to sell every ssd that ends up in Apple computers.

There are some issues with different controller chips, but nothing that couldn't be handled. I'm sure that manufactures would love to cooperate to achieve integration into Apple computers.

Hope this helps, Greg

Please Log in to join the conversation.

More
29 Nov 2014 18:51 #56654 by dkag7
Replied by dkag7 on topic SSD and yosemite question
Thanks Guys..

Any ideas on if the drive (SSD boot) is a clone from a HDD?
Does it matter?
I read in a few posts that if Yosemite is installed on a HDD, then cloned to a SSD, this is not an issue...

thanks again
Kurt

Please Log in to join the conversation.

More
29 Nov 2014 20:53 #56655 by Nervebroke
I have a 13" Macbook Pro mid 2012. I installed the following SSD back during Mavericks.


Samsung SSD 840 EVO 250GB:

Capacity: 250.06 GB (250,059,350,016 bytes)
Model: Samsung SSD 840 EVO 250GB
Revision: EXT0BB6Q
Serial Number: S1DBNSCF413615A
Native Command Queuing: Yes
Queue Depth: 32
Removable Media: No
Detachable Drive: No
BSD Name: disk0
Medium Type: Solid State
TRIM Support: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Verified

When Yosemite came out I upgraded, not a clean instal. I have not had a problem with this SSD

Maybe issues will come later.

Dave

Please Log in to join the conversation.

More
03 Dec 2014 19:15 #56854 by dkag7
Replied by dkag7 on topic SSD and yosemite question
I have installed the SSD's and was able to boot up OK.
So if you have CCC's from a HDD to a SSD (Boot OS), trim will be off and you can boot fine.

I dont think it was really worth it to change to SSD however...If anyone else is thinking of going to SSD

Speed gains were less than I hoped for.
about 500 read and write for a stripe raid of 2 480gb SSD's (230gb used space, 730gb free)
Using 4 7200rpm HDD's as a stripe raid I was able to get about 300 to 400 read and write (with about twice that in used space when running the speed tests).

System is a mac pro 5,1
This has the 3 gigabit SATA speeds and not the 6 gigabit.

kurt

Please Log in to join the conversation.