{"id":74237,"date":"2021-04-29T12:00:00","date_gmt":"2021-04-29T17:00:00","guid":{"rendered":"https:\/\/eshop.macsales.com\/blog\/?p=74237"},"modified":"2021-04-29T09:37:45","modified_gmt":"2021-04-29T14:37:45","slug":"macos-beta-no-longer-required-when-using-softraid-on-m1-macs","status":"publish","type":"post","link":"https:\/\/eshop.macsales.com\/blog\/74237-macos-beta-no-longer-required-when-using-softraid-on-m1-macs\/","title":{"rendered":"macOS Beta No Longer Required When Using SoftRAID on M1 Macs"},"content":{"rendered":"\n
\"SoftRAID<\/figure><\/div>\n\n\n\n

What Apple broke in macOS Big Sur 11.2<\/strong> <\/h2>\n\n\n\n

With the release of macOS 11.2, Apple introduced a bug in the kernel which prevented the SoftRAID<\/a> driver when running on M1 Macs.  While Apple had this fixed in a beta release of macOS about a month later, most users don’t want to run a beta version of an operating system on their Mac.<\/p>\n\n\n\n

\n\n\n\n

The fix is in<\/strong><\/h3>\n\n\n\n

The good news is that Apple has released the official version of macOS 11.3 to all Mac users. This version restores the ability to load the SoftRAID driver on M1 Macs. This bug was on M1 Macs only so the SoftRAID driver has been able to run on Intel Macs on all versions of macOS 11.2.<\/p>\n\n\n\n

\n\n\n\n

Why you might still have problems loading drivers with macOS 11.3<\/strong><\/h3>\n\n\n\n

There are still occasional situations where the SoftRAID driver doesn’t load on macOS 11.3 but this occurs on both<\/strong> Intel and M1 Macs. When this occurs, all third-party drivers are blocked from loading, not just the SoftRAID driver.<\/p>\n\n\n\n

Our Customer Support staff has determined that this happens when users have older drivers installed on their Mac. These drivers, often for older printers, are often unsigned and may even date back to 2007. These out-of-date drivers get copied over to your new M1 or Intel Mac when you use Apple’s Migration Assistant application. They can also exist if you updated your existing startup to macOS 11 rather than performing a clean install on a new startup volume.<\/p>\n\n\n\n

Prior to macOS Big Sur 11, the operating system would just skip insecure drivers and go ahead and load the rest normally. New with macOS 11, the kernel will encounter one of these insecure drivers and then just refuse to load all third-party drivers. I’m still not sure whether this new behavior is a bug or a feature.<\/p>\n\n\n\n

So, now it is up to the user to delete these out-of-date drivers manually before their system will work correctly.<\/p>\n\n\n\n

\n\n\n\n