Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Intel 510 Install on 2011 15 inch

G

Guy Mancuso

macrumors 6502a
Original poster
Mar 28, 2009
863
46
Well i read pretty much everything i could find and yes some success and some failures on the 13 and 17 but the 15 seems to be less of a issue. Not sure here but I ordered the darn thing to try. I already have a OWC 200gb Extreme Pro sitting in the optical bay running the OS today and the spinning drive as backup in the hard drive space which will be removed for the Intel 510 to try and get Sata 3.

My game plan open the box install the 510 in hard drive connector space. Boot from the current OS I know i will get initialize the drive which I will do as normal but I will zero it out first than create a partition only maybe 5mgs smaller than the total capacity. This seemed to work for someone. Than I will clone over the OS from the OWC than boot with SMC than pick the new drive and see what gives. just in case I do have 2 OS backups and just did a time machine drive for kicks. I don't normally use time machine

Any additional thoughts to those who have had success on the 15 inch. Figured I ask now before I attack tomorrow just in case I am missing some weird little catch to getting this thing to negotiate to sata 3.

Thanks in advance.
 
I don't think you should zero out SSDs. Can anyone confirm or deny this? I've read that this should be avoided.
 
It's vey unclear whats going on. At least on person has stated that his 510 works great in bootcamp but fails in OS X. So this is something to consider, as it would effect a new 15 inch as well.

But what we know (or think we know): Some work, some don't. Some work and occasionally beachball, some don't want to work at all (or freeze a lot).

Like you said, i've only seen up until now 13" and 17" inch complaints, but there are also working 13" and 17" machines, so it's possible that this would also be the case with 15": Anand had one that worked, etc.

Your move.
 
Tyrion said:
I don't think you should zero out SSDs. Can anyone confirm or deny this? I've read that this should be avoided.
Click to expand...

Zeroing out the drive is actually a good idea in the beginning to find any potential defects with the drive (ie a defective flash chip) -- the write will fail and you'll know something's up. It will cause you to reduce the lifespan of your entire SSD by 1 write cycle, but that's pretty negligible. And it shouldn't affect performance with any modern controller (and especially if you enable TRIM in the OS); most people report that zeroing a heavily used SSD will restore its performance to like-new levels.
 
Well the one reason to zero it out at least in my thinking is maybe there is something on the drive from the factory that I may really want to wipe out anyway. It seems now this is a guess those that zeroed are seeing less issues. Well I'll know soon enough just got my overnight tracking. i will get it all going but might wait for Trim until I get back from trip.
 
smileyborg said:
Zeroing out the drive is actually a good idea in the beginning to find any potential defects with the drive (ie a defective flash chip) -- the write will fail and you'll know something's up. It will cause you to reduce the lifespan of your entire SSD by 1 write cycle, but that's pretty negligible. And it shouldn't affect performance with any modern controller (and especially if you enable TRIM in the OS); most people report that zeroing a heavily used SSD will restore its performance to like-new levels.
Click to expand...

If you zero out the entire drive without TRIM support, you will significantly decrease write performance on the drive, sometimes as much as 50%. If you DO have TRIM support enabled (see here), a zero will make sure the drive has been TRIM'd and all space is clear to write data. If you have not enabled TRIM support by the hack do not zero the drive.

As another data point, I have a Intel 510 120GB in a 2011 13" MBP and it works perfectly. Others with seemingly the same machine and using the same install method I do have problems. (shrug)
 
Hmmm so how do you apply the Trim support before you can zero this drive out to load the OS.

Not sure this will work . Apply Hack to my OWC now than when i CC it over will it stick with the Intel.

Option 2 not sure I can do this . Initialize don't zero and try to apply the hack to that drive than zero than load OS.
 
Why don't you just eschew the zeroing, format to HFS+, install/copy your backup, THEN apply the hack?
 
Yeah, I would skip the zeroing out. In any case, there's no point to try to enable TRIM before installing the OS - seeing how TRIM support is an OS thing so that wouldn't work.

