with TG pro it is the easiest
but in your screenshot I do not see the NVMes
that's what it looks like to me:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP All Models PCIe SSDs - NVMe & AHCI
- Thread starter MisterAndrew
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
with TG pro it is the easiest
but in your screenshot I do not see the NVMes
that's what it looks like to me:
Hello!
So, after few days of tests i could say thank you very much @tsialex
I tested my kryo with WD black SN750 250GB and HP ex920 - it works as should be.
Also, sn550 works nice with PC, so it's only not good for mac os/ or cMP
Anybody with permissions may add to 1st post - WD BLACK SN750 is compatible, works good,
and Blue SN550 - issues/not compatible. Thanks again for help.
So, after few days of tests i could say thank you very much @tsialex
I tested my kryo with WD black SN750 250GB and HP ex920 - it works as should be.
Also, sn550 works nice with PC, so it's only not good for mac os/ or cMP
Anybody with permissions may add to 1st post - WD BLACK SN750 is compatible, works good,
and Blue SN550 - issues/not compatible. Thanks again for help.
iStat only have basic support for PCIe SSDs, there are several temperature sensors with PCIe drives/blades, use DriveDX.
Edited the first post to make more clear what is internal and external for 2019 Mac Pro, since T2 Security override macOS:
What are internal storage for the Mac Pro firmware:
What are internal storage for the Mac Pro firmware:
| Mac Pro year model: | Model Identifier: | What Mac Pro firmware recognise as internal drives: |
| Mac Pro (2006) | MP1,1 | SATA drives connected to the 6 southbridge SATA ports plus the two PATA drives connected to the PATA cable inside the ODD bay. |
| 8-Core Mac Pro (2007) | MP2,1 | SATA drives connected to the 6 southbridge SATA ports plus the two PATA drives connected to the PATA cable inside the ODD bay. |
| early-2008 Mac Pro | MP3,1 | SATA drives connected to the 6 southbridge SATA ports plus the two PATA drives connected to the PATA cable inside the ODD bay. |
| early-2009 Mac Pro | MP4,1 | SATA/SAS drives connected to the 4 southbridge SATA ports plus the two SATA drives connected to the SATA cable inside the ODD bay. |
| mid-2010 Mac Pro | MP5,1 | SATA/SAS drives connected to the 4 southbridge SATA ports plus the two SATA drives connected to the SATA cable inside the ODD bay. |
| mid-2012 Mac Pro | MP5,1 | SATA/SAS drives connected to the 4 southbridge SATA ports plus the two SATA drives connected to the SATA cable inside the ODD bay. |
| late-2013 Mac Pro | MP6,1 | Only the PCIe SSD is a internal drive. |
| 2019 Mac Pro | MP7,1 | Only the T2 Storage is an internal drive for T2 Security. While the two SATA ports of the logic board are internal for macOS, T2 Security definitions override macOS and you can only boot from SATA native ports with relaxed T2 Security, with external boot enabled with Startup Security Utility. Any PCIe connected storage are external for the firmware and T2 Security. |
I don't see TG Pro reporting an NVMe temperature either... even with the latest update to TG Pro. These temperatures were during a SuperDuper Smart Update 750Mbps transfer from our 1TB Samsung 970 Evo Plus in it's Aquacomputer KryoM.2 Evo PCIe card in slot 2 to a 1TB Samsung 850 Pro SSD on a Apricom Duo PCIe card in slot 4.
Anybody know how to find the NVMe temp of our 1TB Samsung 970 Evo Plus in it's Aquacomputer KryoM.2 Evo PCIe card?
Thanks!
Here's our MacPro5,1 temperatures doing a 1,050 Mbps SuperDuper! Smart Copy (clone) from our 1TB Samsung 970 Evo Plus on an Aquacomputer KryoM.2 Evo PCIe card in slot 2 to a 1TB Samsung 850 Pro SSD on an Apricom Duo PCIe card in slot 4. Temperatures all completely normal.
Hello,
I've bought a second hand I/O Crest SI-PEX40129 card, on Amazon warehouse, my Mac Pro can't recognize any nvme blades on it, I've tested in Windows 10 with 2 970Evo + 250GB (last firmware) and one 970 Evo 250GB.
The two 970Evo + blades installed in the previous I/O Crest SI-PEX40129 work great, and the 970Evo in a Kryo M2 too, the three in Raid 0 are ok, when I switch in the second SI-PEX40129, the last blade isn't available.
The fan works, and the card has been tested in my Cyclone Backplane and in all the Mac Pro slots, same results. Is the card deffective?
The goal is to use the two cards.
I've bought a second hand I/O Crest SI-PEX40129 card, on Amazon warehouse, my Mac Pro can't recognize any nvme blades on it, I've tested in Windows 10 with 2 970Evo + 250GB (last firmware) and one 970 Evo 250GB.
The two 970Evo + blades installed in the previous I/O Crest SI-PEX40129 work great, and the 970Evo in a Kryo M2 too, the three in Raid 0 are ok, when I switch in the second SI-PEX40129, the last blade isn't available.
The fan works, and the card has been tested in my Cyclone Backplane and in all the Mac Pro slots, same results. Is the card deffective?
The goal is to use the two cards.
Attachments
PCIe SSDs have multiple temperature sensors, most apps like iStat Menus and TGPro don't read all the sensors.
Install DriveDX, 14-day trial, and pay attention to spikes of temperature. It's not the median temperature that is the problem, but the sudden spikes.
Seems a defective one. See if at least the PCIe switch shows with SystemReport and lspci.
TGPro shows the instant temperature and nothing more. DriveDX shows:
- Instant temperature and maximum temperature reached since power up/for the session,
- LifeTime temperature,
- Range and limit.
but why does driveDX recommended/max temperature
write 85 degrees and samsung gives max 70 degrees?
can only be a misinformation from driveDX
write 85 degrees and samsung gives max 70 degrees?
can only be a misinformation from driveDX
DriveDX definitions tables are upgraded frequently, there is a option to enable it. If you found anything wrong, report to BinaryFruit.
The important setting to pay attention is the maximum temperature for the session, to track the spikes in temperature, and the other SMART settings that are showed in every detail.
Thanks tsialex,
I've dowloaded SIV64X System Information Viewer:
The first I/O Crest SI-PEX40129 card and the blades are listed in the SystemReport,
the second I/O Crest SI-PEX40129 isn't listed … I'll return this card to Amazon.
Thanks for your help.
have a chance to try the IO-Crest(Syba) IO-PEX40152 4x M.2 Slot with my friend's New MacPro7,1 today, the card is native supported , and test with 970 EVO Plus , speed is good , wanna try RAID, but he only got one SSD in hand ..maybe later..
and i put my Dual IO-Crest card to his 7,1 , with 2x M.2 SM951 , running RAID, the speed can reach 3400mb/s read , pretty good , maybe the help of PCIe 3.0 slot at 7,1 ? so i think if RAID by 2x 970 EVO plus , the speed will go higher ?
time to add the 4x M.2 IO-Crest card to buy list ?
and i put my Dual IO-Crest card to his 7,1 , with 2x M.2 SM951 , running RAID, the speed can reach 3400mb/s read , pretty good , maybe the help of PCIe 3.0 slot at 7,1 ? so i think if RAID by 2x 970 EVO plus , the speed will go higher ?
time to add the 4x M.2 IO-Crest card to buy list ?
Bifurcation question. What happens when you have a non bifurcation card in a mac pro 7,1? Does it not work outright, or intermittent problems. I have a bunch of evo 850 msatas trying to make them work with a Syba card
https://www.sybausa.com/index.php?route=product/product&product_id=178.
Have not yet found documentation on the card, i wrote tech support.
Drives randomly eject after a couple days
https://www.sybausa.com/index.php?route=product/product&product_id=178.
Have not yet found documentation on the card, i wrote tech support.
Drives randomly eject after a couple days
It's a 4 port mSATA card, Marvell 4-port SATA controller, bifurcation only applies to PCIe SSDs. I doubt that this card was ever really certified for Mac use or is compatible with MP7,1.
A long shot is to report the problems to Apple, maybe someone in Cupertino read the report and do something.
Btw, this thread is about PCIe SSDs (M.2/U.2).
Ya it takes 4 msata ssd's as well as 4 ports of data. You can only use one or the other need to switch jumpers
[automerge]1583788366[/automerge]
It says Mac compatible on the website. My question is specific what happens when you put a non bifurcation card in a Mac pro 7 1. Does it not work out right or does it sputter
[automerge]1583788468[/automerge]
Ok I see bifurcation does not apply to msata. the controller shows up in system profiler and the card seems to work fine so it must be a problem with the firmware on the Samsung Evo 850
[automerge]1583788366[/automerge]
It says Mac compatible on the website. My question is specific what happens when you put a non bifurcation card in a Mac pro 7 1. Does it not work out right or does it sputter
[automerge]1583788468[/automerge]
Ok I see bifurcation does not apply to msata. the controller shows up in system profiler and the card seems to work fine so it must be a problem with the firmware on the Samsung Evo 850
I have this fine MacPro 2009 (5.1) that runs High Sierra. This BootROM you mention, is that somethin I could change myselv once I got it (from ?? where??) I live in Denmark
cross posted from Mojave’s thread
Hello. This forum has been of so much help to me in the past year with my journey with my cMP. However, I am having an issue that finally moved me to make an account and post about.
Some necessary information:
- My boot drive is a Crucial P1 NVMe SSD connected with an adapter to a x4 PCIe slot.
- I had an old HDD as a backup drive in a SATA bay.
- I have an RX 580 and the original EFI GPU.
Recently I decided to take on the upgrade to Mojave (mostly for HW accel) from my long time stay with High Sierra. BootROM upgrade went with no error (in fact I had upgraded to 140.0.0.0 sometime in the past to receive NVMe booting support, so I just needed to jump to 144.0.0.0). I had to switch the Wifi card which went perfect.
So I started the Mojave installer. However, when I finished updating to Mojave, I could not boot to my NVMe SSD. It worked initially when the update finished and the computer booted itself up (funny I have a screenshot of me in Mojave), and a Restart I tried worked; but when I shut it down, reset the PRAM/NVRAM (as I was having trouble with iMessage), and tried booting it would not display an image. I slotted in my EFI GPU and confirmed that, even when manually set, the Mac Pro would refuse to boot from my NVMe SSD.
Is there an issue with my SSD; is my SSD not compatible with Mojave? What would you guys recommend I try? I am posting this from my Mac which I was very fortunate to restore from my backup HDD to High Sierra. I really want Mojave, but at this point I feel like I have to get a SATA SSD to be on Mojave, but that would mean my NVMe SSD would be unused until my next rig and, in turn, a waste of money. Am I missing something?
One thing I have noticed is that APFS seems to mess with my SSD. I think a few months back I tried to upgrade to APFS in High Sierra, and after that I couldn't boot and had to restore back to HFS+. Perhaps it's not Mojave and just APFS?
Thank you all in advance, and thank you for all the information you put up previously that has sustained me until now.
Hello. This forum has been of so much help to me in the past year with my journey with my cMP. However, I am having an issue that finally moved me to make an account and post about.
Some necessary information:
- My boot drive is a Crucial P1 NVMe SSD connected with an adapter to a x4 PCIe slot.
- I had an old HDD as a backup drive in a SATA bay.
- I have an RX 580 and the original EFI GPU.
Recently I decided to take on the upgrade to Mojave (mostly for HW accel) from my long time stay with High Sierra. BootROM upgrade went with no error (in fact I had upgraded to 140.0.0.0 sometime in the past to receive NVMe booting support, so I just needed to jump to 144.0.0.0). I had to switch the Wifi card which went perfect.
So I started the Mojave installer. However, when I finished updating to Mojave, I could not boot to my NVMe SSD. It worked initially when the update finished and the computer booted itself up (funny I have a screenshot of me in Mojave), and a Restart I tried worked; but when I shut it down, reset the PRAM/NVRAM (as I was having trouble with iMessage), and tried booting it would not display an image. I slotted in my EFI GPU and confirmed that, even when manually set, the Mac Pro would refuse to boot from my NVMe SSD.
Is there an issue with my SSD; is my SSD not compatible with Mojave? What would you guys recommend I try? I am posting this from my Mac which I was very fortunate to restore from my backup HDD to High Sierra. I really want Mojave, but at this point I feel like I have to get a SATA SSD to be on Mojave, but that would mean my NVMe SSD would be unused until my next rig and, in turn, a waste of money. Am I missing something?
One thing I have noticed is that APFS seems to mess with my SSD. I think a few months back I tried to upgrade to APFS in High Sierra, and after that I couldn't boot and had to restore back to HFS+. Perhaps it's not Mojave and just APFS?
Thank you all in advance, and thank you for all the information you put up previously that has sustained me until now.
Hi! I'm running a Trebleet Thunderbolt 3 enclosure with a Samsung 970 EVO Plus 1TB and am seeing poor write speeds (on an iMac I'm seeing around 870 MB/s, and on a 2016 MacBook Pro, around 1100 MB/s). I'm running macOS 10.15.3 on the iMac and 10.14.6 on the MacBook Pro. Has anyone seen such low write speeds? I didn't see any evidence of that in the thread history, but wanted to ask explicitly. I tried benchmarking both APFS and HFS+ but there's no major difference between the two. I also tried two different certified TBT3 cables, no change. Maybe there's a setting I'm missing somehow?
