MacBook Pro M1 crash while Raid drive mounting (Softraid 6.0.5 and Mac OS 11.6)
My thunderbolt 4bays drive won't mount anymore, I hear the drive spinning (waking up) when I plug it in, and just before they'd mount, it crashes the computer: pink flash, black screen, reboot.
This is an M1?
The problem is perhaps twofold. Can you get me the panic log from the crash? (report to Apple, more details, then copy/paste into text edit)
the crash may have something to do with a rebuild, or it may be the thunderbolt bus crashing I can tell partially from the panic report.
This is indeed the thunderbolt controller crashing.
We need to try something.
A) if you have an intel computer around. Connect to that and make sure the volume is in sync (or let it rebuild if not)
B) remove one disk, and connect to your computer. It will mount is my guess. Save a SoftRAID tech support file and send it to me.
If you do not have another computer, removing a disk will let it connect, but it may cause a problem with the volume. (you may need to backup/restore to get the volume optimized again) But it won't risk your data.
Let me know.
I do have a 2013 Mac Pro with Catalina on it, and I will try to mount it and follow your instructions.
But does it mean one of the drives might be dead?
No, I think this is a bug in the M1. Not sure, but if you connect it to the Catalina machine and it is in sync, great. You can validate it if you want/have time. Then remove any disk, temporarily, and connect to the M1. I bet it works. Let me know.
I've got a related issue. I've tried to read/understand all of the various threads related to Big Sur, M1 and Pink screen crashes. We have an M1 Mini with a USB connected SSD formerly part of an older mirrored system (one SATA internal SSD, one USB External SSD). We have a new Thunderbolt/USB-C SanDisk 1TB SSD that we'd like to use as the mirror volume to the original (and slower) USB-A (3.0?) SSD, so initially, the M1 loads fine with just the one drive. We've gone through the "hold power button down" to reduce security, clicking all of the loosening security checkboxes, but not running csrutil (which I thought might be equivalent?)
Note, we're running 6.0.5 and 11.6 on the M1 with 8GB or RAM. Attempting to add the USB-C as a secondary disk immediately crashes the machine. We've also tried moving both USB and USB-C drives to an older intel MBP (2020) where the 2 can be paired normally and successfully, but we didn't have time to let the mirror fully synchronize as it's a mail server volume that needed to be restored ASAP. Thus, moving it back to the M1 booted fine, but now would not mount. Attempting to mount manually (just right-clicking on volume) didn't work. Unplugging the USB-C drive would allow it to mount, but machine would crash as soon as the drive was plugged back in.
We haven't tried 6.1beta yet, but I was hoping there might be some evolution of this issue that would be relevant. I can obtain some support docs if that helps, especially if they're obtainable using softraidtool command-line utility. I have run the kextstat command to confirm 6.0.5 is loaded:
mike@sf ➜ /Users/mike
$ sudo kextstat -b com.softraid.driver.SoftRAID ~
Executing: /usr/bin/kmutil showloaded --bundle-identifier com.softraid.driver.SoftRAID
No variant specified, falling back to release
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
223 0 0xfffffe0006ebc000 0x4000 0x4000 com.softraid.driver.SoftRAID (6.0.5) 49B1BBDE-E9CE-36CC-8C01-19B861E807C8 <15 5 4 3>
Thanks for any insights.
csrutil will not work on M1, just do the third party developer preference, as I think you did.
Try the beta, we did make one driver change. There are some USB bugs in M1, hope you are not running into that.
When you say USBC, that is the cable type. Is it USB C to C, or A to C, or what?
(the USB bus type is 1, 2, 3, 3.1, 3.1gen2) its confusing)
@softraid-support We've installed 6.1 beta 8 and sadly, it doesn't address the problem. We get the pink screen of death within seconds of the new drive being plugged in; it briefly shows up in SoftRAID, but probably right where it tries to start mirroring/syncing it dies. I've enclosed the TechSupport file, and I ran the sysdiagnose utility which I can try to upload via the instructions you've posted in other threads. It's 235MB. Not sure if that's useful to you or not.
Can you send me a panic log (report to Apple, more details, save to a text edit file)
What if you set the SoftRAID Mirror preference to disable auto rebuilding? restart and connect the drive. Does it panic?
Yes, send me a link to the System Diagnostic also. thanks
Question, did it do this on 11.5?
@softraid-support Quick update; turning auto-rebuilding off did indeed allow the disk to be connected. We "Removed Secondary Disk" as well prior to plugging the drive in which, in retrospect, may not have been the best idea, but we were then able to re-initialize the disk (now with 6.1b8) and re-add it to the volume, all without any panics. As a confirmation step, prior to initiating a mirror sync, we decided to reboot the machine and got launched into "Panic Medic Boot" with the dialog: "A third party kernel extension was preventing the machine from successfully booting. All 3rd party kernel extension have been disabled. You will be prompted to re-enable them in the Security & Privacy sys pref pane as they are used." Where in the privacy sys pref pane should we be looking for the OWC "allowed" instance? I think we hit that button when we first installed and dialed back all the security steps.
@softraid-support So, we have yet to attempt a re-sync, but since we're not able to restart with both drives attached without triggering the Panic Medic Boot, it seems like we need to crawl before we can walk... Booting is totally normal without the 2nd drive attached at all, but now, plugging the disk in immediately pink screens again. I'm assuming we can repeat the cycle by "removing secondary disk" to allow the plugging in of the drive and then re-add it to the volume.
One more odd thing, we checked the "Manually Load SR driver on Restart" option and we'd had the "Mount volumes when no user logged in" in 6.0.5, but both options became unchecked. The latter, perhaps, is not preserved across App revisions (shouldn't it be, though?), but the former seemed surprising.