Clover General discussion

[Cyberdevs]

Yep the Clover installs the files on the root instead of the ESP 

 

here's the Diskutil list output:

 

Spoiler

cyberdevs@Cyberdevss-iMac ~ % 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:                 Apple_APFS Container disk2         499.9 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_APFS Container disk2         239.8 GB   disk1s2

 

/dev/disk2 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +739.7 GB   disk2

                                 Physical Stores disk1s2, disk0s2

   1:                APFS Volume Macintosh HD - Data     3.8 GB     disk2s1

   2:                APFS Volume Preboot                 81.0 MB    disk2s2

   3:                APFS Volume Recovery                526.8 MB   disk2s3

   4:                APFS Volume VM                      1.1 MB     disk2s4

   5:                APFS Volume Macintosh HD            10.3 GB    disk2s5

 

cyberdevs@Cyberdevss-iMac ~ %

 

another update by @ricoc90 request:

Spoiler

cyberdevs@Cyberdevss-iMac ~ % diskutil info /dev/disk0

   Device Identifier:         disk0

   Device Node:               /dev/disk0

   Whole:                     Yes

   Part of Whole:             disk0

   Device / Media Name:       ST3500418ASQ

 

   Volume Name:               Not applicable (no file system)

   Mounted:                   Not applicable (no file system)

   File System:               None

 

   Content (IOContent):       GUID_partition_scheme

   OS Can Be Installed:       No

   Media Type:                Generic

   Protocol:                  SATA

   SMART Status:              Verified

 

   Disk Size:                 500.1 GB (500107862016 Bytes) (exactly 976773168 512-Byte-Units)

   Device Block Size:         512 Bytes

 

   Read-Only Media:           No

   Read-Only Volume:          Not applicable (no file system)

 

   Device Location:           Internal

   Removable Media:           Fixed

 

   Solid State:               No

   Virtual:                   No

   Hardware AES Support:      No

 

cyberdevs@Cyberdevss-iMac ~ % diskutil info /dev/disk1

   Device Identifier:         disk1

   Device Node:               /dev/disk1

   Whole:                     Yes

   Part of Whole:             disk1

   Device / Media Name:       KINGSTON SHSS37A240G

 

   Volume Name:               Not applicable (no file system)

   Mounted:                   Not applicable (no file system)

   File System:               None

 

   Content (IOContent):       GUID_partition_scheme

   OS Can Be Installed:       No

   Media Type:                Generic

   Protocol:                  SATA

   SMART Status:              Verified

 

   Disk Size:                 240.1 GB (240057409536 Bytes) (exactly 468862128 512-Byte-Units)

   Device Block Size:         512 Bytes

 

   Read-Only Media:           No

   Read-Only Volume:          Not applicable (no file system)

 

   Device Location:           Internal

   Removable Media:           Fixed

 

   Solid State:               Yes

   Virtual:                   No

   Hardware AES Support:      No

 

cyberdevs@Cyberdevss-iMac ~ % diskutil info /dev/disk2

   Device Identifier:         disk2

   Device Node:               /dev/disk2

   Whole:                     Yes

   Part of Whole:             disk2

   Device / Media Name:       KINGSTON SHSS37A240G

 

   Volume Name:               Not applicable (no file system)

   Mounted:                   Not applicable (no file system)

   File System:               None

 

   Content (IOContent):       EF57347C-0000-11AA-AA11-00306543ECAC

   OS Can Be Installed:       No

   Media Type:                Generic

   Protocol:                  SATA

   SMART Status:              Verified

   Disk / Partition UUID:     23E80DC2-F0ED-4DA7-8598-19AAB272D305

 

   Disk Size:                 739.7 GB (739745759232 Bytes) (exactly 1444815936 512-Byte-Units)

   Device Block Size:         4096 Bytes

 

   Read-Only Media:           No

   Read-Only Volume:          Not applicable (no file system)

 

   Device Location:           Internal

   Removable Media:           Fixed

 

   Solid State:               Yes

   Virtual:                   Yes

   Hardware AES Support:      No

 

   This disk is an APFS Container.  APFS Information:

   APFS Physical Store:       disk1s2

   APFS Physical Store:       disk0s2

   Fusion Drive:              Yes

cyberdevs@Cyberdevss-iMac ~ %

 

[fusion71au]

On 7/10/2019 at 2:52 PM, Slice said:

ISO image must contain necessary drivers for UEFI boot from the DVD.

At least Fat.efi, HFS+, APFS, Aptio,

 

Or UEFI boot from DVD is impossible?

 

On 7/10/2019 at 9:26 PM, vector sigma said:

I was guessing about this. Isn't a legacy boot only with the cdboot used?

 

On 7/10/2019 at 9:35 PM, Slice said:

Yes, the ISO is designed for legacy boot (and it really works!). I am just not sure if UEFI boot is also possible.

 

After a bit of digging around, the answer is definitively YES, it is possible to pure UEFI boot from CD/DVD, but a lot depends on the (U)EFI firmware doing the booting.

 

The standard Clover ISO only consists of a single 10MB HFS+ volume which can be EFI booted by firmware that understands HFS+ eg Apple machines and VMware Virtual Machines.  For it to boot on standard PCs, however, only the legacy pathway is available via the cdboot/eltorito pathway.

 

On the other hand, Ubuntu and Linux Mint Installation ISOs have dual formats for UEFI boot or Legacy boot

1) A 2.4MB FAT efi.img that contains grubx64.efi and functions as a "mini" EFI, recognizable for UEFI booting by standard PCs

2) A much larger ISO9660 file system that has all of the installation files and can also boot via the legacy eltorito pathway.

 

I was able to adapt this procedure from the Debian Wiki: RepackBootableISO, to repack the Clover ISO with an extra 2.4MB FAT efi.img containing CLOVERX64.efi, UEFI drivers, FakeSMC, the embedded theme and a custom config.plist that works for @arsradu to test on his system....

 

 

Note: the About Clover GUI screen that shows firmware booting by American Megatrends (not Clover EFI so NOT legacy boot).....and it boots his system fine .

 

Ingredients needed to make a real UEFI bootable Clover CD/DVD

1) A special mbr_template that enables the booting off the 2.4MB FAT efi.img (extracted from Linux Mint 19.1 Installation ISO) ...

isohdpfx.bin ---> I saved it to /home/fusion71au/Downloads/CLOVER/isohdpfx.bin
2) A 2.4MB FAT efi.img that contains CLOVERX64.efi, UEFI drivers, FakeSMC, the embedded theme and a config.plist

3) xorriso utility in Linux (Homebrew version for OSX here).  I was able to compile Clover with Build_Clover.command, then repacked the Clover ISO with xorriso with the following terminal commands...

 

new_files=~/src/edk2/Clover/CloverPackage/sym/CloverCD
new_iso=~/src/edk2/Clover/CloverPackage/sym/CloverISO-5018/Clover-v2.5k-5018-X64_UEFI.iso
xorriso -as mkisofs \
> -r -V 'Clover-v2.5k-5018-X64.iso' \
> -o "$new_iso" \
> -J -J -joliet-long -cache-inodes \
> -isohybrid-mbr '/home/fusion71au/Downloads/Clover/isohdpfx.bin' \
> -b /usr/standalone/i386/cdboot \
> -boot-load-size 4 -boot-info-table -no-emul-boot \
> -eltorito-alt-boot \
> -e /EFI/CLOVER/efi.img \
> -no-emul-boot -isohybrid-gpt-basdat -isohybrid-apm-hfsplus \
> "$new_files"

End result....Clover-v2.5k-5018-X64_UEFI.iso

 

PS:

If you want to play around with that efi.img, you can mount it as a loop device in Linux...

 

Say it is in your ~/Downloads folder

Open terminal and type

sudo mkdir /media/floppy1

sudo mount -o loop ~/Downloads/efi.img /media/floppy1/

 

