[Sticky] Big Sur on M1 machines and SoftRAID issues

Guys, please think. The behaviour is different.

Before, the driver did not load. There was no popup at all.

Now, there is a popup saying that the developer OWC has to update the driver

So again, I think Apple did change something, possibly fixing the problem. But OWC need to sign the driver in order for it to work. That should be a pretty easy thing to do if everything else works.

@sunstarfire

I do not think you are correct. Paste the output to this command in a response, I can confirm it is the same bug:

sudo kextload -v 6 /Library/Extensions/SoftRAID.kext

@softraid-support

% sudo kextload -v 6 /Library/Extensions/SoftRAID.kext
Password:
Kext user-space log filter changed from 0xff2 to 0xfff.
Kext kernel-space log filter changed from 0xff2 to 0xfff.
Kext library architecture set to arm64e.
Executing: /usr/bin/kmutil load -p /Library/Extensions/SoftRAID.kext
Error Domain=KMErrorDomain Code=31 "Error occurred while building a collection: 
    1: One or more binaries has an error which prevented linking.  See other errors.
    2: Could not use 'com.softraid.driver.SoftRAID' because: Failed to bind '__ZN18IOMemoryDescriptor16setPreparationIDEv' in 'com.softraid.driver.SoftRAID' (at offset 0x128 in __DATA_CONST, __got) as could not find a kext which exports this symbol
com.softraid.driver.SoftRAID specific: 
    1: Failed to bind '__ZN18IOMemoryDescriptor16setPreparationIDEv' in 'com.softraid.driver.SoftRAID' (at offset 0x128 in __DATA_CONST, __got) as could not find a kext which exports this symbol
" UserInfo={NSLocalizedDescription=Error occurred while building a collection: 
    1: One or more binaries has an error which prevented linking.  See other errors.
    2: Could not use 'com.softraid.driver.SoftRAID' because: Failed to bind '__ZN18IOMemoryDescriptor16setPreparationIDEv' in 'com.softraid.driver.SoftRAID' (at offset 0x128 in __DATA_CONST, __got) as could not find a kext which exports this symbol
com.softraid.driver.SoftRAID specific: 
    1: Failed to bind '__ZN18IOMemoryDescriptor16setPreparationIDEv' in 'com.softraid.driver.SoftRAID' (at offset 0x128 in __DATA_CONST, __got) as could not find a kext which exports this symbol
}

@sunstarfire

thanks, this confirms it is the same issue and the driver cannot be loaded. It is not "correctable" on our side.

@softraid-support *sigh* And there was me hoping you could, since it would have been faster than to wait for Apple :(

Fwiw, I have seen some other methods on here about downgrading. In my case, I didn't have any snapshots so I needed to do a full system restore. But I was able to downgrade without losing my data, apps etc by doing the following steps below. I haven't seen anyone mention it but if its a repeat post, mods feel free to remove it. This got me back go 11.1 so I could get my SOFTRAID working again.

1. Used Carbon Copy Cloner to create a data backup of my current 11.2.1 system onto an external drive

2. Downgraded using the MrMacintosh method (downloading 11.1 IPSW, putting my M1 Mac into DFU mode, restoring clean back to 11.1

3. Upon startup of new 11.1 system, migration assistant asks if you want to restore; selected yes and then pointed it to my external drive.

4. MA restores all my files, apps, and data

5. Rebooted into recovery to set the security policy back to reduced allowing kernel extensions

6. Started up system, went through prompts to set up new machine (its not a clone so you will need to go through some initial setup). Also had to allow some extensions under Security, including OWC. SOFTRAID successfully loaded my RAID array.

Back in business.

@mushbuddygoose

Thanks. It has been mentioned that if you upgraded to 11.3, the system auto updates again if you use your method. What version were you running when you went back to 11.1?

@softraid-support "I did believe 11.3 beta 2 was going to fix this." Right, I believe in a lot of things too, doesn't mean I claim them too be true It sure doesn't increase trust in your product that you did. What confuses me even more is when I see that you seem to rely on customers on this forum to inform you that the latest beta once again fails to load the driver(s). Seems even less assuring that even though this issue is now going on for weeks you don't even test out new beta versions yourself... As stated in your support email you just sent me you don't actually have the slightest clue when this is going to be fixed. Could be weeks to come. Not one of my drives doesn't work on my M1 running Big Sur, except the most important and expensive one. Never again OWC is all I can say about this. 

@softraid-support interesting. I was on 11.2.1.

What do you mean auto updates? After you install 11.1 it then upgrades to 11.3? Or it doesn't let you install 11.1?

This is exactly what I did to revert to 11.1 from 11.2.

@softraid-support no such option. I see my drives in the app but they won’t mount.

If after reverting back to 11.1, you disable all the auto-updating options in Software Update system pref, does that keep any later system updates from completing?

In my case (on my M1), when 11.2 first came out, I started the download to do the update. But literally a few minutes later I saw the message on this forum that 11.2 breaks Softraid, so I immediately cancelled the download and then made sure all the auto update selections in the Software Update pref were turned off (including in the Advanced section). Later, I was able to do shut downs/power ups and restarts after this and my system still remained on 11.1. Also later, I started up the Softraid app (b48) and noticed that there were 2 Mac HD volumes showing, one with 11.1 showing a startup status, and another showing 11.2. See the attached screenshot below (note: I didn't have any Softraid volumes connected at this time).

Does this mean the 11.2 download completed later and was just sitting there ready to startup to 11.2 if I requested a restart on the Software Update system pref? Maybe @SoftRAID-Support can say?

I just thought I'd mention this in case it helps others who revert back to 11.1, and doing what I did with disabling all auto-updates will keep their system from updating to 11.2/3.

Thx.

pruthe

@schmollywood

You completely misunderstand. We cannot, because of Apple NDAs discuss any confidential problem, until it is mentioned by a customer on the forum, or other public place. Its not our choice.

This is a very embarrassing issue, and one we cannot offer a fix to. We must wait until Apple fixes this issue.

And while we test versions of course, we must ask users to write about their results first. We are registered developers and want to keep a good relationship with Apple.

And when the next beta is released, we will ask users to to comment again, so we can then discuss it.

@pruthe

Very good point, I am not sure our documentation points out (clearly enough) the need to disable auto updates.

The concern one user pointed out was after updating to 11.3 beta 2, going back to 11.1 did not work. I have not tested that scenario yet (11.3b2 -> 11.1), as it requires wiping the computer and I currently have 4 different systems on it for testing. And my other M1 machine is doing a long term test right now.