Level 1

17 points

Bootcamp booting clobbered by Yosemite upgrade

I've enjoyed being able to boot into OSX Mavericks or Windows 8.1 for the past year on my MBP (mid 2012, single 500GB SSD) but I recently performed the Yosemite upgrade. The resulting OSX installation appears to work fine but when I hold down the Option key after the chime the option to boot from Bootcamp Windows is missing. Worse, when I set "Startup Disk" to Bootcamp Windows the result fails.

@Loner T usually requests the following Terminal results so here they are:

Last login: Sun Sep 20 22:09:22 on ttys000

My-MacBook-Pro:~ me$ diskutil list

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *512.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 255.3 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 255.5 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *254.9 GB disk1

Logical Volume on disk0s2

F6545BAB-5B31-4838-A188-C59D210B12FB

Unencrypted

==========

My-MacBook-Pro:~ me$ diskutil cs list

CoreStorage logical volume groups (1 found)

+-- Logical Volume Group B8FA8874-F8C3-4EC1-8F53-0F555EDFC166

=========================================================

Name: Macintosh HD

Status: Online

Size: 255250432000 B (255.3 GB)

Free Space: 18907136 B (18.9 MB)

+-< Physical Volume 84E5E470-49E8-4585-AA1D-397BDEA61A3D

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 255250432000 B (255.3 GB)

+-> Logical Volume Family E409753F-A5B6-4DAC-BF6F-17CE4956E11E

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

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

+-> Logical Volume F6545BAB-5B31-4838-A188-C59D210B12FB

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

Disk: disk1

Status: Online

Size (Total): 254879203328 B (254.9 GB)

Conversion Progress: -none-

Revertible: Yes (no decryption required)

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

==========

My-MacBook-Pro:~ me$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=512110190592; sectorsize=512; blocks=1000215216

gpt show: /dev/disk0: PMBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 1000215215

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 498536000 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

498945640 1269536 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

500215176 632

500215808 499077120 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

999292928 922255

1000215183 32 Sec GPT table

1000215215 1 Sec GPT header

==========

My-MacBook-Pro:~ me$ sudo fdisk /dev/disk0

Disk: /dev/disk0 geometry: 62260/255/63 [1000215216 sectors]

Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

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

1: EE 1023 254 63 - 1023 254 63 [ 1 - 1000215215] <Unknown ID>

2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

I would appreciate help getting Bootcamp booting again.

Posted on Sep 20, 2015 8:43 PM

68 replies

trwd Author

Level 1

17 points

Sep 30, 2015 3:58 PM in response to Loner T

First, please know that I greatly appreciate your help here. It is unbelievably gracious of you. Can you help me understand where the following line of reasoning runs off the track?

The HDD copy appears to be identical to the original, and I think you agreed with this earlier today. Doesn't this mean that Terabyte Image for Linux did a good job of cloning the original drive with the exception that the Secondary GPT must be moved to the end of the drive? I had hoped to pin that and move on.

But...

The HDD copy boots fine only when the internal SSD is disconnected from the system. It's a hassle to disconnect the battery and SSD every time I want to switch between booting from the SSD and the HDD so I wondered what prevents both drives from being connected and booting from either.

The Terabyte support tech and I speculated that Macs can't handle two drives having the same GUID, just as Windows PCs cannot tolerate two physical drives with the same Volume ID/Serial Number. So I asked you how to change the GUID, which you helped me do today.

To me the threshold question is: was I wrong believing that the identical GUID's was the obstacle to keeping both drives connected?

Since I have now changed the drive GUID there must be some other obstacle to having both connected. Any idea what it is?

The source disk SSD was NOT reverted prior to cloning. It is unchanged and CoreStorage is still intact. Is the fact that both drives use CoreStorage the reason they both cannot coexist?

trwd Author

Level 1

17 points

Sep 30, 2015 5:53 PM in response to Loner T

I understand that TB IFL's exact copy did not put the GPT secondary 32 sectors from the physical end of last sector, but wasn't that fixed when I changed the GUID and agreed to let this problem be fixed?

So at this point would you agree that the HDD copy is as compatible with the MBP as the original, up to spec, ready to use -- provided it's the only boot drive connected (i.e., the original drive is no longer connected)?

I'd like to close this much of the case if possible.

trwd Author

Level 1

17 points

Sep 30, 2015 5:55 PM in response to Loner T

From the following segment of your reply:

The GUID and the entire connection path are used. There is also boot ability in play here. There is a 'bless' command, which allows EFI and/or MBR (in legacy mode) partitions on how booting is accomplished. With CoreStorage in place, you will have metadata and journaling conflicts which are used for recovery purposes in CS settings. JHFS+ is much simpler, and once you change the disk GUIDs, the journals and identity are unique.

I gather that the answer to my "threshold question":

Was I wrong believing that the identical GUID's was the obstacle to keeping both drives connected?

.. is: Yes, you (OP) were wrong; other factors related to both drives using CoreStorage are an obstacle to using an original drive and its clone connected at the same time.

Do you agree with the above?

Loner T

Level 9

59,536 points

Sep 30, 2015 5:55 PM in response to trwd

trwd wrote:

I understand that TB IFL's exact copy did not put the GPT secondary 32 sectors from the physical end of last sector, but wasn't that fixed when I changed the GUID and agreed to let this problem be fixed?

It is expected behavior and expected result. Gdisk should have corrected it as long as we did the write and reboot. You can also check it on the destination with the GPT command.

So at this point would you agree that the HDD copy is as compatible with the MBP as the original, up to spec, ready to use -- provided it's the only boot drive?

It would be good to address this as well. One test I would suggest is using a 16Gb Flash disk with the HDD connected, booting from the Recovery HD on the HDD (using Al/Option key), and installing OS X on the 16GB USB and booting from it to ensure external disks do not see any other issues.

I'd like to close this much of the case if possible.

Certainly. Can you also test backing up the OS X and Windows partitions? It will help in ensuring recoverability of both OSes without any further issues. Time Machine uses the disk GUIDs of what is being backed up and the partition information as well as Recovery HD. We should ensure reliability for any future use. You do not want any underlying issues to come back later and cause more problems.

Loner T

Level 9

59,536 points

Sep 30, 2015 5:58 PM in response to trwd

trwd wrote:

From the following segment of your reply:

The GUID and the entire connection path are used. There is also boot ability in play here. There is a 'bless' command, which allows EFI and/or MBR (in legacy mode) partitions on how booting is accomplished. With CoreStorage in place, you will have metadata and journaling conflicts which are used for recovery purposes in CS settings. JHFS+ is much simpler, and once you change the disk GUIDs, the journals and identity are unique.

I gather that the answer to my "threshold question":

Was I wrong believing that the identical GUID's was the obstacle to keeping both drives connected?

.. is: Yes, you (OP) were wrong; other factors related to both drives using CoreStorage are an obstacle to using an original drive and its clone connected at the same time.

Do you agree with the above?

No, you are not wrong. There are additional parameters to the equation, this being one. Do not short-change yourself. 😉

trwd Author

Level 1

17 points

Oct 1, 2015 6:48 AM in response to Loner T

(re the last sentence in your reply: "In addition, you are also going to boot...")

Ah, so the goal is to test booting from the USB flash drive. Got it.

While you didn't say yes or no to my idea of disabling CS on the HDD I see that you wrote "HDD (no CS)" so I assume you think it's worth a try. Let me know if not. I won't be able to do this until later today.

Loner T

Level 9

59,536 points

Oct 1, 2015 7:01 AM in response to trwd

trwd wrote:

(re the last sentence in your reply: "In addition, you are also going to boot...")

Ah, so the goal is to test booting from the USB flash drive. Got it.

While you didn't say yes or no to my idea of disabling CS on the HDD I see that you wrote "HDD (no CS)" so I assume you think it's worth a try. Let me know if not. I won't be able to do this until later today.

In one of my previous reposes, I had

Run diskutil cs revert on the HDD only.

Yes, only revert the HDD to non-CS and test connecting both with a USB Flash boot device, and then test booting individually from the HDD and SSD. Bootcamp from the clones external HDD is unlikely to work due to Windows restrictions. Test when you can. 😉

trwd Author

Level 1

17 points

Oct 2, 2015 12:47 PM in response to Loner T

I'm back and ready to run "diskutil cs revert" on the HDD but I don't know how to get the correct UUID for the HDD. You wrote previously:

diskutil cs revert F6545BAB-5B31-4838-A188-C59D210B12FB

(The UUID came from your diskutil cs list output). This will expose the underlying JHFS+ volume which is a regular partition on disk. You can clone the disk using Terabyte or at least try and it and test it.

I ran "diskutil cs list" and got the following results but I don't understand the hierarchical structure of the report.

Last login: Fri Oct 2 12:31:09 on console

diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group B8FA8874-F8C3-4EC1-8F53-0F555EDFC166

=========================================================

Name: Macintosh HD

Status: Online

Size: 255250432000 B (255.3 GB)

Free Space: 18907136 B (18.9 MB)

|

+-< Physical Volume 84E5E470-49E8-4585-AA1D-397BDEA61A3D

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 255250432000 B (255.3 GB)

|

+-> Logical Volume Family E409753F-A5B6-4DAC-BF6F-17CE4956E11E

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

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

|

+-> Logical Volume F6545BAB-5B31-4838-A188-C59D210B12FB

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

Disk: disk1

Status: Online

Size (Total): 254879203328 B (254.9 GB)

Conversion Progress: -none-

Revertible: Yes (no decryption required)

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

Since the last 4 digits of the UUID match the UUID of a logical volume on disk1 (the SSD), I assume I'm looking for its equivalent on the HDD.

Please advise. BTW, at one point I asked you what "Disk1" refers to since in reality there are two physical disks: Disk0 (SSD) and Disk2 (HDD - USB). Would you mind digressing briefly and telling me how to interpret the above report -- or is it incomplete? Thanks.

trwd Author

Level 1

17 points

Oct 2, 2015 1:25 PM in response to trwd

The following is with the internal SSD connected to SATA and the external HDD clone -- ready to have Corestorage disabled using "convert" - connected to one of the USB 3 ports on my MBP.

I ran "diskutil cs list" and got the following results but I don't understand if the desired UUID is listed.

Last login: Fri Oct 2 12:31:09 on console

diskutil cs list

CoreStorage logical volume groups (1 found)

|

+-- Logical Volume Group B8FA8874-F8C3-4EC1-8F53-0F555EDFC166

=========================================================

Name: Macintosh HD

Status: Online

Size: 255250432000 B (255.3 GB)

Free Space: 18907136 B (18.9 MB)

|

+-< Physical Volume 84E5E470-49E8-4585-AA1D-397BDEA61A3D

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 255250432000 B (255.3 GB)

|

+-> Logical Volume Family E409753F-A5B6-4DAC-BF6F-17CE4956E11E

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

Encryption Status: Unlocked

Encryption Type: None

Conversion Status: NoConversion

Conversion Direction: -none-

Has Encrypted Extents: No

Fully Secure: No

Passphrase Required: No

|

+-> Logical Volume F6545BAB-5B31-4838-A188-C59D210B12FB

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

Disk: disk1

Status: Online

Size (Total): 254879203328 B (254.9 GB)

Conversion Progress: -none-

Revertible: Yes (no decryption required)

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

Loner T

Level 9

59,536 points

Oct 2, 2015 2:36 PM in response to trwd

If the external disk is connected, we should see it's CS entry as well. Does diskutil list show both disks connected? If yes, do they both show up as Corestorage volumes? If they were cloned, you may have a CS UUID conflict. Check for any errors in Applications -> Utilities -> Console logs.

trwd Author

Level 1

17 points

Oct 2, 2015 3:05 PM in response to Loner T

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *512.1 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_CoreStorage 255.3 GB disk0s2

3: Apple_Boot Recovery HD 650.0 MB disk0s3

4: Microsoft Basic Data BOOTCAMP 255.5 GB disk0s4

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD *254.9 GB disk1

Logical Volume on disk0s2

F6545BAB-5B31-4838-A188-C59D210B12FB

Unencrypted

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.5 TB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_CoreStorage 255.3 GB disk2s2

3: Apple_Boot Recovery HD 650.0 MB disk2s3

4: Microsoft Basic Data BOOTCAMP 255.5 GB disk2s4

trwd Author

Level 1

17 points

Oct 2, 2015 3:18 PM in response to Loner T

attached is the log. I first cleared the log, then reconnected the USB HDD to log after that. At the end I see some "failed" items.

No attachments allowed I guess. Pasted below. Sorry. It's verbose.

10/2/15 5:08:33.000 PM

0x55aa 0x100, 3

10/2/15 5:08:35.132 PM

10/2/15 5:08:35.133 PM

10/2/15 5:08:35.134 PM

10/2/15 5:08:35.000 PM

84E5E470-49E8-4585-AA1D-397BDEA61A3D in group "Macintosh HD" (B8FA8874-F8C3-4EC1-8F53-0F555EDFC166).

kernel[0] USBMSC

Identifier (non-unique): 0123456789ABCDEF 0x174c

WDSecurityHelper[313]

kernel[0] CoreStorage::startPhysicalVolume detected duplicate pv

10/2/15 5:08:35.134 PM

10/2/15 5:08:35.135 PM

AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/AS2105@15200000 /IOUSBInterface@0/

IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub/IOSCSIPeripheralDeviceType00/IOB lockStorageServices

10/2/15 5:08:35.135 PM

WDSecurityHelper[313]

DAMediaWhole=1

DAMediaBSDName=disk2

DAMediaSize=1500301910016

DAMediaKind=IOMedia

DAMediaIcon={

WDSecurityHelper[313]

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

IOBundleResourceFile = "USBHD.icns";

}

10/2/15 5:08:35.135 PM

10/2/15 5:08:35.136 PM

10/2/15 5:08:35.137 PM

@2:0

10/2/15 5:08:35.137 PM

10/2/15 5:08:35.156 PM

disk2s2

WDSecurityHelper[313]

DADeviceProtocol=USB

DAAppearanceTime=465516515.073202

DAMediaBSDMajor=1

DADeviceModel=003-9YN16G

DAMediaBSDMinor=6

DAMediaWritable=1

DAMediaName=ST1500DM 003-9YN16G Media

DAVolumeNetwork=0

DAMediaBSDUnit=2

DAMediaBlockSize=512

DADeviceVendor=ST1500DM

DAMediaPath=IODeviceTree:/PCI0@0/XHC1@14/

DAMediaRemovable=0

DADeviceRevision=HP16

DABusName=XHC1

isDiskACDROMDevice = FALSE

userIsActive = TRUE

UnrecognizedDiskPeek called for device

10/2/15 5:08:35.156 PM

10/2/15 5:08:35.157 PM

AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/AS2105@15200000 /IOUSBInterface@0/

IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub/IOSCSIPeripheralDeviceType00/IOB lockStorageServices

10/2/15 5:08:35.157 PM

WDSecurityHelper[313]

DAMediaWhole=1

DAMediaBSDName=disk2

DAMediaSize=1500301910016

DAMediaKind=IOMedia

DAMediaIcon={

WDSecurityHelper[313]

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

IOBundleResourceFile = "USBHD.icns";

}

10/2/15 5:08:35.157 PM

10/2/15 5:08:35.158 PM

WDSecurityHelper[313]

DADeviceProtocol=USB

DAAppearanceTime=465516515.073202

DAMediaBSDMajor=1

DADeviceModel=003-9YN16G

DAMediaBSDMinor=6

DAMediaWritable=1

DAMediaName=ST1500DM 003-9YN16G Media

DAVolumeNetwork=0

DAMediaBSDUnit=2

DAMediaBlockSize=512

mountApproval for device disk2s4

isDiskACDROMDevice

DAMediaLeaf=0

DADeviceUnit=2

DADeviceInternal=0

DAMediaEjectable=0

DABusPath=IODeviceTree:/PCI0@0/XHC1@14

DAMediaContent=GUID_partition_scheme

DADevicePath=IOService:/

isDiskACDROMDevice

DAMediaLeaf=0

DADeviceUnit=2

DADeviceInternal=0

DAMediaEjectable=0

DABusPath=IODeviceTree:/PCI0@0/XHC1@14

DAMediaContent=GUID_partition_scheme

DADevicePath=IOService:/

10/2/15 5:08:35.158 PM

@2:0

10/2/15 5:08:35.158 PM

10/2/15 5:08:35.159 PM

10/2/15 5:08:35.160 PM

AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/AS2105@15200000 /IOUSBInterface@0/

IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub/IOSCSIPeripheralDeviceType00/IOB lockStorageServices

10/2/15 5:08:35.161 PM

WDSecurityHelper[313]

DAMediaWhole=1

DAMediaBSDName=disk2

DAMediaSize=1500301910016

DAMediaKind=IOMedia

DAMediaIcon={

IOBundleResourceFile = "USBHD.icns";

}

WDSecurityHelper[313]

DADeviceVendor=ST1500DM

DAMediaPath=IODeviceTree:/PCI0@0/XHC1@14/

WDSecurityHelper[313]

DAMediaRemovable=0

DADeviceRevision=HP16

DABusName=XHC1

isDiskACDROMDevice = FALSE

mountApproval for device disk2s1

isDiskACDROMDevice

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

10/2/15 5:08:35.161 PM

10/2/15 5:08:35.162 PM

@2:0

10/2/15 5:08:35.162 PM

10/2/15 5:08:35.163 PM

10/2/15 5:08:35.000 PM

10/2/15 5:08:35.649 PM

10/2/15 5:08:35.650 PM

disk2s4

10/2/15 5:08:35.651 PM

disk2s1

10/2/15 5:08:35.666 PM

Bootstrapped Creating a default store:1 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/BOOTCAMP 1 10/2/15 5:08:35.673 PM WDSecurityHelper[313] {

DAAppearanceTime = "465516515.075413";

DABusName = XHC1;

DABusPath = "IODeviceTree:/PCI0@0/XHC1@14";

DADeviceInternal = 0;

DADeviceModel = "003-9YN16G";

DADevicePath = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/

AS2105@15200000/IOUSBInterface@0/IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub /

IOSCSIPeripheralDeviceType00/IOBlockStorageServices";

DADeviceProtocol = USB;

DADeviceRevision = HP16;

DADeviceUnit = 2;

DADeviceVendor = ST1500DM;

DAMediaBSDMajor = 1;

DAMediaBSDMinor = 8;

DAMediaBSDName = disk2s4;

DAMediaBSDUnit = 2;

DAMediaBlockSize = 512;

DAMediaContent = "EBD0A0A2-B9E5-4433-87C0-68B6B72699C7";

WDSecurityHelper[313]

DADeviceProtocol=USB

DAAppearanceTime=465516515.073202

DAMediaBSDMajor=1

DADeviceModel=003-9YN16G

DAMediaBSDMinor=6

DAMediaWritable=1

DAMediaName=ST1500DM 003-9YN16G Media

DAVolumeNetwork=0

DAMediaBSDUnit=2

DAMediaBlockSize=512

DADeviceVendor=ST1500DM

DAMediaPath=IODeviceTree:/PCI0@0/XHC1@14/

WDSecurityHelper[313]

kernel[0] NTFS volume name BOOTCAMP, version 3.1.

WDSecurityHelper[313]

MountableVolumeAppeared for device disk2s4

MountableVolumeAppeared for device disk2s1

processMountableVolumeApperance for device

DAMediaLeaf=0

DADeviceUnit=2

DADeviceInternal=0

DAMediaEjectable=0

DABusPath=IODeviceTree:/PCI0@0/XHC1@14

DAMediaContent=GUID_partition_scheme

DADevicePath=IOService:/

DAMediaRemovable=0

DADeviceRevision=HP16

DABusName=XHC1

isDiskACDROMDevice = FALSE

WDSecurityHelper[313]

mds[55] (Volume.Normal:2464) volume:0x7ffb34818000 **********

processMountableVolumeApperance for device

DAMediaEjectable = 0;

DAMediaIcon = {

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

IOBundleResourceFile = "USBHD.icns";

};

DAMediaKind = IOMedia;

DAMediaLeaf = 1;

DAMediaName = BOOTCAMP;

DAMediaPath = "IODeviceTree:/PCI0@0/XHC1@14/@2:4";

DAMediaRemovable = 0;

DAMediaSize = 255527485440;

DAMediaUUID = "<CFUUID 0x610000021840> 8ABE4F53-9BDE-4367-BBD1-8E21676DD18B";

DAMediaWhole = 0;

DAMediaWritable = 1;

DAVolumeKind = ntfs;

DAVolumeMountable = 1;

DAVolumeName = BOOTCAMP;

DAVolumeNetwork = 0;

DAVolumePath = "file:///Volumes/BOOTCAMP%201/";

DAVolumeUUID = "<CFUUID 0x610000022fc0> A4021B5A-1460-47AC-8600-E7E5D1CE5D2F";

}

10/2/15 5:08:35.674 PM

10/2/15 5:08:35.675 PM

10/2/15 5:08:35.676 PM

10/2/15 5:08:35.677 PM

10/2/15 5:08:35.681 PM

10/2/15 5:08:35.682 PM

10/2/15 5:08:35.683 PM

AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/AS2105@15200000 /IOUSBInterface@0/

IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub/IOSCSIPeripheralDeviceType00/IOB lockStorageServices

10/2/15 5:08:35.684 PM

WDSecurityHelper[313]

DAMediaWhole=1

DAMediaBSDName=disk2

DAMediaSize=1500301910016

DAMediaKind=IOMedia

DAMediaIcon={

WDSecurityHelper[313]

isSupportedPid

IOGUIDPartitionScheme

IOMedia

IOBlockStorageDriver

IOBlockStorageServices

IOSCSIPeripheralDeviceType00

IOSCSIPeripheralDeviceNub

IOUSBMassStorageClass

IOUSBInterface

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

IOBundleResourceFile = "USBHD.icns";

}

10/2/15 5:08:35.685 PM

10/2/15 5:08:35.686 PM

10/2/15 5:08:35.687 PM

@2:0

10/2/15 5:08:35.687 PM

10/2/15 5:08:35.688 PM