Should then see something like this....

 

You can add/delete files to the volume as the root user.  As you can see, I only have about 300kB left to play with .  To unmount the volume, just click the "eject" icon.

 

Edited July 20, 2019 by fusion71au
Update UEFI.iso with generic config.plist and AptioMemoryFix.efi instead of OsxAptioFix3Drv.efi

[arsradu]

@fusion71au I think it was a little more than "a bit of" digging around. :)) It was a lot of digging. In and around. All started from a simple question: if they can do it, why couldn't we?

 

Cheers! And thank you!

 

Edit: bdmesg added if you wanna take a look.

Terminal Saved Output Clover ISO UEFI

Edited July 18, 2019 by arsradu

[Sherlocks]

@vector sigma

latest clover vboxhfs default check was removed. is it right?

to work hfs, we have been use vboxhfs or hfsplus like current ApfsDriverLoader.efi in latest clover package.

old clover package vboxhfs default check. and script check if user have hfsplus.efi, then if have it, vboxhfs installation have been ignore.

with this log in install log

"Removing drivers64UEFI/VBoxHfs-64.efi driver because HFSPlus driver present"

 

r5027. i removed /Library/Preferences/com.projectosx.clover.installer.plist file.

the i capture this default drivers.

 

EDIT1

VirtualSMC.efi case is working

i checked this log

Removing UEFI/SMCHelper.efi driver because VirtualSMC driver present

Edited July 20, 2019 by Sherlocks

[joevt]

On 7/18/2019 at 12:58 AM, fusion71au said:

Ingredients needed to make a real UEFI bootable Clover CD/DVD

1) A special mbr_template that enables the booting off the 2.4MB FAT efi.img (extracted from Linux Mint 19.1 Installation ISO) ...

isohdpfx.bin ---> I saved it to /home/fusion71au/Downloads/CLOVER/isohdpfx.bin
2) A 2.4MB FAT efi.img that contains CLOVERX64.efi, UEFI drivers, FakeSMC, the embedded theme and a config.plist

3) xorriso utility in Linux (Homebrew version for OSX here).  I was able to compile Clover with Build_Clover.command, then repacked the Clover ISO with xorriso with the following terminal commands...

 

new_files=~/src/edk2/Clover/CloverPackage/sym/CloverCD
new_iso=~/src/edk2/Clover/CloverPackage/sym/CloverISO-5018/Clover-v2.5k-5018-X64_UEFI.iso
xorriso -as mkisofs \
> -r -V 'Clover-v2.5k-5018-X64.iso' \
> -o "$new_iso" \
> -J -J -joliet-long -cache-inodes \
> -isohybrid-mbr '/home/fusion71au/Downloads/Clover/isohdpfx.bin' \
> -b /usr/standalone/i386/cdboot \
> -boot-load-size 4 -boot-info-table -no-emul-boot \
> -eltorito-alt-boot \
> -e /EFI/CLOVER/efi.img \
> -no-emul-boot -isohybrid-gpt-basdat -isohybrid-apm-hfsplus \
> "$new_files"

End result....Clover-v2.5k-5018-X64_UEFI.iso

 

As you can see, I only have about 300kB left to play with .  To unmount the volume, just click the "eject" icon.

 

Is there a reason why the size of the efi image can't be greater than 2.4 MB?

[joevt]

On 7/16/2019 at 9:08 AM, vector sigma said:

Yeah, subscripting can be a solution. Did you try your self? ok, I'll do that as soon as I can. Anyway it is not enough since we need to ensure the file system is apfs and is writable. For the fs I can just make a shell script to something like:

diskutil info / | grep 'File System Personality:' |  awk '{print $NF}'

or just forgot about aeverything and see if the root volume is read-only: 

diskutil info / | grep 'Read-Only Volume:' | awk '{print $NF}'

but since I'm on 10.11 at job, I can't ensure what's on Catalina. So please anyone... check the above command in Catalina with both cases (fs rw or ro)

 

What does the mount command show for Catalina? The output will be more succinct and easier to parse than diskutil probably. It shows each device and the mount point and the mount flags (read-only, etc.).

mount

 

I use mount to see if a partition is already mounted or not, and mount it if it's not already mounted. Here's a script to mount all EFI partitions:

for slice in $(diskutil list | sed -nE '/^ *[0-9]+: +EFI .* (disk[0-9]+s[0-9]+)$/s//\1/p'); do
    mountpoint=$(mount | sed -n -E "/\/dev\/$slice on (.*) \(.*/s//\1/p")
    if [ -z $mountpoint ]; then
        i=0
        startmountpoint=/Volumes/EFI
        mountpoint=$startmountpoint
        while [ -d $mountpoint ]; do
            ((i++))
            mountpoint=$startmountpoint$i
        done
    fi
    if [ ! -d $mountpoint ]; then
        sudo mkdir $mountpoint 2> /dev/null
        sudo mount_msdos /dev/$slice $mountpoint
    fi
done

 

[Mork vom Ork]

one short question:

are the MEMORY FIX drivers just UEFI or

are the MEMORY FIX drivers LEGACY & UEFI (especialy the AptioMemoryFix.efi)?

 

never used LEGACY BIOS, that's why i ask.

[fusion71au]

On 7/21/2019 at 8:21 AM, joevt said:

Is there a reason why the size of the efi image can't be greater than 2.4 MB?

Good question. 

 

Since I was using the Linux Mint 19.1 ISO as my template for a UEFI bootable CD/DVD, I reused its isohybrid-mbr and 2.4MB FAT efi.img for creating the Clover UEFI ISO. 

 

I have since created a larger 10MB FAT efi.img...

mkfs.msdos -C ~/src/edk2/Clover/CloverPackage/sym/CloverCD/EFI/CLOVER/efi.img 10240

and compiled successfully with xorriso, Clover-v2.5k-5027-X64_UEFI.iso.zip.  This also EFI boots Catalina DP4 OK on my VMware12 virtual machine....

 

Awaiting @arsradu's real world testing on his system <--- Edit: confirmed working on real hardware.

 

 

 

On 7/21/2019 at 9:08 AM, Mork vom Ork said:

one short question:

are the MEMORY FIX drivers just UEFI or

are the MEMORY FIX drivers LEGACY & UEFI (especialy the AptioMemoryFix.efi)?

 

never used LEGACY BIOS, that's why i ask.

Yes, MEMORY FIX drivers are just for UEFI booting.  Never needed AptioMemoryFix.efi for Clover's legacy boot because Clover has its own EFI firmware (based on DUET, not Aptio).

 

Edited July 23, 2019 by fusion71au
ISO confirmed working with larger FAT efi.img (UEFI or Legacy boot), added extra kexts, BIOS drivers and more universal config.plist

[arsradu]

@fusion71au,  you know I was asking you the very same question, right? )

I’ll take a look later today. Bit busy right now.

 

EDIT: it boots perfectly fine.  Haven't tried Catalina (only Mojave), but I see no reason why it wouldn't boot that one, as well.

Edited July 21, 2019 by arsradu

[vector sigma]

18 hours ago, joevt said:

The output will be more succinct and easier to parse than diskutil probably. It shows each device and the mount point and the mount flags (read-only, etc.).

