SoftRAID driver not...
 
Notifications
Clear all

[Sticky] SoftRAID driver not loading at startup in Big Sur - workaround in SoftRAID 6.1 beta

Page 6 / 10
(@rdieringer)
Eminent Member

@softraid-support

I did upgrade to Monterey, but that didn't fix the problem. I then decided to split the mirror so I could finally get back to my data, but got this error (in console): The split mirror command for volume "RAID" failed with an error (error number = 101).

ReplyQuote
Posted : 28/10/2021 5:27 pm
(@softraid-support)
Member Admin

@rdieringer

Make sure the SoftRAID driver is loaded, and you should be able to split mirror.

ReplyQuote
Topic starter Posted : 28/10/2021 8:10 pm
(@rdieringer)
Eminent Member

@softraid-support

Well, that's the rub - the driver never loads, by any and all means. So that's under 11.6, 11.6.1, and 12.0.1 now - behavior doesn't change.

ReplyQuote
Posted : 28/10/2021 9:48 pm
(@softraid-support)
Member Admin

@rdieringer

Have you tried creating a second system volume? I can give steps if I have not yet for you.

ReplyQuote
Topic starter Posted : 28/10/2021 10:50 pm
 zoli
(@zoli)
Eminent Member

I have waited to the new SofRaid software (6.2) to use, but no success! The M1 Mini with OS 11.6 try to restart every single time, when I have connect the Raid 5 ("your computer was restart because of a problem"). I have to disconnect the driver to able to use the computer again. Panic Medic Boot report. "Third party kernel extension was preventing machine ......"

ReplyQuote
Posted : 29/10/2021 6:04 am
(@rdieringer)
Eminent Member

@softraid-support

I have a second boot drive (not yet updated from 11.6.1), but that's the one where sofdtraid won't launch (from an earlier message - the window opens and immediately closes with no error dialog or crash report).

ReplyQuote
Posted : 29/10/2021 7:47 am
(@softraid-support)
Member Admin

@zoli

This is a Thunderbay correct? Not USB?

ReplyQuote
Topic starter Posted : 29/10/2021 10:24 am
(@softraid-support)
Member Admin

@rdieringer

We are going to have to test a clean macOS X install.

Go to Disk Utility

Click your startup disk (internal) on left.

Click + volume and add an APFS volume.

name it clean Monterey or similar

Quit and shut down.

Hit the power key, then hold it down, go into recover mode.

Reinstall MacOS

Go trhough the boxes, then point it to the new volume

Do not import, use your same name/password, though for simplicity.

Go back to internet mode and under Secure Startup Utility, enable third party developers.

Run SoftRAID, install the driver and "Allow" OWC as a third party developer.

Now connect your enclosure. Does it work?

ReplyQuote
Topic starter Posted : 29/10/2021 10:28 am
(@rdieringer)
Eminent Member

@softraid-support

This is a Thunderbay 4. My environment is: new Mac mini with 512GB drive, untouched except for updating to 12.0.1 (this morning) and setting up a user (I did set security policy from security utility); my main boot drive (1TB) is in the first slot of the enclosure, with the raid drives in 2&3 and a time machine drive in 4. System of prior computer (using same boot drive) was Mojave, so I had to re-initialize that drive to install Big Sur. Raid was created with softRAID 5.xxx initially.

After updating the internal drive today to Monterey, I unzipped your 6.2 archive and dragged the folder to Applications. Tried to launch, but it quit as soon as the window opened, with no error messages. I did find this in my system log right after that: Oct 29 1104 Ricks-Mac-mini com.apple.xpc.launchd[1]: Coalition Cache Hit: app<application.com.softraid.SoftRAID.773003.773013(501)> [1481]

ReplyQuote
Posted : 29/10/2021 12:03 pm
(@softraid-support)
Member Admin

@rdieringer

What other messages are near this? Launch it again and capture the 4-5 lines above or below, if they seem even vaguely related.

I see some developers complaining about this error, I never saw it in testing, however. The references I saw related to Python, which we do not use in SoftRAID.

If you launch a second time, same behaviour?

ReplyQuote
Topic starter Posted : 29/10/2021 12:45 pm
(@rdieringer)
Eminent Member

@softraid-support

