[Sticky] Big Sur on M1 machines and SoftRAID issues

@antonyrock

Thanks for the monitor output, that was to verify that the correct version of Monitor is loaded.

@softraid-support

no blue light in menu bar

@antonyrock

Can you also run the console.app? Look in the crash logs, diagnostic report folders for a SoftRAID Monitor crash log. if you see it can you save it as a txt file and attach it?

@softraid-support

please tell me in detail what I need to do? I sent you the logs already.

1. Open Files and ports. attach

2. attach

@antonyrock

Open the console.app.

There are various folders on the left,  look for crash logs for SoftRAID Monitor. Look in the crash reports, spin reports and diagnostic reports sections. If there are multiple, as likely, just use the file menu to "reveal in Finder" to get to it. You can rename it .txt to post it.

@softraid-support

I understand nothing.. what folders are you talking about, where on the left..? You can normally write please. where are the report and diagnostic files that you need ? Write specifically and I will send them to you. please. I've already sent you a bunch of logs..

@softraid-support

This is just an FYI. I am now running macOS 11.5 Beta (20G5023d). my RAID array continues to work as expected. The app correctly reports the RAID format as APFS and continues to show the mounted array as unmounted and I am holding my breath waiting for you to announce that encryption is supported.

One question, that I could test for myself, but I would rather ask: Once the RAID drivers are installed can full security protection be turned on again without risk? To put it another way, is reduced protection only needed when installing and updating the SoftRAID drivers?

@joemikeb

We will be adding APFS support in SoftRAID 6 application in 6.1.

On M1, any third party driver must run under "reduced security", that is by design. Apple intends to fix this soon, in macOS 12 or 13, we have to wait for the developers conference. Its highly likely that "driver kit" will be announced/released in beta, but not functional until macOS "13". All drivers are being moved out of the core installation when this happens.

If you are on intel, there is no need to run "reduced security", that was a Catalina limitation, fixed in Big Sur.

Hope this helps.

@antonyrock

Run the console.app

On the left side are "Reports", that when clicked on, show the log files in them. When you click on one, it can display the crash below.

What I am looking for are SoftRAID Monitor crashes. (dated when you ran SoftRAID)

On Big Sur, they will probably be in "spin reports". but you should check crash reports and Diagnostic reports if you do not see any in spin reports.

@softraid-support

Thanks. That is exactly what I wanted to know.

@softraid-support

I was finally able to capture the before and after Tech Support Reports in the same log on session as lock up warning. Note the Array is still mounted

@softraid-support

Call me "picky" but, I just noticed an interesting quirk. The SoftRAID 6.0.4 app is inconsistently reports the format of the array. Sometimes it reports it as "unidentified" and more often it correctly identifies the format as "APFS". Am I correct in assuming that will be fixed in 6.1? I will try to grab Reports of each in the same logon session if that would help.

Add me to the list of people who have M1 Macs and kernel panic. Running 11.3.1, non beta. ThunderBay and Apple Thunderbolt 3 to 2 adapter. I have reduced security, allowed the driver and granted full disk access. I gathered the support files. This is the new iMac. Setup as new, and didn’t pull anything from backups. 

@joemikeb

Thanks, This will go to engineering.

@joemikeb

Yes, 6.1 should address all these issues. the next update, 6.0.5 will not address APFS in the user interface, it will be a minor update.