Jump to content

Create Custom Entries to Hide Preboot and Recovery APFS Volumes, Fusion Drive Installation with Clover Configurator


fusion71au
40 posts in this topic

Recommended Posts

  • 3 months later...

UPDATE!

 

At least, for Mojave and last version of Clover boot loader, you need to use the UUID of the partion that corresponds to the APFS container, in the example above from user "fusion71au", UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 (disk3s4).

 

Resuming, that UUID must be inserted in the top first field on the left of the custom entry, reffering to any entry (partition) inside the container you are trying to configure. RIGHT?!

Link to comment
Share on other sites

15 hours ago, catrindade1958 said:

UPDATE!

 

At least, for Mojave and last version of Clover boot loader, you need to use the UUID of the partion that corresponds to the APFS container, in the example above from user "fusion71au", UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 (disk3s4).

 

Resuming, that UUID must be inserted in the top first field on the left of the custom entry, reffering to any entry (partition) inside the container you are trying to configure. RIGHT?!

 

not that complicated for me, I have clover 4722 and Mojave dev beta 14.2 I only put "Preboot" in clover GUI hide volumes section.

 

 

 

Screen Shot 2018-11-05 at 7.37.42 PM.png

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

I wanted to simplify the boot menu of my Hackintosh for users in my household would be confused by the multiple boot volume choices they are confronted with when they first boot the computer up, so I turned to Clover Configurator's GUI / Custom Entries function. For my purposes, have a dual-boot Hackintosh that can boot either in to OS X Mojave or Windows 10.

 

This post is to provide some notes from my experience; you can treat it as minor update to the original guide that was published in this thread. Please refer to 

 

Under Clover Configurator v5.3.2
  • Use Generate boot.log function in Clover Configurator to get a log of the EFI boot sequence. You can also do ```bdmesg``` at CLI to get the same information
  • Look under ScanLoaders to find the volume number, expressed within square brackets, that matches the user-friendly English name of the volume of interest. In our case, it was ‘Preboot’ with volume [19]
  • Then look under ScanVolumes and find the entry that matches the volume number, e.g. [19]. For OSX EFI boot volumes, the volume ID is within the VenMedia group, second argument, .e.g
    • [19]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x5,0xFFFF,0x0)\HD(2,GPT,1016XXXX-XXXX-XXXX-XXXX-XXXXXXXXA406,0x64028,0x746A2D60)\VenMedia(BE74XXXX-XXXX-XXXX-XXXX-XXXXXXXX6842,2610XXXXXXXXXXXXXXXXXXXX9AF3)
    • So the volume ID for this volume is ***2610XXXXXXXXXXXXXXXXXXXX9AF3***
    • This volume ID can be put into Configurator/Boot/Default Boot Volume, to define the default boot volume, i.e. automatically boot from here after a certain timeout period defined on the same page
    • This volume ID is also used in the Custom Entries objects you can define
    • For Windows EFI boot volumes, the volume ID is trickier to get. Ours happens to be volume number [15]:
      • [15]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x4,0xFFFF,0x0)\HD(1,GPT,B9E7XXXX-XXXX-XXXX-XXXX-XXXXXXXXA4F6,0x28,0x64000)
    • However, it’s hard to determine that this is the volume that you want, based only on the user-friendly name ‘EFI’ in the boot.log and hard to determine what the volume ID is.
      • It’s much easier to boot into the Clover boot loader, and then highlight the volume of interest, and hit <Spacebar> to get the volume ID
      • Note however, that for some reason the path to the boot file has an extra ‘i’ at the end
      • Clover boot loader also doesn’t wrap the lines so if the name is really long you won’t be able to see the end part of the path
  • Also note that the volume ID for the OSX EFI boot volume is not hyphenated, while the one for Windows is. This matters, as whatever is being reported from the boot subsystem must match what you define in your config.plist
  • Like 1
Link to comment
Share on other sites

  • 1 year later...

Does the first post still apply to Big Sur?

With new clover changes main partition is now hidden from GUI to leave the proper boot volume, Preboot. I would like to have a custom entry for this but using the old instructions I cannot get it to work like it used too. 

Link to comment
Share on other sites

i am not sur, but this is still for high sierra, mojave, catalina.

 

is this script inside Clover configurator ?

(for instance, all get forme diskutil list and distutil apfs list), when we create a new entry, a selected disk by name ans diskxsy could choice to automati fill some

information (UUId, recover, preboot, etc...), and we complet to validate if need

 

