Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The Samsung 830 SSD thread
- Thread starter Acejam2k
- Start date
- Sort by reaction score
Thanks for that.
Now, let me add why I feel this may not actually be working. Once you put the stock Apple SSDs into software RAID, Trim stops. Here are you essentially forcing it on, the question is: Why is Apple turning it off?
I didnt force anything i dont need it either,i get the same results on or off i dont write to raid just boot disk.If in system profiler is said is working then its working.Apple is turning off to buy SSD from them to pay simple as that.
Well you do force it on... TRIM isn't magically on for 3rd party SSDs.
And your last point makes NO sense. I am saying with Apple SSDs, meaning the SSDs you buy FROM Apple, if you put two of them in software RAID TRIM is disabled.
The question is, why is Apple disabling TRIM? Does it possibly indicate that there is a problem using TRIM in RAID configurations?
Trim supported universally is not an apple or windows technique.Apple dont use his own SSD's .As for the last you said it doesn't make any sense apple computers dont ship with two SSD's.
The internet is full of posts noting that TRIM in RAID configurations is hardly well supported or vetted. It doesn't matter that it is a universal technique. The question is: How well does it work in RAID configurations? You don't have an answer.
Because we all know you can NEVER change the configuration of your machine if it doesn't ship that way from Apple...
I installed two APPLE SSDs (Toshiba), where TRIM is supported by default, in a RAID configuration and lost TRIM.
Quick update.
Two 512GB 830s in RAID 0. Running Mountain Lion GM.
Performance is the same with Trim Enabled. I am still a little skeptical on using Trim with a software RAID 0...
My goodness, 8 second boot from shutdown.
Two 512GB 830s in RAID 0. Running Mountain Lion GM.
Performance is the same with Trim Enabled. I am still a little skeptical on using Trim with a software RAID 0...
My goodness, 8 second boot from shutdown.
Attachments
Last edited:
So I haven't installed my 830 ssd in a mbp but maybe someone might know how to fix this issue, I bought a 64 gig samsung 830 to use as a boot drive in an early 2009 iMac 24 inch. As I understood it, I should be getting SATA II speeds but its not going quite that fast. Currently I'm running at SATA I speeds and I don't think its for lack of supporting sata 2. Anyone have a clue as to why the negotiated link speed is 1.5 gigabits when its capable of 3 gigabits?
Also I have tried searching but I can only find mention of people having this problem with no way of solving it other than getting a Vertex 3 drive and using their linux boot cd
Also I have tried searching but I can only find mention of people having this problem with no way of solving it other than getting a Vertex 3 drive and using their linux boot cd
I don't think it's only Apple. Many controllers (hardware raid) do not support TRIM in RAID mode.
What is your boot time?
Running mine in a mid 2010 13" also.
Have it running in the optibay, I think the main hd location would give me a your write speeds but this is more than enough.
Hardware raid ≠ Software raid.
The latest Intel controllers should be able to pass TRIM now via a software setup, or at least they do on Windows 7. Whether OS X is the same is a different matter.
The latest Intel controllers should be able to pass TRIM now via a software setup, or at least they do on Windows 7. Whether OS X is the same is a different matter.
Is that running off the Optical drives sata port? If it is try Plugging the SSD into the original HDD's sata port. I think the 2009 iMac uses a Nvidia sata chip which is known to force some Sata3 SSD's to run at Sata1 speeds. The OCZ drives have a firmware upgrade that fixes the issue for those drives.
Last edited:
Please don't give me that relax BS.
The point is: There is no indication that these drives can handle TRIM in a software or hardware RAID.
I am aware that the latest Intel controllers are capable of this, however, we aren't talking about Intel.
I installed my 830 256GB yesterday. Works great so far, I didn't expect it to be that fast as my MB Unibody Late 2008 only supports SATA II.
I did a fresh install and used the Migration Assistant to migrate my whole data. As I am planning to remove some bigger files now I'm struggling with the TRIM-question. Although I read that more or less nobody witnessed any problems so far (if having used the terminal commands instead of the trim enabler) I am not 100% sure, whether to turn it on or not.
But no worries - I am not asking for another advice, I now know that everybody should decide for themself. But this question could help me decide:
The garbage, which is left after deleting data, the "ones and zeroes", is it possible to manually clean them up? Or in other words: will the garbage be there forever, if I don't turn TRIM on before deleting data? What if, for instance, I made a CCC-Clone on another Drive, format my SSD and then clone the "backup" to my then formatted SSD?
I did a fresh install and used the Migration Assistant to migrate my whole data. As I am planning to remove some bigger files now I'm struggling with the TRIM-question. Although I read that more or less nobody witnessed any problems so far (if having used the terminal commands instead of the trim enabler) I am not 100% sure, whether to turn it on or not.
But no worries - I am not asking for another advice, I now know that everybody should decide for themself. But this question could help me decide:
The garbage, which is left after deleting data, the "ones and zeroes", is it possible to manually clean them up? Or in other words: will the garbage be there forever, if I don't turn TRIM on before deleting data? What if, for instance, I made a CCC-Clone on another Drive, format my SSD and then clone the "backup" to my then formatted SSD?
I installed my 830 256GB yesterday. Works great so far, I didn't expect it to be that fast as my MB Unibody Late 2008 only supports SATA II.
I did a fresh install and used the Migration Assistant to migrate my whole data. As I am planning to remove some bigger files now I'm struggling with the TRIM-question. Although I read that more or less nobody witnessed any problems so far (if having used the terminal commands instead of the trim enabler) I am not 100% sure, whether to turn it on or not.
But no worries - I am not asking for another advice, I now know that everybody should decide for themself. But this question could help me decide:
The garbage, which is left after deleting data, the "ones and zeroes", is it possible to manually clean them up? Or in other words: will the garbage be there forever, if I don't turn TRIM on before deleting data? What if, for instance, I made a CCC-Clone on another Drive, format my SSD and then clone the "backup" to my then formatted SSD?
I was just as confused as you, so I made a thread about it
calderone provided an excellent response, scroll down to check it out: https://forums.macrumors.com/threads/1407843/
In the end I did turn on TRIM and noticed immediate results in my booting times and overall responsiveness on ML
----------
What is your boot time?
Running mine in a mid 2010 13" also.
Have it running in the optibay, I think the main hd location would give me a your write speeds but this is more than enough.
Image
3 seconds to shutdown
less than 10 seconds to boot into the login screen
Last edited:
Kernel Panics with 2009 MBP
I'm hoping someone here can help. I installed the Samsung 830 in my 2009 13" MBP a few weeks ago. I did a fresh install of Snow Leopard using migration assistant to move my stuff over when I put the SSD in. It seems to work fine except I'm getting occasional kernel panics (grey screen slowly appears with power button forcing a restart) that do not seem to be related to anything I'm doing. They typically happen once every 2 days or so. I don't think it's the RAM. I have 8GB installed now which worked fine with my old stock hard drive. I tried going back to the old 2GB of RAM. It worked okay for a couple of days even though it was really slow with lots of beachballs, but eventually I got a kernel panic forcing a restart.
Drive is fast and I want to like it, but I'm frustrated that my system seems to crash randomly. Could there be a problem with my computer being SATA II and the drive is SATA III? From what I read it should work, but I'm running out of ideas here. I feel like if the hard drive was bad, it would crash more consistently and not after an extended amount of use. I suppose something else could be going on with my computer, although I didn't have a single kernel panic in the 3 years I had the old stock drive in. Any help would be greatly appreciated.
I'm hoping someone here can help. I installed the Samsung 830 in my 2009 13" MBP a few weeks ago. I did a fresh install of Snow Leopard using migration assistant to move my stuff over when I put the SSD in. It seems to work fine except I'm getting occasional kernel panics (grey screen slowly appears with power button forcing a restart) that do not seem to be related to anything I'm doing. They typically happen once every 2 days or so. I don't think it's the RAM. I have 8GB installed now which worked fine with my old stock hard drive. I tried going back to the old 2GB of RAM. It worked okay for a couple of days even though it was really slow with lots of beachballs, but eventually I got a kernel panic forcing a restart.
Drive is fast and I want to like it, but I'm frustrated that my system seems to crash randomly. Could there be a problem with my computer being SATA II and the drive is SATA III? From what I read it should work, but I'm running out of ideas here. I feel like if the hard drive was bad, it would crash more consistently and not after an extended amount of use. I suppose something else could be going on with my computer, although I didn't have a single kernel panic in the 3 years I had the old stock drive in. Any help would be greatly appreciated.
I've had the 512MB version in my 2009 13" MBP with Mountain Lion GM for a week now and not had any kernel panics, nor when I've booted into Win XP on Bootcamp (I cloned old partition from HD to SSD, hence XP and not Win 7)
Thanks for the response. I figured it should work fine with my 2009 MBP. I've just booted into safe mode and I'm going to run it for a few days and see if I still get kernel panics. I want to avoid re-installing OSX if I can help it.