Besides, the chances of you rewriting the part where the OS resides won't happen till the next OS update anyway - and if you hack it, TRIM would have already worked by the time it's needed.
 
Yea i will just skip trim for now and do it later or wait for Apple.


Drive should be here soon so thought I would run X-bench on the OWC 200gb Extreme Pro. Will update this in a few hours and see what changes happen.

Results 407.58
System Info
Xbench Version 1.3
System Version 10.6.7 (10J3250)
Physical RAM 8192 MB
Model MacBookPro8,2
Drive Type OWC Mercury Extreme Pro RE SSD
CPU Test 252.91
GCD Loop 339.43 17.89 Mops/sec
Floating Point Basic 220.18 5.23 Gflop/sec
vecLib FFT 162.45 5.36 Gflop/sec
Floating Point Library 460.32 80.16 Mops/sec
Thread Test 777.97
Computation 737.58 14.94 Mops/sec, 4 threads
Lock Contention 823.04 35.41 Mlocks/sec, 4 threads
Memory Test 581.24
System 595.83
Allocate 765.88 2.81 Malloc/sec
Fill 435.88 21193.38 MB/sec
Copy 696.83 14392.72 MB/sec
Stream 567.35
Copy 552.15 11404.34 MB/sec
Scale 545.38 11267.44 MB/sec
Add 599.26 12765.62 MB/sec
Triad 575.74 12316.57 MB/sec
Quartz Graphics Test 384.45
Line 298.82 19.89 Klines/sec [50% alpha]
Rectangle 390.01 116.44 Krects/sec [50% alpha]
Circle 325.26 26.51 Kcircles/sec [50% alpha]
Bezier 328.14 8.28 Kbeziers/sec [50% alpha]
Text 1027.61 64.28 Kchars/sec
OpenGL Graphics Test 432.55
Spinning Squares 432.55 548.72 frames/sec
User Interface Test 480.35
Elements 480.35 2.20 Krefresh/sec
Disk Test 310.57
Sequential 185.77
Uncached Write 305.41 187.52 MB/sec [4K blocks]
Uncached Write 297.10 168.10 MB/sec [256K blocks]
Uncached Read 82.70 24.20 MB/sec [4K blocks]
Uncached Read 357.04 179.44 MB/sec [256K blocks]
Random 946.36
Uncached Write 1496.20 158.39 MB/sec [4K blocks]
Uncached Write 468.49 149.98 MB/sec [256K blocks]
Uncached Read 2648.36 18.77 MB/sec [4K blocks]
Uncached Read 955.81 177.36 MB/sec [256K blocks]
 
Guy Mancuso said:
Hmmm so how do you apply the Trim support before you can zero this drive out to load the OS.

Not sure this will work . Apply Hack to my OWC now than when i CC it over will it stick with the Intel.

Option 2 not sure I can do this . Initialize don't zero and try to apply the hack to that drive than zero than load OS.
Click to expand...

TRIM is done by the OS. With no OS there can be no TRIM. You need to install the OS then enable the TRIM hack.... then zero the drive's free space. This will give you a clean start.
 
Weaselboy said:
TRIM is done by the OS. With no OS there can be no TRIM. You need to install the OS then enable the TRIM hack.... then zero the drive's free space. This will give you a clean start.
Click to expand...

Sorry if I'm a bit new to this, but how does this work? How do you zero the drive after installing the OS? What is zeroing? Is it just the secure erase (write with zeros 1-pass) option in disc utility?
 
hehe299792458 said:
Sorry if I'm a bit new to this, but how does this work? How do you zero the drive after installing the OS? What is zeroing? Is it just the secure erase (write with zeros 1-pass) option in disc utility?
Click to expand...

Yes exactly. With TRIM enabled using the hack, do a secure erase of free space with Disk Util. That will free up all the open space on the SSD for new writes and theoretically speed things up. In the TRIM hack thread you can see people who have posted test results before and after doing this and it does make a difference.
 
