ianinsane Posted February 17, 2019 Share Posted February 17, 2019 My E6220 with HS Sierra was running smoothly, but when I last booted it failed after the bootloader screen. It said: header read size 200 Incorrect image signature, expected version 10.7 Normal boot and with -s flag does not work. Do you have any idea where to start troubleshooting? Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 17, 2019 Administrators Share Posted February 17, 2019 It looks like it's trying to restart from an hibernation file. Didn't you disable that ? If you run with Enoch, you should be able to recover by booting manually without cache with the following flags and options: KernelBooter_kexts=Yes -f -v This will only work if you've kept a copy of all the minimum add-on kexts such as FakeSMC in /Extra/extensions. 1 Link to comment Share on other sites More sharing options...
ianinsane Posted February 18, 2019 Author Share Posted February 18, 2019 That's strange. I did disable that... Yes I'm using Enoch, but when trying to boot with KernelBooter_kexts= Yes -f -v I get this message: No kext.plist replacement found :-( Is there anything else I can do? Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 18, 2019 Administrators Share Posted February 18, 2019 That warning doesn't matter, it's for kexts patches. You've clearly not installed that file, that's all. Did you nevertheless manage to boot? If not, didn't this issue happen after that you installed a High Sierra update? If so, it's highly likely that you're back with Core Storage applied and Enoch does not support that. You'd therefore have to boot with Clover (i.e. your original HiSie USB installer I presume) and revert the partition to plain old HFS+ before Enoch can boot High Sierra again. 1 Link to comment Share on other sites More sharing options...
ianinsane Posted February 18, 2019 Author Share Posted February 18, 2019 No, I wasn't able to boot... And I didn't install any updates, also diskutil list shows the SSD as Apple_HFS. The first time this problem appeared was after it wouldn't boot due to low battery. I plugged in the power chord and hit f1 to continue booting, like I did so many times back when I was running Yosemite on that machine. This time though, with my 2 month old HS Sierra install, it got me this problem. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 18, 2019 Administrators Share Posted February 18, 2019 Try and post the output of your diskutil list command so that we verify Core Storage presence of absence. 1 Link to comment Share on other sites More sharing options...
ianinsane Posted February 18, 2019 Author Share Posted February 18, 2019 Of course: Spoiler -bash-3.2# diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *250.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh SSD 249.2 GB disk0s2 3: Apple_Boot Recovery HD 650.0 MB disk0s3 /dev/disk1 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *15.7 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS OS X Base System 1 15.4 GB disk1s2 /dev/disk2 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +5.2 MB disk2 /dev/disk3 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk3 /dev/disk4 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk4 /dev/disk5 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk5 /dev/disk6 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +2.1 MB disk6 /dev/disk7 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk7 /dev/disk8 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk8 /dev/disk9 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +6.3 MB disk9 /dev/disk10 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +2.1 MB disk10 /dev/disk11 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +1.0 MB disk11 /dev/disk12 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +2.1 MB disk12 /dev/disk13 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk13 /dev/disk14 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk14 /dev/disk15 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +1.0 MB disk15 /dev/disk16 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +6.3 MB disk16 /dev/disk17 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: untitled +524.3 KB disk17 -bash-3.2# Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 18, 2019 Administrators Share Posted February 18, 2019 Check if "sleepimage" file exists on the "Macintosh" SSD partition: ls -la /Volumes/Macintosh/var/vm If it does, remove it: rm -f /Volumes/Macintosh/var/vm/sleepimage You may then try to rebuild the cache: touch -f /Volumes/Macintosh/System/Library/Extensions /Volumes/Macintosh/usr/sbin/kextcache -Boot -U /Volumes/Macintosh -k /Volumes/Macintosh/System/Library/Kernels/kernel 1 Link to comment Share on other sites More sharing options...
ianinsane Posted February 18, 2019 Author Share Posted February 18, 2019 The first command triggers this response: ls: /Volumes/Macintosh/var/vm/: no such file or directory Still tried to rebuild the cache and got "no such file or directory" for the first two directories, "read-only file system" for all the flags and "not a directory" for the last directory... Link to comment Share on other sites More sharing options...
ianinsane Posted February 18, 2019 Author Share Posted February 18, 2019 To rule out a misunderstanding: I was now booting from the USB installer into the Sierra installation menu and ran Terminal from there. Link to comment Share on other sites More sharing options...
Recommended Posts