[Sticky] Running Big Sur (beta) on Intel Macs
How close are we to the full final release?
Cannot say. When the User Interface elements are in place, we may be ready, depending on other factors. Its too early to predict.
Updated to latest 52 with one installation issue... after it installs and you must go to security and allow OWC again and then you update the driver the OS says it needs to restart for it to take effect however if you click restart in that popup it then errors out saying SoftRaid cancelled restart, 'try again' doesn't work. It seem you must first manually close the splash screen SoftRaid is displaying that has the 'don't show this on startup' checkbox in it which to be honest it should either default to off or remember that I unchecked that last time or even realize this window is unnecessary for an update since it was shown to the user before most certainly. In any case those popup windows should never cancel an OS restart. It is just a clunky experience for the update process.
understand and agree. this is on the list for UI enhancements. thanks!
Did you guys improve the beta pop-ups in 52 because I am still getting random pop ups daily.
No, unfortunately. Your SoftRAID Monitor must be crashing, as the beta should not be alerting daily.'What if you change the preferences for updates to "Never", just to see if it makes a difference?
not seeing any crashes in the logs...
Look in Console for "diagnostic reports" and browse looking for SoftRAID Monitor crashes. They won't be in the System Log.
Yep, nothing there either...
OK, not sure what I can offer then. I will try to find where to look.
just happened again...
Problem is I cannot replicate this in house yet. Whatever is broken in your case, does not happen on a clean system (which is what I test on). I need to reproduce it, so it can be fixed.
Just popped up again and I have been actively using the machine the whole time including audio actually playing from the external raid drive... no hiccups in the audio and SoftRaid didn't crash or anything. It just seems like you have a timer in your code that triggers the pop-up daily. If you think this isn't the case probably there is a branch of logic someone forgot to remove. Maybe just do a full deep dive code review of the popup code and you will find the weird edge case.
It does look like the monitor initiated a SMART test on all disks when it happened. Is the popup logic in the callback of this test somehow?
This is exactly what I would expect if either the driver or Monitor crashed.
Can you check console.app for any SoftRAID Monitor, or SoftRAID kext crashes?
(Probably in one of the diagnostic reports folders)