This is really just a note to report an issue I just sorted out. I'm on macOS 13.0 and running SoftRAID 7.0 beta18 on a Mac Studio. I got everything up and running (both ThunderBay enclosures mounted) and then later needed to disable SIP. Even with reinstalling the driver, I would really quickly get a kernel panic upon booting with the drives plugged in (similar to what happened when I moved from Intel to M1 via migration, before the 6.3 beta and Ventura beta). I had to re-enable SIP and reload the SoftRAID kext via command line so it would rebuild the boot caches. When it came back up, all is well again.
There may be something really obviously wrong about what I've said up there, just mentioning that disabling SIP after it all works seems to bork things up. Perhaps if I'd done the below code with the drives unplugged with SIP disabled it would have sorted itself out, but I was more interested in getting my drives to mount again than futzing with having SIP disabled at this point.
sudo kmutil load -p /Library/Extensions/SoftRAID.kext
That's it. Cheers
What made you disable SIP?
I recommend you do this, as disabling SIP (even temporarily) can have longer term repercussions on installing drivers in Big Sur and later.
Startup in System Security mode, as you do to enable third party drivers.
Run the terminal.app: (this assumes your startup volume is named Macintosh HD, change as approrpriate)
Enter the command: kmutil trigger-panic-medic —-volume-root “Volumes/Macintosh HD”
Note: The quotation marks are important if the name for your startup volume has a space in it.
You will see some text about macOS disabling all third party extensions
- Restart your Mac
A dialog box will pop up informing you all third party extensions have been disabled. Click OK to go to System Preferences, Privacy and Security to enable extensions again.
Just to be clear, you mean for me to do this now, having previously disabled SIP and then re-enabled it, to clear up potential issues down the road? As in do this as a preventative step, just in case.
Either way thank you.
Yes, you could run into unexpected issues down the road, so its best to reset this macOS "database".
Its no different than resetting the clock in MacOS to a past date for a while, that can cause unexpected issues also. But that requires a MacOS reinstall to fix, this is just a terminal command.
Got it. Thanks a bunch.