Yeah, overall it shows how bad MacOS became in recent years.
No roadmap, no real development communication with consumers, no driver updates, walled garden everything...
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 7,1 Mac Pro 2019 NVME Raid drives failing to mount
- Thread starter LukeMacPro
- Start date
- Sort by reaction score
No roadmap, no real development communication with consumers, no driver updates, walled garden everything...
It's far from a solution, as it's presumably no good for those who want to boot from their PCIE drives, but as I don't need to do that, unmounting my PCIE drives before shutdown is a viable and so far reliable workaround for me on my 2019. Early days still though!
So to take stock for a bit - apart from @flowrider is there anyone who is running Ventura, and booting / sleepwaking from NVME SSDs without problems?
I don't really fancy dropping a grand and a half to be the guinea pig :/
I don't really fancy dropping a grand and a half to be the guinea pig :/
I had no problems with my Highpoint 1580 card with a Micron 9300Pro 15TB drive with either Ventura or Sonoma. The OS sees it as external but it just always boots right up, thankfully. Maybe because it's the boot drive, that makes a difference?
OK well I found out today that Highpoint has discontinued the 1104f, leaving only the passively cooled 1104, or the triple-the-price pci4, or double the price pci3 8 bay cards as options.
Then I found AmazonUS had them in stock, so i kinda panic bought one, and a pair of 4tb Samsung 990 Pros (which AmazonAU sells from America for abut 2/3 the price of the local market ones).
So, guinea pig time, i guess. Here's hoping I don't end up as the tasty snack on a stick version.
Then I found AmazonUS had them in stock, so i kinda panic bought one, and a pair of 4tb Samsung 990 Pros (which AmazonAU sells from America for abut 2/3 the price of the local market ones).
So, guinea pig time, i guess. Here's hoping I don't end up as the tasty snack on a stick version.
Reliable until I unplugged my USB drives after shutting down and then plugged them back into different ports before restarting - apparently that's still enough to cause the PCIE drives to fail to mount, and need a further shutdown and reboot to come back! [Expletives deleted]
I just had to reset the SMC to get my PCIE drives back, after resetting the NVRAM didn't work; all seemingly from just unintentionally plugging my USB drives back into different ports. My theory is that whatever is stored in the SMC (and NVRAM?) is vulnerable to being "invalidated" by what ought to be innocuously minor configuration changes between one boot and the next.
I'm tempted to upgrade to the Highpoint Rocket 1104 (the passive version) - so it'd be very useful to hear what experience anyone has had already with that specific card on the Mac Pro 2019, and with which SSDs.
Last edited:
Yeah, its weird. Seems to be different results for different users with the same mac, NVME card and system version (but then it always seems to have been like this for Apple, eg, I intall a lab of say 20 iMac & cloned systems & three might be realy weird, no reason).
My personal experience with this to date:
7,1 mac pro, Sonoma 14.4.1, Sonnet 4xm2 PCIe with Samsung 970 EVO+.
This mounting issue happened all the time with earlier versions of Sonoma; 'seemed to stop' or at least got a little bettter at 14.3.
The one thing that set this 'no mounting' off again - & including now on 14.4.1 - was installing some new sw & something with drivers, eg, UAD plugins, Softraid etc. Because of the drivers & re-boot I can only assume this could be something to do with mac os security bs [?] Otherwise, 14.4.1 now always mounts correctly.
The only thing that would bring mounting back correctly was indeed an NMC reset immediatey followed by zap PRAM. Still the very odd thing about that is that this computer is in effect ALWAYS with an SMC reser becuase this studio is powered down at a main UPS unit when not in use.
PS
don't get me started on the dreadful mess that is date-stamping on mac os. Unbelievable.
Last edited:
They are using the same FAN for years now and its not noisy at all. Last time I had Areca ARC-1882-IX-12 in 5,1 and I didn't hear it at all. Arecas are quality products.
Update: moving Sonnet from PCI sled 4 to 5 hasn't improved anything. The random boot fail continues.
I'm also looking forward to macOS 15. I will not even touch Sotona, I mean Sodoma, I mean Sonoma again.
External (PCIe) drives on latest Ventura with 0 (ZERO) issues:
1x PCIe toU.2 3.86TB Micron drive
1x PCIe to SSD drive
2x NVMe drives (Samsung 980 1TB) on Sonnet M.2 4x4 Silent
Last edited:
I've just been looking into how to change the "put hard disks to sleep" setting in Sonoma. This is how my power settings were configured:
![Screenshot 2024-04-14 at 15.53.17.png]( "Screenshot 2024-04-14 at 15.53.17.png")
But I've managed to update the disksleep setting by running the command "sudo pmset -c spindown 0" .
I've no idea whether this will make a jot of difference to the mounting problem, but it seems pointless and potentially counter-productive to have my computer set to spin disks down when there aren't any spinning disks!
But I've managed to update the disksleep setting by running the command "sudo pmset -c spindown 0" .
I've no idea whether this will make a jot of difference to the mounting problem, but it seems pointless and potentially counter-productive to have my computer set to spin disks down when there aren't any spinning disks!
Last edited:
Thanks @bax2023 - disksleep didn't help with the mounting problem but I think I might as well leave it at 0. I've matched the other settings to yours though, just in case...
Refresh my memory - does this problem effect wake from sleep, or only boot. Also, have you set your machine to verbose boot?
I had the problem once (I think - unless I just didn't notice that the drives were missing from boot) when coming out of sleep, before I turned on the "prevent automatic sleeping when the display is turned off" option. So I just thought it would be sensible to disable any other disk-related sleep settings. I suspect that the problem (more generally) relates to power management, so am on the look-out for anything related to that, which can be tweaked to see if it helps.
I did try verbose boot, but it didn't prevent the problem for me.
Verbose eventually failed for me too after a promising start.
I've accepted defeat and gone back to the internal drive for now.
*if* it's happening during sleep, I wonder if the trick of disabling all scheduled maintenance wake events would do anything for it... It certainly cured my display issues, which I put down to the system not fully waking up the GPUs & GPU drivers, which need to be fully engaged to drive all three displays.
Wih the caveat these are being used in Ventura, so check if Sonoma needs changes to it:
Unlock prior to any system updates.
Clear Sleep / Wake schedule:
Code:
pmset schedule cancelallLock Sleep / Wake schedule:
Code:
sudo chflags schg /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plistUnlock Sleep / Wake schedule:
Code:
sudo chflags noschg /Library/Preferences/SystemConfiguration/com.apple.AutoWake.plistCheck Wake reasons:
Code:
log show --style syslog | fgrep "Wake reason"To be clear BTW, the reason I'm using this technique to lock the sleep / wake schedule, is that the calendar app periodically wakes your machine from sleep to check if it's moved geographically, in order to make sure the "time to leave" notifications stay accurate to where the machine is located. When it does this partial wake, it doesn't fire up the full GPU drivers - darkwake - (without full GPU driver, eg during boot, the system only supports 2 displays), which results in some applications (affinity suite) having their window arrangement nerfed.
Reasoning being maybe storage PCI cards experience a version of this?
Reasoning being maybe storage PCI cards experience a version of this?