Running 6.2 and Monterey 12.0.1
Running SoftRaid and Thunderbay 4 Mini HAS worked.
But it's also crashed and restarted my laptop on an endless loop several times.
When I unplug the Thunderbay, the crashing stops.
Today, every time I try to plug the Thunderbay in, the computer begins to crash endlessly.
Attached a report from SoftRaid
Support file was not attached and I think the panic you reported is not connected here.
This appears to be the Thunderbolt bus crash we are working on.
We are swapping out a system with a user with this problem, so we have an example we can bring into Apple engineering.
If you remove exactly one disk to your volume from your enclosure, I suspect the system does not crash, correct?
I haven’t tried. This is my first time with a RAID system.
Is there any risk to the data on the disks removing the single drive?
Attached the file below.
Removing the disk means you do not have "parity" protection, but there is no actual risk to the data.
Make sure your backups are up to date (or update them!)
If it lets you use your system until we can all get this figured out, though, it gets you past the worst.
Just as an additional data point, I attempted to use the RAID on my M1 Air running Monterey.
As soon as I updated SoftRaid to 6.2 and had the Thunderbay Mini connected, the endless crashing began again.
Please remove one drive, until we can figure this out. I expect we will get an example failing computer this weekend.
I can confirm that if I don't have my laptop plugged into its power supply, the Thunderbay 4 Mini mounts (with all 4 drives), works and does NOT crash my system.
We received a users system and have started testing. So far, I can confirm this is not caused by the enclosure. It is a System problem. We are testing multiple clean macOS installs next. (that is time consuming) So far, it appears to be a problem in the specific System folder on the host machine.
When we have enough information we will be working with Apple on getting this fixed.
I don't know if this helps, but through Terminal I was able to screenshot this "Incompatible architecture: Binary is for x86_64, but needed arch arm64e". See attached. Running M1 Max with latest Monterrey and Thunderbay 8. Looping crashes.
Over the weekend, I identified the trigger, not the cause. If you change your RAID level to RAID 4, the crashes will go away.
Also, a clean system install will fix this, but since the problem is clearly caused by something inside macOS, its possible it is a third party app triggering this, rather than a setting or something in macoS. A third party installation would most explain why we see such a low percentage of users with this issue. Its too early to tell, but now we have the hardware to dig deep.
this will be a high priority to get the information we are learning to Apple engineering, so a fix (from us or Apple) can be identified. But it is much more promising now.
@softraid-support. Here is the kernel panic report in the event that it helps you figure stuff out.
panic(cpu 1 caller 0xfffffe001f12ac98): busy timeout[0], (60s): 'Untitled 4' @IOService.cpp:5520
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 21A559
Kernel version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 3B2CA3833A09A383D66FB36667ED9CBF
Kernel UUID: 67BCB41B-BAA4-3634-8E51-B0210457E324
iBoot version: iBoot-7429.41.5
secure boot?: YES
Paniclog version: 13
<snip>
last started kext at 1041546149: com.boxcryptor.BCFS.filesystems.bcfs 2081.20 (addr 0xfffffe001df5c000, size 6240)
loaded kexts:
com.boxcryptor.BCFS.filesystems.bcfs 2081.20
com.softraid.driver.SoftRAID 6.2
<snipped to save space>
this is a totally different panic. When does this occur?
this appears to be caused by boxcryptor, it is in the backtrace, and the last kernel extension executed.
This crash is unrelated to the M1 problem we have been tracking.
@softraid-support. You are right looking at it. I just replicated the same results. Truncated panic report below. Odd thing is that Boxcryptor is not on or touch any data on the Thunderbay. Also odd is that this exact same software setup works perfectly on my Intel-based Macbook Pro. I mirrored the laptops complete with Boxcryptor, Softraid 6.2 etc. What I can attempt to do is temporarily remove Boxcryptor from the M1 Max MacBook Pro and retest. This will be quite involved, unfortunately.
@softraid-support. The panic is now happening on an Apple driver rather than Boxcryptor. Why can't we attach PDFs for you in this forum? Sorry to dump so much data here.
In the Apple discussions there is a similar panic, but not caused by boxcryptor, caused by Symantec
https://discussions.apple.com/thread/253180195
Maybe it is worth posting this panic to the discussion forums, but recently the quality of helpers on the forums seem to have dropped dramatically.