![]() Panic(cpu 1 caller 0xfffffe001eef5678): "Halt/Restart Timed Out" 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. ![]() 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. 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. I'm now (obviously?) thinking that the problem has to do with the number of connected drive enclosures. And I can also cleanly shut down if no units are connected. Btw, it took about 35 seconds to cleanly shut down with 5 units. Only if I add the 6th unit does it panic. If I remove just one of the drive enclosures from the TB chain, I can successfully complete a clean shut down. I'm using M1/Big Sur compatible Pegasus and Softraid drivers that have recently been made available and seem to work OK.īooting 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). I connected Mac Mini TB4 port to the OWC TB3 unit, then used an Apple TB3 to TB2 to connect other TB2 units. 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 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). REGION TYPE START - END PRT/MAX SHRMOD REGION DETAIL but it stopped at that place and has not finished still.Īctivity Monitor still reports a few items that have not been killed when I initiated the "Quit Docker Desktop" command. DD0014: are the backend processes running? 5 errors occurred: ![]() [linuxkit/pkg/desktop-host-tools/pkg/client.NewClient() [ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:59 [linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(.) ipc.NewClient: -> lifecycle-server.sock VMDockerdAPI DD0004: is the Docker engine running? Get " dial unix lifecycle-server.sock: connect: no such file or directory DD0031: does the Docker API work? Cannot connect to the Docker daemon at unix://. DD0028: is there available VM disk space? DD0027: is there available disk space on the host? $ /Applications/Docker.app/Contents/MacOS/ check Output of /Applications/Docker.app/Contents/MacOS/ check The problem did not appear with an update, but with a restart of the computer and an update to the latest Docker Desktop did not resolve it. The problem is new - Docker Desktop used to work last week (This is Friday and today is Monday), which was running a previous version - either 4.11 or 4.7 or something close, since I did not note it except that I have a memory of seeing a version number when trying to re-install via homebrew. This behaviour is not reproducible on any other Mac computer I have access to other than the one I used to produce the diagnostics. Intel chip or Apple chip: Apple chip - M1 Max.I cannot run the cli tool, nor Docker Desktop is usable - it shows "Docker Desktop is stopping" and the whole UI is unusable, except for the bug report/reset tool (and various not so useful views). I have tried disabling enabled experimental features. ![]() I have tried with the latest version of Docker Desktop. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |