Installation and Boot Process

This section covers downloading the ISO, creating boot media, troubleshooting, and advanced boot configurations for starting Clonezilla. It's essential for ensuring a smooth cloning operation without unexpected interruptions.

Creating Live Media

Option 1: USB Drive (Recommended)

Linux terminal showing dd command for creating Clonezilla USB — Using dd command on Linux to create bootable Clonezilla USB

On Linux:

# Download Clonezilla ISO from official source wget https://sourceforge.net/projects/clonezilla/files/latest/download -O clonezilla.iso # Create bootable USB (WARNING: destroys all data on USB!) sudo dd if=clonezilla.iso of=/dev/sdX bs=4M status=progress && sync

Replace /dev/sdX with your actual USB device (e.g., /dev/sdb). Always double-check with lsblk to avoid writing to the wrong drive!

Verification Step: After creating the bootable USB, verify it with sudo fdisk -l /dev/sdX to ensure the partition structure looks correct before using it.

On Windows:

Download the Clonezilla ISO from SourceForge
Download and install Rufus (free, open-source tool)
Select the downloaded ISO file in Rufus
Choose your USB drive from the dropdown
Click START to create bootable media

Pro Tip: Use a USB 3.0 drive with at least 16GB capacity for faster boot times and better compatibility with modern DGX systems. Smaller USB drives (4-8GB) may not have enough space for large disk images.

Option 2: Network PXE Boot (For Multiple Machines)

For enterprise deployments across many machines, PXE boot eliminates the need for individual USB drives. This is ideal for imaging workstations in a lab environment or server farms.

Set up Clonezilla-server on a Debian/Ubuntu machine (requires Docker or manual installation)
Configure DHCP server with TFTP options for network booting
Boot target machines via network boot (PXE) from BIOS/UEFI

Example PXE Configuration (/etc/dhcp/dhcpd.conf):

subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.100 192.168.1.200; option routers 192.168.1.1; next-server 192.168.1.10; filename "boot/grpc/boot.sys"; }

Booting Clonezilla

Insert USB drive (or ensure network boot is enabled)
Restart target machine and enter BIOS/UEFI (usually F2, F12, or Del key)
Set USB or network boot as first boot priority
Save changes and reboot
Select language (e.g., "1" for English)
Choose keyboard layout (e.g., "1" for US)
Display mode: "1" for text mode (most reliable)

System Requirements

Minimum RAM: 256MB (512MB+ recommended for network operations)
Disk space: 2GB for Clonezilla itself, plus storage for images
Network: Required for PXE boot and NFS/iSCSI backups
Hardware: Works on x86/x86_64, ARM64, and PowerPC architectures
Storage: For DGX Spark, ensure backup destination has at least 1TB free space for full disk imaging

Important for DGX Spark: Clonezilla requires direct hardware access. It cannot run from within a VM without appropriate passthrough configuration for storage devices. For best results with DGX Spark, boot directly from USB.

Troubleshooting Common Boot Issues

USB Not Booting

If your Clonezilla USB isn't booting, check these common issues:

BIOS/UEFI mismatch: Ensure your boot mode (UEFI vs Legacy BIOS) matches the USB creation mode. Rufus can create both UEFI and Legacy BIOS versions.
Secure Boot: Disable Secure Boot in BIOS settings, or use a signed Clonezilla image that's compatible with your motherboard's key database.
USB port issues: Try different USB ports, especially USB 2.0 ports on older systems that might not support booting from USB 3.0-only devices.

Display/Keyboard Issues

Clonezilla uses text-based interfaces. If you see a black screen or can't use the keyboard:

Switch display mode: Try different display options (1, 2, or 3) to find one compatible with your graphics card.
Keyboard layout: If keys don't match expected output, restart and select a different keyboard layout option.
Serial console: For headless systems, you can redirect Clonezilla output to a serial console using kernel parameters.

Bootloader/Partition Table Issues

When restoring a disk image, you may encounter boot errors:

GRUB not found: After restoring to new hardware, you may need to chroot into the restored system and reinstall GRUB/bootloader.
Partition alignment: Modern SSDs benefit from 4K-aligned partitions. Clonezilla handles this automatically with the "aligned" option during restore.
Filesystem check: Always run fsck on restored filesystems before booting to prevent corruption.

Advanced Boot Options

For experienced users, Clonezilla supports boot command-line parameters:

clock: Set clock settings (e.g., clock=20240101000000 for 2024-01-01 00:00:00)
clocksource: Specify clock source (e.g., clocksource=tsc)
rescue: Boot into rescue mode for system recovery
noacpi: Disable ACPI for compatibility with older hardware

Example boot command: clonezilla clocksource=tsc noacpi

Note: Advanced boot parameters require understanding of kernel boot behavior. Use with caution and test in a non-production environment first.

Verification After Boot

Once Clonezilla boots successfully, verify the system is functioning correctly:

Check available disk space: df -h
List connected drives: lsblk
Verify network connectivity: ping -c 3 192.168.1.1 (adjust for your network)
Test write permissions if backing up to network storage: touch test_file

Once verified, you're ready to proceed with disk imaging operations. See the Recommended Tools section for utilities that will streamline your workflow.