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

[Xaphier]

Yes, I just updated to Monterrey and the first crash happened as I was trying to order some pictures on the photo app. I installed DriveDx which didn't start to report until very recently Media and data integrity errors (currently at 76) which wasn't a thing before. Whenever I boot the mac, wake it from hibernation or start doing task that require constant SSD reads the count for integrity errors increases and sometimes it even crashes. It actually begins with a spinning rainbow circle, then the screen fades to black and I got a prohibitory symbol or a folder with a question mark. At first i got scared thinking the ssd might have gotten corrupted but restarting fixes it albeit I get that kernel panic log which i shared earlier. I am starting to realize that this is probably an incompatibility issue arising from Monterey itself.

Would you mind installing DriveDx (has a free trial) to see if yours also reports Media and data integrity errors?

I think we have similar experience. Now that I think about it, the crashes usually happened when there are some high read activity. (Downloads, Waking Up, etc). If the crashes continue, I might explore the option to downgrade to Big Sur.

I have installed DriveDX, will update here if it start to reports Data integrity errors.

 

[iKalamaZoo]

It seems to be even lower than the Crucial P2 standby which is around 0,12 A. Very nice.

Yep. But, sometimes, not too frequently, it gets 0,16A! So, I would say that there's a range between 0,10~0,16A. A2000 can be an energy hog like any NVMe! I think that the point here could be my inactivity at that very moment. Anyway, I think that 0,10A could not be considered as a standard form A2000. I would say that something between 0,12~0,15A would fit better.

 

[coso]

Yep. But, sometimes, not too frequently, it gets 0,16A! So, I would say that there's a range between 0,10~0,16A. A2000 can be an energy hog like any NVMe! I think that the point here could be my inactivity at that very moment. Anyway, I think that 0,10A could not be considered as a standard form A2000. I would say that something between 0,12~0,15A would fit better.

That would be in line with tom’s hardware review, dividing the watts consumption by the voltage (3,3V). The P2 QLC has still a lower idle consumption then according to their measurements. Still the A2000 is not bad

 

[iano7000]

Samsung 980 installed. Running well below benchmark - Macbook 11,5.
Am I doing something wrong? Is there a secret firmware patch? Otherwise I will return this and swap for an 970 Evo Plus.

Using Sintech mini adapter.
Firmware 1B4QFXO7
Tried a SMC reset - needed to unplug battery with power disconnected in order to get my mac to boot after performing this.

 

[herb2k]

And... without these extensions? I heard most of the time they're fine, but they can also cause trouble. Not sure to what extent though, should browse more the thread

No trouble at all without the extensions. They are primarily used to reduce idle power consumption and heat output.

 

[SalRunyon]

Also it's been 2 weeks I'm using every day a Sabrent 4TB and I am so far very satisfied : low power consumption, stable, fast !

First of all, thank you. This is really amazing work. A gift to the community. I almost bought a 2019 MacBook Pro with touch bar because I thought it was the only option besides shelling out a small fortune on the new 16".

How did the Sabrent 4TB on your 15" MacBook Pro work out? I'm considering getting a Mid 2015 MacBook Pro and a Sabrent 4TB. From what I'm reading here, it seems like, other than an 8TB, that's the best of all worlds. Could I do better? My main concern is avoiding kernel panics and other glitches. I'd like to have this machine for years to come (at least 3 or 4). I don't need the latest Mac OS. I tend to stay a few versions behind.

Any help very much appreciated!

 

[herb2k]

I could not figure out from any of the posts whether a new MacOS than the 10.14.6 i am running might support NVMexpress power saving modes. Can anybody confirm that they don't or that they do ?

They do not.

 

[blulitespecial]

Alright, I'm at my wits end here.

MacBook Pro (Retina, 13-inch, Late 2013)
Mojave 10.14.6
Boot ROM Version: 432.40.8.0.1
MacBookPro11,1

I have an original Apple 256gb ssd, and bought a SK Hynix P31 Gold 1TB + Sintech adapter to upgrade. I've followed the above steps, and go all the way to the P31 firmware update, but the drive shows as "Not Responding" in the Hynix firmware update tool.
I have Windows 10 To Go on a 64gb external ssd, with Boot Camp drivers installed. P31 drive is installed internally. Ran Windows updates as well.

The P31 shows up in Disk Management in Win10 with correct 1TB capacity, but is not assigned a drive letter.
Previously, I tried updating the P31 firmware with it in an external enclosure, but that gave the "Not Responding" in the update tool too.

I don't think the P31 is faulty, because I was able to install Big Sur on it, and boot from it externally. However, once I installed it internally, it gave a "not permitted" symbol on boot up. Assuming this is because of the ssd firmware not being up to date.

I was suspecting that the Sintech adapter could be faulty, but if the P31 shows in Win10 Disk Management, then the drive is being recognized and I assume that rules out faulty hardware. I've gone through many different google searches, and reseated the P31 and adapter many times now. Not sure what to try next.

For future notice, in case anyone runs into a similar issue. My brand new SK Hynix P31 Gold was "write protected" out of the box. I've never heard of this before, but after doing some digging, I figured it out. Somehow, I was able to format it in macOS. I was unable to format it in Windows 10. It would show up in windows as a letter drive, but I couldn't do anything with it. It showed up in disk management, but any attempts to interact with it would cause it to disappear. It would not show up in diskpart at all. I followed several guides online and couldn't get the write protection turned off. It would either not show up or error on attempted changes. Not sure why macOS was able to use the drive but not Windows. So strange.

I bought a MP510, which worked easily. Booted into Big Sur installer drive, formatted MP510, and installed without issue.

 

[te36]

Oh now I get the graphs. The QLC P2 is still the most low power consuming SSD, but in some tasks it's so slow that it will keep running more time than other SSDs to complete the job, hence it will end up consuming more power

The question is just whether the powr hungry jobs are what you're doing when you are runnin on battery. Copying half a disk for backup or so is maybesomething i am doing when on power supply, so most of my battery time is for low-disk-access ...

 

[coso]

The question is just whether the powr hungry jobs are what you're doing when you are runnin on battery. Copying half a disk for backup or so is maybesomething i am doing when on power supply, so most of my battery time is for low-disk-access ...

Yes, the P2 could still be a good choice (the best?) for light tasks and to preserve the battery the most

 

[mork4]

My Mid 2015 15" MBP with 1TB Sabrent SSD (Sintech adapter) started to crash a lot after upgrading to Monterey. I had almost 0 crashes during Big Sur, but now I get 3 to 4 crashes a day, very frustrating. I updated to Monterey by swapping the drive to original Apple SSD and update to Monterey, swap to Sabrent SSD with adapter and update to Monterey again.

Crash logs for those who are interested:

Spoiler

panic(cpu 0 caller 0xffffff8016542836): nvme: "3rd party NVMe controller. Loss of MMIO space. Write. fBuiltIn=1 MODEL=Sabrent FW=ECFM12.2 CSTS=0xffffffff US[1]=0x0 US[0]=0x5a VID=0x1987 DID=0x5012 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6053
Panicked task 0xffffff853f2606a0: 167 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff8541fb8b70, Frame : Return Address
0xffffffd04c6bbaa0 : 0xffffff8013c9c00d
0xffffffd04c6bbaf0 : 0xffffff8013df5d85
0xffffffd04c6bbb30 : 0xffffff8013de5763
0xffffffd04c6bbb80 : 0xffffff8013c3ba60
0xffffffd04c6bbba0 : 0xffffff8013c9c3dd
0xffffffd04c6bbcc0 : 0xffffff8013c9bb96
0xffffffd04c6bbd20 : 0xffffff8014518649
0xffffffd04c6bbd90 : 0xffffff8016542836
0xffffffd04c6bbda0 : 0xffffff8016525ac7
0xffffffd04c6bbdd0 : 0xffffff8014460c75
0xffffffd04c6bbe40 : 0xffffff8014460b78
0xffffffd04c6bbe70 : 0xffffff8013cecc85
0xffffffd04c6bbee0 : 0xffffff8013cedcd2
0xffffffd04c6bbfa0 : 0xffffff8013c3b18e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[5D151865-3739-3750-ABC7-3F081504A6A6]@0xffffff801651d000->0xffffff8016549fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[BB7769F7-6389-3ABC-A6CF-2BC079FA7BF8]@0xffffff801536f000->0xffffff8015390fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[5E1B0BE0-4B73-35F5-9126-EB05FBB8BAF5]@0xffffff80167ee000->0xffffff8016818fff
dependency: com.apple.iokit.IOReportFamily(47)[81D7D4E0-A39C-332D-A4A4-AEBB70A9B6FF]@0xffffff801682a000->0xffffff801682cfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[6637C48D-A128-3A23-A8F4-96CD5CA12779]@0xffffff801692f000->0xffffff8016945fff