Success.

Just for members here . I loaded the drive in the hard bay slot and than did a immediate SMC before I had the chance to initialize it as soon as I formatted it first I checked the negotiated speed and it was Sata 3 than I made a partition for the drive and left out about 5gb of space so the drive is 245 instead of 250. CCC from the OWC drive ( okay fast as heck ) than went to system preferences and selected the Intel as the boot drive and all seems okay for now.

Doing the X bench test it did score a little better but some numbers are better than others as well and some much lower. It is the way they have this drive setup and actually I lost some time in processing raw files. Now I will do that again, I do believe in a little seasoning on drives. LOL

But works and i am running Sata 3. Now I will recreate the OWC drive in 2 partitions one 80gb space for a backup OS and the rest for storage. Eventually I will have to see what OWC Sata 3 drives will look like and may make the switch but for now this looks good

Okay here is the Intel 510 X bench


Results 428.53
System Info
Xbench Version 1.3
System Version 10.6.7 (10J3250)
Physical RAM 8192 MB
Model MacBookPro8,2
Drive Type INTEL SSDSC2MH250A2
CPU Test 256.67
GCD Loop 342.33 18.04 Mops/sec
Floating Point Basic 224.45 5.33 Gflop/sec
vecLib FFT 164.51 5.43 Gflop/sec
Floating Point Library 469.74 81.80 Mops/sec
Thread Test 893.77
Computation 862.09 17.46 Mops/sec, 4 threads
Lock Contention 927.86 39.92 Mlocks/sec, 4 threads
Memory Test 602.49
System 637.48
Allocate 966.24 3.55 Malloc/sec
Fill 444.91 21632.74 MB/sec
Copy 702.51 14510.05 MB/sec
Stream 571.14
Copy 559.32 11552.57 MB/sec
Scale 546.16 11283.54 MB/sec
Add 601.82 12820.08 MB/sec
Triad 580.36 12415.31 MB/sec
Quartz Graphics Test 394.06
Line 296.22 19.72 Klines/sec [50% alpha]
Rectangle 402.49 120.17 Krects/sec [50% alpha]
Circle 336.01 27.39 Kcircles/sec [50% alpha]
Bezier 346.45 8.74 Kbeziers/sec [50% alpha]
Text 1035.50 64.78 Kchars/sec
OpenGL Graphics Test 398.13
Spinning Squares 398.13 505.05 frames/sec
User Interface Test 477.71
Elements 477.71 2.19 Krefresh/sec
Disk Test 397.22
Sequential 258.68
Uncached Write 299.90 184.13 MB/sec [4K blocks]
Uncached Write 472.26 267.20 MB/sec [256K blocks]
Uncached Read 117.49 34.38 MB/sec [4K blocks]
Uncached Read 666.73 335.10 MB/sec [256K blocks]
Random 855.34
Uncached Write 466.19 49.35 MB/sec [4K blocks]
Uncached Write 859.58 275.18 MB/sec [256K blocks]
Uncached Read 2067.55 14.65 MB/sec [4K blocks]
Uncached Read 1130.70 209.81 MB/sec [256K blocks]


And here is the OWC X bench


