The WD LIVE TV HUB is outfitted with a 1TB mechanical HD and the goal is to upgrade it to a 2TB SSD, because the device HD is 12 years old and will fail sooner than later. > The primary processor on the Hub is a Sigma SMP8654AD-CBE3, which is > the same as used on the WD Live Plus. Ethernet is provided by a > Realtek RTL8110SC and there’s 256 MB of RAM. As far as software, just > like the previous models, the WD TV Live Hub runs Linux internally. I have an Ubuntu desktop to format / move data to the SSD. 1) Can Clonezilla be used format / move data to the SSD? 2) OR do I have to format the SSD with gParted and rsync the data to the SSD? Looking for a simple and systematic procedure, preferably from someone has done this before. If both are options, a review of the pros / cons is appreciated.

**My objective:** create imaging resource on bootable USB drive (256 GB) which will contain finalized laptop configuration. This is to say, I want to boot from the flash drive and use the same flash drive to store the image created by clonezilla and as needed, to restore the image at a later date. **My understanding** Limited. I've used bootable optical media for both clonezilla and gparted, as well as bootable Linux Live CD media, but I'm not a qualified *nix operator. My capabilities are akin to a code kitty(?) / kiddie in that I copy others' work in order to accomplish my occasional *nix objectives, often using Ubuntu. **What I've searched and found** A number of sites providing tutorials/guidance to create dual (or multi-) boot USB drives using Windows utilities (my choice at this stage). I've also found the source .ISO files for both clonezilla and gparted. I've found this answer , which appeared when I created the subject line but it doesn't appear to solve the objective. **Restrictions** One of the laptops does not have an optical drive. I'd prefer to have both machines to use a bootable flash drive for ease of storage. I'm aiming for a minimum *nix install on the flash drive, to allow greater storage for the created image file. The image file will be of the entire drive, all partitions, as the laptops contain multiple partitions which support manufacturer's nuances (Dell Alienware). I'd like to avoid having to boot from one flash drive and store the image file to a second flash drive, simply to avoid the creation of three drives (one boot, two image), but as a last resort, that's acceptable. It is also the route that I can travel without additional support from SE, but the challenge of learning something new vanishes. **Miscellaneous thoughts** If such a solution involves a bootable drive that contains both clonezilla and gparted, I'd find that acceptable, especially as it would provide greater capacity remaining for the image file. My current approach of creating a multi-boot flash drive would eat up twice as much as I'd expect would be necessary. I'm not averse to creating a Live boot drive that can be stripped down to a minimum of the two utilities with no GUI if a tutorial could be found to facilitate such a creation. **What I don't know** When creating the configurations suggested above, will the process use a minimum partition size on the drive, allowing the remaining space for image storage? Adjunct to that, will I have to manually create the unused space for that purpose? Finally, is this a practical approach? **Adjusted objective** Let's say that I can do without the gparted aspect of this project. This means that I can use the canned utilities for Windows to create a bootable USB for clonezilla. I'm comfortable using that program. Now the focus is how to ensure that I can use the minimum flash drive space for this bootable portion and to have the maximum space for the image file. What options do I have now?

I've built a Debian rootfs for an embedded Linux platform using debootstrap et al. My goal is to make this installable to my devices over the network. I previously built [my own solution](https://github.com/rgov/netinstall) using iPXE but I'm evaluating switching to Clonezilla. However, I am not cloning an existing drive; I want to make the restorable image from my rootfs directory, and populate the necessary metadata fields about the partitions for Clonezilla to recreate on restore. What is the process for "manually" creating a Clonezilla restore image? E.g., should I create a disk image with mkfs && mount -o loop and then clone it? Is there some incantation of partclone that supports this? (A process that doesn't require root and/or that works inside a Docker container would be preferred, since that's easier to deploy via CI.)

My system is seated on 2 Disks: /dev/nvme0n1p2 239152936 88597432 138334364 40% / /dev/nvme0n1p1 101158 4914 96244 5% /boot/efi /dev/sda2 927306756 520268880 359859552 60% /home Can i proceed like shown in https://unix.stackexchange.com/questions/598470/clonezilla-restoring-to-a-different-partition to get my clonezilla mage save on the other Computer, which has only one (suitable partitoned) Harddisk or do i have to perform some more steps before or after these steps? Regards Rainer

What library does Clonezilla use to show menus, dialogs, etc in its text user interface? I would like to use it directly as a fail-safe option for GUI apps when no GUI subsystem is available. I presume it is a C library. Does it have python bindings? I think it would be built on curses, but is there any additional layer on top of that, or is it bare-bones curses? I'd like to be able to create UIs like this:

I have a 1 TB NVMe disk with Ubuntu 22 installed with vanilla options, except I used LVM, and enabled LUKS. I'd like to image the disk for easy restores. Simply backing up the files is not enough for me, because I also want to revert partition/LVM information when restoring. However, I don't want to end up with a 1 TB image file that is 95% empty space. How do I get Clonezilla to do this? I can unlock/mount the encrypted volumes, and image them, but that doesn't maintain the underlying partition structure. If I image the underlying partitions, it images the LUKS partitions like they're just a 900ish GB slab of binary. What's a workaround here?

I tried to use Clonezilla to copy a 4TB SSD (/dev/sdd), with 3 partitions, to a 2TB 3.5" SATA3 drive (/dev/sdc). The original drive had a lot of empty space, so I had Clonezilla resize the partitions such that they fit. The e2fsprogs package was installed. Incidentally, I do not actually want to copy all 3 partitions, I just want a bootable system using the first 2 partitions. I thought I would copy the entire thing, then delete the third partition and resize the second. Suggestions on how to do this more efficiently would be welcome. I am not comfortable using disk destroyer (dd). These messages were emitted before the clone actually started:

