Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Could you be a little bit more specific: is the NVM Express Controller listed in PCI section in System infromation ?

Could you be a little bit more specific: is the NVM Express Controller listed in PCI section in System infromation ?
The controller is visible everywhere. In diskutility(but greyed out), system information, pci configuration utility, .....
Everywhere except in Finder or on the desktop. The 2 NVME-disks on the card are configured as RAID-0.
Tried resetting, different PCI-slots, multiple restarts, activating in diskutility gives an error.
 
Agh, I'll have to go back and check more closely what was said. My main query is making the boot drive a 3rd party nVME mounted on a drive carrier in the PCI slots, not the Apple one.
I was using a Samsung 850 EVO SSD connected to one of the two internal SATA ports. I did use Monterey on an NVME drive in a Sonnet card - no issues there - but Monterey wasn't known to have issues with NVME drives disappearing.
 
I was using a Samsung 850 EVO SSD connected to one of the two internal SATA ports. I did use Monterey on an NVME drive in a Sonnet card - no issues there - but Monterey wasn't known to have issues with NVME drives disappearing.
Yeah I found the post that answered my Q. Sonoma was giving me a lot of trouble.
I want to avoid overheating and overwriting my internal Apple SSD as much as possible as its a PITA to change. So I was referring to running the new OS on an internal 3rd party PCIe NVME drive. Seems its possible and reliable now.
 
The controller is visible everywhere. In diskutility(but greyed out), system information, pci configuration utility, .....
Everywhere except in Finder or on the desktop. The 2 NVME-disks on the card are configured as RAID-0.
Tried resetting, different PCI-slots, multiple restarts, activating in diskutility gives an error.
What is the exact model of your IO Crest controller ?
 
What is the exact model of your IO Crest controller ?
Thank you for your help but I think I found the solution. After a little thinking and reading some articles about PCI slots, there was one possibility I did not try out. PCI slot3 was occupied with a Sonnet 4xNVME Silent Card. The IO Crest controller was in slot 4. I exchanged those two and now everything seems to be fine. I'll see if this stays this way the next couple of days. Thanks again.
 
  • Like
Reactions: bax2023
A quote from OWC's blog:

If you are using macOS 14 on a 2019 Mac Pro with a PCI card with blades, you have probably started up your Mac at some point and had the volumes on the blades not appear. It’s not just the volumes that do not appear—the blades don’t either. System Report shows that the PCI card is installed, but according to macOS, the card contains no NVMe blades. The blades do not show up in Apple’s Disk Utility application or in SoftRAID. This “feature” was introduced with a new NVMe driver as part of last year’s macOS Sonoma.

This bug only affects Macs running macOS 14 and can occur with OWC Accelsior 4M2 and 8M2 cards as well as other cards like Sonnet 4×4 and 8×4 Silent cards. It occurs with any brand NVMe blade installed on the PCI card. Some users were able to work around it by booting first into Safe Mode and then booting immediately back into normal mode, while others have had to revert to macOS 13 (Ventura) before their blades would finally become available.

The great news is that this bug is now completely fixed in macOS Sequoia. Upon updating your Mac Pro to Sequoia, your blades should now always appear. No more booting into Safe Mode, no more rebooting countless times hoping your blades would show up. It (now) just works!

Sounds good.
 
Not at all. See my previous posts. Yesterday I thought I found the solution but today the problems are back again. Instead of not recognizing the IO-Crest controller Sonoma now does not recognize the Sonnet NVME controller.
Thanks Apple❗:mad:

Did you check Expansion Slot Utility bandwidth allocations ?

This is mine config:

Screenshot 2024-09-19 at 15.53.08.png
 
Did you check Expansion Slot Utility bandwidth allocations ?

This is mine config:
Slot 3 = Sonnet
Slot 4 = IO crest

When IOcrest is in Pool B the IOcrest is vissible and the Sonnet not
When IOcrest is in Pool A the IOcrest is not visible and the Sonnet does

I spent the whole morning in switching Pool A or B, switching cards in differerent lanes and all I get
is or only the IOcrest is visible or only the Sonnet card. Seqoia only recognizes one RAID at the time.

 

Attachments

  • Scherm­afbeelding 2024-09-20 om 12.46.17.png
    Scherm­afbeelding 2024-09-20 om 12.46.17.png
    162.1 KB · Views: 29
Slot 3 = Sonnet
Slot 4 = IO crest

When IOcrest is in Pool B the IOcrest is vissible and the Sonnet not
When IOcrest is in Pool A the IOcrest is not visible and the Sonnet does

I spent the whole morning in switching Pool A or B, switching cards in differerent lanes and all I get
is or only the IOcrest is visible or only the Sonnet card. Seqoia only recognizes one RAID at the time.
OK, so, you have RAID arrays on both M.2 controllers ? Just for testing, can you temporary use one or multiple NVMe blades on one of the cards without RAID ?
 
OK, so, you have RAID arrays on both M.2 controllers ? Just for testing, can you temporary use one or multiple NVMe blades on one of the cards without RAID ?
I've removed the RAID of the IOcrest. With two seperate blads it's working oké.
But when I configur a RAID in Seqoia it's gone again.🥴
 
Not at all.
Well, for me and many others, a few bugs seem to have been squashed.

See my previous posts.
I will not. My post was not in response to anything you have written, but rather an expansion of the post prior to mine, where I extracted some key information for people who just want a quick summary.

Yesterday I thought I found the solution but today the problems are back again.
Hard to say if your dual RAID should count as enough of a 'special case' or not, but I've only seen stable performance so far with my Sonnet Fusion soft RAID. I do hope your case gets sorted out as well, though.
 
That sleep mode problem is an interesting one. Back when I used attempt putting this mac to sleep, I first suspected Power Nap (which seems to wake your mac to perform background tasks). So I switched that off. It was better, but still woke up on occasion. Then after a chat with support, I was told SpotLight indexing was another culprit. Didn't want to turn that off, so waited it out for a few days to finish indexing, and again the mac did indeed wake less. But I could never convince it to stay asleep without turning off services I found to be useful.
These days, I'm cheating. Since the mac now has new server duties (via VMs) as well as its standard workstation tasks, I never ask it to sleep, since hosted services would be affected.
This Sleep Problems Link also suggested you might have to perform an SMC reset (which I think equates to unplugging your MP 7.1 for 15 minutes, and then plugging it in again). Not sure, never tried it.
Just read your edit, glad you found the issue :)
 
Last edited:
  • Like
Reactions: Natalia22
In sleep mode, monitors turn off, but HDD and SSD drives do not turn off. I hear the sounds of HDD drives turning off, and then immediately the sounds of turning on, this repeats endlessly. I also hear the sounds of the HighPoint SSD7101A-1 controller fan. The system unit light also does not turn off. In the settings, it is noted - turn off drives when possible. Has anyone noticed this behavior of your 7.1 (Sequoia) and is there a solution to the problem?

UPD. After a clean installation of Sequoia, there are no problems with sleep mode. Thanks everyone!)

I found the reason for the disks waking up - the Logitech Options mouse driver.(
  1. Try Ohanaware's Sleep Aid
  2. clear the power schedule, & disable system access to the power management schedue.
 
  • Like
Reactions: Natalia22
Thank you very much for sharing your experience and useful observations, they will be useful to me in the future). I read the article on your link. I had a similar problem - mandatory activation of the Bluetooth mouse driver, even if the mouse is connected via a USB receiver.


Surprisingly, I couldn't see your post all this time(
No worries, good on you for finding the solution & thanks for the tip! I like to think that if we're still smiling at the end, we're still winning :)
 
  • Like
Reactions: Natalia22
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.