Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Think it might be some missing updates in between to Monterey !?

No, you already have the most recent BootROM.

Your issue seems hardware wise. Open System Information, Hardware, NVMExpress, Generic SSD Controller and look at Link Width and Link Speed:

Code:
Generic SSD Controller:

WD_BLACK SN770 2TB:

  Capacity:    2 TB (2.000.398.934.016 bytes)
  TRIM Support:    Yes
  Model:    WD_BLACK SN770 2TB
  Revision:    731100WD
  Serial Number:    xxxxxxxxxxxxxxxxxx
  Link Width:    x4
  Link Speed:    5.0 GT/s
  Detachable Drive:    No
  BSD Name:    disk0
  Partition Map Type:    GPT (GUID Partition Table)
  Removable Media:    No
  S.M.A.R.T. status:    Verified

Btw, if your SSD is full, write speeds drop absurdly.
 
No, you already have the most recent BootROM.

Your issue seems hardware wise. Open System Information, Hardware, NVMExpress, Generic SSD Controller and look at Link Width and Link Speed:

Code:
Generic SSD Controller:

WD_BLACK SN770 2TB:

  Capacity:    2 TB (2.000.398.934.016 bytes)
  TRIM Support:    Yes
  Model:    WD_BLACK SN770 2TB
  Revision:    731100WD
  Serial Number:    xxxxxxxxxxxxxxxxxx
  Link Width:    x4
  Link Speed:    5.0 GT/s
  Detachable Drive:    No
  BSD Name:    disk0
  Partition Map Type:    GPT (GUID Partition Table)
  Removable Media:    No
  S.M.A.R.T. status:    Verified

Btw, if your SSD is full, write speeds drop absurdly.
I will have a look for it. But… the NVME are fresh taken out of the package, I installed naked High Sierra or big sure.there is nothing on the discs.Everything with the same write limit. It feels a little bit like the Mac 6.1 did not unterstand NVME and was still working in SATA Mode. Are there any patches or updates available I can install to get it running as I want??
 
I will have a look for it. But… the NVME are fresh taken out of the package, I installed naked High Sierra or big sure.there is nothing on the discs.Everything with the same write limit. It feels a little bit like the Mac 6.1 did not unterstand NVME and was still working in SATA Mode. Are there any patches or updates available I can install to get it running as I want??
The Tb2 Transcend 855 HDD has the same write maximum
 
I will have a look for it. But… the NVME are fresh taken out of the package, I installed naked High Sierra or big sure.there is nothing on the discs.Everything with the same write limit. It feels a little bit like the Mac 6.1 did not unterstand NVME and was still working in SATA Mode.

MacPro6,1 does not even have SATA devices…

Are there any patches or updates available I can install to get it running as I want??

No, you already have 481.0.0.0.0. You probably have something wrong with the 12+16 socket or the adapter. I'd install back the AppleOEM blade and try to run ASD 3S159 to see if something is wrong with the hardware.

Disconnected AirPort can cause high CPU usage and your low transfer rate can be from that.
 
MacPro6,1 does not even have SATA devices…



No, you already have 481.0.0.0.0. You probably have something wrong with the 12+16 socket or the adapter. I'd install back the AppleOEM blade and try to run ASD 3S159 to see if something is wrong with the hardware.

Disconnected AirPort can cause high CPU usage and your low transfer rate can be from that.
I am just downloading the diagnostic tool. What means/are disconnected airport?
And the second question: why does external TB2 case with NVME has the same limits- r/w values?
 
I am just downloading the diagnostic tool. What means/are disconnected airport?
And the second question: why does external TB2 case with NVME has the same limits- r/w values?
Adapter (I just tried 2) was also my idea.
 
I am just downloading the diagnostic tool. What means/are disconnected airport?

When you have something like the AirPort with a bad connection, MacPro6,1 CPU usage goes to the roof. That's why I suggested you to run ASD.


Anyway, double check anything, don't just assume something.

And the second question: why does external TB2 case with NVME has the same limits- r/w values?

First thing, TB2 have a lot of overhead, so expect around 20% less throughput.

If the CPU usage is high, explains why you also have poor throughput with TB connected drives.
 
It is not clear how you have connected your NVMe drive. Is it plugged into the internal slot or an external TB2 enclosure?
I have both. external NVME in Transcend 855 case and what I am trying to get running internal sintech adapter + crucial 2TB NVME SSD. Both seem to be limited in writing performance anyway.
 
So ladies and Gentlemen, This day I worked it out. The story went completely different. As you mentioned I tried the ASD and the Mac Pro was totally fine. No problem with Airport nothing. But one thing was NOK: The memory! When I bought it two years ago, I ordered non Apple memory that worked - 64 GB ECC-R. but exactly those lead to the problem. Registered dimms seem to be not so good. I changed back to the original ones I still had and ran the tests and wow! I have now 1400 Write 1400 Read! I also tried all the NVME I have still laying and the best performance came from the Samsung 990 Pro 1 TB NVME - WD Black or Crucial P3 or 970 EVO exactly 100 MB below. So this shall be the end of the story and I am happy!!! Thank you for ideas and effort!!
 
  • Like
