Samsung SSD 840 freezes OSX Lion on MacbookPro Early 2008

Thanks a lot. What you suggested from the beginning.

Sadly enough I can't return the disk, since it's been mounted and too long time has passed. Maybe I'll install it in my newer MBP with SATA 3 - even if it's a litlle small for that purpose.

But again thanks a lot for your time and effort -

regards Martin

I've followed this thread from the start. It's a shame that the drive hasn't worked successfully in your 2008 MacBook Pro. Mine ran perfectly in my 2007 macbook, so much so that I highly recommend samsung drives to other people based on my experience. I'm currently looking to get an 840 evo for my 2011 MacBook Pro.

I appreciate all the help that everyone gave you on this matter and had hoped it would be resolved. It's a shame it hasn't been and that it does indeed look like a comparability issue from the Sata I to III interface. I shant be so hasty to recommend the drive for older machines going forward.

Will you look to get a Sata II drive to,replace it?

Yes, there is a margin for error however at my side, how unbelievable that may sound 😁...

I hope Linc Davis comes in anyway, because this "professor reads these logs as a nice roman...

and then we can all learn from it.

Robodisko you were lucky. Samsung is a very good brand, the 830 is a wonderfull disk, but the new 840 is completely different and obviously can be a "borderline" case when two steps down. The 830 (less advanced) could be trusted always. But if you reserach this forum and others you will see that nobody really afvises to use an SSD sata3 in a sata1 situation. I have about 10 ssd's Crucial and Samsung, and they all work perfectly well, but I have never built them in a two step down computer. Pfff.

And even now I am only 99% sure it is the SSD. But the 840 is a completely new architecture, laid out for sata3 and 22nm for extreme efficiency and speed.

I have found a Samsung 830 for a quite cheap prize. It's only 128 GB, but will serve me well. Would it be safe to buy it?

I have one in a sata3 mbp: running fine, and one in a sata2 mbp running fine, this one was in a sata1 mb also running fine for a small year or so before. But these two don't prove 100%.

I would take the bet anyway, since it has a less exceptional architecture.

Sob-sob: Just installed the 128 GB Samsung 830 - and had a freeze. Hope it was a one-timer😐

What the f****.

Post the crash report.

Hope that Linc still is following the thread.

.

Hi again - thanks for your concern. Had another freeze just when I was about to answer.

IOATAController device blocking bus could be the culprit? (Knowing that the old HD is in the opticbay)

This should be the log:

01/10/13 20.50.52,000 kernel[0]: hibernate_page_list_setall time: 383 ms

01/10/13 20.50.52,000 kernel[0]: pages 1036793, wire 105205, act 275779, inact 205, cleaned 0 spec 65, zf 11095, throt 0, could discard act 191957 inact 68863 purgeable 2882 spec 380742 cleaned 0

01/10/13 20.50.52,000 kernel[0]: hibernate_page_list_setall found pageCount 392349

01/10/13 20.50.52,000 kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0

01/10/13 20.50.52,000 kernel[0]: IOHibernatePollerOpen(0)

01/10/13 20.50.52,000 kernel[0]: encryptStart 13230

01/10/13 20.50.52,000 kernel[0]: bitmap_size 0x20040, previewSize 0x20e070, writing 391530 pages @ 0x2412e0

01/10/13 20.50.52,000 kernel[0]: encryptEnd 65dca00

01/10/13 20.50.52,000 kernel[0]: image1Size 0xb53ce00, encryptStart1 0x13230, End1 0x65dca00

01/10/13 20.50.52,000 kernel[0]: encryptStart b53ce00

01/10/13 20.50.52,000 kernel[0]: encryptEnd 2ae19c00

01/10/13 20.50.52,000 kernel[0]: PMStats: Hibernate write took 11895 ms

01/10/13 20.50.52,000 kernel[0]: all time: 11895 ms, comp bytes: 1604071424 time: 2271 ms 673 Mb/s, crypt bytes: 636118480 time: 4096 ms 148 Mb/s,

01/10/13 20.50.52,000 kernel[0]: image 719428608 (16%), uncompressed 1604071424 (391619), compressed 713620352 (44%), sum1 4d57c473, sum2 e5391606

01/10/13 20.50.52,000 kernel[0]: wired_pages_encrypted 54615, wired_pages_clear 49860, dirty_pages_encrypted 287144

