MacPro Late 2013 & Windows 10 - EFI problem

Winclone
21

Ananke, thanks for chiming in! I hope we can figure this out.

Tim, thanks for the link to your article; as I mentioned earlier, my antivirus app (Norton) is not active against internal activity and shows no logs against WinClone. Also, it was running at the time WinClone was not posing any problems. Even now, EFI partitions can be mounted manually and are writable.

Although I do not have immediate access to my Mac and cannot check, I carefully went through my earlier posting of WinClone logs and noted a few items I don’t understand. Please remember that, at most times I had several external drives connected with unsuccessful WinClone clones. Also remember my earlier comment that ALL clones (bootable or not) were dismounted during restoration…

My observations and questions on the earlier logs:

  • 2019-04-16 14:58:52.567007+0200 localhost com.twocanoes.WincloneHelper[646]: Executing “ntfsclone -f -O /dev/disk6s2 /dev/disk0s3”

Which is the source, and which is the destination here? If I remember correctly, /dev/disk0s3 was the source. Correct?

Nevertheless, the source is identified as:

  • 2019-04-16 15:12:29.485568+0200 localhost com.twocanoes.WincloneHelper[646]: [com.twocanoes.winclone:WincloneHelper] source device is file:///dev/disk6s2

The next log is:

  • 2019-04-16 15:12:29.603681+0200 localhost com.twocanoes.WincloneHelper[646]: Copying /Volumes/MacPro_Win 1/Windows/Boot/EFI/bg-BG to /Volumes/EFI/EFI/Microsoft/Boot/bg-BG

Here I do not understand /Volumes/MacPro_Win 1 (certainly not the original source or destination) and /Volumes/EFI/EFI/Microsoft (EFI/EFI ?)

For another attempt the previously posted logs show:

  • 2019-04-17 21:03:48.875092+0200 localhost com.twocanoes.WincloneHelper[5055]: [com.twocanoes.winclone:WincloneHelper] source device is file:///dev/disk3s2

  • 2019-04-17 21:03:48.993647+0200 localhost com.twocanoes.WincloneHelper[5055]: Copying /Volumes/MacPro_Win 1/Windows/Boot/EFI/bg-BG to /private/var/tmp/MPSHQG2K/EFI/Microsoft/Boot/bg-BG

Looks very different and, again, /Volumes/MacPro_Win 1 cannot correspond to the source.

For future debugging it would be great if the disk/partition would be mentioned in logs like:

  • 2019-04-16 18:18:36.744131+0200 localhost com.twocanoes.WincloneHelper[693]: [com.twocanoes.winclone:WincloneHelper] Error mounting EFI on disk .<.p.r.i.v.a.t.e.>. (sorry this word, without the dots, disappears when text is pasted into this forum - I’ll update this post accordingly)

Could it be that, when multiple volumes with EFI and Windows partitions are present (bootable or not), the ID pointers get mixed up? Does WinClone check whether sourcefiles exist and copies actually get written? If not, this would the empty EFI partitions I mentioned earlier…

Again, thanks for your help

22

The /Volumes/MacPro_Win 1 usually means there are 2 volumes mounted with the same name, or the mount point didn’t get removed. You can see the exact mount point for the Boot Camp drive by running “mount” in Terminal. That will show what devices are mounted where.

It might also be an issue if the EFI partition is not on the first slice. Can you post the output of the command “diskutil list” in Terminal?

tim

23

Tim

I don’t have access to the machine right now, but this is what I recovered from the log files:
2019-04-17 19:24:46.306248+0200 localhost Winclone[3287]: (DiskDevice) /dev/disk0 (internal, physical):
2019-04-17 19:24:46.306283+0200 localhost Winclone[3287]: (DiskDevice) #: TYPE NAME SIZE IDENTIFIER
2019-04-17 19:24:46.306303+0200 localhost Winclone[3287]: (DiskDevice) 0: GUID_partition_scheme *251.0 GB disk0
2019-04-17 19:24:46.306322+0200 localhost Winclone[3287]: (DiskDevice) 1: EFI EFI 209.7 MB disk0s1
2019-04-17 19:24:46.306340+0200 localhost Winclone[3287]: (DiskDevice) 2: Apple_APFS Container disk1 150.0 GB disk0s2
2019-04-17 19:24:46.306358+0200 localhost Winclone[3287]: (DiskDevice) 3: Microsoft Basic Data MacPro_Win 100.3 GB disk0s3
2019-04-17 19:24:46.306375+0200 localhost Winclone[3287]: (DiskDevice) 4: Windows Recovery 503.3 MB disk0s4
2019-04-17 19:24:46.306392+0200 localhost Winclone[3287]: (DiskDevice)
2019-04-17 19:24:46.306409+0200 localhost Winclone[3287]: (DiskDevice) /dev/disk1 (synthesized):
2019-04-17 19:24:46.306425+0200 localhost Winclone[3287]: (DiskDevice) #: TYPE NAME SIZE IDENTIFIER
2019-04-17 19:24:46.306442+0200 localhost Winclone[3287]: (DiskDevice) 0: APFS Container Scheme - +150.0 GB disk1
2019-04-17 19:24:46.306459+0200 localhost Winclone[3287]: (DiskDevice) Physical Store disk0s2
2019-04-17 19:24:46.306476+0200 localhost Winclone[3287]: (DiskDevice) 1: APFS Volume Macintosh HD 85.3 GB disk1s1
2019-04-17 19:24:46.306504+0200 localhost Winclone[3287]: (DiskDevice) 2: APFS Volume Preboot 45.2 MB disk1s2
2019-04-17 19:24:46.306521+0200 localhost Winclone[3287]: (DiskDevice) 3: APFS Volume Recovery 517.0 MB disk1s3
2019-04-17 19:24:46.306538+0200 localhost Winclone[3287]: (DiskDevice) 4: APFS Volume VM 20.5 KB disk1s4
2019-04-17 19:24:46.306558+0200 localhost Winclone[3287]: (DiskDevice)
2019-04-17 19:24:46.306575+0200 localhost Winclone[3287]: (DiskDevice) /dev/disk2 (external, physical):
2019-04-17 19:24:46.306592+0200 localhost Winclone[3287]: (DiskDevice) #: TYPE NAME SIZE IDENTIFIER
2019-04-17 19:24:46.306608+0200 localhost Winclone[3287]: (DiskDevice) 0: GUID_partition_scheme *3.0 TB disk2
2019-04-17 19:24:46.306625+0200 localhost Winclone[3287]: (DiskDevice) 1: EFI EFI 209.7 MB disk2s1
2019-04-17 19:24:46.306641+0200 localhost Winclone[3287]: (DiskDevice) 2: Apple_RAID 3.0 TB disk2s2
2019-04-17 19:24:46.306657+0200 localhost Winclone[3287]: (DiskDevice) 3: Apple_Boot Boot OS X 134.2 MB disk2s3
2019-04-17 19:24:46.306673+0200 localhost Winclone[3287]: (DiskDevice)
2019-04-17 19:24:46.306688+0200 localhost Winclone[3287]: (DiskDevice) /dev/disk3 (external, physical):
2019-04-17 19:24:46.306704+0200 localhost Winclone[3287]: (DiskDevice) #: TYPE NAME SIZE IDENTIFIER
2019-04-17 19:24:46.306720+0200 localhost Winclone[3287]: (DiskDevice) 0: GUID_partition_scheme *480.1 GB disk3
2019-04-17 19:24:46.306738+0200 localhost Winclone[3287]: (DiskDevice) 1: EFI EFI 209.7 MB disk3s1
2019-04-17 19:24:46.306754+0200 localhost Winclone[3287]: (DiskDevice) 2: Microsoft Basic Data MacPro_Win 479.9 GB disk3s2
2019-04-17 19:24:46.306770+0200 localhost Winclone[3287]: (DiskDevice)
2019-04-17 19:24:46.306786+0200 localhost Winclone[3287]: (DiskDevice) /dev/disk4 (external, physical):
2019-04-17 19:24:46.306802+0200 localhost Winclone[3287]: (DiskDevice) #: TYPE NAME SIZE IDENTIFIER
2019-04-17 19:24:46.306818+0200 localhost Winclone[3287]: (DiskDevice) 0: GUID_partition_scheme *3.0 TB disk4
2019-04-17 19:24:46.306834+0200 localhost Winclone[3287]: (DiskDevice) 1: EFI EFI 209.7 MB disk4s1
2019-04-17 19:24:46.306850+0200 localhost Winclone[3287]: (DiskDevice) 2: Apple_RAID 3.0 TB disk4s2
2019-04-17 19:24:46.306866+0200 localhost Winclone[3287]: (DiskDevice) 3: Apple_Boot Boot OS X 134.2 MB disk4s3
2019-04-17 19:24:46.306882+0200 localhost Winclone[3287]: (DiskDevice)
2019-04-17 19:24:46.306897+0200 localhost Winclone[3287]: (DiskDevice) /dev/disk5 (external, virtual):
2019-04-17 19:24:46.306913+0200 localhost Winclone[3287]: (DiskDevice) #: TYPE NAME SIZE IDENTIFIER
2019-04-17 19:24:46.306929+0200 localhost Winclone[3287]: (DiskDevice) 0: Apple_HFS 2Big +6.0 TB disk5
2019-04-17 19:24:46.306945+0200 localhost Winclone[3287]: (DiskDevice)

Indeed, I had multiple Windows partitions with the same name (produced by Winclone), but only the internal could be booted at any time. This part of the problem solved for now.
The first copy command in building a new EFI is sometimes shown as:
Copying /Volumes/MacPro_Win 1/Windows/Boot/EFI/bg-BG to /Volumes/EFI 1/EFI/Microsoft/Boot/bg-BG
and sometimes as:
Copying /Volumes/MacPro_Win 1/Windows/Boot/EFI/bg-BG to /private/var/tmp/MPSHQG2K/EFI/Microsoft/Boot/bg-BG
Is this normal? I do not have my notes here, so I cannot tell the exact circumstances.
I’ll try to run cleaner tests.

Thanks

1 Like