I am posting a beta of 6.2.1 b3 that will fix the kernel panics on M1. I would like to know if it also fixes your panic (inadvertently)
http://www.softraid.com/sr_beta
Let me know either way
Its likely the 6.2.1 b3 beta fixes your panic issue. Please try it and report back:
Please try the current SoftRAID beta version:
http://www.softraid.com/sr_beta
My recommendation is Uninstall SoftRAID. restart and run SoftRAID and install the driver. before restarting, go to System Preferences/Security to "Allow" OWC as an identified developer. this ensures that macOS actually loads the new driver version.
We believe this beta will fix your problem.
Try the latest beta version and report back, please:
http://www.softraid.com/sr_beta
My recommendation is Uninstall SoftRAID. restart and run SoftRAID and install the driver. before restarting, go to System Preferences/Security to "Allow" OWC as an identified developer. this ensures that macOS actually loads the new driver version.
Spinning up with laptop power attached!
I'll put it through some paces and report back.
Encouraging start.
@softraid-support Thanks! SoftRAID starts up as expected; all disks and volumes appear and mount. I'll continue to test, but it looks good so far. Thanks again!
@softraid-support After a promising start, no joy.
The 6.2.1 b3 driver installed fine and shows at the bottom right of the SoftRAID window. When I plugged in the two ThunderBay 4 units (Thunderbolt 2 via Apple TB3-TB2 adapters), it seemed to run fine, showing and mounting all the disks/volumes. FYI: I also had an NEC EA244UHD daisy-chained to one TB4 (Thunderbolt 2 to DisplayPort cable) and an OWC Drive Dock (Thunderbolt 2) daisy-chained to the other (Thunderbolt 2 to Thunderbolt 2 cable) and an OWC Thunderbolt Hub attached to the third Thunderbolt port on the MacBook Pro.
All subsequent reboots were unsuccessful (repeated reboot cycle) unless the two ThunderBay units were disconnected. Connecting only the ThunderBay units (no daisy-chained devices) still results in a reboot cycle. I've attached a support file.
At one point, after several reboot cycles, I received a system error message saying that a third party extension signed by OWC had caused a problem with startup and asking me to reactivate it in System Preferences > Security, which I did.
After a successful startup, if I plug in the two ThunderBay 4 units, they startup, and SoftRAID briefly displays and mounts the disks/volumes before the machine restarts.
If you plug in just one disk (so it does not panic) and paste this into terminal, what driver version loads?
sudo kextstat -b com.softraid.driver.SoftRAID
@softraid-support I forgot to mention that I did try plugging in just one TB4 unit (with 4 disks) and it still panicked.
To clarify, were you asking me to plug in one TB unit - or one unit with only one drive installed?
@softraid-support FYI: here's what I see without any external drives plugged in:
Executing: /usr/bin/kmutil showloaded --bundle-identifier com.softraid.driver.SoftRAID
No variant specified, falling back to release
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
Just one disk. The reason you are getting blank result is there is no disk to trigger the SoftRAID driver to load.
@softraid-support Great time to not be able to find the keys to the TB4 units – I moved a year ago. Arghh. I just ordered a replacement set...
@softraid-support Sorry for the delay. I had to wait for my replacement keys to arrive.
With one drive in the TB4 unit, there is no panic. Here's what I see in Terminal:
Executing: /usr/bin/kmutil showloaded --bundle-identifier com.softraid.driver.SoftRAID
No variant specified, falling back to release
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
267 0 0xfffffe0006e98000 0x4000 0x4000 com.softraid.driver.SoftRAID (6.2.1b3) 23E46A8B-78DA-31E2-B284-6AC9381251B2 <16 5 4 3>
@softraid-support FYI: I noticed in another thread that you seem to have narrowed the issue to RAID 5 volumes. I can confirm that I have one RAID 5 volume among the volumes on the two TB4 units.