01/10/13 20.50.52,000 kernel[0]: hibernate_write_image done(0)

01/10/13 20.50.52,000 kernel[0]: sleep

01/10/13 20.50.52,000 kernel[0]: Wake reason: EC LID0 FRWR

01/10/13 20.50.52,000 kernel[0]: HID tickle 41 ms

01/10/13 20.50.52,000 kernel[0]: Previous Sleep Cause: 5

01/10/13 20.50.52,000 kernel[0]: IOATAController device blocking bus.

01/10/13 20.50.52,000 kernel[0]: IOATAController device blocking bus.

01/10/13 20.50.52,000 kernel[0]: IOATAController device blocking bus.

01/10/13 20.50.52,000 kernel[0]: IOATAController device blocking bus.

01/10/13 20.52.20,000 bootlog[0]: BOOT_TIME 1380653540 0

01/10/13 20.52.24,000 kernel[0]: Darwin Kernel Version 12.5.0: Mon Jul 29 16:33:49 PDT 2013; root:xnu-2050.48.11~1/RELEASE_X86_64

01/10/13 20.52.24,000 kernel[0]: vm_page_bootstrap: 895743 free pages and 144641 wired pages

01/10/13 20.52.24,000 kernel[0]: kext submap [0xffffff7f80742000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000742000]

01/10/13 20.52.24,000 kernel[0]: zone leak detection enabled

01/10/13 20.52.24,000 kernel[0]: standard timeslicing quantum is 10000 us

01/10/13 20.52.24,000 kernel[0]: standard background quantum is 2500 us

01/10/13 20.52.24,000 kernel[0]: mig_table_max_displ = 74

01/10/13 20.52.24,000 kernel[0]: corecrypto kext started!

01/10/13 20.52.24,000 kernel[0]: Running kernel space in FIPS MODE

01/10/13 20.52.24,000 kernel[0]: Plist hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d

01/10/13 20.52.24,000 kernel[0]: Computed hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d

01/10/13 20.52.24,000 kernel[0]: corecrypto.kext FIPS integrity POST test passed!

more on the head

SystemPreferences/EnergySaver/ set "computersleep" to "never" and uncheck "put harddisks to sleep when possible".

In Terminal with copy/paste:

sudo pmset -a hibernatemode 0

and enter, then

sudo rm /var/vm/sleepimage

and enter, then

sudo touch /private/var/vm/sleepimage

and enter, then

sudo chflags uchg /private/var/vm/sleepimage

and enter, then Quit Terminal

This makes the SSD not sleep, write no sleepimage (same size as Ram), removed the existing sleepimage, placed a locked zero bytes sleepimage in its place (because in ML the sleepimage comes back even with hiberbate mode 0).

That we have to do anyway for the SSD. For the moment we do not activate a Trim command, the Garbage Collection on the Samsung SSD is effective.

That will hopefully cover all the hibernate entries.

This piece of crash log mentions a "zone leak", does free memory fall low in ActivityMonitor.

Can you run an Etrecheck list please.

Hi Lex

What about my theory? That the old HD is the culprit?

(Hate to use a lot of yours and my time not finding a solution)

regards

Martin Ammentorp

I don't think so: it IS the ssd with the OS that crashes?

A test is simple: if you don't need the hdd to run the mac, open up and just removethe hdd or disconnect it's sata connector. close up (don't run the mac while open!) and test.

But the hibernatemode as I explained above is one of the things that you should do anyway (and the EnergySaver settings) to give the ssd a longer life. More important than the Trim command.

Keeping my fingers crossed now...😊

The mac has now been running without freezes since this morning: And the HD in the opticbay has been unmounted all the time. I made an Applescript to unmount and mount.

Beautiful! Great thinking!

I should have seen it: the optibay is not sata! (early 2012 MBP).

The sata hdd will not run correctly in that connection. The same for the ssd.

Better put the optidrive back, or nothing.

Now do the Hibernate mode and the energysaver setting: check both after an OS update.

Let the Trim be uninstalled, it will have to be set also after OS updates and probably will not work well in Mavericks (if you want to go there). And the Samsung have a very active GarbageCollection.

Great.

Would like to know if the samsung 840 EVO 500gb would be a good fit for my early 2008, 24 inch iMac while running it on Snow Leopard 10.6.8 with trim enabler 2.2. Any tips or advice is appreciated...