Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

2006/2007 Mac Pro (1,1/2,1) and OS X El Capitan

Andreaux

Andreaux

macrumors member
May 8, 2016
52
7
I just tried to re-create an installer USB stick and ran into the same issue (after this, I get the same error as @wazzco):

Here's what the log looks like:

Saving an original copy of the Install OS X El Capitan InstallESD.dmg....

Open the InstallESD disk image
Piking the OSInstall collection
Saving the original copy of the BaseSystem.dmg....

Open the BaseSystem disk image
Piking the Base System
Adding the missing fonts...
Close the BaseSystem disk image

Put the modified BaseSystem back into the InstallESD disk image
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $42FD50BE: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $A1953BB9: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $6AE0C428: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
.........................hdiutil: updateHeader failed - No space left on device

hdiutil: convert failed - No space left on device


How to overcome this "No space left on device" issue?
I have plenty of space everywhere....
 
C

cdmawolf

macrumors member
Feb 26, 2016
63
10
Andreaux said:
I just tried to re-create an installer USB stick and ran into the same issue (after this, I get the same error as @wazzco):

Here's what the log looks like:

Saving an original copy of the Install OS X El Capitan InstallESD.dmg....

Open the InstallESD disk image
Piking the OSInstall collection
Saving the original copy of the BaseSystem.dmg....

Open the BaseSystem disk image
Piking the Base System
Adding the missing fonts...
Close the BaseSystem disk image

Put the modified BaseSystem back into the InstallESD disk image
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $42FD50BE: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $A1953BB9: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $6AE0C428: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
.........................hdiutil: updateHeader failed - No space left on device

hdiutil: convert failed - No space left on device


How to overcome this "No space left on device" issue?
I have plenty of space everywhere....
Click to expand...


I ran into this yesterday also(I have ElCap 10.11.4 and 10.11.5 running on 2 partitions)while trying to troubleshoot someone else's problem. I was running from 10.11.4 and got this trying to build on a 8G usb and a 600G partition. I rebooted into Lion and it worked like a champ. ? That is all I had time to try. BTW the Installer was 10.11.4
 
  • Like
Reactions: Andreaux
wazzco

wazzco

macrumors newbie
Jul 4, 2016
9
0
Ok, so I tried running ./createpikeinstallmedia with an OSX 10.11.5 freshly downloaded el capitan installer.app exactly as it should. it failed in both OSX 10.7.5 and in 10.11.5 (with SIP turned off) to make an USB thumbdrive.

IT DID NOT WORK:

== A problem occurred when creating the install media with Apple's createinstallmedia tool
== The most common issue is that the installer volume could not be unmounted because some other process is using it
== Close all other windows (especially terminal windows) and try again

When I ran the /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia when I fresh downloaded it (before running pikify script) it worked perfectly and made me the USB thumbdrive perfectly.

The moment that image gets edited by the pikify 3.1v10 installer, it does not work.
When I try again, i get to choose to reset the install.app to its original state.
After this, performing the createinstallmedia script from the original installer works perfectly.

Additional notes:
- I don't have anything else running on the computer during the process that could remotely come close to performing actions on the usb drive, so that it cannot be unmounted.
- It has nothing to to with SIP, I'm running it from Lion - and I have SIP turned off in el capitan
 
Andreaux

Andreaux

macrumors member
May 8, 2016
52
7
I can't have it to run in Lion either...

@wazzco: if you scroll up in Terminal after you get the error you copied out, do you also see that "
hdiutil: convert failed - No space left on device" error? I have it in El Capitan and Lion as well.

Maybe this has to do with the pikify package... when it worked for me, I was using v8, now it's v10... idk.
 
Last edited:
wazzco

wazzco

macrumors newbie
Jul 4, 2016
9
0
Andreaux said:
I can't have it to run in Lion either...

@wazzco: if you scroll up in Terminal after you get the error you copied out, do you also see that "
hdiutil: convert failed - No space left on device" error? I have it in El Capitan and Lion as well.

