[Sticky] Big Sur on M1 machines and SoftRAID issues
Make sure you download SoftRAID from this machine, not copy it over.
The driver appears to be blocked by OS X. Go through the steps here and see if it helps
(they are slightly different, but you will be able to follow)
I am running an HFS+ volume in a Thunderbay 4 in Raid 1+0. Currently my Mac completely crashes whenever I plug it in on the current beta. I'm not sure if this is what is happening with other 1+0 volumes, or if there's anyway to get it semi functioning.
I get this message when trying to change security properties... my Mac mini m1 won’t 4tb thunderblade won’t mount I previously have footage on the drive from a intel Mac but I want to work on the footage on my Mac mini but the drive won’t mount to the desktop. I see it in soft raid but it doesn’t show on the desktop... once I’m able to mount and do my work again life will be at ease again.
@softraid-support I have tried the forwards and backwards. I have tried going back to the previous beta, and doing this. I have uninstalled, and reinstalled, numerous times, doing this. I can no longer get my system to ask for the OWC extension permission, and I can no longer get my drives to mount.
I plan to do some testing today on my M1. I have another enclosure and a few spare disks to test to see if migrating was a cause of any issues.
Per my other post, I cannot get the driver to load properly on my Mac mini but it seems others have. Any idea why when I tried to load the kext I get the error message:
Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e
That would suggest the wrong kext versions were installed for intel macs? Not sure how as I tried downloading the beta twice to be certain. And no blocked access under Security snd the app has full disk access. Once I can get the driver working I can do some testing.
Works on M1 MacBook Pro and Mac Mini, install hoops are unfortunate, but if it's a one-shot action, I can live with it.
However, the BigSur usage of my ThunderBlade 8T, using Raid0 on both Intel and M1 have showed very (extremely) slow mounting.
After reboot, it takes up to 5-10 minutes before 'some dust' settles it seems, and the disk is mounted.
Once mounted everything is great, performance seems in line with what would be expected.
Just a small question, I hear the SoftRaid app is not supporting APFS, but we can manipulate (format etc...) through Disk Utility?
Sorry cant edit my previous post but...i think i know why the error is being thrown up. The other Kexts that the installer includes in the /L/E folder are the 3 OWC kexts and the the one OWC plugin. All of those are x86. If I delete those and re-run a kextload it doesn’t fail. However, it also doesn’t complete and output that it loaded successfully. When I look under a system report, i can see that the softraid.kext is not loaded. Even on a restart a kext cache reload. Not sure what those other OWC kexts do but clearly they are causing issues. Any ideas or help to get the driver to load would be great. Then at least i can start testing the systems.
Yes I approved OWC as an identified developer when the dialog box came up, and there is at least one other third party extension running Rogue Ameaba's ACE. As to the "clean install" issue I had just installed the MacOS 11.2 beta. As part of my attempts to force the SoftRAID array to mount I used the SoftRAID uninstall feature (which reported a successful uninstallation), rebooted, ran SoftRAID and reinstalled the driver (this time I was not prompted to approve OWC), and rebooted once more. The results were the same SoftRAID sees the array normally but will not/cannot mount it. 🤷♂️
Make intentional errors —
Otherwise the Great Spirit
realizes you have fulfilled
your purpose on earth.
— Navajo saying
The OWC extensions are SMART USB drivers. Disable SMART USB in SoftRAID disk preferences. That should remove them. I will investigate this, they should not cause a problem, but perhaps...
Sorry, I confirmed this in further testing that HDD"s with RAID 1+0 are causing a kernel panic. interestingly, SSD media does not. We will work on this and get a new beta out ASAP, but it may take until Friday.
I don't see your error message. What does it say?
Run this command in terminal.app:
sudo kextstat -b com.softraid.driver.SoftRAID
It should show B46 loading.
Next check SoftRAID and see if in the volumes tile, a Disk Identifier is present, or if it shows only a -