Could you be a little bit more specific: is the NVM Express Controller listed in PCI section in System infromation ?My IOcrest 2x NVme card is no longer recognized in Seqoia i'm going back.
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, .....Could you be a little bit more specific: is the NVM Express Controller listed in PCI section in System infromation ?
It worked extremely well installed on a Samsung 850 EVO 500GB drive connected to the internal SATA port.Did everything work okay on the internal SSD overall?
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.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.
Yeah I found the post that answered my Q. Sonoma was giving me a lot of trouble.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.
What is the exact model of your IO Crest controller ?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.
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.What is the exact model of your IO Crest controller ?
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!
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.A quote from OWC's blog:
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❗
Slot 3 = SonnetDid you check Expansion Slot Utility bandwidth allocations ?
This is mine config:
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 ?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.
I've removed the RAID of the IOcrest. With two seperate blads it's working oké.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 ?
Well, for me and many others, a few bugs seem to have been squashed.Not at all.
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.See my previous posts.
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.Yesterday I thought I found the solution but today the problems are back again.
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.(
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 winningThank 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 it isn't. I've still got problems,No mount issues in Sequoia 15.0.1.
100% solved.