I've been using clonezilla for a long time now to save fresh images for a test lab. Recently the new mac's have been having issues consistently restoring an image.
I believe the issue is related to restoring the partition map and EFI boot options, but i'm struggling to find a way to either confirm this and hense try and fix it. Seems to happen more consistenly when going from an image that has a bootcamp partition to one that doesn't or vice versa.
That being said i've also completely removed everything using the /dev/zero and sgdisk -Z and that didn't help
While everything is restoring it looks like it worked, but obviously trying to boot doesn't, sometimes with the bootcamp images it will boot into windows, but not mac.
Does any of this sound familiar? I've searched the forums, but nothing is helping at this moment.
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?
Did you try the latest testing Clonezilla live, like 2.5.5-21?
BTW, please post the error messages when restoring if there are. You can take a photo about the whole screen then post it.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thats what i'm currently running now, but i've been having this problem for a while now and no new versions seem to be helping.
finally found the clonezilla.log and i'm seeing this
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Restoring the MBR data (512 bytes), i.e. executable code area + table of primary partitions + MBR signature, for nvme0n1... done.
Making kernel re-read the partition table of /dev/nvme0n1... Informing the OS of partition table changes.... done!
done.
The partition table of /dev/nvme0n1 is: ********.
Running: update-efi-nvram-boot-entry -r /home/partimag/MBP-System8-10.12/efi-nvram.dat -f /tmp/efi_info.GoxUEb /dev/nvme0n1
Updating boot entry of EFI NVRAM...
EFI system partition: /dev/nvme0n1p1
[1;33mNo partition boot entry from hard drive exists in EFI NVRAM.
[0;39mEFI boot entries on this system:*******.
BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0080
Boot0080 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,4c755f18-41b8-41cc-91ce-c14f10d5062e,0x6,0x12c00)
Boot0081 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(4,GPT,19944a22-f80e-4c5e-953e-2323e13c2a8e,0x2f1c300,0x1dcc00)
Boot0082 PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x30d241c,0x26be4)
BootFFFF PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x3a4a087,0x26be4)/File(\System\Library\CoreServices\boot.efi) **********.
[1;31mEFI boot file in partition /dev/nvme0n1p1 was NOT found.
[0;39mProgram terminated!!
End of restoreparts job for image MBP-System8-10.12.
End of restoredisk job for image MBP-System8-10.12.
Checking if udevd rules have to be restored...
couple of entries that are having trouble restoring the EFI
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can enter screen command then manually run this command in Clonezilla live environment:
sudo bash -x update-efi-nvram-boot-entry -r /home/partimag/MBP-System8-10.12/efi-nvram.dat -f /tmp/myefi.info /dev/nvme0n1
Then scroll back to see the output. Find why not EFI boot file is not found. Or maybe we have to update the variable known_efi_boot_file_chklist in /usr/sbin/update-efi-nvram-boot-entry.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Updating boot entry of EFI NVRAM...
EFI system partition: /dev/nvme0n1p1
[1;33mNo partition boot entry from hard drive exists in EFI NVRAM.
[0;39mEFI boot entries on this system: *******.
BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0080
Boot0080 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,4c755f18-41b8-41cc-91ce-c14f10d5062e,0x6,0x12c00)
Boot0081 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(4,GPT,19944a22-f80e-4c5e-953e-2323e13c2a8e,0x2f1c300,0x1dcc00)
Boot0082 PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x30d241c,0x26be4)
BootFFFF* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x3a4a087,0x26be4)/File(\System\Library\CoreServices\boot.efi)********.
[1;31mEFI boot file in partition /dev/nvme0n1p1 was NOT found.
[0;39mProgram terminated!!
If I cat update-efi-nvram-boot-entry looking for known_efi_boot_file_chklist there isn't any boot.efi in the list of variables
If i search for boot.efi, there are two entries in lines that are commented out in the check_if_nvram_efi_boot_partition_exist() function.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In /usr/sbin/update-efi-nvram-boot-entry, the variable is defined as:
known_efi_boot_file_chklist="/EFI/centos/grubx64.efi /EFI/debian/grubx64.efi \
/EFI/ubuntu/grubx64.efi /EFI/fedora/shim.efi /EFI/fedora/grubx64.efi \
/EFI/redhat/grub.efi /EFI/opensuse/grubx64.efi \
/EFI/Microsoft/Boot/bootmgfw.efi /EFI/Boot/bootx64.efi"
This is about the OS EFI boot loader.
Normally for Mac you do not have to update EFI boot entry. That's why the one from MacOS is not listed.
"the new mac's have been having issues consistently restoring an image." -> What were the error messages on the screen? Could you please take photos then post them?
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there are no errors on the screen besides the one above when it attempts to do the efi update, hense the need for help here :)
I found the whole log, i believe, and have attached it, let me know if there is a different log to get more information from.
once it restores it reboots and fails to boot with the mac "no" symbol.
A normal EFI partition in MacOS contains:
root@bionic:/mnt# tree
.
└── EFI
└── APPLE
├── EXTENSIONS
│ └── Firmware.scap
└── FIRMWARE
└── MM71_0220_B06_LOCKED.scap
From what I understand, these two files are firmware files, not like those efi boot files for MS Windows for GNU/Linux...
Therefore it makes sense that when update-efi-nvram-boot-entry was run, it exited with the messages:
EFI boot file in partition /dev/nvme0n1p1 was NOT found.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been using clonezilla for a long time now to save fresh images for a test lab. Recently the new mac's have been having issues consistently restoring an image.
I believe the issue is related to restoring the partition map and EFI boot options, but i'm struggling to find a way to either confirm this and hense try and fix it. Seems to happen more consistenly when going from an image that has a bootcamp partition to one that doesn't or vice versa.
That being said i've also completely removed everything using the /dev/zero and sgdisk -Z and that didn't help
While everything is restoring it looks like it worked, but obviously trying to boot doesn't, sometimes with the bootcamp images it will boot into windows, but not mac.
Does any of this sound familiar? I've searched the forums, but nothing is helping at this moment.
Which version of Clonezilla live did you use?
Did you try the latest testing Clonezilla live, like 2.5.5-21?
BTW, please post the error messages when restoring if there are. You can take a photo about the whole screen then post it.
Thanks.
Steven
thats what i'm currently running now, but i've been having this problem for a while now and no new versions seem to be helping.
finally found the clonezilla.log and i'm seeing this
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
Restoring the MBR data (512 bytes), i.e. executable code area + table of primary partitions + MBR signature, for nvme0n1... done.
Making kernel re-read the partition table of /dev/nvme0n1... Informing the OS of partition table changes.... done!
done.
The partition table of /dev/nvme0n1 is:
********.
Running: update-efi-nvram-boot-entry -r /home/partimag/MBP-System8-10.12/efi-nvram.dat -f /tmp/efi_info.GoxUEb /dev/nvme0n1
Updating boot entry of EFI NVRAM...
EFI system partition: /dev/nvme0n1p1
[1;33mNo partition boot entry from hard drive exists in EFI NVRAM.
[0;39mEFI boot entries on this system:*******.
BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0080
Boot0080 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,4c755f18-41b8-41cc-91ce-c14f10d5062e,0x6,0x12c00)
Boot0081 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(4,GPT,19944a22-f80e-4c5e-953e-2323e13c2a8e,0x2f1c300,0x1dcc00)
Boot0082 PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x30d241c,0x26be4)
BootFFFF PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x3a4a087,0x26be4)/File(\System\Library\CoreServices\boot.efi)
**********.
[1;31mEFI boot file in partition /dev/nvme0n1p1 was NOT found.
[0;39mProgram terminated!!
End of restoreparts job for image MBP-System8-10.12.
End of restoredisk job for image MBP-System8-10.12.
Checking if udevd rules have to be restored...
couple of entries that are having trouble restoring the EFI
You can enter screen command then manually run this command in Clonezilla live environment:
sudo bash -x update-efi-nvram-boot-entry -r /home/partimag/MBP-System8-10.12/efi-nvram.dat -f /tmp/myefi.info /dev/nvme0n1
Then scroll back to see the output. Find why not EFI boot file is not found. Or maybe we have to update the variable known_efi_boot_file_chklist in /usr/sbin/update-efi-nvram-boot-entry.
Steven
oh ok, i think i see it.
the output from the command says:
Updating boot entry of EFI NVRAM...
EFI system partition: /dev/nvme0n1p1
[1;33mNo partition boot entry from hard drive exists in EFI NVRAM.
[0;39mEFI boot entries on this system:
*******.
BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0080
Boot0080 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(1,GPT,4c755f18-41b8-41cc-91ce-c14f10d5062e,0x6,0x12c00)
Boot0081 Mac OS X PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(4,GPT,19944a22-f80e-4c5e-953e-2323e13c2a8e,0x2f1c300,0x1dcc00)
Boot0082 PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x30d241c,0x26be4)
BootFFFF* PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)//HD(3,GPT,1ba81898-e009-49a7-8da9-508dd5492562,0x3a4a087,0x26be4)/File(\System\Library\CoreServices\boot.efi)********.
[1;31mEFI boot file in partition /dev/nvme0n1p1 was NOT found.
[0;39mProgram terminated!!
If I cat update-efi-nvram-boot-entry looking for known_efi_boot_file_chklist there isn't any boot.efi in the list of variables
If i search for boot.efi, there are two entries in lines that are commented out in the check_if_nvram_efi_boot_partition_exist() function.
In /usr/sbin/update-efi-nvram-boot-entry, the variable is defined as:
known_efi_boot_file_chklist="/EFI/centos/grubx64.efi /EFI/debian/grubx64.efi \ /EFI/ubuntu/grubx64.efi /EFI/fedora/shim.efi /EFI/fedora/grubx64.efi \ /EFI/redhat/grub.efi /EFI/opensuse/grubx64.efi \ /EFI/Microsoft/Boot/bootmgfw.efi /EFI/Boot/bootx64.efi"
This is about the OS EFI boot loader.
Normally for Mac you do not have to update EFI boot entry. That's why the one from MacOS is not listed.
"the new mac's have been having issues consistently restoring an image." -> What were the error messages on the screen? Could you please take photos then post them?
Steven
there are no errors on the screen besides the one above when it attempts to do the efi update, hense the need for help here :)
I found the whole log, i believe, and have attached it, let me know if there is a different log to get more information from.
once it restores it reboots and fails to boot with the mac "no" symbol.
A normal EFI partition in MacOS contains:
root@bionic:/mnt# tree
.
└── EFI
└── APPLE
├── EXTENSIONS
│ └── Firmware.scap
└── FIRMWARE
└── MM71_0220_B06_LOCKED.scap
From what I understand, these two files are firmware files, not like those efi boot files for MS Windows for GNU/Linux...
Therefore it makes sense that when update-efi-nvram-boot-entry was run, it exited with the messages:
EFI boot file in partition /dev/nvme0n1p1 was NOT found.
Steven
i've done fresh installs and grabbed new images and restoring has the same effect, so it must have to do with the savedisk method?
Not really.
So you still have an issue to boot after restoring?
Steen