I have read the threads about how SoftRAID is working with Apple to resolve issues created with Catalina's new security architecture, but I have not seen this issue addressed.
I am running MacOS 10.15.4 and SoftRAID 5.8.3 and I have figured out how to successfully install the 5.8.3 driver. My issue is that I have to reinstall that driver with each and every update to MacOS 10.15. Because I am participating in Apple's Beta test program (I am well aware of the risks in beta testing) there are updates every few weeks. Are there plans to make SoftRAID driver updates survive MacOS updates or will this remain the status quo?
My second question is a lot tougher to answer, and I understand if you cannot answer it at all. Is there an estimated/planned/hoped for time to develop a "fix" for the security issues created by the T2 chip and Catalina?
______________
Make intentional errors —
Otherwise the Great Spirit
realizes you have fulfilled
your purpose on earth.
— Navajo saying
In 10.15.x, there is unlikely to be a fix to either.
The driver downgrade is because we bundle SoftRAID with Catalina, Apple's installer team decided to overwrite any later driver and reinstall the bundled version each update. The only solution is stop including SoftRAID with Catalina, or wait until Apple fixes this. We are waiting for now.
The Secure Boot is a similar issue. To prevent potential hacks/exploits, any driver bundled with OS X must be the same version that loads, when Secure Boot is enabled. This was added post-beta in Catalina. Again, we have had no luck in getting this changed.
Sometime in the future, Apple intends to change the driver model so we can avoid this. Until we see 10.16 in beta, we won't know if it is then, or the next update.
In 10.15.x, there is unlikely to be a fix to either.
The driver downgrade is because we bundle SoftRAID with Catalina, Apple's installer team decided to overwrite any later driver and reinstall the bundled version each update. The only solution is stop including SoftRAID with Catalina, or wait until Apple fixes this. We are waiting for now.
The Secure Boot is a similar issue. To prevent potential hacks/exploits, any driver bundled with OS X must be the same version that loads, when Secure Boot is enabled. This was added post-beta in Catalina. Again, we have had no luck in getting this changed.
Sometime in the future, Apple intends to change the driver model so we can avoid this. Until we see 10.16 in beta, we won't know if it is then, or the next update.
In a related issue, the 5.8.3 driver is flagged as a "legacy" kernel extension and support is not guaranteed beyond Catalina. Obviously the future is NOW!
______________
Make intentional errors —
Otherwise the Great Spirit
realizes you have fulfilled
your purpose on earth.
— Navajo saying
The future will be when Apple publishes new driver extension standards and has a beta that supports them. We do not believe any new method for handling drivers will be implemented until 10.17, but will be happy to migrate sooner if possible.
In 10.15.x, there is unlikely to be a fix to either.
The driver downgrade is because we bundle SoftRAID with Catalina, Apple's installer team decided to overwrite any later driver and reinstall the bundled version each update. The only solution is stop including SoftRAID with Catalina, or wait until Apple fixes this. We are waiting for now.
The Secure Boot is a similar issue. To prevent potential hacks/exploits, any driver bundled with OS X must be the same version that loads, when Secure Boot is enabled. This was added post-beta in Catalina. Again, we have had no luck in getting this changed.
Sometime in the future, Apple intends to change the driver model so we can avoid this. Until we see 10.16 in beta, we won't know if it is then, or the next update.
So what exactly is the solution for this? I'm running into the same issue with the driver wanting to reinstall with every reboot with the T2 chip enabled. Disable the chip or just deal with the driver install every time?
In your case, disable Secure Boot. There is no solution for this. This was a decision made by the Security team at Apple and we have not yet been able to get an exception or a workaround.
https://srforums.wpengine.com/pages/support/faq/faq_imacpro_secureboot.html
In your case, disable Secure Boot. There is no solution for this. This was a decision made by the Security team at Apple and we have not yet been able to get an exception or a workaround.
https://srforums.wpengine.com/pages/support/faq/faq_imacpro_secureboot.html
Yeah, I just saw that I don't really have a choice but to disable it if I want to create volumes in Softraid.
We understand and are fighting hard to get this resolved.
My system is now reporting 4 kernel extensions that "may not work in the next version MacOS" including:
SoftRAID.kext 5.8.3
OWC_SCSI_Device_OE.kext 1.1.0b16
OWC_SCSI_Device.kext 101.0b16
OWC_SATA_Command.kext 8.1.0b16
all of which I am guessing are part of SoftRAID
Is there any progress in resolving the issues with Apple?
______________
Make intentional errors —
Otherwise the Great Spirit
realizes you have fulfilled
your purpose on earth.
— Navajo saying
We will have a set of compatible drivers for 10.16, not to worry!

