Mac Pro newest, promise technology raid attached two monitors. System runs fine, but at shut down, system appears to take a long time to shut down, kinda hangs and eventually shuts down briefly. It then reboots by itself and reports a crash, a kernel panic type crash.
This doesn’t happen at every shutdown, I haven’t yet been able to isolate whether having had a particular application running at shutdown time yet is associated.
anyone else?
Still working to isolate this. One promise array is native thunderbolt 3, the other is 2, but with a 3-2 adapter. With either one connected without the other, there is no panic at shut down time. However, it will happen with both arrays attached. Previously with Catalina, no issue. Not 100% yet on this, but getting there. Promise Utility and firmware all up to date.
Still working to isolate this. One promise array is native thunderbolt 3, the other is 2, but with a 3-2 adapter. With either one connected without the other, there is no panic at shut down time. However, it will happen with both arrays attached. Previously with Catalina, no issue. Not 100% yet on this, but getting there. Promise Utility and firmware all up to date.
I actually did work around this. Set up was, 4 promise arrays, 2 t2's and 2 t3's. Previous set up daisy chained the 2 3's, and the two 2's were daisy chained with a 3-2 adapter right at the t3 port on the computer. This configuration worked in Catalina, but caused crash at shutdown in big sur with a panic.
New configuration which worked around it: each t2 array was daisy chained of a t3 array with adapter between the t3 array and each t2.
In both cases two t3 ports were used on the computer. Hope this makes sense.
I have the same problem and a very similar configuration (iMac Pro with two Raids, one TB3 and one TB2 connected via the Apple adapter to TB3, two Monitors). I happens at nearly every shutdown.
Have you (or anybody else) found a solution?
I have now completely worked around this issue. I used two external drives (raid arrays) for time machine backups, both were hfs volumes. After researching some more, big sur appears to prefer apfs case sensitive formatted partitions. I then carefully reset my backup volumes in this manner, starting the backups over on each drive (7 hourse each) and the problem of not being able to eject volumes at shutdown time leading to a kernel panic has disappeared. This both remains a bug, as well as missing advice to users say via a treatise on this topic being published in apple support.
I also have a similar problem on my new M1 Mac mini on Big Sur (11.1), a 40" 4k external display, and connected to 6 external drive enclosures, all Mac OS Extended (Journaled). Two of the enclosures are Promise Pegasus2 R4s (TB2), two are Akitio 4 bay units (TB2) and two are OWC 4 bay units (TB2 and TB3). I connected Mac Mini TB4 port to the OWC TB3 unit, then used an Apple TB3 to TB2 to connect other TB2 units. I'm using M1/Big Sur compatible Pegasus and Softraid drivers that have recently been made available and seem to work OK.
Booting up the M1 from a cold start works fine, but if try to shut down with all external drive units connected, after about 40 seconds, the Mini will restart with a panic notification (I copied the beginning part of the panic report below). If I remove just one of the drive enclosures from the TB chain, I can successfully complete a clean shut down. Only if I add the 6th unit does it panic. Btw, it took about 35 seconds to cleanly shut down with 5 units. And I can also cleanly shut down if no units are connected.
I'm now (obviously?) thinking that the problem has to do with the number of connected drive enclosures. When I connect these same 6 units to my Mac Pro (late 2013) on Catalina (10.15.7), I have no problems and it cleanly shuts down every time. The time needed to cleanly shut down all 6 units on Catalina is about 26 seconds, which is much shorter than when on Big Sur.
I've been able to bypass the problem by ejecting the 2 Promise units, disconnecting from TB chain, then shut down, but hopefully Apple can come up with a fix soon so I don't have to keep doing this.
---
panic(cpu 1 caller 0xfffffe001eef5678): "Halt/Restart Timed Out"
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 20C69
Kernel version: Darwin Kernel Version 20.2.0: Wed Dec 2 20:40:21 PST 2020; root:xnu-7195.60.75~1/RELEASE_ARM64_T8101
Fileset Kernelcache UUID: 3E6AA74DF723BCB886499A5AAB34FA34
Kernel UUID: 48F71DB3-6C91-3E62-9576-3A1DCEF2B536
iBoot version: iBoot-6723.61.3
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x0000000016b00000
KernelCache base: 0xfffffe001db04000
Kernel slide: 0x0000000017640000
Kernel text base: 0xfffffe001e644000
Kernel text exec base: 0xfffffe001e70c000
mach_absolute_time: 0xdab986b2
Epoch Time: sec usec
Boot : 0x5fe237e2 0x000d88d1
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x5fe2386d 0x0007f0ab
CORE 0 recently retired instr at 0xfffffe001e876c5c
CORE 1 recently retired instr at 0xfffffe001e875798
CORE 2 recently retired instr at 0xfffffe001e876c5c
CORE 3 recently retired instr at 0xfffffe001e876c5c
CORE 4 recently retired instr at 0xfffffe001e876c60
CORE 5 recently retired instr at 0xfffffe001e876c60
CORE 6 recently retired instr at 0xfffffe001e876c60
CORE 7 recently retired instr at 0xfffffe001e876c60
Panicked task 0xfffffe166d004c70: 38253 pages, 512 threads: pid 0: kernel_task
Panicked thread: 0xfffffe16718f1fb8, backtrace: 0xfffffe308932b7a0, tid: 9734
lr: 0xfffffe001e759f8c fp: 0xfffffe308932b810
lr: 0xfffffe001e759d58 fp: 0xfffffe308932b880
lr: 0xfffffe001e87bf5c fp: 0xfffffe308932b8a0
lr: 0xfffffe001e86d914 fp: 0xfffffe308932b950
lr: 0xfffffe001e7137e8 fp: 0xfffffe308932b960
lr: 0xfffffe001e7599e8 fp: 0xfffffe308932bcf0
lr: 0xfffffe001e7599e8 fp: 0xfffffe308932bd60
lr: 0xfffffe001eef43f8 fp: 0xfffffe308932bd80
lr: 0xfffffe001eef5678 fp: 0xfffffe308932bd90
lr: 0xfffffe001e79b4d0 fp: 0xfffffe308932be10
lr: 0xfffffe001e79afac fp: 0xfffffe308932bf00
lr: 0xfffffe001e71cc14 fp: 0x0000000000000000
last started kext at 1109183920: com.apple.iokit.SCSITaskUserClient 436.40.6 (addr 0xfffffe001e3c8000, size 16384)
loaded kexts:
com.softraid.driver.SoftRAID 6.0.1b47
com.promise.driver.stex 6.2.16
com.apple.iokit.SCSITaskUserClient 436.40.6
com.apple.filesystems.autofs 3.0
... (additional report info removed)
thanks! Right sounds familiar. 2 of my external pegasus units were used for time machine. I reformatted in to apfs for those two drives, started over afresh with time machine on each Problem gone. It seems like it may take two conditions, using more than one time machine drive AND using hfs+ on each. Changing to apfs (case sensitive) and starting over the backups on each fixed it.
I'm not using Time machine. I have my Pegasus units backed up onto some other Softraid units. I think I'll wait a while to see if Apple makes a fix, like in next OS release. If no fix coming soon, I might try reformatting to APFS since I have them backed up. Btw, did you report this to Apple? I did forward panic reports to Apple, but don't know if that makes them look at it sooner. Thx.
Yes, worked with Apple extensively to provide information to chase it down. In the mean time I kept working through it and narrowing down the whole thing, solved it for me as I mentioned and has been fine since. I let them know of the work-around or solution I came up with.
By the way, interestingly, the panic would not occur if either of those Pegasus units were not backed up to. So, for example, if I had the machine up for a short enough time before a backup would run, then I could do a normal shutdown without a panic. That along with some reading about the fact that time machine in particular likes apfs formatted volumes to live on, led me to the workaround noted above.
Sounds like my situation is a little different from yours since I'm not using Time Machine. If the problem is also related to how many drive units are connected, you'd think others on Big Sur and with multiple external drive units might run into the same problem. Of course if they are APFS formatted units, like you say, maybe the problem will not be encountered. Again, I think I'll wait until next OS update occurs to see if goes away. If not, I might try reformatting to APFS. Thanks a lot for your help! Paul
Just to report in I'm on the same boat. Just updated 2015 iMac from scratch (aka reformat and install empty BigSur then import using migration assistant) and using Time Machine on a Synology NAS and a My Cloud ethernet WD drive for shared network data access, system collapses on shutdown with the ugly multilanguage gray text and icon prone to system restart instead of actually shutdown.
I (MacBook Pro (15-inch, 2017)) seem to have a similar/the same problem after the last update, yet I don't have anything attached except an external monitor from Dell. So no external drives. The system gets stuck and then reboots and also reports a crash.
Wow that makes it even more confusing... as everything sounded related to "drives" not being ejected by the system on shutdown.
Anyone experiencing this on anything other than laptops besides me? I just use the "Suspend" function until a patch or solution is found...
I have a bunch of drives attached. And it takes almost a minute to shut down. No issues restarting other than the long wait.
iMac (Retina 5K, 27-inch, 2017)
6 attached drives one of which is a JBOD array of 2 disks.
I do not have the significant setup that some of you do, but I DO have the same problem. My newer iMac running Big Sur 11.1 often reboots or won't shut down properly. The next boot up shows an un-properly shut down machine, which I dutifully report. I have 2 external hard drives. 6GB and 8 GB. One holds all of my photographs and the other backs up my computer and the photography HD using Time Machine. Regardless.... after reading some of your reports I tried un-mounting my HD's before shut down and like magic... all shut down quickly. I hope Apple is working on a fix for this. I haven't had to ritualize my shut downs since my old PC-WIndows days! :-)
Same issue here. I have an application called AutoMounter which does like it says and auto mounts (and auto remounts) my NAS for me: https://www.pixeleyes.co.nz/automounter/
’Pausing’ the auto mount function in there, manually unmounting the drives and waiting a few seconds resulted in the first clean shutdown in weeks!
This was never an issue before but seems big sur can’t unmount the drives like it used to be able to.
Big Sur hang and crash at shutdown