Link to comment
Share on other sites

On 10/21/2020 at 2:46 PM, SavageAUS said:

Does the first post still apply to Big Sur?

With new clover changes main partition is now hidden from GUI to leave the proper boot volume, Preboot. I would like to have a custom entry for this but using the old instructions I cannot get it to work like it used too. 

 

Short answer: Yes.

 

Here is my custom entry for Big Sur Beta10_20A5395g, using latest Clover_r5125_d0388ee7a

		<key>Custom</key>
		<dict>
			<key>Entries</key>
			<array>
				<dict>
					<key>Disabled</key>
					<false/>
					<key>FullTitle</key>
					<string>macOS Big Sur</string>
					<key>Image</key>
					<string>os_bigsur.icns</string>
					<key>Hidden</key>
					<false/>
					<key>InjectKexts</key>
					<true/>
					<key>NoCaches</key>
					<false/>
					<key>Path</key>
					<string>\EC2BD3BC-03F9-3D1E-920F-A352B4DE5867\System\Library\CoreServices\boot.efi</string>
					<key>Type</key>
					<string>OSX</string>
					<key>Volume</key>
					<string>95874DAF161EDF4E9AF37CABBBE2E124</string>
				</dict>

Clover GUI Screenshots...

Spoiler

custom_entry1.thumb.png.5188717d984f77b07a25c5f020407da4.pngcustom_entry2.thumb.png.bb0d331b0c64b059df5787d70a4c1d70.pngcustom_entry3.thumb.png.6d595c1348a4e9d5e85e991d16a28225.pngcustom_entry4.thumb.png.e433738187c1b810afbbe2e09dfd7519.png

 

Relevant Diskutil Info from Terminal and Clover Boot Log...

Spoiler

usion71au@fusion71ausiMac ~ % 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:         Microsoft Reserved                         134.2 MB   disk0s2
   3:       Microsoft Basic Data WIN10                   128.3 GB   disk0s3
   4:           Windows Recovery                         579.9 MB   disk0s4
   5:                 Apple_APFS Container disk2         60.9 GB    disk0s5
   6:                 Apple_APFS Container disk3         59.4 GB    disk0s6

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:       Microsoft Basic Data DATA                    871.1 GB   disk1s2
   3:           Linux Filesystem                         120.0 GB   disk1s3
   4:                 Linux Swap                         8.6 GB     disk1s4

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +60.9 GB    disk2
                                 Physical Store disk0s5
   1:                APFS Volume Macintosh SSD — Data    9.8 GB     disk2s1
   2:                APFS Volume Preboot                 402.9 MB   disk2s2
   3:                APFS Volume Recovery                655.1 MB   disk2s3
   4:                APFS Volume VM                      1.1 MB     disk2s4
   5:                APFS Volume                         15.6 GB    disk2s5
   6:                APFS Volume Update                  458.8 KB   disk2s6

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +59.4 GB    disk3
                                 Physical Store disk0s6
   1:                APFS Volume macOS Catalina — Data   26.4 GB    disk3s1
   2:                APFS Volume Preboot                 83.8 MB    disk3s2
   3:                APFS Volume Recovery                529.0 MB   disk3s3
   4:                APFS Volume VM                      3.2 GB     disk3s4
   5:                APFS Volume macOS Catalina          11.3 GB    disk3s5

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.9 GB    disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:                  Apple_HFS Install macOS Big Su... 15.5 GB    disk4s2


Big Sur  — Data UUID on disk2s1
fusion71au@fusion71ausiMac ~ % diskutil info disk2s1 | grep UUID
   Volume UUID:               EC2BD3BC-03F9-3D1E-920F-A352B4DE5867
   Disk / Partition UUID:     EC2BD3BC-03F9-3D1E-920F-A352B4DE5867

Preboot UUID on disk2s2
fusion71au@fusion71ausiMac ~ % diskutil info disk2s2 | grep UUID
   Volume UUID:               AF4D8795-1E16-4EDF-9AF3-7CABBBE2E124 (Big Endian Format)
                              95874DAF-161E-DF4E-9AF3-7CABBBE2E124 (Converted to Little Endian Format as seen in Clover boot log)
                             =95874DAF161EDF4E9AF37CABBBE2E124 (removing the dashes)

 

  • In Big Sur Beta10, booting can only happen through the Preboot Entry, not the main Big Sur Entry —> hence we do not hide Preboot but actually use it to boot.  Latest Clover automatically hides the main Big Sur Entry.
  • No "Ignore" key anymore under Custom Entry
  • All kexts placed in /EFI/CLOVER/kexts/Other folder (since there is no auto detection of macOS version for Custom Entry)
  • Image file was PNG photo that is 128 by 128 pixels copied to root of Preboot Volume (in this eg named “os_bigsur.icns” but use whatever name you want)
