Contribute
Register

panic when booting from "Boot MacOS X Install" on installation

Joined
Jan 10, 2012
Messages
126
Motherboard
AsRock Z97E-ITX/AC
CPU
i5-5675C
Graphics
HD 6200
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Hello everybody,

Updating to High Sierra fails on my configuration.

It seems, my config is not too common, and I am not sure what is causing the problem - I might just be missing something.

"Specials" I am using:
i5-5675c with internal graphics
M.2 SSD ADATA Premier SP600
and with that iMac16,2 system definition.

It has always worked great until I tried to install the High Sierra Update.

When staring the update process, the system reboots from the Boot MacOS X Install part of my drive and panics relatively early.
It seems the crash happens in "cleanup_installer" - see below.

Any ideas what I am missing - or what I should change?

Thanks in advance,
Rudolf

Code:
Process:               cleanup_installer [67]
Path:                  /macOS Install Data/*/cleanup_installer
Identifier:            cleanup_installer
Version:               1073.8
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           cleanup_installer [67]
User ID:               0

Date/Time:             2018-01-04 17:37:49.650 +0100
OS Version:            Mac OS X 10.12.6 (16G1114)
Report Version:        12
Anonymous UUID:        3878DCFF-CC3E-ADEB-AB0E-D389E0F4127D


Time Awake Since Boot: 2 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x4] Symbol missing

Dyld Error Message:
  Symbol not found: _syslog$DARWIN_EXTSN
  Referenced from: /macOS Install Data/*/cleanup_installer (which was built for Mac OS X 10.13)
  Expected in: /usr/lib/libSystem.B.dylib

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   dyld                              0x000000010ab3f9ee __abort_with_payload + 10
1   dyld                              0x000000010ab3f43b abort_with_payload_wrapper_internal + 90
2   dyld                              0x000000010ab3f464 abort_with_payload + 9
3   dyld                              0x000000010ab1a793 dyld::halt(char const*) + 361
4   dyld                              0x000000010ab1a89e dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 139
5   libdyld.dylib                     0x00007fff9668f282 dyld_stub_binder + 282
6   ???                               0x000000010783e008 0 + 4421050376
7   libdyld.dylib                     0x00007fff96693235 start + 1

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000002000209  rbx: 0x0000000000000004  rcx: 0x00007fff583c2b38  rdx: 0x00007fff583c2fb0
  rdi: 0x0000000000000006  rsi: 0x0000000000000004  rbp: 0x00007fff583c2b90  rsp: 0x00007fff583c2b38
   r8: 0x00007fff583c2bb0   r9: 0x0000000000000000  r10: 0x0000000000000077  r11: 0x0000000000000246
  r12: 0x0000000000000077  r13: 0x00007fff583c2fb0  r14: 0x0000000000000006  r15: 0x0000000000000000
  rip: 0x000000010ab3f9ee  rfl: 0x0000000000000246  cr2: 0x0000000107875000
 
Logical CPU:     0
Error Code:      0x02000209
Trap Number:     133
 
Last edited:
Joined
Jan 10, 2012
Messages
126
Motherboard
AsRock Z97E-ITX/AC
CPU
i5-5675C
Graphics
HD 6200
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Tried lilu.kext with both IntelGraphicsDVMTFixup.kext and IntelGraphicsFixup.kext - but that did not help.

As Sierra worked flawlessly that might not be the problem?

Maybe the internal M.2 SSD I am booting from (successfully with Sierra)?

I also tried not to convert the file system, but that did not help.
 
Joined
Jan 10, 2012
Messages
126
Motherboard
AsRock Z97E-ITX/AC
CPU
i5-5675C
Graphics
HD 6200
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Here's the verbose output of my failing boot:
IMG_8510.JPG
 
Joined
Dec 19, 2015
Messages
16
Motherboard
Gigabyte B85-D3V
CPU
Intel Xeon E3-1230-V3
Graphics
Nvidia GTX760
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Same problem with you. I don't get any idea what's wrong with it now.
 
Top