Mojave Update - Panic on Boot

[cmn699]

Attached is the diskutil list:

If you’ll note the different drives:

Mojave Large = The new clean install
Samsung OSX = Original system drive with all personal data (problem drive)

So I see one is external (disk4s1). So that would be my USB. My question is which EFI is associated with my problem drive (Samsung OSX)?

• You said you had difficulty with one disk to start with and you had to build another one. So, the first disk has a bad EFI

• Then you created another disk that also had the same fate.

• That means both those disks that could not boot without the constant presence of your Installer USB disk during boot time have bad EFIs.
• You can connect one of them first, and using your good usb Installer's EFI repair that disk
• Test it by booting without USB.
• If it boots OK to desktop, that disk is repaired.
• Repeat the same with the other.
• If that also boots to desktop, that is also fixed.
• If that cannot reach the desktop, in addition to CLOVER ,there may be other issues causing the failure to boot
• Verbose boot screen uploaded to the Forum can help in the diagnosis in such cases.

 

[Bcb871810]

Great info! Just one thing, can you give me a run down on how to repair the EFI of the broken disk from the USB or link me to a guide?

• You said you had difficulty with one disk to start with and you had to build another one. So, the first disk has a bad EFI

• Then you created another disk that also had the same fate.

• That means both those disks that could not boot without the constant presence of your Installer USB disk during boot time have bad EFIs.
• You can connect one of them first, and using your good usb Installer's EFI repair that disk
• Test it by booting without USB.
• If it boots OK to desktop, that disk is repaired.
• Repeat the same with the other.
• If that also boots to desktop, that is also fixed.
• If that cannot reach the desktop, in addition to CLOVER ,there may be other issues causing the failure to boot
• Verbose boot screen uploaded to the Forum can help in the diagnosis in such cases.

 

[cmn699]

Great info! Just one thing, can you give me a run down on how to repair the EFI of the broken disk from the USB or link me to a guide?

In your thread #24 you said

I have a fresh drive with a working version of Mojave but does not have any personal data. I boot with that drive, downloaded EFI mounter and searched through the old drive to gather the Clover folder.

• You can use that disk you were referring to in that thread because it has a good EFI to reach its Desktop.
• Once you are on the Desktop, mount that disk's EFI with EFI Mounter V3 or Clover Configurator (Global Edition).
• and paste the copied EFI Folder on the Desktop screen
• If you have connected the non-booting Hard disk with a defective EFI (that caused it not to boot) , you can mount its EFI Partition using the EFI Mounter or CCG as in the above step copy and paste the EFI Folder from the Desktop to replace whatever you find in its EFI Partition.
  • If you find an EFI there , Delete it and paste the copied EFI.
  • If EFI Partition is empty , no problem , just paste the copied EFI.
    • You know that EFI has the juice to take any Hackintosh disk made in that system to login screen and Desktop .
• Shut down the Computer and disconnect the EFI Donor Disk( The first disk that has no personal files ).
• Reboot the Disk with the transplanted EFI in Verbose Mode.
• Take pictures of any problem screen you see at any time.

 

[Bcb871810]

Mounted the EFI of the working disk, copied EFI folder to desktop, unmounted working EFI and mounted the non-working EFI. Deleted the EFI folder out of the non-working disk and replaced with the working one. Still having the same issues. Attached are some shots.

In your thread #24 you said

• You can use that disk you were referring to in that thread because it has a good EFI to reach its Desktop.
• Once you are on the Desktop, mount that disk's EFI with EFI Mounter V3 or Clover Configurator (Global Edition).
• and paste the copied EFI Folder on the Desktop screen
• If you have connected the non-booting Hard disk with a defective EFI (that caused it not to boot) , you can mount its EFI Partition using the EFI Mounter or CCG as in the above step copy and paste the EFI Folder from the Desktop to replace whatever you find in its EFI Partition.
  • If you find an EFI there , Delete it and paste the copied EFI.
  • If EFI Partition is empty , no problem , just paste the copied EFI.
    • You know that EFI has the juice to take any Hackintosh disk made in that system to login screen and Desktop .
• Shut down the Computer and disconnect the EFI Donor Disk( The first disk that has no personal files ).
• Reboot the Disk with the transplanted EFI in Verbose Mode.
• Take pictures of any problem screen you see at any time.

 

