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.
This don't exist at all, only SATA M.2 to plain SATA.

BTW, SFF8639 adapters work because the U2 SAS cable also has the PCIe signals.
Maybe a miscommunication or false terminology
 

Attachments

  • shopping.jpeg
    shopping.jpeg
    34 KB · Views: 135
This is for a B-key (SATA) M.2 blade. You can't even insert a M-key (PCIe AHCI/NVMe) blade.
It says for both actually in the product description, but if not this card then another. Point being they exist. But I have since learned that that's not a solution either, regardless. It's just a bit misleading when everyone's talking about Nvme's when it could be any hard drive - the issue persists regardless.
 
It says for both actually in the product description, but if not this card then another. Point being they exist. But I have since learned that that's not a solution either, regardless. It's just a bit misleading when everyone's talking about Nvme's when it could be any hard drive - the issue persists regardless.
Sorry, but they don't. How do you convert PCIe signals from the M.2 blade to the Mac Pro SATA interface?!?

M.2 is a format, this format have two main standards, M-key and B-key. M-key blades require a M.2 PCIe interface, B-key blades require a SATA M.2 interface. You can't use a B-key adapter with a M-key blade, they don't even connect.

You can only use a format adaptor to connect a B-key M.2 blade to the Mac Pro SATA ports.
 
Last edited:
Hi. Does anyone know if with the launch of BS 11.4, is it now safe to update the Mac Pro 5,1 to 11.4 or should we stay on BS 11.2.3 for now?

greetz,
Willem
 
Hi. Does anyone know if with the launch of BS 11.4, is it now safe to update the Mac Pro 5,1 to 11.4 or should we stay on BS 11.2.3 for now?

greetz,
Willem
Nope, 11.2.3 is still the most recent MP5,1 compatible Big Sur release.

Read the first post here:

 
Sorry, but they don't. How do you convert PCIe signals from the M.2 blade to the Mac Pro SATA interface?!?

M.2 is a format, this format have two main standards, M-key and B-key. M-key blades require a M.2 PCIe interface, B-key blades require a SATA M.2 interface. You can't use a B-key adapter with a M-key blade, they don't even connect.

You can only use a format adaptor to connect a B-key M.2 blade to the Mac Pro SATA ports.
So what about 2.5" SATA SSDs? But like I said according to my research, it doesn't seem to make a difference, either.
 
So what about 2.5" SATA SSDs? But like I said according to my research, it doesn't seem to make a difference, either.
Works fine up to 11.2.3, for details of the problem read the first post below:

 
Nope, 11.2.3 is still the most recent MP5,1 compatible Big Sur release.

Read the first post here:

Thanks ! I was following the "Big Sur on unsupported Macs" thread but since I have a MP5,1, I was pointed to this thread :)
 
Anyone has the Problem that USB3 Card (Sonnet USB3C-4PM-E) quits working after warm boot with OpenCore 0.6.9 (Martins package)?!

The card has an ASM3142 chipset...
 
Last edited:
Major update: I am running 11.4, it fixed my graphical glitches from the previous version but the boot procedure is amusing to say the least. Otherwise runs stable as can be.

Disclaimer: My PCIe config is anything but clean, light or OEM (Think DIY solder jobs)

It is probably best I attach my OpenCore config file, since I cannot yet pinpoint precise measurements to succeed with this. All I can say is I recently had a lot of struggle with getting Windows to run cleanly without refind or clover and so on, since I don't like them aesthetically. I had to learn to build Apple style EFI partitions manually and tinkered quite a bit with my open core config. Windows runs great now and the only downside is I have to reset NVRAM sometimes after an update on either end of the dual boot, to be able to boot again. That might have something to do with the update having worked now.

