Home |
Last modified: 16-06-2020 |
Clonezilla is a Debian-based, open-source cloning/imaging alternative to commercial products such as Symantec/Norton Ghost, Acronis, etc. It can be found either as a stand-alone, bootable CD, or as part of the PartedMagic Linux live CD that also includes tools like GParted to manage partitions.
What does CZ provide that a regular live distro doesn't?
Note: If a USB keydrive doesn't boot, try using the open-source and up-to-date Rufus utility to format and burn the ISO file. Alternatively, there's the HP USB Disk Storage Format Tool; As of August 2012, the latest release seems to be 2.2.3.
More information on important options (-g, -t, -j, etc.)
To create a partition on a specific start sector, use "fdisk -u /dev/sdX". cfdisk (also part of util-linux 2.19.1) only prompts for total size in MB.
By default, Clonezilla refuses to proceed. Even using the -idcs Expert option won't work.
A work-around is to delete and re-create the target partition. Maybe it's just not a good idead to restore an image to a smaller partition even if you know there's enough room:
Bunch of GRUB-related errors ("Warning! Found grub partition (/dev/sda1) file system is ext4! Not all version of grub 1 supports file system ext4!") and won't boot: "mkfs.ext4 /dev/sda1" and trying again made no difference.
FYI, partition infos as kept in /mnt/sda2/<name of partition image>/sda-pt.parted.
The image is start=2048, end=102402438, FS=ext4. "df -T" confirms that sda1 is ext4. So why the GRUB failure?
Used fdisk to mark sda1 as bootable, restored image, and rebooted: still stuck in "grub>" prompt.
Next, mkfs.ext3 /dev/sda1 and told CZ to restore: same error.
Next, wiped out MBR, CZ : same error.
Next, tried restoring Mint instead of Ubuntu: OK.
eg. used to be /dev/sda1 but, for some reason, is now /dev/sdb1 after booting Clonezilla?
Clonezilla will gladly restore the image, but Windows may not like it: "Windows failed to start. A recent hardware or software change might be the cause."
To solve this, enter the shell, and resize the target partition to match its original size thusly:
In case you need to send/receive files from the Clonezilla host to a Windows host, one of the ways is to mount a Windows partition thusly:
mount -t cifs //192.168.0.1/"C" /mnt/my.xp -o username=joe,password=mypasswd
No. I restored a Ubuntu 11.04 image in a partition marked as NTFS/HPFS, and it booted OK.
Next, I removed the boot switch for that partition, and Ubuntu booted OK anyway.
Only Windows cares that a partition be marked as bootable and its type be NTFS/HPFS.
In case you need download files from a host booted up with Clonezilla:
Alternativaly, you can compile and use the single-EXE Mongoose.
Just ignore the error, and try to connect to the Clonezilla host through SSH.
Clonezilla ships with SSH, but you must run /etc/init.d/ssh start to start it.
Make sure Clonezilla includes the driver for your network adapter, though...
lftp
To get the eth0 to receive an IP configuration from the DHCP server:
dhclient eth0
By default, Clonezilla will try to restore to the same partition (eg. /dev/sda1) and will stop if that partition doesn't exist because something happened since you cloned that partition.
Using fdisk /dev/sdaX, delete the partition, reboot, recreate the partition with the right number, restore the image
1/2, and 5 used. Chose 3, then 4: "No free sectors available"
mkdir
fdisk -l
dd if=/dev/zero of=/dev/sda bs=440 count=1
Laptop just displays "Prepare boot to OS" for a split second, then blinking cursor.
-t1 option?
Make sure the partition is typed as "NTFS" instead of "Linux" and is marked as bootable.
If you deleted a partition, just reboot and try again.
If it boots through GRUB, let Windows boot, and download and run MbrFix to put the Windows boot loader back in the MBR, effectively removing GRUB.
Alternatively, boot with Clonezilla, and try the "-t1" option ("Client restores the prebuilt MBR from syslinux").
If Windows still doesn't boot, reboot with its CD and run the "fixmbr" command.
Partclone is said to be much better than Partimage + ntfsclone.
Based on the names, it appears that PartClone is done by the same people who do Clonezilla (Steven Shaiu and the NCHC Free Software Labs in Taiwan.)
So Clonezilla is a live CD with a text-based front-end to Partclone.
Read this.
It does, when performing a disk-to-disk cloning.
When restoring a partition from a file in a second partition (source), by default, Clonezilla will restore the bootloader that it saved when making an image of a partition, although it's possible to tell it to only restore the partition and leave the MBR alone.
Here's more information on the relevant options:
-t (default: enabled) Client does not restore the MBR (Master Boot Record): Do NOT restore the MBR (Mater Boot Record) when restoring image. If this option is set, you must make sure there is an existing MBR in the current restored harddisk. Default is Yes, ie. Clonezilla will restore the MBR (where "MBR" = "bootloader")
-t1 (default: disabled) Client restores the prebuilt MBR from syslinux (For Windows only): If this option is set, the MBR is overwritten by prebuilt one which chainloads Windows. Use this option if you have to restore Windows and make it bootable, but don't have the original MBR or backup of it.
-g (default: enabled) auto Reinstall grub in client disk MBR (only if grub config exists): Causes Clonezilla Live to reinstall GRUB into the Master Boot Record of the disk if at least one partition contains GRUB config file (/boot/grub/menu.lst). The option is enabled by default and shouldn't cause any harm. However, it should be disabled if you for example have another bootloader in MBR and chainload GRUB with it.
-j1 (default: disabled) Write MBR (512 B) again after image is restored. Not OK for partition table differ: When a disk image is restored, the partition table must be updated to reflect the actual partitions in the disk. If you don't want it to happen, enable this option. Then the Master Boot Record (including the partition table) is restored again after restoring the image. Note that using this option can destroy all the data in the target drive.
-j2 (default: enabled) Clone the hidden data between MBR and 1st partition: If this option is set, the 15 hidden sectors between Master Boot Record and the first partition are restored. This area usually contains some data necessary for booting. The option is enabled by default and should be kept enabled if you are cloning a bootable disk.
-r (default: enabled): "Try to resize the filesystem to fit partition size".
Note: In the options above, depending on the context, "client = Clonezilla" or "client = target partition on which to restore image"...
Unlike previous versions of Windows, it appears that Vista/Windows7 identify each partition with a unique ID, and aren't happy when restoring images.
The solution is to start Windows, edit the Registry, head for the HKLM\System\MountedDevices\ section, remove all entries except "Default", and then save this partition using CloneZilla.
More information:
This error message can be displayed after restoring a Windows image, and the computer will enter an endless reboot cycle.
Boot with Clonezilla, enter the command prompt the first chance you have, "sudo -s" to su to root, and use fdisk to check the partitions: If the partition where you restored Windows contained Linux previously, Clonezilla may have left its ID to "Linux" instead of changing it to "NTFS/HPFS". If that's the case, use the "t" option in fdisk to change the ID, save, and reboot.
There are two other projects, but they seem abandonned:
In case Clonezilla leaves the GRUB bootloader in the MBR after restoring a Windows partition, and provided the Windows partition is marked as "active"... is GRUB able to just start Windows even though the partition obviously doesn't contain the GRUB configuration files (/boot/grub/)?
The boot parameters for Clonezilla live
Preseed options to do job after booting
Laptop BIOS displays as "USB HDD: KingstonDT 101 G2"
Quick Windows Format
Unzipped, makeboot
Boots OK
Laptop stuck as F2 to enter Setup, F12 to change boot device
Desktop: USB ZIP/FDD/CDROM ignored, boots from hard disk
Laptop BIOS displays as "USB FDD: General USB Flash Disk"
Desktop: USB ZIP/FDD/CDROM ignored, boots from hard disk. Failed updating BIOS with BIOS_R03-B0.zip_R03-B0_A_A.zip "OnBoard BIOS Not Award BIOS !"
dd if=/dev/zero of=/dev/sdb bs=512 count=1
mkfs.vfat -n linux -F 32 -v /dev/sdb1
sfdisk -c /dev/sdb 1 b (to set partition ID to W95 FAT32)
fdisk -l /dev/sdb
mkdir /mnt/usb
mount /dev/sdb1 /mnt/usb/
cd /tmp
wget -c ???? (Check http://clonezilla.org/downloads/alternative/iso-zip-files.php)
mv ???? cz.zip
(apt-get install unzip)
unzip cz.zip -d /mnt/usbcd /mnt/usb/utils/linux
bash makeboot.sh /dev/sdb1
COULD BE DUE TO NEWER PARTEd /dev/sdb1: this doesn't look like a valid FAT filesystem
parted -s /dev/sdb1 print
umount /dev/sdb1
Full Windows Format
Unzipped, makeboot
STUCK SYSLINUX 4.05
Full Windows Format
Unzipped, makeboot
syslinux -sfmar H:
STUCK SYSLINUX 4.05
Universal USB Installer 1.8.8.4
Tuxboot 39
linuxmint-12-gnome-cd-nocodecs-32bit.iso
clonezilla-live-20120127-oneiric.iso
QF = Windows Quick Format, FF = Windows Full Format
IF = Internal format
Format |
Application |
File |
Result |
QF |
UNetBootin |
Mint |
Stuck. SYSLINUX 4.03 |
QF |
UnivUSB |
Mint |
OK |
QF |
UnivUSB |
CZ |
Stuck. SYSLINUX 4.04 |
QF |
TuxBoot |
Mint |
Stuck. Blinking cursor. |
QF |
TuxBoot |
CZ |
Stuck. SYSLINUX 4.04 |
IF |
UnivUSB |
PartedMagic |
OK |
IF |
UnivUSB |
CZ |
OK |
Bottom line: