Mac experts help!

[xcj]

Hi everyone,

I just upgraded my MacBook Pro Retina internal SSD of 256GB by a Samsung MSata 500GB SSD + adaptor to fit in the Macbook.

I have Mac OS X El Capitan and Windows 10 on a bootcamp partition.

I wanted a raw copy solution that would clone all the partitions to the new SSD and allowed me to resize them.

All intructions for this task i found on the internet recomended two seperate aplications , one for cloning the MAC OS X partition (Carbon Copy Cloner or SuperDuper) and another for cloning the Bootcamp partition (Winclone), both would allow you to resize the partition on the destination disk.

I tried both Carbon Copy and SuperDuper (both the latest version) and booting the new SSD cloned in either of them has a strange 10 second delay between powering on the machine and seing the boot loading progress bar.

The Winclone (version 4.4) had a problem of permissions on the end of the process that fails to write changes to the partition table, so i am still unable to clone the bootcamp partition added to the delay problem described above with the 2 applications cloning method.

I also tried CloneZilla and it could not understand the original partition table in order to start clonning.

Until i tried HDDGuro HDD Raw Copy!

I was really impressed with it, the system booted instantly just like the original SSD , both partitions working, Mac OS X and Windows 10, so i was so happy that i closed the machine (ten screws ) , thinking that all i needed to do would be going to disk utility and resize my Mac OS Partition using the new unnalocated space (leaving the bootcamp as is).

The thing is, in El Capitan the disk utility is rather different from previous Mas OS X versions, it has a graphic showing how much size each partition uses from the total of the disk BUT from a total equivalent to the original SSD SIZE!

It recognizes that the SSD is 512GB but i can only resize partitions in a way that the total can only be the original 256GB!

If i run the disk manager on the windows side, it show the unnalocated space but if i try to use it for a partition it says that the partition table will change from static to dynamic and all other OS's could stop working (meaning MAC OS X..)

Does anyone know a workaround for this? Some form of resizing partitions both Mac OS and bootcamp that has no problems with both El Capitan and Windows 10?

Thanks in advance for the help!!

[dick]

Does anyone know a workaround for this? Some form of resizing partitions both Mac OS and bootcamp that has no problems with both El Capitan and Windows 10?

Yep. Also I think the problem might be down to the location of the recovery partition?
I used Gparted which is open source and freeware. Just get the iso and boot from a usb stick or cd drive. In Gparted you should be able to move the partitions on the 500gb partition. Then using the El Capitan disk tools on the bootable installer usb memory stick you should be able to resize the partitions and make use of the unused space.
I can't remember all the exact details but Gparted was the way to go.

[SOSdonnees]

It recognizes that the SSD is 512GB but i can only resize partitions in a way that the total can only be the original 256GB!

Hi,

I cannot advise you for the bootcamp stuff, but as for resizing the partition, the issue you might encounter after cloning to a larger SSD drive is that you cannot enlarge an existing partition.

This has to see with the GUID partitioning (GPT) as the "map" was designed for the smaller SSD and is too small to fully exploit the larger size of the new drive.

Basically, you have to destroy write down (or print) the GPT partitioning scheme, destroy it and recreate it manually. Then, the Disk Utility will let you enlarge the existing partition.

Look at this method which works, but read it twice and be sure to understand what you're doing as the name of the partition will be else :
http://blog.kyodium.net/2010/11/increas ... ze-in.html
At the end of the thread, you'll find my comment from 3 September 2015 at 23:13 for further trick.

Also make sure that you have the "old" drive still working (and maybe a second clone) before you try anything with the new drive.

[xcj]

Thanks guys, sorry for the late reply.

I tried the GParted method for moving the bootcamp to the "end" of the SSD , and that solved the resize problem for the MAC OS partition, but it nuked the windows 10 partition (no longer booted).

I didn't try the other method because a simpler one worked, i had to use supersuper and winclone, both had to be the latest versions to suport both newest OS's (MAC OS El Capitan and Wndows 10).

I'll leave the steps here for whoever needs them next.

1-Connect the new SSD via USB to the MAC (for me it required an adaptor from "apple connector" to SATA and another from SATA to USB, most Mac Users will only need the SATA to USB)

2-Partition the new SSD with a MAC-OS partition and a FAT32 Partition on the final size you want each partition to have.

3-Use SuperDuper (or CabonCapyCloner) to clone you current and working MAC-OS partition to the USB SDD.

4-Use Winclone to clone the Bootcamp partition to the FAT32 (it will convert it to NTFS) but it will fail to make it bootable because of the System Integrity Protection (new MAC OS X El Capitan feature).

5-Swap the USB SDD to inside the MAC (leave the original SDD untouched until you get everything right)

6-Boot El Capitan and check if everything is OK on the MAC OS side.

7-Use Paragon Partion tools for MAC to create a new El Capitan Recovery Partition (SuperDuper does not copy the recovery partition, may not be a problem for CarbonCopyClone), since your new SDD wil not have one, you will have only the "live recovery" trough internet access that is the same from Mac OS Mavericks and you need the El Capitan Recovery.

8-Boot El Capitan Recovery Partition and run this (http://osxdaily.com/2015/10/05/disable- ... -mac-os-x/) tuturial to disable the System Integrity Protection

9-Boot El Capitan again and go to Winclone, go to your bootcamp partition and on the menu select "make legacy bootable" (you couldn't do that before step

10-Test booting Windows 10 again and check if everythin is OK on the Windows side.

Done!