Process name corresponding to current thread (0xffffff8541fb8b70): kernel_task

Mac OS version:
21A559

Kernel version:
Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64
Kernel UUID: 19BD4E1B-0268-3EE0-BC66-91F035BC9429
KernelCache slide: 0x0000000013a00000
KernelCache base: 0xffffff8013c00000
Kernel slide: 0x0000000013a10000
Kernel text base: 0xffffff8013c10000
__HIB text base: 0xffffff8013b00000
System model name: MacBookPro11,4 (Mac-06F11FD93F0323C5)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 75737950419
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000011a25578fa
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000002a64e0b96 0x0000000000000000
Zone info:
Foreign : 0xffffff80192f2000 - 0xffffff80192ff000
Native : 0xffffff80319a8000 - 0xffffffa0319a8000
Readonly : 0 - 0
Metadata : 0xffffffe658cb4000 - 0xffffffe678e3b000
Bitmaps : 0xffffffe678e3b000 - 0xffffffe67ee3b000
last started kext at 34412504411: >driverkit.serial 6.0.0 (addr 0xffffff7fac2d1000, size 28672)
loaded kexts:
>AGPM 125
>X86PlatformShim 1.0.0
>!APlatformEnabler 2.7.0d0
@filesystems.autofs 3.0
@fileutil 20.036.15
>!AHDAHardwareConfigDriver 283.15
>!AHDA 283.15
>!AUpstreamUserClient 3.6.8
>eficheck 1
>!AGraphicsDevicePolicy 6.4.9
@AGDCPluginDisplayMetrics 6.4.9
>!ALPC 3.1
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!A!IHD5000Graphics 18.0.2
>!AHV 1
>!ADiskImages2 126.40.1
>!ACameraInterface 7.8.0
>!ASMCLMU 212
>!AFIVRDriver 4.1.0
>AGDCBacklightControl 6.4.9
>!ABacklight 180.3
>!AMuxControl 6.4.9
>ACPI_SMC_PlatformPlugin 1.0.0
>!AMCCSControl 1.14
>!A!ISlowAdaptiveClocking 4.0.0
>!A!IFramebufferAzul 18.0.2
>!AThunderboltIP 4.0.3
|SCSITaskUserClient 452.30.4
>!ATopCaseHIDEventDriver 5010.1
>!UTopCaseDriver 5010.1
>!UCardReader 532.40.7
@filesystems.apfs 1933.41.2
>AirPort.BrcmNIC 1400.1.1
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.lifs 1
@filesystems.hfs.kext 582.40.4
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@private.KextAudit 1.0
>!ASmartBatteryManager 161.0.0
>!ARTC 2.0.1
>!AACPIButtons 6.1
>!AHPET 1.8
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 402
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
@Dont_Steal_Mac_OS_X 7.0.0
@kec.!AEncryptedArchive 1
>driverkit.serial 6.0.0
|IOSerial!F 11
@kext.triggers 1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>!UAudio 412.8
>!AAudioClockLibs 100.9.1
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOAudio!F 300.10
@vecLib.kext 1.2.0
|IO!BSerialManager 9.0.0
|IO!BPacketLogger 9.0.0
|IO!BHost!CUSBTransport 9.0.0
|IO!BHost!CUARTTransport 9.0.0
|IO!BHost!CTransport 9.0.0
>IO!BHost!CPCIeTransport 9.0.0
|IOAVB!F 1010.2
@plugin.IOgPTPPlugin 1000.11
|IOEthernetAVB!C 1.1.0
|CSR!BHost!CUSBTransport 9.0.0
|Broadcom!BHost!CUSBTransport 9.0.0
|Broadcom!B20703USBTransport 9.0.0
>!AIPAppender 1.0
>!ASMBusPCI 1.0.14d1
>!ABacklightExpert 1.1.0
|IONDRVSupport 593
>!AGraphicsControl 6.4.9
>IOPlatformPluginLegacy 1.0.0
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
>!ASMBus!C 1.0.18d1
@!AGPUWrangler 6.4.9
|IOSlowAdaptiveClocking!F 1.0.0
|IOAccelerator!F2 462.4
@!AGraphicsDeviceControl 6.4.9
|IOGraphics!F 593
>!AThunderboltEDMSink 5.0.3
>!AThunderboltDPOutAdapter 8.5.0
>!AActuatorDriver 5400.25
>!AHS!BDriver 5010.1
>IO!BHIDDriver 9.0.0
>!AMultitouchDriver 5400.25
>!AInputDeviceSupport 5400.30
>!AHIDKeyboard 228
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AThunderboltDPInAdapter 8.5.0
>!AThunderboltDPAdapter!F 8.5.0
>!AThunderboltPCIDownAdapter 4.1.1
>!AXsanScheme 3
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
|IO80211!FLegacy 1200.12.2b1
|IOSkywalk!F 1.0
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
>!A!ILpssGspi 3.0.60
|IONVMe!F 2.1.0
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!ABSDKextStarter 3
|IOSurface 302.9
@filesystems.hfs.encodings.kext 1
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
|IOTimeSync!F 1000.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 9.0.0
|IOReport!F 47
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 532.40.7
|IOUSBMass!SDriver 209.40.6
|IOSCSIBlockCommandsDevice 452.30.4
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 452.30.4
>!AMobileFileIntegrity 1.0.5
$!AImage4 4.1.0
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 12.0

