[Sticky] Running Big Sur (beta) on Intel Macs
Post a SoftRAID Tech Support file. This should not be the case.
Can you both attach SoftRAID Tech Support files?
I am glad you can find humor in comments such as those by 23WOMe. I'm sure I am one of many who appreciate your work. I can imagine the complexity of creating a driver for RAID systems, and understand that it isn't possible to test all the various configurations of computers in which it will be used. I greatly appreciate that you have been keeping us informed as well as being very responsive to the very many posts which are coming in. I notice that you have been posting on the 26th and 27th - which is admirable.
@softraid-support yes this is the error I get coming out of sleep. wouldn't it be possible for you to identify disks based on a serial number or something more permanent and remap the numbers if they change? As a driver I would think you are operating at the level these things could be fixed on your side until apple gets around to figuring it out.
Since disabling the notifications and not running my RAID-based VM I do not get any panics, reboots, or errors. The logs also don't show any issues. So it seems this only happens when those monitor prefs are enabled and something about having open sessions on a disk through a sleep causes system crashes.
All IO is controlled by the IO registry. There is no way around it without writing a complete kernel driver. We piggyback on OSX's low level driver, and SoftRAID acts like a traffic cop, directing traffic (IO) from disk to disk. We do this for compatibility reasons, and others. I have been told when asking this question, not possible. I am not an engineer/programmer, so cannot articulate why.
We are going to investigate whether there is a bug in Monitor sending "false alarms", but if you disable Monitor, there can be no alerts, the Monitor is what talks to the driver and sends events up to userland.
And 25th! ;-)
(and of course we will be here on the 31st/1st!)
I don't think I have missed a day of support in 25 years.
It has been hard recently, as the forum is an awkward way to manage issues, but informative for users. it is also a place to find similar problems.
Thanks for the feedback!
If you are referring to the intel issues with b47, when we figure out what changes when the M1 code is added, when building a driver. There must be a bug in there somewhere. I do support, not engineering. Hopefully by new years, but it can take time to debug something like this.
@softraid-support right, disabling the monitor I get no errors and things still seem to work. enabling it with default notifications it throws these errors coming out of sleep that cause me to reboot even though it seems all volumes are showing as without error in the monitor. disabling the notifications seems to also work fine and logs show no errors. I think there is a bug in the monitor coming in and out of sleep perhaps with drives over thunderbolt that don't themselves come immediately out of sleep or some sort of race condition around that.
Currently running B43.
Any idea when a newer (stable) beta will be available?
Can we have a 'final' release for intel based systems at least?