Saltar al contenido principal

Cómo determinar causas de apagado en Mac

  1. Cómo determinar causas de apagado en Mac, Abrir Terminal.app: paso 1, imagen 1 de 1
    • Abrir Terminal.app

    The terminal responded:log: warning: The log archive contains partial or missing metadata

    log: cannot use --last when archive metadata is missing

    Any advice anyone?

    Edward - Contestar

  2. Cómo determinar causas de apagado en Mac, Listar eventos de apagado anteriores: paso 2, imagen 1 de 1
    • Copia y pega el siguiente comando en tu ventana de Terminal:

    • log show --predicate 'eventMessage contains "Previous shutdown cause"' --last 24h

    • Podemos cambiar la parte '24h' por cualquier cantidad de horas, dependiendo de qué tan atrás necesitas ver.

    This doesn’t appear to show anything on Apple Silicon M1 systems.

    Henk Poley - Contestar

    That’s right.

    Greenie CP -

    Late 2013 cause -128 :( Probably old boy needs replacement already

    Alexsey Novik - Contestar

    My terminal reads:

    Bad predicate (Unable to parse the format string “ ‘eventMessage”): ‘eventMessage

    Any ideas?

    Richard Freeman - Contestar

    I got the same message Big Sur 11.7.1.

    Ivan Ciego -

  3. Cómo determinar causas de apagado en Mac, Determinación de las causas de apagado: paso 3, imagen 1 de 1
    • Las causas de apagado anteriores en el período de tiempo que seleccionaste aparecerán como una lista.

    • Las causas comunes de apagado incluyen 5 que indica un apagado normal, 3 que indica un apagado forzado (es decir, mantener presionado el botón de encendido) y 0 que indica que se desconectó la alimentación.

    • Puedes encontrar una lista de causas de apagado aquí: Causas de apagado (del blog de George Garside)

    the terminal command does not work in El Capitan. Apparently this works only with Sierra onwards. Any ideas how to get this to work with El Capitan?

    Avocet Peregrine - Contestar

    I’m getting a Previous Shutdown Cause code that is not listed in either iFixit or in grgarside blog (Previous shutdown cause: -8). Any ideas on what it might be? Thanks.

    Chevindu Wickramathilaka - Contestar

Conclusión

¡Hecho! Deberías poder usar estos códigos para solucionar más problemas de apagados aleatorios u otros eventos extraños.

Presiona el botón a continuación si esta guía ayudó a resolver tu problema :)

23 personas más completaron esta guía.

Un agradecimiento especial a estos traductores:

en es

100%

Estos traductores nos están ayudando a reparar el mundo! ¿Quieres contribuir?
Empezar a traducir ›

Documentos Adjuntos

Jonah Aragon

Miembro Desde 08/05/18

5,303 Reputación

5 Guías creadas

Equipo

Experimax Coon Rapids Miembro de Experimax Coon Rapids

Business

3 Miembros

17 Guías creadas

13 comentarios

For me it says

kernel: (AppleSMC) Previous shutdown cause: -20

The attached PDF (and the internet) doesn’t seem to have any information about this code. What’s the source of the codes for the PDF? Maybe they have updated listing for shutdown codes.

Saurabh Shrivastava - Contestar

we also have -20 as a cause and have no idea what it means. did you ever find it out?

octomobiki -

I also have -20 code of shut down after macOS 10.15.5 update with MBP 16inches model.

but no information at all….

赤月小黄泉 -

writErr = -20, /*I/O System Errors*/ its this error for code -20 .. Find all error codes here :- https://krypted.com/lists/comprehensive-...

UNKNOWN X -

Sorry , that was not related, check this one : - https://georgegarside.com/blog/macos/shu...

and, error code 20- T2 security chip initiated shutdown

UNKNOWN X -

copied/pasted your terminal command and got this: -bash: log: command not found

OS 10.11.6

Chris Catalano - Contestar

Hello,

First time posting here but I’m having some issues with a Macbook Air 2020 (Not the M1) having some shutdowns, I have run the terminal command and it’s coming up with Error -67 and I can’t seem to find this one anywhere. Hoping someone has some guidance, Running most up to date Big Sur, (11.1). Clean installed the OS and didn’t transfer a backup over and it seems to be still happening. Also tried an SMC / NVRAM reset, Safe mode, first aid disk. Any advise would be appreciated!

Blair Harrison - Contestar

My MacBook air 2015 is unusable now . It keeps shutting down after 5-10 minutes of uses … and the last shut down cause is -128

What should i do now ? any one ????

CLOUD GAMING - Contestar

I have 2014 MacBook Pro 13 and I had the same problem my Mac was shutting down randomly. I looked the logs from the terminal and it stated the problem was power disconnected (shutdown cause 0). So I reset the SMC and unplugged my battery and plug it back to logic board. Also I drained my battery completely and charged it to 100 without distraction and waited 8 more hours on the %100. My problem was solved. Mac never shuts down again and my Mac is working faster. Maybe this information will be helpful to somebody.

Selim Tuzel - Contestar

cloud gaming, -128 is not the error you want to see as it refers to a problem with the logic board

cheers

marcus stephen - Contestar

Does not work on M1 Macs. 0 entries come up.

Drew - Contestar

Hello , what would be this command but for a M1 rubbing lates Ventura version ?

Erick Llanos - Contestar

in my case it is -128 which is same to -112. can you please tell me the solution

Muhammad Ali Kayani - Contestar

Agregar Comentario

Ver Estadísticas:

Ultimas 24 horas: 71

Ultimos 7 días: 307

Ultimos 30 días: 1,367

Todo El Tiempo: 87,837