Its sucks that you have degraded RAID, but you scared me, I already tought that this is some kind of fluke, but 22 days of fluke would be almost impobssible since I use Mac Pro daily for all kinds of tasks.Update:
After much faff trying to downgrade from Sequoia beta back to Sonoma, which Apple won't let you do easily without completely formatting the drive in boot recovery and reinstalling from a boot usb and bringing everything back from with Time Machine/Migration assistant, Softraid is saying that the Raid on my Sonnet 8x4 is degraded/missing a disk and so will not mount. Even though I can see the missing disk there without errors. I'm thinking this was already an issuse before i Updated to Sequoia as it wasn't mouting before I upgraded and just assumed it was the usual mounting issues, hoping it would appear with the update.
Point I'm making is, ignore my previous comment that Sequoia doesn't solve the issue as @bax2023 hasn't had mounting issues since updating and I'll need to test again once I've rebuilt the Raid and done another update to Sequoia.
🔫
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
Hello friends!
About 3 years ago, the same problems began with the disappearance of external drives in other operating systems on HighPoint SSD7101A-1, Sonnet Fusion Flex J3 i, frequent reboots, turning off/on the computer was very annoying.
Fortunately, there were also pleasant moments when the external system worked properly for weeks. I began to notice a pattern and am sharing my experience with you, I hope it will help someone. I have been working steadily for about a year.
If you need to work on an external macOS drive, then when you turn on the computer, you must first boot into the system on the main Apple drive and reboot through “System Settings - General - Boot Disk” to another drive with macOS or Windows, Bootcamp.
When you turn on MacPro 7.1, do not boot the system from external media through the Option/Alt boot disk selection menu, this method is only applicable for the Apple disk (after updating the system there may be failures, but the Option/Alt key when turning on my computer helps boot into the main system Macintosh HD).
For clarity, I will attach a screenshot.
Sincerely, Natalia.
I'll add this so you don't get confused.
On my computer I installed a second MacOS and Windows system on NVME and Bootcamp - on SATA. SATA drives work fine and don't disappear.
About 3 years ago, the same problems began with the disappearance of external drives in other operating systems on HighPoint SSD7101A-1, Sonnet Fusion Flex J3 i, frequent reboots, turning off/on the computer was very annoying.
Fortunately, there were also pleasant moments when the external system worked properly for weeks. I began to notice a pattern and am sharing my experience with you, I hope it will help someone. I have been working steadily for about a year.
If you need to work on an external macOS drive, then when you turn on the computer, you must first boot into the system on the main Apple drive and reboot through “System Settings - General - Boot Disk” to another drive with macOS or Windows, Bootcamp.
When you turn on MacPro 7.1, do not boot the system from external media through the Option/Alt boot disk selection menu, this method is only applicable for the Apple disk (after updating the system there may be failures, but the Option/Alt key when turning on my computer helps boot into the main system Macintosh HD).
For clarity, I will attach a screenshot.
Sincerely, Natalia.
I'll add this so you don't get confused.
On my computer I installed a second MacOS and Windows system on NVME and Bootcamp - on SATA. SATA drives work fine and don't disappear.
Last edited:
Interesting theory, but in my case, macOS Sequoia is on the SSD (Samsung 870 EVO 500GB) connected to one of the SATA ports. Because Sequoia runs stable for my workflow I haven't booted into Apple SSDs (Ventura) for more than 3 weeks. If this OS (Sequoia) remains stable through betas and finaly to RC and Stable versions, I'll then clone it to the Apple SSD.
I've install Sequoia Beta 1 (and then Beta 2) as an upgrade to the Sonoma 14.4 which was on that same SATA SSD drive. Actually, that macOS Sonoma befora the update had NVMe mount issue very oftenly.
I'm thinking of going to one of those SATA drives in the meantime. I need the space and hoping that it's only the NVME drives that are disappearing?
Only the NVMe drives are not mounting properly at least in Sonoma and very rarely in Ventura. Did not use my MP with older OSes.
Well if Sequoia doesn't fix it then that's ,my route. Security and data integrity are more important than speed.
Sequioa looks promising so far, that's the reason I'm keeping this forum posted about my experience with it regarding NVMe. One of the reason I've got Mac Pro over some other machine are internal storage upgrades. If Sequoia does not solves this, I'll have to look for other non-Mac solution.
The non Mac solution is definitely coming for me some day. Unfortunately.
ARM just in't up to date on drivers, (in the industrial workspace), I've even had to go back to an Intel MacBook Pro for site work.
Good to know.
I'd suggest it's a Mac software thing, (whteher software or firmware). I never get disconnects when running Win10.
Would you be so kind as to tell me what the real world read/writes are for that 500 SSD?
I would likely remind you of the Problem with most if not all Samsung NVME Drives incompatibility with Apple´s Trim on APFS in connection to the Phoenix Controller of the Samsung NVME Drives.
This is also leading to an almost unusable System after Time if you use an NVME from Samsung with the Phoenix Controller because Trim at Boot can Take up to 20 Minutes.
I do not get why in this World anybody is using Samsung NVME Drives in or at a Mac in any shape or form.
This does not relate to most of the SATA SSD but also there are some incompatible ones.
Best Buy for NVME in and at Mac is WD SN770 / WD SN 850 also with the X.
Best Buy for SSD is Crucial MX500.
For Details read this Post from trs96 @ tonymycx86:
Even the Crucial P5 NVME does not have the Trim Problems but does not work with the Energy States in and at Mac also in external Enclosure well and sucks continuously 8W.
This is also present with the Samsung NVME´s and does lead to heating and in a Laptop to Battery drain.
This knowledge is old but trs96 sums it up mostly about Samsung and WD.
In the Teminal you can Enter the following to see how long Trim took at boot for each Disk:
This is also leading to an almost unusable System after Time if you use an NVME from Samsung with the Phoenix Controller because Trim at Boot can Take up to 20 Minutes.
I do not get why in this World anybody is using Samsung NVME Drives in or at a Mac in any shape or form.
This does not relate to most of the SATA SSD but also there are some incompatible ones.
Best Buy for NVME in and at Mac is WD SN770 / WD SN 850 also with the X.
Best Buy for SSD is Crucial MX500.
For Details read this Post from trs96 @ tonymycx86:
Even the Crucial P5 NVME does not have the Trim Problems but does not work with the Energy States in and at Mac also in external Enclosure well and sucks continuously 8W.
This is also present with the Samsung NVME´s and does lead to heating and in a Laptop to Battery drain.
This knowledge is old but trs96 sums it up mostly about Samsung and WD.
In the Teminal you can Enter the following to see how long Trim took at boot for each Disk:
Bash:
log show --predicate "processID == 0" | grep spaceman
Last edited:
Seem to work fine here, no slowdowns with boot - not that I (re)boot the machine more often than every month or two, or mount problems.
Good job I have a selection of brands.
I'll try the Corsair or Sabrent.
I have six Samsung NVME drives on two cards in my 7,1 NcMP. These were first installed in my 5,1 cMP. They are four 970 EVOs and Two 970 Pros. I've never had issues with these drives.
Lou
My MP7.1 has four 970 EVO PLUS drives installed and the problem exists. But I learned to cope with it.
Interesting about TRIM.. If I boot into the system on NVME APFS via an Apple disk, then after that NVME works normally, I can reboot as much as I want, turn off/on the computer, and not a single disk disappears.
Interesting about TRIM.. If I boot into the system on NVME APFS via an Apple disk, then after that NVME works normally, I can reboot as much as I want, turn off/on the computer, and not a single disk disappears.
I'm now no longer having the issue with two 980 Pro NVMEs. I've been rebooting into windows and back and forwards without dramas.
I am on MacOS 15b2.
I am on MacOS 15b2.