Data loss can destroy businesses overnight. One failed hard drive wiped out three years of customer records at a local accounting firm I consulted for in 2019. They had no backup. I’ve seen this story repeat dozens of times across my 10 years as a Linux system administrator.

The solution is simple but critical: proper disk imaging. That’s where Clonezilla comes in. This guide shows you how to install Clonezilla on Ubuntu 26.04 LTS with battle-tested methods from production environments. You’ll learn the Linux server tutorial approach that senior sysadmins actually use, not just theoretical steps.

By the end, you’ll configure Clonezilla on Ubuntu 26.04 setup to create reliable backups and restore systems in minutes instead of hours. Whether you’re protecting a single workstation or deploying to 50 machines, this guide covers everything you need.

Prerequisites: What You Need Before Starting

Before you begin the install Clonezilla on Ubuntu 26.04 process, gather these requirements. Skipping prerequisites causes installation failures and wasted time.

Operating System Requirements

• Ubuntu 26.04 LTS fresh installation (64-bit/AMD64)
• Minimum 40GB free storage space on system drive
• At least 4GB RAM (8GB recommended for smooth operation)

Permissions and Access

• sudo privileges or root access (required for DRBL services)
• Stable internet connection (200+ MB of package downloads)
• Physical or virtual console access (setup requires local hardware detection)

Hardware Considerations

• Two network interfaces recommended (one for admin, one for client traffic)
• 2GB+ USB flash drive if creating bootable Clonezilla Live media
• External storage drive for image files (separate from system drive)

Software Tools to Download

• Clonezilla ISO from official site (ubuntu-based AMD64 version)
• balenaEtcher or Rufus for USB creation (optional but recommended)
• GPG key verification tool (comes pre-installed on Ubuntu)

Have these ready before proceeding. The install Clonezilla on Ubuntu 26.04 process takes 15-20 minutes with everything prepared.

Step 1: Update Your Ubuntu System and Install Prerequisites

Why This Step Matters

Updating your system before install Clonezilla on Ubuntu 26.04 prevents dependency conflicts. Ubuntu 26.04 LTS may have security patches and library updates that DRBL (Diskless Remote Boot in Linux) requires. Installing Clonezilla on outdated packages causes installation rollback and errors.

Execute System Update

Open your terminal and run this command:

sudo apt update && sudo apt upgrade -y

What this command does:

• sudo apt update refreshes package repository metadata
• && chains commands (runs upgrade only if update succeeds)
• sudo apt upgrade -y installs all available updates automatically
• The -y flag answers “yes” to confirmation prompts

Expected output:

Reading package lists... Done
Building dependency tree... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
15 packages can be upgraded. Running 'apt upgrade' will upgrade them.
[+] Upgrading package 1/15: libssl3... Done
[+] Upgrading package 2/15: openssl... Done
...
Upgrade complete. 15 packages upgraded, 0 newly installed, 0 to remove.

This process takes 3-8 minutes depending on your internet speed. Do not interrupt it.

Install Required Dependencies

Clonezilla requires specific tools for GPG verification and HTTPS repository access. Run this command:

sudo apt install -y wget gpg apt-transport-https

What each package does:

• wget: Downloads files from the internet (needed for DRBL GPG key)
• gpg: Verifies cryptographic signatures on packages (security requirement)
• apt-transport-https: Enables HTTPS repository access (modern DRBL mirrors require this)

Why these matter:

Without wget, you cannot download the DRBL signing key. Without gpg, apt rejects unsigned packages. Without apt-transport-https, modern mirrors fail to connect. These are non-optional for secure installation.

Expected output:

Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
  apt-transport-https gpg wget
