Notifications
Clear all
Monterey Issues
355
Posts
50
Users
8
Reactions
57.1 K
Views
Topic starter
That is probably the cause, as there is an APFS encryption bug that affects SoftRAID volumes in particular, Apple volumes much less so. Its another issue we reported and are waiting for a fix on.
Posted : 21/02/2022 12:51 pm
Thank you. It seems working for unencrypted time machine backup. Wish the bug can be fixed soon. Thank you.
Posted : 21/02/2022 2:02 pm
I don't have a clean answer to that. Give it a try, it it works and is reliable, keep doing it. Mixing Thunderbolt and USB may not always work.
Just an update on my previous issue, after disconnecting all USB devices from the Thunderbay, so far no more crashes. Hopefully it stays that way.
Posted : 01/03/2022 12:43 pm
Topic starter
Are these USB 3.2 (USB C) devices connected to the rear?
Posted : 01/03/2022 1:05 pm
No it was a usb hub with some older devices connected including a Drobo and printer. I reconnected the hub directly to the Mac Mini.
Posted : 01/03/2022 1:07 pm
Topic starter
So the hub was likely the cause of the issues?
Posted : 01/03/2022 5:20 pm
@softraid-support So far it seems like it, I did have one other issue with it saying a drive was missing on reboot which I mentioned in a new thread. I still have my mac set to not shut down drives or sleep while displays are off, but I do have the displays sleeping and no crashes so far.
Posted : 01/03/2022 6:05 pm
macOS Monterey
Version 12.2.1
MacBook Pro M1 Max 64GB Ram
OWC Express 4M2
4 4TB NVMe Drives - Raid 5
System will crash hard if the drive is plugged in. Have tried 6.2.1 as well as the beta version.
System is fine on the Mac mini M1.
This post was modified 4 years ago 2 times by SoftRAID Support
Posted : 02/03/2022 6:34 pm
Topic starter
This is the thunderbolt chip (the DART I/O chip) crashing, which is a bug Apple is working on.
When you connect to the MBP, try pulling out one drive slightly, then after 5 minutes push it in and it should be OK and auto rebuild.
(and this is more confirmation that it is some kind of macOS System setting triggering this.)
This post was modified 4 years ago by SoftRAID Support
Posted : 02/03/2022 7:33 pm
Had a kernel panic today.
panic(cpu 1 caller 0xfffffe0015611e88): IOGMD: not wired for the IODMACommand @IOMemoryDescriptor.cpp:3236
This post was modified 4 years ago by SoftRAID Support
Posted : 07/03/2022 11:31 am
Topic starter
the IODMA panic reports can go back to the early days of macOS. Early cases were video card triggered from what I could find, later IODMA panics appear to be related to USB devices/driver, but all kinds of IO mechanisms. So it appears many things can trigger this panic.
Did this happen when you unmounted a SoftRAID volume? Or unplugged it, after unmounting?
Posted : 07/03/2022 4:01 pm