WDSecurityHelper[313]

DADeviceProtocol=USB

DAAppearanceTime=465516515.073202

DAMediaBSDMajor=1

DADeviceModel=003-9YN16G

DAMediaBSDMinor=6

DAVolumeMountable=0

DAMediaWritable=1

DAMediaName=ST1500DM 003-9YN16G Media

DAVolumeNetwork=0

DAMediaBSDUnit=2

DAMediaBlockSize=512

DADeviceVendor=ST1500DM

DAMediaPath=IODeviceTree:/PCI0@0/XHC1@14/

DAMediaRemovable=0

DADeviceRevision=HP16

DABusName=XHC1

isDiskACDROMDevice = FALSE

userIsActive = TRUE

IOUSBDevice

pidIsSupported = FALSE

disk2s4 is not supported...

mountApproval for device disk2s3

isDiskACDROMDevice

DAMediaLeaf=0

DADeviceUnit=2

DADeviceInternal=0

DAMediaEjectable=0

DABusPath=IODeviceTree:/PCI0@0/XHC1@14

DAMediaContent=GUID_partition_scheme

DADevicePath=IOService:/

10/2/15 5:08:35.688 PM

10/2/15 5:08:35.689 PM

10/2/15 5:08:35.690 PM

AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/AS2105@15200000 /IOUSBInterface@0/

IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub/IOSCSIPeripheralDeviceType00/IOB lockStorageServices

WDSecurityHelper[313]

UnrecognizedDiskPeek called for device disk2

isDiskACDROMDevice

DAMediaLeaf=0

DADeviceUnit=2

10/2/15 5:08:35.690 PM

10/2/15 5:08:35.691 PM

WDSecurityHelper[313]

DAMediaWhole=1

DAMediaBSDName=disk2

DAMediaSize=1500301910016

DAMediaKind=IOMedia

DAMediaIcon={

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

IOBundleResourceFile = "USBHD.icns";

}

10/2/15 5:08:35.691 PM

10/2/15 5:08:35.692 PM

10/2/15 5:08:35.693 PM

@2:0

10/2/15 5:08:35.693 PM

10/2/15 5:08:35.694 PM

10/2/15 5:08:35.695 PM

disk2s3

WDSecurityHelper[313]

DADeviceProtocol=USB

DAAppearanceTime=465516515.073202

DAMediaBSDMajor=1

DADeviceModel=003-9YN16G

DAMediaBSDMinor=6

DAVolumeMountable=0

DAMediaWritable=1

DAMediaName=ST1500DM 003-9YN16G Media

DAVolumeNetwork=0

DAMediaBSDUnit=2

DAMediaBlockSize=512

DADeviceVendor=ST1500DM

DAMediaPath=IODeviceTree:/PCI0@0/XHC1@14/

DAMediaRemovable=0

DADeviceRevision=HP16

DABusName=XHC1

isDiskACDROMDevice = FALSE

MountableVolumeAppeared for device disk2s3

processMountableVolumeApperance for device

10/2/15 5:08:35.700 PM

DAAppearanceTime = "465516515.074008";

DABusName = XHC1;

DABusPath = "IODeviceTree:/PCI0@0/XHC1@14";

DADeviceInternal = 0;

DADeviceModel = "003-9YN16G";

DADevicePath = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/

AS2105@15200000/IOUSBInterface@0/IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub /

IOSCSIPeripheralDeviceType00/IOBlockStorageServices";

DADeviceProtocol = USB;

DADeviceRevision = HP16;

DADeviceUnit = 2;

DADeviceVendor = ST1500DM;

DAMediaBSDMajor = 1;

DAMediaBSDMinor = 7;

DAMediaBSDName = disk2s3;

DAMediaBSDUnit = 2;

DAMediaBlockSize = 512;

DAMediaContent = "426F6F74-0000-11AA-AA11-00306543ECAC";

DAMediaEjectable = 0;

DAMediaIcon = {

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

IOBundleResourceFile = "USBHD.icns";

};

DAMediaKind = IOMedia;

DAMediaLeaf = 1;

DAMediaName = "Recovery HD";

DAMediaPath = "IODeviceTree:/PCI0@0/XHC1@14/@2:3";

DAMediaRemovable = 0;

DAMediaSize = 650002432;

DAMediaUUID = "<CFUUID 0x618000023300> 762EA4AA-4CFC-4D62-B20F-D87129B2DCE2";

WDSecurityHelper[313]