2021-10-29 1455.009988 (pid/1137/com.apple.WebKit.WebContent.Development) <Notice>: internal event: PETRIFIED, code = 0
2021-10-29 1455.009992 (pid/1137/com.apple.audio.Core-Audio-Driver-Service.helper) <Notice>: internal event: PETRIFIED, code = 0
2021-10-29 1455.009996 (pid/1137/com.apple.WebKit.Plugin.64) <Notice>: internal event: PETRIFIED, code = 0
2021-10-29 1455.010000 (pid/1137/com.apple.audio.Core-Audio-Driver-Service) <Notice>: internal event: PETRIFIED, code = 0
2021-10-29 1455.010004 (pid/1137/com.apple.quicklook.externalSatellite.arm64) <Notice>: internal event: PETRIFIED, code = 0
2021-10-29 1455.010037 (pid/1137 [SoftRAID]) <Notice>: cleaning up
2021-10-29 1455.010042 (system) <Notice>: removing child: pid/1137
2021-10-29 1455.011511 <Notice>: Flushed 26 logs [limit: 20]
2021-10-29 1455.010805 (gui/501/application.com.softraid.SoftRAID.773003.773013) <Notice>: removing job: caller = runningboardd
2021-10-29 1455.010808 (gui/501 [100005]) <Notice>: removing service: application.com.softraid.SoftRAID.773003.773013
2021-10-29 1455.010941 (gui/501/application.com.softraid.SoftRAID.773003.773013) <Notice>: internal event: PETRIFIED, code = 0
2021-10-29 1455.010943 (gui/501/application.com.softraid.SoftRAID.773003.773013) <Notice>: job state = removed
2021-10-29 1405.668208 (system/com.apple.newsyslog) <Notice>: internal event: WILL_SPAWN, code = 0
2021-10-29 1405.668277 (system/com.apple.newsyslog) <Notice>: service state: spawn scheduled
2021-10-29 1405.668282 (system/com.apple.newsyslog) <Notice>: service state: spawning
2021-10-29 1405.668663 (system/com.apple.newsyslog) <Notice>: launching: xpc event

ReplyQuote
Posted : 29/10/2021 1:36 pm
(@softraid-support)
Member Admin

@rdieringer

Brand new to me. I won't hear back from engineering for several days, unfortunately.

You can try a manual removal in terminal, then install again:

 

How to manually Remove/uninstall the SoftRAID driver and components:

Paste each command line below into the terminal application. You will need your normal admin password for some steps.

Delete the SoftRAID driver:
sudo rm -r /Library/Extensions/SoftRAID.kext
sudo touch /Library/Extensions
sudo kextcache -fu /

Now, Restart your computer

Remove the daemon and SoftRAID Monitor:
sudo rm /Library/LaunchDaemons/com.softraid.softraidd.plist
sudo rm /Library/LaunchAgents/com.softraid.SoftRAIDMonitor.plist

Remove the SoftRAID application support directory:
sudo rm -r /Library/Application\ Support/SoftRAID

Remove all the SoftRAID preferences:
defaults delete com.softraid.SoftRAID

Remove preference files
sudo rm -r com.softraid.com

reset the extensions caches:
sudo kmutil clear-staging
sudo kextcache -i /

Restart the Mac. SoftRAID volumes will no longer mount on the desktop, but that is temporary, until you reinstall the driver.

When you run SoftRAID to install the driver, do not immediately restart. wait until the dialog box pops up to go to System Preferences/Security. "Allow" OWC as an Identified developer, now restart later when you quit System Preference, go to SoftRAID and restart.

 

 

 

ReplyQuote
Topic starter Posted : 29/10/2021 4:28 pm
(@rdieringer)
Eminent Member

@softraid-support

Did all of that. After the driver is installed, System Prefs NEVER presents the dialog to allow OWC as an identified developer (as noted in several of my other posts earlier in the week). That's because my System Report already shows OWC as an identified developer. Just as has happened for the past nine days, the driver is installed but never loads on boot. Tries to load it thru the terminal also fail. Now I have to try the above on my internal boot drive (the one where softraid won't launch). After over a week of struggling with this, if I have no luck there, I'll need to know how to split the mirror without a driver loaded.

ReplyQuote
Posted : 29/10/2021 5:02 pm
(@rdieringer)
Eminent Member

@softraid-support

I just ran all the terminal commands on my clean internal boot drive (most reported item not found because I never was able to install softraid). After rebooting, tried to launch the application but it immediately quit as before.

ReplyQuote
Posted : 29/10/2021 6:17 pm
(@softraid-support)
Member Admin

@rdieringer

My experience is every driver update and uninstall/reinstall means you need to "Allow" OWC again, each time.

Lets delete a couple old printer drivers that are < 5 years old. Paste these into terminal:

 

sudo rm -r /Library/Extensions/BJUSBLoad.kext

sudo rm -r /Library/Extensions/CIJUSBLoad.kext

sudo kmutil clear-staging
sudo kextcache -i /

Reinstall SoftRAID and see if you get the "Allow" option now.

ReplyQuote
Topic starter Posted : 30/10/2021 2:11 am
Page 6 / 10
Share:
close
open