@softraid-support I feel that this is my only hope at this stage. I'm actually getting new kinds of panics I haven't had before on current MacOS. I start each of my disks separately and power on monitor after everything has ran for a bit, previously this resulted in my system never panicking. Now even after doing this I have a disk that I can hear revving up and revving down and eventually getting a disk degraded warning followed by a disk disappeared warning and then track pad locks up and panic occurs. This log is an example of this,
You are one of the users getting kernel panics with M1, correct?
If you are interested in running Ventura (beta 3 as of this writing) and testing whether it fixes your panic, your feedback will be appreciated.You will need to install this beta for Ventura. (Note: the release version of 6.3 probably will not support Ventura, but a new compatible beta will be released)
http://www.softraid.com/sr_beta
Installed Ventura and installed 6.3 b20 and this is the error I'm getting every time I open SoftRaid
I think if you have no disks connected when you launch SoftRAID, then connect the disks you can get around this.
this was introduced in beta 3. We reported this to Apple of course.
there is a second bug where "the installation of the SoftRAID driver failed", even when it succeeded. As long as the "Allow" OWC is set before restart the driver will load normally.
its a beta of MacOS. It may be a while before it is solid.
SoftRAID is in the backtrace on this one. Can you send a SoftRAID tech support file, so I can enter this as an issue in our bug database?
thanks!
So, was editing in FCP. MacBook had been running for hours with no issues. Out of the blue trackpad quits working and FCP freezes and seconds later panics. I'm attaching the report from that panic. Will try to get you tech support file after that.
I am not a backtrace reader, but looking at this:
panic(cpu 2 caller 0xfffffe0021135b14): IOGMD: not wired for the IODMACommand @IOMemoryDescriptor.cpp:3243
This type of panic has been around for at least 8 years.
Looking at the backtrace...
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[7178BA06-C0B4-3163-9237-240AD6E71801]@0xfffffe0022bffce0->0xfffffe0022c544df
dependency: com.apple.driver.AppleA7IOP(1.0.2)[CC3A6AA9-CA7F-3FF7-B91E-B4A9E6AE85CA]@0xfffffe00212e1670->0xfffffe00212f0393
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[12D5CDCA-8B0E-3783-8FEC-D4761DA26B1E]@0xfffffe002138ea20->0xfffffe00213d90bb
dependency: com.apple.driver.AppleEmbeddedPCIE(1)[65615DAA-4AAB-3B53-AA86-98701916A8AA]@0xfffffe002194e510->0xfffffe002195e7ef
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A9F6E230-0390-32A4-AFED-C6D734A41B54]@0xfffffe0021d02430->0xfffffe0021d1d22f
dependency: com.apple.driver.AppleNANDConfigAccess(1.0.0)[6591C965-89F5-33DA-ACF6-5B16E1011ED9]@0xfffffe0021d3d360->0xfffffe0021d3d757
dependency: com.apple.driver.AppleSMC(3.1.9)[C40B8D99-1CA6-34CC-ABB5-697F1CB8934F]@0xfffffe0021eb62e0->0xfffffe0021ee630b
dependency: com.apple.driver.IOSlaveProcessor(1)[206F0379-18EC-37F2-9D8E-9F7EFBE576AB]@0xfffffe0022db33e0->0xfffffe0022db4d33
dependency: com.apple.driver.RTBuddy(1.0.0)[30A37BB3-D620-3827-8C49-6653D9137882]@0xfffffe00232af1d0->0xfffffe00232e7d6f
dependency: com.apple.iokit.IOHIDFamily(2.0.0)[DBE59A21-AB88-3A0E-939E-92CB75B71D33]@0xfffffe0022afbe20->0xfffffe0022b7ee33
dependency: com.apple.iokit.IOPCIFamily(2.9)[9AE720E5-D48E-39CB-8B0C-3A396D2E18E5]@0xfffffe0022cde2a0->0xfffffe0022cfcb63
dependency: com.apple.iokit.IOStorageFamily(2.1)[2912B6A9-2D4A-35E7-8280-2EDE64A64E87]@0xfffffe0022db6e70->0xfffffe0022dd7a23
this appears to be either the internal drive?
SoftRAID is nowhere near this panic, from what I can tell. I don't know what to tell you.
Not sure how to read the panics but I don't see how this one here isnt soft raid. This one always occurs anytime I boot all of my disks at once.
This is the DART controller chip. Are any of your volumes RAID 5?
@softraid-support 4 of them are, only one that isnt is the PCIe SSD in my flex 8
Apple is fixing this finally in macOS 13, Ventura. You might be are a good candidate to try Ventura. But wait until we get a new beta, as Ventura is doing something weird and many users cannot get the application to launch.
For now, wait 5 minutes before connecting the drives.
@softraid-support Yes I downloaded Ventura on a separate partition and I couldn't get the program to launch, deleted for now.

