Kernel Panic on older Intel Based Mac with Ventura

Thanks, and "perfect". I wll see if we can start capturing panics in this folder.

Will there be a fix in the upcoming release, and is there anything else that I can do to expedite a fix?

@soluwalana 

This is appearing to be a MacOS kernel issue. We have not heard anything whether it is being worked on, but we asked it be investigated.

If you are not pulling cables during copy, however, you do not get the panics?

No. I don't see panics unless unplugging during a data transfer, it seems to be pretty stable otherwise.

@soluwalana 

Interesting, that is good news, there may be a hardware component to this panic. I have not been able to reproduce it in our lab.

Should I start a replacement for the enclosure?

@soluwalana 

Its highly unlikely to be the enclosure, this is not a typical symptom. I think it would be a waste of shipping. there are no other symptoms.

Here is a simple test. Plug it into a different port on your Mac. Example if on top, plug it in back, etc. Any change in behavior?

I've tried it on everyone of my employee's macbooks (all intel based, 4 different machines). 

It kernel panics on each one, consistently.

I've also tried it in each of the 4 different usb-c ports, the behavior is very consistent. This is occurring between versions 12.4 and 13.5, as those are the versions on the macs that we have.

If you'd like to set up a Facetime or zoom, I can show you

@soluwalana 

We need to try two things. One may not be possible, can you delete the volume? (test with no volume, then create a new volume, it should not panic) no volume gives you a control Creating the volume again, tests against a file system issue.

13.5 fixes most all of the kernel panics, especially all of the "easy to reproduce" ones. I still see some "kernel data abort", or "watchdog" panics, but not anything generic. if this is happening across computers, chances are, something in the volume is damaged and causign the crashes.

If the enclosure is damaged, symptoms would be no disks, powering down, perhaps disks ejecting, not kernel panics. So I have to guess at the moment, this is a volume issue. Are you able to test that?

So to make sure I'm on the same page for the test instructions, you want me to delete the volume, but then how would I start a transfer of data to it?

@soluwalana 

This is a "destructive test". You have a point, I was not thinking this was triggered by data copying, not just connecting the volume.

Here is something you can do. Create a 4 drive RAID 0 volume. See if it panics on copy. Then "convert" to Apple RAID, if it does.
use this beta of SoftRAID to convert: softraid.com/sr_beta

it will support APFS or HFS volumes.

If it does not panic copying on RAID 0, delete it and create another RAID 5 volume and see what happens. thanks for your patience. Random panics like this issue are hard, as there is no experience to fall back on.

I'd guess this is triggered by mac trying to resume a data transfer or something along those lines. The panic only occurs when the transfer is interrupted. 

So to confirm:
- delete my raid array
- create a RAID 0 array with 4 drives
- attempt test

- create a raid 4 with 4 drives
- attempt test

When the panic happens
- convert the raid 0 array to apple raid
- retest

- convert the raid 4 array to apple raid
- retest

- delete raid arrays and recreate as RAID5 
- convert to apple raid
- retest

Is that correct?

@soluwalana 

Not quite:
create a RAID 0 new SoftRAID volume.

test. if it does not panic, then create a new RAID 5 volume and test.

report

If the RAID 0 panics, then use "convert" to convert to an Apple RAID 0 volume and test.

report

(if your RAID 0 is HFS, SoftRAID can convert. if APFS, use the beta I gave a link to)

let me know