Winclone Restore hangs at Updating MBR

Winclone
1

I have been struggling to move a Bootcamp image from a Macbook Pro with a standard PCIe SSD to the same Macbook Pro with a standard, Apple, NVMe SSD.

I have finally made good progress, once I understood the 4k versus 512 block issues.

I made a clean Bootcamp image, with the original SSD, using Winclone 6 (I am still on El Capitan and have no desire to use High Sierra, or play games with APFS).

The last messages from Winclone, in the system log are:

Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Updating MBR On Device
Jun 22 13:35:51 macbook5 Winclone 6[814]: +++++++++++++++++++++++++++++++Updating MBR+++++++++++++++++++++++++++++++
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Starting sector is 25094144
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: updating MBR and partition info
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: /dev/disk0s4 is the in_ntfspartition
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Opening device
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Reading BIOS partition table
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: blocksize is 4096
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Reading GPT Header
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Reading GPT
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: setting signature to aa55
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Changing to standard guard MBR
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Checking MBR to see if it needs to be updated.
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: lba is different: 6 1
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: lba_size is different: 488552557 488552529
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: type is different: 07 ee
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: MBR needs to be updated
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: writing bios
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: ----------------------------- BIOS Partition Table--------------------------
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: #: id cyl hd sec - cyl hd sec [ start - size]
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: ------------------------------------------------------------------------
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]:
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: 1: 07 1023 254 63 - 1023 254 63 [ 6 - 488552557]
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]:
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: 2: 00 0 0 0 - 0 0 0 [ 0 - 0]
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]:
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: 3: 00 0 0 0 - 0 0 0 [ 0 - 0]
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]:
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: 4: 00 0 0 0 - 0 0 0 [ 0 - 0]
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: writing signature of aa55
Jun 22 13:35:51 macbook5 com.twocanoes.WincloneHelper[823]: Type of first partition in LBA 0 is not 0xEE. Writing this would cause the partition table to be unreadable. Exiting.

I was able to get the Windows bootcamp partition to boot (at least in VMware, as a Bootcamp VM, but I am pretty sure it will boot natively also).

I stopped the winclone restore process, since it had hung.

I then used Paragon Hard Disk Manager to ‘Fix the BOOTCAMP boot record’.

I believe that is what winclone was trying to do.

This is likely a bug.

2

Details of the disk being used:

$ diskutil info disk0
Device Identifier: disk0
Device Node: /dev/disk0
Whole: Yes
Part of Whole: disk0
Device / Media Name: APPLE SSD SM2048L

Volume Name: Not applicable (no file system)

Mounted: Not applicable (no file system)

File System: None

Content (IOContent): GUID_partition_scheme
OS Can Be Installed: No
Media Type: Generic
Protocol: PCI-Express
SMART Status: Not Supported

Total Size: 2.0 TB (2001111162880 Bytes) (exactly 3908420240 512-Byte-Units)
Volume Free Space: Not applicable (no file system)
Device Block Size: 4096 Bytes

Read-Only Media: No
Read-Only Volume: Not applicable (no file system)

Device Location: Internal
Removable Media: No

Solid State: Yes
OS 9 Drivers: No
Low Level Format: Not supported

3

I suspect it is has to do with the partition table of the disk. Did you format / partition the drive? What is the output of “diskutil list” and “sudo gpt show disk0”?