![]() ![]() A process called "kextcache" was using this "invisible" volume and not unmounting when shutdown or restart was performed, preventing the OS to power off. I also realised there was another volume named as "Macintosh HD - Data 1" which was not visible in the GUI but in CLI only when cd into /Volumes. With this version of Catalina (from Mojave upgrade to Catalina), I am able to shutdown / restart without any issues so far.Īlso, I realised that The "Storage" tab of "About This Mac" now shows only one disk, whereas when I had the problem and after doing a Catalina installation (either from the image on the disk or via internet recovery), I always had two disks with the same size one named as "Macintosh HD" and the other as "Macintosh HD - Data". The upgrade completed without any issues. After a few shutdown/restart tries, I upgraded to Catalina (Apple > About This Mac > Overview > Software Update). If your Mac won’t power on at all, likely suspects are a failed power supply, a bad logic board, a blown fuse (on desktops), a dead battery or a bad AC adapter (on portables). I was able to shutdown / restart without issues in Mojave. My problem is that when am closing my laptop screen (not shutting down) like putting it on sleep. You will get some authentication notice, just hit enter again and the file will be created in the /tmp/spindump.txt directory. You can drag the shutdown log file (from Finder into Terminal) after the space and hit enter. I then did a clean Mojave installation which went okay. How to Fix Grey Screen of Death on Windows and Mac. You will need to open up terminal and type in, 'spindump -i ' and notice the space after the 'i'. In recovery mode, I wiped everything from the SSD. I created a Mojave installation USB (current macOS version is Catalina), and I booted the laptop from the USB. 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. |