Kernel Panic when RAID 5 volume mounts
I have a RAID 5 volume (in ThunderBay 4 with TB2) that was originally created in 2014. I'm running MacOS 11.1 and SoftRAID 6 beta 48. Overnight my iMac (15,1) kernel panicked. I found I cannot log in without a kernel panic unless the RAID 5 volume is disconnected. If I insert each disk one at a time, it appears in the SoftRAID interface with no problems reported. Adding 2nd disk is fine. But adding 3rd disk causes the volume to attempt to mount and then instant kernel panic.
I also tried connecting the disk chassis to my 2015 MacBook Pro with the latest version of MacOS Catalina (10.15.6?). It has no SoftRAID drivers installed. It also kernel panics as soon as it attempts to mount the volume.
It appears the HW is OK and likely the volume is corrupted. There doesn't seem to be a way to repair it since it immediately panics.
Disable Auto rebuilds in SoftRAID preferences. I do not think this will help, but we need to try this first.
restart, then connect your volume. Does it panic?
Followed your suggestion. Did not help.
Also, I have a ThunderBay Mini with 4 SSD in RAID 6. Still works fine - same iMac.
If you connect two disks, run SoftRAID. Look for "predicted failure".
then connect the other two (only).
Are any disks failing?
All four drives show zero I/O errors and SMART status of PASS. No predicted drive failure message.
I am not sure why a mount should panic the system.
Did you ever try to connect this to another computer? Different OS (Catalina for example?)
Yes. From my original post: "I also tried connecting the disk chassis to my 2015 MacBook Pro with the latest version of MacOS Catalina (10.15.6?). It has no SoftRAID drivers installed. It also kernel panics as soon as it attempts to mount the volume."
Assuming this is not recoverable, which is seeming more likely than ever, can I reformat the drives and start over? Or should I get new drives? I have a backup to recover from.
If you have a backup, its probably simplest to delete the volume and recreate it.
Just insert 2 disks, delete the volume, then the other two, delete and create a new volume and restore.
I do not understand why just mounting would k.p. the system. Theoretically MacOS should prevent that.
Since there seems to be no chance of recovery, I deleted the volume and recreated a new one with the same disks. So far after a few days it is working fine.
I'm having the same kernel panics, however the ThunderBay doesn't always need to be connected.
This is on macOS Monterey on new M1 Max MacBook Pro.