Yup. Success!
I was able to update the Recovery HD when I was booted off another disk.
Thank you team!
- David
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS boot.efi developer's thread
- Thread starter mikeboss
- Start date
- Sort by reaction score
Yup. Success!
I was able to update the Recovery HD when I was booted off another disk.
Thank you team!
- David
If you originally started with pikify3.1, then the recovery partition should already be modified (pikify does it for you).
It is possible that the 10.11.2 Recovery HD update may have overwritten things.
The simple change is posted at #1454 on the main thread.
If you feel the need to change the BaseSystem.dmg as well...
Assuming the recovery partition is mounted at /Volumes/Recovery HD
Code:rsync -ah --progress /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg /tmp hdiutil attach -nobrowse -noverify -owners on -kernel /tmp/BaseSystem.dmg -shadow cp [pike-boot.efi] /Volumes/OS\ X\ Base\ System/System/Library/CoreServices/boot.efi cp [pike-boot.efi] /Volumes/OS\ X\ Base\ System/usr/standalone/i386/boot.efi cd / hdiutil detach /Volumes/OS\ X\ Base\ System/ rm /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg hdiutil convert -format UDZO -imagekey zlib-level=9 /tmp/BaseSystem.dmg -shadow -o /Volumes/Recovery\ HD/com.apple.recovery.boot/BaseSystem.dmg rm /tmp/BaseSystem.dmg /tmp/BaseSystem.dmg.shadow
The Recovery HD is not usually large enough to make the changes in-place, hence the copy to /tmp
Thank you. I appreciate that set of commands. I'd tried to figure this out myself once before... had a miserable time and buggered a few things. This is great. Thank you again.
- David
Last piece of feedback for today...
I have successfully updated the EFI on my Recovery HD disks across the two MacPro's.
I've also verified the updates by booting into the recovery partitions.
I think I've found ONE issue - probably not a major if you can dual boot.
I'm fairly sure on the boot screen [OPTION KEY on boot]... I cannot see the Recovery HD for the Fusion drive.
The drives installed are listed below. On the boot screen I see:
ElTestO : MacPro09 : FusionHD : FusionHD : Recovery-10.11.2 : Recovery-10.9.3
- I have successfully booted into Recovery-10.11.2 (and I believe it's the RecoveryHD associated with ElTestO).
- ElTestO is a Standard HD with 10.11.2 installed.
Oh... and I'm updating the Recovery disks because around the time 10.11.2 was released... there was also a update for the Recovery disk from Apple.
- David
I have successfully updated the EFI on my Recovery HD disks across the two MacPro's.
I've also verified the updates by booting into the recovery partitions.
I think I've found ONE issue - probably not a major if you can dual boot.
I'm fairly sure on the boot screen [OPTION KEY on boot]... I cannot see the Recovery HD for the Fusion drive.
The drives installed are listed below. On the boot screen I see:
ElTestO : MacPro09 : FusionHD : FusionHD : Recovery-10.11.2 : Recovery-10.9.3
- I have successfully booted into Recovery-10.11.2 (and I believe it's the RecoveryHD associated with ElTestO).
- ElTestO is a Standard HD with 10.11.2 installed.
Oh... and I'm updating the Recovery disks because around the time 10.11.2 was released... there was also a update for the Recovery disk from Apple.
- David
Code:
Mac-Pro-1:Volumes dgwilson$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS MacPro09 249.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *128.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_CoreStorage Fusion 127.7 GB disk1s2
3: Apple_Boot Boot OS X 134.2 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_CoreStorage Fusion 1.5 TB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/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 Spare1.5TB 1.4 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
/dev/disk5 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS FusionHD +1.6 TB disk5
Logical Volume on disk1s2, disk2s2
84A2C986-1E84-4DDE-A430-342EAA77D696
Unencrypted Fusion Drive
You have 2 physical disks making up your fusion hd; /dev/disk1 is your 128GB SSD (I assume), and /dev/disk2 is your 1.5TB spinning one.
Both of these each have 3 partitions.
Your Core Storage hybrid is a virtual drive which is using slice 2 of each of your physical drives, the majority of the storage space.
Strictly speaking you do not have a recovery partition on your fusion drive /dev/disk5, it only has one partition of the combined storage.
There is a recovery partition on /dev/disk2s3. But I'm unsure how Apple might present that to you in the boot picker. Try
diskutil mount /dev/disk2s3
If the recovery HD mounts, try blessing with
Code:
bless --folder /Volumes/Recovery\ HD/com.apple.recovery.boot --label "Recovery HD disk2"
Last edited:
Cheers. Thanks for that. I successfully labelled the Recovery HD, rebooted with option key down and had it display on the screen.
Selecting the Fusion Recovery HD and booting... it actually booted into the main OS, not recovery.
I do believe the fusion creation and OS installation to be clean - it was created with pikify I'm fairly sure... It's probably time to find another couple of Hard Drives and install in MacPro2 - create a new fusion drive and test from scratch.
- David
EDIT: Installed 2 x more HDD's into 2nd MacPro. Manually built Fusion drive. Successfully installed 10.11.2 ( via pikify off USB key). Logged in. Performed Software update (iTunes, Camera RAW, and OS X El Capitan Recovery Update). Rebooted to the other El Capitan on the same hardware. Mounted Recovery HD on the 2nd Fusion HDD. Updated boot.efi and performed bless (to ensure label was known). Rebooted with Option key held down - Recovery HDD visible with assigned name. Selected disk ... and it booted into the main El Capitan OS (not recovery).
I'm not too bothered about this. Pursuing for knowledge and understanding. Happy to experiment further.
Last edited:
Although one or two users have claimed being able to successfully boot into Recovery HD through the Startup Manager (via Option when you hear the boot chime), my personal experience is that you can only access the Recovery HD through Cmd-R when the computer boots.
The non-Fusion drives I can boot to just fine through the Startup Manager. And the Fusion Drive Recovery Partition is visible through the Startup Manager.
Just so I'm clear:
My ElTestO HDD is a El Capital installation on a single HDD. A Recovery partition is also there.
When booted from another OS ... the one ons the Fusion drive for example... I can mount and update the Recovery HD with a new boot.efi file (pike 3.1).
I am subsequently able to reboot the machine, hold down option for the Startup manager select the Recovery HD for this drive (ElTestO) and it loads.
Code:
/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 disk4s3CMD-R ... will look into that tomorrow.
- David
Hi David,
Also check the basics: is the boot.efi file on the Recovery HD partition one of Pike's? I would be surprised, the way I wrote the pikify.pkg would not cater for hybrids in this manner. The technique I used to find the associated Recovery partition expects it to be on the same /dev/diskN as the main OS. In your case it is not.
Hi David,
I decided to try and cater for your Fusion drive. Would you like to try pikify3.1.v6 and let me know how you get on?
I modified the pikify.pkg to (hopefully) detect a hybrid disk and find the spinning member disk with the Recovery HD on it...
I also implemented the cosmetic label for the recovery HD, I set it to "Recovery HD - [associated OS drive]"
Hi rthpjm.
I had not caught up with your message. I'll download and have a go. I maybe short on a hard drive at the moment as I was using one in the test machine that had a "Failing" SMART status. ... Will see what I can get sorted.
EDIT: Install completed.
Code:
diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS 300GB 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_CoreStorage Fusion 319.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk
1: EFI EFI 209.7 MB disk2s1
2: Apple_HFS Macintosh HD 499.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_CoreStorage Fusion 319.7 GB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS FusionHD +632.0 GB disk4
Logical Volume on disk1s2, disk3s2
D2243130-A761-4812-B726-50CEB15C86E1
Unencrypted Fusion Drive
Davids-Mac-Pro:~ dgwilson$ diskutil mount /dev/disk1s3
Volume Recovery HD on /dev/disk1s3 mounted
Davids-Mac-Pro:~ dgwilson$ cd /Volumes/Recovery\ HD/
Davids-Mac-Pro:Recovery HD dgwilson$ ls -la
total 0
drwxr-xr-x 10 root wheel 408 21 Dec 16:00 .
drwxrwxrwt@ 6 root admin 204 21 Dec 16:09 ..
d-wx-wx-wt 2 root wheel 68 21 Dec 15:44 .Trashes
drwxr-xr-x 3 root wheel 102 21 Dec 15:44 .fseventsd
-rw-r--r-- 1 root wheel 0 21 Dec 15:44 .metadata_never_index
drwxr-xr-x 3 root wheel 102 21 Dec 15:58 System
drwxr-xr-x 5 root wheel 170 21 Dec 16:00 com.apple.boot.P
drwxr-xr-x 10 root wheel 340 21 Dec 15:45 com.apple.recovery.boot
Davids-Mac-Pro:Recovery HD dgwilson$ ls -la com.apple.recovery.boot/
total 974512
drwxr-xr-x 10 root wheel 340 21 Dec 15:45 .
drwxr-xr-x 10 root wheel 408 21 Dec 16:00 ..
drwxr-xr-x 5 root wheel 170 21 Dec 15:45 .diagnostics
-rw-r--r--@ 1 root admin 1948 2 Dec 23:02 BaseSystem.chunklist
-rw-r--r--@ 1 root admin 477045123 21 Dec 15:06 BaseSystem.dmg
-rw-r--r-- 1 root wheel 5691 1 Oct 15:32 PlatformSupport.plist
-r--r--r-- 1 root wheel 480 2 Dec 20:38 SystemVersion.plist
-rw-r--r--@ 1 root wheel 314880 21 Dec 15:04 boot.efi
-rw-r--r-- 1 root wheel 365 21 Dec 15:45 com.apple.Boot.plist
-rw-r--r-- 1 root wheel 21563822 2 Dec 20:34 prelinkedkernelboot.efi on the recovery partition looks like the right size!
I've got 2 x FusionHD's on my startup screen - assuming one of these is Recovery HD - it probably just needs a label tweak. I'm rebooting into it now (with a bit of guesswork on the startup screen). Reboot has loaded the EFI and landed on a blank screen - mouse cursor showing...
- David
Last edited:
Hi David
Hmm, I might have to take another look. Your first attempt had the Recovery HD on the second of the two physical disks. For this attempt, the recovery is on disk1, the first physical disk in the list!
Can you test v7 for me please?
BTW, v7 is a bit more verbose and includes a ton of extra error checking (cos other users on the forums keep messing up by not following the instructions or not waiting for the script to finish!)
Test results.
Code:
CoreStorage deleted and rebuilt. This is what it looks like before the OS is installed.
diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS 300GB 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_CoreStorage Fusion 319.7 GB disk1s2
3: Apple_Boot Boot OS X 134.2 MB disk1s3
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_HFS Macintosh HD 499.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_CoreStorage Fusion 319.7 GB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS FusionHD +632.5 GB disk4
Logical Volume on disk1s2, disk3s2
FE8BA7DA-7175-488B-8ABC-68CC4237DB6B
Unencrypted Fusion Drive
After installation:
diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Fusion 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Macintosh HD 499.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/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_HFS 300GB 319.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_CoreStorage Fusion 319.7 GB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS FusionHD +632.0 GB disk4
Logical Volume on disk0s2, disk3s2
FE8BA7DA-7175-488B-8ABC-68CC4237DB6B
Unencrypted Fusion Drive
Davids-Mac-Pro:~ dgwilson$ diskutil mount /dev/disk0s3
Volume Recovery HD on /dev/disk0s3 mounted
Davids-Mac-Pro:~ dgwilson$ cd /Volumes/Recovery\ HD/
Davids-Mac-Pro:Recovery HD dgwilson$ ls -la com.apple.recovery.boot/
total 974536
drwxr-xr-x 12 root wheel 408 22 Dec 13:39 .
drwxr-xr-x 10 root wheel 408 22 Dec 13:39 ..
drwxr-xr-x 5 root wheel 170 22 Dec 13:24 .diagnostics
-rw-r--r--@ 1 root wheel 1385 22 Dec 13:39 .disk_label
-rw-r--r--@ 1 root wheel 5525 22 Dec 13:39 .disk_label_2x
-rw-r--r--@ 1 root admin 1948 2 Dec 23:02 BaseSystem.chunklist
-rw-r--r--@ 1 root admin 477045122 22 Dec 13:05 BaseSystem.dmg
-rw-r--r-- 1 root wheel 5691 22 Dec 13:39 PlatformSupport.plist
-r--r--r-- 1 root wheel 480 2 Dec 20:38 SystemVersion.plist
-rw-r--r--@ 1 root wheel 314880 22 Dec 13:39 boot.efi
-rw-r--r-- 1 root wheel 365 22 Dec 13:24 com.apple.Boot.plist
-rw-r--r-- 1 root wheel 21563822 2 Dec 20:34 prelinkedkernel
Davids-Mac-Pro:Recovery HD dgwilson$Attempts to reboot into Recovery HD from Startup screen off both available partitions resulted in booting into the normal OS.
Reboot to alternate El Capitan environment to action bless on Fusion Recovery HD
Code:
Mac-Pro-2:~ dgwilson$ diskutil mount /dev/disk1s3
Volume Recovery HD on /dev/disk1s3 mounted
Mac-Pro-2:~ dgwilson$ sudo bless --folder /Volumes/Recovery\ HD/com.apple.recovery.boot --label "FusionRec disk1s3"
Mac-Pro-2:~ dgwilson$ diskutil unmount /dev/disk1s3
Volume Recovery HD on disk1s3 unmountedNow shows as "FusionRec disk1s3" on the startup screen.
Reboot with OPT key select this disk - boots to normal OS on FusionHD.
- David
Sorry David, I've run out of ideas. I'm pretty sure the Recovery HD will have all the correct files in all the correct places. It looks to me like the Fusion gets in the way (presumably because there is something in the low level disk headers that makes it look for the conjoined disk and forces you to boot from that - a bit like an OS soft link I suppose)
Thank you for thinking about it and changing the disk image creation tool.
It's not a big deal for me as there will always be another OS to boot from in the machine.
There is a software update pending to update the recovery partition - so I'll proceed with that now and see what mayhem I can create with that. I see there's a "PlatformSupport.plist" file in com.apple.recovery.boot so I'll take a look at that and check it's contents (not that it matters with 3.1 boot.efi)
- David
Posted as an FYI...
The following did not work. It rebooted into the main Fusion drive after selection FusionRec from the Startup screen.
OS X El Capitan Recovery Update - version 1.0 installed
Reboot to alternate OS X El Capitan
Code:
ioreg -p IODeviceTree -r -n / -d 1
+-o / <class IOPlatformExpertDevice, id 0x100000112, registered, matched, active, busy 0 (30103 ms), retain 30>
{
"compatible" = <"MacPro2,1">
"version" = <"1.0">
"board-id" = <"Mac-F42C88C8">
"IOInterruptSpecifiers" = (<0900000005000000>)
"IOPolledInterface" = "SMCPolledInterface is not serializable"
"serial-number" = <55505a00000000000000000000594d37313630433355505a00000000000000000000000000000000000000>
"IOInterruptControllers" = ("io-apic-0")
"IOPlatformUUID" = "2B12FE1B-1090-593B-B740-2E45F371D1E4"
"clock-frequency" = <00b5644f>
"manufacturer" = <"Apple Computer, Inc.">
"IOConsoleSecurityInterest" = "IOCommand is not serializable"
"IOPlatformSerialNumber" = "YM7160C3UPZ"
"system-type" = <03>
"product-name" = <"MacPro2,1">
"model" = <"MacPro2,1">
"name" = <"/">
"IOBusyInterest" = "IOCommand is not serializable"
}According to PlatformSupport.plist on the Recovery HD - "Mac-F42C88C8" is associated with a MacPro3,1 - so I'll assume this is a trick of the boot.efi.
However... I have modified the PlatformSupport.plist to include the following:
<string>Mac-F4208DC8</string>
<string>Mac-F4208DA9</string>
<string>MacPro1,1</string>
<string>MacPro2,1</string>
Code:
Mac-Pro-2:com.apple.recovery.boot dgwilson$ sudo cp ~/Desktop/PlatformSupport.plist .
Mac-Pro-2:com.apple.recovery.boot dgwilson$ sudo chflags nouchg boot.efi
Mac-Pro-2:com.apple.recovery.boot dgwilson$ sudo cp ~/Desktop/boot.efi .
Mac-Pro-2:com.apple.recovery.boot dgwilson$ sudo chflags uchg boot.efi
Mac-Pro-2:com.apple.recovery.boot dgwilson$ sudo bless --folder /Volumes/Recovery\ HD/com.apple.recovery.boot --label "FusionRec"- David
If you are still testing. One thought crossed my mind.
When I'm testing I like to perform a full disk erase. It gets rid of the Recovery HD (and in your case the other Boot OS X partition).
From your earlier post where you showed diskutil transcript before and after, I notice that before is still showing the diskNs3 partitions.
My suggestion would be to deconstruct your fusion drive again (to the before state). Let's assume disk0 and disk3 as above (although I always check with a diskutil list just to make sure)
Code:
diskutil eraseDisk JHFS+ "300G" /dev/disk0
diskutil eraseDisk JHFS+ "Fusion" /dev/disk3Will perform the full disk erase, setting the resulting single volume to Journaled HFS+ format with the disk name as the quoted text.
At this point you can be sure that there is no residual info from previous builds.
diskutil list to be sure.
Then rebuild your CoreStorage Fusion drive.
I'd be interested to see the content of the Boot OS X partition, and maybe the output of the following command
Code:
gpt -vvv show -l disk0 disk3 disk5Someone claims to have figured it out. See
http://apple.stackexchange.com/ques...ing-recovery-hd-to-a-corestorage-volume-group
http://apple.stackexchange.com/ques...ing-recovery-hd-to-a-corestorage-volume-group
If you are still testing. One thought crossed my mind.
When I'm testing I like to perform a full disk erase. It gets rid of the Recovery HD (and in your case the other Boot OS X partition).
From your earlier post where you showed diskutil transcript before and after, I notice that before is still showing the diskNs3 partitions.
My suggestion would be to deconstruct your fusion drive again (to the before state). Let's assume disk0 and disk3 as above (although I always check with a diskutil list just to make sure)
Code:diskutil eraseDisk JHFS+ "300G" /dev/disk0 diskutil eraseDisk JHFS+ "Fusion" /dev/disk3
Will perform the full disk erase, setting the resulting single volume to Journaled HFS+ format with the disk name as the quoted text.
At this point you can be sure that there is no residual info from previous builds.
diskutil list to be sure.
Then rebuild your CoreStorage Fusion drive.
I'd be interested to see the content of the Boot OS X partition, and maybe the output of the following command
(assuming disk5 is the resulting Fusion device) - but now we're getting into the deep realms of of disk partitions!!!Code:gpt -vvv show -l disk0 disk3 disk5
I haven't put it in my notes (should have)... after I tear down the fusion drive with cs deleteVolume and cs delete - I perform a disk erase with the diskutil gui. I'm happy to repeat the process using the command line. I'll do that tomorrow. ... incidentally I won't get a chance on the 25th... or for another 10 days or so after that.
In the mean time, I've done the gpt command you have requested. The machine is currently booted and running on the Fusion drive.
Code:
Davids-Mac-Pro:~ dgwilson$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS 300GB 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Macintosh HD 499.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/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_CoreStorage Fusion 319.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_CoreStorage Fusion 319.7 GB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS FusionHD +632.0 GB disk4
Logical Volume on disk2s2, disk3s2
FE8BA7DA-7175-488B-8ABC-68CC4237DB6B
Unencrypted Fusion Drive
Davids-Mac-Pro:~ dgwilson$ gpt -vvv show -l disk2 disk3 disk4
gpt show: unable to open device 'disk2': Permission denied
Davids-Mac-Pro:~ dgwilson$ sudo gpt -vvv show -l disk2 disk3 disk4
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
gpt show: disk2: mediasize=320072933376; sectorsize=512; blocks=625142448
gpt show: disk2: PMBR at sector 0
gpt show: disk2: Pri GPT at sector 1
gpt show: disk2: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=40, size=409600
gpt show: disk2: GPT partition: type=53746F72-6167-11AA-AA11-00306543ECAC, start=409640, size=623463232
gpt show: disk2: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=623872872, size=1269536
gpt show: disk2: Sec GPT at sector 625142447
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - "EFI System Partition"
409640 623463232 2 GPT part - "Fusion"
623872872 1269536 3 GPT part - "Recovery HD"
625142408 7
625142415 32 Sec GPT table
625142447 1 Sec GPT header
gpt show: disk3: mediasize=320072933376; sectorsize=512; blocks=625142448
gpt show: disk3: PMBR at sector 0
gpt show: disk3: Pri GPT at sector 1
gpt show: disk3: GPT partition: type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, start=40, size=409600
gpt show: disk3: GPT partition: type=53746F72-6167-11AA-AA11-00306543ECAC, start=409640, size=624470624
gpt show: disk3: GPT partition: type=426F6F74-0000-11AA-AA11-00306543ECAC, start=624880264, size=262144
gpt show: disk3: Sec GPT at sector 625142447
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - "EFI System Partition"
409640 624470624 2 GPT part - "Fusion"
624880264 262144 3 GPT part - "Booter"
625142408 7
625142415 32 Sec GPT table
625142447 1 Sec GPT header
gpt show: unable to open device 'disk4': Resource busyI've just read through it. It doesn't seem to fit this scenario... that is I have a recovery partition... the OS install did create it successfully.
BUT...
I when I've created the fusion drive lately I've done it as
Code:
diskutil cs create Fusion diskN DiskN
Code:
diskutil cs create Fusion diskN DiskNSNI'll try the above tomorrow.
Another reference article. http://hints.macworld.com/article.php?story=2014030311173257
Boot to 300GB drive with El Capitan 10.11.2
Previous Fusion drive deleted. New Fusion drive to be created from disk1 and disk3
Code:
Mac-Pro-2:~ dgwilson$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS 300GB 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Untitled 319.2 GB disk1s2
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_HFS Macintosh HD 499.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS Untitled 319.7 GB disk3s2
Mac-Pro-2:~ dgwilson$ diskutil eraseDisk JHFS+ "untitled" /dev/disk1
Started erase on disk1
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk1s2 as Mac OS Extended (Journaled) with name untitled
Initialized /dev/rdisk1s2 as a 298 GB case-insensitive HFS Plus volume with a 24576k journal
Mounting disk
Finished erase on disk1
Mac-Pro-2:~ dgwilson$ diskutil eraseDisk JHFS+ "untitled" /dev/disk3
Started erase on disk3
Unmounting disk
Creating the partition map
Waiting for the disks to reappear
Formatting disk3s2 as Mac OS Extended (Journaled) with name untitled
Initialized /dev/rdisk3s2 as a 298 GB case-insensitive HFS Plus volume with a 24576k journal
Mounting disk
Finished erase on disk3
Mac-Pro-2:~ dgwilson$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS 300GB 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS untitled 319.7 GB disk1s2
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_HFS Macintosh HD 499.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS untitled 319.7 GB disk3s2
Mac-Pro-2:~ dgwilson$ diskutil cs create Fusion /dev/disk1 /dev/disk3s2
Started CoreStorage operation
Unmounting disk1
Repartitioning disk1
Unmounting disk
Creating the partition map
Rediscovering disk1
Adding disk1s2 to Logical Volume Group
Unmounting disk3s2
Touching partition type on disk3s2
Adding disk3s2 to Logical Volume Group
Creating Core Storage Logical Volume Group
Switching disk1s2 to Core Storage
Switching disk3s2 to Core Storage
Waiting for Logical Volume Group to appear
Discovered new Logical Volume Group "519E61EE-0599-4BFD-9149-E4450C42A86E"
Core Storage LVG UUID: 519E61EE-0599-4BFD-9149-E4450C42A86E
Finished CoreStorage operation
Mac-Pro-2:~ dgwilson$ diskutil cs createVolume 519E61EE-0599-4BFD-9149-E4450C42A86E jhfs+ FusionHD 100%
Started CoreStorage operation
Waiting for Logical Volume to appear
Formatting file system for Logical Volume
Initialized /dev/rdisk4 as a 589 GB case-insensitive HFS Plus volume with a 49152k journal
Mounting disk
Core Storage LV UUID: DF3A3286-002B-4B77-9D3E-8EEB2DA9E284
Core Storage disk: disk4
Finished CoreStorage operation
Mac-Pro-2:~ dgwilson$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS 300GB 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_CoreStorage Fusion 319.7 GB disk1s2
3: Apple_Boot Boot OS X 134.2 MB disk1s3
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_HFS Macintosh HD 499.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_CoreStorage Fusion 319.7 GB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS FusionHD +632.5 GB disk4
Logical Volume on disk1s2, disk3s2
DF3A3286-002B-4B77-9D3E-8EEB2DA9E284
Unencrypted Fusion Drive[ http://hints.macworld.com/article.php?story=2014030311173257 ]
After OS installation.
Code:
Davids-Mac-Pro:~ dgwilson$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage Fusion 319.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Macintosh HD 499.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/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_HFS 300GB 319.2 GB disk2s2
3: Apple_Boot Recovery HD 650.0 MB disk2s3
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *320.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_CoreStorage Fusion 319.7 GB disk3s2
3: Apple_Boot Boot OS X 134.2 MB disk3s3
/dev/disk4 (internal, virtual):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS FusionHD +632.0 GB disk4
Logical Volume on disk0s2, disk3s2
DF3A3286-002B-4B77-9D3E-8EEB2DA9E284
Unencrypted Fusion DriveReboot to Recover HD from startup screen ... boots to FusionHD
Code:
sudo bless --folder /Volumes/Recovery\ HD/com.apple.recovery.boot --label "FusionRec"tried this and reboot to FusionRec as well - yielded the same result.
As an aside ... I'm struggling with this upgrade also getting errors extracting the Essentials.pkg. Thing is I have two of these same Mac Pros .... one with upgraded memory 16GB and the whole process worked FLAWLESSLY and a separate machine full of stock OEM 512 MB DIMMS ... 8 of them for 4 G. I just came upon this after trying the same sort of gyrations (trying multiple drives, etc) and will just swap the memory between the machines and see how that goes..... I think you are on to something with the memory some how causing the issue.
In your second machine... make sure you have at least 12GB of RAM, then repeat the install process.
Curious to know how that goes ... if you are able to retain the 512MB DIMM's - will depending on the available DIMM hardware you have.
- David
Guys, there are at least 5 people who have posted that the OEM 512MB modules cause issues. Who knows if and how many others discovered the same thing. 667MHz is SUPER cheap. I got 32GB for $32 shipped on eBay. Just throw the damn 512MB away and be done with it. Being frugal is one thing, but how much is your time worth to you? I struggled for over a week. Don't be like me.
It is really interesting and THANKS .... I switched out the 512MB DIMMS and put in 16G worth of 2G DIMMS and the install went perfectly. I set things up and then switched back to the 512MB DIMMS. The system booted fine and looked "good" for a few minutes but then the system just kept crashing and rebooting when trying to bring up Safari and just about any app --- not good. Now looking to go back to 12 GB per your recommendation since 4 and 8GB even with the larger DIMMS is not working. It's not that hard a requirement to manage (12GB) but seems a bit odd when the OS requirement sure isn't 12GB.
UPDATE: Well -- I tried the install with 4GB, 8GB, and then 12GB .... and voila, as those reading here already expect, the installation worked without issue with 12 GB RAM going directly to 10.11.2 using a pikify'd USB. After some time, I then dropped both machines to 10 GB (using 4 of the 512 MB DIMMS and 4 of the 2GB DIMMS) and the machines are both running stable for a full day with normal activity. I do have more 2 GB DIMMS ordered so I will go to 16 GB on both machines and get rid of the 512 MB all together but I believe the issue with the 512 MB isn't so much the DIMMS themselves but the fact that if you use them you will be hard pressed to have a config with at least 12 GB total RAM and the installation definitely failed for me with only 8 .... and I did not try 10 GB (yet).
Last edited: