fusion71au Posted August 26, 2017 Share Posted August 26, 2017 Create Custom Entries to Hide Preboot and Recovery APFS Volumes with Clover Configurator With the release of High Sierra and the APFS file system, Clover users now have "extra" entries appearing in their Main Menu - Preboot and Recovery APFS volumes. While they are harmless and actually useful in certain circumstances (eg need Preboot to boot if using File Vault encryption, need Recovery to fix some file system problems), most users will likely want to hide them in day to day use. Note: This guide is tailored to those users who want to understand how to create custom APFS entries and the "nuts and bolts" of how Clover parses the file system looking for efi loader entries. If all you want to do is hide entries, the easiest way is through the GUI/Hide section of the config.plist. This won't allow you to rename custom entries, nor unhide them with the <F3> key (at least not till Clover r4247). Pre-requisites macOS High Sierra installed on APFS SSD or HDD Clover r4097+ with apfs.efi installed in /EFI/CLOVER/drivers64UEFI or /EFI/CLOVER/drivers64 Clover Configurator v 4.49.0.0 or later Procedure 1. Record output of "diskutil list" and "diskutil apfs list" to determine the layout of the actual physical disk(s) and the synthesized APFS container. In my example, the High Sierra Volume is named macOS_HS and is installed in physical disk partition disk3s4. fusion71aus-iMac:~ fusion71au$ diskutil list /dev/disk3 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk3 1: EFI EFI 209.7 MB disk3s1 2: Microsoft Basic Data DATA 935.6 GB disk3s2 3: Microsoft Reserved 134.2 MB disk3s3 4: Apple_APFS Container disk4 63.6 GB disk3s4 5: Apple_KernelCoreDump 655.4 MB disk3s5 /dev/disk4 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +63.6 GB disk4 Physical Store disk3s4 1: APFS Volume macOS_HS 34.3 GB disk4s1 2: APFS Volume Preboot 20.9 MB disk4s2 3: APFS Volume Recovery 519.6 MB disk4s3 4: APFS Volume VM 20.5 KB disk4s4 2. Generate Clover Boot Log with terminal bdmesg > ~/Documents/bootlog.txt Note: for easier analysis of boot log, please remove all Custom/Hidden Entries from config.plist/GUI first (leaving only Clover auto scanning) before generating it. 3. Open bootlog.txt with a text editor and under the [ ScanLoader ] section, note the volume numbers corresponding to the Preboot, High Sierra and Recovery APFS volumes... 11:719 0:014 === [ ScanVolumes ] ======================================= 11:719 0:000 Found 28 volumes with blockIO 11:719 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x2,0x0) 11:730 0:011 Result of bootcode detection: bootable unknown (legacy) 11:730 0:000 USB volume 11:730 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x1A,0x7)\USB(0x2,0x0)\HD(1,MBR,0xDDF06EF8,0x80,0xF3800) 11:742 0:011 Result of bootcode detection: bootable Clover (clover) 11:742 0:000 USB volume 11:742 0:000 This is SelfVolume !! 11:742 0:000 - [02]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x0) 11:742 0:000 USB volume 11:742 0:000 - [03]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x1) 11:742 0:000 USB volume 11:742 0:000 - [04]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x2) 11:742 0:000 USB volume 11:742 0:000 - [05]: Volume: PcieRoot(0x0)\Pci(0x1D,0x7)\USB(0x0,0x0)\Unit(0x3) 11:742 0:000 USB volume 11:742 0:000 - [06]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0) 11:744 0:002 Result of bootcode detection: bootable unknown (legacy) 11:744 0:000 - [07]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0) 11:764 0:019 Result of bootcode detection: bootable unknown (legacy) 11:764 0:000 - [08]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0) 11:764 0:000 Result of bootcode detection: bootable unknown (legacy) 11:764 0:000 - [09]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,MBR,0x50CFED9B,0x800,0x32000) 11:764 0:000 Result of bootcode detection: bootable Clover (clover) 11:765 0:000 - [10]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,MBR,0x50CFED9B,0x32800,0xDF61000) 11:765 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:765 0:000 - [11]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(1,GPT,1B386756-0922-4B96-BD59-1FC3B79E189E,0x800,0x64000) 11:769 0:003 Result of bootcode detection: bootable Clover (clover) 11:769 0:000 - [12]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(2,GPT,55225B2F-270E-453A-88B9-E12C5D9F6F12,0x64800,0xC99A3800) 11:769 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:769 0:000 - [13]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(3,GPT,1FE507E9-E82B-43BF-8A8C-2249DFF67874,0xC9A08000,0xF8C68E0) 11:769 0:000 - [14]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(4,GPT,06C99874-BE94-4641-9935-2BDC5778B0E9,0xD92CE8E0,0x135F20) 11:769 0:000 - [15]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(5,GPT,A75A0F00-1C9A-40A7-9CC9-25EFEB5BA8D4,0xD9404800,0x40000) 11:769 0:000 Result of bootcode detection: bootable unknown (legacy) 11:769 0:000 - [16]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(6,GPT,696E551C-EF37-4132-8ADD-F7E3932173C4,0xD9444800,0xF8E2000) 11:770 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:770 0:000 - [17]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(7,GPT,F7710EE3-36B3-4594-9622-40ACE95BFAD9,0xE8D26800,0xE1000) 11:770 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:770 0:000 - [18]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(1,GPT,5BA2531C-72D6-4B9E-8519-A17EE40D1500,0x28,0x64000) 11:770 0:000 Result of bootcode detection: bootable Clover (clover) 11:778 0:007 - [19]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(2,GPT,685228AF-4F5E-4C8A-AA24-22FE96002F84,0x64800,0x6CEA2000) 11:778 0:000 Result of bootcode detection: bootable Windows (vista,win) 11:778 0:000 - [20]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(3,GPT,7D80B5FA-7720-49DA-BC47-5637E5BD2009,0x6CF06800,0x40000) 11:779 0:000 - [21]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(4,GPT,E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88) 11:779 0:000 Result of bootcode detection: bootable unknown (legacy) 11:779 0:000 - [22]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(5,GPT,4499D433-49D6-40D3-ACB4-3C5CC827EFCB,0x745CE588,0x138800) 11:805 0:025 - [23]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0x0,0x0) 11:805 0:000 Found optical drive 11:805 0:000 - [24]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(4,GPT,E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,050BA2A72D1D0E4D8ABDE9B99632868E) 11:805 0:000 - [25]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(4,GPT,E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,67B6FC62811C594E819DACAE2F90240D) 11:805 0:000 - [26]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(4,GPT,E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,F3D73FFF25C8334DAF3C183BC35433DF) 11:805 0:000 - [27]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(4,GPT,E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,8D3DE4AA2F63C3439A3651612754DEF1) 11:837 0:031 PutNvramPlistToRtVars: nvram.plist not found 11:837 0:000 === [ InitTheme ] ========================================= 11:852 0:015 Using theme 'BGM' (EFI\CLOVER\themes\BGM) 11:852 0:000 OS main and drive as badge 11:882 0:029 Loading font from ThemeDir: Success 11:882 0:000 Choosing theme BGM 11:882 0:000 after NVRAM boot-args=dart=0 kext-dev-mode=1 -lilubeta 11:882 0:000 === [ Dump SMC keys from NVRAM ] ========================== 11:882 0:000 found AppleSMC protocol 11:882 0:000 === [ AddCustomEntries ] ================================== 11:882 0:000 Custom entry 0 skipped because it is hidden. 11:882 0:000 === [ ScanLoader ] ======================================== 11:882 0:000 - [01]: 'CLOVER' 11:897 0:014 - [09]: 'SYSTEM' 11:899 0:002 AddLoaderEntry for Volume Name=SYSTEM 11:899 0:000 Not match custom entry 0: Type: not match 11:955 0:056 - [10]: 'WIN7_X64SSD' 11:957 0:002 - [11]: 'EFI' 11:989 0:031 AddLoaderEntry for Volume Name=EFI 11:989 0:000 Not match custom entry 0: Type: not match 11:992 0:002 - [12]: 'DATA_TSH' 11:997 0:004 - [13]: 'Macintosh HD' 12:039 0:041 AddLoaderEntry for Volume Name=Macintosh HD 12:039 0:000 Not match custom entry 0: Type: not match 12:074 0:034 Check if volume Is Hibernated: 12:074 0:000 Check sleep image 'by signature': 12:117 0:043 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success 12:117 0:000 SleepImage name from pref: ImageVolume = 'Macintosh HD', ImageName = '\private\var\vm\sleepimage' 12:144 0:026 sleepimage not found -> Not Found 12:144 0:000 hibernated: no - sign 12:159 0:014 [!] Icon 17 (icons\vol_internal_hfs.icns) not found (path: EFI\CLOVER\themes\BGM) 12:159 0:000 - [14]: 'Recovery HD' 12:160 0:000 AddLoaderEntry for Volume Name=Recovery HD 12:160 0:000 Skipped because matching custom entry 0! 12:160 0:000 - [16]: 'WIN10' 12:162 0:002 - [17]: '' 12:165 0:002 - [18]: 'EFI' 12:190 0:025 - [19]: 'DATA' 12:193 0:002 - [24]: 'Preboot' 12:195 0:002 AddLoaderEntry for Volume Name=Preboot 12:195 0:000 Not match custom entry 0: Type: not match 12:224 0:028 Check if volume Is Hibernated: 12:224 0:000 Check sleep image 'by signature': 12:224 0:000 using default sleep image name = \private\var\vm\sleepimage 12:224 0:000 sleepimage not found -> Not Found 12:224 0:000 hibernated: no - sign 12:241 0:016 - [25]: 'macOS_HS' 12:382 0:140 AddLoaderEntry for Volume Name=macOS_HS 12:382 0:000 Not match custom entry 0: Type: not match 12:440 0:058 Check if volume Is Hibernated: 12:440 0:000 Check sleep image 'by signature': 12:555 0:115 read prefs \Library\Preferences\com.apple.PowerManagement.plist status=Success 12:555 0:000 using default sleep image name = \private\var\vm\sleepimage 12:600 0:045 sleepimage not found -> Not Found 12:600 0:000 hibernated: no - sign 12:603 0:002 - [26]: 'Recovery' 12:605 0:002 AddLoaderEntry for Volume Name=Recovery 12:605 0:000 Skipped because matching custom entry 0! 12:606 0:001 - [27]: 'VM' 12:606 0:000 === [ AddCustomTool ] ===================================== 12:621 0:014 found tool \EFI\CLOVER\tools\Shell64U.efi 12:621 0:000 Checking EFI partition Volume 11 for Clover 12:644 0:023 Found Clover 12:660 0:015 === [ GetEfiBootDeviceFromNvram ] ========================= 12:660 0:000 - found entry 0. 'Boot Microsoft EFI Boot from SYSTEM', Volume 'SYSTEM', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,MBR,0x50CFED9B,0x800,0x32000)\EFI\microsoft\Boot\bootmgfw.efii' 12:660 0:000 DefaultIndex=0 and MainMenu.EntryCount=11 13:585 0:925 GUI ready Preboot Volume ---> 24 High Sierra Volume ---> 25 Recovery Volume ---> 26 4. Under [ ScanVolumes ] section, record the UUIDs of the above 3 Volumes In this example Vol 24 = Preboot: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,050BA2A72D1D0E4D8ABDE9B99632868E Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = 050BA2A72D1D0E4D8ABDE9B99632868E (little endian format) Vol 25 = macOS_HS: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,67B6FC62811C594E819DACAE2F90240D Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = 67B6FC62-811C-594E-819D-ACAE2F90240D (little endian format), 62FCB667-1C81-4E59-819D-ACAE2F90240D (big endian format) Vol 26 = Recovery: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,F3D73FFF25C8334DAF3C183BC35433DF Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = F3D73FFF25C8334DAF3C183BC35433DF (little endian format) Note the partition UUIDs for all the APFS volumes are the same because they are all formed from the same physical disk partition disk3s4 = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 5. Mount the APFS Volumes to determine the "path" to boot.efi for the Preboot and Recovery Volumes. In terminal: fusion71aus-iMac:~ fusion71au$ diskutil mount disk4s2 Volume Preboot on disk4s2 mounted fusion71aus-iMac:~ fusion71au$ diskutil mount disk4s3 Volume Recovery on disk4s3 mounted fusion71aus-iMac:~ fusion71au$ open /Volumes In Finder, the hidden folder /Volumes will open (or use "ShowAllFiles.app" attached)... Record the "path to boot.efi" by expanding the directory tree of Preboot and Recovery (hint: drag the icon of boot.efi to a terminal window for full path): So for Preboot Volume, path = /Volumes/Preboot/62FCB667-1C81-4E59-819D-ACAE2F90240D/System/Library/CoreServices/boot.efi --> record as \62FCB667-1C81-4E59-819D-ACAE2F90240D\System\Library\CoreServices\boot.efi and for Recovery Volume, path = /Volumes/Recovery/62FCB667-1C81-4E59-819D-ACAE2F90240D/boot.efi ---> record as \62FCB667-1C81-4E59-819D-ACAE2F90240D\boot.efi Notes Need backslashes in the path, including the leading \ The UUID in the paths to boot.efi, for both the Preboot and Recovery APFS volumes, is the same = Vol UUID of the High Sierra Volume in big endian format... In terminal fusion71aus-iMac:~ fusion71au$ diskutil info disk4s1 | grep UUID Volume UUID: 62FCB667-1C81-4E59-819D-ACAE2F90240D Disk / Partition UUID: 62FCB667-1C81-4E59-819D-ACAE2F90240D 6. Open Clover Configurator, mount EFI System Partition to edit /Volumes/EFI/EFI/CLOVER/config.plist 7. Click GUI section on LHS and the + sign under Custom Entries to create New Custom Entry 8. Create Preboot High Sierra Custom Entry In Volume, copy and paste Vol UUID of Preboot Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ Click Title/FullTitle and enter the display name you want eg "Preboot High Sierra" Set Injectkexts and Hidden attributes to Yes Set Entry type to OSX Leave VolumeType blank 9. Create APFS Recovery Custom Entry In Volume, copy and paste Vol UUID of Recovery APFS Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ Click Title/FullTitle and enter the display name you want eg "APFS Recovery" Set Injectkexts and Hidden attributes to Yes Set Entry type to OSXRecovery Leave VolumeType blank 10. Save config.plist and reboot the system. At the main Clover Menu, you should see something like this ... To unhide the custom APFS entries, press the F3 key Update: New "macOS Install Prebooter" Entry with Clover r4225+ Clover r4225+ has added new code to detect OS X installer data on the Preboot Volume ---> causes an extra entry at the Clover Main Menu: "Boot macOS Install Prebooter from Preboot"... If you mount your Preboot volume, you will see ... Method for hiding the new entry would be similar to hiding the Preboot Entry discussed above: In Volume, copy and paste Vol UUID of Preboot Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ (eg \UUID\com.apple.installer\boot.efi ) Click Title/FullTitle and enter the display name you want eg "High Sierra Install Prebooter" Set Injectkexts and Hidden attributes to Yes Set Entry type to OSXInstaller Leave VolumeType blank Custom Entry for Fusion Drive Installation of Sierra or High Sierra - post#22. sample_config.plist.zip apfs.efi.zip ShowAllFiles.app.zip Clover_v2.4k_r4220.zip 17 1 Link to comment Share on other sites More sharing options...
luky35 Posted August 27, 2017 Share Posted August 27, 2017 Please help!When I make the mount disk Preboot and Recovery, I can not find the paths to them as shown by your image under point 5. instructions.Thank you. My bootlog.txt bootlog.txt.zip Link to comment Share on other sites More sharing options...
fusion71au Posted August 27, 2017 Author Share Posted August 27, 2017 @luky35, The /Volumes folder is normally hidden. In terminal, type open /Volumes ---> the hidden folder /Volumes will open in Finder (or use "ShowAllFiles.app" attached). Record the "path to boot.efi" by expanding the directory tree of Preboot and Recovery (hint: drag the icon of boot.efi to a terminal window for full path). From your bootlog.txt, volume UUIDs are in blue: [08]: 'Preboot' [08]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,530D1EACF76D3F4D93B9227B2D11340B) [09]: 'macOS High Sierra' [09]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,6340DDA53663F048B1E87350FE52327A) Vol UUID = 6340DDA5-3663-F048-B1E8-7350FE52327A (little endian) = A5DD4063-6336-48F0-B1E8-7350FE52327A (big endian) - see post#13564 [10]: 'Recovery' [10]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,800E618FF361FF4587B5A37CE4B6B5A7) UUID used in "path"=Vol UUID of macOS High Sierra = A5DD4063-6336-48F0-B1E8-7350FE52327A (big endian) Edit1 @fusion71au hi, I'm sorry I did not rename Preboot and Recovery. I do not know which keys are correct because there are more High Sierra rename boot OK. http://shrani.si/f/11/7c/4bSOySCb/preboot.png 1. What is the output of diskutil list? 2. Mounted Preboot and Recovery with diskutil mount? 3. In terminal, type open /Volumes to open the /Volumes folder in Finder 4. Confirm Vol UUID of macOS High Sierra volume with diskutil info "macOS High Sierra" | grep UUID 5. The following should work in the GUI section of your config.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Preboot High Sierra</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\A5DD4063-6336-48F0-B1E8-7350FE52327A\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>530D1EACF76D3F4D93B9227B2D11340B</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>APFS Recovery</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\A5DD4063-6336-48F0-B1E8-7350FE52327A\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>800E618FF361FF4587B5A37CE4B6B5A7</string> </dict> </array> </dict> </plist> Edit2 @fusion71au hi, I'm sending you my config.plist and images boot menu... Please write where I make a mistake that I do not succeed.Thank you. I noticed you omitted the leading \ in the Paths for Preboot and APS Recovery. Edited "luky35_config_edited.plist" attached. Good luck! ShowAllFiles.app.zip luky35_sample_config.zip luky35_config_edited.plist.zip Link to comment Share on other sites More sharing options...
luky35 Posted August 27, 2017 Share Posted August 27, 2017 @luky35, The /Volumes folder is normally hidden. You can either use the "Go" menu of Finder to navigate to that folder... Finder Go Menu.png or the "ShowAllFiles.app" attached to the post. From your bootlog.txt, volume UUIDs are in blue: [08]: 'Preboot' [08]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,530D1EACF76D3F4D93B9227B2D11340B) [09]: 'macOS High Sierra' [09]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,6340DDA53663F048B1E87350FE52327A) Vol UUID = 6340DDA5-3663-F048-B1E8-7350FE52327A (little endian) = A5DD4063-6336-48F0-B1E8-7350FE52327A (big endian) - see post#13564 [10]: 'Recovery' [10]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,800E618FF361FF4587B5A37CE4B6B5A7) UUID used in "path"=Vol UUID of macOS High Sierra = A5DD4063-6336-48F0-B1E8-7350FE52327A (big endian) @fusion71au hi, I'm sorry I did not rename Preboot and Recovery. I do not know which keys are correct because there are more High Sierra rename boot OK. http://shrani.si/f/11/7c/4bSOySCb/preboot.png Link to comment Share on other sites More sharing options...
SavageAUS Posted August 27, 2017 Share Posted August 27, 2017 What would you do in this use case? Even without any custom entries the recovery volume does not show on the clover boot screen. This is a fresh DB7 install. Shanes-MBP:~ shane$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Microsoft Reserved 16.8 MB disk0s2 3: Microsoft Basic Data Windows 10 249.9 GB disk0s3 4: Apple_HFS 125.0 GB disk0s4 5: Apple_Boot 134.2 MB disk0s5 6: Apple_APFS Container disk1 124.9 GB disk0s6 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +124.9 GB disk1 Physical Store disk0s6 1: APFS Volume macOS High Sierra 12.2 GB disk1s1 2: APFS Volume Preboot 20.6 MB disk1s2 3: APFS Volume Recovery 519.6 MB disk1s3 4: APFS Volume VM 4.3 GB disk1s4 Shanes-MBP:~ shane$ bootlog.log.txt 1 Link to comment Share on other sites More sharing options...
fusion71au Posted August 28, 2017 Author Share Posted August 28, 2017 @SavageAUS, Interesting bootlog . Clover doesn't seem to be able to detect your Recovery APFS volume at all (only 3 APFS volumes showing up instead of 4?). How did you make space for and install High Sierra? What is disk0s5, size 134.2MB and can you mount it with diskutil mount disk0s5? It looks suspicious - remnants of Recovery from previous install or did you "reserve" it and make it Apple Boot Partition type? What does the GUI section of your config.plist look like? What is the output of diskutil info "macOS High Sierra" | grep UUID ? Can you show your /Volumes folder and expanded directory tree for Recovery in Finder ie type open /Volumes in terminal? Can you drill down to boot.efi? Edit1 Yes it is strange, it happening on my desktop as well, 3 instead of 4.Shanes-MBP:/ shane$ mount /dev/disk1s3mount: /dev/disk1s3: unknown special file or file system.Shanes-MBP:/ shane$ You used the incorrect terminal command to mount APFS Recovery. Should be diskutil mount disk1s3 open /Volumes then take screenshot of expanded directory tree for Recovery. I suspect the problem arose because of the order of installation and which partition you installed High Sierra. Why not install Sierra first into disk0s4 (instead of "reserving it" for install later), then install High Sierra into disk0s6? Can you delete the partition disk0s5 e.g. with GParted or GDisk? A normal Recovery HD for Sierra would be 650MB in size instead of the 134.2MB you "reserved" for it. Also I noticed you didn't follow my guide for the Custom Preboot entry... Edit2 I didnt reserve the 134 volume.... Here is recovery.Shanes-MBP:~ shane$ diskutil mount disk1s3Volume Recovery on disk1s3 mountedShanes-MBP:~ shane$ cd /Volumes/Shanes-MBP:Volumes shane$ lsPreboot Windows 10 macOS SierraRecovery macOS High SierraShanes-MBP:Volumes shane$ cd Recovery/Shanes-MBP:Recovery shane$ ls9893F89D-1A42-4275-B34F-551DC83EED70 We now have enough info for the custom Preboot Entry but still need the Vol UUID of the Recovery APFS because bootlog doesn't show it.... <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Preboot High Sierra</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\9893F89D-1A42-4275-B34F-551DC83EED70\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>2800BDBF670FC448A0774359BC62B595</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>APFS Recovery</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\9893F89D-1A42-4275-B34F-551DC83EED70\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>################################</string> </dict> </array> </dict> Can you show the result of running the following commands in terminal? diskutil info "Recovery" | grep UUID diskutil info disk1s3 | grep UUID diskutil apfs list The result will need to be converted from big endian to little endian, then used for UUID of Recovery. Maybe even try <key>Volume</key> <string>Recovery</string> for Volume name if UUID doesn't work? Edit3 I'll post output of Terminal commands when I can and config.plist gui section but still on both my machines with fresh installs the APFS recovery partition is not detected by clover so I don't think I can create a custom entry for it.Surely it's not because of Sierra recovery? I'll check other threads and see if any one else is having same issue. Try this to remove complicating factors: 1. Remove all disks from system except the High Sierra Disk0. 2. Replace the entire GUI section of your config.plist with the one below and attached to this post (has custom High Sierra, Preboot & Recovery). You have far too many custom entries that make troubleshooting very difficult. Don't specify Volume Type (let Clover decide). <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra PreBoot</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\05263B84-EEBE-32E6-AF1F-51A8FE57501D\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>3A8C9026A35CE14E8903F7DF4BBDD19C</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>843B2605BEEEE632AF1F51A8FE57501D</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra Recovery</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\05263B84-EEBE-32E6-AF1F-51A8FE57501D\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>F6A93E1CCC174B40AC09B5D229876937</string> </dict> </array> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Kernel</key> <string>MostRecent</string> <key>Legacy</key> <false/> <key>Linux</key> <false/> <key>Tool</key> <true/> </dict> </dict> </dict> </plist> 3. Hopefully all should work. F3 should un-hide Preboot and Recovery. 4. If doesn't work, provide new bootlog.txt with Clover autoscanning only (no Custom/Hidden Entries). 5. Also provide another bootlog.txt with my Custom Entries added. SavAu_GUI_config.plist.zip Link to comment Share on other sites More sharing options...
SavageAUS Posted August 28, 2017 Share Posted August 28, 2017 @SavageAUS, Very weird (and interesting) bootlog . Clover doesn't seem to be able to detect your Recovery APFS volume at all (only 3 APFS volumes showing up instead of 4?). How did you install High Sierra? Did you completely wipe the drive or just created space in an existing drive which already had other partitions first? What does the GUI section of your config.plist look like? What is the output of diskutil info "macOS High Sierra" | grep UUID ? Can you show your /Volumes folder and expanded directory tree for Recovery in Finder ie type open /Volumes in terminal? Can you drill down to boot.efi? Yes it is strange, it happening on my desktop as well, 3 instead of 4. I created my USB with createinstallmedia. I completely wiped my drive with disk utility, created partitions with disk utility then installed windows 10 first then High Sierra. <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Windows 10</string> <key>Ignore</key> <false/> <key>Type</key> <string>Windows</string> <key>Volume</key> <string>F2FB2FB8-67D2-45FF-9956-E8EC29293114</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra</string> <key>Ignore</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>9DF89398421A7542B34F551DC83EED70</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra Recovery</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>NoCaches</key> <false/> <key>Path</key> <string>\9893F89D-1A42-4275-B34F-551DC83EED70\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>F4D53CC5E88ECA48B845FFF2F3A70C18</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra PreBoot</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>BE74FCF7-0B7C-49F3-9147-01F4042E6842</string> <- this worked to rename PreBoot on my desktop but not on this machine. <key>VolumeType</key> <string>Internal</string> </dict> </array> </dict> Shanes-MBP:~ shane$ diskutil info "macOS High Sierra" | grep UUID Volume UUID: 9893F89D-1A42-4275-B34F-551DC83EED70 Disk / Partition UUID: 9893F89D-1A42-4275-B34F-551DC83EED70 Shanes-MBP:/ shane$ mount /dev/disk1s3 mount: /dev/disk1s3: unknown special file or file system. Shanes-MBP:/ shane$ Shanes-MBP:~ shane$ cd /Volumes/ Shanes-MBP:Volumes shane$ ls EFI Preboot macOS High Sierra Windows 10 macOS Sierra <- not installed yet. Shanes-MBP:Volumes shane$ Link to comment Share on other sites More sharing options...
luky35 Posted August 28, 2017 Share Posted August 28, 2017 @fusion71au hi, I'm sending you my config.plist and images boot menu. In the boot menu there is no change in the preboot and recovery sign as written in the GUI config.plist. With the F3 key, the boot menu displays double preboot and recovery icons. I also send the last bootlog.txt for review.Please write where I make a mistake that I do not succeed.Thank you. Boot Menu (F3).zip Boot Menu.zip config.plist.zip bootlog.txt.zip Terminal.zip 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted August 28, 2017 Share Posted August 28, 2017 @SavageAUS, Very weird (and interesting) bootlog . Clover doesn't seem to be able to detect your Recovery APFS volume at all (only 3 APFS volumes showing up instead of 4?). How did you make space for and install High Sierra? What is disk0s5, size 134.2MB and can you mount it with diskutil mount disk0s5? It looks suspicious - remnants of Recovery from previous install or did you "reserve" it and make it Apple Boot Partition type? What does the GUI section of your config.plist look like? What is the output of diskutil info "macOS High Sierra" | grep UUID ? Can you show your /Volumes folder and expanded directory tree for Recovery in Finder ie type open /Volumes in terminal? Can you drill down to boot.efi? You used the incorrect terminal command to mount APFS Recovery. Should be diskutil mount disk1s3 open /Volumes then take screenshot of expanded directory tree for Recovery. I suspect the problem arose because of the order of installation and which partition you installed High Sierra. Why not install Sierra first into disk0s4 (instead of "reserving it" for install later), then install High Sierra into disk0s6? Can you delete the partition disk0s5 e.g. with GParted or GDisk? A normal Recovery HD for Sierra would be 650MB in size instead of the 134.2MB you "reserved" for it. Also I noticed you didn't follow my guide for the Custom Preboot entry... I didnt reserve the 134 volume. I created 3 partitions initially. Half disk for Windows Quarter for Sierra Quarter for High Sierra Thats it. Here is recovery. Shanes-MBP:~ shane$ diskutil mount disk1s3 Volume Recovery on disk1s3 mounted Shanes-MBP:~ shane$ cd /Volumes/ Shanes-MBP:Volumes shane$ ls Preboot Windows 10 macOS Sierra Recovery macOS High Sierra Shanes-MBP:Volumes shane$ cd Recovery/ Shanes-MBP:Recovery shane$ ls 9893F89D-1A42-4275-B34F-551DC83EED70 Shanes-MBP:Recovery shane$ cd 9893F89D-1A42-4275-B34F-551DC83EED70/ Shanes-MBP:9893F89D-1A42-4275-B34F-551DC83EED70 shane$ ls BaseSystem.chunklist SystemVersion.plist immutablekernel BaseSystem.dmg boot.efi prelinkedkernel PlatformSupport.plist com.apple.Boot.plist Shanes-MBP:9893F89D-1A42-4275-B34F-551DC83EED70 shane$ Link to comment Share on other sites More sharing options...
luky35 Posted August 28, 2017 Share Posted August 28, 2017 @luky35, The /Volumes folder is normally hidden. In terminal, type open /Volumes ---> the hidden folder /Volumes will open in Finder (or use "ShowAllFiles.app" attached). Record the "path to boot.efi" by expanding the directory tree of Preboot and Recovery (hint: drag the icon of boot.efi to a terminal window for full path). From your bootlog.txt, volume UUIDs are in blue: [08]: 'Preboot' [08]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,530D1EACF76D3F4D93B9227B2D11340B) [09]: 'macOS High Sierra' [09]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,6340DDA53663F048B1E87350FE52327A) Vol UUID = 6340DDA5-3663-F048-B1E8-7350FE52327A (little endian) = A5DD4063-6336-48F0-B1E8-7350FE52327A (big endian) - see post#13564 [10]: 'Recovery' [10]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,3E159462-B634-4816-A6EB-75D42730AE42,0x64028,0x16B946B0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,800E618FF361FF4587B5A37CE4B6B5A7) UUID used in "path"=Vol UUID of macOS High Sierra = A5DD4063-6336-48F0-B1E8-7350FE52327A (big endian) Edit1 1. What is the output of diskutil list? 2. Mounted Preboot and Recovery with diskutil mount? 3. In terminal, type open /Volumes to open the /Volumes folder in Finder 4. Confirm Vol UUID of macOS High Sierra volume with diskutil info "macOS High Sierra" | grep UUID Open :Volumes in Terminal.png 5. The following should work in the GUI section of your config.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Preboot High Sierra</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\A5DD4063-6336-48F0-B1E8-7350FE52327A\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>530D1EACF76D3F4D93B9227B2D11340B</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>APFS Recovery</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\A5DD4063-6336-48F0-B1E8-7350FE52327A\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>800E618FF361FF4587B5A37CE4B6B5A7</string> </dict> </array> </dict> </plist> Edit2 I noticed you omitted the leading \ in the Paths for Preboot and APS Recovery. Edited "luky35_config_edited.plist" attached. Good luck! It works great. Thank you 1 Link to comment Share on other sites More sharing options...
SavageAUS Posted August 29, 2017 Share Posted August 29, 2017 I'll post output of Terminal commands when I can and config.plist gui section but still on both my machines with fresh installs the APFS recovery partition is not detected by clover so I don't think I can create a custom entry for it.Surely it's not because of Sierra recovery? I'll check other threads and see if any one else is having same issue.Sent from my SM-G930F using Tapatalk Entries GUI <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS Sierra</string> <key>Ignore</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>543B37C3-8FD3-45DF-B6A9-5B9A4258D004</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS Sierra recovery</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>8C67363E-92F5-4491-AF0A-64A4ABF419FE</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra</string> <key>Ignore</key> <false/> <key>NoCaches</key> <false/> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>843B2605BEEEE632AF1F51A8FE57501D</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra Recovery</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\05263B84-EEBE-32E6-AF1F-51A8FE57501D\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>C96A5300AE920F4AA444B84EB1E1C4D7</string> <key>VolumeType</key> <string>Internal</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High Sierra PreBoot</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\05263B84-EEBE-32E6-AF1F-51A8FE57501D\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>3A8C9026A35CE14E8903F7DF4BBDD19C</string> <key>VolumeType</key> <string>Internal</string> </dict> Diskutil list Shanes-iMac:~ shane$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *240.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_APFS Container disk4 239.8 GB disk0s2 /dev/disk1 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *240.1 GB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS macOS Sierra 239.2 GB disk1s2 3: Apple_Boot Recovery HD 650.0 MB disk1s3 /dev/disk4 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +239.8 GB disk4 Physical Store disk0s2 1: APFS Volume macOS High Sierra 14.0 GB disk4s1 2: APFS Volume Preboot 20.1 MB disk4s2 3: APFS Volume Recovery 519.6 MB disk4s3 4: APFS Volume VM 2.1 GB disk4s4 Bootlog bootlog.log.txt Shanes-iMac:~ shane$ diskutil info "Recovery" | grep UUID Volume UUID: 1C3EA9F6-17CC-404B-AC09-B5D229876937 Disk / Partition UUID: 1C3EA9F6-17CC-404B-AC09-B5D229876937 Shanes-iMac:~ shane$ Shanes-iMac:~ shane$ diskutil info disk4s3 | grep UUID Volume UUID: 1C3EA9F6-17CC-404B-AC09-B5D229876937 Disk / Partition UUID: 1C3EA9F6-17CC-404B-AC09-B5D229876937 Shanes-iMac:~ shane$ Shanes-iMac:~ shane$ diskutil apfs list APFS Container (1 found) | +-- Container disk4 7501D715-3201-4AED-A9AD-0CDD62150409 ==================================================== APFS Container Reference: disk4 Capacity Ceiling (Size): 239847653376 B (239.8 GB) Capacity In Use By Volumes: 16798076928 B (16.8 GB) (7.0% used) Capacity Available: 223049576448 B (223.0 GB) (93.0% free) | +-< Physical Store disk0s2 9B77FC33-F245-4183-8B31-58A45927D823 | ----------------------------------------------------------- | APFS Physical Store Disk: disk0s2 | Size: 239847653376 B (239.8 GB) | +-> Volume disk4s1 05263B84-EEBE-32E6-AF1F-51A8FE57501D | --------------------------------------------------- | APFS Volume Disk (Role): disk4s1 (No specific role) | Name: macOS High Sierra (Case-insensitive) | Mount Point: / | Capacity Consumed: 13973471232 B (14.0 GB) | Encrypted: No | +-> Volume disk4s2 26908C3A-5CA3-4EE1-8903-F7DF4BBDD19C | --------------------------------------------------- | APFS Volume Disk (Role): disk4s2 (Preboot) | Name: Preboot (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 20127744 B (20.1 MB) | Encrypted: No | +-> Volume disk4s3 1C3EA9F6-17CC-404B-AC09-B5D229876937 | --------------------------------------------------- | APFS Volume Disk (Role): disk4s3 (Recovery) | Name: Recovery (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 519626752 B (519.6 MB) | Encrypted: No | +-> Volume disk4s4 00536AC9-92AE-4A0F-A444-B84EB1E1C4D7 --------------------------------------------------- APFS Volume Disk (Role): disk4s4 (VM) Name: VM (Case-insensitive) Mount Point: /private/var/vm Capacity Consumed: 2147504128 B (2.1 GB) Encrypted: No Shanes-iMac:~ shane$ Link to comment Share on other sites More sharing options...
mustangmd Posted September 25, 2017 Share Posted September 25, 2017 Thanks for this post. I've been trying to get custom entries to work on High Sierra GM. Have latest version Clover installed-4220. No luck. Below is my info. terminal diskutil info: /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *120.0 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_APFS Container disk1 119.8 GB disk0s2 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +119.8 GB disk1 Physical Store disk0s2 1: APFS Volume Macintosh HD 85.2 GB disk1s1 2: APFS Volume Preboot 25.7 MB disk1s2 3: APFS Volume Recovery 517.0 MB disk1s3 4: APFS Volume VM 2.1 GB disk1s4 /dev/disk2 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *3.0 TB disk2 1: EFI EFI 314.6 MB disk2s1 2: Apple_HFS Time Machine 1000.0 GB disk2s2 3: Apple_HFS Data 2.0 TB disk2s3 APFS Container (1 found) | +-- Container disk1 4CDFE3DE-3408-453E-9310-54E5D4D35FB4 ==================================================== APFS Container Reference: disk1 Capacity Ceiling (Size): 119824367616 B (119.8 GB) Capacity In Use By Volumes: 88045780992 B (88.0 GB) (73.5% used) Capacity Available: 31778586624 B (31.8 GB) (26.5% free) | +-< Physical Store disk0s2 B28A57DC-973D-4499-BDBE-5720A6349D01 | ----------------------------------------------------------- | APFS Physical Store Disk: disk0s2 | Size: 119824367616 B (119.8 GB) | +-> Volume disk1s1 876A0EA7-5A83-40D1-BDE7-F9CA2C4160BE | --------------------------------------------------- | APFS Volume Disk (Role): disk1s1 (No specific role) | Name: Macintosh HD (Case-insensitive) | Mount Point: / | Capacity Consumed: 85229309952 B (85.2 GB) | Encrypted: No | +-> Volume disk1s2 97726A50-329C-48E5-9C2C-515EA4439FC8 | --------------------------------------------------- | APFS Volume Disk (Role): disk1s2 (Preboot) | Name: Preboot (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 25690112 B (25.7 MB) | Encrypted: No | +-> Volume disk1s3 02C1C443-E695-48B9-A598-F55615A75392 | --------------------------------------------------- | APFS Volume Disk (Role): disk1s3 (Recovery) | Name: Recovery (Case-insensitive) | Mount Point: Not Mounted | Capacity Consumed: 517029888 B (517.0 MB) | Encrypted: No | +-> Volume disk1s4 2FF46437-E60D-4EF0-A333-4452639A4848 --------------------------------------------------- APFS Volume Disk (Role): disk1s4 (VM) Name: VM (Case-insensitive) Mount Point: /private/var/vm Capacity Consumed: 2147504128 B (2.1 GB) Encrypted: No I've attached my config.plist and bootlog info. Not sure why clover is not matching entries? bootlog.log.txt config.plist.zip Link to comment Share on other sites More sharing options...
fusion71au Posted September 25, 2017 Author Share Posted September 25, 2017 @mustangmd, Your custom High Sierra Entry was missing a path to boot.efi, and the path you used for the Recovery Entry had forward slashes (/) instead of backslashes (\) . 1:791 0:000 Checking volume "Macintosh HD" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,B28A57DC-973D-4499-BDBE-5720A6349D01,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,A70E6A87835AD140BDE7F9CA2C4160BE)) ... skipped because path does not exist 1:792 0:000 Checking volume "Recovery" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,B28A57DC-973D-4499-BDBE-5720A6349D01,0x64028,0xDF30B60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,43C4C10295E6B948A598F55615A75392)) ... skipped because path does not exist Here are the relevant UUIDs from your boot-log & sample custom entries (High Sierra, Recovery, Preboot) for your config.plist/GUI.... [12]: 'Preboot' UUID = 506A72979C32E5489C2C515EA4439FC8 [13]: 'Macintosh HD' UUID = A70E6A87-835A-D140-BDE7-F9CA2C4160BE (Little Endian) 876A0EA7-5A83-40D1-BDE7-F9CA2C4160BE (Big Endian) [14]: 'Recovery' UUID = 43C4C10295E6B948A598F55615A75392 <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>macOS High SIerra</string> <key>Ignore</key> <false/> <key>InjectKexts</key> <string>Detect</string> <key>NoCaches</key> <false/> <key>Path</key> <string>\System\Library\CoreServices\boot.efi</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>A70E6A87835AD140BDE7F9CA2C4160BE</string> </dict> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>Recovery HD</string> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\876A0EA7-5A83-40D1-BDE7-F9CA2C4160BE\boot.efi</string> <key>Type</key> <string>OSXRecovery</string> <key>Volume</key> <string>43C4C10295E6B948A598F55615A75392</string> </dict> <dict> <key>Disabled</key> <false/> <key>Hidden</key> <true/> <key>Ignore</key> <false/> <key>InjectKexts</key> <string>Detect</string> <key>NoCaches</key> <false/> <key>Path</key> <string>\876A0EA7-5A83-40D1-BDE7-F9CA2C4160BE\System\Library\CoreServices\boot.efi</string> <key>Title</key> <string>Preboot APFS</string> <key>Type</key> <string>OSX</string> <key>Volume</key> <string>506A72979C32E5489C2C515EA4439FC8</string> </dict> </array> </dict> config_mustangmd_edited.zip 1 Link to comment Share on other sites More sharing options...
mustangmd Posted September 25, 2017 Share Posted September 25, 2017 Thanks so much fusion71au!! I spent several hours trying to figure this out. It's one of these moments! 1 Link to comment Share on other sites More sharing options...
bennyasf Posted September 27, 2017 Share Posted September 27, 2017 can someone help me? trying to disable preboot and recovery but in bootlog and terminal everything is different what would you need if you decide to help? Link to comment Share on other sites More sharing options...
mustangmd Posted September 28, 2017 Share Posted September 28, 2017 @bennyasf This guide is very thorough and accurate if you follow all the steps. You create custom entries and make them "hidden" in GUI section of Clover configurator. If you are simply just trying to hide the volumes, you can enter them in the top right section of GUI section under "Hide Volume" and add one line for Preboot and add a second line for Recovery. Doing that in this manner hides them permanently though. 1 Link to comment Share on other sites More sharing options...
BiTRiP Posted October 7, 2017 Share Posted October 7, 2017 Very good and clear tutorial. Thanks for that. 1 Link to comment Share on other sites More sharing options...
holyfield Posted October 11, 2017 Share Posted October 11, 2017 Why so complex approach by creation of custom Entries to Hide Preboot and Recovery APFS Volumes with Clover Configurator? You can just add Preboot into Hide Volume's section. Otherwise of course good tutorial 1 Link to comment Share on other sites More sharing options...
Resset Posted October 20, 2017 Share Posted October 20, 2017 Why so complex approach by creation of custom Entries to Hide Preboot and Recovery APFS Volumes with Clover Configurator? 171011-0001.jpg You can just add Preboot into Hide Volume's section. Otherwise of course good tutorial It's because sometimes you need to have access to boot from such partitions. 1 Link to comment Share on other sites More sharing options...
piiggggg Posted October 23, 2017 Share Posted October 23, 2017 I have 2 entries of Preboot partition, one for Filevault and one for macOS update. So hide macOS partition and use Preboot should be a solution with me Link to comment Share on other sites More sharing options...
jan-munich Posted October 25, 2017 Share Posted October 25, 2017 It's because sometimes you need to have access to boot from such partitions. Than you press F3 and have all your volumes back. Why so complex approach by creation of custom Entries to Hide Preboot and Recovery APFS Volumes with Clover Configurator? 171011-0001.jpg You can just add Preboot into Hide Volume's section. Otherwise of course good tutorial Agree: easiest way seems to be just to add the following: <key>GUI</key> <dict> <key>Hide</key> <array> <string>Recovery</string> <string>Preboot</string> <string>VM</string> </array> <key>Scan</key> <true/> </dict> Link to comment Share on other sites More sharing options...
fusion71au Posted November 11, 2017 Author Share Posted November 11, 2017 Creating a Custom Entry for Sierra/High Sierra Installation on a Fusion Drive At the time of writing this guide, Clover r4297 does not yet have the code to detect the boot files created by the Sierra/High Sierra installer on the "Boot OS X" partitions of the physical drives comprising a Fusion Drive. As a consequence, after the first phase of installation and reboot, there is no "Boot macOS install" entry for the Fusion Drive ---> installation cannot continue without creating a Custom Entry in Clover's config.plist that points to these boot files (located in com.apple.boot.R folder - reference post#15322 in Clover General Discussion thread). Prerequisites 1. Existing OS X installation or Sierra/High Sierra USB installer with Clover installed in EFI partition 2. 1 x Standard SATA SSD 3. 1 x Standard SATA HD Create Fusion Drive 1. Boot from the USB Installer and format both of the drives you want to use with Disk Utility as jHFS+. 2. Launch terminal and type "diskutil list". Note the disk numbers of the SSD and HD (eg disk0, disk1). 3. In terminal, create the Fusion Drive with the following command: "diskutil CS create "FusionHD" <SSD> <HD>" where <SSD>=SSD number, <HD>=Hard Disk number. -bash-3.2# diskutil CS create "FusionHD" disk0 disk1 Started CoreStorage operation Unmounting disk0 Repartitioning disk0 Unmounting disk Creating the partition map Rediscovering disk0 Adding disk0s2 to Logical Volume Group Unmounting disk1 Repartitioning disk1 Unmounting disk Creating the partition map Rediscovering disk1 Adding disk1s2 to Logical Volume Group Creating Core Storage Logical Volume Group Switching disk0s2 to Core Storage Switching disk1s2 to Core Storage Waiting for Logical Volume Group to appear Discovered new Logical Volume Group "F77C452C-BEAD-4D8C-8359-C3D745B68E85" Core Storage LVG UUID: F77C452C-BEAD-4D8C-8359-C3D745B68E85 Finished CoreStorage operation Note the UUID of the Logical Volume Group eg in this case, F77C452C-BEAD-4D8C-8359-C3D745B68E85 ---> will be needed again in step 5. 4. Once the fusion of the two drives has finished, in terminal type "diskutil CS list" ---> this will show the layout structure of your new CoreStorage (LVG) Logical Volume Group. -bash-3.2# diskutil CS list 5. You won't be able to create the first partition on the new (LVG) Logical Volume Group with Disk Utility. In preparation for the Sierra/High Sierra installation, type "diskutil CS createVolume UUID jhfs+ "FusionHD" 100%" in terminal: -bash-3.2# diskutil CS createVolume F77C452C-BEAD-4D8C-8359-C3D745B68E85 jhfs+ FusionHD 100% Started CoreStorage operation Waiting for Logical Volume to appear Formatting file system for Logical Volume Initialized /dev/rdisk21 as a 89 GB case-insensitive HFS Plus volume with a 8192k journal Mounting disk Core Storage LV UUID: 60E582DB-A590-44B5-8386-7FCAE66D7A88 Core Storage disk: disk21 Finished CoreStorage operation Your Logical Volume is now complete, formatted as jHFS+, and ready for installation. Add Custom Entry to Clover's config.plist on the USB Installer This is most easily done with Clover configurator in an existing OS X installation but can also be done with a plist/text editor. The custom entry should point to either of the "Boot OS X" volumes on the physical drives, loader path is \com.apple.boot.R\boot.efi: 1. Partition UUID of "Boot OS X" can be determined by running the diskutil info command in terminal... -bash-3.2# diskutil info "Boot OS X" | grep UUID Volume UUID: 1DF31F9F-B27C-3244-9778-BA81B8B5142D Disk / Partition UUID: 84496AE5-87DA-4862-AC79-C69E65D56EDA 2. Mount the EFI partition on the USB Installer and edit Clover's config.plist, adding the custom entry as shown below... <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>FusionHD Installer</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\com.apple.boot.R\boot.efi</string> <key>Type</key> <string>OSXInstaller</string> <key>Volume</key> <string>Boot OS X</string> #or replace with Partition UUID of "Boot OS X" </dict> </array> </dict> </dict> Installation of Sierra/High Sierra and Clover on the Fusion Drive 1. Boot to USB Installer via Clover Main Menu 2. Open Disk Utility to erase FusionHD as jHFS+ 3. Choose to install Sierra/High Sierra ---> files copied to "macOS Install Data" folder on FusionHD and boot files to "Boot OS X" partitions. System will reboot when complete... 4. Select FusionHD Installer custom entry from Clover Main Menu ---> pkg files will be extracted to final locations. System will reboot when complete... 5. Choose to "Boot macOS from Boot OS X (or from Recovery HD)" ---> complete update of boot caches, setup new user etc. 6. Mount EFI partitions of the physical drives (SSD, HD and USB Installer) with Clover Configurator and copy EFI folder from USB installer to the EFI partitions of the physical drives comprising the Fusion Drive. Update: Clover r4301 code now recognizes Fusion Drives for Sierra and High Sierra. 1 Link to comment Share on other sites More sharing options...
Allan Posted November 11, 2017 Share Posted November 11, 2017 Thank you @fusion71au 1 Link to comment Share on other sites More sharing options...
MacGTO Posted November 13, 2017 Share Posted November 13, 2017 Creating a Custom Entry for Sierra/High Sierra Installation on a Fusion Drive At the time of writing this guide, Clover r4297 does not yet have the code to detect the boot files created by the Sierra/High Sierra installer on the "Boot OS X" partitions of the physical drives comprising a Fusion Drive. As a consequence, after the first phase of installation and reboot, there is no "Boot macOS install" entry for the Fusion Drive ---> installation cannot continue without creating a Custom Entry in Clover's config.plist that points to these boot files (located in com.apple.boot.R folder - reference post#15322 in Clover General Discussion thread). Prerequisites 1. Existing OS X installation or Sierra/High Sierra USB installer with Clover installed in EFI partition 2. 1 x Standard SATA SSD 3. 1 x Standard SATA HD Create Fusion Drive 1. Boot from the USB Installer and format both of the drives you want to use with Disk Utility as jHFS+. 2. Launch terminal and type "diskutil list". Note the disk numbers of the SSD and HD (eg disk0, disk1). 3. In terminal, create the Fusion Drive with the following command: "diskutil CS create "FusionHD" <SSD> <HD>" where <SSD>=SSD number, <HD>=Hard Disk number. -bash-3.2# diskutil CS create "FusionHD" disk0 disk1 Started CoreStorage operation Unmounting disk0 Repartitioning disk0 Unmounting disk Creating the partition map Rediscovering disk0 Adding disk0s2 to Logical Volume Group Unmounting disk1 Repartitioning disk1 Unmounting disk Creating the partition map Rediscovering disk1 Adding disk1s2 to Logical Volume Group Creating Core Storage Logical Volume Group Switching disk0s2 to Core Storage Switching disk1s2 to Core Storage Waiting for Logical Volume Group to appear Discovered new Logical Volume Group "F77C452C-BEAD-4D8C-8359-C3D745B68E85" Core Storage LVG UUID: F77C452C-BEAD-4D8C-8359-C3D745B68E85 Finished CoreStorage operationNote the UUID of the Logical Volume Group eg in this case, F77C452C-BEAD-4D8C-8359-C3D745B68E85 ---> will be needed again in step 5. 4. Once the fusion of the two drives has finished, in terminal type "diskutil CS list" ---> this will show the layout structure of your new CoreStorage (LVG) Logical Volume Group. -bash-3.2# diskutil CS list5. You won't be able to create the first partition on the new (LVG) Logical Volume Group with Disk Utility. In preparation for the Sierra/High Sierra installation, type "diskutil CS createVolume UUID jhfs+ "FusionHD" 100%" in terminal: -bash-3.2# diskutil CS createVolume F77C452C-BEAD-4D8C-8359-C3D745B68E85 jhfs+ FusionHD 100% Started CoreStorage operation Waiting for Logical Volume to appear Formatting file system for Logical Volume Initialized /dev/rdisk21 as a 89 GB case-insensitive HFS Plus volume with a 8192k journal Mounting disk Core Storage LV UUID: 60E582DB-A590-44B5-8386-7FCAE66D7A88 Core Storage disk: disk21 Finished CoreStorage operation Your Logical Volume is now complete, formatted as jHFS+, and ready for installation. Add Custom Entry to Clover's config.plist on the USB Installer This is most easily done with Clover configurator in an existing OS X installation but can also be done with a plist/text editor. The custom entry should point to either of the "Boot OS X" volumes on the physical drives, loader path is \com.apple.boot.R\boot.efi: Boot OS X com.apple.boot.R.png 1. Partition UUID of "Boot OS X" can be determined by running the diskutil info command in terminal... -bash-3.2# diskutil info "Boot OS X" | grep UUID Volume UUID: 1DF31F9F-B27C-3244-9778-BA81B8B5142D Disk / Partition UUID: 84496AE5-87DA-4862-AC79-C69E65D56EDA2. Mount the EFI partition on the USB Installer and edit Clover's config.plist, adding the custom entry as shown below... FusionHD Installer Custom Entry.png <key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Disabled</key> <false/> <key>FullTitle</key> <string>FusionHD Installer</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>InjectKexts</key> <true/> <key>NoCaches</key> <false/> <key>Path</key> <string>\com.apple.boot.R\boot.efi</string> <key>Type</key> <string>OSXInstaller</string> <key>Volume</key> <string>Boot OS X</string> #or replace with Partition UUID of "Boot OS X" </dict> </array> </dict> </dict> Installation of Sierra/High Sierra and Clover on the Fusion Drive 1. Boot to USB Installer via Clover Main Menu 2. Open Disk Utility to erase FusionHD as jHFS+ 3. Choose to install Sierra/High Sierra ---> files copied to "macOS Install Data" folder on FusionHD and boot files to "Boot OS X" partitions. System will reboot when complete... 4. Select FusionHD Installer custom entry from Clover Main Menu ---> pkg files will be extracted to final locations. Boot from FusionHD Installer.png System will reboot when complete...5. Choose to "Boot macOS from FusionHD" ---> complete update of boot caches, setup new user etc. 6. Mount EFI partitions of the physical drives (SSD, HD and USB Installer) with Clover Configurator and copy EFI folder from USB installer to the EFI partitions of the physical drives comprising the Fusion Drive. Hi, after create the custom entries at first reboot when I boot from custom I’ve an error: OSInstall.mpkg missing or damaged Any solution?? Link to comment Share on other sites More sharing options...
MacGTO Posted November 15, 2017 Share Posted November 15, 2017 UPDATE: injecting SmUUID on config.plist the installation start.... maybe is a must?? Link to comment Share on other sites More sharing options...
Recommended Posts