Upgrading 2013-2015 Macbook Pro SSD to M.2 NVMe

[jimbocho]

Hi guys! I hope someone can help:
I just updated my Macbook Pro 13" late 2013 (already running with M.2 SSD) to Big Sur, in the hopes I can use hibernate/sleep like with the original drive.
However, once the Macbook goes to sleep, it reboots once I open the lid again:

Sleep Wake failure in EFI

Failure code:: 0x0171260e 0x0000001f

Please IGNORE the below stackshot

================================================================
Date/Time:        2021-03-05 20:52:38.535 +0100
OS Version:       ??? ??? (Build ???)
Architecture:     x86_64
Report Version:   32

Data Source:      Stackshots
Shared Cache:     77B63435-1866-32DD-98A1-47090B666EFA slid base address 0x7fff2002d000, slide 0x2d000

Event:            Sleep Wake Failure
Duration:         0.00s
Steps:            1

Time Awake Since Boot: 40s



Process:          swd [378]
Architecture:     x86_64
Footprint:        328 KB
Time Since Fork:  2s
Num samples:      1 (1)

  Thread 0x9e2    1 sample (1)    priority 4 (base 4)
  <thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>
  1  start + 1 (libdyld.dylib + 87585) [0x7fff20359621] 1
    1  ??? [0x10a77d454] 1
      1  ??? [0x10a77d1e8] 1
        1  __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 143386) [0x7fff2032c01a] 1
         *1  ??? [0xffffff80002601f6] 1
           *1  ??? [0xffffff80009698cb] 1
             *1  ??? [0xffffff80008733c1] 1
               *1  ??? [0xffffff80002831c9] 1
                 *1  ??? [0xffffff80002ba3ed] (running) 1

  Binary Images:
        0x7fff20309000 -     0x7fff20337fff  libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076>  /usr/lib/system/libsystem_kernel.dylib
        0x7fff20344000 -     0x7fff2037efff  libdyld.dylib (832.7.3)            <4641E48F-75B5-3CC7-8263-47BF79F15394>  /usr/lib/system/libdyld.dylib
Model: MacBookPro11,1, BootROM 149.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2,4 GHz, 8 GB, SMC 2.16f68
Graphics: kHW_IntelIrisItem, Intel Iris, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1675.1)
Bluetooth: Version 8.0.3d9, 3 services, 27 devices, 1 incoming serial ports
Network Service: Thunderbolt Ethernet, Ethernet, en5
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2

What I find strange is that in System Information, there is no Bootrom Version shown:

Would I have needed to update to Big Sur with the original drive?

Thanks so much in advance!

Jan

 

[jimbocho]

Never mind. Just realized that "System Firmware Version" is the value to look at and that it was indeed ancient. Did go through with the Big Sur upgrade on the Apple drive (would there have been a faster/easier way?) and it's now on the current Firmware.

 

[FF89]