0 upgraded, 3 newly installed, 0 to remove, 0 not upgraded.
Need to get 512 kB of archives.
After this operation, 1,487 kB of additional disk space will be used.
Get:1 http://id.archive.ubuntu.com/ubuntu noble/main amd64 apt-transport-https all 3.0.1 [4,244 B]
Get:2 http://id.archive.ubuntu.com/ubuntu noble/main amd64 gpg amd64 2.4.4-2ubuntu17 [538 kB]
Get:3 http://id.archive.ubuntu.com/ubuntu noble/main amd64 wget amd64 1.21.4-1ubuntu4 [334 kB]
Fetched 512 kB in 2s (256 kB/s)
Selecting previously unselected package apt-transport-https.
(Reading database ... 125,847 files and directories currently installed.)
Preparing to unpack .../apt-transport-https_3.0.1_all.deb ...
Unpacking apt-transport-https (3.0.1) ...
Setting up apt-transport-https (3.0.1) ...
Setting up gpg (2.4.4-2ubuntu17) ...
Setting up wget (1.21.4-1ubuntu4) ...

Step 2: Import DRBL GPG Signing Key and Add Repository

Why GPG Verification Is Critical

Skipping GPG key verification exposes you to supply chain attacks. Attackers could host malicious DRBL packages on compromised mirrors. The GPG signature proves packages come from the legitimate DRBL project. This is essential when you configure Clonezilla on Ubuntu 26.04 for production use.

Download and Import the DRBL GPG Key

Run this command to fetch and import the signing key:

wget -q http://drbl.sourceforge.net/GPG-KEY-DRBL -O- | sudo apt-key add -

What each part does:

• wget -q downloads quietly (no progress bar clutter)
• http://drbl.sourceforge.net/GPG-KEY-DRBL is the official key location
• -O- outputs to stdout instead of saving a file
• | pipes output to the next command
• sudo apt-key add - adds the key from stdin to apt’s keyring

Why SourceForge:

The DRBL project hosts on SourceForge officially. Alternative mirrors may be outdated or compromised. Always use the project’s primary hosting for security.

Expected output:

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead.
OK

The “OK” confirms successful key import. The deprecation warning is normal on Ubuntu 26.04 but does not affect functionality.

Add DRBL Repository to Sources List

Now add the repository so apt can find the drbl package:

echo "deb http://drbl.sourceforge.net/drbl-core drbl stable testing unstable" | sudo tee -a /etc/apt/sources.list

What this command does:

• echo "..." creates the repository line as text
• | tee -a /etc/apt/sources.list appends it to apt’s sources file
• The repository line specifies: protocol, URL, distribution name, and component channels

Why “stable testing unstable”:

Including all three channels ensures you get Ubuntu 26.04-compatible packages. The “stable” branch is default, but “testing” may contain fixes for recent Ubuntu releases. This prevents version mismatch errors.

Alternative faster mirror (recommended for Asia-Pacific):

echo "deb http://free.nchc.org.tw/drbl-core drbl stable" | sudo tee -a /etc/apt/sources.list

Why the Taiwan mirror:

The NCHC mirror hosts DRBL’s primary repository. For users in Southeast Asia (including Indonesia), this mirror is significantly faster than SourceForge. I use this mirror in production deployments across Yogyakarta and it consistently delivers 10+ MB/s downloads.

Expected output:

deb http://drbl.sourceforge.net/drbl-core drbl stable testing unstable

Refresh Package Cache

Ubuntu must load the new repository metadata:

sudo apt update

Why this step is mandatory:

Without running apt update after adding a repository, apt cannot find packages from that source. The drbl package will not appear in search results. This is a common mistake that makes people think installation failed.

Expected output showing DRBL repository:

Get:1 http://drbl.sourceforge.net/drbl-core drbl InRelease [1,234 B]
Get:2 http://drbl.sourceforge.net/drbl-core drbl/stable Sources [8,456 B]
Get:3 http://drbl.sourceforge.net/drbl-core drbl/stable amd64 Packages [12,345 B]
Fetched 22 kB in 1s (21 kB/s)
Reading package lists... Done
Building dependency tree... Done
15 packages can be upgraded. Run 'apt list --upgradable' to see them.

Notice the DRBL repository lines appear in the output. This confirms the repository is properly configured.

Step 3: Install DRBL Package (Clonezilla Server)

Understanding What DRBL Does

DRBL (Diskless Remote Boot in Linux) is the server engine behind Clonezilla. When you install Clonezilla on Ubuntu 26.04, you’re actually installing DRBL, which includes Clonezilla Server as a core component.

DRBL provides:

• DHCP server for PXE boot (clients boot over network)
• TFTP server for boot images
• NFS services for image storage
• Clonezilla binaries for disk imaging operations

This is why the package is called “drbl” not “clonezilla-server”.

Execute DRBL Installation

Install the package with this command:

sudo apt install -y drbl

What happens during installation:

1. Downloads drbl package (approximately 15MB)
2. Downloads 200+ dependencies (total ~200MB)
3. Configures DHCP server (/etc/dhcp/dhcpd.conf)
4. Sets up TFTP root directory (/tftpboot)
5. Creates NFS exports configuration
6. Enables systemd services for DHCP, TFTP, and NFS

Why this takes 5-10 minutes:

The dependency chain is large. DRBL requires networking tools, bootloaders, compression utilities, and file system drivers. Your system downloads and installs all of these automatically.

Expected output:

Reading package lists... Done
Building dependency tree... Done
The following additional packages will be installed:
  dhcp-server tftpd-hpa nfs-kernel-server partclone syslinux grub-pc
The following NEW packages will be installed:
  drbl dhcp-server tftpd-hpa nfs-kernel-server partclone syslinux grub-pc
0 upgraded, 234 newly installed, 0 to remove, 0 not upgraded.
Need to get 89.4 MB of archives.
After this operation, 156 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://id.archive.ubuntu.com/ubuntu noble/universe amd64 drbl all 2.6.0-1 [15.2 MB]
Fetched 89.4 MB in 8s (11.2 MB/s)
Selecting previously unselected package drbl.
(Reading database ... 126,102 files and directories currently installed.)
Preparing to unpack .../drbl_2.6.0-1_all.deb ...
Unpacking drbl (2.6.0-1) ...
Setting up drbl (2.6.0-1) ...
Processing triggers for man-db (2.12.0-3ubuntu4) ...

Monitor Installation Progress

Watch for interactive prompts during installation. DRBL may ask about:

• Network interface selection: Choose your primary NIC
• DHCP configuration: Select “Yes” to let DRBL configure automatically
• Firewall settings: Allow DHCP, TFTP, and NFS through ufw

If you see prompts, answer based on your setup. Most users should accept defaults.

Step 4: Configure DRBL Server Interactively

Why Interactive Configuration Is Required

DRBL needs to know your network topology to serve PXE clients properly. The setup script detects hardware and configures DHCP, TFTP, and NFS automatically. Running configuration manually introduces errors that break client booting.

Launch the DRBL Server Setup Script

Execute this command locally (not over SSH):

sudo /opt/drbl/sbin/drblsrv -i

What the flags mean:

• /opt/drbl/sbin/drblsrv is the DRBL server setup script
• -i enables interactive mode (prompts for decisions)

Why local console access matters:

The script detects network interfaces by querying local hardware. SSH sessions can cause interface detection to fail or return wrong information. This is a common pitfall that prevents PXE boot from working.

Navigate the Configuration Prompts

The script presents several decisions. Here’s what to select and why:

Prompt 1: Network Interface for PXE

Please select network interface for PXE boot:
[1] eth0 (192.168.1.100)
[2] eth1 (192.168.100.1)
[3] wlan0 (192.168.1.105)
Enter choice [1-3]:

What to choose:

Select the interface dedicated to client traffic. If you have two NICs, choose the second one (eth1).

Why this matters:

Prompt 2: DHCP Server Configuration

Do you want DRBL to configure DHCP server? [y/N]

What to select:

Enter y (yes) and press Enter.

Why automatic configuration:

DRBL’s DHCP configuration includes complex options (option 66 for TFTP server, option 67 for boot filename). Manual configuration is error-prone. DRBL handles this correctly by default.

Warning if existing DHCP detected:

Warning: DHCP server (dhcpd) is already running. Stop it first? [y/N]

What to do:

Enter y to stop the existing DHCP service.

Why stop existing DHCP:

You cannot run two DHCP servers on the same network. They conflict and cause IP address conflicts. DRBL needs exclusive control.

Prompt 3: Linux Image Installation

Do you want to install Linux image for diskless client? [y/N]

What to select:

Enter N (no) if you only need Clonezilla for disk imaging.