First of all I had 11.3 stuck at ~20% and the snapshot and update files laying around for a while now.
- NVRAM has been reset a few times during my windows fiasco. So probably start with a clean slate on that.
- Deleted all traces of the 11.3 update
- Downloaded 11.4r and let it restart (it attempted to download more updates but got interrupted by the update's own shutdown signal, which counted down in Notification Center… odd!)
- Apple Logo with progress bar, got stuck and it broke the circuit on its own (hard shut down)
- Restarted and picked the update partition
- Went half way or so then circuit break again
- Reset NVRAM, no boot procedure otherwise
- Started install partition again
- Got thru almost the entire way, then black screen, then progress bar again after a long while
- Very slow boot sequence
- Long period of black screen
- Login Screen, Success!

I wonder if my boot procedure will always be this wonky now, not that I care really.
Standby for years.

Hope this helps some of you in some way, shape or form, to solve the mystery.
 

Attachments

  • config.plist.txt
    21.6 KB · Views: 81
How do you convert PCIe signals from the M.2 blade to the Mac Pro SATA interface?!?

M.2 is a format, this format have two main standards, M-key and B-key. M-key blades require a M.2 PCIe interface, B-key blades require a SATA M.2 interface. You can't use a B-key adapter with a M-key blade, they don't even connect.

You can only use a format adaptor to connect a B-key M.2 blade to the Mac Pro SATA ports.
There exists USB to NVMe Bridge Chips (such as the JMicron JMS583). Some of the enclosures that can do this also support SATA devices using a USB to SATA bridge.

I suppose a SATA to NVMe bridge chip could be possible (well, anything in computing is possible with enough work) but I don't know of any.

I did find this NVMe to SATA Bridge:
https://www.intelliprop.com/ipp-nv186a-br/
But it connects SATA SSDs to a host's NVMe slot which is the opposite of what we want: to connect NVMe SSDs to a host's SATA slot.
 
I'm still on Mojave without opencore. So does this mean there is no way for me to upgrade to Big Sur and opencore?
This has being asked multiple times on the last page. No, you can't use any Big Sur release after 11.2.3 reliably with a MP5,1, including this week beta of 11.5.

Please read the first post of the thread below:

 
  • Like
Reactions: joebclash
***************
SOLVED
***************
It was my own mistake. WinClone 9 was not able to unmount the internal partition from that boot SSD and so it shows up that error. I boot up from an external SSD and all was fine restored.


Hello together,

I am looking for some advice. I'm running the OpenCore 0.6.9 Package from Martin Lo with macos Catalina 10.15.7 Build 19H1030. I also running Windows 10 Pro 64 Bit latest Updates as UEFI Install via OpenCore BootManager - all fine. Today I made a Image via WinClone 9 because I want to move Windows to the internal drive Samsung EVO 860 SSD 1 TB via OWC Accelsior S.

I made a 200 GB Partition in the backyard of the disk (see picture disk.jpg) as I had this structure before on the other disk. Now I try to restore the Windows Image from WinClone 9 to the disk and then I got an error which I did not expect because it shoud not be shown - but see for yourself:

SIP is disabled
SIP-Disabled.jpg


WinClone 9 Restore Error
WinClone-9.jpg

Disk Structure
Disk.jpg


Any hint is very welcome...
 
Last edited:
***************
SOLVED
***************
It was my own mistake. WinClone 9 was not able to unmount the internal partition from that boot SSD and so it shows up that error. I boot up from an external SSD and all was fine restored.


Hello together,

I am looking for some advice. I'm running the OpenCore 0.6.9 Package from Martin Lo with macos Catalina 10.15.7 Build 19H1030. I also running Windows 10 Pro 64 Bit latest Updates as UEFI Install via OpenCore BootManager - all fine. Today I made a Image via WinClone 9 because I want to move Windows to the internal drive Samsung EVO 860 SSD 1 TB via OWC Accelsior S.

I made a 200 GB Partition in the backyard of the disk (see picture disk.jpg) as I had this structure before on the other disk. Now I try to restore the Windows Image from WinClone 9 to the disk and then I got an error which I did not expect because it shoud not be shown - but see for yourself:

SIP is disabled
View attachment 1782600

WinClone 9 Restore Error
View attachment 1782601
Disk Structure
View attachment 1782602

Any hint is very welcome...
Use this setting for SIP:
Code:
<key>csr-active-config</key>
                <data>fwgAAA==</data>

Code:
nvram csr-active-config
csr-active-config    %7f%08%00%00
 
  • Like
Reactions: paalb
Works fine up to 11.2.3, for details of the problem read the first post below:

Alex will via Clone to NVMe for a boot drive work for 11.2.3
 
Alex will via Clone to NVMe for a boot drive work for 11.2.3
I didn't understood what you really asking above.

If you want to clone your 11.2.3 boot disk using an app that support BigSur cloning like the current version of CCC, yes. Don't matter if it's a NVMe/AHCI/SATA/USB.
 
I didn't understood what you really asking above.

If you want to clone your 11.2.3 boot disk using an app that support BigSur cloning like the current version of CCC, yes. Don't matter if it's a NVMe/AHCI/SATA/USB.
Or use Clonezilla.It´s able to clone everything. I use it in drives with a windows or Linux partitions.
 
  • Like
Reactions: TheStork
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.