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

Upgrade SSD Macbook pro mid 2014 - A1502 Samsung 860 evo M.2

opensource93

opensource93

macrumors newbie
Original poster
Nov 28, 2018
1
0
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Samsung 970 EVO and adapter are what you need. The thread Audit 13 pointed to is one to follow. You might want to start at the end since the thread is very long.
 
One thing with the Samsung drives is higher battery drain and possibly higher temps.

There's also the possibility of kernel panics with pre-2015 MBPs and you must disable hibernation 25.
 
Audit13 said:
One thing with the Samsung drives is higher battery drain and possibly higher temps.

There's also the possibility of kernel panics with pre-2015 MBPs and you must disable hibernation 25.
Click to expand...

What does disabling hibernation do?
Will you still be able to 'sleep' your machine and wake it up?
Or does it mean that you will have to shut down every time?
 
akineyle5 said:
What does disabling hibernation do?
Will you still be able to 'sleep' your machine and wake it up?
Or does it mean that you will have to shut down every time?
Click to expand...
The machine can't go into hibernation. In hibernation, everything in ram is written to the SSD and the MacBook powers itself off so the battery doesn't drain.

When you close the lid or choose sleep from the menu, the contents in ram are written to the SSD and the battery continues to power the ram to keep the ram contents from being lost. This is why the battery will drain even with the MacBook being put to sleep by either closing the lid or using the menu option. If the battery drains completely, contents in ram are lost. When power is restored, the contents are loaded from the SSD.

With an nvme drive, waking the MacBook from hibernation may cause kernel panics so disabling hibernation is necessary.
 
Audit13 said:
The machine can't go into hibernation. In hibernation, everything in ram is written to the SSD and the MacBook powers itself off so the battery doesn't drain.

When you close the lid or choose sleep from the menu, the contents in ram are written to the SSD and the battery continues to power the ram to keep the ram contents from being lost. This is why the battery will drain even with the MacBook being put to sleep by either closing the lid or using the menu option. If the battery drains completely, contents in ram are lost. When power is restored, the contents are loaded from the SSD.

With an nvme drive, waking the MacBook from hibernation may cause kernel panics so disabling hibernation is necessary.
Click to expand...

Thanks for clarifying this, i was having a hard time figuring out what the difference was between sleep and hibernation mode on a mac.

I think you meant that in sleep mode though the contents are not stored or written to the SSD? However, the battery continues to power RAM enabling users to 'wake' the system instantaneously.

I apologize and will ask a dumb question though... How do you hibernate your mac and is this turned on by default? Is hibernation shutting down the mac with 're-open windows when logging back in' option checked off? There is no'hibernation' button when you shut down or sleep is there, or am i missing something?

To me it sounds like turning off the hibernation mode is not really that big of a deal for most people. In my situation though I think most times I sleep the machine, and the there are very few times i will actually shut down. When sleeping the machine, i do not usually let the battery drain to the point where it loses everything from RAM.
 
Last edited:
Hi all,

I tried to make sense out of this thread coz I'm about to upgrade the drive in my late 2013 15" MBP.

I am still not clear on the question if the sleep-wake crashes affect all SSDs or just some - most notably the Samsung 970 Evo Series devices?

I experience the crashes on the 970 Evo, which is why I ordered a Crucial P1 hoping this SSD isn't affected.

Any comments to enlighten me? Thanks....
 
I know, I did that - albeit it did not work. What worked though is setting the standbydelay higher, to about a week or so. The Mac would still crash after that week - but since I'm using it pretty much each day I of course don't care.

Some claim that problem only exists using Samsung Evos, not on others (like Intels). So I'm inclined to send the Samsung back and try the Crucial P1 instead...
So you're saying the problem exists with any NVME SSD?
 
Yes, the problem exists with all nvme drives in the pre-2015 Macs from what I have read.

I have an early 2015 Air with an Intel 600p and I do not have the problem.
 
Ok. So far so bad.

Indeed, I got a friends early 2015 MBP 13 here to set up after replacing the SSD - no problem whatsoever using the 970 Evo. Works like a charm, read/write speeds at around 1500 MB/s
 
This person is using the Intel 760p with 2014 MBP: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-101#post-26831247 with hibernate mode 3: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-103#post-26841478

Person got a frozen screen and had perform a hard reboot: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-103#post-26842869

This person's experience may not be typical of the Intel SSDs.
[doublepost=1543703187][/doublepost]
09872738 said:
Ok. So far so bad.

Indeed, I got a friends early 2015 MBP 13 here to set up after replacing the SSD - no problem whatsoever using the 970 Evo. Works like a charm, read/write speeds at around 1500 MB/s
Click to expand...
Test hibernation to know for sure.
 
Audit13 said:
This person is using the Intel 760p with 2014 MBP: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-101#post-26831247 with hibernate mode 3: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-103#post-26841478

Person got a frozen screen and had perform a hard reboot: https://forums.macrumors.com/thread...sd-to-m-2-nvme.2034976/page-103#post-26842869
Click to expand...

So the Crucial is about to arrive on monday; I guess I'll give it a try. If it works using the Crucial, Crucial it is. Otherwise .. see below

Audit13 said:
[doublepost=1543703187][/doublepost]
Test hibernation to know for sure.
Click to expand...

I did. With modes 0, 3 and 25. Crashed upon wakeup each time. No big deal, as mentioned increasing delay accordingly.
 
Is this known to work for sure? If I got it correctly some in this thread commented the updated bootrom didn't sport any results
 
Thx for providing that link.

That said, tinkering with flashing devices is out of the question, unfortunately.

So I'll try the Crucial the other day and in case this crashes too I'll just disable hibernation. No big deal
 
Last edited:
Good luck with the Crucial.

I've been interested in an nvme drive for a while and started with a mid-2013 Air. It had the crash problems so I went back to using the original 128 GB SSD. I eventually passed the Air onto a relative and got myself an early 2015 Air.
 
Update: as anticipated, the Macbook also crashes using the Crucial P1. Well then.. standbydelay to one week. Problem circumnavigated hence considered solved.

Thanks all
 
Audit13 said:
The other way around the crash would be to flash a modded bootrom.
Click to expand...

Do you need to pull the bootrom from a newer MacBook, or can you just download this from somewhere?

Does this all mean that the Sintech adapter with the Samsung M.2 NVME 970 Evo will still have crashing problems?
 
You use your Macbooks original bootrom to create the modified bootrom.

With the modified bootrom, deep sleep will not cause panics.

A modified bootrom is no guarantee that something else won't make the MBP crash.
 
Last edited:
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