trwd
Level 1 (15 points)
Audio

Q: 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

by trwd,Solvedanswer
trwd trwd
Level 1 (15 points)
Audio
A:

Loner T has been incredibly patient and helpful. Apple should be paying him!

 

I had to put this recovery project on hold starting Oct 3rd and was unable to return to it until today.  Early in the thread Loner T provided instructions for recreating the Bootcamp boot record but I was wary about performing that operation to my Mac without first making a valid clone of the SSD. I discovered in the process that Terabyte's Image for Linux can successfully create a clone or image of the entire Mac drive. But I then got bogged down trying to have both the clone (in a USB 3 dock) and the SSD online, and boot from either. (I wanted to first perform the boot record recovery on the clone instead of my original SSD.) That probably occupied the last couple pages of this thread.

 

Upon returning to the project tonight and trying to figure out where we had left off I decided to try an entirely different approach to solving the problem.

 

I bought and installed Winclone Basic. I used it to make an image of the Bootcamp partition (remember: it's been visible all this time; the upgrade to Yosemite just screwed up booting to it).  Then I restored that image. Russell Scheil of Two Canoes Software had told me that Winclone would recreate the boot record as part of its restore process.

 

I'm happy to report that after rebooting and holding down the Option key my Bootcamp partition is once again accessible. It's baaack!

 

Thank you to Loner T and to Russell Scheil for your help.

Posted on Nov 10, 2015 10:27 PM

Close
trwd

Q: Bootcamp booting clobbered by Yosemite upgrade

  • All replies
  • Helpful answers

Previous Page 2 of 5 last Next

  • by Loner T,

    Loner T Loner T Sep 28, 2015 12:59 PM in response to trwd
    Level 7 (24,098 points)
    Safari
    Sep 28, 2015 12:59 PM in response to trwd

    Yes, a Mac will boot OSX from an external drive. See How to install OS X on an external drive connected to your Mac - Apple Support as an example. You can boot form the internal disk which si working, attach the clone a san external disk and use a utility like GPT or GPT Fdisk to examine GUIDs on each disk.

     

    Clonezilla may use methods like U*ix DD to make an exact replica, including the GUIDs.

     

    GPT Command

     

    sudo gpt -vv -r show /dev/disk0

    Password:

    gpt show: /dev/disk0: mediasize=1000555581440; sectorsize=512; blocks=1954210120

    gpt show: /dev/disk0: Suspicious MBR at sector 0

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

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

           start        size  index  contents

               0           1         MBR

               1           1         Pri GPT header

               2          32         Pri GPT table

              34           6        

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

          409640  1448624648      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC

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

      1450303824        1712        

      1450305536   503904256      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

      1954209792         295        

      1954210087          32         Sec GPT table

      1954210119           1         Sec GPT header

     

    GPT Fdisk Commands

     

    sudo gdisk -l /dev/disk0

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: hybrid

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with hybrid MBR; using GPT.

    Disk /dev/disk0: 1954210120 sectors, 931.8 GiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 6ED0C429-00D1-4759-B50E-04B6FB80D0E3

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 1954210086

    Partitions will be aligned on 8-sector boundaries

    Total free space is 2013 sectors (1006.5 KiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640      1449034287   690.8 GiB   AF00  Customer

       3      1449034288      1450303823   619.9 MiB   AB00  Recovery HD

       4      1450305536      1954209791   240.3 GiB   0700  BOOTCAMP

     

    sudo gdisk /dev/disk0

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: hybrid

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with hybrid MBR; using GPT.

     

    Command (? for help): p

    Disk /dev/disk0: 1954210120 sectors, 931.8 GiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 6ED0C429-00D1-4759-B50E-04B6FB80D0E3

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 1954210086

    Partitions will be aligned on 8-sector boundaries

    Total free space is 2013 sectors (1006.5 KiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640      1449034287   690.8 GiB   AF00  Customer

       3      1449034288      1450303823   619.9 MiB   AB00  Recovery HD

       4      1450305536      1954209791   240.3 GiB   0700  BOOTCAMP

     

    Command (? for help): i

    Partition number (1-4): 1

    Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System)

    Partition unique GUID: 9BE44DE5-9AA9-4F22-9DDF-B6D13A28C14A

    First sector: 40 (at 20.0 KiB)

    Last sector: 409639 (at 200.0 MiB)

    Partition size: 409600 sectors (200.0 MiB)

    Attribute flags: 0000000000000000

    Partition name: 'EFI System Partition'

  • by trwd,

    trwd trwd Sep 28, 2015 4:30 PM in response to Loner T
    Level 1 (15 points)
    Audio
    Sep 28, 2015 4:30 PM in response to Loner T

    Thank you Loner T.  Your reply may be a little beyond my understanding but (to confirm) I believe you told me how to see the GUID's on both internal and external drive.

     

    You wrote earlier:

     

    Bootcamp is a NTFS partition/volume, while Macintosh HD is a LVG/LV combination. A LVG can contain more than LV. You should check with CloneZilla . It is unlikely that such tools understand the LVG/LV abstractions.

     

    When I emailed Terabyte (Image for Linux) Support with the news that the external copy did not boot I included the above comment from you. He replied with the following, which is equally beyond my understanding. Perhaps you will understand what he wrote, though.  All I was able to deduce is that he's suggesting I try an option that copies all sectors.  I wish you could correspond directly with him and arrive at a go/no-go conclusion as to whether Terabyte Image for Linux can make a perfect copy. I think it can but the Devil's in the Details (the settings).

     

    If you are not using standard partitions in the GPT but something like LVM's in Linux, it would copy the GPT partition that is not HFS+ (or a known file system) as raw sector by sector. It won't update anything *outside* the volume/partition area if they keep meta data outside of it.

     

    To test you would simple do the copy using the options, then remove the original (to not cause a conflict which may alter something) and put the copy in its place.

     

    Booting on (U)EFI load ins the kernel loader from the EFI System partition which is responsible for booting the OS. If their using something like LVM's as an option, and data is outside partitions, you'd have to copy the entire drive raw (by enabling the "backup/copy unused sectors" option). That will copy all sectors on the source HD from 0-n to the new drive. If their LVM structure is a bad design like Dynamic Drives in Windows, it's possible it calculates the location it expects metadata based on the hard drive size.

     

    A quick look up finds they call it "corestorage" and can be disabled. The command "diskutil cs revert" is what is used. Once reverted you can do normal things.

  • by Loner T,

    Loner T Loner T Sep 28, 2015 5:41 PM in response to trwd
    Level 7 (24,098 points)
    Safari
    Sep 28, 2015 5:41 PM in response to trwd

    trwd wrote:

     

    Thank you Loner T.  Your reply may be a little beyond my understanding but (to confirm) I believe you told me how to see the GUID's on both internal and external drive.

     

    You wrote earlier:

     

    Bootcamp is a NTFS partition/volume, while Macintosh HD is a LVG/LV combination. A LVG can contain more than LV. You should check with CloneZilla . It is unlikely that such tools understand the LVG/LV abstractions.

    A Logical Volume Group is a container for the underlying HFS+ volume.  The following indicates that it can be reverted exposing the underlying HFS+ partition/filesystem.

    Revertible:            Yes (no decryption required)

     

     

    When I emailed Terabyte (Image for Linux) Support with the news that the external copy did not boot I included the above comment from you. He replied with the following, which is equally beyond my understanding. Perhaps you will understand what he wrote, though.  All I was able to deduce is that he's suggesting I try an option that copies all sectors.  I wish you could correspond directly with him and arrive at a go/no-go conclusion as to whether Terabyte Image for Linux can make a perfect copy. I think it can but the Devil's in the Details (the settings).

     

    If you are not using standard partitions in the GPT but something like LVM's in Linux, it would copy the GPT partition that is not HFS+ (or a known file system) as raw sector by sector. It won't update anything *outside* the volume/partition area if they keep meta data outside of it.

     

    To test you would simple do the copy using the options, then remove the original (to not cause a conflict which may alter something) and put the copy in its place.

     

    Booting on (U)EFI load ins the kernel loader from the EFI System partition which is responsible for booting the OS. If their using something like LVM's as an option, and data is outside partitions, you'd have to copy the entire drive raw (by enabling the "backup/copy unused sectors" option). That will copy all sectors on the source HD from 0-n to the new drive. If their LVM structure is a bad design like Dynamic Drives in Windows, it's possible it calculates the location it expects metadata based on the hard drive size.

     

    A quick look up finds they call it "corestorage" and can be disabled. The command "diskutil cs revert" is what is used. Once reverted you can do normal things.

    At least the person on the other side is aware of what is going on. Please use the following command.

     

    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.

  • by trwd,

    trwd trwd Sep 28, 2015 6:25 PM in response to Loner T
    Level 1 (15 points)
    Audio
    Sep 28, 2015 6:25 PM in response to Loner T

    Will doing the following make a change that might be an obstacle to a future upgrade of OSX? It sounds like this will "disable corestorage", which doesn't sound good.

    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.

  • by Loner T,

    Loner T Loner T Sep 28, 2015 7:00 PM in response to trwd
    Level 7 (24,098 points)
    Safari
    Sep 28, 2015 7:00 PM in response to trwd

    No. Once you clone and test, your JHFS+ volume can be converted to CoreStorage on the cloned disk.

  • by trwd,

    trwd trwd Sep 28, 2015 8:35 PM in response to Loner T
    Level 1 (15 points)
    Audio
    Sep 28, 2015 8:35 PM in response to Loner T

    Ah!  So revert only to make the clone, then it's possible to "un-revert"? What is the Terminal command?

  • by Loner T,

    Loner T Loner T Sep 29, 2015 3:36 AM in response to trwd
    Level 7 (24,098 points)
    Safari
    Sep 29, 2015 3:36 AM in response to trwd

    Your diskutil cs list command shows the underlying physical volume to be disk0s2.

     

    diskutil cs convert disk0s2

     

    I have included the cs create command to show the initial creation of a CS LVG container from which LVs can be carved out.

    diskutil cs convert

    Usage:  diskutil coreStorage convert

            MountPoint|DiskIdentifier|DeviceNode

            [-stdinpassphrase | -passphrase [passphrase]]

    Convert a regular JHFS+ partition into a CoreStorage logical volume.

    The file system must be mounted and resizable (i.e. Journaled HFS+).

    Ownership of the affected disk is required.

     

    diskutil cs create

    Usage:  diskutil coreStorage create lvgName

            MountPoint|DiskIdentifier|DeviceNode ...

    Create a CoreStorage logical volume group from one or more disks.

    The specified disks will become the initial set of PVs.

    All existing data on the drive will be lost.

    Ownership of the affected disks is required.

    Example: diskutil coreStorage create MyLVG disk1

  • by trwd,

    trwd trwd Sep 30, 2015 7:11 AM in response to Loner T
    Level 1 (15 points)
    Audio
    Sep 30, 2015 7:11 AM in response to Loner T

    I was able to make what appears to be a perfect clone of the internal SSD to an external USB HDD. I used Terabyte Image for Linux. I'll post how separately.  Since both drives have the same GUID I cannot boot from the external USB HDD while the internal SSD is connected.

     

    @Loner T: is it possible to change the GUID(s?) on the external HDD so I can have both connected and boot either one?  If so, please tell me how to do this.

     

    Pasted below are the results of the commands you suggested for showing the GUID.

     

    First, the internal SSD:

    sudo gdisk -l /dev/disk0

    Password:

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: protective

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with protective MBR; using GPT.

    Disk /dev/disk0: 1000215216 sectors, 476.9 GiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 02445E37-1F51-4E77-91B0-00DEC704C5D7

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 1000215182

    Partitions will be aligned on 8-sector boundaries

    Total free space is 922893 sectors (450.6 MiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640       498945639   237.7 GiB   AF05  Macintosh HD

       3       498945640       500215175   619.9 MiB   AB00  Recovery HD

       4       500215808       999292927   238.0 GiB   0700  BOOTCAMP

     

    sudo gdisk /dev/disk0

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: protective

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with protective MBR; using GPT.

     

    Command (? for help): p

    Disk /dev/disk0: 1000215216 sectors, 476.9 GiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 02445E37-1F51-4E77-91B0-00DEC704C5D7

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 1000215182

    Partitions will be aligned on 8-sector boundaries

    Total free space is 922893 sectors (450.6 MiB)

     

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640       498945639   237.7 GiB   AF05  Macintosh HD

       3       498945640       500215175   619.9 MiB   AB00  Recovery HD

       4       500215808       999292927   238.0 GiB   0700  BOOTCAMP

     

     

    Command (? for help): i

    Partition number (1-4): 1

    Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System)

    Partition unique GUID: 3F03187B-0E58-402F-A712-F86E70CFA2ED

    First sector: 40 (at 20.0 KiB)

    Last sector: 409639 (at 200.0 MiB)

    Partition size: 409600 sectors (200.0 MiB)

    Attribute flags: 0000000000000000

    Partition name: 'EFI System Partition'

     

     

    Now, the external USB HDD:

    sudo gdisk -l /dev/disk2

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: protective

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with protective MBR; using GPT.

    Disk /dev/disk2: 2930277168 sectors, 1.4 TiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 02445E37-1F51-4E77-91B0-00DEC704C5D7

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 1000215182

    Partitions will be aligned on 8-sector boundaries

    Total free space is 922893 sectors (450.6 MiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640       498945639   237.7 GiB   AF05  Macintosh HD

       3       498945640       500215175   619.9 MiB   AB00  Recovery HD

       4       500215808       999292927   238.0 GiB   0700  BOOTCAMP

     

    sudo gdisk /dev/disk2

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: protective

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with protective MBR; using GPT.

     

    Command (? for help): p

    Disk /dev/disk2: 2930277168 sectors, 1.4 TiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 02445E37-1F51-4E77-91B0-00DEC704C5D7

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 1000215182

    Partitions will be aligned on 8-sector boundaries

    Total free space is 922893 sectors (450.6 MiB)

     

    Number  Start (sector)    End (sector)  Size       Code  Name

       1              40          409639   200.0 MiB   EF00  EFI System Partition

       2          409640       498945639   237.7 GiB   AF05  Macintosh HD

       3       498945640       500215175   619.9 MiB   AB00  Recovery HD

       4       500215808       999292927   238.0 GiB   0700  BOOTCAMP

     

    Command (? for help): i

    Partition number (1-4): 1

    Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System)

    Partition unique GUID: 3F03187B-0E58-402F-A712-F86E70CFA2ED

    First sector: 40 (at 20.0 KiB)

    Last sector: 409639 (at 200.0 MiB)

    Partition size: 409600 sectors (200.0 MiB)

    Attribute flags: 0000000000000000

    Partition name: 'EFI System Partition'

  • by Loner T,

    Loner T Loner T Sep 30, 2015 7:43 AM in response to trwd
    Level 7 (24,098 points)
    Safari
    Sep 30, 2015 7:43 AM in response to trwd

    You can use Gdisk to change GUIDs for the disk. Do not change Partition Type GUIDs, only the Disk GUIDs on the SSD. Leave the original source disk intact.

     

    sudo gdisk /dev/disk0

    Password:

    GPT fdisk (gdisk) version 1.0.0

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: hybrid

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with hybrid MBR; using GPT.

     

    Recovery/transformation command (? for help): x

     

    Expert command (? for help): ?

    a set attributes

    c change partition GUID

    d display the sector alignment value

    e relocate backup data structures to the end of the disk

    g change disk GUID

    h recompute CHS values in protective/hybrid MBR

    i show detailed information on a partition

    l set the sector alignment value

    m return to main menu

    n create a new protective MBR

    o print protective MBR data

    p print the partition table

    q quit without saving changes

    r recovery and transformation options (experts only)

    s resize partition table

    t transpose two partition table entries

    u replicate partition table on new device

    v verify disk

    w write table to disk and exit

    z zap (destroy) GPT data structures and exit

    ? print this menu

  • by trwd,

    trwd trwd Sep 30, 2015 8:39 AM in response to Loner T
    Level 1 (15 points)
    Audio
    Sep 30, 2015 8:39 AM in response to Loner T

    Thank you for replying so quickly, Loner T!

     

    The SSD is the original internal SSD.  The copy I made is an external HDD, which I figured out is Disk2 by using the Mount command to get that info.

     

    So you say I can change the GUID using the experts command "G".  Next, use "R" for Randomize -- is that okay?  AND, do I then use "W" to write the change to the HDD?

  • by Loner T,

    Loner T Loner T Sep 30, 2015 8:48 AM in response to trwd
    Level 7 (24,098 points)
    Safari
    Sep 30, 2015 8:48 AM in response to trwd

    trwd wrote:

     

    The SSD is the original internal SSD.  The copy I made is an external HDD, which I figured out is Disk2 by using the Mount command to get that info.

    Leave the  SSD untouched.

     

     

    So you say I can change the GUID using the experts command "G".  Next, use "R" for Randomize -- is that okay?  AND, do I then use "W" to write the change to the HDD?

    Yes to all.

  • by trwd,

    trwd trwd Sep 30, 2015 8:54 AM in response to Loner T
    Level 1 (15 points)
    Audio
    Sep 30, 2015 8:54 AM in response to Loner T

    oops, a snag:

     

    sudo gdisk /dev/disk2

    Password:

    GPT fdisk (gdisk) version 1.0.0

     

     

    Warning: Devices opened with shared lock will not have their

    partition table automatically reloaded!

    Partition table scan:

      MBR: protective

      BSD: not present

      APM: not present

      GPT: present

     

    Found valid GPT with protective MBR; using GPT.

     

    Command (? for help): x        

     

    Expert command (? for help): g

    Enter the disk's unique GUID ('R' to randomize): R

    The new disk GUID is 0DD37833-D344-41D8-82C1-E216E3630A8E

     

    Expert command (? for help): w

    Warning! Secondary header is placed too early on the disk! Do you want to

    correct this problem? (Y/N):

  • by Loner T,

    Loner T Loner T Sep 30, 2015 9:03 AM in response to trwd
    Level 7 (24,098 points)
    Safari
    Sep 30, 2015 9:03 AM in response to trwd

    Can you post the output of

     

    sudo gpt -vv -r show /dev/disk2

     

    You can 'q'(uit) out of the Gdisk Disk GUID session for the time being. Also, you can use  'b'(ackup) to backup the GPT from disk2 to a file, before we make changes.

  • by trwd,

    trwd trwd Sep 30, 2015 9:12 AM in response to Loner T
    Level 1 (15 points)
    Audio
    Sep 30, 2015 9:12 AM in response to Loner T

    thank you for the quick follow-up.

     

    sudo gpt -vv -r show /dev/disk2

     

    gpt show: /dev/disk2: mediasize=1500301910016; sectorsize=512; blocks=2930277168

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

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

    gpt show: /dev/disk2: Sec GPT at sector 2930277167

          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  1930984207      

      2930277135          32        Sec GPT table

      2930277167          1        Sec GPT header

  • by trwd,

    trwd trwd Sep 30, 2015 9:13 AM in response to trwd
    Level 1 (15 points)
    Audio
    Sep 30, 2015 9:13 AM in response to trwd

    Here's the same command for the SSD in case a comparison is worthwhile.

     

    sudo gpt -vv -r show /dev/disk0

    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

Previous Page 2 of 5 last Next