After completing the installation, I installed the ssdpmenabler.kext v0.1.1 by KVCI-z (https://github.com/kvic-z/SsdPmEnabler). It was successful and managed to significantly reduce the SSD current consumption from 0.1 A to 0.01 A during idle when observed using iStat Menus.

Hello,

Today, I noticed a momentarily increase in SSD current about 0.05-0.10A during idle (SSD temperature around 43-44 Celcius) after I turned on the rMBP (as shown in iStat Menus below from time 4:49 to 5:19). Eventually, after around hour of usage (surfing, youtube) and let to idle, the current value returned in the range of 0.00-0.01A (31-34 Celcius) again. I wonder why is it initially increase and maintain at 0.05-0.10A? Anyone had experienced the same situation?

Note: I only applied ssdpmenabler at the moment. Previously, I have tested applying ssdpmenabler with Lilu 1.5.1 + NVMeFix 1.0.5, but no difference in SSD current value compared to using ssdpmenabler alone. Therefore, i decided to remove Lilu and NVMeFix, and maintain only ssdpmenabler for my configuration.

Configuration:
Macbook Pro (15-inch Retina, Mid 2014) (MacbookPro 11,2)
macOS Big Sur 11.2.2
NFHK N-941A Adapter
Crucial P2 1TB
Kext: ssdpmenabler.kext only

​

 

[dickster]

I just installed a 500GB Crucial P2 SSD with a JESOT adapter (Sintech was on backorder) in my 2015 13" Air. Battery life while active is better than with the OEM drive, battery life while sleeping somewhat worse (1-2%/hour). Battery use while hibernating is negligible (<1%/day), so after shortening the hibernation timer to something more reasonable than the 24H default I've been very satisfied. Satisfied enough that I haven't bothered with any of the NVMeFix or SsdPmEnabler kext mods.

Hello everyone.

A seemingly easy question - which 1TB SSD for my Macbook Air early 2015 core i7 2.2Ghz?

I spent a week reading through these posts and every time I think I've found 'the one', I find out there's some issue with it e.g.

1. Sabrent Rocket (works great at first but multiple reports that it dies after a few months)
2. ADATA SX8200 (used to be great but they've changed to a slower controller + heat build-up issues)
3. Samsung EVO 970 (slows down after some time?)

Forgive me if I got it wrong - probably got things mixed up.

The bottom line is I'm looking for the most reliable SSD and willing to sacrifice some speed if necessary.

Any thoughts if the Crucial (P1 or P2) fits the bill for me?

Many thanks in advance.

 

[padams35]

The bottom line is I'm looking for the most reliable SSD and willing to sacrifice some speed if necessary.

Any thoughts if the Crucial (P1 or P2) fits the bill for me?

Many thanks in advance.

The most reliable would probably be the OWC Aura N2 since that is was customized to use Apple's connector eliminating any possible adapter complications; I just happened to be Crucial brand loyal and decided not to splurge on the +$50 OWC price premium.

I've been very satisfied with previous Crucial Memory/SSD purchases and have high hopes for the P2, but admittedly haven't owned that particular model very long.

 

[xboxbml]

Hello everyone.

A seemingly easy question - which 1TB SSD for my Macbook Air early 2015 core i7 2.2Ghz?

I spent a week reading through these posts and every time I think I've found 'the one', I find out there's some issue with it e.g.

1. Sabrent Rocket (works great at first but multiple reports that it dies after a few months)
2. ADATA SX8200 (used to be great but they've changed to a slower controller + heat build-up issues)
3. Samsung EVO 970 (slows down after some time?)

Forgive me if I got it wrong - probably got things mixed up.

The bottom line is I'm looking for the most reliable SSD and willing to sacrifice some speed if necessary.

Any thoughts if the Crucial (P1 or P2) fits the bill for me?

Many thanks in advance.

I've had my ADATA since Sept 2020 I think.. No issues. I put the heatsink on mine so I can't see which controller it has unfortunately, and I'm not gonna try and get it off.. It's stuck on there really well.

 

[AstroZero]

1. Sabrent Rocket (works great at first but multiple reports that it dies after a few months)

Have you got any links to examples of the drive dying? @Michaela_ posted that the drive was unreadable on the Mac but worked on a different machine (not sure which drive it is though!).

I have been using a sabrent rocket since August 2019 on my 2015 Air with short sintech on Mojave. I had only a few random kernel panics and no data loss or failure. These panics may have been due to my own poor installation, see #8,526 above.

After cleaning the contacts, I've had no issues for 2 days (kernel uptime) so far.

Using the iStat Menu tool, I found that any speed issues I had are due to heat caused by heavy use. The highest temp I witnessed was 64c when I left the BlackMagic benchmark on- it is normally around 32c. Fast transfers and benchmarking using BlackMagic mean I get lower speeds (<900MB/s R/W down from 1200MB/s R/W). Most of my real world use is bursty. I am using the kexts, too. I am considering getting a heatsink that will fit the 2015 Air.

Attached is iStat menu's hard drive temp reading for 7 days.

edit: typos+ I too would take lower speeds for reliability!

 

[Skypalace]

I’m running a late 2013 15” MacBook Pro, a couple of years ago I upgraded to a 2TB Sabrent w short Sintech, of course w help out this group and thread. I’m happy, all has been working fine, I just ensure I don’t go too long w/o power as I haven’t hacked rom to fix the hibernate issues.

My Q: I’m on an old OS (Mojave 10.14.6) and bootrom (153.0.0.0.0) and was thinking of upgrading, my Mac is showing me Big Sur 11.2.1 as an upgrade.
...

I'm now up to 430.0.0.0.0 but I learned a few things.

1) I did NOT get boot rom updates to work on my 13,1 with 153.0.0.0.0, until I reinstalled my original Apple SSD. There's a minimum bootrom version needed to be able to update bootroms with aftermarket NVMe, and 153.0.0.0.0 is too early.

2) I did not need to (or bother) updating to Catalina or Big Sur from Mojave

3) I was able to get the bootrom updates by reinstalling the Apple SSD, and updating Mojave on that old SSD from an older version to 10.14.6. I did these by just refreshing Software Update under System Preferences, ignoring the Big Sur update, selecting Advanced, and choosing the Mojave update available.

