#77 Restore fails on iMac Late 2015

[Manu]

I installed a tripple boot with Windows 8.1 Pro, OSX 10.11.4, clonezilla live(-hd) on a iMac 21,5" Late 2015.
My Installation is a bit special:

1. Installed Windows in (U)EFI Mode and created 6 partitions:
   • win-recovery
   • efi-partition
   • windows
   • restore-partion (clonezilla-live)
   • installer-partition (a fat32 part which contains installer-files for mac and windows)
   • OSX partition
2. Installed OSX 10.11.4 via OSX Bootstick
3. Disabled SIP (system integrety protection)
4. Installed refind 0.10.1

So gdisk tells me I got a plain gpt partition table with a protective mbr.
I took the disk-image to restore the same computer (another iMac with the exact same configuration) and restored it.

During the restore, gdisk tells me I got a gpt with protective mbr and the 6 partitons -> everything looks fine.
When ocs-restore finished I got a gpt with -hybrid- mbr..

Result:

• So OSX is booting fine
• The internal clonezilla live is booting
• Windows ends up with a bootfailue (0xc000000e) which tells me to use recovery tools on install stick to recover the boot error
• But the install stick also ends with cannot resolve issue

What I already tried:

• Googled about boot error code 0xc000000e, which tells me to do rebuild bcd or to a fixmbr (but I am booting on gpt with efi not bcd)
• Using -t options to -not- recover mbr
• disabling -j1 and -j2
• recreating the partition-tabel by hand, and then do a part-restore

Is there any option I am missing or is it not possible to recover such kind of partition table?

[Steven Shiau]

Did you try Clonezilla live 2.4.6-8 or 20160412-*?
http://clonezilla.org/downloads.php
There are some improvements. Maybe it works for you.
//NOTE// Backup important data before you use Clonezilla. Just in case.

Steven

[Manu]

Yes 2.4.6-8 worked, thank you!
Is there a relase plan for the new version?

I have a rather big installation with about 300 computers here and am a bit afraid rolling out the testing version.

Manu

[Steven Shiau]

If it works for you, just use it. The reason it's still testing release is, we need to get more feedbacks and bug reports. Since it works there, I do not see any reason why you can not use that to deploy your 300 computers.

Steven