Results 407.58
System Info
Xbench Version 1.3
System Version 10.6.7 (10J3250)
Physical RAM 8192 MB
Model MacBookPro8,2
Drive Type OWC Mercury Extreme Pro RE SSD
CPU Test 252.91
GCD Loop 339.43 17.89 Mops/sec
Floating Point Basic 220.18 5.23 Gflop/sec
vecLib FFT 162.45 5.36 Gflop/sec
Floating Point Library 460.32 80.16 Mops/sec
Thread Test 777.97
Computation 737.58 14.94 Mops/sec, 4 threads
Lock Contention 823.04 35.41 Mlocks/sec, 4 threads
Memory Test 581.24
System 595.83
Allocate 765.88 2.81 Malloc/sec
Fill 435.88 21193.38 MB/sec
Copy 696.83 14392.72 MB/sec
Stream 567.35
Copy 552.15 11404.34 MB/sec
Scale 545.38 11267.44 MB/sec
Add 599.26 12765.62 MB/sec
Triad 575.74 12316.57 MB/sec
Quartz Graphics Test 384.45
Line 298.82 19.89 Klines/sec [50% alpha]
Rectangle 390.01 116.44 Krects/sec [50% alpha]
Circle 325.26 26.51 Kcircles/sec [50% alpha]
Bezier 328.14 8.28 Kbeziers/sec [50% alpha]
Text 1027.61 64.28 Kchars/sec
OpenGL Graphics Test 432.55
Spinning Squares 432.55 548.72 frames/sec
User Interface Test 480.35
Elements 480.35 2.20 Krefresh/sec
Disk Test 310.57
Sequential 185.77
Uncached Write 305.41 187.52 MB/sec [4K blocks]
Uncached Write 297.10 168.10 MB/sec [256K blocks]
Uncached Read 82.70 24.20 MB/sec [4K blocks]
Uncached Read 357.04 179.44 MB/sec [256K blocks]
Random 946.36
Uncached Write 1496.20 158.39 MB/sec [4K blocks]
Uncached Write 468.49 149.98 MB/sec [256K blocks]
Uncached Read 2648.36 18.77 MB/sec [4K blocks]
Uncached Read 955.81 177.36 MB/sec [256K blocks]
 
Oh one thing I did notice when on initial boot of drive the fans kicked in hard and temps went up for a period of time ( after OS install). Might be just working itself in with some processes. I shut down after things settled down than rebooted and all is well. Don't tell anyone but my temp went down at idle 2-4 C also. Must be the spinner not being in the box now
 
Guy Mancuso said:
Oh one thing I did notice when on initial boot of drive the fans kicked in hard and temps went up for a period of time ( after OS install). Might be just working itself in with some processes. I shut down after things settled down than rebooted and all is well. Don't tell anyone but my temp went down at idle 2-4 C also. Must be the spinner not being in the box now
Click to expand...

That's initial hard work was most likely the initial Spotlight indexing.

The same thing happens in with the Windows Search in a VMware or Parallels virtual machine.
 
Weaselboy said:
Yes exactly. With TRIM enabled using the hack, do a secure erase of free space with Disk Util. That will free up all the open space on the SSD for new writes and theoretically speed things up. In the TRIM hack thread you can see people who have posted test results before and after doing this and it does make a difference.
Click to expand...

Pardon my ignorance, but how does this work exactly? For example, do I do the TRIM hack first or zero out the drive first? And what if I partitioned the drive in 2? I do zero out both partitions, or just the OS partition?

How will TRIM ensure sustained speed after use? Do I have to zero out my drive every time I want TRIM to do its thing?
 
hehe299792458 said:
Pardon my ignorance, but how does this work exactly? For example, do I do the TRIM hack first or zero out the drive first? And what if I partitioned the drive in 2? I do zero out both partitions, or just the OS partition?

How will TRIM ensure sustained speed after use? Do I have to zero out my drive every time I want TRIM to do its thing?
Click to expand...

When you buy a new SSD each cell on the drive is marked as unused so data can quickly be written there. When you write data to a cell then delete that data, the cell is marked by the SSD as available for use but the data is not really deleted from the cell until that cell is written to again. So the second time that same cell is written to the old data has to be deleted before the new data can go there... and this slows down the SSD's write speed. This is how things work without TRIM. If you don't write a lot of data, it may take a long time before each cell is written to once and you won't notice write performance drop much. If you write a lot if data, write performance can drop more quickly.

Now add TRIM to the equation. What TRIM does is at the OS Level tell the SSD a file delete has occurred and not only makes a cell available for use but ALSO deletes the data from the cell. In this way all available SSD memory cells are "fresh" like when the drive was new. When data needs to be rewritten to one of these cells there is only a write operation and not the delete first then write operation I described earlier. Much faster.

