Hi Steve, No, I found a manual command to fix the problem (and that does not work all the time, not sure what is the issue there, it gives random result everytime I run it). Finally for the moment, what I have is I dual boot the usb with Clonezilla and Boot-Repair-Disk (http://sourceforge.net/p/boot-repair-cd/home/Home/
), and the procedure is when Clonezilla is stuck there (that is almost all the time) reboot and boot up with the Boot-Repair-Disk and fix the bootsector. Thanks, Shayan > Hi Shayan, > So on github you have mentioned the issue has been fixed? > Or you still have problem for that? > Thanks. > > Steven. > > On 05/06/2015 08:12 AM, Shayan Eskandari wrote: > > Hi, > > > > I'm trying to make an automated restore clonezilla live, and I've been > > having some issues. > > One would be is it possible to make it completely unattended? I've > > tried "noprompt noprompt" but still it asks user to say "yes" to erase > > the data on the disk. > > but the major issue is this : > > https://github.com/stevenshiau/clonezilla/issues/5 > > > > > > while making an unattended restore, after restoring the partition, > > I encounter this error message: > > > > |Updating the boot entry 00005 by command: > > efibootmgr -c -d /dev/sda -p -L > > "HD(6,16570000BLAHBLAH)File(\EFI\ubuntu\grubx64.efi)" > -l "\EFI\ubuntu\grubx64.efi" > > > > Could not prepare boot variable: Invalid argument > > > > ************************************************************ > *********** > > Setting network boot in the 1st order of uEFI NVRAM... > > > > | > > > > and it gets stuck here....! if I do a reboot it would not > > recognize the hard drive any more so nothing boots. > > > > However on one try I CTRL+C ed there and went on the command-line > > mode, I did try the same command (with sudo, otherwise permission > > error), it gave me the same error and when I removed "-L > > "HD(6,16570000BLAHBLAH)File(\EFI\ubuntu\grubx64.efi)" -l > > "\EFI\ubuntu\grubx64.efi"" that are just the labels and names, it > > worked and the system was able to boot up from the restored image. > > > > so I narrowed down the issue, i guess it's somewhere > > here: > https://github.com/stevenshiau/clonezilla/blob/a80ae5a477c1e124ee87771d0a6f3551ff095efe/sbin/update-efi-nvram-boot-entry#L409 > > > > > > Is there any boot variables to disable what is happening here? or > > any other workarounds? > > > > > > Thanks, > > Shayan > > BitAccess.co > > > -------- S - B
------------------------------------------------------------------------------
_______________________________________________ Clonezilla-live mailing list Clonezilla-live@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/clonezilla-live