This actually took TWO updates, only one showing at a time. One Mojave system update that though the download was under 3GB, needed 12.4GB free space on the SSD to be able to upgrade. This upgrade, once fully installed, updated my bootrom from 153.0.0.0.0 to 156.0.0.0.0.

Then, there was a second security update available, 2.4GB. This one, once fully installed, updated my bootrom from 156.0.0.0.0 to 430.0.0.0.0.

4) My Sabrent Rocket is running ECFM12.2 firmware, as shown in my prevoius post. Sabrent doesn't show available updates, I did not try updating to the reference 12.3 software, nor have any seen any trustworthy sources that say what updates/changes/fixes are in 12.3 vs. 12.2

5) Instead of standbydelaylow 3600 as others have done, I did 7200, as I found that my Time Machine backup disk, which I'd had doing a backup, was improperly ejected when the machine slept. Gives me extra time to manually remove the drive after the time machine backup is complete, which can be long with a 2TB drive.

 

[ztoby]

Hello,

I finally upgraded my early 2015 Macbook pro with a Crucial P2 1TB ssd, using sintech adapter.

I used ccc method, after upgrading to Big Sur. Everything works fine. I attach the Speedtest results.

Is there anything else I should do? Should I install SsdPmEnabler?

Thank you for all the info!

 

[dickster]

Have you got any links to examples of the drive dying? @Michaela_ posted that the drive was unreadable on the Mac but worked on a different machine (not sure which drive it is though!).

I was set to get the Sabrent Rocket but this article kind of put me off:

Here's why you should NOT buy a Sabrent Rocket SSD

DISCLAIMER: all the opinions expressed in this article represent the personal belief of the author and are in no way oriented by commercial relations of any kin

www.ryadel.com

 

[FF89]

Hello,

I finally upgraded my early 2015 Macbook pro with a Crucial P2 1TB ssd, using sintech adapter.

I used ccc method, after upgrading to Big Sur. Everything works fine. I attach the Speedtest results.

Is there anything else I should do? Should I install SsdPmEnabler?

Thank you for all the info!

Hello,

You should try installing SsdPmEnabler and monitor your SSD current during idle before and after installing the kext using iStat Menus.

For me, it does contribute to significant reduction in current of the SSD during idle (From 0.1 A to ~0.00-0.01 A). In addition, I done updating my macOS Big Sur from 11.2.2 to 11.2.3 today using bootable Installer USB method without uninstalling the SsdPmEnabler. The result, the update went fine without any issue and the SsdPmEnabler continues to work. I would recommend to backup your storage before updating the macOS.

 

[jumleguf]

Ok, I have hibernation/sleep problems and all out of ideas here ... Could really use some help
Long, tiresome journey, which I'll try and sum up shortly, if there should be a clue to a solution/explanation somewhere ...