Have you installed also Lilu, NvMEfix and SSDPMEnabler ?

 

[te36]

With Kingston A2000 you'll get original kexts from Apple, without any additional command or workarounds, everything will be installed from Apple original release candidate package. Anyway, any workarounds, additional kexts and and other commands are unnecessary with Kingston A2000. Just buy, put it in Sintech adapter, plug and install your clean macOS. Done! Every single thing working like and original Apple SSD.

Can you point me to the place where you sourced this information from ? I am trying to understand why the Kingston A2000 would be treated differently, and if so, by which MacOS version. Is this the same HW as used in some MacBooks originally ?

 

[olfo]

I am beginning to get an idea of the power states that NVMe SSDs can have, after I have read this article:

NVMe™ Technology Power Features

NVMe™ Technology Power Management Features NVM Express (NVMe) architecture contains various features to manage the power of SSDs. In the data center, this can be used to throttle an SSD to a specific TDP (thermal design power) to manage platform thermals and total power draw. Max power is...

nvmexpress.org

Now when I look at the numbers from smartctl, they make kind of sense to me.
I have noticed that the (only slightly restricted) Demo version of SMARTReporter will show this too. In case you are interested:

Mac SMARTReporter - protect your data with disk failure prediction

mac app to monitor hard disk drive health

www.corecode.io

Also the info on Anandtech is now more readable for me. They are comparing the power states of the SSDs they test.
For example:

The Corsair Force MP510 SSD (960GB) Review: A High-End Contender

www.anandtech.com

The Best NVMe SSD for Laptops and Notebooks: SK hynix Gold P31 1TB SSD Reviewed

www.anandtech.com

“Idle Power no PM” should come very close to what is discussed here recently.
While the “Idle Power consumption” results are giving an idea what could be possible with SsdpmEnabler, I suppose. This kext works very nicely, btw.

 

[ultimaDC]

Anyone who has succeeded using Monterey (without so much crashing) via patch with NVME on Macbook Pro 11,1?

 

[te36]

I have now tried a Patriot P300 M.2 1TB and it does go down to 0.04A report in iStat Menus, so it comes closest to the low point of 0.03A from my original Apple SSD. Of course, no measuremt of power consumption under load, AFAIK i have not suffficient tools to easily measure that in comparison.

 

[coso]

I have now tried a Patriot P300 M.2 1TB and it does go down to 0.04A report in iStat Menus, so it comes closest to the low point of 0.03A from my original Apple SSD. Of course, no measuremt of power consumption under load, AFAIK i have not suffficient tools to easily measure that in comparison.

with kexts?

 

[te36]

with kexts?

I installed Lilu, NvMEfix and SSDPMEnabler kext. I have not figured out if/why i would want Lilu or NvMEfix. WOuld be interested to learn what they might be good for in addition to SSDPMenabler.