Why skip Linux image:

Linux image installation adds 2GB+ of disk space for diskless clients. If you’re using Clonezilla for backup/restore only (not diskless booting), you don’t need this. Saves space and reduces complexity.

Review Configuration Summary

The script displays a summary before applying changes. Verify these key items:

• Network interface matches your selection
• DHCP server is enabled
• TFTP root directory is /tftpboot
• NFS export path is /home/partimag

If everything looks correct, press Enter to apply. The script takes 2-3 minutes to configure services.

Expected completion message:

DRBL server configuration completed successfully.
Services started: dhcpd, tftpd-hpa, nfs-kernel-server
Configuration saved to /etc/drbl/drbl.conf

Step 5: Push DRBL Configuration to Client Machines

Understanding What drblpush Does

The drblpush command sets up the diskless boot environment for client machines. It creates PXE configuration files, generates boot images, and configures NFS shares. Without this step, clients cannot boot Clonezilla over the network.

Execute DRBL Push Configuration

Run this command interactively:

sudo /opt/drbl/sbin/drblpush -i

What the command accomplishes:

1. Creates /tftpboot/pxelinux.0 directory structure
2. Generates PXE configuration files for different architectures
3. Copies boot images (vmlinuz, initrd.img) to TFTP root
4. Sets up NFS exports in /etc/exports
5. Regenerates GRUB configuration
6. Restarts TFTP and NFS services

Why interactive mode:

Interactive mode allows customization of boot options. The non-interactive version (drblpush -f) may fail on edge cases like unusual hardware or custom network configurations.

Monitor the Push Process

The script displays progress as it creates files:

[+] Creating PXE boot configuration... Done
[+] Copying boot images to /tftpboot... Done
[+] Configuring NFS exports... Done
[+] Updating /etc/exports... Done
[+] Restarting nfs-kernel-server... Done
[+] Restarting tftpd-hpa... Done
DRBL push completed successfully.

What to verify:

• All steps show “Done” without errors
• /tftpboot directory contains files (run ls -la /tftpboot)
• /etc/exports includes /home/partimag entry

Test Service Status

Confirm all services are running:

systemctl status dhcpd
systemctl status tftpd-hpa
systemctl status nfs-server

Expected output for each service:

● dhcpd.service - ISC DHCP Server
     Loaded: loaded (/lib/systemd/system/dhcpd.service; enabled)
     Active: active (running) since Wed 2026-06-03 17:15:23 WIB; 2min ago

● tftpd-hpa.service - HPA TFTP Server
     Loaded: loaded (/lib/systemd/system/tftpd-hpa.service; enabled)
     Active: active (running) since Wed 2026-06-03 17:15:24 WIB; 2min ago

● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled)
     Active: active (running) since Wed 2026-06-03 17:15:25 WIB; 2min ago

Why verify each service:

• dhcpd: Required for PXE clients to obtain IP addresses
• tftpd-hpa: Required for clients to download boot images
• nfs-server: Required for clients to access image storage

If any service shows “inactive” or “failed”, check /var/log/syslog for error details.

Step 6: Launch Clonezilla Server Interface and Perform First Backup

Starting the DRBL Console

The dcs command launches the DRBL Console menu system. This is your primary interface for Clonezilla operations.

sudo /opt/drbl/sbin/dcs

What dcs provides:

• Menu-driven interface (no command-line memorization needed)
• Beginner and expert modes
• Options for save-disk, restore-disk, save-partition, restore-partition
• Multicast cloning for multiple machines simultaneously

Why use the menu system:

The menu prevents syntax errors. Clonezilla CLI commands are complex and easy to mistype. The menu guides you through each decision with clear descriptions.

Navigate to Clonezilla Operations

From the main menu, select these options in order:

1. Clonezilla start (press Enter or type the number)
2. Beginner mode (recommended for first-time users)
3. Choose your operation:
   • savedisk = Clone entire disk to image
   • restore-disk = Restore image to disk
   • save-partition = Clone single partition
   • restore-partition = Restore single partition

Why beginner mode:

Beginner mode simplifies options and prevents dangerous mistakes. Expert mode exposes advanced parameters that can cause data loss if misconfigured.

