MP 1,1-5,1 MacPro 5,1 NVMe - Can't Boot Into Recovery Mode

sfalatko

macrumors newbie
Original poster
Sep 24, 2016
14
3
I have a 2010 Mac Pro 5,1 with 144.0.0.0.0 firmware running macOS Mojave 10.14.5 booting from a Samsung 970 Pro formatted as APFS. No matter how I try I can't boot into recovery mode - either using Command+R or booting with the Option key (I don't see the recovery partition as a boot option)

Can anyone provide any troubleshooting tips or advice?
 

tsialex

macrumors 603
Jun 13, 2016
5,385
6,100
Brazil
I have a 2010 Mac Pro 5,1 with 144.0.0.0.0 firmware running macOS Mojave 10.14.5 booting from a Samsung 970 Pro formatted as APFS. No matter how I try I can't boot into recovery mode - either using Command+R or booting with the Option key (I don't see the recovery partition as a boot option)

Can anyone provide any troubleshooting tips or advice?
I have your exactly config and no problems booting Recovery. Did you cloned your install?

Btw, Recovery don’t show in the BootPicker/BootSelector for years, Apple removed it from there, you just use Command-R to access it.
 

sfalatko

macrumors newbie
Original poster
Sep 24, 2016
14
3
I have your exactly config and no problems booting Recovery. Did you cloned your install?

Btw, Recovery don’t show in the BootPicker/BootSelector for years, Apple removed it from there, you just use Command-R to access it.
Yes, I cloned the install. The recovery partition shows with a diskutil list in terminal. Also ran the lated recovery partition updater.

Any thoughts?
 

tsialex

macrumors 603
Jun 13, 2016
5,385
6,100
Brazil
Yes, I cloned the install. The recovery partition shows with a diskutil list in terminal. Also ran the lated recovery partition updater.

Any thoughts?
Fully erase your PCIe drive and do a clean install to test if it works correctly, then you diagnose your cloned install.

Use gpt destroy command to fully erase your NVMe blade, change diskXX for the appropriate diskID:

Code:
diskutil list
diskutil unmountdisk diskXX
sudo gpt destroy diskXX
 

sfalatko

macrumors newbie
Original poster
Sep 24, 2016
14
3
Fully erase your PCIe drive and do a clean install to test if it works correctly, then you diagnose your cloned install.

Use gpt destroy command to fully erase your NVMe blade, change diskXX for the appropriate diskID:

Code:
diskutil list
diskutil unmountdisk diskXX
sudo gpt destroy diskXX
OK, after I test if it works (and find that it does) can I then use Migration Assistant or SuperDuper to move my data and apps to the newly installed Mohave?
 

tsialex

macrumors 603
Jun 13, 2016
5,385
6,100
Brazil
OK, after I test if it works (and find that it does) can I then use Migration Assistant or SuperDuper to move my data and apps to the newly installed Mohave?
Migration Assistant or manually, SuperDuper clones your drive.
 

sfalatko

macrumors newbie
Original poster
Sep 24, 2016
14
3
Migration Assistant or manually, SuperDuper clones your drive.
tsialex,

Thanks for all the help. As an experiment before I wiped the drive and did a clean install I tried an install using the full installer over my current install. That actually worked and I can now boot into the recovery partition on my NVMe blade.
 
  • Like
Reactions: tsialex