PoisonApple666 Posted October 27, 2017 Share Posted October 27, 2017 I'm running old stuff...P67 vintage...High Sierra installs with little trouble and seems to run nice with the new file system off of an SSD. But since I'm forced to use Clover in legacy mode...EFI...how can I get that onto the SSD with APFS? Probs been asked already but I'ma gonna ask it anyway... Any help or pointers in the right direction appreciated R. Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 27, 2017 Share Posted October 27, 2017 I'm running old stuff...P67 vintage...High Sierra installs with little trouble and seems to run nice with the new file system off of an SSD. But since I'm forced to use Clover in legacy mode...EFI...how can I get that onto the SSD with APFS? Probs been asked already but I'ma gonna ask it anyway... Any help or pointers in the right direction appreciated R. Just put the apfs.efi into /efi/clover/drivers64 folder and clover will show you the APFS formatted volume so you can boot from it. Link to comment Share on other sites More sharing options...
Guest ricoc90 Posted October 27, 2017 Share Posted October 27, 2017 There have been some issues on installing Clover on APFS, however in the latest versions this has been fixed.So you can just install Clover on your SSD as how you usually would do it and indeed, like cyberdevs said, put apfs.efi in /efi/clover/drivers64.apfs.efi can be located at /usr/standalone/i386/ (hit shift + windows key (or command key if using Apple keyboard) + . to show hidden files) Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 28, 2017 Author Share Posted October 28, 2017 Thanks guys...I did all that and I can see the High Sierra disk...it has 3 other partitions...preboot and such, but no efi. What am I doing wrong? Is EFI somewhere else? Is it called something else? Should I dynamite what I have and start over? signed, Confused. Link to comment Share on other sites More sharing options...
HBP Posted October 28, 2017 Share Posted October 28, 2017 use disk util and list the partitions, on the host disk (not the disk that is formatted APFS, because that is inside a container on the host disk) there should be 2 partitions, EFI and Apple_APFS Container here is an example /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *320.1 GB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_APFS Container disk3 319.9 GB disk2s2 /dev/disk3 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +319.9 GB disk3 Physical Store disk2s2 1: APFS Volume OSX_HS 28.5 GB disk3s1 2: APFS Volume VM 9.7 GB disk3s2 3: APFS Volume Preboot 19.8 MB disk3s3 4: APFS Volume Recovery 20.5 KB disk3s4 5: APFS Volume OSX_HS2 24.0 GB disk3s5 the disk3 is what is inside the container disk2 is what is the Physical disk. HBP Link to comment Share on other sites More sharing options...
Cyberdevs Posted October 28, 2017 Share Posted October 28, 2017 Thanks guys...I did all that and I can see the High Sierra disk...it has 3 other partitions...preboot and such, but no efi. What am I doing wrong? Is EFI somewhere else? Is it called something else? Should I dynamite what I have and start over? signed, Confused. The EFI partition must be there, nothing has changed about the structure of the GUID partition scheme regarding the EFI partition although there are major changes on how macOS handles the data on an APFS formatted partition. You can run diskutil list command and you'll find the EFI partition outside the APFS container. Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 28, 2017 Author Share Posted October 28, 2017 use disk util and list the partitions, on the host disk (not the disk that is formatted APFS, because that is inside a container on the host disk) there should be 2 partitions, EFI and Apple_APFS Container here is an example /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *320.1 GB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_APFS Container disk3 319.9 GB disk2s2 /dev/disk3 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +319.9 GB disk3 Physical Store disk2s2 1: APFS Volume OSX_HS 28.5 GB disk3s1 2: APFS Volume VM 9.7 GB disk3s2 3: APFS Volume Preboot 19.8 MB disk3s3 4: APFS Volume Recovery 20.5 KB disk3s4 5: APFS Volume OSX_HS2 24.0 GB disk3s5 the disk3 is what is inside the container disk2 is what is the Physical disk. HBP I will try this...thanks Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 29, 2017 Author Share Posted October 29, 2017 use disk util and list the partitions, on the host disk (not the disk that is formatted APFS, because that is inside a container on the host disk) there should be 2 partitions, EFI and Apple_APFS Container here is an example /dev/disk2 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *320.1 GB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_APFS Container disk3 319.9 GB disk2s2 /dev/disk3 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +319.9 GB disk3 Physical Store disk2s2 1: APFS Volume OSX_HS 28.5 GB disk3s1 2: APFS Volume VM 9.7 GB disk3s2 3: APFS Volume Preboot 19.8 MB disk3s3 4: APFS Volume Recovery 20.5 KB disk3s4 5: APFS Volume OSX_HS2 24.0 GB disk3s5 the disk3 is what is inside the container disk2 is what is the Physical disk. HBP ok...I used diskutil list and found the physical drive and the efi partition was there just as you said it would be. so that part is groovy. however, when I use diskutil mount /dev/disk4s1 I get diskutil mount /dev/disk4s1 Volume on disk4s1 failed to mount If the volume is damaged, try the "readOnly" option so...am i attempting to mount this incorrectly to get to this partition to install clover, or is my installation of high sierra incorrect, or I dunno Thanks R. Link to comment Share on other sites More sharing options...
foskvs Posted October 29, 2017 Share Posted October 29, 2017 ok...I used diskutil list and found the physical drive and the efi partition was there just as you said it would be. so that part is groovy. however, when I use diskutil mount /dev/disk4s1 I get diskutil mount /dev/disk4s1 Volume on disk4s1 failed to mount If the volume is damaged, try the "readOnly" option so...am i attempting to mount this incorrectly to get to this partition to install clover, or is my installation of high sierra incorrect, or I dunno Thanks R. Try to mount it by using Clover Configurator. Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 29, 2017 Author Share Posted October 29, 2017 Try to mount it by using Clover Configurator. ok...good idea....I'll try that. thanks R. 1 Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 30, 2017 Author Share Posted October 30, 2017 Try to mount it by using Clover Configurator. nope....no luck should i try a fresh install? any opinions welcome thanx R. Link to comment Share on other sites More sharing options...
HBP Posted October 30, 2017 Share Posted October 30, 2017 nope....no luck should i try a fresh install? any opinions welcome thanx R. first question to ask is how did you install clover? if you have not formatted the EFI partition fat32 then it probably will not mount in clover configurator because it does not see that partition as being a valid partition. so... time to get Scary. mess up and this will Screw your machine. <code> diskutil list diskutil eraseVolume FAT32 EFI /Volumes/DiskXs1 // **note X is the drive you want to reformat the EFI partition on. </code> then run clover installer and chose the EFI options and tell it you need to modify the boot record, (I believe at this point they have modified the installer to look for the Host disk vs the APFS disks) and this should make a bootable clover install. if not, let me know and I can ether point you to the guides to manually install the clover boot loader(a pain in the butt, or write a quick guide on the process.) HBP Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 30, 2017 Author Share Posted October 30, 2017 first question to ask is how did you install clover? if you have not formatted the EFI partition fat32 then it probably will not mount in clover configurator because it does not see that partition as being a valid partition. so... time to get Scary. mess up and this will Screw your machine. <code> diskutil list diskutil eraseVolume FAT32 EFI /Volumes/DiskXs1 // **note X is the drive you want to reformat the EFI partition on. </code> then run clover installer and chose the EFI options and tell it you need to modify the boot record, (I believe at this point they have modified the installer to look for the Host disk vs the APFS disks) and this should make a bootable clover install. if not, let me know and I can ether point you to the guides to manually install the clover boot loader(a pain in the butt, or write a quick guide on the process.) HBP that is scary...fortunately high sierra is on a completely separate disk I will try this and report back thanks very much R one question though...should this be done from inside high sierra or from my sierra setup? Thanks Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 31, 2017 Author Share Posted October 31, 2017 tried the re-writing of the efi partition in both high sierra and sierra and no luck...terminal can't find the partition. the disk can be mounted...or so says terminal...but the efi cannot...to terminal...it just doesn't exist. am I better of wiping the disk and setting up the 200mb efi partition as fat32 and then installing? any ideas appreciated, though i think i be a bit screwed until clover actually has the ability to read that partition and that may never happen because who wants to deal with older equipment. signed, flumoxed Link to comment Share on other sites More sharing options...
foskvs Posted October 31, 2017 Share Posted October 31, 2017 am I better of wiping the disk and setting up the 200mb efi partition as fat32 and then installing? I suppose you're booting in UEFI mode. In this case, if you erase your disk with GUID partition table, you will have a 200MB EFI partition at diskXs1. There's no need to create it manually. Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 31, 2017 Author Share Posted October 31, 2017 no...not in uefi...I don't believe my old motherboard supports that...i was trying for a legacy install Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 31, 2017 Author Share Posted October 31, 2017 OK...I got it to work...I found a youtube vid that gave these instructions from terminal: sudo newfs_msdos -v EFI -F 32 /dev/diskXs1 from there I can mount the EFI on the high sierra disk and install clover. Thanks to everyone for your help Greatly appreciated. R. Link to comment Share on other sites More sharing options...
HBP Posted October 31, 2017 Share Posted October 31, 2017 OK...I got it to work...I found a youtube vid that gave these instructions from terminal: sudo newfs_msdos -v EFI -F 32 /dev/diskXs1 from there I can mount the EFI on the high sierra disk and install clover. Thanks to everyone for your help Greatly appreciated. R. That is the underlying command that the diskutil uses to format a partition. HBP Link to comment Share on other sites More sharing options...
PoisonApple666 Posted October 31, 2017 Author Share Posted October 31, 2017 thats interesting...why did that work and the higher level command didn't? seems curious. Link to comment Share on other sites More sharing options...
PoisonApple666 Posted November 4, 2017 Author Share Posted November 4, 2017 thanks to everyone for your help!!! Link to comment Share on other sites More sharing options...
HBP Posted November 5, 2017 Share Posted November 5, 2017 Probably a glitch with diskutil. Stranger things have happened. I am glad that it worked. HBP Link to comment Share on other sites More sharing options...
Recommended Posts