PS. Next time you can run this command directly:
/usr/sbin/ocs-onthefly -g auto -e1 auto -e2 -r -j2 -sfsck -k1 -icds -p choose  -f sdd -d sdc
This command is also saved as this file name for later use if necessary: /tmp/ocs-onthefly-2024-08-30-09-21
*****************************************************.
Press "Enter" to continue... 
*****************************************************.
opt_for_ocs_sr_restore_this_run: -g auto -e1 auto -e2 -r -j2 -sfsck -k1 -icds
///WARNING/// filesystem.squashfs not found! No idea where is LIVE MEDIA!!! Assume this is running in DRBL client.
*****************************************************.
*****************************************************.
Searching for data partition(s)...
Finding all disks and partitions..
Excluding busy partition.....................
Excluding linux raid member partition.....
Unmounted partitions (including extended or swap): sdc1 sdc2
Collecting info... done!
Getting /dev/sdc1 info...
Getting /dev/sdc2 info...
WARNING!!! WARNING!!! WARNING!!!
WARNING! THE EXISTING DATA IN THIS HARDDISK/PARTITION(S) WILL BE OVERWRITTEN! ALL EXISTING DATA WILL BE LOST: sdc
*****************************************************.
Machine: VirtualBox
sdc (2000GB_Voyager_S3__pci-0000_00_0c_0-usb-0_1_1_0-scsi-0_0_0_0_ZK3085P9)
sdc1 (512M_vfat(In_Voyager_S3_)_pci-0000_00_0c_0-usb-0_1_1_0-scsi-0_0_0_0_ZK3085P9)
sdc2 (931.1G_ext4(In_Voyager_S3_)_pci-0000_00_0c_0-usb-0_1_1_0-scsi-0_0_0_0_ZK3085P9)
*****************************************************.
Are you sure you want to continue? (y/n) y
OK, let's do it!!
*****************************************************.
Let me ask you again.
WARNING!!! WARNING!!! WARNING!!!
WARNING! THE EXISTING DATA IN THIS HARDDISK/PARTITION(S) WILL BE OVERWRITTEN! ALL EXISTING DATA WILL BE LOST: sdc
*****************************************************.
Machine: VirtualBox
sdc (2000GB_Voyager_S3__pci-0000_00_0c_0-usb-0_1_1_0-scsi-0_0_0_0_ZK3085P9)
sdc1 (512M_vfat(In_Voyager_S3_)_pci-0000_00_0c_0-usb-0_1_1_0-scsi-0_0_0_0_ZK3085P9)
sdc2 (931.1G_ext4(In_Voyager_S3_)_pci-0000_00_0c_0-usb-0_1_1_0-scsi-0_0_0_0_ZK3085P9)
*****************************************************.
Are you sure you want to continue? (y/n) y
OK, let's do it!!
Saving the source device as a pseudo image. Running:
LC_ALL=C ocs-sr --ocsroot /tmp/ocs_onthefly_src.9hdcnm -luks no -sfsck -sfs -nogui -q2 --batch -j2 -scs -senc -p true  savedisk d2d-pseudo sdd
Setting the TERM as linux
Starting /usr/sbin/ocs-sr at 2024-08-30 09:21:59 EDT...
Start preparing device name cache files in /tmp/ocs-cache//...
The file /proc/partitions remains the same. Skip generating disk(s) list file.
The file /proc/partitions remains the same. Skip generating partitions(s) list file.
Both /proc/partitions and blkid output do not change. Skip generating file system cache file related to the dev(s).
*****************************************************.
Clonezilla image dir: /tmp/ocs_onthefly_src.9hdcnm
*****************************************************.
The image name is: d2d-pseudo
Selected device [sdd] found!
The selected devices: sdd
*****************************************************.
Activating the partition info in /proc... done!
Selected device [sdd] found!
The selected devices: sdd
Searching for data/swap/extended partition(s)...
Finding all disks and partitions..
Excluding busy partition.....................
Excluding linux raid member partition......
Unmounted partitions (including extended or swap): sdd1 sdd2 sdd3
Collecting info.... done!
The data partition to be saved: sdd1 sdd2 sdd3
Activating the partition info in /proc... done!
Selected device [sdd1] found!
Selected device [sdd2] found!
Selected device [sdd3] found!
The selected devices: sdd1 sdd2 sdd3
Getting /dev/sdd1 info...
Getting /dev/sdd2 info...
Getting /dev/sdd3 info...
*****************************************************.
/usr/share/drbl/sbin/ocs-functions: line 9334: cryptsetup: command not found
/usr/share/drbl/sbin/ocs-functions: line 9334: cryptsetup: command not found
/usr/share/drbl/sbin/ocs-functions: line 9334: cryptsetup: command not found
*****************************************************.
*****************************************************.
*****************************************************.
*****************************************************.
*****************************************************.
*****************************************************.
Saving block devices info in /tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/blkdev.list...
Saving block devices attributes in /tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/blkid.list...
Checking the integrity of partition table in the disk /dev/sdd... 
Reading the partition table for /dev/sdd...RETVAL=0
*****************************************************.
Saving the primary GPT of sdd as /tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/sdd-gpt-1st by dd...
34+0 records in
34+0 records out
17408 bytes (17 kB, 17 KiB) copied, 0.0403371 s, 432 kB/s
*****************************************************.
Saving the secondary GPT of sdd as /tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/sdd-gpt-2nd by dd...
32+0 records in
32+0 records out
16384 bytes (16 kB, 16 KiB) copied, 0.0179181 s, 914 kB/s
*****************************************************.
Saving the GPT of sdd as /tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/sdd-gpt.gdisk by gdisk...
The operation has completed successfully.
*****************************************************.
done!
Saving the MBR data for sdd...
1+0 records in
1+0 records out
512 bytes copied, 0.00241426 s, 212 kB/s
End of saveparts job for image /tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo.
*****************************************************.
*****************************************************.
This image was saved successfully: d2d-pseudo
End of savedisk job for image d2d-pseudo.
Saving hardware info by lshw...
Saving DMI info...          
Saving PCI info...
Saving OS info from the device...
Saving package info...
Saving image size info...
*****************************************************
*****************************************************
Checking if udevd rules have to be restored...
This program is not started by Clonezilla server, so skip notifying it the job is done.
Finished!
Generating a tag file for this image...
The mounted bitlocker device was not found. Skip unmounting it.
Now syncing - flush filesystem buffers...

