MacPro 2019 PCIE M.2 (Sonnet AND OWC) drives not mounting after Sonoma updates

I've been fighting this as well since late last year, and have read your terrific PDF. I've gone so far as to purchase an external TB PCIe chassis (Sonnet Echo II DV) and move my two Sonnet FUS-SSD-4X4-E3 to it. It was rock solid, and I did not encounter the "missing NVMe drives" issue a single time in that configuration. That was with a lot of cold and warm booting and disk speed tests with ATTO, AJA, and Blackmagic. That said, it certainly wasn't the same performance using the internal PCIe x16 slots, but I was able to get the ATTO speed test to register 5.33GB/s read + 4.11GB/s write for a RAID 0 across all 8 Samsung 970 Pro M.2 sticks, and 5.34GB/s read + 2.05 GB/s write for a RAID 10 across them.

I have (for unrelated reasons) moved the two PCIe cards back into my Mac Pro 2019, and have observed that I haven't encountered the problem again in a few days. The two differences from before are (1) instead of using slots 3 and 4 just above my W5700X, I'm using slots 4 and 5 for better thermal flow and (2) instead of slots 6 and 7 being empty, I have a Sonnet USB3C-2PM-E in each of them. That is, if this is a PCIe bus probing problem somehow, the gaps in my bus layout are more consolidated (was 1 [2 W5700X disabled] 3 4 gap 8, now is 1 [2 W5700X disabled] gap 4 5 6 7 8). I'm also oversubscribed at 125% on both my Pool A and Pool B Allocations, for what that's worth.

Of course, having written that, I now expect the problem to resurface just out of spite. Often in the other thread, folks would say "hey the problem went away" and then would post a few days later "never mind" (in the voice of Emily Litella).

This is not fixed in macOS 14.6. As before, the workaround of completely shutting down, perhaps leaving off for a few minutes, then starting up cold leads to the PCIe-mounted disks being recognized and mounted.

you don't get a ticket for any informal Bug Reports submitted through the Product feedback links.

If you want a ticket, you need to contact Apple support and work with a first responder, and ask for a specialist to work with you to develop a sution or create a formal, tracked Bug Report.

Sorry your linked file was removed, but when you post stuff on another site, we have sometimes found that later, when Readers go to check up on that, the information on the external site is no longer available.

So the mantra is, post Everything HERE, please, so that it is guaranteed available and can be used as a reference by readers who find your post by searching -- for a long, long time.

--------

It sounds like you have already done a great job getting the makers to work on fixing this NVMe drive mounting issue. Sonnet Tech has a strong interest in making sure this works and continues to work.

Readers who encounter this issue should contact support and file a FORMAL, tracked, Bug Report -OR- get their information added to yours

Developers who are seeing this issue should consider using the Developer Bug reporting system to file a formal bug report as well.

if not willing to put in the time and energy, anyone can, as you suggest, quickly and easily file an informal bug report on the Product Feedback pages.

Yup. As expected, "never mind". Just lost the FUS-SSD-4X4-E3 in slot 4 after a warm reboot. macOS 14.5.

<< As a mod working for Apple, >.

I am not a Moderator, and do not work for Apple. I do not speak for Apple, I speak only for myself.

Most Apple employees are expressly prohibited from participating here.

Moderators/Hosts are mainly here to maintain decorum. This WILL be a welcoming place to share your issues.

Community Specialists (with distinctive Apple avatar) make certain that posts do not go completely un-answered if they have no response after a few days.

I went to Feedback - Mac Pro - Apple and submitted my "Bug Report" for this issue back in the other thread. However, it neither gave me a ticket nor emailed me one.

I tried posting here an ask if anyone had seen any progress in ... well, I can't write it because this post will get taken down. But it would be nice to know if the bleeding edge is seeing any hope.

I actually received an email copy of your reply before it got deleted because I'm subscribed to this thread. That was good news. Since the problem spread from macOS 14 back through macOS 13 from what I've read, I wonder if regression testing of the fix will happen similarly.

Update for macOS 14.6: not fixed. Cold-booted today with a loss of my slot 4 Sonnet NVMe storage.

Checking in (and thread bumping) @StuartFoxMusic — how's your partition working?