Sleep support?

@smckenzie

If the volume is mounted, it must be. Send me a SoftRAID tech support file (attach it)

@softraid-support

I had to uninstall soft raid and reinstall and then serialize before the volumes would mount. Otherwise the GUI would just say "mounting" then return to"un-mounted". Nothing in the error log either.

Once I had done that the volume appeared in DiskWarrior and I was able to run a repair. The file index was a 9/10 anyway, no errors, but did it anyway.

It seems a little better but now every time I reboot the volume won't mount and I have to repeat the steps above.

You should  be able to use this terminal command to tell macOS to load the SoftRAID driver:

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

Note:
The "up" key in terminal will show prior commands, so next time you want to do this, just hit the up arrow and this commmand will be available without having to enter it.

@softraid-support

Any progress with the 'volume not mounting on restart' issue?

Just did it again. Woke iMac from sleep, computer hung then rebooted. This time when logged back in SoftRaid said it quit because of an internal error. After 3 attempts the GUI loaded but drives were unmounted, tried to mount and the volumes failed to mount.

So then tried your command:

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

and both volumes mounted fine.

New issue with SoftRAID 6.0.5: when I launch the application I get blank columns for Disks and Volumes.

My RAID5 volume is mounted and functional but I cannot check the status or do anything from the SoftRAID app.

@gvansteelant

That says most likely a process is hanging, like scanning the disks. Did you try restarting and relaunching?

I had to force a shutdown and reboot because restarting hung on the stuck SoftRAID app or related process and the Finder beach balled indefinitely.

It's OK again now. After manually loading the kext again of course.

I've been using SoftRAID since 1998 (Version 2.0) and I've never had this many issues with it.

Can't say the take-over by OWC has me impressed.

Actually this is the same team behind SoftRAID. What has changed is MacOS.

The driver loading, we hope will be fixed in Monterey, I am skeptical Apple will fix it before that, but they might.

Has anyone downloaded and installed the Monterey beta and determined if this problem has been resolved?

It's really getting irritating to deal with reinstalling the driver every time you restart.

Also, ymmv, but my kernel panics when away from my machine (watchdog) have pretty much gone away since I've unplugged the external monitors.

Finally, I have a Thunderbay Flex 8 and the damn things is reading and writing ALL THE TIME even when there are no applications open and time machine isn't running. Does anyone else have this problem? I can't figure out what is causing it. Activity monitor isn't shedding much light...but I might not know what to look for either.

@spaceneedle

I have heard that beta 2 in Monterey has not fixed this yet.

The activity may be spotlight. SoftRAID does not initiate any activity on its own. Try disable Spotlight and restart and see if this goes away. then you can re-enable it and see if it settles down after a couple days of indexing.

@softraid-support

thanks.  I will hold off on the beta update to Monterey. And I appreciate the thoughts on spotlight. I’ll turn it off and see if it settles down. 

Either the update to Big Sur 11.5 or my deleting old dropbox and google drive extensions has cleared up the issue with the driver not loading after a restart for me.

Hopefully Monterey will not cause a relaps.

@gvansteelant

One thing I have noticed about the google extensions is they are dated 40 years ago and could be causing issues, but I have not been asking users to delete them. One would think a small company like google could correctly code-sign and date their tools.

Posted by: @softraid-support

@gvansteelant

One thing I have noticed about the google extensions is they are dated 40 years ago and could be causing issues, but I have not been asking users to delete them. One would think a small company like google could correctly code-sign and date their tools.

With the most recent update to Google Drive (and obsoletion of Backup and Sync), Google had to be special again and the installation creates a folder in /Library/StagedExtensions/Library/.

All other extensions are put in the /Extensions folder at this location but Google creates a separate Google folder with a DriveFS folder in there and then the dfsfuse.kext. The older kext which was in the correct /Extensions folder was not removed. Not sure if that caused the issues with the SoftRAID kext but it sure is messy.