[cmn699]

Mounted the EFI of the working disk, copied EFI folder to desktop, unmounted working EFI and mounted the non-working EFI. Deleted the EFI folder out of the non-working disk and replaced with the working one. Still having the same issues. Attached are some shots.

• Your uploaded verbose boot screen images are referring to a USB disk of some kind NOT a SATA SSD! I cannot explain failure of an Internal SATA SSD based on the images.
• Did the screen show a Prohibit Entry Sign after a garbled Text after the last image you have uploaded?
• Are you some how connecting your SATS SSD via any USB adapters?

Something does not fit with the verbose boot screen images and the information provided to this point.
I re-read your post several times to see if I would have missed anything explicitly posted.

 

[Bcb871810]

For some reason the images did not get posted in order however image number 6 is the last one where it attempts to reboot. Normally it will automatically reboot unless I use clover to “Don’t reboot on panic”. I did not see any prohibit entry. Just a fast moving screen with a bunch of text then where it hangs with the message of reporting the panic to Apple (image 6)

All of my drives are connected directly to the MB via SATA. When I attempt to boot, I use F12 in the BIOS to ensure the drive I want to boot is being selected, and then when clover loads, I ensure to select the correct drive as well. I’m not sure why it’s referring to any external disk.

Is there something on the broken disk that I can go into and delete out of there that might be causing an issue? A kext or something?

• Your uploaded verbose boot screen images are referring to a USB disk of some kind NOT a SATA SSD! I cannot explain failure of an Internal SATA SSD based on the images.
• Did the screen show a Prohibit Entry Sign after a garbled Text after the last image you have uploaded?
• Are you some how connecting your SATS SSD via any USB adapters?

Something does not fit with the verbose boot screen images and the information provided to this point.
I re-read your post several times to see if I would have missed anything explicitly posted.

 

[cmn699]

For some reason the images did not get posted in order however image number 6 is the last one where it attempts to reboot. Normally it will automatically reboot unless I use clover to “Don’t reboot on panic”. I did not see any prohibit entry. Just a fast moving screen with a bunch of text then where it hangs with the message of reporting the panic to Apple (image 6)

All of my drives are connected directly to the MB via SATA. When I attempt to boot, I use F12 in the BIOS to ensure the drive I want to boot is being selected, and then when clover loads, I ensure to select the correct drive as well. I’m not sure why it’s referring to any external disk.

Is there something on the broken disk that I can go into and delete out of there that might be causing an issue? A kext or something?

Just a fast moving screen with a bunch of text then where it hangs with the message of reporting the panic to Apple (image 6)

Is there something on the broken disk that I can go into and delete out of there that might be causing an issue? A kext or something?

I want you to take another look at the EFI Folder of the disk that can boot and this "broken disk" where you were to copy and paste the EFI. Do a real side by side comparison to see for any differences.

Disk booting is based on EFI+ BIOS settings. If they both Arte OK , disk must boot OK. If there is an early Boot Crash, something is lacking or something bad is still lurking inside in the BIOS' chosen option or Kexts in "Other" folder or .efi files in "Drivers64UEFI" folder.
To check CLOVER you have to boot using your Good disk and then access this Broken disk from the Desktop.

 

[Bcb871810]

I'm going to look through them but thought maybe you wanted to take a look as well. Attached is both the EFI from the working disk and the one from the non-working disk. Also, I forgot to attach it in the last post, maybe it will help, but when I boot the working disk, I keep getting the message saying my Mac restarted due to an error and it generated a system report. Now, I know this is from the working drive but maybe it can provide some sort of insight.

I want you to take another look at the EFI Folder of the disk that can boot and this "broken disk" where you were to copy and paste the EFI. Do a real side by side comparison to see for any differences.

Disk booting is based on EFI+ BIOS settings. If they both Arte OK , disk must boot OK. If there is an early Boot Crash, something is lacking or something bad is still lurking inside in the BIOS' chosen option or Kexts in "Other" folder or .efi files in "Drivers64UEFI" folder.
To check CLOVER you have to boot using your Good disk and then access this Broken disk from the Desktop.

 

[cmn699]

