From: nospam@needed.invalid   
      
   On Mon, 2/16/2026 11:14 PM, Gordon wrote:   
   > On 2026-02-15, Lawrence D’Oliveiro  wrote:   
   >> On Sun, 15 Feb 2026 12:15:23 +1100, Axel wrote:   
   >>   
   >>> I could be wrong, but I think if you use Rescuezilla/Clonezilla you   
   >>> can extract files from the backup image   
   >>   
   >> It is really easier to use a backup program/regime where the backups   
   >> are just simple filesystems in their own right.   
   >   
   > Very true. Clonezilla is for cloning, not backing up. Fudging functions is   
   > not best practice when there is many other backup programmes to choose from.   
   >   
   > The real point is to get a set of programmes which suit the user and are   
   > trusted by the user.   
   >   
      
   That's a backup done with Clonezilla (Device==>Image). The source is   
   an LM222 in a VM that happened to install into a single partition (/swapfile).   
   The   
   Clonezilla run was from Live Media so that the OS disk backup target,   
   would be at rest.   
      
   mint@mint:/media/mint/BACKUP/2026-02-17-09-img$ ls -al   
   total 4655460   
   drwxrwxr-x 2 mint mint       4096 Feb 17 09:28 .   
   drwxr-xr-x 6 root root       4096 Feb 17 09:28 ..   
   -rw-r--r-- 1 root root       1299 Feb 17 09:28 Info-OS-prober.txt   
   -rw-r--r-- 1 root root       1891 Feb 17 09:28 Info-dmi.txt   
   -rw-r--r-- 1 root root        236 Feb 17 09:28 Info-img-id.txt   
   -rw-r--r-- 1 root root         58 Feb 17 09:28 Info-img-size.txt   
   -rw-r--r-- 1 root root      15239 Feb 17 09:28 Info-lshw.txt   
   -rw-r--r-- 1 root root       1311 Feb 17 09:28 Info-lspci.txt   
   -rw-r--r-- 1 root root        171 Feb 17 09:28 Info-packages.txt   
   -rw-r--r-- 1 root root         94 Feb 17 09:28 Info-saved-by-cmd.txt   
   -rw-r--r-- 1 root root        588 Feb 17 09:28 blkdev.list   
   -rw-r--r-- 1 root root        448 Feb 17 09:28 blkid.list   
   -rw-r--r-- 1 root root       4446 Feb 17 09:28 clonezilla-img   
   -rw-r--r-- 1 root root        156 Feb 17 09:25 dev-fs.list   
   -rw-r--r-- 1 root root          4 Feb 17 09:28 disk   
   -rw-r--r-- 1 root root          5 Feb 17 09:28 parts   
   -rw-r--r-- 1 root root         36 Feb 17 09:28 sda-chs.sf   
   -rw-r--r-- 1 root root      17408 Feb 17 09:28 sda-gpt-1st   
   -rw-r--r-- 1 root root      16384 Feb 17 09:28 sda-gpt-2nd   
   -rw-r--r-- 1 root root      17920 Feb 17 09:28 sda-gpt.gdisk   
   -rw-r--r-- 1 root root        552 Feb 17 09:28 sda-gpt.sgdisk   
   -rw-r--r-- 1 root root        512 Feb 17 09:28 sda-mbr   
   -rw-r--r-- 1 root root        244 Feb 17 09:28 sda-pt.parted   
   -rw-r--r-- 1 root root        226 Feb 17 09:28 sda-pt.parted.compact   
   -rw-r--r-- 1 root root        277 Feb 17 09:28 sda-pt.sf   
   -rwxrwxr-x 1 mint mint 4767020293 Feb 17 09:28 sda1.ext4-ptcl-img.gz     
   chowned/chmodded, to copy this   
                                                                          for   
   forensics...   
   mint@mint:/media/mint/BACKUP/2026-02-17-09-img$   
      
   One annoyance, is I didn't really want the partclone-img compressed.   
   But all it offers is compression options (these can slow down   
   your backup).   
      
   The source disk and partition were approximately 64GB, the content   
   about 13GB and the compressed result is as shown (about 4.7GB).   
      
   And that is suitable for disaster recovery (a "bad disk").   
      
       Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)