[Sticky] Monterey Crash/kernel panics
I have a couple of screen shots that might be helpful, but the forum software is indicating the file type is not allowed. I had this problem attempting to attach a .txt as well. What graphic formats are permitted?
jpg and .txt.
You need to export PNG as jpg.
If in text edit you "Make plain text" it will save it as a text file. Otherwise, it will be (in fact) .txt.rtf, the second extension is hidden from view, but it is not a text file. So use "Make plain text".
You can try a reinsall Monterey, but do not import data. Just use the same admin name.
What I woudl recommend is a new volume, install into that, which leaves the old volume and System intact.
Run Disk Utility.
Click + volume
Create a new volume
restart into recovery mode (hold the power button)
Select the new volume.
When you are done, there are a couple additional steps:
Start up into the OLD volume.
Now, restart to the NEW volume.
Now you can startup into recovery mode and go to Startup System recovery, and Enable third party developers, which needs to be set for each system.
With APFS, you can have multiple volumes inside the same container, its different than HFS.
Now try running SoftRAID, install the driver, etc.. It should work.
Another File System panic. We have not reported this one to Apple yet, but attach a SoftRAID tech support file so I can add it to the panic log, we are going to file this as a bug report also.
In summary, I'm seeing kernel panics issue SoftRAID on an M1 Mac with a Thunderbay IV configured as RAID 5 AND 64K stripe size.
I've already been working with SoftRaid's helpful support, but here's more detail...
I was trying to use an OWC Thunderbay IV (Thunderbolt 1 version) originally configured as RAID 5 with 16K stripe size on my Mac Studio. After setting up the volume with SoftRAID I was seeing odd behavior when trying to copy files to the drive (very, very slow data transfer). I then realized that if I rebooted the Mac Studio with the Thunderbay plugged in, I would get a kernel panic shortly after the system comes up. Contacted OWC support with a support file and MacOS crash log. They told me about the bug and thought if I recreated the volume with RAID 5 and 64K stripe size I would be OK. I did that. Everything seemed OK at that point and I was able to copy a couple of TB of data onto the Thunderbay with no issues and with the speeds I would expect. The first time I restarted the computer with the Thunderbay plugged in, instant kernel panic (it panics during the boot process so I unplugged the drive). I've sent this crash report to OWC support as well. And yes, I did migrate data from my previous Mac to the Mac Studio...
What's the latest thinking? Any possible workarounds? Doesn't sound like Apple will have this fixed soon and I've got multiple Thunderbay IVs...
We have been helping directly. So not much to comment on.
Its frustrating that the 64k apparently is starting to hit users with 12.3.1.
Apple should be releasing a fix, but it may not (probably not) be in Monterey
RAID 4 is another option here.
Does this mean that all the files on my external array are essentially irretrievable until the next major release of MacOS? I haven't been able to mount the array successfully, despite a full reformat and reinstall of my primary OS drive.
100% clean install. Waited 15 minutes before connecting array and powering it up. SoftRaid can see the array, but cannot mount or validate any of the four disks. It's not crashing, which is a minor victory, but I cannot access any of my data. Any further ideas?
If this is an M1, you need to set System Startup to "Allow third party developers", which has to be done on each system.
Here are the steps again:
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.
1. In Monterey, there is no longer an Energy Saver Pane and 2. No sleep functions were checked under the nearly named "Battery" Pane.
Make intentional errors —
Otherwise the Great Spirit
realizes you have fulfilled
your purpose on earth.
— Navajo saying