Maybe this has to do with the pikify package... when it worked for me, I was using v8, now it's v10... idk.
Click to expand...

Hi,

I don't have that same error as you do.

Here's my resulting sequence:

------------------------------------------------------------------------------------------------------------------------------------------------------------


Pikify3.1 contains a script and other items to create install media for Mac OS X El Capitan to be used on 32-bit EFI based Macintosh computers
It uses Apple's "Install OS X El Capitan.app" application which must be located in your /Applications folder

There are a number of processing steps, please be patient and let this script run through to completion
A small number of users have been too eager to get started and pulled their installer volume out of the USB socket too early

The script will end with ######### DONE PIKIFYING ########### if all goes well


------------------------------------------------------------------------------------------------------------------------------------------------------------


Saving an original copy of the Install OS X El Capitan InstallESD.dmg....


Open the InstallESD disk image
Piking the OSInstall collection
Saving the original copy of the BaseSystem.dmg....


Open the BaseSystem disk image
Piking the Base System
Adding the missing fonts...
Close the BaseSystem disk image


Put the modified BaseSystem back into the InstallESD disk image
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $5B440D18: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $4A7E20D9: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $987D5EAA: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
..........................................................................
(CRC32 $A0A68EAB: disk image (Apple_HFS : 4))
Reading (Apple_Free : 5)…
..............................................................................
(CRC32 $00000000: (Apple_Free : 5))
Reading GPT Partition Data (Backup GPT Table : 6)…
..............................................................................
(CRC32 $987D5EAA: GPT Partition Data (Backup GPT Table : 6))
Reading GPT Header (Backup GPT Header : 7)…
...............................................................................
(CRC32 $AD25EB56: GPT Header (Backup GPT Header : 7))
Adding resources…
...............................................................................
Elapsed Time: 1m 20.332s
File size: 481211967 bytes, Checksum: CRC32 $C6F1AC57
Sectors processed: 4194272, 2989284 compressed
Speed: 18.2Mbytes/sec
Savings: 77.6%
created: /Volumes/OS X Install ESD/BaseSystem.dmg
Close the InstallESD disk image


