Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
----------------------------
Thanks for replying.

Is there a way to know if indexing is happening?

Note:I migrated the contents of my drive from a Time Machine backup from a different Mac.

RE: Q vs non Q
Wow, that's strange that 303.3 is Rocket Q...i ordered this from Amazon and it's not supposed to be the QLC version! The item from Amazon says:
Sabrent 1TB ROCKET NVMe PCIe M.2 2280 Internal SSD High Performance Solid State Drive (SB-ROCKET-1TB)
ASIN: B07LGF54XR

The item I received looks like the one pictured on Amazon and not the labelled Q version below on Amazon is: Sabrent Rocket Q 1TB NVMe PCIe M.2 2280 Internal SSD High Performance Solid State Drive R/W 3200/2000MB/s (SB-RKTQ-1TB)

I'm really confused if the item I have is a Q. Any ideas?

For indexing, just check spotlight to see if it's still working (CMD+Space) and typing a few letters usually shows a progress bar "indexing" if it's still working.

If you do have a drive with QLC - then normally waiting 30 minutes or so (system on but idle, with minimal disk activity) for the drive to flush it's caches will let the speed recover.

You could also use Black Magic Disk Speed Test, set it to 5gb and let it run on a loop for a long period of time... you will see the performance slowly drop if your drive is QLC.

I just did a quick search on RKT303.3 - and the first results were related to Rocket Q, I don't have this drive personally but I found these posts that go into differences: https://www.reddit.com/r/NewMaxx/comments/drriga/sabrent_rocket_hardware_change/, maybe they will help you?
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
I just put the adapter and ssd in, did a complete fresh install and no issues whatsoever on a late 2013 MBP. No overheating, no hibernation issues, nothing..I am beyond thrilled at how easy it was. Didn't even have to do anything with Trim, it's all enabled!

Sooooo, still no issues even with hibernation? Finally my Sintech adaptor arrived and I want to try so bad with my MBP Retina Late 2013 to upgrade my ssd but still have some fear.
I will be choosing in case the "Sabrent SSD 512GB Rocket NVMe PCIe M.2 2280 Drive (SB-ROCKET-512)", is it good?
 
Sooooo, still no issues even with hibernation? Finally my Sintech adaptor arrived and I want to try so bad with my MBP Retina Late 2013 to upgrade my ssd but still have some fear.
I will be choosing in case the "Sabrent SSD 512GB Rocket NVMe PCIe M.2 2280 Drive (SB-ROCKET-512)", is it good?

Still no issues and power/temps have been good too. I went with the 1T in my 15" and 512 in my 13". Both have been no problem upgrades.
 
I have a MBP 13" Mid 2014 model 11,1, boot room version 162.0.0.0. I changed my native 120GB SSD to a Sandisk Ultra 500GB 3D NVME with an adaptor that I don't know its brand (it's not a Sintech) on Friday and so far so good. I was afraid of changing it because I'm a noob, so I saved the solutions I've read in this thread to use them just in case. Thankfully nothing weird happened.

Today I installed the bootcamp for the first time (I didn't have it on the other SSD) and everything went well. The battery consumption seems fine and the SSD temperature is 41ºC now on Macs Fan Control (I don't have iStats installed). You can see the before and after speeds below. Thank you all! All the posts helped me to be aware of everything I needed. I'll come back later to tell you how everything is going.
 

Attachments

  • DiskSpeedTest.png
    DiskSpeedTest.png
    225.3 KB · Views: 168
  • DiskSpeedTest 2.png
    DiskSpeedTest 2.png
    224.9 KB · Views: 161
  • Like
Reactions: Audit13
Hello there,
I have upgraded two years ago and I never stopped having problems.
Wake problems, than battery gone, now lately I have the following :
mac wakes up at night boots twice waking us up at 5 o'clock in the morning, then the battery life seems never to last as it should. Complete disaster. I have changed the sudo instructions according to the latest recommendations of this thread but it does not work. I attach the latest crash report for discussion
Many thanks to everyone for your help and attention
Andrea
 

Attachments

  • crash.zip
    2.2 KB · Views: 89
I have 2015 MBPr 13" as well, with Intel 660p and Sabrent Adapters - actually I tried 3, green and black Sabrent and 1 RIVO from Amazon.

Some things I tried that helped...

Changing standbydelay to 1hr when above 50% and 30 mins when below 50%. You don't need to use hibernatemode=25, the default of "3" for our device works fine.

sudo pmset -b standbydelaylow 3600
sudo pmset -b standbydelaylow 1800

Installing NVMeFix to forcibly enable APST (Not 100% sure if it helps with my drive - but idle temperatures for the SSD go from 42-46C to 35-37C).

I will get 5-7hrs on battery depending on brightness and what I am doing, and adjusting standbydelay means 2-5% drain overnight.

is NVMEfix working for you? I tried it but APST was still disabled.
 
is NVMEfix working for you? I tried it but APST was still disabled.

Yes it is! The github page is a bit confusing, once you turn on the debug flag ("-nvmefdbg") ... you can enter this command in terminal:

log show --style syslog --last boot --predicate "process == \"kernel\" and eventMessage CONTAINS[c] \"nvme\"" --info --debug

Which will give you some data like this: (APST Status 1 means it's enabled)
2020-08-15 21:57:49.071346-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) APST status 0
2020-08-15 21:57:49.071350-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) Configuring APST
2020-08-15 21:57:49.071398-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) APST enabled: max PS = 4, max round-trip latency = 14000us
2020-08-15 21:57:49.112014-0700 localhost kernel[0]: (Lilu) NVMeFix apst: @ (DBG) APST status 1
2020-08-15 21:57:49.132407-0700 localhost kernel[0]: (Lilu) NVMeFix pm: @ (DBG) Registering power change interest
2020-08-15 23:38:23.664936-0700 localhost kernel[0]: (Lilu) NVMeFix pm: @ (DBG) powerStateDidChangeTo 0x0
2020-08-15 23:38:23.664941-0700 localhost kernel[0]: (Lilu) NVMeFix pm: @ (DBG) Ignoring transition to non-usable state 0x0
2020-08-15 23:48:11.940420-0700 localhost kernel[0]: (Lilu) NVMeFix pm: @ (DBG) powerStateDidChangeTo 0x2
 
well well well...today Sabrent Rocket 512GB cost only 64€ sooooo I think I will buy it and test on my MacBook Pro :)
 
  • Like
Reactions: pdxplm
Hello there,
I have upgraded two years ago and I never stopped having problems.
Wake problems, than battery gone, now lately I have the following :
mac wakes up at night boots twice waking us up at 5 o'clock in the morning, then the battery life seems never to last as it should. Complete disaster. I have changed the sudo instructions according to the latest recommendations of this thread but it does not work. I attach the latest crash report for discussion
Many thanks to everyone for your help and attention
Andrea
Your MacBook is a late 2013 13".

You will need to shut down the MacBook each night. The MacBook 11,1 does not support safe sleep with a a NVMe drive.
 
  • Like
Reactions: andrearicci
What's the best NVMe for the upgrade? I'm debating between the Samsung Evo 970 and the Adata XPG SX8200 Pro
Anyone has any suggestions
 
Unless you are reading and writing a lot of large files, a QLC drive should be fine in a 2014 Air.

I have used an Intel 660p and 600p in 13" Airs and they were both faster than the stock drives they replaced.

Yes, they are slower than some TLC drives but they have pretty low power draw as well. The people for whom I upgraded were very pleased with the results.
 
Success again! But first of all, thanks to gilles_polysoft and dosdude1 for discovering and sharing this upgrade possibility! Great work. For my rMBP 2013 13" (A1502) I replaced my Apple SSD about 2 weeks ago with a ADATA SX8200 PRO 1TB and disabled (deep)sleep. Ran fine, battery drain was not bad. Still, I was interested in taking it up a notch. I followed Inge83 and his hints (thanks!) and installed a Mattcard with a patched Bootrom - which contains the NVMe drivers of the 2015 Macbook Pro. It is the safest way to get that result, as the Matt card can be removed again if faulty.
I patched the Bootrom myself using the ROM tool of dosdude1 and UEFItool (do not use the A54 version, use 0.26.0). Then I asked cmizapper.nl if he would flash this file on the matt card before sending it out, which he agreed to do (thanks!). Today I installed it, takes only 3 minutes. Restored the defaults of energy management (hibernate 3 and so on) - no sleep issues so far. I will write a short guide on how to patch the bootrom later. For noobs, here is my summary of upgrading options.
Upgrading 2013/2014 Macbook Pro SSD to M.2 NVMe Summary
[doublepost=1548093258][/doublepost]Guide for getting a patched bootrom:
Use Rom Tool ( ROMTool.zip password rom) and dump your ROM to a file. My chip could not be clearly identified by Rom Tool, I simply chose the suggested one. Get OS X Update 10.14.1 to extract the latest Bootrom and its NVMe driver from the Macbook Pro 2015 (Macbook 12,1) - 10.14.2 does not contain a Firmware update, so use 10.14.1. Your current Bootrom must match the version number of the Firmware update!

Use Unarchiver and/or Finder's Show Package Contents, until you get the MBP121.fd file. Open it in UEFItool. I got 2 parseVolume messages - ignore. Search "Text" "not unicode" "case sensitive" for "NVMe", double-click on the "ASCII text "NVME" found". Save the entire branch (51116915-....) by right-click and "extract as is". Close this MBP121.fd file, open your Rom dump from above. Ignore the 2 parseVolume messages about unknown file system. Now you need to insert the saved branch there. Look for "NVMe" again (using options as above), then replace the entire branch (51116915-...) using "replace as is". The result is your patched Bootrom.

Be aware of the following:
This Bootrom file contains your serial number - and maybe also your EFI-password (at least not in plain characters). Understand that before you send it to a third party.
Alternatively, you can flash it yourself - not with Rom Tool, this does not work (signature missing). You could use a SOIC8 clip and a Raspberry Pi to flash the chip on the Matt Card.

Thank you for the detailed summary. I am going to purchase the Sabrent rocket SSD for my 2014 MBP retina as well as a mattcard for eliminating the hibernation/sleep issues. Based on the hibernation/sleep issues that are plaguing users throughout this thread, is it possible to create a bootrom to send to cmizapper.nl for flashing prior to installation / migration to new SSD or does the bootrom need to contain detail from the newly installed SSD? I am trying to make this migration as smooth as possible without running into issues and hoping to complete both at the same time.
 
Took mine about 1-2 weeks to Canada with a tracking number.

I bought two adapters from Sintech. The first one, around 8 months ago. It took 2 weeks to arrive in Toronto.

Last April, I bought another short adapter (same Amazon link) + one 1TB Silicon Power NVMe drive. Believe it or not, they arrived 3 days later in the same Amazon package.
 
Hy guys. Here I am again. I'm live testing my new Sabrent 512GB on my "old" MBP Retina 15 Late 2013. Disk wasn't recognize at first with a High Sierra usb install disk. I create a Catalina one and all went good.
I installed a fresh copy of the OS and this is my benchmarks values, what do you think?


These are my old benchmarks values with the Apple SSD:


Thanks
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.