Link to comment
Share on other sites

Hi everyone, for the love of me I cannot get Pre-OC clover 5123.1 to show any custom icons/entries in boot screen...

What is the needed setting for SCAN key and HIDE? Do they impact the display of custom entries?

Do we need to Scan Entries if we use Custom ones?

Do custom entries show up as "additional" icons on top of scanned ones?

        <key>Scan</key>
        <dict>
            <key>Tool</key>
            <true/>
            <key>Entries</key>
            <true/>
            <key>Legacy</key>
            <false/>
            <key>Linux</key>
            <false/>
        </dict>

If I set Entries=false I get zero icons to choose from, none... and nothing by pressing F3 in the boot screen, either...

 

Can someone share his/her working config.plist with Catalina please, so I can see what is the structure? And the UUID for Catalina entry, is it the one found via:

diskutil info disk1s5 | grep -i "Partition UUID" | rev | cut -d' ' -f 1 | rev

....where disk1s5 is the volume inside disk0 where the Volume for main Catalina is registered and not the container? After doing diskutil list of course:

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *512.1 GB   disk0
   1:                        EFI NUC                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         511.9 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +511.9 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Sabrent SSD - Data      166.5 GB   disk1s1
   2:                APFS Volume Preboot                 82.8 MB    disk1s2
   3:                APFS Volume Recovery                528.9 MB   disk1s3
   4:                APFS Volume VM                      1.1 MB     disk1s4
   5:                APFS Volume Sabrent SSD             11.1 GB    disk1s5

Thank you!

(not even close to making a custom Windows 10 entry from a different drive...)

Edited by MacKonsti
Link to comment
Share on other sites

OK everyone, here's an answer to myself that I post for everyone else to see.

 

Custom entries is quite tricky and very little documented. So here's the easy approach that I took after 50 like, reboots :)

 

Main Clover settings:

		<key>Scan</key>
		<dict>
			<key>Tool</key>
			<true/>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<false/>
			<key>Linux</key>
			<false/>
		</dict>

I am not using Linux in the same hack or disk as partition; moreover, Clover Configurator has a "kernel" option that I am not using at all, so not sure about that.

I am leaving Tool=true as this refers to UEFI Shell as I understand, that is visible with F3 button (hide/unhide).

 

Next, what to hide:

		<key>Hide</key>
		<array>
			<string>Legacy</string>
			<string>Preboot</string>
			<string>Recovery</string>
			<string>Windows</string>
		</array>

I see many people also add VM as entry or NO NAME (yes with space) and also \EFI\BOOT\BOOTX64.EFI as well, for now it was not needed. Not sure how old were these hacks and threads.

 

Open Hackintool, go to Logs tab and Boot and search for "Scan Loader" section, which will provide you the needed data for the custom icons:

0:550  0:000  === [ ScanLoader ] ==============================
0:550  0:000  - [01]: 'EFI'
0:591  0:041          AddLoaderEntry for Volume Name=EFI
0:591  0:000       skipped because path `PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0x0,0x0)\HD(1,GPT,FBE1ACEF-BC5C-494E-9793-46EE27B47E99,0x800,0x32000)\EFI\microsoft\Boot\bootmgfw.efi` already exists for another entry!
0:625  0:034          AddLoaderEntry for Volume Name=EFI
0:625  0:000      Not match custom entry 1: Volume: not match, Path: not match, Type: not match
0:625  0:000      Not match custom entry 2: Volume: not match, Path: not match, Type: not match
0:625  0:000  IconName=unknown comma=-1 size=7
0:625  0:000    Full=unknown
0:625  0:000   Show badge as Drive.
0:625  0:000      Loader entry created for 'PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0x0,0x0)\HD(1,GPT,FBE1ACEF-BC5C-494E-9793-46EE27B47E99,0x800,0x32000)\EFI\BOOT\BOOTX64.efi'
0:625  0:000  - [06]: 'EFI'
0:626  0:000          AddLoaderEntry for Volume Name=EFI
0:626  0:000       skipped because path `PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(1,GPT,66EB8733-50FE-4BD9-AF52-BE988DD6F9DD,0x28,0x64000)\EFI\BOOT\BOOTX64.efi` is self path!
0:626  0:000  - [08]: 'Preboot'
0:627  0:000          AddLoaderEntry for Volume Name=Preboot
0:627  0:000      Skipped because matching custom entry 1!
0:627  0:000      Not match custom entry 2: Volume: match, Path: not match, Type: not match
0:627  0:000      hibernated: set as never
0:627  0:000  IconName=cata,mac comma=4 size=8
0:627  0:000    first=os_cata
0:627  0:000   Show badge as Drive.
0:627  0:000      Loader entry created for 'PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,E2DE3E57-FA51-4335-9421-BD3F281C2573,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,48BF21CC28A11F46918C8D4998D9B09B)\B529F40F-E665-4957-BBD1-72CEF40763F7\System\Library\CoreServices\boot.efi'
0:628  0:000  - [09]: 'Intel NVMe - Data'
0:628  0:000  - [10]: 'Recovery'
0:628  0:000          AddLoaderEntry for Volume Name=Recovery
0:628  0:000      Not match custom entry 1: Volume: match, Path: not match, Type: not match
0:628  0:000      Skipped because matching custom entry 2!
0:628  0:000  IconName=cata,mac comma=4 size=8
0:628  0:000    first=os_cata
0:629  0:000   Show badge as Drive.
0:629  0:000      Loader entry created for 'PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,E2DE3E57-FA51-4335-9421-BD3F281C2573,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,DC876E7CCD92DA43B338B142C5D6A43A)\B529F40F-E665-4957-BBD1-72CEF40763F7\boot.efi'
0:629  0:000  - [11]: 'VM'
0:629  0:000  - [12]: 'Intel NVMe'
0:631  0:001          AddLoaderEntry for Volume Name=Intel NVMe
0:631  0:000       skipped because path `PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,E2DE3E57-FA51-4335-9421-BD3F281C2573,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,0FF429B565E65749BBD172CEF40763F7)\System\Library\CoreServices\boot.efi` already exists for another entry!
0:631  0:000  === [ AddCustomTool ] ===========================

Let's start first by creating on purpose the Preboot and Recovery icons.

 

We see that in this log section [08] Preboot reports "Loader entry created" for

PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,E2DE3E57-FA51-4335-9421-BD3F281C2573,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,48BF21CC28A11F46918C8D4998D9B09B)\B529F40F-E665-4957-BBD1-72CEF40763F7\System\Library\CoreServices\boot.efi

 

Take the 2 needed parts, the one after the HD(GPT, part and the past part that contains the booter i.e. after the right parenthesis including back-slash:

E2DE3E57-FA51-4335-9421-BD3F281C2573 --> Volume

\B529F40F-E665-4957-BBD1-72CEF40763F7\System\Library\CoreServices\boot.efi --> Path

 

This results to:

				<dict>
					<key>Ignore</key>
					<false/>
					<key>Hidden</key>
					<true/>
					<key>Volume</key>
					<string>E2DE3E57-FA51-4335-9421-BD3F281C2573</string>
					<key>FullTitle</key>
					<string>Catalina Preboot</string>
					<key>Disabled</key>
					<false/>
					<key>Type</key>
					<string>OSX</string>
					<key>Path</key>
					<string>\B529F40F-E665-4957-BBD1-72CEF40763F7\System\Library\CoreServices\boot.efi</string>
					<key>NoCaches</key>
					<false/>
					<key>InjectKexts</key>
					<true/>
				</dict>

Next find the section [10] Recovery and its "Loader entry created"

PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,E2DE3E57-FA51-4335-9421-BD3F281C2573,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,DC876E7CCD92DA43B338B142C5D6A43A)\B529F40F-E665-4957-BBD1-72CEF40763F7\boot.efi

 

Similarly to the above, we use the GPT information as the "Volume" and "Path" variables:

				<dict>
					<key>Ignore</key>
					<false/>
					<key>Hidden</key>
					<true/>
					<key>Volume</key>
					<string>E2DE3E57-FA51-4335-9421-BD3F281C2573</string>
					<key>FullTitle</key>
					<string>Catalina Recovery</string>
					<key>Disabled</key>
					<false/>
					<key>Type</key>
					<string>OSXRecovery</string>
					<key>Path</key>
					<string>\B529F40F-E665-4957-BBD1-72CEF40763F7\boot.efi</string>
					<key>NoCaches</key>
					<false/>
					<key>InjectKexts</key>
					<true/>
				</dict>

