boot.efi developer's thread

Discussion in 'Mac Programming' started by mikeboss, Oct 2, 2015.

  1. iMattux macrumors member

    Joined:
    Oct 6, 2015
    #826
    A picture is worth a thousand words:

    Screen Shot 2015-11-12 at 7.16.55 PM.png

    I show hidden files all the time and prefer column view. The drives that are involved are up top, you can disregard the drives on the lower portion of the Desktop. Everything is it's proper place... How the hell does my install log have no mention of "pikify"? :confused:o_O
     
  2. OGNerd macrumors member

    OGNerd

    Joined:
    Jun 1, 2015
    #827
    My basic machine profile is as follows -

    Model Name:
    Mac Pro
    Model Type: 8-core
    Model Identifier: MacPro2,1
    Board Identifier: Mac-F42C88C8
    Processor Name: Quad-Core Intel Xeon CPU X5365
    Processor Model: Clovertown
    Processor Speed: 3 GHz
    Number of Processors: 2
    Total Number of Cores: 8
    Memory Size: 32 GB 667 MHz DDR2 FB-DIMM
    Graphics Model: AMD Radeon HD 7950 3072 MB
    Boot ROM Version: MP21.007F.B06
    System SMC Version: 1.15f3

    My primary El Capitan boot drive is a 1TB SSD in a PCIe slot, but I also boot from Yosemite or Mavericks partitions on a 1TB fusion drive, as well as Carbon Copy clones of the three on partitions of a 2TB spinner. I also have a 2TB spinner dedicated to TimeMachine, and another 2TB spinner for shared data.

    16GB flash media created by CREATEINSTALLMEDIA and DISK MAKER X 5 both failed with an Essentials.pkg extraction error. I was only able to successfully install 10.11 on my MP 2,1 via Target Disk mode from a supported MBP 8,2.
     
  3. iMattux macrumors member

    Joined:
    Oct 6, 2015
    #828
    MacPro1,1 =>2,1, stock Xeon5150's, 8G of RAM, Gigabyte Radeon HD7950 3GB factory overclocked, flashed for bootscreens, Cinebench =35.8fps, it's working fine. A ridiculous collection of hard drives... lol

    The super fantastic news is that after a few weeks of struggling with kernel panics, I am finally stable. It was my RAM. I suspect the OEM 4x512 MB DIMMs were the problem, but I don't care to prove it at the moment.

    I pulled them and the add'l 2GB from OWC out and replaced them with 4x2GB matched DIMMS.
    After shuffling them around, I'm rock solid. I'll be throwing another 16GB on top and I'll be very happy to stop tinkering with my computer and start using it. Then maybe I'll swap in faster CPU's and an SSD or two. Or maybe a used 3.1 on eBay...

    DGWilson - I strongly recommend you get the RAM I linked. It did the trick for me.

    I'll try running the script again tmrw and see if we can track something down.

    Cheers
     
  4. PeterHolbrook macrumors 6502a

    Joined:
    Sep 23, 2009
    #829
    Of course it was. I'm glad you solved your issue.
     
  5. dgwilson macrumors member

    dgwilson

    Joined:
    Feb 8, 2015
    Location:
    Wellington, New Zealand
    #830
    Ordered. On slow boat to New Zealand. ETA was after 24 Nov.
    I did swap RAM between the two x machines that I have so that there are only 1GB DIMMs in the machine ... it totals 6GB.

    - David
     
  6. TimeFire macrumors newbie

    Joined:
    Nov 4, 2015
    #831
    It's true: it's the RAM.

    Problem solved for me too.

    Bought 8 of these: http://www.ebay.com/itm/161781548424

    Probably the cheapest here in Europe, but they work.

    I hope dgwilson will finally fix it with new RAM.

    Thanks everyone for the help. I wish Pike all the best and I hope he'll get better.

    In the end, like everyone says: sorry for my bad english.
     
  7. Inspector42 macrumors newbie

    Inspector42

    Joined:
    Nov 8, 2015
    Location:
    Germany
    #832
    I can report that this worked flawlessly on my MacPro, even the restart countdown started without interaction.
    The installer was created on a HD partition and OS X installed on another wiped HD partition.
    Many thanks to Pike, Peter, Mike, rthpjm and all the other contributors for making this work.

    My thoughts go to Pike and his family. I hope he will fully recover.
     
  8. 666sheep, Nov 14, 2015
    Last edited: Nov 14, 2015

    666sheep macrumors 68040

    666sheep

    Joined:
    Dec 7, 2009
    Location:
    Poland
    #833
    I tried this today. What a weird result I got :)

    Installer building went OK, my 2006 booted normally off of it.
    Installation process went fine as well, but after the restart it booted straight to recovery partition.
    On OS partition I saw only "private" folder, but 9GB of drive space were used.
    I put the SSD in 2009 and all was the same. No trace of System, Library etc folders.
    Anyone here got similar experience?

    I built the Installer thumb drive on 10.8.5, on a MP 2009. El Capitan installer app was pure 10.11 (not the 10.11.1).

    P.S. I'm suspecting some RAM issue, because after reinstalling with classical (another compatible Mac) method I got a few KP's when updating to 10.11.1 from AppStore.
    New RAM is on the way, so I'll re-test this in a few days.

    P.S.2: CapitanPikeFix which I posted in installation thread works like it should. With SIP disabled of course.
     
  9. PeterHolbrook macrumors 6502a

    Joined:
    Sep 23, 2009
    #834
    "CapitanPike" sounds funny. Considering Pike lives in Spain, perhaps it should be CapitánPike. In any case, I hope everyone using this particular launch daemon is conscious that, by running a SIP-less El Capitan, you are running an operating system with no more safety than Yosemite. If that is so (and it is), why upgrade from Yosemite at all?
     
  10. currymac macrumors newbie

    Joined:
    Jul 5, 2008
    Location:
    Nova Scotia
    #835
    I downloaded pikify3.1.zip and successfully created an installer thumb drive. It successfully boots my MacPro 1,1. First I attempted to update the perfectly functional Yosemite OS that's running on an SSD in a PCI card. It gets to about 2 minutes remaining but then the computer reboots before completing the install. The computer reboots to the thumb drive and asks to start the install as if nothing happened. In case this was because I was trying to update, I installed a 1TB hard drive, booted into the installer, formatted the drive and tried an install. I ended up with the same result. Any ideas would be appreciated. Also, if I remove the SSD and upgrade it to El Capitan on my Macbook Pro, what do I have to do before I put it back in my Mac Pro?
     
  11. 666sheep macrumors 68040

    666sheep

    Joined:
    Dec 7, 2009
    Location:
    Poland
    #836
    Peter: to each its own I guess.
    Someone finds SIP as a bless, someone as PITA.
    El Capitan fortunately provides some more than only this POS ;)
     
  12. PeterHolbrook, Nov 14, 2015
    Last edited: Nov 14, 2015

    PeterHolbrook macrumors 6502a

    Joined:
    Sep 23, 2009
    #837
    Two or three people have commented having mystifying unsuccessful installation attempts such as yours. In the end, everything boiled down to bad RAM. I suggest that you check yours.
     
  13. currymac macrumors newbie

    Joined:
    Jul 5, 2008
    Location:
    Nova Scotia
    #838
    Well, the computer worked perfectly with Yosemite, and the RAM is brand new from OWC.
     
  14. rthpjm, Nov 15, 2015
    Last edited: Nov 15, 2015

    rthpjm macrumors 6502

    rthpjm

    Joined:
    Jan 31, 2011
    Location:
    U.K.
    #839
    Hello currymac,

    Can you take a look in the /Volumes/[your_target_install_disk(your 1TB drive)]/private/var/log/ please? In that folder you should find the file install.log. Post a copy of it here and I'll take a look. If you're using the Finder, open the disk then press the key combination [shift][cmd]g, a panel will open, type var, hit the [Go] button, then open the log folder.
    If it is not there, try to re-run the installer, whilst the installer is running open the log viewer (from the menus or press [cmd]L). There's a save icon top right of the log window, try to save the log just before the reboot.

    If you do this, then you will need to replace the two boot.efi files located at /Volumes/[your_disk]/System/Library/CoreServices/boot.efi and /Volumes/[your_disk]/usr/standalone/i386/boot.efi before you put it back into your Mac.
    You should probably bless the disk too, from the terminal run:
    Code:
    sudo bless --folder "/Volumes/[your_disk]/System/Library/CoreServices" --file "/Volumes/[your_disk]/System/Library/CoreServices/boot.efi"
    [your password]
    There is more to do if you want the accompanying Recovery HD to work too....
     
  15. currymac macrumors newbie

    Joined:
    Jul 5, 2008
    Location:
    Nova Scotia
    #840
    Here is the install.log
     

    Attached Files:

  16. rthpjm macrumors 6502

    rthpjm

    Joined:
    Jan 31, 2011
    Location:
    U.K.
    #841
    Hello currymac,

    Everything looks fine until you got to near the end of the installation process, then this happened:
    Code:
    Nov 14 05:55:09 Mac-Pro OSInstaller[469]: PackageKit: update_dyld_shared_cache - root /Volumes/El Capitan/.OSInstallSandboxPath/Root
    Nov 14 05:55:35 Mac-Pro OSInstaller[469]: update_dyld_shared_cache(548,0x10472c000) malloc: *** error for object 0x7f81338568b8: incorrect checksum for freed object - object was probably modified after being freed.
    Nov 14 05:55:35 Mac-Pro OSInstaller[469]: *** set a breakpoint in malloc_error_break to debug
    Nov 14 05:55:35 Mac-Pro OSInstaller[469]: update_dyld_shared_cache exited with 6 Nov 14 05:55:35 Mac-Pro OSInstaller[469]: PackageKit: Triggering XPC service cache rebuild on next boot
    malloc is memory allocation. Sad to say but this looks like yet another memory issue. You'll need to check your RAM. Since you say the RAM is new, double check that it is installed okay (make sure the RAM sticks are properly seated and locked in). If that all seems to be okay, check the pairings, make sure you follow the recommended slot installation sequences, etc... Failing all else, eject all but two sticks, try again. Add two more sticks, repeat - the goal is to see if you can identify a problematic pair of memory sticks...

    I have a theory as to why the installer is highlighting RAM issues, I think it may be because the installer loads it's OS into RAM-disk, and hence will probably exercise a good deal more of your RAM than is usual.... (Just a theory mind you...!)
     
  17. mikeboss thread starter macrumors 6502a

    mikeboss

    Joined:
    Aug 13, 2009
    Location:
    switzerland
    #842
    there are some very good news over at Pike's blog. it appears that everything's going to be alright in the end. what a relief...
     
  18. PeterHolbrook macrumors 6502a

    Joined:
    Sep 23, 2009
    #843
    That's very good news indeed, Mike. Thank you for telling us.
     
  19. javirnat macrumors newbie

    javirnat

    Joined:
    Jun 14, 2015
    Location:
    Valldemossa (Baleares Spain)
    #844
    -------------------------------
    I feel very happy with these news , I hope Pike.R Alfa. can go back home as soon as possible .
    And he could be with us in these forums too.
    I have missed him.
    sorry for my bad english.
     
  20. Morpheo macrumors 6502a

    Morpheo

    Joined:
    Feb 26, 2014
    Location:
    Paris/Montreal
    #845
    wow. Thanks for the update! Now Pike get back to work goddammit! Vacation's over :D

    ...Awesome news.:)
     
  21. dgwilson macrumors member

    dgwilson

    Joined:
    Feb 8, 2015
    Location:
    Wellington, New Zealand
    #846
    RAM Received.
    I have achieved a successful installation.

    What's interesting is that I received 16GB of RAM - two packages.
    As I have two machines my idea was to install 8GB in each machine. So In Machine #1 - I removed all of the existing RAM and installed 2 x 2GB on Riser A, and 2 x 2GB on Riser B.
    - Installation of El Capitan failed ... usual story Essentials.pkg

    So Then I installed the remaining RAM (all the new stuff).
    4 x 4GB on Riser A, and 4 x 4GB on Riser B.
    - Installation of El Capitan successful


    I used the new magic installer creater as well... so nothing to do after the install either!


    I would be interested in someone else trying the installation on a machine with 8GB of RAM - do we have to have > xxGB to achieve the successful install?

    - David
     
  22. donjames macrumors member

    Joined:
    Feb 20, 2015
    Location:
    Henderson, Texas
    #847
    Hi,

    I successfully installed El Capitan on my Macpro1,1 using your script. When I first tried, I had only 6 gigabytes of ram and got the Essentials.pkg error message. I increased the ram to 12 gigabytes and the install went flawlessly.

    Thanks for all of your hard work.

    Thanks to Pike for all of his hard work.

    Sincerely,

    donjames
     
  23. donjames macrumors member

    Joined:
    Feb 20, 2015
    Location:
    Henderson, Texas
    #848
    Hi,

    I did a successful install with 12 GB of ram. Could not install with 6 GB ram.

    Don
     
  24. dgwilson macrumors member

    dgwilson

    Joined:
    Feb 8, 2015
    Location:
    Wellington, New Zealand
    #849
    Time for another update.

    Short story - Fusion Drive creation and OS Installation with 16GB RAM, and using "pikify3.1" to create the installer = SUCCESS!

    Slightly longer story....
    1. After the first successful OS install this morning to a HDD I recreated my Fusion drive - refer output below
    2. OS Install HDD was still attached from previous successful install.
    3. Reboot machine with Option key, select Install media (HDD)
    4. Boots with Apple logo - and basically even after 1 hour the after the progress line eventually completed - it had not gone any further
    5. rince and repeat step 4 - no change in result
    6. Reboot to El Capitan - previously installed earlier in the day
    7. destroy fusion drive
    8. Reboot machine with Option key, select Install media (HDD)
    9. Boots with Apple logo - and basically even after 1 hour the after the progress line eventually completed - it had not gone any further

    [Bugger]

    10. disconnect install media - install in MacBook Pro - recreate install media using "pikify3.1"
    11. Recreate Fusion Frive
    12. Reboot machine with Option key, select Install media (HDD)
    13. Boot success - install OS - success.


    ... so that was weird.

    - David


    Code:
    Davids-Mac-Pro:~ dgwilson$ diskutil list
    /dev/disk0 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *128.0 GB   disk0
      1:                        EFI EFI                     209.7 MB   disk0s1
      2:                  Apple_HFS SSD                     127.7 GB   disk0s2
    /dev/disk1 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *250.1 GB   disk1
      1:                        EFI EFI                     209.7 MB   disk1s1
      2:                  Apple_HFS MacPro09                249.2 GB   disk1s2
      3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    /dev/disk2 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *1.5 TB     disk2
      1:                        EFI EFI                     209.7 MB   disk2s1
      2:                  Apple_HFS Spare1.5TB              1.4 TB     disk2s2
    /dev/disk3 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *1.5 TB     disk3
      1:                        EFI EFI                     209.7 MB   disk3s1
      2:                  Apple_HFS HDD                     1.5 TB     disk3s2
    /dev/disk4 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *1.5 TB     disk4
      1:                        EFI EFI                     209.7 MB   disk4s1
      2:                  Apple_HFS ElTestO                 1.5 TB     disk4s2
      3:                 Apple_Boot Recovery HD             650.0 MB   disk4s3
    Davids-Mac-Pro:~ dgwilson$ diskutil cs create Fusion /dev/disk0 /dev/disk3
    Started CoreStorage operation
    Unmounting disk0
    Repartitioning disk0
    Unmounting disk
    Creating the partition map
    Rediscovering disk0
    Adding disk0s2 to Logical Volume Group
    Unmounting disk3
    Repartitioning disk3
    Unmounting disk
    Creating the partition map
    Rediscovering disk3
    Adding disk3s2 to Logical Volume Group
    Creating Core Storage Logical Volume Group
    Switching disk0s2 to Core Storage
    Switching disk3s2 to Core Storage
    Waiting for Logical Volume Group to appear
    Discovered new Logical Volume Group "094AF142-64BE-45F2-BB5F-68B71CD82DF3"
    Core Storage LVG UUID: 094AF142-64BE-45F2-BB5F-68B71CD82DF3
    Finished CoreStorage operation
    Davids-Mac-Pro:~ dgwilson$ diskutil cs createVolume 094AF142-64BE-45F2-BB5F-68B71CD82DF3 jhfs+ FusionHD 100%
    Started CoreStorage operation
    Waiting for Logical Volume to appear
    Formatting file system for Logical Volume
    Initialized /dev/rdisk5 as a 1 TB case-insensitive HFS Plus volume with a 131072k journal
    Mounting disk
    Core Storage LV UUID: C39C355A-0FC2-49BF-AA0B-E56132F1CFCB
    Core Storage disk: disk5
    Finished CoreStorage operation
    Davids-Mac-Pro:~ dgwilson$ diskutil cs list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group 094AF142-64BE-45F2-BB5F-68B71CD82DF3
        =========================================================
        Name:         Fusion
        Status:       Online
        Size:         1627649638400 B (1.6 TB)
        Free Space:   24576 B (24.6 KB)
        |
        +-< Physical Volume 3A6E7C8B-7939-4CA3-AF0F-3C3807A097D2
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk0s2
        |   Status:   Online
        |   Size:     127691702272 B (127.7 GB)
        |
        +-< Physical Volume 44A03319-128E-4060-9681-2307A2C54242
        |   ----------------------------------------------------
        |   Index:    1
        |   Disk:     disk3s2
        |   Status:   Online
        |   Size:     1499957936128 B (1.5 TB)
        |
        +-> Logical Volume Family 67FA2BEC-71DE-402E-A08B-AD3849972307
            ----------------------------------------------------------
            Encryption Type:         None
            |
            +-> Logical Volume C39C355A-0FC2-49BF-AA0B-E56132F1CFCB
                ---------------------------------------------------
                Disk:                  disk5
                Status:                Online
                Size (Total):          1621757657088 B (1.6 TB)
                Revertible:            No
                LV Name:               FusionHD
                Volume Name:           FusionHD
                Content Hint:          Apple_HFS
                LVG Type:              Fusion, Sparse
    Davids-Mac-Pro:~ dgwilson$ diskutil list
    /dev/disk0 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *128.0 GB   disk0
      1:                        EFI EFI                     209.7 MB   disk0s1
      2:          Apple_CoreStorage Fusion                  127.7 GB   disk0s2
      3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
    /dev/disk1 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *250.1 GB   disk1
      1:                        EFI EFI                     209.7 MB   disk1s1
      2:                  Apple_HFS MacPro09                249.2 GB   disk1s2
      3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    /dev/disk2 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *1.5 TB     disk2
      1:                        EFI EFI                     209.7 MB   disk2s1
      2:                  Apple_HFS Spare1.5TB              1.4 TB     disk2s2
    /dev/disk3 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *1.5 TB     disk3
      1:                        EFI EFI                     209.7 MB   disk3s1
      2:          Apple_CoreStorage Fusion                  1.5 TB     disk3s2
      3:                 Apple_Boot Boot OS X               134.2 MB   disk3s3
    /dev/disk4 (internal, physical):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:      GUID_partition_scheme                        *1.5 TB     disk4
      1:                        EFI EFI                     209.7 MB   disk4s1
      2:                  Apple_HFS ElTestO                 1.5 TB     disk4s2
      3:                 Apple_Boot Recovery HD             650.0 MB   disk4s3
    /dev/disk5 (internal, virtual):
      #:                       TYPE NAME                    SIZE       IDENTIFIER
      0:                  Apple_HFS FusionHD               +1.6 TB     disk5
                                    Logical Volume on disk0s2, disk3s2
                                    C39C355A-0FC2-49BF-AA0B-E56132F1CFCB
                                    Unencrypted Fusion Drive
    

    And for reference... Here is what the disks look like after the OS install - see the Fusion drive now has a RecoveryHD.

    Code:
    diskutil list
    /dev/disk0 (internal, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *128.0 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:          Apple_CoreStorage Fusion                  127.7 GB   disk0s2
       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
    /dev/disk1 (internal, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *250.1 GB   disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS MacPro09                249.2 GB   disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    /dev/disk2 (internal, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.5 TB     disk2
       1:                        EFI EFI                     209.7 MB   disk2s1
       2:                  Apple_HFS Spare1.5TB              1.4 TB     disk2s2
    /dev/disk3 (internal, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.5 TB     disk3
       1:                        EFI EFI                     209.7 MB   disk3s1
       2:          Apple_CoreStorage Fusion                  1.5 TB     disk3s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3
    /dev/disk4 (internal, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.5 TB     disk4
       1:                        EFI EFI                     209.7 MB   disk4s1
       2:                  Apple_HFS ElTestO                 1.5 TB     disk4s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk4s3
    /dev/disk5 (internal, virtual):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS FusionHD               +1.6 TB     disk5
                                     Logical Volume on disk0s2, disk3s2
                                     84A2C986-1E84-4DDE-A430-342EAA77D696
                                     Unencrypted Fusion Drive
    /dev/disk6 (external, physical):
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk6
       1:                        EFI EFI                     209.7 MB   disk6s1
       2:                  Apple_HFS Install OS X El Capitan 499.8 GB   disk6s2
    
     
  25. 666sheep macrumors 68040

    666sheep

    Joined:
    Dec 7, 2009
    Location:
    Poland
    #850
    Yep, my issue was RAM related as well.
    Installed the OS from that same USB installer again and all went OK.
    rthpjm: great work!
     

Share This Page