Ending /usr/sbin/ocs-sr at 2024-08-30 09:22:25 EDT...
*****************************************************.
*****************************************************.
Cloning the source device to /dev/sdc. Running:
LC_ALL=C ocs-sr --ocsroot /tmp/ocs_onthefly_src.9hdcnm -l en_US.UTF-8 --batch -j2 -scr -p true -g auto -e1 auto -e2 -r -j2 -sfsck -k1 -icds ld2d_restoredisk d2d-pseudo sdc
Setting the TERM as linux
Starting /usr/sbin/ocs-sr at 2024-08-30 09:22:25 EDT...
Start preparing device name cache files in /tmp/ocs-cache//...
The file /proc/partitions remains the same. Skip generating disk(s) list file.
The file /proc/partitions remains the same. Skip generating partitions(s) list file.
Both /proc/partitions and blkid output do not change. Skip generating file system cache file related to the dev(s).
*****************************************************.
Clonezilla image dir: /tmp/ocs_onthefly_src.9hdcnm
*****************************************************.
Target disk sdc does not exist in the image saved from disk(s) "sdd".
Creating a tmp Clonezilla image "d2d-pseudo-tmp-cnvted" based on the image "d2d-pseudo" so that we can restore the image d2d-pseudo (was saved from sdd) to sdc...
///NOTE/// If the restored OS is GNU/Linux, you might have to modify /etc/fstab and grub config file in the restored GNU/Linux to affect these changes so that it can boot successfully!
Running: create-ocs-tmp-img -or /tmp/ocs_onthefly_src.9hdcnm  d2d-pseudo d2d-pseudo-tmp-cnvted sdd sdc
Creating a temporary image based on image d2d-pseudo...
/tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/sdd1* was not found! Skip this!
/tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/sdd2* was not found! Skip this!
/tmp/ocs_onthefly_src.9hdcnm/d2d-pseudo/sdd3* was not found! Skip this!
Setting the TERM as linux
Clonezilla image dir: /tmp
*****************************************************.
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/parts... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/sdd-pt.sf... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/dev-fs.list... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/blkdev.list... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/blkid.list... done!
*****************************************************.
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/disk... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/sdd-pt.parted... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/sdd-pt.parted.compact... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/blkdev.list... done!
Change sdd to sdc in /tmp/d2d-pseudo-tmp-cnvted/blkid.list... done!
*****************************************************.
*****************************************************.
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-chs.sf' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-chs.sf'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-gpt-1st' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-gpt-1st'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-gpt-2nd' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-gpt-2nd'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-gpt.gdisk' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-gpt.gdisk'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-gpt.sgdisk' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-gpt.sgdisk'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-mbr' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-mbr'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-pt.parted' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-pt.parted'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-pt.parted.compact' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-pt.parted.compact'
renamed '/tmp/d2d-pseudo-tmp-cnvted/sdd-pt.sf' -> '/tmp/d2d-pseudo-tmp-cnvted/sdc-pt.sf'
The created image is "/tmp/d2d-pseudo-tmp-cnvted".
Activating the partition info in /proc... done!
Creating partition in /dev/sdc...
Finding all disks and partitions..
Excluding busy partition.....................
Excluding linux raid member partition.....
Unmounted partitions (including extended or swap): sdc1 sdc2
Collecting info... done!
/usr/sbin/ocs-clean-disk-part-fs: line 65: pvs: command not found
Clean filesystem header in device /dev/sdc1...
/dev/sdc1: 8 bytes were erased at offset 0x00000052 (vfat): 46 41 54 33 32 20 20 20
/dev/sdc1: 1 byte was erased at offset 0x00000000 (vfat): eb
/dev/sdc1: 2 bytes were erased at offset 0x000001fe (vfat): 55 aa
Clean filesystem header in device /dev/sdc2...
/dev/sdc2: 2 bytes were erased at offset 0x00000438 (ext4): 53 ef
Cleaning RAID metadata in device /dev/sdc...
Running: dmraid -r -E /dev/sdc
/usr/share/drbl/sbin/ocs-functions: line 16010: dmraid: command not found
Running: dd if=/dev/zero of=/dev/sdc bs=512 seek=3907028144 count=1024
1024+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.166869 s, 3.1 MB/s
Clean filesystem header in device /dev/sdc...
/dev/sdc: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/sdc: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
Trying to clean the MBR and GPT partition table on the destination disk first: /dev/sdc
Informing the OS of partition table changes... done!
*****************************************************.
Running: dd if=/dev/zero of=/dev/sdc bs=512 count=1
1+0 records in
1+0 records out
512 bytes copied, 0.0150244 s, 34.1 kB/s
*****************************************************.
/usr/share/drbl/sbin/ocs-functions: line 3476: lvscan: command not found
Error: /dev/sdc: unrecognised disk label
Create the proportional partition table in /dev/sdc based on /tmp/d2d-pseudo-tmp-cnvted/sdc-pt.sf and the size of /dev/sdc...
Running: EXTRA_SFDISK_OPT="--force --wipe always" ocs-expand-gpt-pt -icds --batch /tmp/d2d-pseudo-tmp-cnvted/sdc-pt.sf /dev/sdc 2>&1
No initial MBR table on disk /dev/sdc. Create one now by:
LC_ALL=C parted -s /dev/sdc mklabel gpt
*****************************************************.
Size of original disk:  7814037168 sectors.
Size of target disk  :  3907029168 sectors.
The ratio for target disk size to original disk size is .5000013544.
"EFI System partition" found. Not to expand this partition.
The last usable sector for this partition is 3907029134.
Changing the calculated partition size from 1953251499 to 1953251299.
The partition table to write in /dev/sdc:
*****************************************
label: gpt
label-id: 6E35A989-4A29-4E12-82CF-C76DF0033AFB
device: /dev/sdc
unit: sectors
first-lba: 34

/dev/sdc1 : start= 2048, size= 1048576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=E70EA3C1-2B5C-4914-9A0E-DE9A386C2146, name="EFI System Partition"
/dev/sdc2 : start= 1050624, size= 1952727212, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=4927BDD7-3B7F-4B2D-BB20-6C2F25353A44, name="System"
/dev/sdc3 : start= 1953777836, size= 1953251299, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=DD13BE78-382D-4E01-A7AF-28086BEDDC64, name="Data"
*****************************************
Running: LC_ALL=C sfdisk --force --wipe always /dev/sdc >> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 6E35A989-4A29-4E12-82CF-C76DF0033AFB).
/dev/sdc1: Created a new partition 1 of type 'EFI System' and of size 512 MiB.
/dev/sdc2: Created a new partition 2 of type 'Linux filesystem' and of size 931.1 GiB.
/dev/sdc3: Created a new partition 3 of type 'Linux filesystem' and of size 931.4 GiB.
/dev/sdc4: Done.

New situation:
Disklabel type: gpt
Disk identifier: 6E35A989-4A29-4E12-82CF-C76DF0033AFB

Device          Start        End    Sectors   Size Type
/dev/sdc1        2048    1050623    1048576   512M EFI System
/dev/sdc2     1050624 1953777835 1952727212 931.1G Linux filesystem
/dev/sdc3  1953777836 3907029134 1953251299 931.4G Linux filesystem

## Failure message

Filesystem volume name:   System
Last mounted on:          /
Filesystem UUID:          f3c9b3ef-8f62-4f64-8565-a26640a017cb
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              122085376
Block count:              488311552
Reserved block count:     24415577
Overhead clusters:        7946188
Free blocks:              254270228
Free inodes:              117630915
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Sun Jul  3 16:00:58 2022
Last mount time:          Wed Aug 28 13:52:13 2024
Last write time:          Thu Aug 29 13:08:06 2024
Mount count:              0
Maximum mount count:      -1
Last checked:             Thu Aug 29 13:08:06 2024
Check interval:           0 ()
Lifetime writes:          9 TB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      4971f2f7-0fdd-4780-9c9b-c8eeaf6456f4
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x8dc6a520

dumpe2fs 1.47.0 (5-Feb-2023)
dumpe2fs: Invalid argument while reading journal super block

Unable to read the contents of this file system!
Because of this some operations may be unavailable.
The cause might be a missing software package.
The following list of software packages is required for ext4 file system support:  e2fsprogs v1.41+.

Any suggestions?

I can install a clonezilla-created Linux image from a USB thumb drive but I'm interested in being able to use Clonezilla Live to install a clonezilla-create image that I have burned onto a DVD. I can't find any references saying it is not possible to install a CloneZilla DVD image (of Linux). Does anyone know if this is possible? I have searched through StackExchange and other community sites, Youtube videos for an answer but what I'm really looking for a definite "no, you cannot install a Clonezilla-create image that is on a DVD". I have tried installing with CloneZilla using the device-image and device-device options.

