(Currently) macOS Catalina 10.15.7 (Intel) --- long story short, just updated the SoftRaid version to 6.3 and disabled SecureBoot for the driver installation. I was previously on 6.03.
On 6.03 this SoftRaid article most certainly applied: https://www.softraid.com/how-secure-boot-and-system-integrity-protection-guard-your-mac-from-malware/ Specifically, the section that says:
What we recommend:
We want to ensure that you are only running the latest version of the SoftRAID driver with all of the enhancements and fixes we have worked hard to develop and test. This means that if you are on a Mac with a T2 chip and running macOS 10.15, you must do one of the following to use the latest SoftRAID driver:
- Disable Secure Boot following these instructions
–or–
- Disconnect your SoftRAID volumes after shutdown and reconnect them more than 2 minutes after your Mac starts up.
Yes, of course I realize that I can leave SecureBoot on "No Security." Upon installation, of course it appeared and worked (with Secure Boot still on "No Security"). However, with 6.03 I had gotten used to putting the computer back on "Full Security" and simply waiting a couple of minutes before connecting SoftRAID drives/volumes. And it always worked that way.
Now, when I do that, even with the drives physically disconnected from the computer, and attempt to load the application, I get a big STOP sign and am told that the driver cannot load with Secure Boot enabled at all. (I have attached a screen shot of the exact message).
Do I just need to leave it on "No Security" all of the time with 6.3? I didn't have to do this with 6.03 and didn't get the memo this changed with 6.3
Couldn't find downloads for versions 6.2 or 6.1 so I may roll back to 6.05 if need be but wanted to ask if this is just the way things are.
Thanks,
Sean
This is a Catalina bug, which was fixed in Big Sur. You need to either disable Secure Boot, or wait the two minutes. Te way around this is updating to Big Sur. (Or live with it)
This is a Catalina bug, which was fixed in Big Sur. You need to either disable Secure Boot, or wait the two minutes. Te way around this is updating to Big Sur. (Or live with it)
Thanks, will do. Super quick follow-up. Does the bug also apply to an anomaly in the Volume Title description? On 6.3 I have just noticed that it shows the volume size, and then the available space remaining is not accurate. In fact, I have "SSD Mirror" and "Video Book Backup Mirror" essentially full, but the volume titles show the 4TB remaining on each. For a moment it freaked me out but mounting and loading in Finder has confirmed the data is all still there so all's well. But the space remaining is not reflecting that
Its a bug from the updated developer kit. We will eventually fix this.