[Sticky] Monterey Crash/kernel panics
Still no news on RAID 5 support with M1 Macs ?
Text Edit is best. Use "make plain text" then save, and it will work. (the extension must be .txt)
I can post a blank file if you want, another user did and used that to post the panic.
Not really. We have one development, which is confirming that 64k stripe unit size on RAID 5 avoids the panic.
We are still waiting for a solution. I agree it should not take this long.
that is inacurate. All our enclosures are supported on M1.
there is also a bug in M1's that can cause kernel panics, which is true.
But now we have multiple ways users can avoid this problem, until Apple fixes the M1 panic.
Alright, here goes:
welp, it worked. Who knows.
Also, just as an update, I was able to back up the drive using an Intel Mac, and I have changed the stripe to 64kb. Hopefully that helps.
Yesterday I did a clean install of Monterey on my Late 2015 iMac and installed SoftRAID XT 6.2.1 for my TB4 enclosure with a RAID5 Volume. I "allow"d OWC in System Preferences, installed 6.2.1 driver and restarted. Everything was OK yesterday but not sure if the computer slept because it was downloading iCloud Photos, Desktop and Documents files for some time. Today I woke the iMac and there was notification that said the RAID Volume was not ejected properly. I saw a message flash briefly from SoftRAID that said something like one disk was missing then the black screen "restarting because there was a problem with you Mac". After restart the volume mounts OK. I reinstalled the 6.2.1 driver and, after reading some of this thread, have given SoftRAID Full Disk Access. Sleep prefs were "Prevent your Mac from automatically sleeping when display is off" - OFF and "Put hard disks to sleep when possible" - ON. (As they were on my Mac running Monterey before the clean install). Apart from wanting to know what to do to fix this, I'm concerned about the integrity of the files on the volume because of the incorrect eject message. FWIW I've used the same sleep prefs for years with this TB4
I would uncheck Put drives to sleep. It is associated with disk eject events.
However, it should not trigger a kernel panic. Let me know if you see another one.
Various sleep issues have existed for a long time in macOS.
SoftRAID keeps the volume integrity, but HFS does not always maintain the directory correctly, so yes, volumes that are incorrectly disconnected, can slowly degrade their directories. APFS has some protection against directory damage, to avoid this issue, but APFS has not turned out to be bullet proof.