I've taken a clone of a machine with the following partitions: Device Type Label /dev/sda /dev/sda1 Ext4 boot /dev/sda2 Linux LVM /dev/system/ LV system /dev/system/home LV home /dev/system/root LV root /dev/system/swap LV swap These are referenced by label in /etc/fstab: LABEL=root / ext4 LABEL=boot /boot ext4 LABEL=home /home ext4 LABEL=swap /swap swap and grub.cfg: menuentry 'openSUSE, with linux ' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux--simple-' { insmod ext2 set root='hd0,msdos1' linux /vmlinuz- root=/dev/mapper/system-root resume=/dev/disk/by-label/swap initrd /initrd- } I am trying to install this clone on another identical machine. The install succeeds, but I can't boot into the machine without doing the following in the grub prompt it dumps me into: grub> set root=(hd0,1) grub> linux /boot/vmlinuz- root=/dev/sda1 grub> initrd /boot/initrd.img- grub> boot I'd much prefer to get an image which does not require these steps, but I'm not sure where the problem lies (grub config, other system files, clonezilla). Things I have tried so far: - Edited /etc/defaults/grub and uncommented 'GRUB_DISABLE_LINUX_UUID=true' - Edited grub-mkconfig_lib to comment out the lines like search --no-floppy --fs-uuid --set=root ${hints} ${fs_uuid} to prevent them being added when grub.cfg is generated - (and re-generated grub.cfg) - Selected advanced clonezilla install and told it to re-install the MBR afterwards (option -j1. option -g auto "Reinstall grub in client disk MBR" was already selected by default) Any other things I can try? I did notice that /boot/grub2/device.map lists "sda1" for hd0, but the HD of the other machine is being detected as sda1 when I install the clone so I don't think this is likely to be the culprit. (I wasn't sure if here or Superuser was the better fit for the question, I am happy for it to be migrated as appropriate.)

I'm sorry if this question is not on topic. I am moving from Windows to Linux and had the idea to use a bootable Linux Mint external SSD to slowly download and integrate all the software I use, while at the same time using Windows as my daily driver. Once I am comfortable with Linux, I will then discard windows and use Linux Mint as my daily driver. I will then need to clone the bootable Linux Mint on to my main SSD. Would Clonezilla allow me to clone the bootable SSD on to my main SSD and use the rest of the allocated space on my drive as free space for Linux Mint?

I have been doing backups with partclone for a short while, and just discovered that it is part of Clonezilla, which may be a more convenient tool than using partclone directly. It appears to be free, so I wanted to download a copy, clicking one of the bewildering array of stuff my search had returned. It took me right down a "rabbit hole" -- weird messages claiming to be from Microsoft (why? I'm doing this on Linux) and claiming I've been infected and if I don't do as they say my data will be deleted. Sheesh! So I closed the browser. So how do I build or download a copy of Clonezilla without letting the bad guys steal everything before I get it backed up?

I have booted clonezilla live done a partition-to-partition copy to copy between a 5400rpm HDD into unpartitioned space on a new SSD (both connected via sata). It took over 12.5 hours to copy 100GB. The 'remaining' time only ever went up (not down). Why is the rate that low when they are both connected onto the primary sata 3 bus? Now it is sitting on 100% and has been for a further 6 hours. I'm just wondering what it is "syncing" about. The time remaining is zero; the elapsed isn't changing. The cursor is still blinking away; the mouse moves, so it doesn't appear to be a lockup. What does this part of the process do? how long do I leave it before I pronounce it a fail, if it indeed is one?

When running Clonezilla on a NTFS-drive with bad sectors the cloning is interrupted and I get a suggestion from Clonezilla to use the -rescue option to save as much as possible from the damaged drive. What does the -rescue option do? How do I use it? When should I use it?

I have the following disks and partitions: sda 8:0 0 238,5G 0 disk ├─sda1 8:1 0 16M 0 part ├─sda2 8:2 0 174,5G 0 part ├─sda3 8:3 0 529M 0 part └─sda4 8:4 0 63,5G 0 part /var/snap/firefox/common/host-hunspell / sdb 8:16 0 931,5G 0 disk ├─sdb1 8:17 0 100M 0 part /boot/efi ├─sdb2 8:18 0 128M 0 part ├─sdb3 8:19 0 467,7G 0 part ├─sdb4 8:20 0 416,8G 0 part /mnt/storage └─sdb5 8:21 0 46,8G 0 part sdc 8:32 0 476,9G 0 disk sr0 11:0 1 1024M 0 rom sda is an SSD containing a Windows partition (sda2) and an Ubuntu partition I'm currently using (sda4). sdb is an HDD used mainly for storage. sdc is a new SSD. I want to clone sda4 to sdc and keep entries for both sda4 and the new cloned partition in GRUB. This is what I'm thinking of at the moment: 1. Use GParted to create an ext4 partition sdc1 on sdc. 2. Boot Clonezilla from a flash drive. 3. Clone sda4 to sdc1. 4. Boot Ubuntu from a flash drive. 5. Generate a new UUID for sdc1 using GParted or command line. 6. Mount sdc1 and update its /etc/fstab file with the new UUID. 7. Run sudo update-grub. I have doubts about the last point. Can it be done on a live Ubuntu? But if I reboot beforehand, I won't know which partition is present in GRUB - sda4 or sdc1 (and does it really matter?)? Is there an easier way to do all of that?

SOLVED! THE REAL PROBLEM WAS MY HARDWARE: I tried running Kubuntu in a live environment through my USB and I had the same problem (and in the windows setup then as well, but I didn't notice). After that I started looking for possible hardware problems and found my PC on this list: https://www.dell.com/support/kbdoc/en-us/000126548/resolution-on-external-monitor-limited-to-1920-x-1080-using-hdmi My PC's motherboard doesn't support 4K over HDMI (only DP), so I'll have to get a display port cable. TLDR AT THE END I recently cloned my SSD with Clonezilla from a laptop with Linux Kubuntu to a new desktop PC. Both SSDs were 500gb, the laptop has a 12th gen i5 processor, and the PC has a 13th gen i7 processor, and there are no separate GPUs . The laptop’s default display is its 1080p built-in display. I've connected the new PC to a new 4K monitor, but it can only display 1080p on the monitor. I suspect it’s an issue with cloning from the laptop because I can connect the monitor to my laptop and have it display 4K without any issues (with the exact same hard drive information as the PC which can’t do this). I don’t know what exactly is going on, but based on this I suspect that the PC thinks that the primary display it’s dealing with is still my laptop’s 1080p built-in display and that there is no (easy) way to change that. The first time I booted into Linux on my new PC, the screen was shrinked to 1080p and centered on the monitor, and when I restarted it was across the entire monitor screen but it was scaled down to 1080p and it's remained that way since. Additionally, the Dell BIOS and the Windows installation the PC came with could both display 4K on any 4K monitor. Here's what I've tried so far: 1. Checked cable connections and the monitor. 4K works on other laptops and PCs without issues. The same problem is present with my PC if I connect it to any other 4K monitor as well. 2. Made sure the system (and the kernel) are up-to-date. 3. Tried to add the resolution with xrandr and failed (both with 30Hz and 60Hz): user:~$ xrandr --output HDMI-2 --mode 3840x2160 xrandr: cannot find mode 3840x2160 user:~$ WLR_DRM_NO_MODIFIERS=1 user:~$ xrandr --output HDMI-2 --mode 3840x2160 xrandr: cannot find mode 3840x2160 user:~$ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) HDMI-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 1920x1080 60.00* 50.00 59.94 1680x1050 59.88 1280x1024 75.02 60.02 1440x900 59.90 1280x960 60.00 1280x720 60.00 50.00 59.94 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 720x576 50.00 720x480 60.00 59.94 640x480 75.00 72.81 66.67 60.00 59.94 720x400 70.08 user:~$ xrandr --newmode "3840x2160_30.00" 297.0 3840 4016 4104 4400 2160 2168 2178 2250 +hsync -vsync xrandr --addmode HDMI-2 "3840x2160_30.00" xrandr --output HDMI-2 --mode "3840x2160_30.00" xrandr: Configure crtc 0 failed 4. Added the new resolution with the „cvt“ command, after which I could see it in xrandr and in system settings. However, when I selected the 4K resolution nothing would happen (the display would just remain at 1080p, confirmed by checking the built-in monitor information). Here is also my output from xrandr –verbose (my monitor is connected with HDMI 2): Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384 DP-1 disconnected (normal left inverted right x axis y axis) Identifier: 0x42 Timestamp: 382787 Subpixel: unknown Clones: HDMI-1 CRTCs: 0 1 2 3 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled vrr_capable: 0 range: (0, 1) Colorspace: Default supported: Default, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, RGB_WIDE_FIXED, RGB_WIDE_FLOAT, BT601_YCC max bpc: 12 range: (6, 12) Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on subconnector: Unknown supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native link-status: Good supported: Good, Bad CONNECTOR_ID: 236 supported: 236 non-desktop: 0 range: (0, 1) HDMI-1 disconnected (normal left inverted right x axis y axis) Identifier: 0x43 Timestamp: 382787 Subpixel: unknown Clones: DP-1 CRTCs: 0 1 2 3 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled max bpc: 12 range: (8, 12) content type: No Data supported: No Data, Graphics, Photo, Cinema, Game Colorspace: Default supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad CONNECTOR_ID: 249 supported: 249 non-desktop: 0 range: (0, 1) HDMI-2 connected primary 1920x1080+0+0 (0x46) normal (normal left inverted right x axis y axis) 632mm x 360mm Identifier: 0x44 Timestamp: 382787 Subpixel: unknown Gamma: 1.0:1.1:1.1 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 2 3 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: _KDE_SCREEN_INDEX: 1 EDID: 00ffffffffffff004c2d1710454d4e30 23210103803f24782ac8b5ad50449e25 0f5054bfef80714f810081c081809500 a9c0b300010108e80030f2705a80b058 8a0078682100001e000000fd00324b1e 873c000a202020202020000000fc004c 5532385235350a2020202020000000ff 00484e4d573830303835340a20200195 020335f04961120313041f10605f2309 070783010000e305c0006b030c001000 b8442000200167d85dc40178800be306 0501e20f81023a801871382d40582c45 0078682100001e023a80d072382d4010 2c458078682100001e04740030f2705a 80b0588a0078682100001e565e00a0a0 a029503020350078682100001a000049 HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled max bpc: 12 range: (8, 12) content type: No Data supported: No Data, Graphics, Photo, Cinema, Game Colorspace: Default supported: Default, SMPTE_170M_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, opRGB, BT2020_CYCC, BT2020_RGB, BT2020_YCC, DCI-P3_RGB_D65, DCI-P3_RGB_Theater aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on link-status: Good supported: Good, Bad CONNECTOR_ID: 255 supported: 255 non-desktop: 0 range: (0, 1) 1920x1080 (0x46) 148.500MHz +HSync +VSync *current h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x47) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew 0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x48) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1680x1050 (0x49) 119.000MHz +HSync -VSync h: width 1680 start 1728 end 1760 total 1840 skew 0 clock 64.67KHz v: height 1050 start 1053 end 1059 total 1080 clock 59.88Hz 1600x900 (0x4a) 108.000MHz +HSync +VSync h: width 1600 start 1624 end 1704 total 1800 skew 0 clock 60.00KHz v: height 900 start 901 end 904 total 1000 clock 60.00Hz 1280x1024 (0x4b) 135.000MHz +HSync +VSync h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 79.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 75.02Hz 1280x1024 (0x4c) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1440x900 (0x4d) 88.750MHz +HSync -VSync h: width 1440 start 1488 end 1520 total 1600 skew 0 clock 55.47KHz v: height 900 start 903 end 909 total 926 clock 59.90Hz 1280x800 (0x4e) 71.000MHz +HSync -VSync h: width 1280 start 1328 end 1360 total 1440 skew 0 clock 49.31KHz v: height 800 start 803 end 809 total 823 clock 59.91Hz 1152x864 (0x4f) 108.000MHz +HSync +VSync h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.50KHz v: height 864 start 865 end 868 total 900 clock 75.00Hz 1280x720 (0x50) 74.250MHz +HSync +VSync h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 45.00KHz v: height 720 start 725 end 730 total 750 clock 60.00Hz 1280x720 (0x51) 74.250MHz +HSync +VSync h: width 1280 start 1720 end 1760 total 1980 skew 0 clock 37.50KHz v: height 720 start 725 end 730 total 750 clock 50.00Hz 1280x720 (0x52) 74.176MHz +HSync +VSync h: width 1280 start 1390 end 1430 total 1650 skew 0 clock 44.96KHz v: height 720 start 725 end 730 total 750 clock 59.94Hz 1024x768 (0x53) 78.750MHz +HSync +VSync h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.02KHz v: height 768 start 769 end 772 total 800 clock 75.03Hz 1024x768 (0x54) 75.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1328 skew 0 clock 56.48KHz v: height 768 start 771 end 777 total 806 clock 70.07Hz 1024x768 (0x55) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 832x624 (0x56) 57.284MHz -HSync -VSync h: width 832 start 864 end 928 total 1152 skew 0 clock 49.73KHz v: height 624 start 625 end 628 total 667 clock 74.55Hz 800x600 (0x57) 50.000MHz +HSync +VSync h: width 800 start 856 end 976 total 1040 skew 0 clock 48.08KHz v: height 600 start 637 end 643 total 666 clock 72.19Hz 800x600 (0x58) 49.500MHz +HSync +VSync h: width 800 start 816 end 896 total 1056 skew 0 clock 46.88KHz v: height 600 start 601 end 604 total 625 clock 75.00Hz 800x600 (0x59) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x5a) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 720x576 (0x5b) 27.000MHz -HSync -VSync h: width 720 start 732 end 796 total 864 skew 0 clock 31.25KHz v: height 576 start 581 end 586 total 625 clock 50.00Hz 720x480 (0x5c) 27.027MHz -HSync -VSync h: width 720 start 736 end 798 total 858 skew 0 clock 31.50KHz v: height 480 start 489 end 495 total 525 clock 60.00Hz 720x480 (0x5d) 27.000MHz -HSync -VSync h: width 720 start 736 end 798 total 858 skew 0 clock 31.47KHz v: height 480 start 489 end 495 total 525 clock 59.94Hz 640x480 (0x5e) 31.500MHz -HSync -VSync h: width 640 start 656 end 720 total 840 skew 0 clock 37.50KHz v: height 480 start 481 end 484 total 500 clock 75.00Hz 640x480 (0x5f) 31.500MHz -HSync -VSync h: width 640 start 664 end 704 total 832 skew 0 clock 37.86KHz v: height 480 start 489 end 492 total 520 clock 72.81Hz 640x480 (0x60) 30.240MHz -HSync -VSync h: width 640 start 704 end 768 total 864 skew 0 clock 35.00KHz v: height 480 start 483 end 486 total 525 clock 66.67Hz 640x480 (0x61) 25.200MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.50KHz v: height 480 start 490 end 492 total 525 clock 60.00Hz 640x480 (0x62) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz v: height 480 start 490 end 492 total 525 clock 59.94Hz 720x400 (0x63) 28.320MHz -HSync +VSync h: width 720 start 738 end 846 total 900 skew 0 clock 31.47KHz v: height 400 start 412 end 414 total 449 clock 70.08Hz 3840x2160_60.00 (0x7a4) 712.750MHz -HSync +VSync h: width 3840 start 4160 end 4576 total 5312 skew 0 clock 134.18KHz v: height 2160 start 2163 end 2168 total 2237 clock 59.98Hz I've also tried some other things which I can't remember right now, but none of them worked. Do you think there's a way to fix this or should I just give up? Also, is it possible to install a fresh Linux Kubuntu installation on my PC (which I assume would solve the problem), copy the monitor configuration files or something if that's possible, clone my laptop SSD again with Clonezilla and then paste the monitor configuration files/settings from the fresh installation into my laptop clone. Is this possible? I'm not that experienced with Linux, so I have no idea. Any help would be greatly appreciated! TL;DR: Cloned Linux Kubuntu installation with Clonezilla from laptop to PC. PC can't display 4K on monitor (only 1080p), but the laptop can. The laptop's built in display is 1080p. The PC could display 4K in Dell BIOS and Windows, and the monitor (as well as its cables) work on all other PCs/laptops, leading me to believe the problem is software related and has to do with cloning from the laptop to a PC (I assume the PC „thinks“ the main display is still the laptop's built-in display). Most common workarounds found online, such as adding the resolution with „xrandr“ didn't work. Using the „cvt“ command added the resolution to xrandr and system settings, but changing the resolution does nothing. Is there a way to fix this? Would creating a new Linux Kubuntu installation and copying some monitor configuration files to the cloned installation fix things?

