I have two paired RAID drives on - Thunder-bay 4
I've had these drives for a couple years, and have no issues. Today they've stopped mounting. They do appear in the SOFTRAID app (V6.0.5), and show up as 'Unmounted'. I try to mount them, but that doesn't work.
I've restarted my Mac (on Big Sur) multiple times, updated SOFTRAID, but the drives still don't connect.
Help - not sure what to do here.
Try pasting this into terminal to see if they mount. the driver is not loading.
sudo kmutil load -p /Library/Extensions/SoftRAID.kext
Note:
The "up" key in terminal will show prior commands, so next time you want to manually load SoftRAID, just hit the up arrow and this command will be available without having to type it.
That works!! Is there a way of doing something so this is fixed? or would I have do this every time? Thanks for your help.
this is a Big Sur bug, it will be fixed in a future macOS release
Note:
The "up" key in terminal will show prior commands, so next time you want to manually load SoftRAID, just hit the up arrow and this command will be available without having to type it.
It may stop with a clean system install, but there will be a macOS fix in the future to resolve this issue, we do not know when, it could be as late as Monterey, however.
For what it's worth...
I've had this same issue when updating to v6.0.5, all while running macOS Big Sur 11.4, which caused me to just stay at v6.0.3.
Yesterday I tried updating again to v6.0.5 and the issue returned: the drive wouldn't remount after a restart and I had to run the "sudo kmutil load -p /Library/Extensions/SoftRAID.kext" command to get the drive on the Desktop.
What I found to eventually work:
Don't "update-in-place" to v6.0.5 from v6.0.3. Run a full uninstall from within v6.0.3.
Restart.
Install v6.0.5, making sure you get the prompts for extension approval and, thus, the need for a restart.
Restart.
Drive mounted automatically after restart and has continued to mount automatically ever since.
We do expect this to be fixed in Monterey, perhaps sooner. As far as I can tell the problem is with a bug in StagedExtensions, which is why "eventually" uninstalling the driver works, the StagedExtensions finally clear.

