Hello,
My first post on this list, forgive me if I write about things you
already know :-(.
I was just hit two days ago by a bug. Probably a bug related to btrfs on
openSUSE Tumbleweed. The result was empty files on the target making in
unusable.
Details: I wanted to clone a presently in use sata 480Go ssd in an asus
N550jk computer (intel i7) to an nvme 512Go disk aimed to an asus tuf
706iu (amd rysen) computer. Many partitions on it. nvme in an usb3 nvme
dock.
Clonezilla-live-3.0.2-21-amd64.iso on a Ventoy usb pen.
no error message at the end of the clone, done mostly with default
options. None of the two openSUSE install on the disk could boot, when
Windows 10 boot correctly.
At first I suspected an UID/fstab problem, but in the end I could see a
lot of system files have quotation marks in ls -l result.
Once a fresh Tumbleweed install done on the (obsolete) openSUSE Leap
15.3 partition, I noticed that these system files on the root of faulty
Tumbleweed where zero length files.
I suspect the problem come from btrfs snapshot/subvols management, the
link between updated and non updated files is broken.
Old ssd partition and faulty Tumbleweed partition are still available
for check is necessary (some files where changed in the way of trying to
boot the system)
sincerely
jdd
--
mon serveur usenet: dodin.fr.nf
c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet
_______________________________________________
Clonezilla-live mailing list
Clonezilla-live@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clonezilla-live
