Jump to content

Search the Community: Showing results for tags 'APFS'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 5 results

  1. 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... 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... 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
  2. The latest issue with APFS comes in the form of introducing an extra 15 seconds of booting time when Trim is enabled. It is currently believed that the filesystem is performing a routine Trim-related cleanup process during this time, which is causing boot times to increase for users who want their SSD’s to benefit from Trim. Trim is an important feature for Solid State Drive performance and longevity. Some users who want to enable Trim on High Sierra may notice an increase in boot time for now. I am convinced this is an unintentional bug in APFS from Apple’s side that should be fixed in an upcoming version of High Sierra.
  3. Hello, I have installed High Sierra and I realised that my SSD drive was reformatted to APFS (without problems, I don't believe it). Now I was wondering if there are any tips to make it work better in a Hackintosh, because the performance I think is more or less the same that which HFS+. Thanks guys!
  4. So my High Sierra boot partition disappeared after HS GM install which is when I discovered there is no option to install without APFS. Well, that maybe the future but I don't want it. So, I removed it. My setup is a dual boot with Win 8 (I use it about once a month, by accident). My Mac boot disk is disk0s6, 70GB, and I have my user data on disk0s8, about 300GB, not the boot disk. This division allows quicker restores and less-dangerous upgrades as the data is always safe. You may need far more than 70GB depending on your applications so think about it before you do that split. I mention that because you have to destroy your boot disk in order to revert to HFS+; having to restore all of your data every time is both tedious and a little more dangerous than having it safely housed away from what ever APPLE has decided is best for us this week. So here are the steps: 1) Make a local USB Time Machine backup of your boot disk; you can use a network version (make sure it is up-to-date!) but the restore will take HOURS. 2) Install the High Sierra GM onto a bootable USB device 3) Migrate your previous backup onto the new install (if your USB is too small, do step 4 before step 3) 4) Boot into Recovery; using DISK Utility, restore the USB install onto your HFS+ boot partition. I'm staying on HFS+ as long as possible - the world is not ready for APFS and way too much stuff is affected without good alternatives.
  5. I just tried to update a Sierra hackintosh to High Sierra, checking the update to APFS checkmark and now after the install, I cannot get to clover and when connecting the disk to a windows pc, it just sees unallocated space. Has the High Sierra installer just wiped the whole disk? Are there issues when using APFS with an MBR disk?
×