According to their instructions, I loaded the driver in the terminal, then confirmed it in the system settings. Reboot .... Kernel Panic. Driver could not be loaded. In Softraid I can see my raid but not activate it.
You need to remove the drives. then uninstall SoftRAID from utilities menu
Run System Preferences
Run SoftRAID and install the driver.
You should get the System Preferences dialog. If you do and allow it before restarting, you still have this issue?
Most users are fixed with 11.4, so there has to be a fix here.
It was a broken record. However, it was not recognized as such by Softraid. After several tests (disks run in Raid 5) I managed to load the driver. I have installed a new disk and the restoration is in progress. I'll get back to you later. Thanks for your support.
@softraid-support Not yet....... I use them. I'll check out the other alternatives first, thanks!
do......@softraid-support Hi! I have done everything. I still can't mount my RAID. Softraid sees it still, but the system doesn't. I've tried to force mount it through the terminal. Nothing. I got all the correct dialog boxes to approve the extension and checked them all. I don't know what else to do...
Sorry for the frustrating experience.
Attach a newly created SoftRAID Tech Support file, and I can see if the driver is loading or not.
As expected the driver is not loading, it is blocked by Big Sur.
Its possible this will fix this:
uninstall SoftRAID (utilities menu)
run the terminal.app and paste these commands in, one at at time. (We are going to delete some old extensions, if you are using the National Instrucments extensions, see if there is a newer version for Big Sur)
sudo rm -r /Library/Extensions/hp_io_enabler_compound.kext
sudo rm -r /Library/Extensions/hp_designjet_series.kext
sudo rm -r /Library/Extensions/Wacom Tablet.kext
sudo rm -r /Library/Extensions/nipalk.kext
sudo rm -r /Library/Extensions/NiViPciK.kext
sudo kmutil clear-staging
sudo kextcache -i /
restart and install the SoftRAID driver again. Do you get the option to "Allow" OWC as an identified developer in System Preferences/Security?
@softraid-support THAT did it!!!!! Kudos for your patience and solution! Whew!!!
Would you please help me as well? Every time I restart my SoftRAID volumes won't mount. I have to go though uninstalling, clearing kext, rebuilding boot cache, reinstalling, and then it works until I reboot again. But now Big Sur never asks me to "Allow" at any point during that process.
EDIT: I seldom post without an edit.
Lets try the test which has helped two users:
Disable SIP
(startup in internet recovery mode (command r), and enter this in terminal:
csrutil disable.
restart and run this command in terminal (copy/paste)
sudo rm -r /var/db/SystemPolicyConfiguration/KextPolicy
restart and run SoftRAID. reinstall the driver. Does this work?
I am testing this theory.
No go. Restarted into Recovery. Disabled SIP. Restarted. Issued the command in Terminal. Restarted. Re-installed SoftRAID driver. Restart. Drives did not mount, nor was I ever prompted to Allow the driver.
So I re-installed the driver again which immediately mounts the drives, then I force quit on the SoftRAID application to avoid the forced restart which will cause my drives not to mount.
EDIT: I seldom post without an edit.
Something else I thought of as well. I completely uninstalled SoftRAID and rebuilt the kext cache. I thought macOS had a built-in although old SoftRAID driver that should mount my array when SoftRAID was not installed?
EDIT: I seldom post without an edit.
Its not good to run with a mismatched driver, however, so your force restart trick is unsafe. There is a built in driver (limited), but when drivers are not loading, neither is the bundled driver.
I am not sure when this is going to be fixed, but it becoming clear this is a issue with the permissions architecture in Big Sur. Hopefully we can find a clear way to make this simpler, but the issues are inconsistent. Users should not have to struggle with as basic a thing as an intentionally installed extension loading.
@softraid-support Thanks for your help. I'm thinking about just moving to a single large drive and dropping the redundancy or something else altogether as this is just too painful. Seems all I do on my Mac nowadays is troubleshoot RAID. Sorry to gripe.
EDIT: I seldom post without an edit.

