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

[just_a_tiny_question]

While Apple doesn't test MacOS on most 3rd-party hardware, NVMe SSDs are the least you should worry about. If it works now, there is no reason to fear it will stop working in new versions for the foreseeable future.

I would install both ssdpmEnabler & NVMeFix (+Lilu) for ADATA SX8200 Pro.

So you'd recommend going with the latest install of Big Sur?
After installing both ssdpmEnabler & NVMeFix (+Lilu), are there any extra steps needed, if I choose to update the next to version of Big Sur in the future? Should they be uninstalled?

 

[developeralioz]

Hi! Thanks for replying Nice to know I am not alone.

Can you post your setup and any Kernel Panic dumps? How often do you get this issue?

In my case NVMeFix, SsdPmEnabler may have fixed the issue I have not experienced any crashes since these were installed (so far!).

I checked my logs and the crash would happen to me between ~30 minutes and 4d 20h after bootup:

Spoiler

$ cat kp-nvme.txt | grep uptime
System uptime in nanoseconds: 33855789329764
System uptime in nanoseconds: 2087773860540
System uptime in nanoseconds: 30905369385053
System uptime in nanoseconds: 131723330659273
System uptime in nanoseconds: 32007630172
System uptime in nanoseconds: 142488114283417
System uptime in nanoseconds: 3256836841426
System uptime in nanoseconds: 418031993376019
System uptime in nanoseconds: 64680443225
System uptime in nanoseconds: 14912135267264
System uptime in nanoseconds: 191590566078998
System uptime in nanoseconds: 32423915462535
System uptime in nanoseconds: 22176681559667
System uptime in nanoseconds: 52706238208914

(average uptime at crash: 21h 21m ; sdev: 1d 6h )

However, since installing NVMeFix and SsdPmEnabler my current uptime is over 5 days:

$ uptime
15:15  up 5 days,  1:37, 2 users, load averages: 1.86 2.76 3.24

According to Chebyshev's inequality, getting ~5 days of uptime (4 * standard deviation), I can be 94% sure that the lack of a crash is not an anomaly. After about 11 days of uptime I will be 99% sure. I will check back in a couple of days how far I make it without an IONVMeController kernel panic. If crashes are normally distributed, then the confidence can be much higher (99.99...% and sooner (~7 days)), but I have not checked the distribution of my crashes.

A quick google search reveals that this issue happens in almost all versions of MacOS including in the newer Catalina and Big Sur. I'm glad I never upgraded to Catalina. In those only the kext/kernel versions and line number of the panic are different. Interestingly, the issue happens to both aftermarket and genuine nvme ssd sticks, although more common with aftermarket sdds and around sleep/wake. (This is why editing sleep settings helps.) So it points to a bug in the Apple IONVMeFamily driver with timeouts, that is more often triggered by aftermarket SSDs. Many SSD manufacturers controller builders have no motivation to offer us a fix as they do not support macs.

IONVMeController Mojave crashes "IONVMeFamily-387.260.15/IONVMeController.cpp:5334" (100+ results), e.g. with both Apple and non Apple SSDs https://discussions.apple.com/thread/250380026

IONVMeController Catalina panic "IONVMeFamily-470.100.17/IONVMeController.cpp:5320" (1000+ results), e.g. with Apple SSD https://discussions.apple.com/thread/251202030

IONVMeController Bug Sur panic "IONVMeFamily-557.40.12/Common/IONVMeController.cpp:5471" (~10 results), e.g. with Apple SSD https://discussions.apple.com/thread/252100672

I'm sure those lines point to some kind of timeout trap and I assume there are many more with this issue out there who have not posted anything online. I only posted after 2+ years, once I realised that I had saved some of the kp dumps in Notes.

edit: fixed typos.

I usually get a kernel panic error once a week. I will share the report with you when I get the next kernel panic error.

I use Big Sur. I'll be installing Catalina next week. I will let you know if there is a change.

 

[mclovely]

Hi all, just found this thread and thank you so much, there is great info on here.
I recently installed a OWC 1.0TB Aura Pro X2 in my Mid 2015 15" MacBook Pro running Catalina and have been continuously experiencing the hibernation issues with it even crashing during use. I was totally confused as to why my MacBook was acting up. As a result, I am returning the OWC Aura Pro and was wondering what is the best SSD to replace it with and is there anything else I need to do. Any help is most appreciated.

 

[trippingale]

Greeting to everyone,
I have just upgraded to a A1398 (mid2014) MBP using Big Sur V 11.2.1 I am looking to upgrade the SSD to the biggest the system can handle and since the start of this thread in 2017, a lot of technology has developed and become much more cost effective and available.

Can anyone please make a recommendation of current or readily available M.2 NVME chip(s) to use with a Sintech adaptor, Speed is obviously secondary due to bottlenecks in the system and the majority of the use would be streaming MP4 vids, storage capacity is primary factor to be a library without the external drives.

Thank you in advance
Best regards
Thomas

 

