Hello, I've downloaded the latest alternative stable release (20160210-wily) as well as the latest alternative testing release (20160308-wily) and cloned a brand new laptop (HP ZBook 17 G2) with Windows 10 Pro on a 512GB Liteon SSD which uses Secureboot and GPT (the default BIOS settings turned on). When cloning, I asked Clonezilla to check the image for restorability and it passes. However, when I attempted to restore, it pauses for a long time on the first partition sbd1 (which is an EFI partition) and then eventually fails. See first two pictures below. I am unable to restore the image.
However, if I go back to "20140331-saucy", I'm able to restore the image (I think, I mean it boots up and works). See third image below. But, it gives plenty of errors. I can't see to find where the restore log is kept. If I enable expert mode and choose the option to save the error log with the image, there is no log in the image directory after it finishes.
Ultimately, as I've got several of these laptops, I'm looking to dress one up, image it and put it on the other ones. However, I'm not sure if it will work or not.
Am I missing something? Do I need to change something in the BIOS? I've tried disabling Secureboot, but it still fails. Any help would be appreciated!
Did you give Clonezilla live 2.4.6-3 or 20160315-* (amd64) a try? http://clonezilla.org/downloads.php
It comes with updated partclone 0.2.88 and the results might be differents.
Steven
Last edit: Steven Shiau 2016-03-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I try to boot to that image, my laptop says "Selected boot image did not authenticate". On the download page, it says that the Alternative version is required for uEFI secure boot. Given that the laptop won't boot to the usb stick now, I'd have to agree.
For the heck of it, I disabled secure boot to attempt a restore and it still gets stuck restoring the first efi partition. I get the same error "fsync error: errno = 5".
Edit: Running it with secure boot off produced some different results. The first two partitions and the 6th partition failed, but for the others, it started copying the data to.
Last edit: Brett H 2016-03-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've attached logs from the old Saucy version (dated 20140331) and logs from the new alternative_wily (dated 20160315). Surprisingly, the partclone (version 0.2.70) in Saucy seems to do the trick (although there are many errors produced on the screen that are not in the log file for some reason).
I thought you have also tried Clonezilla live >= 2.4.6-3? It comes with partclone 0.2.88 with some updates for FAT.
So could you please confirm that you have used Clonezilla live >=2.4.6-3 (i.e. partclone 0.2.88) or not? If so, same issue?
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Steven,
I tried to use 2.4.6-3, but the laptop would not boot to it unless I disabled secure boot. When I disabled secure boot, it would not restore partitions 1,2 and 6. I did not include a log for that version since it wouldn't natively work with uEFI.
The Alternative Wily version (dated 20160315), that I included logs above for, also has partclone 0.2.88, but fails completely.
Brett
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's very difficult for us to reproduce the issue here. Therefore if your FAT partition does not contain any classified data, please use old Saucy version (dated 20140331) to save it as an image and share that with us. We will try to reproduce the issue here. Once this problem is reproducible, then we will have a chance to fix it.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Steven,
I've created a new image with Saucy and also restored the image with Saucy. I'm including logs from both. In the restore there are errors on the screen that are not reported in the log at the beginning (something about not being able to determine the size). The files are what I found at the end of both operations in /var/log.
Kind Regards,
Brett
So huge? Well, if google drive works for you, then please use that to share.
Or if you can reproduce this issue in a smaller image, please share the smaller image.
Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately, the factory image size is 31.3GB (has Windows 10 installed and includes a recovery partition).
I have a Google account, but there is a (non-paid) 15GB limit. Do you have a paid Dropbox account? I do have that and can share that way. Please contact me at: moc dot asubln at llih dot tterb (Address is reversed except for the words "dot" and "at" which should be replaced with "." and "@". Please unreverse it for correct sequence) with your contact info for sharing.
Thanks,
Brett
Edit: I can increase my Google account if that's what's needed.
Last edit: Brett H 2016-04-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Brett,
We tested this last week but forgot to reply you that we can not reproduce the issue here. It just worked when we restored the image in a virtual machine. Not sure if it's linux kernel/hardware support issue.
As the issue can not reproduced here, it's very difficult for us to fix it...
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, that's unfortunate! I was really hoping you would be able to find the fix for this. We had a similar problem with some Lenovo laptops that have SSD's also that I wrote a post on last year I believe. Not sure why the older version of clonezilla works and the newer one doesn't (to restore, the imaging part works fine).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This issue we are sure it's not from Partclone, so we guess it might be from the Linux kernel or some other file system tools. Did you try different versions of Clonezilla live, especially the one in testing release? They come with newer Linux kernel (>=4.5) so the results might be different.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I've downloaded the latest alternative stable release (20160210-wily) as well as the latest alternative testing release (20160308-wily) and cloned a brand new laptop (HP ZBook 17 G2) with Windows 10 Pro on a 512GB Liteon SSD which uses Secureboot and GPT (the default BIOS settings turned on). When cloning, I asked Clonezilla to check the image for restorability and it passes. However, when I attempted to restore, it pauses for a long time on the first partition sbd1 (which is an EFI partition) and then eventually fails. See first two pictures below. I am unable to restore the image.
However, if I go back to "20140331-saucy", I'm able to restore the image (I think, I mean it boots up and works). See third image below. But, it gives plenty of errors. I can't see to find where the restore log is kept. If I enable expert mode and choose the option to save the error log with the image, there is no log in the image directory after it finishes.
Ultimately, as I've got several of these laptops, I'm looking to dress one up, image it and put it on the other ones. However, I'm not sure if it will work or not.
Am I missing something? Do I need to change something in the BIOS? I've tried disabling Secureboot, but it still fails. Any help would be appreciated!
Thanks,
Brett
Last edit: Brett H 2016-03-09
I have never seen the error message "fsync error: errorno = 5". I will ask Thomas Tsai about the partclone error message.
Steven
Thanks! We're eagerly waiting to find out the cause.
One other thing I should note is that this laptop has 32GB of RAM (CAD laptop). I don't know if the large amount of RAM is affecting this or not.
Did you give Clonezilla live 2.4.6-3 or 20160315-* (amd64) a try?
http://clonezilla.org/downloads.php
It comes with updated partclone 0.2.88 and the results might be differents.
Steven
Last edit: Steven Shiau 2016-03-20
When I try to boot to that image, my laptop says "Selected boot image did not authenticate". On the download page, it says that the Alternative version is required for uEFI secure boot. Given that the laptop won't boot to the usb stick now, I'd have to agree.
For the heck of it, I disabled secure boot to attempt a restore and it still gets stuck restoring the first efi partition. I get the same error "fsync error: errno = 5".
Edit: Running it with secure boot off produced some different results. The first two partitions and the 6th partition failed, but for the others, it started copying the data to.
Last edit: Brett H 2016-03-21
I've attached logs from the old Saucy version (dated 20140331) and logs from the new alternative_wily (dated 20160315). Surprisingly, the partclone (version 0.2.70) in Saucy seems to do the trick (although there are many errors produced on the screen that are not in the log file for some reason).
I thought you have also tried Clonezilla live >= 2.4.6-3? It comes with partclone 0.2.88 with some updates for FAT.
So could you please confirm that you have used Clonezilla live >=2.4.6-3 (i.e. partclone 0.2.88) or not? If so, same issue?
Thanks.
Steven
Hello Steven,
I tried to use 2.4.6-3, but the laptop would not boot to it unless I disabled secure boot. When I disabled secure boot, it would not restore partitions 1,2 and 6. I did not include a log for that version since it wouldn't natively work with uEFI.
The Alternative Wily version (dated 20160315), that I included logs above for, also has partclone 0.2.88, but fails completely.
Brett
It's very difficult for us to reproduce the issue here. Therefore if your FAT partition does not contain any classified data, please use old Saucy version (dated 20140331) to save it as an image and share that with us. We will try to reproduce the issue here. Once this problem is reproducible, then we will have a chance to fix it.
Thanks.
Steven
Hello Steven,
I've created a new image with Saucy and also restored the image with Saucy. I'm including logs from both. In the restore there are errors on the screen that are not reported in the log at the beginning (something about not being able to determine the size). The files are what I found at the end of both operations in /var/log.
Kind Regards,
Brett
Last edit: Brett H 2016-03-24
There is no chance for you to share the image file? It would be easier for us to debug with that.
Thanks.
Steven
How would you like me to share the image file? It's 31.3GB in size.
Thanks,
Brett
So huge? Well, if google drive works for you, then please use that to share.
Or if you can reproduce this issue in a smaller image, please share the smaller image.
Thanks.
Steven
Unfortunately, the factory image size is 31.3GB (has Windows 10 installed and includes a recovery partition).
I have a Google account, but there is a (non-paid) 15GB limit. Do you have a paid Dropbox account? I do have that and can share that way. Please contact me at: moc dot asubln at llih dot tterb (Address is reversed except for the words "dot" and "at" which should be replaced with "." and "@". Please unreverse it for correct sequence) with your contact info for sharing.
Thanks,
Brett
Edit: I can increase my Google account if that's what's needed.
Last edit: Brett H 2016-04-12
Brett,
I have sent you an email. Please check your email box.
Thanks.
Steven
Shared with you the first two partitions via your email and Google Drive.
Hi Brett,
We tested this last week but forgot to reply you that we can not reproduce the issue here. It just worked when we restored the image in a virtual machine. Not sure if it's linux kernel/hardware support issue.
As the issue can not reproduced here, it's very difficult for us to fix it...
Steven
Well, that's unfortunate! I was really hoping you would be able to find the fix for this. We had a similar problem with some Lenovo laptops that have SSD's also that I wrote a post on last year I believe. Not sure why the older version of clonezilla works and the newer one doesn't (to restore, the imaging part works fine).
This issue we are sure it's not from Partclone, so we guess it might be from the Linux kernel or some other file system tools. Did you try different versions of Clonezilla live, especially the one in testing release? They come with newer Linux kernel (>=4.5) so the results might be different.
Steven
Yes, I've tried the Xenial versions you've posted, but not the Yakkety. Xenial didn't work any better. I have not tried Yakkety yet.