When I was using the clonezilla-live-20220502-jammy-amd64 version of clonezilla for a linux system backup, the following error occurred. When I executed the e2fsck -f /dev/mmcblk0p2 command and backed up again, there was no error. I want to know the specific reason for it. I am concerned about any hidden system bugs that may cause exceptions when running programs on the backup system in the future. Use partclone with pigz to save the image. Image file will be split with size limit 4096 MB. If this action fails or hangs, check: * Is the disk full ? Running: partclone.ext4 -2 10485760 -L /var/log/partclone.log -c -s /dev/sad2 Partclone y03.20 http://partclone.org Starting to clone device (/dey/mmcblkOp2) to image (-) Reading Super Block Calculating bitmap.... Please wait ..1.00%extfsclone.c: bi Elapsed: 00:00:01, Remaining: 00:01:39, Completed:1.00% Please run fsck to check and repair the file system Partclone fail, please check /var/log/partclone.logChecking the disk space .. Failed to use partclone program to save or restore an image!

Guess this is the first time I post a question here. Have been playing with Linux and VMware servers for more than 10 years now. Lately I decided to move my focus on Debian desktops and ProxMox (again). Reasons being more privacy friendly, broader hardware support and lower resource reqs. So bye bye Windows (for now) and Intel/AMD (later on). Have been working hard to compose my own Debian desktop from scratch, picking XFCe for GUI. Works quite nice now (not as slick as Windows, but smarter, faster), but with a lot of loose ends to tie up. One of em being the lack of genuine Microsoft fonts (working on that), another being Samba on my (home brew) NASses: gives a number of issues with Linux applications (locking problems, not able to create shortcuts on the NAS, etc). Will try and see how NFS goes later. My problem, however: Having converted my 1st Windows desktop to a Debian/XFCe desktop I am about to convert my 2nd Windows desktop. I've used Clonezilla v2.2.3 for years and it served me well. When trying to backup Debian v11 (Bullseye) though, it didn't work so well. Had to upgrade to Clonezilla v3.0.1. Now for the cloning part: my three Windows desktops have identical hardware, and cloning Windows (with Clz v2.2.3) always went well (of course changing licence keys, IPs and hostnames). But when I clone my Debian desktop (with disk-to-image backup and image-to-disk restore), I can't make the clone to boot. BIOS/UEFI says 'Reboot and select proper boot device'. Tried to fix it myself. Read a number of posts (many ArchLinux and Ubuntu by the way) and finally tried this: www.debian.org/releases/stable/amd64/ch08s06.en.html Using my Debian installation USB stick I was able to get into Rescue Mode and have the installer reinstall GRUB on my boot disk: it ended with: "Execution of 'grub-install /dev/sda' failed". Most of the other articles I read point in the same direction, so I'm kinda stuck. My questions: Does anybody have good experiences with cloning Linux systems with Clonezilla? Any idea how I could go on from here? Additional info: My partiton layout is: # Size In use Free iSize Type/description 1 499 MB 4 MB 495 MB 476 MiB EFI/boot partition (/boot/efi) 2 40,0 GB 11,8 GB 28,2 GB 37,3 GiB Linux root (/) 3 16,1 GB 10,0 GB PM 9,3 GiB Linux swap 4 70,0 GB 12,3 GB 57,7 GB 65,2 GiB Linux home (/home) - 120 GB PM 120 GB 111,3 GiB Free space 1st partition starts at sector 2048 (partition alignment is at 1 MB intervals). Sector 0 = boot sector, sector 2-33 is (primary?) GPT partition table. Don't know what sector 1 is used for. Wikipedia says GPT is GUID (UUID) based. I'm aware that with GPT every disk (and partition on it) has a UUID. Can't remember if I had to fix that when cloning Windows in the past. On the other hand: overriding a UUID during cloning to me seems only a possible problem if the old UUID is actually stored in NVRAM in the BIOS/UEFI. I've not seen an indication for this in my (AMI) BIOS boot menu. On my live desktop I see a directory called 'EFI' under '/boot/efi'. The latter directory was empty when I looked at it on my clone system under Rescue Mode. But I guess that's OK since I learned that my 1st partition is mounted under /boot/efi during normal bootup. Final remarks: I've searched through this forum and found slightly related posts, but not close enough. And I hope my personal introduction is not considered too long or off topic. Awaiting your reactions, With kind regards, Steijn van Essen *From i8088 to i7-980X in 25 years and still waiting … But not for much longer: when Windows is gone, Intel will be next (in favor of ARM on Raspberry Pi)*