Configure Image Storage Location

Before starting a backup, ensure /home/partimag is properly mounted:

df -h /home/partimag

Expected output:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb1        50G   10G   38G  21% /home/partimag

What to check:

• /home/partimag exists and is mounted
• Sufficient free space (Avail column)
• Correct filesystem type (ext4, NTFS, or exFAT)

Why separate storage:

You cannot store images on the same disk you’re backing up. If that disk fails, you lose both the original and the backup. Always use separate physical storage.

Execute Your First Disk Image (savedisk)

Follow these steps in the Clonezilla menu:

1. Select savedisk (save entire disk to image)
2. Choose source disk (verify by size and name)
3. Select /home/partimag as destination
4. Enter image name (use descriptive format: server-backup-2026-06-03)
5. Choose compression level (default is good balance)
6. Confirm and start cloning

Why verify source disk:

Selecting wrong disk creates image of wrong system. Check disk size matches your expectation. A 500GB disk should not be confused with a 1TB disk.

Expected progress output:

Starting disk clone...
Source: /dev/sda (500GB)
Destination: /home/partimag/server-backup-2026-06-03
Compression: gzip (level 4)
Speed: 8.5 GB/min
Estimated time: 58 minutes
[====================] 45% complete

Why compression matters:

Compression reduces image size by 30-70%. Level 4 balances speed and compression ratio. Higher levels save space but take longer.

DO NOT interrupt the process. An interrupted image is corrupted and unusable.

Troubleshooting Common Installation Issues

Problem 1: DRBL Installation Fails with Package Conflicts

Error message:

Error: The following packages have unmet dependencies:
 drbl : Depends: dhcp-server but it is not installable
        Depends: tftpd-hpa but it is not going to be installed

Root cause:

Existing DHCP or TFTP server conflicts with DRBL dependencies. Ubuntu may have different package names than expected.

Solution:

Stop and remove conflicting services before installing DRBL:

sudo systemctl stop dhcpd
sudo systemctl disable dhcpd
sudo apt remove -y isc-dhcp-server
sudo apt autoremove -y
sudo apt install -y drbl

Why this works:

Removing the old DHCP server eliminates the conflict. DRBL can then install its required version without dependency errors.

Problem 2: Clients Cannot PXE Boot (No Boot Menu Appears)

Error symptoms:

• Client shows “No bootable device”
• Client gets stuck at “PXE-E53: No boot filename received”
• Client displays DHCP timeout errors

Root cause:

Wrong network interface selected during drblsrv configuration, or DHCP service is not running.

Solution:

Re-run DRBL server setup and select correct interface:

sudo /opt/drbl/sbin/drblsrv -i

During setup:

1. When prompted for network interface, verify using ip addr show
2. Select the interface that clients can reach
3. Confirm DHCP is enabled and not blocked by firewall

Check firewall rules:

sudo ufw status
sudo ufw allow 67/udp   # DHCP
sudo ufw allow 69/udp   # TFTP
sudo ufw allow 2049/tcp # NFS

Why this fixes it:

Clients need DHCP to get IP addresses and TFTP to download boot images. Wrong interface or blocked ports prevent this communication.

Problem 3: Secure Boot Prevents Clonezilla Live from Booting

Error symptoms:

• System skips USB/CD and boots directly to hard drive
• BIOS shows “Secure Boot violation” error
• Clonezilla menu never appears

Root cause:

Using Debian-based Clonezilla Live on system with Secure Boot enabled. Debian-based versions lack signed bootloaders.

Solution:

Download Ubuntu-based Clonezilla Live instead:

1. Go to https://clonezilla.org/downloads.php
2. Select Ubuntu-based AMD64 “alternative stable” version
3. Verify GPG signature before use
4. Recreate bootable USB with new ISO

Why Ubuntu-based works:

Ubuntu-based Clonezilla includes signed bootloaders compatible with Secure Boot. Debian-based versions do not. This is documented on the official Clonezilla site.

Problem 4: Image Storage Mount Fails or Shows “Permission Denied”

Error message:

mount: /home/partimag: permission denied
or
mount: wrong fs type, bad option, bad superblock