{

DADeviceInternal=0

DAMediaEjectable=0

DABusPath=IODeviceTree:/PCI0@0/XHC1@14

DAMediaContent=GUID_partition_scheme

DADevicePath=IOService:/

DAMediaWhole = 0;

DAMediaWritable = 1;

DAVolumeKind = hfs;

DAVolumeMountable = 1;

DAVolumeName = "Recovery HD";

DAVolumeNetwork = 0;

DAVolumeUUID = "<CFUUID 0x6180000233a0> 57FA46B1-E13E-3579-A93C-C2FCC1D01D75";

}

10/2/15 5:08:35.701 PM

10/2/15 5:08:35.702 PM

10/2/15 5:08:35.703 PM

10/2/15 5:08:35.704 PM

10/2/15 5:08:35.807 PM

WDSecurityHelper[313]

isSupportedPid

IOGUIDPartitionScheme

IOMedia

IOBlockStorageDriver

IOBlockStorageServices

IOSCSIPeripheralDeviceType00

IOSCSIPeripheralDeviceNub

IOUSBMassStorageClass

IOUSBInterface

IOUSBDevice

pidIsSupported = FALSE

disk2s3 is not supported...

{

DAAppearanceTime = "465516515.074721";

DABusName = XHC1;

DABusPath = "IODeviceTree:/PCI0@0/XHC1@14";

DADeviceInternal = 0;

DADeviceModel = "003-9YN16G";

DADevicePath = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC1@14/AppleUSBXHCI/

AS2105@15200000/IOUSBInterface@0/IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub /

IOSCSIPeripheralDeviceType00/IOBlockStorageServices";

DADeviceProtocol = USB;

DADeviceRevision = HP16;

DADeviceUnit = 2;

DADeviceVendor = ST1500DM;

DAMediaBSDMajor = 1;

DAMediaBSDMinor = 9;

DAMediaBSDName = disk2s1;

DAMediaBSDUnit = 2;

DAMediaBlockSize = 512;

DAMediaContent = "C12A7328-F81F-11D2-BA4B-00A0C93EC93B";

DAMediaEjectable = 0;

DAMediaIcon = {

CFBundleIdentifier = "com.apple.iokit.IOSCSIArchitectureModelFamily";

IOBundleResourceFile = "USBHD.icns";

};

DAMediaKind = IOMedia;

DAMediaLeaf = 1;

DAMediaName = "EFI System Partition";

DAMediaPath = "IODeviceTree:/PCI0@0/XHC1@14/@2:1";

DAMediaRemovable = 0;

DAMediaSize = 209715200;

DAMediaUUID = "<CFUUID 0x608000023cc0> 3F03187B-0E58-402F-A712-F86E70CFA2ED";

DAMediaWhole = 0;

DAMediaWritable = 1;

DAVolumeKind = msdos;

DAVolumeMountable = 1;

DAVolumeName = EFI;

DAVolumeNetwork = 0;

DAVolumeUUID = "<CFUUID 0x6080000226a0> 0E239BC6-F960-3107-89CF-1C97F78BB46B";

}

10/2/15 5:08:35.808 PM

10/2/15 5:08:35.809 PM

WDSecurityHelper[313]

isSupportedPid

IOGUIDPartitionScheme

IOMedia

IOBlockStorageDriver

IOBlockStorageServices

IOSCSIPeripheralDeviceType00

IOSCSIPeripheralDeviceNub

IOUSBMassStorageClass

IOUSBInterface

IOUSBDevice

pidIsSupported = FALSE

disk2s1 is not supported...

Loner T

Level 9

59,536 points

Oct 2, 2015 3:45 PM in response to trwd

84E5E470-49E8-4585-AA1D-397BDEA61A3D in group "Macintosh HD" (B8FA8874-F8C3-4EC1-8F53-0F555EDFC166).

kernel[0] USBMSC

Identifier (non-unique): 0123456789ABCDEF 0x174c

The cloning process duplicated the UUIDs. Can you disconnect the SATA cable and only the USB? This will allow

1. Reverting the CS on the USB.

2. Randomizing the UUIDs on the jhfs+ exposed on the USB, using Gdisk.

3. Connect the SATA and test coexistence.

trwd Author

Level 1

17 points

Oct 2, 2015 7:27 PM in response to Loner T

I removed the SSD and booted from the external USB HDD. Went fine. Results of reversion:

+-> Logical Volume F6545BAB-5B31-4838-A188-C59D210B12FB

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

Disk: disk1

Status: Online

Size (Total): 254879203328 B (254.9 GB)

Conversion Progress: -none-

Revertible: Yes (no decryption required)

LV Name: Macintosh HD

