I'm trying to create a new image for the new batch of 2015 Macbook Pro 512GB. Here was my process to help determine what can be done.
1. Using clonzilla 2.4.2-32 x64 i created a savdisk with both Yosemite and bootcamp windows 10. (Successful)
2. Next i get another macbook pro, same model; and do a restoredisk. (Sucessful)
3. Loading the bootcamp partition with the windows 10 works, however the Yoesmite OS does not boot and gives me the no symbol.
I am wondering if anyone has experimented with the new macbook pros and have done a successful restore.
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have never used bootcamp in my Macmini, so I do not know if it works or not.
Did it work in older model of Mac Pro?
BTW, does anyone on this forum have similar experience to share?
Thanks.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Cloned base system (Mac Pro) running Yosemite and bootcamp Win 10
Imaged a second but identical Mac Pro
Win 10 loads fine, OS X begins to load and then displays the Prohibitory Sign.
Clonezilla displays the following error when running the update efi nvram boot entry:
Due to an issue of efibootmgr on Mac machine EFI NVRAM boot entry update is skipped.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm having a slightly different issue on several different Macbook models with the same 'efibootmgr' message.
I initially installed OSX 10.11.2 - 4 on various boxes but then decided to downgrade back to Yosemite using a previous Clonezilla image. After restoring the disk, the output identifies the machine as a Mac and then prompts in yellow the message "Due to an issue of efibootmgr on Mac machine, EFI NVRAM boot entry update is skipped", followed with a "Program terminated!!" string. Upon reboot of the machine, after about 10~15 seconds of the Yosemite loader bar progressing, the no OS symbol appears and the machine goes into a hanging state.
I can't recall the exact version of Clonezilla I used to create the image initially (most likely 2.4.2-x variant) but I have tried restoring with versions between 2.1.2-20 through the latest 2.4.5-23.
Any thoughts?
Thanks Steven---
EDIT: I completed this post initially after I saw the 'skipped' message on the 2.4.5-23 screen since all the other instances seem to fail afterwards. However, I rebooted and the machine successfully booted afterwards. The previous version that did not work was 2.4.2-61.
Last edit: nyuhsuk 2016-03-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Last week (March 2016) I purchased a few new Mac Book Pro's 15.4/2.2GHZ/16GB/256GB PartNumber:MJLQ2LL/A.
I install all Mac Updates (OS X El Capitan), and then use Boot Camp Wizard and install Windows 10 Pro and all it updates.
I used TUXBOOT to download the latest Clonezilla Live USB Bootable drive. I do a full disk capture to a USB drive and then do a restore to the exact same model Mac.
The Windows Boot Camp partition boots and works great. When I try to boot the the MAC OSX partition it fails with the infamous "NO" sign.
If I run the Mac Disk utilities it says (shows) the Mac OSX Partition as unformatted.
Anyone have an easy soltuion to image New Mac Book with OS X El Capitan with boot camp and Windows 10?
Last edit: Chad C 2016-04-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Which version of Clonezilla live did you use?
Have you tried the latest testing ones, like Cloneizlla live 2.4.6-7 or 20160404-xenial amd64? http://clonezilla.org/downloads.php
They come with newer Linux kernel so it might help.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Chad,
Your Mac Book Pro is most likely using CoreStorage instead of regular partitions. I had this issue cloning a bunch of new iMacs (with OS X 10.11 and Windows 10 partitions). You'll need to disable CoreStorage, reboot, then reimage the drive. You can find directions on these sites, site1, site2 , site3.
Last edit: jworm 2016-04-15
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the same issue cloning the dual boot image from a late 2015 iMac. I was able to use Clonezilla live to make the image. However, when I restored to another iMac it gives me the no entry sign and it will not boot from the OSX partition. What can be done to solve this issue? I used 2 different versions of Clonezilla (2.4.7-8 and alternate stable xenial). I even tried the device to device over the network option to no avail.
Last edit: RPrezz 2016-07-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Steven,
The one I capture the dual boot image is a iMac 27". The one I applied the image to was iMac 21". Both late 2015 with the UEFI feature enabled. I'm about to start capturing the image from the iMac 21" but this time using Clonezilla version 2,4.6.6-amd64. Does both versions of Clonezilla have to be the same for backing and restoring the image?
Thanks,
RPrezz
Last edit: RPrezz 2016-07-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Basically nothing too much about Macs was changed in these two versions of Clonezilla live. Your issue should be on the EFI boot manager. Maybe you have to enter the EFI manager and manually add the restored OS in the booting menu. Please let us know the results if you make it.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was able to get it to work by using Clonezilla Live 2.4.6-25-i686-pae version. Now, I'm able to use the same version for both iMacs. Before doing so, I had to disable System Integrity Protection and CoreStorage option using Terminal in recovery mode on both iMacs.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey,
I'm trying to create a new image for the new batch of 2015 Macbook Pro 512GB. Here was my process to help determine what can be done.
1. Using clonzilla 2.4.2-32 x64 i created a savdisk with both Yosemite and bootcamp windows 10. (Successful)
2. Next i get another macbook pro, same model; and do a restoredisk. (Sucessful)
3. Loading the bootcamp partition with the windows 10 works, however the Yoesmite OS does not boot and gives me the no symbol.
I am wondering if anyone has experimented with the new macbook pros and have done a successful restore.
thanks
I have never used bootcamp in my Macmini, so I do not know if it works or not.
Did it work in older model of Mac Pro?
BTW, does anyone on this forum have similar experience to share?
Thanks.
Steven.
Same behavior except using clonezilla 2.4.2-3 x64
Cloned base system (Mac Pro) running Yosemite and bootcamp Win 10
Imaged a second but identical Mac Pro
Win 10 loads fine, OS X begins to load and then displays the Prohibitory Sign.
Clonezilla displays the following error when running the update efi nvram boot entry:
Due to an issue of efibootmgr on Mac machine EFI NVRAM boot entry update is skipped.
So the version >= 2.4.2-3 x86-64 works for you?
If so, please keep using that. Thanks.
Steven.
I'm having a slightly different issue on several different Macbook models with the same 'efibootmgr' message.
I initially installed OSX 10.11.2 - 4 on various boxes but then decided to downgrade back to Yosemite using a previous Clonezilla image. After restoring the disk, the output identifies the machine as a Mac and then prompts in yellow the message "Due to an issue of efibootmgr on Mac machine, EFI NVRAM boot entry update is skipped", followed with a "Program terminated!!" string. Upon reboot of the machine, after about 10~15 seconds of the Yosemite loader bar progressing, the no OS symbol appears and the machine goes into a hanging state.
I can't recall the exact version of Clonezilla I used to create the image initially (most likely 2.4.2-x variant) but I have tried restoring with versions between 2.1.2-20 through the latest 2.4.5-23.
Any thoughts?
Thanks Steven---
EDIT: I completed this post initially after I saw the 'skipped' message on the 2.4.5-23 screen since all the other instances seem to fail afterwards. However, I rebooted and the machine successfully booted afterwards. The previous version that did not work was 2.4.2-61.
Last edit: nyuhsuk 2016-03-24
@nyuhsuk,
Thanks for your report.
So is your issues gone or still it remains?
Steven
Last week (March 2016) I purchased a few new Mac Book Pro's 15.4/2.2GHZ/16GB/256GB PartNumber:MJLQ2LL/A.
I install all Mac Updates (OS X El Capitan), and then use Boot Camp Wizard and install Windows 10 Pro and all it updates.
I used TUXBOOT to download the latest Clonezilla Live USB Bootable drive. I do a full disk capture to a USB drive and then do a restore to the exact same model Mac.
The Windows Boot Camp partition boots and works great. When I try to boot the the MAC OSX partition it fails with the infamous "NO" sign.
If I run the Mac Disk utilities it says (shows) the Mac OSX Partition as unformatted.
Anyone have an easy soltuion to image New Mac Book with OS X El Capitan with boot camp and Windows 10?
Last edit: Chad C 2016-04-05
Which version of Clonezilla live did you use?
Have you tried the latest testing ones, like Cloneizlla live 2.4.6-7 or 20160404-xenial amd64?
http://clonezilla.org/downloads.php
They come with newer Linux kernel so it might help.
Steven
Chad,
Your Mac Book Pro is most likely using CoreStorage instead of regular partitions. I had this issue cloning a bunch of new iMacs (with OS X 10.11 and Windows 10 partitions). You'll need to disable CoreStorage, reboot, then reimage the drive. You can find directions on these sites, site1, site2 , site3.
Last edit: jworm 2016-04-15
I have the same issue cloning the dual boot image from a late 2015 iMac. I was able to use Clonezilla live to make the image. However, when I restored to another iMac it gives me the no entry sign and it will not boot from the OSX partition. What can be done to solve this issue? I used 2 different versions of Clonezilla (2.4.7-8 and alternate stable xenial). I even tried the device to device over the network option to no avail.
Last edit: RPrezz 2016-07-08
Are these two iMac same model?
Steven
Steven,
The one I capture the dual boot image is a iMac 27". The one I applied the image to was iMac 21". Both late 2015 with the UEFI feature enabled. I'm about to start capturing the image from the iMac 21" but this time using Clonezilla version 2,4.6.6-amd64. Does both versions of Clonezilla have to be the same for backing and restoring the image?
Thanks,
RPrezz
Last edit: RPrezz 2016-07-12
Basically nothing too much about Macs was changed in these two versions of Clonezilla live. Your issue should be on the EFI boot manager. Maybe you have to enter the EFI manager and manually add the restored OS in the booting menu. Please let us know the results if you make it.
Thanks.
Steven
I was able to get it to work by using Clonezilla Live 2.4.6-25-i686-pae version. Now, I'm able to use the same version for both iMacs. Before doing so, I had to disable System Integrity Protection and CoreStorage option using Terminal in recovery mode on both iMacs.
Thanks.
Cool! Thanks for sharing that.
Steven