1: Installed a 1TB Samsung EVO 970 in my Macbook Late 2013 (11,1) with a QNINE adapter ( https://www.amazon.co.uk/dp/B07S9Q6TCN?tag=macr0e-21&geniuslink=true ), and then tried installing Big Sur as an experiment. It did however feel a little bit sluggish to me, so I decided to take a step back and install Catalina instead.

2: Installed Catalina, and it was marginally faster, but now I noticed a few things:
- The machine got rather hot and ate away battery time (new battery too) very fast.
- Shutting the lid seemed to work fine, and the Macbook didn’t reboot or crash when doing this. BUT, when running out of battery, it didn’t go into hibernation/sleep and pick back up when re-powered, but simply die and reboot, not even a low battery symbol.

3: Then I found this forum, and learned a few things:
- That the 970 EVO is a power hog, so other drives might be a better choice
- I might have the wrong adapter too, it ought to be the Sintech
- Big Sur might be part of the solution after all, due to the Boot ROM upgrade of this version, which should handle NVME units better in terms of sleep/hibernation/boot and so on.
Hooray, hope restored!

4: So, instead, I put in a 1TB Crucial P2 with the Sintech adapter, hoping all would be cool. During the process, I found out that the Boot ROM had already been upgraded to 430.0.0.0.0, due to my earlier Big Sur install, leading me to believe that things might work now with Catalina too.
So, I tried keeping it simple by reinstalling Catalina. It worked fine, but the upgraded Boot ROM didn’t change anything, the machine still just died when running out of battery.

5: Now I’ve tried simply updating my Catalina install to Big Sur, hoping that’d do the trick.
And shutting the lid still works fine, doesn’t make the MacBook crash or reboot or anything, and it doesn’t use battery overnight f.e., so that part of it seems ok.
Now I get the pretty “Low Power” icon, when the battery has gone flat, and at this point it should normally spring back to life and continue where I left off, when I plug in the power supply and hit the Power button.
But still, the machine just reboots :-( :-( :-(
I tried resetting SMC and NVRAM with no effect, plus setting the hibernatemode to 25, no luck with that either.


I’m all out of ideas now, can someone PLEASE help me make this work!! 😩

 

[FF89]

Ok, I have hibernation/sleep problems and all out of ideas here ... Could really use some help
Long, tiresome journey, which I'll try and sum up shortly, if there should be a clue to a solution/explanation somewhere ...

1: Installed a 1TB Samsung EVO 970 in my Macbook Late 2013 (11,1) with a QNINE adapter ( https://www.amazon.co.uk/dp/B07S9Q6TCN?tag=macr0e-21&geniuslink=true ), and then tried installing Big Sur as an experiment. It did however feel a little bit sluggish to me, so I decided to take a step back and install Catalina instead.

2: Installed Catalina, and it was marginally faster, but now I noticed a few things:
- The machine got rather hot and ate away battery time (new battery too) very fast.
- Shutting the lid seemed to work fine, and the Macbook didn’t reboot or crash when doing this. BUT, when running out of battery, it didn’t go into hibernation/sleep and pick back up when re-powered, but simply die and reboot, not even a low battery symbol.

3: Then I found this forum, and learned a few things:
- That the 970 EVO is a power hog, so other drives might be a better choice
- I might have the wrong adapter too, it ought to be the Sintech
- Big Sur might be part of the solution after all, due to the Boot ROM upgrade of this version, which should handle NVME units better in terms of sleep/hibernation/boot and so on.
Hooray, hope restored!

4: So, instead, I put in a 1TB Crucial P2 with the Sintech adapter, hoping all would be cool. During the process, I found out that the Boot ROM had already been upgraded to 430.0.0.0.0, due to my earlier Big Sur install, leading me to believe that things might work now with Catalina too.
So, I tried keeping it simple by reinstalling Catalina. It worked fine, but the upgraded Boot ROM didn’t change anything, the machine still just died when running out of battery.

5: Now I’ve tried simply updating my Catalina install to Big Sur, hoping that’d do the trick.
And shutting the lid still works fine, doesn’t make the MacBook crash or reboot or anything, and it doesn’t use battery overnight f.e., so that part of it seems ok.
Now I get the pretty “Low Power” icon, when the battery has gone flat, and at this point it should normally spring back to life and continue where I left off, when I plug in the power supply and hit the Power button.
But still, the machine just reboots :-( :-( :-(
I tried resetting SMC and NVRAM with no effect, plus setting the hibernatemode to 25, no luck with that either.


I’m all out of ideas now, can someone PLEASE help me make this work!! 😩

Hello,

Is it possible to share your “system-wide power setting”?

You can check your currently in use setting by typing pmset -g in the terminal.

Maybe we can learn something from the output.

 

[jumleguf]

Hello,

Is it possible to share your “system-wide power setting”?

You can check your currently in use setting by typing pmset -g

Maybe we can learn something from the output.

Absolutely, here goes:

System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 1
halfdim 1
hibernatefile /var/vm/sleepimage
gpuswitch 2
powernap 0
disksleep 0
standbydelayhigh 86400
sleep 1
autopoweroffdelay 259200
hibernatemode 25
autopoweroff 1
ttyskeepawake 1
displaysleep 0
highstandbythreshold 50
acwake 0
lidwake 1

Is this helpful?

 

[FF89]

Absolutely, here goes:

System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 1
halfdim 1
hibernatefile /var/vm/sleepimage
gpuswitch 2
powernap 0
disksleep 0
standbydelayhigh 86400
sleep 1
autopoweroffdelay 259200
hibernatemode 25
autopoweroff 1
ttyskeepawake 1
displaysleep 0
highstandbythreshold 50
acwake 0
lidwake 1

Is this helpful?

Almost all setting are identical to mine except for disksleep (10), hibernationmode (3), and displaysleep (2). I am not sure if they are the cause.

All the other setting which trigger hibernation mode look fine.

So far, I never tried using the MBP below 30% to preserve battery health. Only tried hibernation when battery still high. I will try later and see the outcome whether it can wake up or reboot.

 

[jumleguf]

Almost all setting are identical to mine except for disksleep (10), hibernationmode (3), and displaysleep (2). I am not sure if they are the cause.

All the other setting which trigger hibernation mode look fine.

So far, I never tried using the MBP below 30% to preserve battery health. Only tried hibernation when battery still high. I will try later and see the outcome whether it can wake up or reboot.

That'd be interesting to hear about, FF89

I'm a bit curious about "disksleep" and "hibernatefile", because regular sleep, like when you close/open the lid, works just fine, and there's only an issue with the wake-up from when the battery runs dry.
Now I'm just guessing wildly, but if the OS is trying to save its current state as a "hibernatefile" in another place than the NVME SSD, so it can't be read properly when powering back up and therefore can't resume as expected, maybe that could be the reason for a cold reboot?

Anyway, I'm no expert and only making assumptions here ...

And even though I'm not deliberately trying to push the battery to the edge every cycle, it just happens ever so often that I'm not paying attention and so the battery just runs out before I can attach some power. Just lazy, I guess ;-)
Before this NVME upgrade, at least the MacBook ALWAYS just resumed whereever it was left, so I never thought about it much. But now I do, because killing and cold rebooting the system like this can't be healthy in the long run :-/

Let me know what you find out!!

 

[zach514]

I recently upgraded my 2014 MBP 15" from the OEM 256gb "blade" SSD to a 1tb Crucial P2 NVME drive with a Sintech adapter. This drive and adapter combo is one of the most common on this thread, so it should work fine, and does seem to work fine for a lot of people.

The actual disk speed is much faster than the old one. It's advertised as being capable of a max of 2400mbps in ideal conditions, but because it is limited by the PCIE 2 bus of my MBP, It maxes out at 1400mbps in Blackmagic disk speed test.

The problem is when I boot the MBP. It used to get from off to the login screen in maybe 10-20 seconds, never actually timed it but it seemed pretty quick. Now with the NVME drive, it takes about a minute, sometimes more to get to the login screen. Weirdly enough, with the new drive, once I enter my password and hit enter, I almost instantly get to my desktop, whereas with the old drive it would take 5-10 second to load in.

I saw that some people recommended disabling TRIM to fix this, so I did that with the console command, rebooted and nothing changed. If anything it might even take slightly longer to boot. Is there any way I can fix this or is it just something I'll have to live with now? Any input is appreciated, thanks!

 

[mork4]

Anyone noticed bootrom update with macOS Big Sur 11.2.3 release? Thanks.

 

[FF89]

I recently upgraded my 2014 MBP 15" from the OEM 256gb "blade" SSD to a 1tb Crucial P2 NVME drive with a Sintech adapter. This drive and adapter combo is one of the most common on this thread, so it should work fine, and does seem to work fine for a lot of people.

The actual disk speed is much faster than the old one. It's advertised as being capable of a max of 2400mbps in ideal conditions, but because it is limited by the PCIE 2 bus of my MBP, It maxes out at 1400mbps in Blackmagic disk speed test.

The problem is when I boot the MBP. It used to get from off to the login screen in maybe 10-20 seconds, never actually timed it but it seemed pretty quick. Now with the NVME drive, it takes about a minute, sometimes more to get to the login screen. Weirdly enough, with the new drive, once I enter my password and hit enter, I almost instantly get to my desktop, whereas with the old drive it would take 5-10 second to load in.

I saw that some people recommended disabling TRIM to fix this, so I did that with the console command, rebooted and nothing changed. If anything it might even take slightly longer to boot. Is there any way I can fix this or is it just something I'll have to live with now? Any input is appreciated, thanks!

Hello,

After you point out, I just tried check my off to the login screen on my 15" MBP 2014 (2.2Ghz) running on macOS 11.2.3. I am also using Crucial P2 1TB but with NFHK short adapter (My Sintech still going back and forth from Shenzhen to Guangzhou for 3 times already for 3 weeks).

I attached a video demonstration. I also feel my original SSD is much faster from off to login screen compared to P2. It took around 30 seconds with P2. I thought this is normal for P2 because of its DRAMless SSD, and it is more focus for energy efficiency and low heat output. I just accept it as it is. I could be wrong.

However, in your case, you did mentioned that it took about a minute from off to login screen.

Have you tried setting the startup disk in the system preferences or performing nvram reset?

 

[FF89]

That'd be interesting to hear about, FF89

I'm a bit curious about "disksleep" and "hibernatefile", because regular sleep, like when you close/open the lid, works just fine, and there's only an issue with the wake-up from when the battery runs dry.
Now I'm just guessing wildly, but if the OS is trying to save its current state as a "hibernatefile" in another place than the NVME SSD, so it can't be read properly when powering back up and therefore can't resume as expected, maybe that could be the reason for a cold reboot?

Anyway, I'm no expert and only making assumptions here ...

And even though I'm not deliberately trying to push the battery to the edge every cycle, it just happens ever so often that I'm not paying attention and so the battery just runs out before I can attach some power. Just lazy, I guess ;-)
Before this NVME upgrade, at least the MacBook ALWAYS just resumed whereever it was left, so I never thought about it much. But now I do, because killing and cold rebooting the system like this can't be healthy in the long run :-/

Let me know what you find out!!

Hello again,

I just depleted my MBP battery. Around 1% of battery remaining, it entered hibernation mode with Low Power Icon was shown on the display. I was browsing Safari at that moment.

I leave the MBP alone for 10 minutes to do some errands. After finished, I check again whether the low power icon still there when pressing the power button and it still there. I immediately connect the MBP to power supply, press the power button, and the MBP wakes up from hibernation to the previous session. All of the process are recorded as in the video below for your reference.

The setting of pmset -g in terminal is as follows:

System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 1
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
disksleep 10
standbydelayhigh 86400
sleep 1
autopoweroffdelay 259200
hibernatemode 3
autopoweroff 1
ttyskeepawake 1
displaysleep 2
highstandbythreshold 50
acwake 0
lidwake 1

Note: This MBP (already in System Firmware version 430.0.0.0.0) was cleaned install with macOS Big Sur 11.2.2, updated to 11.2.3 with everything at default setting including Battery setting in the system preferences. No data transfer from the original SSD. SsdPmEnabler.kext is installed. No peripherals were connected to the Thunderbolt 2 ports, USB ports, HDMI port, SD card reader and also audio jack. Any apps that could hinder the sleep process (e.g., amphetamine) are disabled throughout this testing.

 

[jumleguf]

Hello again,

I just depleted my MBP battery. Around 1% of battery remaining, it entered hibernation mode with Low Power Icon was shown on the display. I was browsing Safari at that moment.

I leave the MBP alone for 10 minutes to do some errands. After finished, I check again whether the low power icon still there when pressing the power button and it still there. I immediately connect the MBP to power supply, press the power button, and the MBP wakes up from hibernation to the previous session. All of the process are recorded as in the video below for your reference.

View attachment 1742035​

The setting of pmset -g in terminal is as follows:

System-wide power settings:
Currently in use:
standbydelaylow 10800
standby 1
halfdim 1
hibernatefile /var/vm/sleepimage
powernap 0
gpuswitch 2
disksleep 10
standbydelayhigh 86400
sleep 1
autopoweroffdelay 259200
hibernatemode 3
autopoweroff 1
ttyskeepawake 1
displaysleep 2
highstandbythreshold 50
acwake 0
lidwake 1

Note: This MBP (already in System Firmware version 430.0.0.0.0) was cleaned install with macOS Big Sur 11.2.2, updated to 11.2.3 with everything at default setting including Battery setting in the system preferences. No data transfer from the original SSD. SsdPmEnabler.kext is installed. No peripherals were connected to the Thunderbolt 2 ports, USB ports, HDMI port, SD card reader and also audio jack. Any apps that could hinder the sleep process (e.g., amphetamine) are disabled throughout this testing.

Thank you for the thorough reply! Yup, that looks like what my machine did before this upgrade ...

Ok, so a few more things I can try ... 1: Fiddle with these pm-settings, which seem to work in your case. 2: Try a clean install, instead of an update from Catalina.

By the way, I believe SsdPmEnabler is not an option for my specific MacBook model (11,1), as it seems to induce crashes and stuff ... :-/

And speaking of model-specific issues, that makes me wonder:
Is there ANYONE here at all in this forum with a MacBook Late 2013 (11,1), who has the hibernation wake-up after battery depletion working without a hitch??

 

[desperex]

I just wonder what has changed in last Big Sur builds,
I had around 0.04A with both ssdPmEnabler and nvmeFix, now it doesn't go below 0.11A
Sabrent Rocket on MBP15 mid 2014
UPDATE: Nevermind, must be something penetrating my SSD, now I got 0.03A

 

[splifingate]

Hello everyone.

A seemingly easy question - which 1TB SSD for my Macbook Air early 2015 core i7 2.2Ghz?

I spent a week reading through these posts and every time I think I've found 'the one', I find out there's some issue with it e.g.

1. Sabrent Rocket (works great at first but multiple reports that it dies after a few months)
2. ADATA SX8200 (used to be great but they've changed to a slower controller + heat build-up issues)
3. Samsung EVO 970 (slows down after some time?)

Forgive me if I got it wrong - probably got things mixed up.

The bottom line is I'm looking for the most reliable SSD and willing to sacrifice some speed if necessary.

Any thoughts if the Crucial (P1 or P2) fits the bill for me?

Many thanks in advance.

I've a Sabrent Rocket 1TB installed in my E-2015 13" MBP (since c. 2019), and it still performs (it Rocks, IMNSHO) . . . battery-life has been somewhat reduced, but this gum-stick has been entirely performant.

No complaints.

Regards, splifingate

 

[rogerdsw6]

Macbook late 2013 upgrade: have no fear it is worth it!
No problem with Big Sur, No hybernation problem with new NVMe SSD!

I would like to confirm that I have upgraded my MacBook 11,1 late 2013 13'' (16GB RAM)with the latest version of Big Sur (March 2021). The upgrade worked perfectly well.

I then decided to replace the SSD using a Crucial P2 512SSD with the syntec adapter. I did an install from scratch using an external USB drive with a copy of Big Sur. The write speed has increased by almost x5 (from 220 to 1100) and the read speed by almost x3 (from 500 to 1300). it is running very smoothly and feels like a brand new great laptop!!!

No need to disable standby or hibernation. I have now used for 2 weeks with default settings and it never had a kernel panic as was previously reported in 2020 by other users.

I tried SsdPmEnabler but It created a crash at boot so disabled it (that was not too hard as there are good guidelines provided to do this).

Power consumption may be a bit higher but I had selected the crucial P2 as it seemed to have the best compromise between speed and power consumption.

upgrade, you will not regret it!

 

[Ektachrome]

Hello All,

Would someone experienced on here be kind enough to give me a quick idea of whether upgrading my MacBook Pro will be problematic or not, please?

I've read the first post and some of the later pages, but still a little uncertain whether my machine would need an EFI boot mod or anything else to work correctly with sleep, etc., or if I'd be good to go with just a replacement and reinstall? It's my main work computer, so that's the reason for checking.

Not sure which specs are most relevant, main ones below, but happy to provide other info if it helps!

MacBook Pro Retina, 15-inch, Late 2013
2.3 GHz Quad-Core Intel Core i7
16GB 1600MHz DDR3
NVIDIA GeForce GT 750M 2 GB
Intel Iris Pro 1536 MB

Mac OS Big Sur 11.2.3 (20D91)

I would be intending to install:
Sintech adapter (latest version)
Crucial P2 2TB

Unless there are better options for less glitches/reliability/battery, etc.?