Reactions: SpotOnT
i just decided i will never buy memory for my trashcan because if the memory i've tested repeatedly was in fact the root cause of the WindowServer watchdog seeing my D300s crashing and kernel panicking, i would lose my entire mind. i gave up a few years ago and installed windows 10 and it's been delightful. occasionally i have to boot to macOS and do something in startup disks or boot option security because WSL stops working due to CPU features being disabled for some reason, but that's not Windows' fault.
 
So ladies and Gentlemen, This day I worked it out. The story went completely different. As you mentioned I tried the ASD and the Mac Pro was totally fine. No problem with Airport nothing. But one thing was NOK: The memory! When I bought it two years ago, I ordered non Apple memory that worked - 64 GB ECC-R. but exactly those lead to the problem. Registered dimms seem to be not so good. I changed back to the original ones I still had and ran the tests and wow! I have now 1400 Write 1400 Read! I also tried all the NVME I have still laying and the best performance came from the Samsung 990 Pro 1 TB NVME - WD Black or Crucial P3 or 970 EVO exactly 100 MB below. So this shall be the end of the story and I am happy!!! Thank you for ideas and effort!!
So here again some feedback- the issue lies in small details. After the memory Desaster I ordered memory specially from a German memory reseller for the 6.1.Can You see the difference? I cannot see, I am very sorry for that. The top one is the one not working, the memory in the package is working like a Charme.. now max memory and high speed NVME + total clean device (when opened for the airport topic cleaned the can with pressure air)
IMG_2642.jpeg
 
So here again some feedback- the issue lies in small details. After the memory Desaster I ordered memory specially from a German memory reseller for the 6.1.Can You see the difference? I cannot see, I am very sorry for that. The top one is the one not working, the memory in the package is working like a Charme.. now max memory and high speed NVME + total clean device (when opened for the airport topic cleaned the can with pressure air)View attachment 2356230
The spec looks identical so its most probable that the DIMM is faulty in some way. I had a similar situation the 6.1 which would run very slowly after I had installed a RAM upgrade. Changing the DIMM fixed the problem
 
The spec looks identical so its most probable that the DIMM is faulty in some way. I had a similar situation the 6.1 which would run very slowly after I had installed a RAM upgrade. Changing the DIMM fixed the problem
I am thinking more on the memory organization. I am no Samsung DIMM specialist, but the working memory Has CMA Q8M signature. This might mean different internal details. In an HP DL380 G8 or a Dell server the memory might work without issues..
 
Still 481.0.0.0.0 with today's Monterey 12.7.4:

Code:
Hardware Overview:

  Model Name:    Mac Pro
  Model Identifier:    MacPro6,1
  Processor Name:    6-Core Intel Xeon E5
  Processor Speed:    3,5 GHz
  Number of Processors:    1
  Total Number of Cores:    6
  L2 Cache (per Core):    256 KB
  L3 Cache:    12 MB
  Hyper-Threading Technology:    Enabled
  Memory:    64 GB
  System Firmware Version:    481.0.0.0.0
  OS Loader Version:    540.120.3~37
  SMC Version (system):    2.20f18
  Panel Illumination Version:    1.4a6
 
The thread here with hundreds two thousands of posts with issues with D300 drivers beg to differ.


Have you installed 12.7.5 yet and seen if the firmware is updated? Safe to proceed with 6,1 in your opinion?
 
Have you installed 12.7.5 yet and seen if the firmware is updated?

Yes, no new firmware upgrades.

Safe to proceed with 6,1 in your opinion?

12.7.5 changes a lot of things, you can’t reset the Launchpad (now you can only reset the Dock) anymore for example. I even did a clean install to make sure that was not a problem elsewhere.

I’d wait a little for more reports.
 
Yes, no new firmware upgrades.



12.7.5 changes a lot of things, you can’t reset the Launchpad (now you can only reset the Dock) anymore for example. I even did a clean install to make sure that was not a problem elsewhere.

I’d wait a little for more reports.

That's good to know.. thank you so much!

Is it possible to do 12.7.4 os and safari update in the meanwhile? I missed this and 'system update' now only gives the option for 12.7.5.

Sorry for this dumb query..
 
  • Like
Reactions: FilthyMcNasty
Yes, no new firmware upgrades.



12.7.5 changes a lot of things, you can’t reset the Launchpad (now you can only reset the Dock) anymore for example. I even did a clean install to make sure that was not a problem elsewhere.

I’d wait a little for more reports.
yep no new firmware
 
  • Like
Reactions: FilthyMcNasty
I'm new to Mac Pro, got the top model trash can and upgraded with 1 TB Aura SSD without reading too much about the possible complications. It's supposed to become a triple boot machine with Mac OS 10.14, the newest Mac OS at any given time by using Open Core Legacy Patcher, and a bootcamp Win 10. I got to partitioning the two Mac OS partitions and had to clone Mojave on to the smallest partition, as I couldn't install. I hoped I could the install Monterey on the other and run OCLP, but even after resetting NVRAM and checking I have Boot ROM Version 481.[..], I can't install onto it. What can I do now and in the long run?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.