Volume does not mount after BigSur 11.5 update.

If you paste this into terminal, does it mount:

sudo kmutil load -p /Library/Extensions/SoftRAID.kext

Yes. For me, with the same problem, that command worked fine to restore the drives to full functionality.

I had all SoftRAID drives (2) showing before I ran /updated the Parallels app. Then they suddenly disappeared from desktop but were fine in the SoftRAID app. Thanks for the quick fix. Is this something I need to do regularly??

@henry-in-florida

Probably each restart. See if 11.5 fixes this for you.

Note:
The "up" key in terminal will show prior commands, so next time you need to manually load SoftRAID, just hit the up arrow in the terminal window, and this command will be available without having to type it.

Posted by: @softraid-support

@henry-in-florida

Probably each restart. See if 11.5 fixes this for you.

Note:
The "up" key in terminal will show prior commands, so next time you need to manually load SoftRAID, just hit the up arrow in the terminal window, and this command will be available without having to type it.

Hmmm... Nope, where it happened is 11.5.1. Please report if it's something to do with MacOS 11.5 or fix the glitch. 

Posted by: @softraid-support

If you paste this into terminal, does it mount:

sudo kmutil load -p /Library/Extensions/SoftRAID.kext

Becoming a PIA. You were right. Happens often and a good thing the previous entry line shows up in Terminal! Is a fix possible for you to implement since you know what the issue is? 

Otherwise, I'll keep posting I get hit by this issue in Big Sur release 11.5.1. Wouldn't care if it were beta, but a release? Yes. I get that your app is in beta... 

Interestingly, I just downloaded the full update to 11.5.1 (All 12 GB of it).  I've now installed it on two machines and I don't have to reboot after the completed installation.  My drives mount in SoftRaid 6.0.5 directly.  Is it possible that Apple finally fixed this bug?

seriously think SR could improve the perceived stability of their product even though it's due to a mac bug by just executing that shell command on startup if it sees unmounted volumes.  like it would really improve the end use experience regardless of where the fault lives.

Same situation as described by Henry-In-Florida. The "patch" (entering sudo kmutil load -p /Library/Extensions/SoftRAID.kext) works as well BUT must do so every reboot. Clearly a pain to say the least. Please investigate permanent resolution.

@mrfearless47

I do not think this is the actual (complete) fix, as it is not yet in Monterey, but its possible it is fixed. At least, it is mostly fixed.

Big Sur has been a huge mess for drivers.

@dfortney

I do not think this is going to happen, though.

@softraid-support why not?  seriously, it would solve the immediate issue many people are facing.  can't you just convince whoever has some dogmatic position against it?  at the end of the day doing what's right for your customers is all that matters.

Ok here's a weird one.  Over the past couple of days I've setup a new 2019 Mac Pro from scratch and attached a new ThunderBay Flex to it.  I created 3 volumes on the Flex.  I expected the volumes not to mount and that I would have to load the SoftRAID.kext via a terminal command anytime I did a restart.  That's exactly how everything played out .... until today.  Today I added my last piece of software to the new machine, Alosft's DiskWarrior 5.2.  Once DiskWarrior's install process finished, I had to A-OK Alsoft's extension via the usual Security & Privacy System Preference and then restart the machine.  I loaded the SoftRAID.kext via the terminal command to mount the volumes and then launched DiskWarrior.  I was surprised to receive yet another request to approve two more extensions.  One for Alsoft and one for Charles Moore. I approved them both and restarted.

Imagine my surprise when all the SoftRAID volumes mounted as they normally should!

@robert_olding

Hopefully this will be fixed soon. thanks for the feedback.

@dfortney

This becomes code that has to be managed/supported. Especially as this will be fixed by Big Sur and is partially fixed in 11.5. I don't see this happening.