I'm going to look through them but thought maybe you wanted to take a look as well. Attached is both the EFI from the working disk and the one from the non-working disk. Also, I forgot to attach it in the last post, maybe it will help, but when I boot the working disk, I keep getting the message saying my Mac restarted due to an error and it generated a system report. Now, I know this is from the working drive but maybe it can provide some sort of insight.

• A quick look of uploaded files show a lot of problems that would prevent the disk from successful boot.
• The so called Good disk was not a Good disk. As you stated it had encountered problems and had panicked; restarted as you said.
  • The uploaded error report shows it was a Kernel Panic related to your Apple Intel Ethernet card. (See image)
• Looking at your CLOVER from both "Working" and "Non-working" disks they have identical Folder_File structure and contents
• The drivers64UEFI contents look OK
  • Contents lack needed kexts in CLOVER/kexts/Other
    • You also have the empty numbered kexts (10.6 to 10.14) that serve no useful purpose and belong to the Trash.
    • Trashing Empty folders can make looking for needed things a lot easier during diagnostic check and editing.
  • Kexts/Other has only one kext: FakeSMC and that is the latest
  • The bad news : other needed kexts are missing: like USB support and Graphics support kexts: (The Latest: USBInjectAll.kext|Lilu.kext|WhateverGreen.kext and your IntelMausi Ethernet.kext)
• config.plist: lacks significantly and can cause problem :
• The kexts you want for the Clover to load during boot for the system to reach its destination, are not real Mac kexts but Hackintosh kexts.
• To load modified kexts, you have to DISABLE System Integrity Protection [SIP] Apple Enables by default to prevent "foreign kexts" from entering.
• In your CLOVER/config.plist SIP is NOT Disabled.
  • CsrActiveConfig=0x30 ; not the needed 0x67
• If Clover cannot load needed kexts (because "Other" folder lacking them or prevented because of SIP ENABLED) during boot-->Kernel Panic

You have to check all your config.plist SECTIONS to make sure the Disk will boot and then save the edited config.plist for it to serve you well during boot.

I am uploading just a few of several screen shots I have made with your upload. Time constrains limit me from uploading all edited images to help you. You need to check them well.

 

[Bcb871810]

Ok. Again, I really appreciate your diligence in helping me. I’ll go through everything. I just really don’t understand why my system is so messed up while using Multibeast and everything else to get it running. And I’m surprised to hear the “working disk” isn’t correct either. Especially since it boots. But I will do the work.

• A quick look of uploaded files show a lot of problems that would prevent the disk from successful boot.
• The so called Good disk was not a Good disk. As you stated it had encountered problems and had panicked; restarted as you said.
  • The uploaded error report shows it was a Kernel Panic related to your Apple Intel Ethernet card. (See image)
• Looking at your CLOVER from both "Working" and "Non-working" disks they have identical Folder_File structure and contents
• The drivers64UEFI contents look OK
  • Contents lack needed kexts in CLOVER/kexts/Other
    • You also have the empty numbered kexts (10.6 to 10.14) that serve no useful purpose and belong to the Trash.
    • Trashing Empty folders can make looking for needed things a lot easier during diagnostic check and editing.
  • Kexts/Other has only one kext: FakeSMC and that is the latest
  • The bad news : other needed kexts are missing: like USB support and Graphics support kexts: (The Latest: USBInjectAll.kext|Lilu.kext|WhateverGreen.kext and your IntelMausi Ethernet.kext)
• config.plist: lacks significantly and can cause problem :
• The kexts you want for the Clover to load during boot for the system to reach its destination, are not real Mac kexts but Hackintosh kexts.
• To load modified kexts, you have to DISABLE System Integrity Protection [SIP] Apple Enables by default to prevent "foreign kexts" from entering.
• In your CLOVER/config.plist SIP is NOT Disabled.
  • CsrActiveConfig=0x30 ; not the needed 0x67
• If Clover cannot load needed kexts (because "Other" folder lacking them or prevented because of SIP ENABLED) during boot-->Kernel Panic

You have to check all your config.plist SECTIONS to make sure the Disk will boot and then save the edited config.plist for it to serve you well during boot.

I am uploading just a few of several screen shots I have made with your upload. Time constrains limit me from uploading all edited images to help you. You need to check them well.