costinel

there seems to be new ideas discussed over there in that lvm issue about saving not the thin LV's but the thin pool itself, by copying the hidden pool data and pool metadata, then restoring them. also, why can't dd mode work for savedisk? it's quite not what I'd expect from a cloning tool, to fail unconditionally just because it encountered a thin pool. it seems to want to do it the lvm way, even when you say you want dd.

also, why savedisk wants individual partitions? isn't savedisk's whole point to ignore partitions and just dump the entire block device?

Hi Steven, clonezilla fails even when instructed in dd mode (-q1); Still attempts and fails to parse lvm, even when explicitly lvm access to devices is restricted via lvm filters! I had to enable lvm filters because ocs-sr ignores -q1 , yet still ignores everything and goes by lvm signatures found on disk. I just gave up and done a manual dd... user@lunar:/home/partimag$ cat /var/log/clonezilla.log | nc termbin.com 9999 https://termbin.com/psv3 user@lunar:/home/partimag$ lvmconfig | nc termbin.com...

dot (.) hotkey doesn't work when displaying disk groups ("g" hotkey when started with -g auto)

OS: Ubuntu Linux 18.04LTS

[ SOLVED] How do I tell clonezilla to not modify any files in the destination during whole disk restore? I noticed that at some point it says "Re-creating initrd" which invokes dracut which re-generates the initrd, and this is something I don't expect to happen for a cloning software. Even if kernel device name had changed, on my systems grub and filesystems are looked up with labels and uuids. At worst, I should have been asked before doing that, even in Beginner mode. cloned OS: Fedora Linux EDIT:...

How do I tell clonezilla to not modify any files in the destination during whole disk restore? I noticed that at some point it says "Re-creating initrd" which invokes dracut which re-generates the initrd, and this is something I don't expect to happen for a cloning software. Even if kernel device name had changed, on my systems grub and filesystems are looked up with labels and uuids. At worst, I should have been asked before doing that, even in Beginner mode. cloned OS: Fedora Linux EDIT: found...

experienced the same behaviour on a mSATA disk on ASRock IMB-150, but with normal BIOS, not EFI issue not present in latest testing.