No problem, thanks. Hopefully it'll be a reliable method from which to boot.I’m booting from Apple ssd, I have other Samsung ssd disks connected.
No problem, thanks. Hopefully it'll be a reliable method from which to boot.I’m booting from Apple ssd, I have other Samsung ssd disks connected.
My three NVMe external drives are used for: Windows 11, Time Machine, and the third one (4TB) is storage for VMs. Currently I'm booting Sequioia from SATA SSD drive.Just to be clear, you guys that are running Sequoia without problems are you all actually booting from it or is it just a storage drive?
Just to be clear, you guys that are running Sequoia without problems are you all actually booting from it or is it just a storage drive?
Just to be clear, you guys that are running Sequoia without problems are you all actually booting from it or is it just a storage drive?
Ah, this is the answer I was looking for - cheers. Good to know.Both👍🏻
Lou
A good mixture.My three NVMe external drives are used for: Windows 11, Time Machine, and the third one (4TB) is storage for VMs. Currently I'm booting Sequioia from SATA SSD drive.
Thank you, I confirm) For me, this is the first and best MP7.1 system. Finally, everything works without problems and you can work calmly without tedious tests with components.Sequoia 15.0 (24A335) updated only OS Loader version on Mac Pro 7,1 to 582~1023.
I think that there is no point for me to give more of updates like these, because as far as I'm concerned, problem is solved.
Very snappy, the os loads far quicker, maybe as fast as on the m2 MacBook Pro.That sounds very promising. How is the Sequioa performance on the MP7.1? Does it feel fast and snappy?
Wow so they maybe invested some time in the 2019 Mac Pro optimizationVery snappy, the os loads far quicker, maybe as fast as on the m2 MacBook Pro.
Great news.
Only took them 2 years to fix, but better late than never, I guess. 😂
Its definately primarily due to OS, because I've already tested this with bad reuslts:On another note for anybody that has been playing with is.
I don't know where Apple made the fix, whether it was a firmware thing or an OS update. Has anybody loaded Sequoia, (which updated firmware), and then also booted from Sonoma and found it to now be behaving itself?
Ah, Ok sorry anbout that. I'd somehow forgotten that post.I’m booting from Apple ssd, I have other Samsung ssd disks connected.
I have it for my Mac Pro 7,1 - downloaded and installed.Available now for my MacBook Pro, but not the Mac Pro strangely enough. Downloading. Only 5 hours remaining on my 500Meg connection.
Apple servers must be getting hit hard.
It's there for me now.I have it for my Mac Pro 7,1 - downloaded and installed.
I have been running the beta for several months on a separate SSD (internal SATA) and as a daily driver for about a month. As many have said no issues with my NVME drives disappearing.It's there for me now.
Gonna do a clone overnight before installation I think.
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 have been running the beta for several months on a separate SSD (internal SATA) and as a daily driver for about a month. As many have said no issues with my NVME drives disappearing.
Based on that I upgraded my base install on the internal Apple NVME from Sonoma to Sequoia.
Did everything work okay on the internal SSD overall?I have been running the beta for several months on a separate SSD (internal SATA) and as a daily driver for about a month. As many have said no issues with my NVME drives disappearing.
Based on that I upgraded my base install on the internal Apple NVME from Sonoma to Sequoia.