kushwavez Posted March 26, 2021 Share Posted March 26, 2021 17 hours ago, kushwavez said: Unfortuantely I'm facing another issue right now. I'm trying to install a Catalina 10.15.7 supplemental patch with Clover v5131 (commit sha in log name), but I can't see the Installer entry, therefore I can't boot from it. It isn't there even with "Show hidden entries". Same with Clover v5130 Spoiler It's okay with Clover v5128 (can't test v5129 because I can't find the .efi): Spoiler attaching debug logs. I saw another person with this issue, he was right: https://github.com/CloverHackyColor/CloverBootloader/issues/380 EDIT: also saw that a lot of Clover release zips are just gone from the Release page 2021-3-25_21-47_CloverX64-RELEASE_XCODE8-20210322154001-829fd04.efi.log 21.49 kB · 1 download preboot_v5128.log 20.83 kB · 0 downloads @MifJpn yes indeed, from USB installer it's working. Thanks for investigating. But I'm trying to install OTA with Software Update (as normally should be installed) like I did every time. On Big Sur, I did not have such problems with OTA, but I decided to downgrade to Cata (mostly because of the memory leak bugs on Big Sur). An OTA update appeared, and I thought okay, go ahead and install it. But after restart I was presented with the same version, the update isn't installed (of course because the entry isn't there). I just don't want to create a whole Installer USB because of a small update. Anyways @Jief_Machak, @Slice I did found something about it: This commit 333b6ce1ca2c02300e93a151e4be513af7414d06 (Hide dead installer prebooter.) After that commit (6bc80b8486563fa3cd76adff4e0209d20aa4c195 - update list in xcode project) it isn't working The commit before (3142593e38f50af12f7a3ff399dd8b0d64893b2d - update model data) is working I won't update now, let me know if you have some .efi to test with 1 1 Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 26, 2021 Share Posted March 26, 2021 17 hours ago, kushwavez said: Unfortuantely I'm facing another issue right now. I'm trying to install a Catalina 10.15.7 supplemental patch with Clover v5131 (commit sha in log name), but I can't see the Installer entry, therefore I can't boot from it. It isn't there even with "Show hidden entries". Same with Clover v5130 It's okay with Clover v5128 (can't test v5129 because I can't find the .efi): attaching debug logs. I saw another person with this issue, he was right: https://github.com/CloverHackyColor/CloverBootloader/issues/380 EDIT: also saw that a lot of Clover release zips are just gone from the Release page 2021-3-25_21-47_CloverX64-RELEASE_XCODE8-20210322154001-829fd04.efi.log 21.49 kB · 2 downloads preboot_v5128.log 20.83 kB · 0 downloads Could you try to replace "ApfsDriverLoader.efi" by this one, for example ?apfs-v11.1.efi 2 Link to comment Share on other sites More sharing options...
kushwavez Posted March 26, 2021 Share Posted March 26, 2021 (edited) Replaced, but same unfortunately. Attaching new debug.log if needed I saw this in the log maybe that is the Installer? It is considered as dead edit: but also see installer dmg boot file not found so maybe that doesn't matter [...] 0:868 0:000 APFSTargetUUID=7ADD3B9E-901D-440E-A91A-E3BCB619F3E4 0:869 0:000 contentDetails name:macOS SSD - adatok 0:869 0:000 Dead installer entry found (installer dmg boot file not found : '\macOS Install Data\Locked Files\BaseSystem.dmg') 0:869 0:000 - [07]: 'macOS SSD - adatok' 0:869 0:000 ApfsContainerUUID=5EF86F43-A55C-4384-B7DF-E35BB7E5CD9F 0:869 0:000 ApfsFileSystemUUID=7ADD3B9E-901D-440E-A91A-E3BCB619F3E4 [...] preboot_v5131.log Edited March 26, 2021 by kushwavez Link to comment Share on other sites More sharing options...
kushwavez Posted March 26, 2021 Share Posted March 26, 2021 in preboot_v5128.log I see in the log 0:782 0:000 Loader entry created for 'PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\NVMe(0x1,55-7E-62-44-68-B7-26-00)\HD(2,GPT,E2A442FB-9313-4522-AD87-63BD30A5D527,0x64028,0x1D0BB7D8)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,C7EF85D336AFBE4F8D97EC42075B2261)\7ADD3B9E-901D-440E-A91A-E3BCB619F3E4\com.apple.installer\boot.efi' 0:782 0:000 - [07]: 'macOS SSD - adatok' I think that is the Installer. I don't see such lines in the latest log 1 Link to comment Share on other sites More sharing options...
kushwavez Posted March 26, 2021 Share Posted March 26, 2021 (edited) 1 hour ago, kushwavez said: [...] 0:868 0:000 APFSTargetUUID=7ADD3B9E-901D-440E-A91A-E3BCB619F3E4 0:869 0:000 contentDetails name:macOS SSD - adatok 0:869 0:000 Dead installer entry found (installer dmg boot file not found : '\macOS Install Data\Locked Files\BaseSystem.dmg') 0:869 0:000 - [07]: 'macOS SSD - adatok' 0:869 0:000 ApfsContainerUUID=5EF86F43-A55C-4384-B7DF-E35BB7E5CD9F 0:869 0:000 ApfsFileSystemUUID=7ADD3B9E-901D-440E-A91A-E3BCB619F3E4 [...] hmmm the log in the latest release says "Dead installer entry found (installer dmg boot file not found: ....\BaseSystem.dmg"), so I thought that doesn't matter. But I think that should be the installer after all. BaseSystem.dmg is there (and the boot.efi is also inside Boot Files dir) kushwavez@Viktor-MBP ~ % sudo ls -la /System/Volumes/Data/macOS\ Install\ Data/Locked\ Files total 980008 drwx------@ 11 root wheel 352 Már 25 22:40 . drwxr-xr-x@ 8 root wheel 256 Már 25 22:40 .. -rw-r--r-- 1 root wheel 893 Már 25 22:40 .disk_label -rw-r--r--@ 1 root wheel 15 Már 25 22:40 .disk_label.contentDetails -rw-r--r-- 1 root wheel 3557 Már 25 22:40 .disk_label_2x -rw-r--r-- 1 root wheel 328 Feb 6 09:18 AppleDiagnostics.chunklist -rw-r--r--@ 1 root wheel 3147481 Feb 6 08:07 AppleDiagnostics.dmg -rw-r--r-- 1 root wheel 2020 Feb 6 09:18 BaseSystem.chunklist -rw-r--r--@ 1 root wheel 498592939 Feb 6 08:07 BaseSystem.dmg drwxr-xr-x 29 root wheel 928 Már 25 22:40 Boot Files drwx------@ 3 root wheel 96 Már 25 22:40 Product Files Edited March 26, 2021 by kushwavez Link to comment Share on other sites More sharing options...
Slice Posted March 26, 2021 Share Posted March 26, 2021 It seems all known bugs resolved. Sorry for my useless commits. Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 26, 2021 Share Posted March 26, 2021 @kushwavez Yes, this is the problem. Old version doesn't check if the installer preboot is "dead" or not. Obviously, Imade a bug when I tried to detect if the dmg file exists or not, or Clover can't read the volume (that's why I proposed a recent apfs.efi). I'm interested to debug that but that means to keep your hard drive like it is now. In a few hours, I can send you a Clover efi with very details log about this dmg detection and try to find what's going on. Let me know if you can stay with this HDD in this half installed state. 1 1 Link to comment Share on other sites More sharing options...
kushwavez Posted March 26, 2021 Share Posted March 26, 2021 @Jief_Machak That's okay, not in a hurry and the OS still can boot because the 2nd stage of the installer didn't start yet. So I'm ready. Link to comment Share on other sites More sharing options...
eng_redaesm Posted March 26, 2021 Share Posted March 26, 2021 i still can't boot even after last commit preboot.log Link to comment Share on other sites More sharing options...
kushwavez Posted March 26, 2021 Share Posted March 26, 2021 (edited) @eng_redaesm last time when I had this freeze it caused by bad Quirks settings. If I remember correctly it was "DisableLinkeditJettison". That needed to be True. I'm now using the Quirks from the config-sample.plist from the release.zip by the way, that's okay (only enabled XhciPortLimit and disabled DisableIoMapper) Edited March 26, 2021 by kushwavez Link to comment Share on other sites More sharing options...
eng_redaesm Posted March 26, 2021 Share Posted March 26, 2021 29 minutes ago, kushwavez said: @eng_redaesm last time when I had this freeze it caused by bad Quirks settings. If I remember correctly it was "DisableLinkeditJettison". That needed to be True. I'm now using the Quirks from the config-sample.plist from the release.zip by the way, that's okay (only enabled XhciPortLimit and disabled DisableIoMapper) @kushwavez. it was working and i already have Xhciportlimit enabled and disanlroMapper disabled and i make DisableLinkeditJettison true but still freezing preboot.log Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 27, 2021 Share Posted March 27, 2021 @eng_redaesm if you has previous Clover configuration that worked, could you follow this : https://jief-machak.gitbook.io/cloverhelp/ Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 27, 2021 Share Posted March 27, 2021 @kushwavez try this efi : CloverX64-2021-03-27-07-01-35-4a3bc61-dirty-jief.zipand send me the log. Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 27, 2021 Share Posted March 27, 2021 @eng_redaesm Other option : find yourself the commit that broke. All the compiled commits are here : https://github.com/jief666/CloverCommits Check first the commit corresponding to a release number. Is it working with 5131 ? 5130 ? 5129 ? Then try commits in between... 1 Link to comment Share on other sites More sharing options...
Slice Posted March 27, 2021 Share Posted March 27, 2021 On 3/26/2021 at 1:07 AM, kushwavez said: Unfortuantely I'm facing another issue right now. I'm trying to install a Catalina 10.15.7 supplemental patch with Clover v5131 (commit sha in log name), but I can't see the Installer entry, therefore I can't boot from it. It isn't there even with "Show hidden entries". Same with Clover v5130 It's okay with Clover v5128 (can't test v5129 because I can't find the .efi): I was updating Mojave with 5131. Click on Update and see what is happen without touching mouse or keyboard. First reboot: I see an Installer in the Clover menu. It started. Second reboot: no the Installer. Clover started from regular OS preboot. Some more reboots, don't know exactly how many. Voila, I see new system not touching mouse or keyboard during the whole update process. 2 Link to comment Share on other sites More sharing options...
eng_redaesm Posted March 27, 2021 Share Posted March 27, 2021 @Jief_Machak until this commit 4b0ddf4de (5131)it was booting without any problem 1 Link to comment Share on other sites More sharing options...
Slice Posted March 27, 2021 Share Posted March 27, 2021 1 hour ago, eng_redaesm said: @Jief_Machak until this commit 4b0ddf4de (5131)it was booting without any problem So you told about QEMU boot? Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 27, 2021 Share Posted March 27, 2021 (edited) 1 hour ago, eng_redaesm said: @Jief_Machak until this commit 4b0ddf4de (5131)it was booting without any problem Ok I'll have a look in few minutes. @eng_redaesm Just to be sure. 4b0ddf4deed019913c1989e192113148139c320a works, 65f8cc122d6cd5db4007218b66b72532382cc28c doesn't. Am I correct ? Could you send me both the debug.log from these 2 commits. 10 minutes ago, Slice said: So you told about QEMU boot? Told who ? eng_redaesm ? Edited March 27, 2021 by Jief_Machak Link to comment Share on other sites More sharing options...
Slice Posted March 27, 2021 Share Posted March 27, 2021 4 minutes ago, Jief_Machak said: Told who ? eng_redaesm ? Yes, I answered him. Link to comment Share on other sites More sharing options...
matxpa Posted March 27, 2021 Share Posted March 27, 2021 1 hour ago, eng_redaesm said: @Jief_Machak until this commit 4b0ddf4de (5131)it was booting without any problem I confirm with CloverX64-RELEASE_XCODE8-20210325001901-4b0ddf4-dirty.efi : boot OK With CloverX64-RELEASE_XCODE8-20210325173256-65f8cc1-dirty.efi : boot KO and with 3252bf6 or 3b542ca Clover crashes too 1 Link to comment Share on other sites More sharing options...
kushwavez Posted March 27, 2021 Share Posted March 27, 2021 (edited) 5 hours ago, Jief_Machak said: @kushwavez try this efi : CloverX64-2021-03-27-07-01-35-4a3bc61-dirty-jief.zipand send me the log. alright, here you are. And I think I know what is the problem (correct me if my hypothesis is wrong). In the log I see this: Volume= Preboot Open "" = Success Open "\" = Success Open "\macOS Install Data" = Not Found Open "\macOS Install Data\Locked Files" = Not Found Open "\macOS Install Data\Locked Files\BaseSystem.dmg" = Not Found So that location is wrong for Catalina. On Cata, the Installer is located in /System/Volumes/Data/macOS\ Install\ Data/Locked\ Files/BaseSystem.dmg It is working for you @Slice because on Mojave, there is no separate Container for System and Data, but there is on Cata, so for you the Installer is located in the "right" place (I suppose) (/macOS\ Install\ Data/) and Clover detects it. EDIT: nvm, I was wrong about that 2021-3-27_8-54_CloverX64-2021-03-27-07-01-35-4a3bc61-dirty-jief.efi.log Edited March 27, 2021 by kushwavez Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 27, 2021 Share Posted March 27, 2021 @kushwavez : the path is correct. /System/Volumes/Data is added by macos. It's the mount point. There is no mount point under Clover. From this : - [07]: 'macOS SSD - adatok' ApfsContainerUUID=5EF86F43-A55C-4384-B7DF-E35BB7E5CD9F ApfsFileSystemUUID=7ADD3B9E-901D-440E-A91A-E3BCB619F3E4 Volume= macOS SSD - adatok Open "" = Not Found Open "\" = Not Found It seems clear that Clover can't read at all your data partition. I'm installing Catalina and will check if it's a normal behaviour. I'll let you know if I need a test. Should be done by today. 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted March 27, 2021 Share Posted March 27, 2021 14 minutes ago, matxpa said: I confirm with CloverX64-RELEASE_XCODE8-20210325001901-4b0ddf4-dirty.efi : boot OK With CloverX64-RELEASE_XCODE8-20210325173256-65f8cc1-dirty.efi : boot KO and with 3252bf6 or 3b542ca Clover crashes too @matxpa What app do you use in this screenshot, please ? Link to comment Share on other sites More sharing options...
kushwavez Posted March 27, 2021 Share Posted March 27, 2021 Oh okay then. Let me know if you want any new informations Link to comment Share on other sites More sharing options...
Jief_Machak Posted March 27, 2021 Share Posted March 27, 2021 Anyway, I'll probably implement something like : if the root of the APFS target can't be opened at all, let's cancel the "dead installer" check... 3 Link to comment Share on other sites More sharing options...
Recommended Posts