Volume Name: Macintosh HD

Content Hint: Apple_HFS

diskutil cs revert F6545BAB-5B31-4838-A188-C59D210B12FB

Started CoreStorage operation on disk1 Macintosh HD

Switching partition from Core Storage type to original type

Reclaiming space formerly used by Core Storage metadata

Even though the disk is now fully reverted, you should reboot soon to re-mount your reverted disk from the actual original partition

Removing Physical Volume

Destroying Logical Volume Group

Remounting former Physical Volume as normal disk

Core Storage LV UUID: F6545BAB-5B31-4838-A188-C59D210B12FB

Core Storage disk: disk0s2

Finished CoreStorage operation on disk1 Macintosh HD

I then powered down, then booted to HDD to test it. I held the Option key down. I noted that two drives were shown (both external according to the icon): Macintosh HD and Recovery. So I assume disabling CS reveals the Recovery volume. I then changed the UUID using GDISK as you taught me earlier in this thread. That worked. Shut down, then booted again to make sure all was still okay with just the HDD connected. Worked.

After shutting down again I installed the SSD and booted with both drives connected (Option key held down). Three drives appeared: the SSD "Macintosh HD", the HDD "Macintosh HD", and the HDD Recovery. I chose the HDD "Macintosh HD" because prior to disabling CS and changing the UUID the system would insist on booting from the SSD regardless of which drive I chose.

During boot there was more activity from the HDD but I still couldn't tell whether the system booted from the SSD or the HDD. It seemed to boot fairly quickly, which makes me think it was the SSD. Below are the results of the two commands you taught me earlier. In your original instructions you referred to something being highlighted but I saw nothing highlighted so I still don't know how to interpret the following results.

df -h

Filesystem Size Used Avail Capacity iused ifree %iused Mounted on

/dev/disk1 237Gi 128Gi 109Gi 55% 33743373 28482993 54% /

devfs 187Ki 187Ki 0Bi 100% 646 0 100% /dev

/dev/disk0s4 238Gi 79Gi 159Gi 34% 226985 166903311 0% /Volumes/BOOTCAMP

map -hosts 0Bi 0Bi 0Bi 100% 0 0 100% /net

map auto_home 0Bi 0Bi 0Bi 100% 0 0 100% /home

/dev/disk2s2 238Gi 135Gi 102Gi 57% 35479200 26837798 57% /Volumes/Macintosh HD 1

/dev/disk2s4 238Gi 79Gi 159Gi 34% 226985 166903311 0% /Volumes/BOOTCAMP 1

diskutil info /

Device Identifier: disk1

Device Node: /dev/disk1

Part of Whole: disk1

Device / Media Name: Macintosh HD

Volume Name: Macintosh HD

Mounted: Yes

Mount Point: /

File System Personality: Journaled HFS+

Type (Bundle): hfs

Name (User Visible): Mac OS Extended (Journaled)

Journal: Journal size 40960 KB at offset 0xee7000

Owners: Enabled

Content (IOContent): Apple_HFS

OS Can Be Installed: Yes

Recovery Disk: disk0s3

Media Type: Generic

Protocol: SATA

SMART Status: Not Supported

Volume UUID: 43D11CC9-E023-3B57-BB38-65F4C8E23CC9

Disk / Partition UUID: F6545BAB-5B31-4838-A188-C59D210B12FB

Total Size: 254.9 GB (254879203328 Bytes) (exactly 497810944 512-Byte-Units)

Volume Free Space: 116.7 GB (116666339328 Bytes) (exactly 227863944 512-Byte-Units)

Device Block Size: 512 Bytes

Allocation Block Size: 4096 Bytes

Read-Only Media: No

Read-Only Volume: No

Ejectable: No

Whole: Yes

Internal: Yes

Solid State: Yes

OS 9 Drivers: No

Low Level Format: Not supported

This disk is a Core Storage Logical Volume (LV). Core Storage Information:

LV UUID: F6545BAB-5B31-4838-A188-C59D210B12FB

LVF UUID: E409753F-A5B6-4DAC-BF6F-17CE4956E11E

LVG UUID: B8FA8874-F8C3-4EC1-8F53-0F555EDFC166

Fusion Drive: No

Encrypted: No

Loner T

Level 9

59,536 points

Oct 2, 2015 8:29 PM in response to trwd

No, neither procedure will render you Mac unusable. The internal SATA SSD content or the HDD content is not begin modified in anyway with these two procedures. You may want to look through the two links which explains the details of exactly what is being done in each.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Bootcamp booting clobbered by Yosemite upgrade