[fiveangle]

Can anyone please make a recommendation of current or readily available M.2 NVME chip(s) to use with a Sintech adaptor...

Thomas- I just purchased the lastest HW rev of the venerable Adata XPG SX8200 Pro and Sintech adapter, did a fresh install of 11.2.2 then used migration assistant to re-import all my apps and user data from my TimeCapsule backup and it all went without a hitch. If I had to do it again, I would probably clone my drive to a USB3 external HD using SuperDuper! or CarbonCopyCloner instead to make the import faster.

But I'm more than happy with the results: it essentially increased by performance by about 1/3rd and doubled my space (2TB):

Through my affiliate link it is on sale right now with a $30 instant coupon which puts it at the same or better than most QLC units: https://www.amazon.com/gp/product/B...e5e986b5feae5&language=en_US&ref_=as_li_ss_tl

BTW- Does anyone have a recommendation on where would be the best place to list my original late 2013 1TB Apple SSD for sale ? I checked eBay for completed listings and didn't see any nor any current listings, so I'm thinking that might not be the best place ?

Thanks !

-=dave

 

[trippingale]

I just purchased the lastest HW rev of the venerable Adata XPG SX8200 Pro and Sintech adapter,

Thank you Dave for the 2TB recommendation

My old computer was 2TB 2.5"SATA SSD and I had to import and export libraries via external drives, I am hoping to get a confirmation that 4TB can work for the Mid 2014 rMBP
Best regards
Thomas

 

[vince22]

Thomas- I just purchased the lastest HW rev of the venerable Adata XPG SX8200 Pro and Sintech adapter, did a fresh install of 11.2.2 then used migration assistant to re-import all my apps and user data from my TimeCapsule backup and it all went without a hitch. If I had to do it again, I would probably clone my drive to a USB3 external HD using SuperDuper! or CarbonCopyCloner instead to make the import faster.

But I'm more than happy with the results: it essentially increased by performance by about 1/3rd and doubled my space (2TB):

View attachment 1737891

Through my affiliate link it is on sale right now with a $30 instant coupon which puts it at the same or better than most QLC units: https://www.amazon.com/gp/product/B...e5e986b5feae5&language=en_US&ref_=as_li_ss_tl

BTW- Does anyone have a recommendation on where would be the best place to list my original late 2013 1TB Apple SSD for sale ? I checked eBay for completed listings and didn't see any nor any current listings, so I'm thinking that might not be the best place ?

Thanks !

-=dave

try local no fees. Facebook Marketplace or OfferUp, why not keep it just in case you will sell that MacBook someday.

 

[fiveangle]

I am hoping to get a confirmation that 4TB can work for the Mid 2014 rMBP

You didn't mention that in your request, just "largest" which doesn't really mean much.

4TB is still at some ridiculous premium $$$/TB that obvi doesn't reflect the component costs market rate so less people buying them. There are 8TB and just released 16TB units as well btw. Good luck !

 

[trippingale]

Hi Dave
My Apologies if you feel misled, I was being vague intentionally because there are many options on the table and I am not sure where reality stands ( what is compatible). I have talked to the manufacturers of the SSD, Sintech and repair centers and know one can give a strait answer.

I never mentioned in my original post "$$$/ TB', with one slot available and size limitations, the only option is to pay higher premiums for the larger storage on same size chip platform. When I bought my original 2TB 2.5" ssd for my old MBP, it was over $800.

I mentioned in my previous post technology has developed and become much more cost effective, I was hopping someone could guild me to help define the upper limits of what size the boot rom and (system) will allow, I had originally budget slated for 8TB, before I start spending I think it would be wise to know the limits before waisting money to find out that its not compatible.

Best regards
Thomas

 

[mclovely]

"Too much of a good thing." - that's how I would describe this massive post! LOL
I've spent 3 days scouring this 8400+ post repository, and I'm now suffering from Paralysis of Analysis.

Initially, I was excited to read that my 15" mid-2015 MBP (11,4) is 'special' in that it's capable of faster storage speeds due to its' PCIe 3.0x4 configuration. That excitement has steadily faded as it doesn't appear that many people are testing/reporting performance on this model.

I find great reports of blazing speed for certain drives, and reports of incredibly low power consumption for others - but that's while installed in something other than the 15" mid-2015 MBP I own.

Is there a suggested route of NVMe upgrade for this oddball MBP I have? While I'd certainly love fast reads/writes (I love my virtual machines via Fusion), I'm also appreciative of battery life for the long study sessions that are happening more and more frequently and power outlets are not always available.

I'm looking to replace the factory 256GB drive with a 1TB drive, and I should mention that I'm running Big Sur 11.2

Thanks everyone!

Did you manage to select a drive for your MacBook? I also have a 15" mid-2015 MBP (11,4) and I am unsure as to which drive to go for.

I am running Catalina with Boot ROM Version: 425.0.0.0.0 and recently installed an OWC 1.0TB Aura Pro X2 but it's crashing A LOT.
I'm considering the Crucial P2 but want to make sure I don't experience what has been happening with the current OWC drive I have installed.

 

[xboxbml]

Hello! Thanks for your answer!

May I ask you why you're thinking about going back to Mojave?


I'm talking about NVMeFix, SsdPmEnabler, Lilu that a lot of people seem to be installing.

Oh ok.. I don't use those. I'm fine with battery life on this. Leave it plugged in mostly now anyway.. Mojave? Cuz it runs a bit smoother than Catalina and has slightly better battery life and still had 32bit support.. Newer OS usually means more things running in the background taking up battery and resources. Terminal functionality was more open until the later versions of Mojave and apple started locking things down more. I know.. onward and upward.. Really I think I only went up to Catalina cuz I wanted dark mode.. Almost went back down right away but I was able to finally get my "unsupported" printer working in Catalina. Otherwise I woulda had to buy a new printer.

 

[padams35]

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.

Admittedly Black Magic Read/Write speeds have been slower than expected... about 1150 MB/s Read and 1000 MB/s write, but that is still a bit faster than the 128GB Apple SSD I replaced.

Maybe Black Magic is slow on the read? Is there a second speed tester worth trying? (For science on the 'slower than expected P2 mystery'... its easily fast enough for my use).

Edit: Perhaps the 'slow' speed is because I formatted the drive as APFS(encrypted)? Is everyone with slower than advertised performance using encryption? As anyone with an unencrypted drive seeing significantly slower than advertised speeds?

 

[fiftystorm]

I tested a Crucial P2 2TB on my 2015 MacBook Pro 13" Retina. I also tried Bootcamp to install Windows 10. No issues so far.

Setup:
Mojave 10.14.6 (18G8022)
MacBookPro12,1
Intel Core i7 3.1 GHz
Boot ROM Version: 426.0.0.0.0
Crucial P2 2TB + Sintech short adapter
AC Power Adapter connected

Idle power draw:
None - 0.10 A
NVMeFix - 0.10 A
SsdPmEnabler - <0.01 A
NVMeFix + SsdPmEnabler - <0.01 A

iStat indicates 0.00 A most of the time just occasionally 0.01 A so I guess it stays between zero and 0.005 A. It's the same exact drive I tested on my 2015 MacBook Air (see my previous post #8427) and it behaves pretty much the same on MBP except it idles even better!

 

[FF89]

Hello Everyone,

First of all, I would like to thanks everyone for contributing valuable information regarding the NMVe SSD upgrade for Macbook Pro Late 2013-Mid 2015. I am from Malaysia (Southeast Asia) and have been following this thread since last month.

It is time for me to contribute to this thread based on my personal experience following recommendation here.