Hi, what we use is the below code in a java script function:

    var writable = true;
    var cmd = '[[ yes == $(diskutil info / | grep -i \'read-only volume:\' | awk \'{print $NF}\' | tr \'[:upper:]\' \'[:lower:]\') ]]'
    r = system.run('/bin/bash', '-c', cmd);
    system.log('checkFileSystemIsWritable diskutil result = ' + r);

    writable = (r != 0);
    
    if (writable) {
	....

 

18 hours ago, joevt said:

Here's a script to mount all EFI partitions:

Thanks but I'm unsure we need this. What is needed is to find the ESP that belongs to the target volume, volume that can be inside a contenitor, corestorage, apfs, fv2, raid (so also combined) etc...

[Guest ricoc90]

With fusion drives there is no EFI partition on the target volume (obviously), but both physical storage disks do contain an EFI partition.
 

So maybe we could just check if the target volume is a Fusion Drive:

# Returns "Yes" is fusion drive and exits non-zero if not
diskutil info the_target_volume | grep -i 'Fusion Drive:' | awk '{print $NF}'

and grab the first physical storage.

i.e.:

[Guest ricoc90]

# Check if volume is a Fusion drive
if [[ "$(echo $(LC_ALL=C diskutil info "$DiskDevice" | \
         grep -i 'Fusion Drive:' | \
         awk '{print $NF}'))" == *"Yes"* ]]; then

         # Volume is Fusion Drive, get its physical store

        realDisk=($(diskutil info "$DiskDevice" | \
                         grep -i 'APFS Physical Store:' | \
                         awk '{print $NF}'))

        echo Target volume "$1" on "$DiskDevice" is a Fusion Drive on physical store:

        for Disk in "${realDisk[@]}"
        do
            echo -e "\t$Disk"
        done

        DiskDevice=$(LC_ALL=C diskutil info "${realDisk[0]}" 2>/dev/null | \
                                             sed -n 's/.*Part [oO]f Whole: *//p')

        echo Using disk "$DiskDevice" for Clover installation
fi

Clover EFI installer log - Mon Jul 22 16:13:16 CEST 2019
Installer version: v2.5k r5027 EFI bootloader
======================================================
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         499.9 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *120.0 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         119.8 GB   disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +619.7 GB   disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD - Data     14.4 GB    disk2s1
   2:                APFS Volume Preboot                 43.5 MB    disk2s2
   3:                APFS Volume Recovery                520.4 MB   disk2s3
   4:                APFS Volume VM                      1.1 GB     disk2s4
   5:                APFS Volume Macintosh HD            10.0 GB    disk2s5

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *8.0 GB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Install macOS 10.15 ... 7.7 GB     disk3s2

Target volume /Volumes/Macintosh HD on disk2 is a Fusion Drive on physical store:
	disk0s2
	disk1s2
Using disk disk0 for Clover installation
======================================================
Backing up EFI files

Backing up stage2 file /Volumes/Macintosh HD/EFIROOTDIR/boot  to /Volumes/Macintosh HD/EFI-Backups/r5027/2019-07-22-16h13/boot
Backing up /Volumes/Macintosh HD/EFIROOTDIR/EFI folder to /Volumes/Macintosh HD/EFI-Backups/r5027/2019-07-22-16h13/EFI
No Active Partition

Stage 0 - Writing boot0af to /dev/rdisk0
dd if=/dev/rdisk0 count=1 bs=512 of=/tmp/origMBR
cp /tmp/origMBR /tmp/newMBR
dd if=//usr/standalone/i386/boot0af of=/tmp/newMBR bs=440 count=1 conv=notrunc
fdisk -f /tmp/newMBR -u -y /dev/rdisk0

Stage 1 - Writing boot1f32 to /dev/rdisk0s1
dd if=/dev/rdisk0s1 count=1 bs=512 of=/tmp/origbs
boot volume format is FAT32
cp /tmp/boot1f32 /tmp/newbs
dd if=/tmp/origbs of=/tmp/newbs skip=3 seek=3 bs=1 count=87 conv=notrunc
dd if=/tmp/newbs of=/dev/rdisk0s1

Stage 2 - Written boot6 (x64) to /Volumes/ESP/boot

======================================================
=========== Clover EFI Installation Finish ===========
======================================================

 

Edited July 23, 2019 by ricoc90

[joevt]

8 hours ago, ricoc90 said:

/dev/disk2

You hardcoded this disk device in your script.

[Guest ricoc90]

45 minutes ago, joevt said:

You hardcoded this disk device in your script.

 

Thanks

[vector sigma]

Hi Guys, attached a command line called espfinder. The purpose is to find the associated EFI partition that belong to a target volume using the Clover package. Here  actually works with or whitout apfs containers. CoreStorage isn't yet implemented but I'm confident that espfinder will give Us usefull informations about it, in fact this beta version make a dump at ~/Desktop/espfinder.plist.

 

Usage:

findesp disk2s4

(whole disks like disk0, disk2 etc. are not allowed)

 

@ricoc90, @Cyberdevs please, I need the dump from both of you. To All,  please confirm you can find the ESP from regular disks (whith apfs containers or other fs).

Thanks in advance

 

P.S. would be cool to have a dump from a RAID set up as well...

espfinder_0.1_beta.zip

[Slice]

10 minutes ago, vector sigma said:

Hi Guys, attached a command line called espfinder. The purpose is to find the associated EFI partition that belong to a target volume using the Clover package. Here  actually works with or whitout apfs containers. CoreStorage isn't yet implemented but I'm confident that espfinder will give Us usefull informations about it, in fact this beta version make a dump at ~/Desktop/espfinder.plist.

 

Usage:

findesp disk2s4

(whole disks like disk0, disk2 etc. are not allowed)

 

@ricoc90, @Cyberdevs please, I need the dump from both of you. To All,  please confirm you can find the ESP from regular disks (whith apfs containers or other fs).

Thanks in advance

 

P.S. would be cool to have a dump from a RAID set up as well...

espfinder_0.1_beta.zip

One drive with several partitions HFS+

espfinder.plist.zip

[vector sigma]

On 7/20/2019 at 3:17 PM, Sherlocks said:

@vector sigma

latest clover vboxhfs default check was removed. is it right?

to work hfs, we have been use vboxhfs or hfsplus like current ApfsDriverLoader.efi in latest clover package.

old clover package vboxhfs default check. and script check if user have hfsplus.efi, then if have it, vboxhfs installation have been ignore.

with this log in install log

"Removing drivers64UEFI/VBoxHfs-64.efi driver because HFSPlus driver present"

@Sherlocks removing the conflictual hfs driver works as intended.

: 

#!/bin/bash

#echo "DEBUG: $ 1 = Full path to the installation package the installer app is processing: " $1
#echo "DEBUG: $ 2 = Full path to the installation destination: " $2
#echo "DEBUG: $ 3 = Installation volume (mountpoint) to receive the payload: " $3
#echo "DEBUG: $ 4 = Root directory for the system: " $4

echo "preinstall: Path to installer....... $1"
echo "preinstall: Path to destination..... $2"
echo "preinstall: Path to dest volume..... $3"
echo "preinstall: Root of system folder... $4"

#############################################################################

DEST_VOL="${3}"
EFI_ROOT_DIR=$(cd "${DEST_VOL}"/EFIROOTDIR; pwd -P)
install_log="${DEST_VOL}/Clover_Install_Log.txt"
driver_dir="UEFI"
driver_name="HFSPlus.efi"

if [[ -d "$EFI_ROOT_DIR/EFI/CLOVER/drivers/$driver_dir" ]]; then
  cd "$EFI_ROOT_DIR/EFI/CLOVER/drivers/$driver_dir"
  if [[ $driver_name == VBoxHfs.efi ]]; then
    for driver in *.efi
    do
      low=$(echo $driver | tr '[:upper:]' '[:lower:]')
      if [[ $driver != $driver_name ]] && [[ "$low" == *hfsplus* || "$low" == *grubhfs* ]]; then
        echo "Removing ${driver_dir}/${driver} because $driver_name is installed!" >> "$install_log"
        rm -f $driver
      fi
    done
  elif [[ $driver_name == HFSPlus.efi ]]; then
    for driver in *.efi
    do
      low=$(echo $driver | tr '[:upper:]' '[:lower:]')
      if [[ $driver != $driver_name ]] && [[ "$low" == *boxhfs* || "$low" == *grubhfs* ]]; then
        echo "Removing ${driver_dir}/${driver} because $driver_name is installed!" >> "$install_log"
        rm -f $driver
      fi
    done
  elif [[ $driver_name == ApfsDriverLoader.efi ]]; then
    for driver in *.efi
    do
      low=$(echo $driver | tr '[:upper:]' '[:lower:]')
      if [[ $driver != $driver_name && "$low" == apfs.efi ]]; then
        echo "Removing ${driver_dir}/${driver} because $driver_name is installed!" >> "$install_log"
        rm -f $driver
      fi
    done
  fi
fi

You can see bugs? Consider that the above is a Post install script and this operation is only performed if you install a file system driver, i.e. HFSPlus in this case.

On 7/20/2019 at 3:17 PM, Sherlocks said:

r5027. i removed /Library/Preferences/com.projectosx.clover.installer.plist file.

the i capture this default drivers.



what for person like me that really doesn't have any hfs partition? . Anyway I'm not alone... so the the simplest and fastest solution is to remove VBoxHfs.efi from the package when HFSPlus.efi is present w/o messing with infinite statement in the Distribution file. 

2 hours ago, Slice said:

One drive with several partitions HFS+

You succeded finding the ESP?

Edited July 24, 2019 by vector sigma

[Guest ricoc90]

32 minutes ago, vector sigma said:

 

@ricoc90, @Cyberdevs please, I need the dump from both of you. To All,  please confirm you can find the ESP from regular disks (whith apfs containers or other fs).

Thanks in advance

Here you go for fusion drive: espfinder.plist.zip 

On my regular system it does find the ESP as it should:

[vector sigma]

2 hours ago, ricoc90 said:

On my regular system it does find the ESP as it should:

Good!

[Slice]

8 hours ago, vector sigma said:

 

You succeded finding the ESP?

Of course!

I proposed you see this in log.

Yes found with any arguments. disk0s4, disk0s7

[Cyberdevs]

@vector sigma

Sorry for the delay here's my log. I have one SSD and one HDD attached to the system and I made the Fusion Drive and I'm running Catalina at the moment.

 

Please let me know if there's anything else that you need me to do.

 

espfinder.plist.zip

[pkdesign]

Odd question. Shouldn’t I be able to boot into EFI shell from Clover menu? I do not have that option currently (see below) I just updated to 5018 but the last version didn’t have that menu option either. What am I missing?

 

 

EDIT:

Okay, I'm a bonehead. In my attempt to have a "pristine" or "clean" EFI folder, I deleted the folder with the shell in it! Doh! It works now.

 

Edited July 26, 2019 by pkdesign
SOLUTION

[arsradu]

8 minutes ago, pkdesign said:

Odd question. Shouldn’t I be able to boot into EFI shell from Clover menu? I do not have that option currently (see below) I just updated to 5018 but the last version didn’t have that menu option either. What am I missing?

 

I have it with 5028. Theme issue...? I've attached my 5028 if you wanna give it a try. 

 

Clover_v2.5k_r5028.zip

Edited July 25, 2019 by arsradu

[vector sigma]

11 hours ago, Slice said:

Of course!

I proposed you see this in log.

Yes found with any arguments. disk0s4, disk0s7

 

8 hours ago, Cyberdevs said:

@vector sigma

Sorry for the delay here's my log. I have one SSD and one HDD attached to the system and I made the Fusion Drive and I'm running Catalina at the moment.

 

Please let me know if there's anything else that you need me to do.

 

espfinder.plist.zip

thanks guys! @Cyberdevs in yours I've found something different, so I'm not sure if in Terminal the message was like 'ESP not found', anyway thanks to your log I'm pretty sure will be able in the next version.... version where the log will show me the result :-)

[Cyberdevs]

3 minutes ago, vector sigma said:

thanks guys! @Cyberdevs in yours I've found something different, so I'm not sure if in Terminal the message was like 'ESP not found', anyway thanks to your log I'm pretty sure will be able in the next version.... version where the log will show me the result :-)

Sure thing man, I will check again and create another log when I get back home and see if it differs from the first log and if it was different I will let you know.

 

Cheers