Do not get puzzled by the same entry for Volume, check that the Path is different; Preboot and Recovery exist within the same APFS container...

 

Finally, for the actual Catalina boot icon, we find from Hackintool log the name of our main boot drive on the desktop, in my case it's called Intel NVMe as [12]: 'Intel NVMe' and the entry

PciRoot(0x0)\Pci(0x1D,0x4)\Pci(0x0,0x0)\NVMe(0x1,52-C4-C1-91-38-E4-D2-5C)\HD(2,GPT,E2DE3E57-FA51-4335-9421-BD3F281C2573,0x64028,0x3B97D260)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,0FF429B565E65749BBD172CEF40763F7)\System\Library\CoreServices\boot.efi

				<dict>
					<key>Ignore</key>
					<false/>
					<key>Hidden</key>
					<false/>
					<key>Volume</key>
					<string>E2DE3E57-FA51-4335-9421-BD3F281C2573</string>
					<key>FullTitle</key>
					<string>Catalina</string>
					<key>Disabled</key>
					<false/>
					<key>Type</key>
					<string>OSX</string>
					<key>Path</key>
					<string>\System\Library\CoreServices\boot.efi</string>
					<key>NoCaches</key>
					<false/>
					<key>InjectKexts</key>
					<true/>
				</dict>

Despite the log saying "skipped because path XXX already exists for another entry" it is the correct one, you can recognise the same Volume UUID as Preboot and Recovery.

 

Finally, for my UEFI installation of Windows 10 (I stress this) in a second disk, the same procedure is followed. That one is more easy to recognise if Windows is installed in a different drive because of the path containing "Microsoft" namely [01]: 'EFI' as shown in my case:

PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0x0,0x0)\HD(1,GPT,FBE1ACEF-BC5C-494E-9793-46EE27B47E99,0x800,0x32000)\EFI\microsoft\Boot\bootmgfw.efi

 

Resulting to a rather simpler config:

				<dict>
					<key>Ignore</key>
					<false/>
					<key>Hidden</key>
					<false/>
					<key>Volume</key>
					<string>FBE1ACEF-BC5C-494E-9793-46EE27B47E99</string>
					<key>FullTitle</key>
					<string>Windows 10</string>
					<key>Disabled</key>
					<false/>
					<key>Type</key>
					<string>Windows</string>
					<key>Path</key>
					<string>\EFI\Microsoft\Boot\bootmgfw.efi</string>
					<key>NoCaches</key>
					<false/>
					<key>InjectKexts</key>
					<false/>
				</dict>

 

So these entries are working 100% and Preboot and Recovery are hidden (tag is set to TRUE) and I only get 2 custom entries on my Lenovo.

Hope this helps you guys.

Edited by MacKonsti
  • Like 4
Link to comment
Share on other sites

  • 1 month later...

Hi Guys, its possible rename Preboot Partition (and boot) to Big Sur 11.2 beta with Clover r5127?

Im need to know if Im try the first post tutorial if will be rename. Im use Windows 7 too. 

 

Thanks a lot!! 

Link to comment
Share on other sites

  • 4 weeks later...

Anybody here managed to

  1. create a GUI custom entry for Big Sur Preboot labeled "Big Sur" or alike so it does not always appear as "Mac OS X from Big Sur via Preboot" in Clover boot screen?
  2. hide the Big Sur system entry?

Still not working here neither with Clover 5128 nor with latest Clover nightly...

 

My system info: macOS installs and volume labels: Big Sur, Catalina, Mojave

 

Big Sur Preboot:
APFS volume name/ label: Preboot

 

Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x1,0xFFFF,0x0)\HD(6,GPT,233EA3E0-9DBD-49F2-8F51-DA57BCC54B87,0x8CF0000,0xDACB000)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,7BE84A7CA39E5F4C8755EACFB18751E5)

 

UUID: 233EA3E0-9DBD-49F2-8F51-DA57BCC54B87

 

APFS File System UUID: 7C4AE87B-9EA3-4C5F-8755-EACFB18751E5

 

APFS Container UUID: 2466E13F-E4BB-4B37-BD4D-DCD0E74E83CE, ApfsRole=0x10

 

APFS target UUID: BA2910E1-CEA3-4140-88E3-89C70BCF433E

 

Could you please share your GUI section from Clover config.plist if you have a working custom entry? Thanks.

Link to comment
Share on other sites

  • 7 months later...
×
×
  • Create New...