Rebuild the InstallESD
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
(CRC32 $1391EFBA: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
(CRC32 $BE99E03B: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
(CRC32 $A3ACF886: GPT Partition Data (Primary GPT Table : 2))
Reading (Apple_Free : 3)…
(CRC32 $00000000: (Apple_Free : 3))
Reading EFI System Partition (Windows_NTFS : 4)…
..
(CRC32 $3966551F: EFI System Partition (Windows_NTFS : 4))
Reading disk image (Apple_HFS : 5)…
.............................................................................
(CRC32 $45BF1F36: disk image (Apple_HFS : 5))
Reading (Apple_Free : 6)…
..............................................................................
(CRC32 $00000000: (Apple_Free : 6))
Reading GPT Partition Data (Backup GPT Table : 7)…
..............................................................................
(CRC32 $A3ACF886: GPT Partition Data (Backup GPT Table : 7))
Reading GPT Header (Backup GPT Header : 8)…
...............................................................................
(CRC32 $A762D7BF: GPT Header (Backup GPT Header : 8))
Adding resources…
...............................................................................
Elapsed Time: 5m 42.377s
File size: 6208101405 bytes, Checksum: CRC32 $8120BC80
Sectors processed: 14120024, 12431259 compressed
Speed: 17.7Mbytes/sec
Savings: 14.1%
created: /Applications/Install OS X El Capitan.app/Contents/SharedSupport/InstallESD.dmg

Running Apple's createinstallmedia tool...
Erasing Disk: 0%... 10%... 20%...100%...
Copying installer files to disk...
The copy of the installer app failed.
.


=================================================================================================================================
==
== ERROR
==
=================================================================================================================================
==
== A problem occurred when creating the install media with Apple's createinstallmedia tool
== The most common issue is that the installer volume could not be unmounted because some other process is using it
== Close all other windows (especially terminal windows) and try again
==
=================================================================================================================================

Since pikify3.1v9 most of the actions are performed on the original install.app before the script invokes Apple's createinstallmedia to copy the modified image to the destination USB/HDD.

Do you (or anyone else) happen to have the pikify 3.1v8 download somewhere? I would like to try it !

Thanks!
 
Andreaux

Andreaux

macrumors member
May 8, 2016
52
7
Yes, but do the [r]eset procedure and try again, then you'll get the same error.... I suppose.

On my end, I have just successfully created an installer with Pikify3.1.v8.... v10 seems to have issues. Try it.

Drop me a PM with your e-mail and I'll send you v8.

Cheers
 
drummerboy78

drummerboy78

macrumors newbie
Jul 4, 2016
3
1
Dallas, TX
Hi, I'm a ultra-newbie here and I am trying to figure out how to do all of these things to make my Mac Pro 1,1 function with all of the below changes. Is someone able to teach me how to do all of this stuff?



Thank you,

Jacob

Mr. Zarniwoop said:
The race is on.

Who's the first to get OS X version 10.11 El Capitan booting perfectly on a 2006/2007 Mac Pro (1,1/2,1)?

UPDATE: Only one day later, 666sheep did it first!

This first post has now been updated with recent summarized information.


Simply looking to download the Piker-Alpha macosxbootloader for El Capitan? Links:
________________________________________________________________

If you have OS X El Capitan up and running on your 2006/2007 Mac Pro with Pike's boot loader, you should consider disabling "Install OS X updates" and "Install system data files and security updates" in System Preferences > App Store so that OS X doesn't automatically install any future updates that may overwrite Pike's boot.efi.
________________________________________________________________

If you find Pike's boot loader valuable in keeping your 2006/2007 Mac up-to-date, please consider simply thanking him via a comment on his blog, as he's done a lot of work without asking for anything in return or benefiting from this project. Thanks Pike!


How can these Macs run El Capitan?

Apple does not support OS X El Capitan on the original 2006/2007 Mac Pro and 2006 Xserve. These 64-bit Mac Pros and Xserves have EFI32 firmware and can't natively boot OS X El Capitan "out-of-the-box", but are easily capable of running it with a different boot loader. Once a new boot loader is used to launch the native 64-bit El Capitan kernel, OS X 10.11 boots and works normally exactly as it does on a 2008 Mac Pro or newer with EFI64 firmware.


Background:

OS X 10.6 Snow Leopard was the first OS X version with optional support for a 64-bit kernel, allowing booting either with a 32-bit or 64-bit kernel. However, Apple did not support booting the 64-bit kernel in Macs that shipped with EFI32 firmware, even if they had 64-bit processors capable of running the 64-bit kernel. When Apple dropped the 32-bit kernel entirely from OS X, starting with OS X 10.8 Mountain Lion, EFI32 Macs no longer had an Apple-supported mechanism to boot newer OS X versions.

The last version of OS X officially supported by Apple on the original 2006 Mac Pro MA356LL/A (MacPro1,1), 2007 Mac Pro (8-core) MA1186/A (MacPro2,1) and Xserve (Late 2006) MA409LL/A (Xserve1,1) models was OS X 10.7 Lion, and then only when booted with a 32-bit kernel due to their EFI32 firmware. However, these Macs were the most powerful and upgradable EFI32 models and have a 64-bit architecture, so the user community has been keeping them running with 64-bit kernels and newer OS X releases using a variety of methods.


The Piker-Alpha bootloader can be used to boot OS X 10.11 El Capitan on unsupported Mac Pro models:

This approach, using a fork of boot.efi boot loader that thunks EFI64 calls from the 64-bit OS X kernel to the EFI32 firmware.

Additional information about Pike's boot.efi is available at Pike's blog, Universum. There are two variations available, one with a legacy light grey background/dark grey Apple logo boot screen boot.efi that blends with the native EFI32 pre-boot screen (2008-2012 Mac Pro-style), and a new black background/white Apple logo boot screen boot.efi (2013 Mac Pro-style).

The simplest method to boot El Capitan on these Macs is the "pikify" createpikeinstallmedia script to create a pre-patched El Capitan installer with the El Capitan branch of the Piker-Alpha bootloader. This directly allows an El Capitan installer to run to be run to completion on a 2006/2007 Mac Pro.

Another alternative install on a 2006/2007 Mac Pro is to use a second El Capitan-supported Mac and install El Capitan to the 2006/2007 Mac Pro's drive. This may be done either by attaching the 2006/2007 Mac Pro's drive as an external drive by placing the 2006/2007 Mac Pro in target disk mode or otherwise mounting the 2006/2007 Mac Pro's drive to an El Capitan-supported Mac.

This alternative approach still requires installation of the Piker-Alpha bootloader before it can be successfully booted on a 2006/2007 Mac Pro. After installation, copy Pike's EFI32 boot.efi to that drive's /usr/standalone/i386 and /System/Library/CoreServices/ directories overwriting the stock Apple EFI64 boot.efi. That drive should now be bootable on a 2006/2007 Mac Pro, although sometimes it still may need to be blessed in the 2006/2007 Mac Pro.

Disabling System Integrity Protection (SIP) may be required to replace the boot.efi in-place.

Alternatively, there's also an approach in the boot.efi development thread to exclude these files from SIP, but it has shown mixed results.

While this method is preferred because it's a native EFI boot, there is real risk that installing future El Capitan updates could overwrite Pike's EFI32 boot.efi if Apple were to update the stock EFI64 boot.efi. This has already happened in the few previous OS X El Capitan updates. When this happens, the system would no longer be natively bootable on a 2006/2007 Mac Pro until it had Apple's stock boot.efi re-replaced with Pike's boot.efi again. A simple approach to help protect against this is CaptainPikeFix, a launch daemon that re-copies the EFI32 boot.efi to proper locations at shutdown, but this approach requires disabling SIP.


Support for Handoff in El Capitan to allow AirDrop, Continuity and Instant Hotspot with iOS devices:

The original Airport Extreme (802.11a/b/g/draft-n Wi-Fi) and Bluetooth 2.0+EDR options from Apple don't support Handoff. Several vendors, including MacVidCards, sell new add-on hardware kits to retrofit older Mac Pros with 802.11ac Wi-Fi and Bluetooth 4.0 LE that work in 2006/2007 Mac Pros to allow Handoff. There have been reports of needing to sign out of iCloud and then sign in again after replacing WiFi and Bluetooth hardware to enable Handoff.

There has been a report of an OEM Bluetooth 2.0+EDR card causing a conflict with USB devices. If you experience issues with the built-in USB ports under El Capitan, you may also consider removing or upgrading your Bluetooth card.

In El Capitan, both Phone Calling and SMS from OS X with an iPhone work with a 2006/2007 Mac Pro and are not dependent on OS X Handoff support.


Unsupported original legacy graphics cards vs. 64-bit-kernel-supported graphics cards vs. Metal-supported graphics cards:

El Capitan does not include 64-bit kernel extension device drivers for the original NVIDIA GeForce 7300 GT, ATI Radeon X1900 XT, and NVIDIA Quadro FX 4500 PCIe graphics cards that shipped with these Mac Pros, nor the ATI Radeon X1300 that shipped with the Xserve (Late 2006), so they do not work properly in El Capitan. These graphics cards display issues such as a very sluggish GUI with no QE/CI support, no framebuffer support (for DVD Player, Geekbench and other programs), graphics artifacts, mouse tearing, inability to change resolutions, bad refresh rates, and other system instabilities. If you need normal graphics support in El Capitan, you will need a newer PCIe graphics card, with popular options being the Apple ATI Radeon HD 5770 Graphics Upgrade Kit for Mac Pro, SAPPHIRE HD 7950 3GB GDDR5 MAC Edition, or many different options of stock and Mac-"flashed" PC cards.

Many, but not all, modern stock non-flashed PC graphics cards with AMD (for OpenCL/OpenGL support) or Nvidia chipsets (for CUDA/OpenCL/OpenGL support) work "plug and play" with El Capitan in 2006/2007 Mac Pros, although the display will remain off until after the OS X Desktop initializes. This means you won't see anything during the boot process.

Compatible properly-Mac-flashed PC cards offer two benefits over stock non-flashed PC cards: allowing a normal boot screen just like a Mac-specific graphics card, and better compatibility in OS X with the card's capabilities/performance/ports. Most, but not all, Mac-flashed ATI/AMD cards have EBC firmware that work in all PCIe-based 2006-2012 Mac Pro models with either EFI32 or EFI64. All newer Mac-flashed Nvidia cards have EFI64 firmware and will act like non-flashed PC cards with no boot screens in EFI32-based 2006/2007 Mac Pros, except for older Mac-flashed Nvidia GeForce 8800 GT/9800 GT/GT 120 cards with EFI32 firmware.

Lastly, El Capitan has added a new graphics API called Metal that allows for much faster access to graphics card hardware. Note that only the most recent AMD (HD 7xxx "Tahiti" or newer) or Nvidia chipset (GeForce 6xx "Kepler" or newer) graphics cards fully and properly support Metal in a 2006/2007 Mac Pro.
Note also that the 2006/2007 Mac Pro has PCIe 1.1 expansion slots, with the bottom double-wide slot capable of being configured to use a maximum 2.5 GT/s link speed when configured as a x16 lane graphics slot. El Capitan's Expansion Slot Utility, located in /System/Library/Core Services, supports the 2006-2007 Mac Pro to configure the number of lanes available in each slot. PCIe 2.0/3.0 cards that can run at 5.0 GT/s link speed in 2008-2012 Mac Pros can work in 2006/2007 Mac Pros, but only with a PCIe 1.1 maximum 2.5 GT/s link speed.

None of these options are officially supported in these Mac Pros by AMD, Apple, or Nvidia, but can work with the Piker-Alpha boot loader.


iMessage/FaceTime note:

Regardless of approach used, some users cannot initially login to iMessage or FaceTime using their Apple ID from their Mac Pro after installing El Capitan as a security precaution. When trying to login, they receive an iMessage Registration validation code. The solution is to contact Apple support, provide the Mac Pro's serial number, explain that El Capitan was installed and that iMessage isn't working and provide the validation code. Apple then unblocks the Mac Pro, allowing iMessage and FaceTime login immediately and in the future without other issues.
Click to expand...
 
C

cdmawolf

macrumors member
Feb 26, 2016
63
10
drummerboy78 said:
Hi, I'm a ultra-newbie here and I am trying to figure out how to do all of these things to make my Mac Pro 1,1 function with all of the below changes. Is someone able to teach me how to do all of this stuff?



Thank you,

Jacob
Click to expand...

START by going to page 56 of this thread and read Post #1390. Do you have 12Gig of memory and NO 512M modules?
Then ask questions........
 
C

cdmawolf

macrumors member
Feb 26, 2016
63
10
Andreaux said:
Yes, but do the [r]eset procedure and try again, then you'll get the same error.... I suppose.

On my end, I have just successfully created an installer with Pikify3.1.v8.... v10 seems to have issues. Try it.

Drop me a PM with your e-mail and I'll send you v8.

Cheers
Click to expand...

I just tried V10 on a VIRGIN El Cap install with a partition target and got No Space Left.
I just tried V2 on a VIRGIN El Cap install with a partition target and it is working.
I just tried V8 on a VIRGIN El Cap install with a partition target and it is working.
 
Last edited:
Andreaux

Andreaux

macrumors member
May 8, 2016
52
7
cdmawolf said:
I just tried V10 on a VIRGIN El Cap install with a partition target and got No Space Left.
I just tried V2 on a VIRGIN El Cap install with a partition target and it is working.
Next V8
Click to expand...

v8 worked perfectly for me yesterday. I have no v9 to try with.
 
wazzco

wazzco

macrumors newbie
Jul 4, 2016
9
0
@cdmawolf & @Andreaux and all others

I've tried OSX 10.11.5 (version 15F34) in combination with pikify 3.1v8 to create an USB thumbdrive. Confirmed working combination to create a bootable USB drive (other disks assumed also OK).

Recap from previous posts: pikify 3.1v10 did not work for me with the OSC 10.11.5 (version 15F34).

Looking at the version history of the pikify script (see page 59, post #1390) I suspect that the changes made after v8 broke the script: Apple's createinstellmedia command does not like the pre-modification of the installer app (15F34).

v2 did create an USB thumbdrive properly-but does not include the latest progress in developments.


So : OSX 10.11.5 + pikify 3.1v8 creates the bootable USB thumbdrive and the installer runs after reboot.

Unfortunately I'm stuck with the installer crashing after some minutes (SEE KERNEL PANIC REPORT ATTACHED - help needed for interpretation)- I have only 3GB of RAM in the machine amongst which 512 MB modules.

So my question: Can anyone with a mac pro 1.1 /2.1 with more than 12 GB (and no 512MB modules) of RAM try out the combination OSX 10.11.5 (version 15F34 = latest at time of writing) + pikify 3.1v8 ? @drummerboy78 maybe? PM me if you need pikify 3.1v8 to try.

I'd be happy to see confirmation of a working complete pikified 10.11.5 El capitan install while I wait for my 32GB of RAM to be delivered :D
Cheers
 

Attachments

  • Kernel panic report encountered during install of el capitan.txt
    8.6 KB · Views: 261
rthpjm

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
wazzco said:
@cdmawolf & @Andreaux and all others

I've tried OSX 10.11.5 (version 15F34) in combination with pikify 3.1v8 to create an USB thumbdrive. Confirmed working combination to create a bootable USB drive (other disks assumed also OK).

Recap from previous posts: pikify 3.1v10 did not work for me with the OSC 10.11.5 (version 15F34).

Looking at the version history of the pikify script (see page 59, post #1390) I suspect that the changes made after v8 broke the script: Apple's createinstellmedia command does not like the pre-modification of the installer app (15F34).

v2 did create an USB thumbdrive properly-but does not include the latest progress in developments.


So : OSX 10.11.5 + pikify 3.1v8 creates the bootable USB thumbdrive and the installer runs after reboot.

Unfortunately I'm stuck with the installer crashing after some minutes (SEE KERNEL PANIC REPORT ATTACHED - help needed for interpretation)- I have only 3GB of RAM in the machine amongst which 512 MB modules.

So my question: Can anyone with a mac pro 1.1 /2.1 with more than 12 GB (and no 512MB modules) of RAM try out the combination OSX 10.11.5 (version 15F34 = latest at time of writing) + pikify 3.1v8 ? @drummerboy78 maybe? PM me if you need pikify 3.1v8 to try.

I'd be happy to see confirmation of a working complete pikified 10.11.5 El capitan install while I wait for my 32GB of RAM to be delivered :D
Cheers
Click to expand...
I'm away from home on business at the moment. Unfortunately I can't help at the moment other than general advice until Thursday evening (GMT/BST).

For those getting the "running Apple's createinstallmedia" error, try to open up Disk Utility, select your USB memory stick (or small disk partition), and try to unmount it. If it unmounts, then re-mount it and try running ./createpikeinstallmedia again.

It's possible that the Spotlight indexing daemon (mds) might be locking the /Volumes/USBstick volume. I'll investigate when I get back home.

For those of you getting "no space left on device", I will have to investigate. It has little to do with the actual physical disk space, it is usually recreating the DMG disk image. The disk image is a fixed size. To investigate properly I will need to know what version of pikify you are using (sounds like v10 is the culprit), and which version of Apple's Install OS X El Capitan you have (10.11.x), and the size of your install media volume (8Gb-ish)

I will re-post pikify3.1.v8 on Thursday, too.
 
  • Like
Reactions: wazzco
wazzco

wazzco

macrumors newbie
Jul 4, 2016
9
0
rthpjm said:
For those getting the "running Apple's createinstallmedia" error, try to open up Disk Utility, select your USB memory stick (or small disk partition), and try to unmount it. If it unmounts, then re-mount it and try running ./createpikeinstallmedia again.

It's possible that the Spotlight indexing daemon (mds) might be locking the /Volumes/USBstick volume. I'll investigate when I get back home.
Click to expand...

Hi rthpjm!

I've tried unmounting + remounting the volume and running the script after that. No success.
Here's what (always) happens with v10: the copying process begins, runs for a long time and then quits.
Ingredients: a virgin 10.11.5 15F34 app + pikify 3.1v10.

Thanks for your devotion to this thread!
 
Andreaux

Andreaux

macrumors member
May 8, 2016
52
7
I had the same results with an older installer (not sure, but probably 10.11.1)

v.10 fails first with the "no space left on device" error, then if ran again, fails with the error wazzco posted. I can reproduce both errors resetting the installer to Apple's state and starting over. 1st run: no space left on device, 2nd run: the other error. Consecutive runs: the second error always.
Tried on both 10.11.4 and 10.7.5.

v.8 no problems with the same installer.
Tried on 10.7.5

My Install USB drive is exactly 8GB in both cases...
 
Last edited:
O

ortizra1

macrumors newbie
Apr 12, 2015
2
0
rthpjm said:
Is your graphics card a generic PC Card?
If so have you tried to flash it with the EFI addition?

Has it ever shown the boot screens?

Have you tried a DVI-to-VGA adaptor, cable to the VGA port on your monitor (or find an old monitor)
Click to expand...

Aloha Sir;

Thank you for your prompt response, if I recall it is a radeon 6890 or 6850. I don't know if it is generic or brand, but it did come in an original radeon box. I don't know what it is to flash the card or how to do it. I do know that if I just let the mac boot on its own, it will boot to my lion os.

Mahalo;
Ray
 
rthpjm

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
ortizra1 said:
Aloha Sir;

Thank you for your prompt response, if I recall it is a radeon 6890 or 6850. I don't know if it is generic or brand, but it did come in an original radeon box. I don't know what it is to flash the card or how to do it. I do know that if I just let the mac boot on its own, it will boot to my lion os.

Mahalo;
Ray
Click to expand...
Hello Ray,

There is some advice buried in the middle of post #1390 for those people with generic PC cards. If you don't flash these cards with an EFI compatible firmware then you do not get to see the initial start up screens. The card only becomes active once the OS has loaded. (If you come from a PC background, the EFI is the newer equivalent to the BIOS environment, it is responsible for the startup sequence, initializing hardware like the graphics card, and then booting the OS). Apple-branded cards come with firmware that contains a BIOS segment and an EFI segment. Generic graphics cards generally only ship with the BIOS firmware. There is a web site (forums.netkas.org) that has a wealth of information and community developed firmware for the popular graphics cards. Flashing new (combined) firmware onto a generic card is a bit scary if you are not used to doing it, but it is relatively simple. There are good step-by-step instructions. The downside is having to trawl through the forum to find the latest and greatest firmware and instructions.

If you have a generic card (and it sounds like you do), then the initial boot sequence will not necessarily display through your gfx card. Where we say "hold down the ALT key when you hear the reboot chime" you are still in the EFI pre-boot environment and your card won't display anything.

Having said that, most AMD cards do show those initial EFI boot screens if you use a VGA display (use a DVI to VGA adaptor).

If you have a community supported card, AND you flash the combined firmware onto your card, then the initial boot screens can be displayed over the digital connections too (DVI and/or Display Port).

My recommendation is try a DVI-VGA adaptor first. If you can't and you don't want to flash the card, then you are effectively operating "blind". Look for the advice on post #1390 about using the arrow keys to select the boot volume.
 
A

apple_iBoy

macrumors 6502a
Oct 28, 2003
734
495
Philadelphia, PA
rthpjm said:
My recommendation is try a DVI-VGA adaptor first. If you can't and you don't want to flash the card, then you are effectively operating "blind". Look for the advice on post #1390 about using the arrow keys to select the boot volume.
Click to expand...

I also had problems using the arrow key method to blindly find the installer media. Tried unsuccessfully a number of times.

What ended up working for me instead was holding down the c key during boot up, like we used to do when we wanted to boot from an actual CD or DVD. Turns out, that startup key also looks for bootable USB drives.
 
rthpjm

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
apple_iBoy said:
I also had problems using the arrow key method to blindly find the installer media. Tried unsuccessfully a number of times.

What ended up working for me instead was holding down the c key during boot up, like we used to do when we wanted to boot from an actual CD or DVD. Turns out, that startup key also looks for bootable USB drives.
Click to expand...
Thanks iBoy

I keep forgetting that one (and I think you posted that advice earlier, so I have no excuse !!!)
 
C

cdmawolf

macrumors member
Feb 26, 2016
63
10
cdmawolf said:
I just tried V10 on a VIRGIN El Cap install with a partition target and got No Space Left.
I just tried V2 on a VIRGIN El Cap install with a partition target and it is working.
I just tried V8 on a VIRGIN El Cap install with a partition target and it is working.
Click to expand...
I used V10 on Lion 10.7 (11A511) and it worked................YMMV
 
rthpjm

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
cdmawolf said:
I used V10 on Lion 10.7 (11A511) and it worked................YMMV
Click to expand...
I think we must have slipped into some alternative reality :confused:

Some say "it works", some say it doesn't!

Maybe the Jupiter probe is interfering with the solar winds or something?!!!!
 
  • Like
Reactions: owbp
C

cdmawolf

macrumors member
Feb 26, 2016
63
10
rthpjm said:
I think we must have slipped into some alternative reality :confused:

Some say "it works", some say it doesn't!

Maybe the Jupiter probe is interfering with the solar winds or something?!!!!
Click to expand...
I used 10.7 and the report was it did not work on 10.7.5. Anything there?

BTW NASA has 360 videos of Juno and Jupiter......
 
Last edited:
Andreaux

Andreaux

macrumors member
May 8, 2016
52
7
I'd just like to report that I successfully updated from 10.11.4 to 10.11.5 this morning. I have CaptainPikeFix installed.
SIP remained disabled after the update.
 
  • Like
Reactions: Eagalution and wazzco
rthpjm

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
rthpjm said:
I'm away from home on business at the moment. Unfortunately I can't help at the moment other than general advice until Thursday evening (GMT/BST).

For those getting the "running Apple's createinstallmedia" error, try to open up Disk Utility, select your USB memory stick (or small disk partition), and try to unmount it. If it unmounts, then re-mount it and try running ./createpikeinstallmedia again.

It's possible that the Spotlight indexing daemon (mds) might be locking the /Volumes/USBstick volume. I'll investigate when I get back home.

For those of you getting "no space left on device", I will have to investigate. It has little to do with the actual physical disk space, it is usually recreating the DMG disk image. The disk image is a fixed size. To investigate properly I will need to know what version of pikify you are using (sounds like v10 is the culprit), and which version of Apple's Install OS X El Capitan you have (10.11.x), and the size of your install media volume (8Gb-ish)

I will re-post pikify3.1.v8 on Thursday, too.
Click to expand...

Ah, I think I might know what is going on!!!
In my effort to speed up the process, I start to modify the on-disk /Applications/Install OS X El Capitan.app. (Disk read/write is faster than read/write over the USB2 bus on MacPro 1,1 / 2,1). Since I'm modifying the Apple Installer, I wanted to keep a copy of the Apple original (so that it can be reset). I move the InstallESD.dmg to InstallESD-original.dmg, then the createpikeinstallmedia script builds a new copy of InstallESD.dmg with the modifications. That means there are now two DMGs (both sized around 6.1Gb).

What I overlooked was that Apple's createinstallmedia copies the whole of the Install OS X El Capitan.app onto the install media!!! So I'm trying to squeeze >12Gb onto an 8Gb Volume. The laws of physics hold, 12 into 8 won't go.

Sorry folks. My bad. I'll post V11 later....
 
  • Like
Reactions: wazzco and cdmawolf
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom