Jump to content
|Topic||Stats||Last action by|
|How is Windows 10... even remotely close to being complete?||
|Win 10 Preview to RTM question.||
|"Like" not working?||
|Windows 10 Insider Preview||
|The Witcher 3: Wild Hunt||
Posted 27 August 2012 - 18:53
Posted 27 August 2012 - 19:54
Posted 27 August 2012 - 21:31
Mhmm. But aside from switching the drives, I did nothing different, so why would it clone in the MBR format one way, and the GUID another? Especially since the original drive was GUID its self. What reason did the clone operation have to switch to MBR?
Sounds like it was partitioned in MBR.
Posted 28 August 2012 - 09:39
Posted 28 August 2012 - 16:08
I explicitly formatted the drive as GUID multiple times, before and in between clones, so... I've no idea what's up with that then. Maybe I just did something wrong and left it in MBR after all. The computer is gone and I've no way of verifying and testing this anymore. Oh well.
Disk Utility won't touch the partition table when you clone a Partition, it'll leave it well alone and 100% of disks come with a MBR Partition Table. So unless you specifically told Disk Utility to change this, it would have continued in MBR mode.
When plugging into an Internal (SATA) port, Disk Utility forces all disks to have a GPT Map.
Posted 03 September 2012 - 18:06
I did try that, yep. The new drive did not show up in the boot menu.
I'm guessing you tried holding option at the EFI?