First of all, this is my rMBP specification:
Apple MacBook Pro 15-Inch "Core i7" 2.2 Mid-2014 (IG) Specs (MGXA2LL/A - MacBookPro11,2 - A1398 - 2876) which is the base model (https://everymac.com/systems/apple/...-iris-only-mid-2014-retina-display-specs.html)

Before I upgrade the storage, the rMBP is already running on macOS Big Sur 11.2.2. Therefore, the system firmware of rMBP already updated to 430.0.0.0.0.

Next, I upgraded my rMBP to Crucial P2 1TB NVMe SSD (~ USD119.34 direct conversion from my country's currency) using NFHK N-941A short adapter (~ USD 3.67 direct conversion from my country's currency). No point in choosing faster storage because my rMBP can only achieve around 1300 MBps in read/write due to PCIe 2.0 x2 storage interface. The price also is very affordable for a 1TB capacity. (But the most important thing is, many in here recommended this NVMe SSD for the upgrade. I am thankful to everyone for this recommendation. Thanks).

I also ordered the recommended Sintech Short Adapter as suggested on Post #1 at USD8.99 directly from Sintech. Still waiting for it to arrive, going back and forth from Shenzhen to Guangzhou for 2 weeks already. In the mean time, I review based on the NFHK N-941A short adapter.




After the storage upgrade, the rMPB was freshly installed with macOS Big Sur 11.2.1 using a bootable USB made in one partition of external drive (Samsung 850 Evo Sata 3 SSD inside Orico USB 3.0 SSD Encloure).

No issue during the installation, the rMBP is connected to the power supply during the installation process.

Just to make sure that my NVMe SSD firmware is up-to-date, I have installed latest Windows 10 (20H2) (ISO downloaded from Microsoft) by using BootCamp Assistant on a Sandisk Ultra 32GB USB3.0 Flash Drive. Again, I make sure my rMBP is connected to power supply during the whole installation process. Only a minor hiccup I had encountered at first reboot before installing window, I need to press option key on the keyboard to select and load the efi of the Windows 10 Bootable USB. other than that, No issue was found. The installation of Windows 10 was smooth. Make sure to install the bootcamp driver, and perform Apple software update after that.

Next, I installed the Crucial Storage Executive on Windows 10. Luckily, I don't need to update my NMVe SSD Firmware because it is already up-to-date.

After complete verifying the NMVe SSD firmware, I just notice that a new full installer of macOS Big Sur 11.2.2 is available on the App Store. So, I download and made a new bootable usb and install the new macOS update using the bootable usb (without erasing the previous installed macOS 11.2.1 on the NVMe SSD) for the sake of testing if there is any issue if performing macOS update on a non-Apple SSD. The reinstallation process ran smoothly without any problem.

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.

Finally I test for the hibernation issue by letting the rMPB sleep overnight. At this point, the hibernation should occured around 3 Hours after the rMBP sleep by default. I left the rMPB for more than 9 Hours. In the morning, the rMBP woke up without any issue. Only small battery drain about 6% was seen (I assume about 2% per hour before hibernation). Therefore, I can conclude that, the rMBP can go into hibernation mode after 3 Hours since so little battery drain. But this is really not a major concern for me since my habit of shutting down the rMBP daily before I am going to bed.



Overall, I am really satisfied with the outcome.



I would like to thank everyone here for your knowledge sharing and contribution to the thread.

 

[AstroZero]

I usually get a kernel panic error once a week. I will share the report with you when I get the next kernel panic error.

I use Big Sur. I'll be installing Catalina next week. I will let you know if there is a change.

Please do let me know, I would be very interested to see if our issues are related. This morning I thought things were all but fixed for me as uptime was:

$ uptime
10:16  up 7 days, 20:37, 2 users, load averages: 1.90 2.66 3.24

I had been cleaning up some things on my mac and had just removed an old Soundflower kext driver. But then, disaster. I had four kernel panics in quick succession. I have saved the logs. I was worried about losing my data I wonder if some caches were being rebuilt and those trigger the error?

The panic after nearly 8 days was:

Spoiler: kernel panic

Anonymous UUID:       A7C31D85-6317-5343-3599-E326142FC9B8

Thu Mar  4 10:19:38 2021

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8f255b30): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x46 VID/DID=0x50121987
. FW Revision=ECFM12.3\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.270.1/IONVMeController.cpp:5334
Backtrace (CPU 0), Frame : Return Address
0xffffff8121513a10 : 0xffffff800c1ae5ad
0xffffff8121513a60 : 0xffffff800c2ea1f5
0xffffff8121513aa0 : 0xffffff800c2db92a
0xffffff8121513b10 : 0xffffff800c15b9d0
0xffffff8121513b30 : 0xffffff800c1adfc7
0xffffff8121513c50 : 0xffffff800c1ade13
0xffffff8121513cc0 : 0xffffff7f8f255b30
0xffffff8121513e20 : 0xffffff800c85e0b7
0xffffff8121513e90 : 0xffffff800c85dfd9
0xffffff8121513ec0 : 0xffffff800c1ed7e5
0xffffff8121513f40 : 0xffffff800c1ed385
0xffffff8121513fa0 : 0xffffff800c15b0ce
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[3AF948C3-2311-35BD-9306-358C1CCFD640]@0xffffff7f8f248000->0xffffff7f8f287fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[8685578D-AF6F-30FA-958F-EA00962E781D]@0xffffff7f8d07f000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[2328355E-F574-3D2A-A77D-A69917B3ED1D]@0xffffff7f8ca95000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[4BF8F99B-6849-3D1A-8F8E-AE2121324A76]@0xffffff7f8db5b000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[2F8C020B-036E-3646-A2CC-21BACD7D89C8]@0xffffff7f8d23f000
            dependency: com.apple.iokit.IOReportFamily(47)[E207FA21-52E9-3522-BE93-5906BB16CD00]@0xffffff7f8d0a0000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18G7016

Kernel version:
Darwin Kernel Version 18.7.0: Tue Nov 10 00:07:31 PST 2020; root:xnu-4903.278.51~1/RELEASE_X86_64
Kernel UUID: 0F94ABBC-EB06-3DEE-A01B-6F82102C1848
Kernel slide:     0x000000000be00000
Kernel text base: 0xffffff800c000000
__HIB  text base: 0xffffff800bf00000
System model name: MacBookAir7,2 (Mac-937CB26E2E02BB01)

System uptime in nanoseconds: 135224141476071
last loaded kext at 127283103953423: com.apple.driver.AppleXsanScheme    3 (addr 0xffffff7f8fb15000, size 32768)
last unloaded kext at 78318181737760: com.apple.filesystems.msdosfs    1.10 (addr 0xffffff7f8fa7a000, size 61440)
loaded kexts:
com.ZLab.SsdPmEnabler    0.1.1
org.virtualbox.kext.VBoxNetAdp    5.2.32
org.virtualbox.kext.VBoxNetFlt    5.2.32
org.virtualbox.kext.VBoxUSB    5.2.32
org.virtualbox.kext.VBoxDrv    5.2.32
com.paragon-software.filesystems.ntfs    71.5.15
com.Cycling74.driver.Soundflower    2
com.displaylink.driver.DisplayLinkDriver    5.2 (15)
org.acidanthera.NVMeFix    1.0.5
as.vit9696.Lilu    1.5.1
com.apple.filesystems.msdosfs    1.10
com.apple.filesystems.smbfs    3.3.2
com.apple.fileutil    20.036.15
com.apple.filesystems.ntfs    3.13
com.apple.filesystems.autofs    3.0
com.apple.driver.AGPM    110.25.11
com.apple.driver.ApplePlatformEnabler    2.7.0d0
com.apple.driver.X86PlatformShim    1.0.0
com.apple.driver.AppleHDA    282.54
com.apple.driver.AudioAUUC    1.70
com.apple.driver.AppleGraphicsDevicePolicy    3.50.16
com.apple.AGDCPluginDisplayMetrics    3.50.16
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.iokit.IOBluetoothSerialManager    6.0.14d12
com.apple.driver.pmtelemetry    1
com.apple.driver.AppleHV    1
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleIntelBDWGraphics    12.1.0
com.apple.driver.AppleBacklight    170.12.12
com.apple.driver.eficheck    1
com.apple.driver.AppleSMCLMU    212
com.apple.driver.AppleUpstreamUserClient    3.6.5
com.apple.driver.AppleLPC    3.1
com.apple.driver.AppleOSXWatchdog    1
com.apple.driver.AppleCameraInterface    6.8.0
com.apple.driver.AppleIntelSlowAdaptiveClocking    4.0.0
com.apple.driver.AppleThunderboltIP    3.1.2
com.apple.driver.AppleIntelBDWGraphicsFramebuffer    12.1.0
com.apple.driver.AppleMCCSControl    1.5.9
com.apple.driver.AppleUSBCardReader    456.260.3
com.apple.driver.AppleTopCaseHIDEventDriver    138.4
com.apple.BootCache    40
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.driver.AppleVirtIO    2.1.3
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0
com.apple.AppleSystemPolicy    1.0
com.apple.filesystems.hfs.kext    407.200.4
com.apple.filesystems.apfs    945.275.9
com.apple.driver.AirPort.BrcmNIC    1400.1.1
com.apple.private.KextAudit    1.0
com.apple.driver.AppleSmartBatteryManager    161.0.0
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleACPIEC    6.1
com.apple.driver.AppleAPIC    1.7
com.apple.security.TMSafetyNet    8
com.apple.nke.applicationfirewall    202
com.apple.driver.AppleXsanScheme    3
com.apple.driver.AppleUSBAudio    315.6
com.apple.driver.usb.IOUSBHostHIDDevice    1.2
com.apple.driver.usb.cdc    5.0.0
com.apple.driver.usb.ethernet.asix    5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice    1.2
com.apple.iokit.IOUSBUserClient    900.4.2
com.apple.kext.triggers    1.0
com.apple.driver.DspFuncLib    282.54
com.apple.kext.OSvKernDSPLib    528
com.apple.driver.AppleGraphicsControl    3.50.16
com.apple.iokit.IOAVBFamily    760.6
com.apple.plugin.IOgPTPPlugin    740.2
com.apple.iokit.IOEthernetAVBController    1.1.0
com.apple.iokit.IOSkywalkFamily    1
com.apple.driver.AppleSSE    1.0
com.apple.driver.AppleBacklightExpert    1.1.0
com.apple.iokit.IONDRVSupport    530.51
com.apple.driver.AppleHDAController    282.54
com.apple.iokit.IOHDAFamily    282.54
com.apple.driver.X86PlatformPlugin    1.0.0
com.apple.driver.IOPlatformPluginFamily    6.0.0d8
com.apple.AppleGPUWrangler    3.50.16
com.apple.iokit.IOSlowAdaptiveClockingFamily    1.0.0
com.apple.AppleGraphicsDeviceControl    3.50.16
com.apple.iokit.IOAcceleratorFamily2    404.14
com.apple.iokit.IOSurface    255.6.1
com.apple.driver.AppleSMBusController    1.0.18d1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport    6.0.14d12
com.apple.iokit.IOBluetoothHostControllerUSBTransport    6.0.14d12
com.apple.iokit.IOBluetoothHostControllerTransport    6.0.14d12
com.apple.driver.usb.AppleUSBHub    1.2
com.apple.iokit.IOAudioFamily    206.5
com.apple.vecLib.kext    1.2.0
com.apple.driver.usb.networking    5.0.0
com.apple.driver.AppleHSBluetoothDriver    138.4
com.apple.driver.IOBluetoothHIDDriver    6.0.14d12
com.apple.iokit.IOBluetoothFamily    6.0.14d12
com.apple.driver.AppleMultitouchDriver    2450.1
com.apple.driver.AppleInputDeviceSupport    2440.4
com.apple.driver.AppleHIDKeyboard    208
com.apple.iokit.IOSerialFamily    11
com.apple.filesystems.hfs.encodings.kext    1
com.apple.driver.AppleHSSPIHIDDriver    55.2
com.apple.iokit.IONVMeFamily    2.1.0
com.apple.driver.AppleThunderboltDPInAdapter    5.6.9
com.apple.driver.AppleThunderboltDPAdapterFamily    5.6.9
com.apple.driver.AppleThunderboltPCIDownAdapter    2.1.5
com.apple.driver.AppleThunderboltNHI    4.7.9
com.apple.iokit.IOThunderboltFamily    6.8.7
com.apple.iokit.IO80211Family    1200.12.2
com.apple.driver.mDNSOffloadUserClient    1.0.1b8
com.apple.driver.corecapture    1.0.4
com.apple.driver.AppleHSSPISupport    55.2
com.apple.driver.usb.AppleUSBHostPacketFilter    1.0
com.apple.driver.AppleIntelLpssSpiController    3.0.60
com.apple.iokit.IOUSBFamily    900.4.2
com.apple.driver.AppleIntelLpssDmac    3.0.60
com.apple.driver.AppleIntelLpssGspi    3.0.60
com.apple.driver.AppleUSBHostMergeProperties    1.2
com.apple.driver.usb.AppleUSBXHCIPCI    1.2
com.apple.driver.usb.AppleUSBXHCI    1.2
com.apple.driver.AppleEFINVRAM    2.1
com.apple.driver.AppleEFIRuntime    2.1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.security.quarantine    3
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleEffaceableStorage    1.0
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleUSBTDM    456.260.3
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.iokit.IOUSBMassStorageDriver    145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice    408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily    408.250.3
com.apple.kext.CoreTrust    1
com.apple.driver.DiskImages    493.0.0
com.apple.iokit.IOStorageFamily    2.1
com.apple.iokit.IOTimeSyncFamily    740.2
com.apple.iokit.IONetworkingFamily    3.4
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.KernelRelayHost    1
com.apple.iokit.IOUSBHostFamily    1.2
com.apple.driver.usb.AppleUSBCommon    1.0
com.apple.driver.AppleBusPowerController    1.0
com.apple.driver.AppleSEPManager    1.0.1
com.apple.driver.IOSlaveProcessor    1
com.apple.iokit.IOReportFamily    47
com.apple.iokit.IOGraphicsFamily    530.68
com.apple.driver.AppleACPIPlatform    6.1
com.apple.driver.AppleSMC    3.1.9
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.pthread    1
com.apple.kec.corecrypto    1.0
com.apple.kec.Libm    1