Okay... so ideally what you want is all available SSD memory cells to have no old data in them so they can be quickly written to, and TRIM does this. But TRIM can only work going forward in time from when it is activated. SSD cells used prior to TRIM activation are not "fresh" and will still require the delete then write steps to use them, and they will be slow.

So what you want to do on a used SSD is partition and format the SSD then install your OS and data and activate TRIM. Then if you run the Disk Util erase free space command it fills every last cell on the SSD with data and then deletes that data making the free space on the drive in a fresh unused state and available for fast write access. You will want to erase free space on any partition on the SSD for the same reason.

There is nothing special about the erase free space Disk Util that causes this. All it is doing is writing a large file to the SSD then erasing it... and this causes the drive to be TRIM'd like you want. You could accomplish the same thing by making a large file and just copy it over and over until the drive is full then delete all the file you made. The objection is to use each SSD cell under TRIM then delete the data under TRIM.

You want to keep TRIM activated long term because without it continued file creation and deletion will set the SSD cells back to "available but used" again and this slows write operations.

There is no need to "zero" the drive again after the first time if you leave TRIM activated as TRIM will keep the SSD cell states as they should be in the future.
 
Weaselboy said:
When you buy a new SSD each cell on the drive is marked as unused so data can quickly be written there. When you write data to a cell then delete that data, the cell is marked by the SSD as available for use but the data is not really deleted from the cell until that cell is written to again. So the second time that same cell is written to the old data has to be deleted before the new data can go there... and this slows down the SSD's write speed. This is how things work without TRIM. If you don't write a lot of data, it may take a long time before each cell is written to once and you won't notice write performance drop much. If you write a lot if data, write performance can drop more quickly.

Now add TRIM to the equation. What TRIM does is at the OS Level tell the SSD a file delete has occurred and not only makes a cell available for use but ALSO deletes the data from the cell. In this way all available SSD memory cells are "fresh" like when the drive was new. When data needs to be rewritten to one of these cells there is only a write operation and not the delete first then write operation I described earlier. Much faster.

Okay... so ideally what you want is all available SSD memory cells to have no old data in them so they can be quickly written to, and TRIM does this. But TRIM can only work going forward in time from when it is activated. SSD cells used prior to TRIM activation are not "fresh" and will still require the delete then write steps to use them, and they will be slow.

So what you want to do on a used SSD is partition and format the SSD then install your OS and data and activate TRIM. Then if you run the Disk Util erase free space command it fills every last cell on the SSD with data and then deletes that data making the free space on the drive in a fresh unused state and available for fast write access. You will want to erase free space on any partition on the SSD for the same reason.

There is nothing special about the erase free space Disk Util that causes this. All it is doing is writing a large file to the SSD then erasing it... and this causes the drive to be TRIM'd like you want. You could accomplish the same thing by making a large file and just copy it over and over until the drive is full then delete all the file you made. The objection is to use each SSD cell under TRIM then delete the data under TRIM.

You want to keep TRIM activated long term because without it continued file creation and deletion will set the SSD cells back to "available but used" again and this slows write operations.

There is no need to "zero" the drive again after the first time if you leave TRIM activated as TRIM will keep the SSD cell states as they should be in the future.
Click to expand...


Wow! What a detailed and wonderful post. Thanks a lot. This should really be a sticky somewhere.
 
hehe299792458 said:
Wow! What a detailed and wonderful post. Thanks a lot. This should really be a sticky somewhere.
Click to expand...

Glad it was helpful.

I should add many SSD's are touted as having firmware that endeavors to do what TRIM does without an OS that uses TRIM. I think the jury is still out on weather these SSD firmware solutions work as well as TRIM.
 
It seems like a nice drive , maybe not the fastest one coming out with Sata 3 but I think a safe bet considering some of the others. If anything when OWC comes out with there Sata 3 i will look at it but this one is very capable of great speed.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back