[Sticky] Monterey Crash/kernel panics

I've had a LOT of Kernel Panics trying to get SoftRAID & my ThunderBay 8 set up on my new Mac Studio (M1 Ultra, Monterey 12.3.1) and I think I'm almost through sorting most of them:

• I was getting the kernel panic on log in when my TB8 was configured in a RAID5 with 16kb stripe unit size... have reformatted to RAID5 w/64kb stripe unit size and that seems to have solved those crashes.
• I could not reformat the HFS volume in Disk Utility to APFS due to the driver not being allowed in Mac OS Security (and the prompt not showing). Had to remove and reinstall soft raid a few times to get this to work. APFS wasn't an option available in softraid when trying to create a new volume so it took ages to figure this out and then for some reason the APFS option suddenly appeared when creating a new volume, so did that and it worked fine.
• It also wasn't remembering that I had allowed SoftRAID full disk access and so was giving error messages saying the disk was in use. So I deleted softraid from the Privacy/Full Disk Access menu and manually re-added it, and that seems to have solved that one.

Now on to the next problem: Time Machine

I am experiencing crashes/kernel panics whenever time machine tries to run. I have a RAID5 volume in APFS format ready to go for Time Machine, but it crashes every time it runs so I have turned it off for now.

Below is the output from the error log:

panic(cpu 1 caller 0xfffffe0013eb3400): "dart-apciec1 (0xfffffe1b33498800): DART(DART) error: SID 1 read protect exception on read of DVA 0x8017b000 (SEG 0x40 PTE 0x5e) ERROR_STATUS 0xa0100020 TIME 0x24661d4e08 TTE 0xc1f10c3297801 AXI_ID 0" @AppleT8110DART.cpp:1725

@jjdodders 

Does it crash when you connect the second volume? Or when Time Machine launches?

This is the same panic as the M1 we have been seeing (DART controller)

@softraid-support Both volumes can connect just fine and everything seems to run ok until the time machine backup begins. I can open the time machine preference pane and change settings etc and it'll be ok, its just when the backup begins is when it loses its marbles. Backup only includes stuff on the Macintosh drive and nothing else (so not backing up other volumes on the TB8). The Time Machine volume is also a RAID5 with 64kb stripe unit size, so I'm guessing that work around doesn't work for this one. Might be to do with it being APFS and the other volume being HFS+? Is this going to be a case of waiting for Apple to sort that panic out then?

@jjdodders 

It does not have to do with the APFS/HFS mix. It must be something Time Machine is triggering. Its running late for Apple to fix this in Monterey, so it must be targeted at fixing in 13.x whatever that will be called.

Maybe use Carbon Copy Cloner in the meantime? It has archive and incremental backups and is pretty fast.

Guessing I'm in the same boat as everyone else, but here goes.

Dual Thunderbay 4 Mini's running RAID5 across them both. Just upgraded to Mac Studio, SoftRAID is the first thing installed, and it panics within 1min of drives being plugged in.

I can't find where to change stripe size, so I'm guessing it'd be a case of wiping and starting from scratch - don't have the option as disks are already populated.

@noggin2k1 

The trick with text edit is "make plain text", then it will be a actual text file.

Yes, changing the size means deleting and recreating the volume. Or you can wait 5 minutes before connecting the volume, which mostly avoids this for users.

M1 pro macbook pro, thunder bay 6, bay 1-3 raid 5 , bay 4 -6 non raid and M2 slot 2tb. i post it before, but still got the watchdog panics. often happen within 5 mins.  

@vincent-chu 

If you unmount the volume before shutdown, you should not get the panic. Correct?

Watch the lights on the enclosure at shutdown, each disk will light, one at a time. Does one seem to take a lot longer than the others?

Add me to the list of "pink screen of kernel panic" folks. This is preventing me from earning income in my studio, as NOTHING can be loaded from the drives. Attached text file may be of help, but I think it's the same issue others are experiencing. Any progress available from OWC? I've fully removed SOFTRAID (following the long instructions posted in this thread), reinstalled, and am having the same issue. What can I do to get this array to mount successfully? I'm not willing to reformat the drives, as it is my expectation that having a MIRRORED array would provide resilience.

@jhendow 

I need more information, as there are no panics with RAID 1.

Attach a panic log (report to Apple, copy/paste the text into text edit, "Make plain text" and save)

Also attach a SoftRAID tech support file.

@softraid-support 

I can't seem to attach the file in either .txt or .doc format. Here is the text itself:

Remember to "make plain text" in text edit. Else the file is secretly named .txt.rtf

@softraid-support 

And here is the tech support file.

@jhendow 

the SoftRAID driver is not loading.

Please confirm:

Did you do this?
https://support.apple.com/en-lk/guide/mac-help/mchl768f7291/mac
Select reduced security and enable this:
Select the “Allow user management of kernel extensions from identified developers” checkbox to allow installation of software that uses legacy kernel extensions.

Now you need to reinstall the SoftRAID driver.

After enabling third party extensions, reinstall the SoftRAID driver, (do not immediately restart) and go to System Preferences / Security to "Allow" OWC as an identified developer.

Also, you should navigate to System Preferences/Security/Privacy/Full Disk Access and enable full disk access for SoftRAID.

to the panic, I don't recognize it. Can you call Apple on this?

It is not SoftRAID, I am pretty certain. The backtrace seems to point to these:

Panicked task 0xfffffe24cd030728: 247 pages, 4 threads: pid 137: watchdogd
Panicked thread: 0xfffffe20018c4140, backtrace: 0xfffffe6094c9b4b0, tid: 2369

Watchdog is a timer.

What's odd is the SoftRAID driver is shown as loaded in the panic log, but it is not loading in your support file.

@softraid-support 

I have followed your recommended steps. I am getting the same result. Two of my three volumes appear to mount, but the third one does not. Within a few seconds, the systems goes to a pink screen crash, with a cycle of reboots until the OS disables third party extensions. Once that is done, SOFTRAID recognizes all three volumes, but cannot mount any of them because their extension has been disabled. This first occurred a few weeks ago, and I cannot access anything on my external disks. Should I reinstall Monterey?