Root cause:

Wrong filesystem type specified, missing filesystem drivers, or incorrect mount command syntax.

Solution:

Mount with auto-detection or install missing drivers:

# For NTFS drives (Windows compatibility)
sudo apt install -y ntfs-3g
sudo mount -t ntfs-3g /dev/sdX1 /home/partimag

# For exFAT drives (cross-platform)
sudo apt install -y exfat-fuse exfat-utils
sudo mount -t exfat /dev/sdX1 /home/partimag

# Let system auto-detect (usually works)
sudo mount -t auto /dev/sdX1 /home/partimag

Why ntfs-3g for NTFS:

Native NTFS support in Linux is read-only. ntfs-3g provides full read-write support that Clonezilla requires for writing images.

Problem 5: Clonezilla Server dcs Command Not Found

Error message:

bash: /opt/drbl/sbin/dcs: No such file or directory

Root cause:

DRBL installation failed or was incomplete. The dcs script exists only after successful DRBL installation.

Solution:

Verify DRBL installation and reinstall if needed:

# Check if drbl package is installed
dpkg -l | grep drbl

# If not installed, reinstall
sudo apt install --reinstall -y drbl

# Verify script exists
ls -la /opt/drbl/sbin/dcs

# Run with full path
sudo /opt/drbl/sbin/dcs

Why this happens:

Installation may have failed silently due to network issues or disk space constraints. Reinstalling ensures all files are present.

Advanced Tips for Production Deployments

Multicast Cloning for Multiple Machines

When imaging 5+ identical machines, use Clonezilla SE multicast mode. This sends one image stream to all clients simultaneously instead of separate unicast streams.

Why multicast saves time:

• Unicast: 10 machines × 1 hour each = 10 hours total
• Multicast: 10 machines simultaneously = 1 hour total
• Bandwidth reduction: 80% less network traffic

How to enable:

In the dcs menu, select “Clonezilla start” → “Expert mode” → Enable multicast option.

Automated Unattended Restore

Create custom GRUB configuration entries with ocs_prerun scripts for fully automated restores. This eliminates manual input during mass deployments.

Why automation matters:

• Reduces human error during repetitive tasks
• Enables overnight deployments without supervision
• Standardizes configuration across all machines

SSH Remote Access for Headless Servers

Enable SSH on Clonezilla Live for remote access in datacenter environments:

service ssh start
passwd user

Why SSH is useful:

Access Clonezilla remotely without physical console. Default credentials are user/live — change password immediately for security.

Regular Testing of Backups

Schedule monthly restore tests on non-production hardware. Backups are useless if restoration fails.

Why test regularly:

• Hardware ages and image formats evolve
• Catch corrupted images before you need them
• Verify your knowledge remains fresh

Security Best Practices for Clonezilla Deployments

Encrypt Image Storage with LUKS

Store image files on encrypted volumes to protect sensitive data:

sudo cryptsetup luksFormat /dev/sdX
sudo cryptsetup open /dev/sdX encrypted_backup
sudo mkfs.ext4 /dev/mapper/encrypted_backup
sudo mount /dev/mapper/encrypted_backup /home/partimag

Why encryption matters:

Image files contain complete system copies including passwords and sensitive data. Theft of imaging drive compromises entire organization.

Network Segmentation for Clonezilla Server

Isolate Clonezilla server on dedicated VLAN separate from production network.

Why isolation helps:

• Prevents unauthorized PXE boot attempts
• Limits attack surface if server is compromised
• Reduces broadcast traffic on production network

Change Default Clonezilla Live Credentials

Always change the default user/live password if using SSH access.

Why change defaults:

Default credentials are public knowledge. Attackers scan for systems with unchanged defaults.

Verify All Downloads with GPG

Always verify ISO and package signatures before use. This prevents supply chain attacks from compromised mirrors.

[su_box title=”VPS Manage Service Offer” style=”bubbles” box_color=”#000000″ radius=”10″]If you don’t have time to do all of this stuff, or if this is not your area of expertise, we offer a service to do “VPS Manage Service Offer”, starting from $10 (Paypal payment). Please contact us to get the best deal![/su_box]