Manuel_B Posted February 14, 2011 Share Posted February 14, 2011 Hello, I just wanted to write some experiences. I bought 2 weeks ago for about 550 € the P256 from Corsair, because a colleague of mine said that SSD makes working a lot faster. I didn't wanted to make the change during the week because I didn't want to take the risk that I break something. So I made the switch on the weekend. First I created a fresh time machine backup on my Time Capsule 1TB. Afterwards I opened my MacBook and removed the old 320 GByte Hardrive. I have about 220 GByte of date on this disc. I didn't had the correct screw driver to remove the four screw for holding the disc and put the on the new SSD so I just skipped them. After connecting the SSD I booted from my Snow Leopard 10.6.3 Install DVD which I ordered a week ago from the Apple Store. I created an HFS journaled file system on the SSD disc and then I restored the backup. The restoring took 8 hours. I used a directly wired connection from my mac book to my time capsule. This was already a real bad experience and I blame apple for that. I let the restoring run over the night. Afterwards I tried to reboot my Mac but the spinner freezed and after half an hour waiting I restarted in single user mode. The is an issues with an 10.6.6 Time Machine Backup: dyld: Symbol not found: _CSSMOID_APPLE_TP_MACAPPSTORE_RECEIPT You can read the details here: http://discussions.apple.com/thread.jspa?threadID=2740183&tstart=30 So after I fixed that. My Mac booted again. So I wanted to make some benchmarks. From the specs the new drive should be about 10 times faster then my old one. Actually if it would have been 5 times faster it would have been already quite cool. The old drive had this result sudo dd if=/dev/disk0 of=/dev/zero bs=4096 count=40960 40960+0 records in 40960+0 records out 167772160 bytes transferred in 7.949526 secs (21104674 bytes/sec) About 20 MB/s read performance with block size 4k. The new drive has the following: sudo dd if=/dev/disk0 of=/dev/zero bs=4096 count=40960 40960+0 records in 40960+0 records out 167772160 bytes transferred in 5.415514 secs (30979914 bytes/sec) About 30 MB/s read performance with block size 4k. Compared to the promised 480 MB/s this is nothing. All in all my spotlight is not working anymore and the Installer crashed during reinstalling 10.6.6. I am quite disappointed with this experience and I don't recommend to anyone to use a SSD disc in a MacBook Pro. It is more Apple fault then Corsairs and I posted a similar reported with I cited in the beginning. I hope this post helps some people and saves some debugging time. Link to comment Share on other sites More sharing options...
Manuel_B Posted February 14, 2011 Author Share Posted February 14, 2011 Here are some more detailed Benchmark Results. Actually it is not that bad but still disappointing :-) http://db.xbench.com/merge.xhtml?doc1=505242 Link to comment Share on other sites More sharing options...
Thorsten753 Posted February 14, 2011 Share Posted February 14, 2011 So just to understand a bit more. Why is this Apple Fault? Should they have proper drivers for this specific harddrive? Or hwere do you think the problem lies? Don't Macs work great with the drives that come factory installed? Oh and 210.56 MB/sec does not seem that bad? Do you know if the Macbook Pro uses Sata 3 or SATA 2? If its SATA 2 it might be quite good considering overhead and stuff. Link to comment Share on other sites More sharing options...
Manuel_B Posted February 14, 2011 Author Share Posted February 14, 2011 Hi, thanks for the fast answer @Thorsten753. Actually it took over 8 hours to restore the backup and afterwards it didn't work that frustrated me a lot. Apple should be more liberal in providing specs about their hardware and drivers. They should give other smart people the possibility to implement great stuff on their hardware plattform. Further my Spotlight is still crashing with the following message: Feb 14 00:01:37 Manuel-Blechschmidts-MacBook-Pro com.apple.launchd[1] (0x10011ac30.mach_init.mdworker[1500]): Job appears to have crashed: Segmentation fault Feb 14 00:01:37 Manuel-Blechschmidts-MacBook-Pro com.apple.ReportCrash.Root[1499]: 2011-02-14 00:01:37.332 ReportCrash[1499:1407] Saved crash report for mdworker[1500] version ??? (???) to /Library/Logs/DiagnosticReports/mdworker_2011-02-14-000137_localhost.crash For someone who is interested here is the complete crash file: $ cat /Library/Logs/DiagnosticReports/mdworker_2011-02-14-000137_localhost.crash Process: mdworker [1500] Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Support/mdworker Identifier: mdworker Version: ??? (???) Code Type: X86-64 (Native) Parent Process: launchd [1] Date/Time: 2011-02-14 00:01:37.091 +0100 OS Version: Mac OS X 10.6.6 (10J567) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000001c9e8b4db Crashed Thread: 3 Thread 0: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x00000001006d92da mach_msg_trap + 10 1 libSystem.B.dylib 0x00000001006d994d mach_msg + 59 2 com.apple.CoreFoundation 0x00007fff88e34932 __CFRunLoopRun + 1698 3 com.apple.CoreFoundation 0x00007fff88e33dbf CFRunLoopRunSpecific + 575 4 com.apple.CoreFoundation 0x00007fff88e33b46 CFRunLoopRun + 70 5 mdworker 0x0000000100008f01 0x100000000 + 36609 6 mdworker 0x0000000100001b88 0x100000000 + 7048 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x00000001006f216a kevent + 10 1 libSystem.B.dylib 0x00000001006f403d _dispatch_mgr_invoke + 154 2 libSystem.B.dylib 0x00000001006f3d14 _dispatch_queue_invoke + 185 3 libSystem.B.dylib 0x00000001006f383e _dispatch_worker_thread2 + 252 4 libSystem.B.dylib 0x00000001006f3168 _pthread_wqthread + 353 5 libSystem.B.dylib 0x00000001006f3005 start_wqthread + 13 Thread 2: 0 libSystem.B.dylib 0x00000001006f2f8a __workq_kernreturn + 10 1 libSystem.B.dylib 0x00000001006f339c _pthread_wqthread + 917 2 libSystem.B.dylib 0x00000001006f3005 start_wqthread + 13 Thread 3 Crashed: 0 ...ple.CoreServices.CarbonCore 0x00007fff84aca24b CSStoreGetUnit + 84 1 com.apple.LaunchServices 0x0000000101100467 _LSBundleFindWithNode + 544 2 com.apple.LaunchServices 0x0000000101104bf0 _LSGetNodePkgInfo(LSContext*, FSNode*, LSBundleData const**, FSNodePkgInfo*) + 116 3 com.apple.LaunchServices 0x0000000101103487 _LSTypeDataInitForNode(LSContext*, LSTypeData*, FSNode*, __CFString const*, unsigned int) + 410 4 com.apple.LaunchServices 0x0000000101103222 _LSCopyNodeAttribute_ContentType(LSNodeAttributeStateCache*) + 76 5 com.apple.LaunchServices 0x000000010110b824 _LSCopyNodeAttributes + 237 6 com.apple.LaunchServices 0x000000010110b700 _LSCopyItemAttributesForRefInfoWithOptions + 267 7 mdworker 0x0000000100007541 0x100000000 + 30017 8 mdworker 0x0000000100005c68 0x100000000 + 23656 9 mdworker 0x0000000100009ec1 0x100000000 + 40641 10 libSystem.B.dylib 0x0000000100712536 _pthread_start + 331 11 libSystem.B.dylib 0x00000001007123e9 thread_start + 13 Thread 3 crashed with X86 Thread State (64-bit): rax: 0x00000000c66124df rbx: 0x0000000000000000 rcx: 0x0000000103879000 rdx: 0x0000000000000000 rdi: 0x00000000bc010000 rsi: 0x00000000df2461c6 rbp: 0x0000000102e7ed70 rsp: 0x0000000102e7ed50 r8: 0x0000000102e7edfc r9: 0x0000000000000000 r10: 0x0000000000001200 r11: 0x0000000000000206 r12: 0x00000001c9e8b4df r13: 0x0000000102a01160 r14: 0x0000000000000000 r15: 0x0000000102e7edfc rip: 0x00007fff84aca24b rfl: 0x0000000000010246 cr2: 0x00000001c9e8b4db Binary Images: 0x100000000 - 0x10003cfff mdworker ??? (???) <A3C885F6-74AF-860E-2A06-94575B9ECCCE> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker 0x100050000 - 0x1002d3ff7 com.apple.Foundation 6.6.4 (751.42) <AF1E3050-3503-8714-8274-EA6BD6BE8A22> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x10044b000 - 0x10044bff7 com.apple.CoreServices 44 (44) <DC7400FB-851E-7B8A-5BF6-6F50094302FB> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x10044e000 - 0x100533fef com.apple.DesktopServices 1.5.9 (1.5.9) <27890B2C-0CD2-7C27-9D0C-D5952C5E8438> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x100582000 - 0x100699fef libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <B2FB9DA8-6EC9-FFBC-C919-C022B9CBEB73> /usr/lib/libxml2.2.dylib 0x1006c2000 - 0x1006d3ff7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <97019C74-161A-3488-41EC-A6CA8738418C> /usr/lib/libz.1.dylib 0x1006d8000 - 0x100899fff libSystem.B.dylib 125.2.1 (compatibility 1.0.0) <F00A8B2F-84A0-0868-1047-3A13F9114864> /usr/lib/libSystem.B.dylib 0x10092a000 - 0x1009e0fff libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <99CB3A0F-64CF-1D16-70CD-8AED2EF06C30> /usr/lib/libobjc.A.dylib 0x1009f4000 - 0x100a54fe7 com.apple.framework.IOKit 2.0 (???) <D107CB8A-5182-3AC4-35D0-07068A695C05> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x100a78000 - 0x100ac4fff libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib 0x100ad1000 - 0x100c8ffff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <781E7B63-2AD0-E9BA-927C-4521DB616D02> /usr/lib/libicucore.A.dylib 0x100cfe000 - 0x100d0cff7 libkxld.dylib ??? (???) <27713C39-0E51-8F5A-877B-C5539C96A520> /usr/lib/system/libkxld.dylib 0x100d10000 - 0x100dc9fff libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib 0x100dd9000 - 0x100eabfe7 com.apple.CFNetwork 454.11.5 (454.11.5) <5D68598D-C138-C8B6-B6AC-B1F48B01E021> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x100f1e000 - 0x100f5ffff com.apple.SystemConfiguration 1.10.5 (1.10.2) <FB39F09C-57BB-D8CC-348D-93E00C602F7D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x100f83000 - 0x101040ff7 com.apple.CoreServices.OSServices 357 (357) <7B22626F-D544-1955-CC53-240F4CACEB4A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x10109a000 - 0x1010d5fff com.apple.AE 496.4 (496.4) <55AAD5CA-7160-7899-1C68-562ED8160DF7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x1010ef000 - 0x10118ffff com.apple.LaunchServices 362.2 (362.2) <A8EDC37C-1D40-5ED0-49BE-90EF110A6B3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x1011d5000 - 0x1011fdfff com.apple.DictionaryServices 1.1.2 (1.1.2) <E9269069-93FA-2B71-F9BA-FDDD23C4A65E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x101217000 - 0x101226fff com.apple.NetFS 3.2.1 (3.2.1) <E5D33870-27D2-E50B-9B35-16AA50369733> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x10122f000 - 0x1013e6fef com.apple.ImageIO.framework 3.0.4 (3.0.4) <EE9DFBD6-6354-7C5A-F4C7-5FF782A7D992> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x10144c000 - 0x1014cafff com.apple.CoreText 3.5.0 (???) <4D5C7932-293B-17FF-7309-B580BB1953EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreText.framework/Versions/A/CoreText 0x101508000 - 0x1015a2fff com.apple.ApplicationServices.ATS 4.4 (???) <395849EE-244A-7323-6CBA-E71E3B722984> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x1015cb000 - 0x101680fe7 com.apple.ColorSync 4.6.3 (4.6.3) <5A7360A8-D495-1E8D-C4B4-A363AF989ADE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x1016bd000 - 0x10170fff7 com.apple.HIServices 1.8.2 (???) <7C91D07D-FA20-0882-632F-0CAE4FAC2B79> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x10173b000 - 0x101750ff7 com.apple.LangAnalysis 1.6.6 (1.6.6) <1AE1FE8F-2204-4410-C94E-0E93B003BEDA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x10175e000 - 0x1017e3ff7 com.apple.print.framework.PrintCore 6.3 (312.7) <CDFE82DD-D811-A091-179F-6E76069B432D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x101819000 - 0x10185afef com.apple.QD 3.36 (???) <5DC41E81-32C9-65B2-5528-B33E934D5BB4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x101872000 - 0x101872ff7 com.apple.Accelerate 1.6 (Accelerate 1.6) <15DF8B4A-96B2-CB4E-368D-DEC7DF6B62BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x101875000 - 0x1018c4fef libTIFF.dylib ??? (???) <176B52ED-4F6C-D0C2-EABC-C032BFC3DFAA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x1018d1000 - 0x1018d6fff libGIF.dylib ??? (???) <A7BF2D68-F489-720C-E5A9-DC2B24DC5A21> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x1018db000 - 0x1018f8ff7 libPng.dylib ??? (???) <667C3883-32A5-CCCC-8624-972B5DFD8EA4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x101900000 - 0x101902fff libRadiance.dylib ??? (???) <6C974488-62D2-71BA-A45E-C764A0AF7354> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x101906000 - 0x10192cfe7 libJPEG.dylib ??? (???) <DFA5DAC2-D1C6-D5ED-F95D-AC185E98B6E7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x101934000 - 0x101934ff7 com.apple.Accelerate.vecLib 3.6 (vecLib 3.6) <4CCE5D69-F1B3-8FD3-1483-E0271DB2CCF3> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x101937000 - 0x10197fff7 libvDSP.dylib 268.0.1 (compatibility 1.0.0) <98FC4457-F405-0262-00F7-56119CA107B6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x101987000 - 0x1019f1fe7 libvMisc.dylib 268.0.1 (compatibility 1.0.0) <AF0EA96D-000F-8C12-B952-CB7E00566E08> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x1019fb000 - 0x101b1cfe7 libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <48AEAFE1-21F4-B3C8-4199-35AD5E8D0613> /usr/lib/libcrypto.0.9.8.dylib 0x101b83000 - 0x101b84ff7 com.apple.TrustEvaluationAgent 1.1 (1) <5952A9FA-BC2B-16EF-91A7-43902A5C07B6> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x101b88000 - 0x101c49fe7 libFontParser.dylib ??? (???) <8B12D37E-3A95-5A73-509C-3AA991E0C546> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x101d40000 - 0x101d79fef libcups.2.dylib 2.8.0 (compatibility 2.0.0) <561D0DCB-47AD-A12C-9066-70E4CBAD331C> /usr/lib/libcups.2.dylib 0x101d88000 - 0x101e37fff edu.mit.Kerberos 6.5.10 (6.5.10) <6A159CD8-5C02-4528-C36F-6AFBFD61576B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x101e5d000 - 0x101e7efff libresolv.9.dylib 41.0.0 (compatibility 1.0.0) <9F322F47-0584-CB7D-5B73-9EBD670851CD> /usr/lib/libresolv.9.dylib 0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld 0x7fff82649000 - 0x7fff828cffff com.apple.security 6.1.1 (37594) <1B4E1ABD-1BB3-DA49-F574-0EEB23E73C6A> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x7fff831a5000 - 0x7fff831efff7 com.apple.Metadata 10.6.3 (507.15) <5170FCE0-ED6C-2E3E-AB28-1DDE3F628FC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x7fff84529000 - 0x7fff8452fff7 com.apple.DiskArbitration 2.3 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x7fff84abf000 - 0x7fff84df3fff com.apple.CoreServices.CarbonCore 861.23 (861.23) <96465459-6536-3FD7-7504-B59D0390EEC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x7fff8541f000 - 0x7fff854affff com.apple.SearchKit 1.3.0 (1.3.0) <4175DC31-1506-228A-08FD-C704AC9DF642> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x7fff854b0000 - 0x7fff858f3fef libLAPACK.dylib 219.0.0 (compatibility 1.0.0) <0CC61C98-FF51-67B3-F3D8-C5E430C201A9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x7fff85903000 - 0x7fff85980fef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib 0x7fff861dc000 - 0x7fff861e0ff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib 0x7fff8682a000 - 0x7fff86f2706f com.apple.CoreGraphics 1.545.0 (???) <356D59D6-1DD1-8BFF-F9B3-1CE51D2F1EC7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x7fff87197000 - 0x7fff879a1fe7 libBLAS.dylib 219.0.0 (compatibility 1.0.0) <FC941ECB-71D0-FAE3-DCBF-C5A619E594B8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x7fff87b9b000 - 0x7fff87c75ff7 com.apple.vImage 4.0 (4.0) <354F34BF-B221-A3C9-2CA7-9BE5E14AD5AD> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x7fff87d46000 - 0x7fff87d46ff7 com.apple.ApplicationServices 38 (38) <10A0B9E9-4988-03D4-FC56-DDE231A02C63> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x7fff8812b000 - 0x7fff88156ff7 libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <87A0B228-B24A-C426-C3FB-B40D7258DD49> /usr/lib/libxslt.1.dylib 0x7fff88daf000 - 0x7fff88dc5fef libbsm.0.dylib ??? (???) <42D3023A-A1F7-4121-6417-FCC6B51B3E90> /usr/lib/libbsm.0.dylib 0x7fff88de8000 - 0x7fff88f5ffe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff890c8000 - 0x7fff890dcff7 com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <621B7415-A0B9-07A7-F313-36BEEDD7B132> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <F00A8B2F-84A0-0868-1047-3A13F9114864> /usr/lib/libSystem.B.dylib I would expect that my Mac Book Pro runs with SATA II at least it says the following in the system profiler (About this Mac -> More Info): NVidia MCP79 AHCI: Vendor: NVidia Product: MCP79 AHCI Link Speed: 3 Gigabit Negotiated Link Speed: 3 Gigabit Description: AHCI Version 1.20 Supported Corsair Performance3 SSD: Capacity: 256,06 GB (256.060.514.304 bytes) Model: Corsair Performance3 SSD Revision: 1.0 Serial Number: 1101810201000342002A 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 Volumes: Capacity: 209,7 MB (209.715.200 bytes) Writable: Yes BSD Name: disk0s1 Macintosh HD: Capacity: 255,72 GB (255.716.540.416 bytes) Available: 55,09 GB (55.086.321.664 bytes) Writable: Yes File System: Journaled HFS+ BSD Name: disk0s2 Mount Point: / Actually I just wanted to be as concrete as possible but the SSD did not met my expectations. /Manuel Link to comment Share on other sites More sharing options...
Synbios Posted February 15, 2011 Share Posted February 15, 2011 Of course the drive does not meet specifications, the performance 3 drive is a SATA III aka SATA 6.0 Gbps drive and you're running it on SATA II and on top of that it's in a laptop which overall may have slower performance than a desktop counterpart. You can't expect much more. Your first test with the command line transfer is not a true test because the drive performs at different speeds for different tasks and data amounts (it actually peforms larger file transfers faster). If you can somehow run ATTO on your system, you will see what I mean and we'll have a better understanding of how fast your drive is running with respect to specification. The link for the ATTO benchmark tool is on the left, I don't know if there is a Macintosh version but you can look for one or run a dual boot configuration and try it on Windows if possible. Link to comment Share on other sites More sharing options...
Manuel_B Posted February 16, 2011 Author Share Posted February 16, 2011 Hello Synbios, thanks for your reply it is very appreciated. Actually I agree that the performance is ok. I also ran Xbench which gave a read performance of 210.56 MB/sec [256K blocks]. At the moment I also have some problems with broken files for example in my Windows XP VM which is running under Paralles. The conclusion for me is that I should only buy and use an SSD on new computer with an SATA III connection and shouldn't try again to replace an old hard disc. I am quite satisfied with Corsair. I bough 8 GByte of RAM from them and it was the cheapest and I had no problems with them at all. /Manuel Link to comment Share on other sites More sharing options...
Manuel_B Posted February 18, 2011 Author Share Posted February 18, 2011 Seems that things are getting back to normal. I just switched on spotlight again: sudo mdutil -i on -a And magically mdworker is not crashing anymore. So if someone has similar problems just wait some days and then try again. Seems that the SSD needs some time to warm up ;): Link to comment Share on other sites More sharing options...
Manuel_B Posted February 24, 2011 Author Share Posted February 24, 2011 To solve the crashes I called Apple Support, they told me to reinstall Mac OS X 10.6.3 from the DVD and update afterwards with the Combo Update to 10.6.6 This worked No crashes anymore. The following applications were affected by crashes: Java Apps (Magic Draw PE 17.0)iCaliTunesInstallermdworker from Spotlight Link to comment Share on other sites More sharing options...
Manuel_B Posted February 25, 2011 Author Share Posted February 25, 2011 The new SSD just died and I am waiting for an RMA number from Corsair. I double checked the dying with an apple retailer. Will report further experiences soon. I am quite excited how long it will take until I get a new SSD. If an Corsair Employee is reading this, my case number is: 1926458 . If you replace my disc very fast I will write a good rewrite ;): Link to comment Share on other sites More sharing options...
oskare Posted March 5, 2011 Share Posted March 5, 2011 Hi I have a new Macbook Pro early 11 (Sandy Bridge) and a Corsair Performance 3 128G disk. I first tried to install my fresh disk via the cd but got crashes after about 30% two tries in a row. I then when for restore via Time Machine and that worked. Now i get freezing crashes, the wheel starts to spinn and I can't nothing except move the wheel mouse pointer around. Seems like it might be related to the problem you solved above? But the link is boken so I can find the page with how to solve it. Can you update it? Any one else that got these problems? Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted March 9, 2011 Corsair Employee Share Posted March 9, 2011 Can you test the drive on another system preferably a Windows system? Also I would suggest you conatct Apple directly and see if they have tested any S-ATA III SSD drives. Link to comment Share on other sites More sharing options...
oskare Posted March 9, 2011 Share Posted March 9, 2011 I have no windows system, or any windows license. Can contact apple about the SATA III compatibility. Is there any what to force SATA II to check if this is the problem? The whole idea why i went fort the corsair disk was that it was SATA III and the sandy bridge supported it but the apple provieded SSD where slow, expensive and didn't support SATA III. I have seen lot less of the freeze since i disabled spotlight indexing, and have only gotten it once in 3 days now. Still to often though. Have you tested the disk with mac computers before you released it? Or only windows? Link to comment Share on other sites More sharing options...
guitrein Posted March 9, 2011 Share Posted March 9, 2011 I have no windows system, or any windows license. Can contact apple about the SATA III compatibility. Is there any what to force SATA II to check if this is the problem? The whole idea why i went fort the corsair disk was that it was SATA III and the sandy bridge supported it but the apple provieded SSD where slow, expensive and didn't support SATA III. I have seen lot less of the freeze since i disabled spotlight indexing, and have only gotten it once in 3 days now. Still to often though. Have you tested the disk with mac computers before you released it? Or only windows? Hello! Well, I have a Corsair F240 (SATA II) in my new Macbook Pro 13" early 2011 and I haven't noticed any problem so far apart from the classical hibernation one. Everything is working just fine. Also, I setup some things on my Mac OS X in order to improve the SSD performance and reliability. Maybe you should try it. Check the link: Mac OS X Tips and Tweaks Link to comment Share on other sites More sharing options...
oskare Posted March 12, 2011 Share Posted March 12, 2011 Hi These were the things recommended, and I have put answers to each: 1) Disable sleeping mode (hibernation) Not a problem with my disk and I really like the hibernation so I havent disabled it. 2) Disable hard drive sleep As far as I know the SSDs uses less power when put to sleep? From around 1,5w to 0,5w. Also never had a problem when I suspect the disk was about or coming back to sleep. 3) Disable sudden motion sensor This sounds like a good idea, how ever does any one know if this is disabled on MacBooks that comes with a SSD pre-installed? Haven done it yet however 4) Enable noatime for SSD filesystems Don't really see how this would help but could be worth testing. Haven't done it yet. 5) Disable Spotlight This one I did and it seems like it help. Since I did it I have only seen the freezing issue once in 6 days. That was when working with massive picture import in Aperture and while editing images at the same time. In general I suspect that my freeze might be related to writing to a place on the disk that has never been used. I now added some large files and duplicated them and then removed them. I'll get back in a couple of days and give you all more updates. Isn't there any one else that has a performance 3 disk in a macbook that can let us know how it works for them? Link to comment Share on other sites More sharing options...
eecue Posted March 14, 2011 Share Posted March 14, 2011 I had the same exact problem with my MBP (new model). I did what you did (actually I used disk tools to restore my drive over, after putting the old one in a usb enclosure). I was having the crashes randomly with kernel panics. I did two things, not sure which fixed it exactly. First I completely erased all spotlight data and regenerated all my spotlight indexes. That seemed to have fixed the problem for the most part. I did have another crash, but after uninstalling Little Snitch that problem went away as well. A few times after putting my laptop to sleep (i disabled the deep sleep hibernate, per the forum recommendations) my laptop woke up with the 3 beeps of death (no ram present). Uninstalling little snitch seems to have fixed this, but who knows. Link to comment Share on other sites More sharing options...
oskare Posted March 14, 2011 Share Posted March 14, 2011 Mine has been running fine for 8 days now. The only thing i did was turn off spotlight indexing. I just tried to turn it back on and it froze once again. So it's definitely related to that. With the spotlight index turned off it has crashed once and that was when doing heavy import and picture editing in Aperture. Haven been able to repeat that though. Hardmac has a theory that it's related to the motion sensor in this article. http://www.hardmac.com/news/2011/03/08/compatibility-problem-between-some-2011-macbook-pro-and-the-c300-maybe-a-solution?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+hardmac+%28HardMac.com%29 Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted March 15, 2011 Corsair Employee Share Posted March 15, 2011 Thank you for the information! Link to comment Share on other sites More sharing options...
Manuel_B Posted April 4, 2011 Author Share Posted April 4, 2011 Hi guys, I am still waiting for my RMA number and I just wrote an email to RMA@corsair.com. Let's see what will happen. /Manuel Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted April 4, 2011 Corsair Employee Share Posted April 4, 2011 You might want to contact customer service with the case # to see what the hold up is. Link to comment Share on other sites More sharing options...
antipop2323 Posted April 4, 2011 Share Posted April 4, 2011 You don't want to use Time Machine to actually restore your primary OS drive to a new drive (it requires your OS X install disc, is insanely slow, yadda yadda). What you want is the app SuperDuper!, which allows you to make a bootable clone of your drive. Then you can boot from this drive, go into disc utility, and restore to your new HDD in a fraction of the time. Link to comment Share on other sites More sharing options...
Manuel_B Posted April 12, 2011 Author Share Posted April 12, 2011 I now got an RMA number and send a package to Corsair. But could take another 5 business days: Please do not reply directly to this e-mail as this address is not monitored. Corsair Technical Support has sent you a message regarding Case #1926458 ---------------------------------- Dear Manuel, We wanted to let you know that we have received your return package for RMA number 1221979 Your returned product is staged for review by our returns department, and we will be contacting you shortly regarding repair or replacement. Please note we are currently experiencing delays with warranty replacement shipments, please allow for an additional 5 business days for processing. Sincerely, Corsair Returns Department Thank You! Corsair Inc. Corsair Corporate Headquarters http://tsx.corsair.com http://www.corsairmemory.com http://www.asktheramguy.com Link to comment Share on other sites More sharing options...
Manuel_B Posted April 28, 2011 Author Share Posted April 28, 2011 Hi, the new SSD arrived at the 20.4. so it took about 2 month until it was replaced in the meantime one of my RAM slots broke in my MacBook Pro. So I decided to get a complete new 2011 MacBook Pro 13". Unfortunately this version seems to not support SATA III disc from foreign vendors: http://www.hardmac.com/news/2011/03/17/about-the-ssd-sata-iii-problem-in-the-2011-macbook-pro I cannot install Mac OS X Snow Leopard on the new computer. Hmm lets see if I can solve this problem. To be continued :-) /Manuel Link to comment Share on other sites More sharing options...
Manuel_B Posted April 28, 2011 Author Share Posted April 28, 2011 Actually I have at the moment the same problems like oskare and eecue. After 3 installations that all failed at another point. I erased the whole disc and filled it with zeros. I could imagine that the 10.6.7. update has some useful stuff in it for SATA III support. http://tonymacx86.blogspot.com/2011/03/mac-os-x-1067-update-for-early-2011.html First I have to get Snow Leopard running. Link to comment Share on other sites More sharing options...
Manuel_B Posted April 28, 2011 Author Share Posted April 28, 2011 Writing zeros helped. At least I got the system installed. I got some arbitrary crashed. Therefore I am now installing the whole system again. Seems to me that Mac OS X is not able to write sustainably blocks on the disc and from time to time it writes bad blocks. I also used the TRIM enabler from Goth. Basically it worked. http://www.groths.org/?p=308 But perhaps the crashes are in conjunction with that. /Manuel Link to comment Share on other sites More sharing options...
Manuel_B Posted April 28, 2011 Author Share Posted April 28, 2011 By the way the performance of the new Mac Book Pro 13" including the Performance 3 was amazing. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.