EOF

System Profile:
Network Service: Apple USB Ethernet Adapter, Ethernet, en3
Network Service: Wi-Fi, AirPort, en0
Boot Volume File System Type: apfs
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A544D4C41522D4E544D
USB Device: USB 3.0 Bus
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple USB Ethernet Adapter
Thunderbolt Bus: MacBook Air, Apple Inc., 27.2
Model: MacBookAir7,2, BootROM 425.0.0.0.0, 2 processors, Intel Core i5, 1.6 GHz, 8 GB, SMC 2.27f2
Graphics: kHW_IntelHDGraphics6000Item, Intel HD Graphics 6000, spdisplays_builtin
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.11)
Bluetooth: Version 6.0.14d12, 3 services, 27 devices, 1 incoming serial ports

I think crashes in Apple's NVMe driver could be caused by many reasons but all people will see is the very similar panic log that you've pulled together from different sources.

Since MacBookAir7,2 is proven to be okay by other folks, if the problem persists, I would check mechanical/electrical contacts in the SSD/adaptor/SSD socket.

Thanks for the advice! Yes I agree, the logs look very similar and could be caused by anything. The line numbers could very well just be a generic error/panic trap. Without drawing a correlation though the high number of crashes with similar arguments (CSTS=0xffffffff US[1]=0x0 US[0]=0x46) is surprising, though.

I will install the latest update (2021-002) and clean the contacts on the motherboard, the sintech (both in/out sides!), and the Rocket SDD with isopropyl.

Very likely you need to put back the original Apple SSD to succeed in the BootROM update.

Just FYI, I have recived BootROM updates without updating to BigSur. Just looking at my kernel panic logs:

Fri Dec 25 11:18:59 2020
...
Model: MacBookAir7,2, BootROM 195.0.0.0.0, 2 processors, Intel Core i5, 1.6 GHz, 8 GB, SMC 2.27f2

But see above, and today my ROM is:

Model: MacBookAir7,2, BootROM 425.0.0.0.0, 2 processors, Intel Core i5, 1.6 GHz, 8 GB, SMC 2.27f2

How might I have got these updates, without any update to macOS Big Sur? (older ROMs shown in my older panic logs)

 

[AstroZero]

How might I have got these updates, without any update to macOS Big Sur? (older ROMs shown in my older panic logs)

Also just to add, I have installed 2021-02 update and my bootrom is now Boot ROM Version: 426.0.0.0.0

No OS install required. The update took a few minutes and required a reboot.

 

