Activity for ari j.
-
ari j. posted a comment on discussion Open Discussion
It works perfectly, exactly what I was thinking of. Thank you so much :)
-
I just thought, it might actually be better to get that information on other/all drives instead: fdisk -x --bytes lsblk -JOb
-
Got it. So you want is to keep the meta data files from Clonezilla, but just only need a whole disk dd image. Correct. The entire Clonezilla image structure is fantastic, but that structure with, precisely as you stated, saving a whole disk dd image would be wonderful in my workflow. Sure. We will think about this and if it's OK, we will try to make it in the future, Thank you so much for considering it!
-
Thanks for responding Steven. I apologize that my message wasn't very clear in what I was requesting. I'll try clarifying it further with visual examples: Instead of this structure (which can be achieved using "-q1" inside expert mode): ./laptop_backup_2021-03-20-14-img/ |-> blkdev.list |-> blkid.list |-> clonezilla-img ... |-> sda1.dd-ptcl-img.zst.aa |-> sda2.dd-ptcl-img.zst.aa |-> sda3.dd-ptcl-img.zst.aa |-> sda3.dd-ptcl-img.zst.ab |-> sda3.dd-ptcl-img.zst.ac |-> sda4.dd-ptcl-img.zst.aa |-> sda-pt.parted...
-
Thanks for responding Steven. I apologize that my message wasn't very clear in what I was requesting. I'll try clarifying it further with visual examples: Instead of this structure (which can be achieved using "-q1" inside expert mode): ./laptop_backup_2021-03-20-14-img/ |-> blkdev.list |-> blkid.list |-> clonezilla-img ... |-> sda1.dd-ptcl-img.zst.aa |-> sda2.dd-ptcl-img.zst.aa |-> sda3.dd-ptcl-img.zst.aa |-> sda3.dd-ptcl-img.zst.ab |-> sda3.dd-ptcl-img.zst.ac |-> sda4.dd-ptcl-img.zst.aa |-> sda-pt.parted...
-
Thanks for responding Steven. I apologize that my message wasn't very clear in what I was requesting. I'll try clarifying it further with visual examples: Instead of this structure (which can be achieved using "-q1" inside expert mode): ./laptop_backup_2021-03-20-14-img/ |-> blkdev.list |-> blkid.list |-> clonezilla-img ... |-> sda1.dd-ptcl-img.zst.aa |-> sda2.dd-ptcl-img.zst.aa |-> sda3.dd-ptcl-img.zst.aa |-> sda3.dd-ptcl-img.zst.ab |-> sda3.dd-ptcl-img.zst.ac |-> sda4.dd-ptcl-img.zst.aa |-> sda-pt.parted...
-
Thanks for the reply Jeremy. I wasn't sure if Clonezilla saved the between-partitions data anywhere but maybe that's only the beginning bytes before the first partition. If you actually want a huge RAW file such as would be produced by dd from the entire disk, then I don't think Clonezilla can do this. This is exactly what I'm looking for, yes. I'm hoping that this functionality could be added to Clonezilla some day. It would help a lot for perfect 1:1 images with a lot of metadata.
-
Title pretty much says it all. I think storing this metadata inside a Clonezilla image would be beneficial. I do this manually when making RAW dd images and save them as fdisk.log and lsblk.json respectively (but feel free to use better names). If this could be added to Clonezilla's image saving procedure I think that would be very nice.
-
Hello, I've used Clonezilla several times in the past and it works nicely for cloning/backing up partitions, however, is there any way to have it copy an entire disk as one single image, -OR- can all (decompressed) partition images be somehow merged into one RAW file which perfectly recreates the drive data as if originally copied using dd? I know I can just use dd or cat on the block device, but I like the TUI wizard Clonezilla offers as well as the rich metadata it stores inside each image directory....
1
