I don't know exactly why, but sometimes the HDD or SSD is in that state, that Clonezilla doesn't able to clone properly medium or verify the backupset (it happend to me wits HDD as well as SSD a few times during about 10 years). It can be on Linux EXT FS or Windows NTFS etc... It issues something like this:
syslinux.d syslinux_fs /dev/....
crc errors block_id = nnn...
...
For check ext2, ext3, or ext4 filesystems
Try to open Gparted (GUI), click on the wheel icon and choose repair. If it is not helped there is second way from command line is to try repair damaged blocks manually using e2fsck. For example:
ubuntu_linux:> e2fsck -f -p -v -c -c C 0 'dev/nvme0n1p2'
Switches: -f force, -p check and automtically repair all issues without prompting you for confirmation, -v verbose, -c -c inode to prevent them from being allocated to a file or directory - if this option is specified twice, then the bad block scan will be done using a non-destructive read-write test. Finally C 0 means, that you can see progress. Be patient it take a time (full NVME 500GB SSD about 2 hour+). Mostly, it helped me.
The both methods you can use repeatedly, but be avare. GParted sometimes can damage your filesystem more and unreversible as well as e2fsck
, but on the other hand, in that situation, maybe the problem was only hidden, so there is no choice how to easily repair medium.
For check NTFS, FATXX etc... filesystems
Similar situation I noticed on Windows10 too (again SSD and again in the time of backup or immediately after). There is situation slightly easier. Windows immediately offer what to do - there is notification, which leads us to the page with advice, how to repair error on medium. Of course, there is again possibility to use command line chkdsk
as explained in commentary above.
After healing bad block it can occur, that something will not work properly. If i t is not fundamental for OS it can be hidden for the time, when you will need to start the application, open the picture etc... If it is program or part of some installation, simply reinstall it. If sytem has any issues, try to reinstall library or simply that, where is problem.
I think I've figured it out - for local_dev, anyway; tomorrow I'll find out whether this applies to Samba as well. I suspect it does. (Edit: YES!)
When I backed up the Windows machines to Samba, it created a folder for each image. When I tried to restore one of those images, I specified that subfolder to be mounted as /home/partimag; apparently this was my mistake. When I copied the files onto a USB stick, I copied them to the root folder - and, as I mentioned above, it still didn't see anything to restore.
Out of some sort of inspiration/desperation, I created a subfolder on the USB stick, moved the files into it, and tried again - and lo and behold, I have now restored that image successfully! Tomorrow I'll try telling CZ to mount the root of the Samba share as /home/partimag, and I suspect I'll be given a choice of images to restore. (I'll update this answer according to my findings.)
Bottom line: CloneZilla has a blind spot in the root folder of whatever you specify as /home/partimag. You've got to tell it to look (at least? needs testing) one level above the folder containing your image files. This may be spelled out in the documentation somewhere - but I sure didn't see it, and I wish I had.
Best Answer
With Win 8 (and most likely Win 10), when you do a normal shutdown, it actually does a special "fast startup" shutdown where not everything is really released so that it can boot up faster. If you hold down SHIFT when clicking the shutdown button, it will do a proper, full shutdown. You'll most likely notice this time it takes several times longer to shutdown than it previously did.
In Win 8 (and most likely Win 10), when you click restart, it does the full shutdown.
In your case, you seem to have shutdown your system normally (resulting in 'fast startup') and hence partitions may not have been properly released. To avoid this, start your Windows 10 again, holding the SHIFT key down click on shutdown, which will perform complete shutdown, releasing all resources (including partitions). Now, you should be able to clone using Clonezilla.