I would like to clone my OS drive, to a same/larger disk. And I will do this periodically. On Windows I use AOEMI Partition Assistant to clone disks. The GUI is very good and idiot-proof. However, Linux isn't supported. I have tried Clonezilla and I didn't find the walkthrough completely obvious/idiot-proof. dd petrifies me in case I make a mistake. Is there anything else to recommend? Particularly anything which contains explicit safety checks to ensure the current OS drive is not over-written.

I have been trying to clone my Debian /dev/sda1 partition containing /root with size of 100GB using Clonezilla. I did this by using Clonezilla-live to create iso file with size around 18 GB. It seems succesfully clone /root. My problem rises when I tried to restore it in virtualbox which I created with drive size of 110GB. The restore process shows the following: Disk destinantion is too small! Destination disk size: 230686720 sectors (118.1 GB) Source disk size from the image: 976773168 sectors (500.1 GB) Program terminated!! It looks like Clonezilla only copies /root, but put the size of entire harddirsk instead of only 1 partition. Am I doing something wrong in creating iso file to restore 1 partition only? Or is it the limitation mentioned in Clonezilla website ? As far as I understand, it states that The destination partition must be equal or larger than the source one not The destination disk.

I have an ubuntu system, and I want to have a semi-automated way of running a clonezilla unattended image / re-image from a USB drive. To that end, I've modified the GRUB menu items to be along these lines: (One for Restore, one for image): menuentry "RESTORE IMAGE" --id live-default { $linux_cmd /live/vmlinuz boot=live union=overlay username=user config components noswap edd=on nomodeset enforcing=0 noprompt ocs_prerun="mount -L Images /mnt" ocs_prerun1="mount --bind /mnt/images /home/partimag/" ocs_live_run="ocs-sr -g auto -e1 auto -e2 -r -j2 -c -k0 -scr -icds -p reboot restoredisk ask_user ask_user" keyboard-layouts=en-us ocs_live_batch="yes" locales=en_US.UTF-8 vga=788 ip= nosplash net.ifnames=0 i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=1 $initrd_cmd /live/initrd.img } What I want to be able to do from the running machine is something like the following: 1. Set next boot (using efibootmgr?) to USB drive 2. touch or set *something* to choose either the RESTORE or IMAGE option on the USB drive GRUB menu item. 3. Reboot into USB drive, run the selected boot path The dumb way I can think of this is modifying the USB grub.conf each time to set the default menu item. There has to be a better way, right?