[Michaela_]

So, update number 2 (original poste here: https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29635732). I honestly have no idea what went wrong or how to proceed further. Everything I put into my MPBr 13" mid-2014, which is not the original drive, is not recognized by the computer. Firstly I thought it was a faulty adapter (since it has worked for a while), then I thought it's the NVMe drive. I've got another adapter, I've checked the NVMe drive on my desktop, I've tried a completely different NVMe drive, it still does not work. I'm honestly desperate because I can't think of any other option here or thing to try. The strangest thing about this whole issue is during the original attempt to swap the drive, I seemingly succeeded. NVMe was recognized, the system was installed, backup restored, I successfully booted into the system, did some tests, and whatnot. At this point, I felt confident enough to screw in all the screws of the bottom lid (I did only 3 or 4 of them because there was a possibility that I would need to reopen the lid). I turned off the computer, tightened all the screws, turned the computer on, and since then the only thing I get is the question mark folder screen. Is there by any chance anyone who had/has such an issue?

Sys info:

I'd be very thankful for any advice.
Thanks.

P.S. Yes, I've tried PRAM/NVRAM resets, Kapton taping almost everything, screwing the NVMe in tight/loose, fiddling around with the angles...

 

[AstroZero]

So, update number 2 (original poste here: https://forums.macrumors.com/thread...ook-pro-ssd-to-m-2-nvme.2034976/post-29635732). I honestly have no idea what went wrong or how to proceed further. Everything I put into my MPBr 13" mid-2014, which is not the original drive, is not recognized by the computer. Firstly I thought it was a faulty adapter (since it has worked for a while), then I thought it's the NVMe drive. I've got another adapter, I've checked the NVMe drive on my desktop, I've tried a completely different NVMe drive, it still does not work. I'm honestly desperate because I can't think of any other option here or thing to try. The strangest thing about this whole issue is during the original attempt to swap the drive, I seemingly succeeded. NVMe was recognized, the system was installed, backup restored, I successfully booted into the system, did some tests, and whatnot. At this point, I felt confident enough to screw in all the screws of the bottom lid (I did only 3 or 4 of them because there was a possibility that I would need to reopen the lid). I turned off the computer, tightened all the screws, turned the computer on, and since then the only thing I get is the question mark folder screen. Is there by any chance anyone who had/has such an issue?

Sys info:
View attachment 1738444

I'd be very thankful for any advice.
Thanks.

P.S. Yes, I've tried PRAM/NVRAM resets, Kapton taping almost everything, screwing the NVMe in tight/loose, fiddling around with the angles...

This is a bit worrying! Sorry to hear it's not working, glad you have have backed up data (from your old post).

Did the NVMe drive work/get recognised in the desktop? (what machine/OS is the desktop?)

In your OP it says the adapter was faulty. Did you now get a second (third?) Sintec adapter?

Also, what version of macOS are you running?

 

[Michaela_]

This is a bit worrying! Sorry to hear it's not working, glad you have have backed up data (from your old post).

Did the NVMe drive work/get recognised in the desktop? (what machine/OS is the desktop?)

In your OP it says the adapter was faulty. Did you now get a second (third?) Sintec adapter?

Also, what version of macOS are you running?

Hi. Thanks for a quick reaction. It's hella worrying!

The NVMe got recognized by Linux (Ubuntu) without any issue. Plugged into the motherboard via M.2 port.

Yes, I said it was faulty but now I'm not really sure it was the adapter. It was (at the time) the easiest possible explanation, but since I've tried another new adapter, I'm starting to doubt it because what are the odds I've got two faulty adapters from two different resellers in a row... Yes, they both are Sintech short adapters.

I'm running the latest Mojave, 10.14.6. Updated to the latest security patch right before I did the first try.

I honestly have 0 ideas about what went wrong.

Thanks.

 

[AstroZero]

I usually get a kernel panic error once a week. I will share the report with you when I get the next kernel panic error.

I use Big Sur. I'll be installing Catalina next week. I will let you know if there is a change.

BTW

/Library/Logs/DiagnosticReports contains crash logs for the last month or so. Check that folder for .panic files, post here if you find any

recommend using pastebin to sharing the kernel panic.

 

[kvic]

So you'd recommend going with the latest install of Big Sur?
After installing both ssdpmEnabler & NVMeFix (+Lilu), are there any extra steps needed, if I choose to update the next to version of Big Sur in the future? Should they be uninstalled?

I believe OS versions (Mojave/Catalina/BigSur) do not matter much in terms of supporting 3rd-party NVMe SSDs.

3rd-party kexts installed inside /Library/Extensions will be carried forward automatically in minor & major OS updates/upgrades. You don't have to uninstall/reinstall. At least no such requirement for ssdpmEnabler.

Just FYI, I have recived BootROM updates without updating to BigSur.

Apple ships BootRom updates in their supported OS versions, currently Mojave, Catalina and Big Sur.

At this point, I felt confident enough to screw in all the screws of the bottom lid (I did only 3 or 4 of them because there was a possibility that I would need to reopen the lid). I turned off the computer, tightened all the screws, turned the computer on, and since then the only thing I get is the question mark folder screen.

I believed @AstroZero, @Baptiste261 and you all run into some sort of poor mechanical/electrical contacts. If you inspect closely and review your installation carefully, you might be able to spot the culprit.

Otherwise, I would simply try a _long_ adaptor which provides mechanically more rigid structure. Hence, provides better electrical contact as a result.

 

[AstroZero]

Apple ships BootRom updates in their supported OS versions, currently Mojave, Catalina and Big Sur.

Thanks!!

I did not have to install my Apple SSD to get the Big Sur BootROM update. I am still on Mojave.

FYI, more confirmation that macs with aftermarket SSDs can get BootROM update without the original Apple SSD:

An interesting aside about firmware and Big Sur is that now, after installing Big Sur on my Macbook Pro 12,1 on a non-original internal SSD, the firmware updated properly as well. Previous OS updates have not updated the firmware unless I reinstalled my original SSD as stated in a previous post here on your site.

from:

Which firmware should your Mac be using? (version 5)

This article lists the firmware versions of Macs which have been successfully updated to run macOS 11.7.10. Apple doesn’t provide an official list of the current firmware versions which shoul…

eclecticlight.co

(I posted this message yesterday, mods have not approved my message because of links so posting without the link)

 

[AstroZero]

Michaela_ said:
The NVMe got recognized by Linux (Ubuntu) without any issue. Plugged into the motherboard via M.2 port.

That is good news, shows that the SSD is still working and that your data should still be intact.

It may be worth trying your nvme SSD in a different MacBook. Are you able to access to another MacBook 2013-2017? I could try your drive/adapter in my Macbook Air 2015 as you are UK based, drop me a PM.

Michaela_ said:
Yes, I said it was faulty but now I'm not really sure it was the adapter. It was (at the time) the easiest possible explanation, but since I've tried another new adapter, I'm starting to doubt it because what are the odds I've got two faulty adapters from two different resellers in a row... Yes, they both are Sintech short adapters.

True, it is quite possible that both your adapters were working all along.

You mention kapton tape but that might leave residue. kapton should not be installed by us, it was just a way to distinguish old vs new sintech adapters - old adapters had kapton from factory.

I would suggest cleaning the contacts on the nvme drive and the adapters with 100% isopropyl, and a cotton bud. I just cleaned my drive/sintech/motherboard connectors. My cleaning process was:

1) (unplug the battery), remove the SSD and sintech
2) put plenty of 100% isopropyl on the flat contacts of the SSD and the sintech
3) rub clean the flat contacts with a cotton bud
4) with isopropyl on the flat contacts, plug and unplug the SSD into the sintech adapter and the sintech adapter into the motherboard. repeat a few times. The pins inside the adapter and on the motherboard are hard to clean otherwise.
5) wait for the isopropyl to dry fully before reinstalling the SSD/adapter/battery.

Repeat 2) - 4) a couple of times- be careful to not touch the contacts with bare hands and wear rubber gloves if possible. [I wonder if I touched the SSD/sintech contacts when I did the original install and that's been causing my kernel panic issues...].

Michaela_ said:
I'm running the latest Mojave, 10.14.6. Updated to the latest security patch right before I did the first try.

This is very interesting. I saw the screenshot was Mojave after I hit send . Did you reinstall the original apple SSD drive to apply the security updates? Have you ever updated to Big Sur with the orig SSD?

You have the latest bootrom for MacBookPro11,1 which is 430.0.0.0. From the comments on the link [1], Apple are definitely sending bootrom as part of security updates. In my case the ROM updates are being applied even with a non Apple SSD drive installed.

Some completely unconfirmed conjecture: the new BootROM version may be the reason your machine is no longer recognising the drive. This is very worrying if true, as any update may stop other drives from working. It would be worth confirming 100%.

BTW I can't tell from your posts, what is your nvme drive / manufacturer? I'm running a 1TB sabrent rocket for ~2 years on Mojave, with a few random kernel panics.

(I posted this message yesterday, mods have not approved my message because of links so posting without the link)

[1] https://eclecticlight.co/2020/11/16/which-firmware-should-your-mac-be-using-version-5/#comment-53151

 

[kvic]

Gosh

Another smartace in the room

I'll be away for a while. Take care everyone

 

[AstroZero]

I believed @AstroZero, @Baptiste261 and you all run into some sort of poor mechanical/electrical contacts. If you inspect closely and review your installation carefully, you might be able to spot the culprit.

Otherwise, I would simply try a _long_ adaptor which provides mechanically more rigid structure. Hence, provides better electrical contact as a result.

Thanks could very well be- i noticed the drive was a little skewed (by <1mm, hardly noticable, see pic) so after cleaning I reseated it as centered on the screw as i could.

picture of skewing:

Let's see how long it lasts this time.