I guess i should try to install Monterey and verify that it runs wihout kext at low power ?! That would seem to be the one unique benefit of The Kingston ???

 

[coso]

I installed Lilu, NvMEfix and SSDPMEnabler kext. I have not figured out if/why i would want Lilu or NvMEfix. WOuld be interested to learn what they might be good for in addition to SSDPMenabler.

I guess i should try to install Monterey and verify that it runs wihout kext at low power ?! That would seem to be the one unique benefit of The Kingston ???

Thanks. No I think the Kingston is the same as other SSDs, without ssdpmenabler it will have the stated idle current as per its data sheet. The general consensus is that if you already had an updated bootrom then you can update with no problems to Monterey. But I don't know, don't do anything you don't want do to 😆

 

[te36]

Oops, i meant to say i only installed SSDPMEnabler, and i don't know what Lilu, NvMfix would be good for.

 

[te36]

Ok, did a fresh install of Monterey on my 2015 MBP using Kingston P2. Install went fine, no problems. But iStat Monitor shows pretty persistent 0.13A...0.15A. Of course without SsdpEnabler. Alas, I did not check with Mojave in the absence of SsdpEnabler. But certainly not the lowest power consumption of 0.04A that I saw with Mojave and SsdpEnabler.

 

[nicopulse]

Hello,

See this benchmark result on the same MacBook Pro mid-2014, 15". Intel Core i7 2,5 Ghz. 16 Go RAM. nVidia GT750m 2 Go video ram.

I can see bad performance on OWC random write... it's normal. ?

OWC Aura Pro X2 :

SK Hynix Gold P31 :

 

[mork4]

Hello,

See this benchmark result on the same MacBook Pro mid-2014, 15". Intel Core i7 2,5 Ghz. 16 Go RAM. nVidia GT750m 2 Go video ram.

I can see bad performance on OWC random write... it's normal. ?

OWC Aura Pro X2 :
View attachment 1903181

SK Hynix Gold P31 :
View attachment 1903185

If you want to see relevant and real difference between two test, you have to use exact or at least same settings on benchmark app. Merge test count and test size and try again 😊

 

[nicopulse]

ok I remake test. better performance with more data (64 Go), lol :

 

[dw2116]

OK. I eventually put a SK Hynix Gold P31 into my MacBookAir6,2. Here are the steps I took in order:

1. Update the OS of MBA6,2 to macOS Big Sur
2. Create a bootable macOS installer on a USB drive
3. Install Parallels Desktop for Mac (free 14-day trial)
4. Install Rufus for Windows in Parallels and use Rufus to create a Windows To Go USB drive
5. Cancel Parallels Desktop for Mac (before the end of free 14-day trial)
6. Remove the OEM hard drive and insert P31 + Sintech adapter
7. Boot with Windows To Go USB drive
8. Install SK hynix Drive Manager in Windows To Go and download the latest P31 firmware
9. Use Drive Manager to bring the firmware of the P31 drive to the latest
10. Boot with macOS installer USB drive, format the P31 drive, and install a fresh macOS or migrate a Time Machine backup
11. Done!

 

[nicopulse]

D'ACCORD. J'ai finalement mis un SK Hynix Gold P31 dans mon MacBookAir6,2. Voici les étapes que j'ai suivies dans l'ordre :

1. Mettre à jour le système d'exploitation de MBA6,2 vers macOS Big Sur
2. Créer un programme d'installation macOS amorçable sur une clé USB
3. Installez Parallels Desktop pour Mac (essai gratuit de 14 jours)
4. Installez Rufus pour Windows dans Parallels et utilisez Rufus pour créer une clé USB Windows To Go
5. Annuler Parallels Desktop pour Mac (avant la fin de l'essai gratuit de 14 jours)
6. Retirez le disque dur OEM et insérez l'adaptateur P31 + Sintech
7. Démarrez avec la clé USB Windows To Go
8. Installez SK hynix Drive Manager dans Windows To Go et téléchargez le dernier firmware P31
9. Utilisez Drive Manager pour mettre à jour le firmware du lecteur P31
10. Démarrez avec le lecteur USB du programme d'installation macOS, formatez le lecteur P31 et installez un nouveau macOS ou migrez une sauvegarde Time Machine
11. Terminé!

The same !
But I use WinToUSB instead of Rufus because rufus don't make a bootable usb for me.