| Version | Package/CD | Comments | ||||
| 3.1.0 | CD |
-- Clonezilla Live updated to version 1.2.4-28-686 -- SystemRescueCD updated to version 1.4.0 +- Clonezilla Live updated to version 1.2.5-17-686 +- SystemRescueCD updated to version 1.5.3 - Super Grub Disk updated to version 0.9799 - Added Super Grub Disk 2 version 1.30 - Most operations are now executed through the TUI (Text User Interface) @@ -526,7 +526,7 @@ SystemRescueCD boot parameters [^]
Clonezilla Live boot parameters [^]
ocs-live About the Image file [^]One thing should be made clear about the image file: it is not a file, it is a folder, containing the actual image file and some data about the disk/partition it is associated with. So when you insert the image file name, you actually insert the folder name where the image will be saved/restored. skip Use existing /home/partimag @@ -1048,22 +1047,36 @@This option prevents Clonezilla Live from cloning your page file if you are cloning a partition containing Windows. Often the page file is big and unneeded, and skipping it may speed cloning up without causing any harm. Mind you, this option is disabled by default because sometimes the page file may be necessary. -ntfs-ok Skip checking NTFS integrity, even bad sectors (ntfsclone only) This option works only if you selected the -q option and you're cloning a NTFS partition. It prevents the integrity check of NTFS partitions and speeds the cloning process up a little. However, if the check is disabled, there is a risk that the filesystem is damaged and the image created from it is useless. +-rescue Continue reading next one when disk blocks read errors +If this option is set, Clonezilla Live continues cloning even if a read error occurs. If there is one, the disk image will be corrupted, but failing hard drives can only be cloned with this option enabled. +-fsck-src-part Check and repair source file system before saving +This option causes Clonezilla Live to check the integrity of the partition(s) to be cloned. If the filesystem of the partition is damaged, Clonezilla Live also attempts to repair it automatically. Enabling this option reduces the risk that the image contains a damaged filesystem. However, the option is disabled by default because the automatic filesystem repair attempt may cause data loss. -gm Generate image MD5 checksums -Causes Clonezilla Live to calculate MD5 checksum(s) of image(s) created. If the image cets corrupted afterwards, the checksum allows to notice the corruption before the image is restored. Mind you, calculating the checksum takes some time and slows the process down a little. +Causes Clonezilla Live to calculate MD5 checksum(s) of image(s) created. If the image gets corrupted afterwards, the checksum allows to notice the corruption before the image is restored. Mind you, calculating the checksum takes some time and slows the process down a little. -gs Generate image SHA1 checksums This option is identical to the above, but creates SHA1 checksum(s) instead of MD5. SHA1 is considered to be more accurate checksum algorithm than MD5, but MD5 is more popular. Compression method [^]--z1 gzip compression (fast with a smaller image) -z1p Use parallel gzip compression (testing), for multicore/CPU This option chooses the method which is used to compress the image while creating it. If no compression is used at all, there won't be any negative speed impact caused by compression. However, the image file size is the size of all the data backed up - for example, if you clone a 160 GB hard drive containing 60 gigabytes of data, the resulting disk image will be 60 gigabytes in size. Gzip and lzop are fast compression methods. Lzop is many times faster than gzip, but creates slightly larger images. Clonezilla Live warns that lzop requires good-quality RAM, but I (the contributor who wrote this chapter) think other compression methods require good RAM too. Bzip2 and lzma are powerful compression methods. Lzma creates a little smaller images than bzip2, and decompressing lzma-compressed images is faster than decompressing bzip2 images. But there is no free lunch: lzma compression method is very slow compared even to bzip2, which isn't fast method either. Bzip2, lzma, xz and lzip are powerful compression methods. Lzma creates a little smaller images than bzip2, and decompressing lzma-compressed images is faster than decompressing bzip2 images. But there is no free lunch: lzma compression method is very slow compared even to bzip2, which isn't fast method either. Lzma method is becoming obsolete, and both xz and lzip are attempting to become its successor. They are a bit less powerful compression methods than lzma, but much faster. The differences between xz and lzip are virtually non-existent. If you don't use the i486 version of Clonezilla-SysRescCD and your processor contains multiple cores and/or supports Hyper-Threading, parallel gzip, bzip2, xz and lzip compression methods are also available. Parallel compression means that each processor core compresses a different part of the image at a time. Without parallel compression one core compresses everything. The speed impact caused by parallel compression depends on the number of processor cores available. In addition, Hyper-Threading increases the speed by about 30 % if parallel compression is used. For example, if your processor contains four cores and supports Hyper-Threading, speed with parallel compression is nearly 5,2 times as high as without. However, parallel compression is currently an experimental feature. This option (command line: -i [number]) decides if the created image files are splitted into smaller pieces, and if yes, how large the pieces are. This setting doesn't usually matter, but some filesystems (most importantly FAT32) don't allow files larger than four gigabytes. If you're saving the disk image to a FAT32 partition, enter 4000 or less. (Value 0 disables splitting, so don't use it in that case.) If the filesystem allows files big enough, enter any value which isn't too small (you don't want to split the image into too many pieces, do you?) Clonezilla Live warns that it is no longer safe to disable splitting because value 0 can confuse init. I (the contributor) don't know what the warning exactly means and haven't been able to reproduce the problem. Anyway, entering a very big value, for example 999999999999, is a safe way to keep the image in one piece. -p true Do nothing when the clone finishes This option is useful if you are cloning a small disk to larger one. It tries to resize the restored filesystem to the size of the partition where it was restored to. It allows you to use the whole size of your new disk without resizing the partition afterwards. The option requires that the disk where the image is copied already contains a partition where the image is restored or that the option -k1 is enabled. -e sfdisk uses the CHS value of hard drive from the saved image Force to use the saved CHS (cylinders, heads, sectors) when using sfdisk. Of cource, there is no use of it when using any of -j0, -k or -k2 options. -icrc Ignore CRC checking of partclone This option causes partclone to skip checking the CRC32 checksums of the image. Enabling this option speeds the restore process up. However, if this option is enabled and the -cm and -cs options are disabled, there is no way to notice if the image has corrupted. -j1 Write MBR (512 B) again after image is restored. Not OK for partition table diffe 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 Clone the hidden data between MBR and 1st partition -j0 Use dd to create partition (NOT OK if logical drives exist) Use dd to dump the partition table from saved image instead of sfdisk. When I use clonezilla to clone M$ windows, there is no any problem when saving an image from template machine. However, after the image is restored to another machine, it fails to boot, the error message is "Missing Operating System". What's going on ? When I use clonezilla to clone M$ windows, there is no any problem when saving an image from template machine. However, after the image is restored to another machine, it fails to boot, the error message is "Missing Operating System". What's going on ? chkdsk /f X: where X: is the drive letter of the disk. When done, boot back into Clonezilla Live and repeat the backup procedure. If the disk/partition you are trying to backup is not the Windows System disk (usually C:), you can boot Windows, and execute the command in a DOS window. To open a DOS window click Start / Run... and at the prompt Open: type cmd. If the Windows version you use is not XP and you're trying to backup the Windows System drive, boot into SystemRescueCD (graphical mode is not needed) and run the following command: ntfsfix /dev/hda1 where /dev/hda1 is the partition name in GNU/Linux. When done, boot back into Clonezilla Live and repeat the backup procedure. If Windows XP Recovery Console is not available, you don't have the time to execute the procedure described above, or even if you have executed it but you still get the same message, and you are absolutely sure that you get this message because the NTFS partition is really scheduled for check, and it's not because Windows crushed or have become corrupt, you can mount the patririon by hand and tell Clonezilla Live to use it. Assuming the partition is /dev/hda1, exit the program and execute the commands: sudo su - sudo su - to reboot the system. What if you don't have a spare local disk or partition or a USB disk? How will you be able to get a backup of your system? Well, if your PC is on the same LAN with another PC running Windows (or linux), you can use Samba to save your image file on that remote PC (which we will call Samba server from now on). We read at http://us1.samba.org/samba/: If you need to change these settings, go to the Getting backups page for instructions . Screen "Start Clonezilla" [^]-I select "Start Clonezilla" and press ENTER. +
Screen "Clonezilla" [^]-I select "device-image" and press ENTER. -Screen "Mount clonezilla image directory" [^+
Screen "Mount clonezilla image directory" [^]In this screen I can select the way the image file directory will be saved.
Available options are local directory, remote directory through ssh, samba or nfs and skip, to use the previously used directory. More info about the image file can be found at section "About the Image file". Screen "Mount Samba Server" [^]-This is where I have to enter the IP address of my Samba server. This is where I have to enter the IP address of my Samba server. Screen "Mount Samba Server" (second time) [^]-This is where I have to enter the account (user) name on my Samba server. This is where I have to enter the domain name on my Samba server. Screen "Mount Samba Server" (third time) [^]-This is where I have to enter the domain name on my Samba server. This is where I have to enter the account (user) name on my Samba server. Screen "Mount Samba Server" (fourth time) [^]-This is where I have to enter the directory name on my Samba server, in which the image file will be saved. This is where I have to enter the directory name on my Samba server, in which the image file will be saved. Screen "Clonezilla - Opensource Clone System (OCS)" [^]-I select Beginner mode to accept the default backup options. If you select Expert mode, you can choose the options yourself. More details can be found here. -Screen "Clonezilla: Select mode" [^]-Here I can select the desired operation. Available options are: -savedisk I select "saveparts" and press ENTER. Screen "Clonezilla - Opensource Clone System (OCS) | Mode: saveparts" [^]-This is the name of the image file. You can insert anything you like, as long as it makes sence to you, so that you can distinguish the image file afterwards. Next screen [^]-Here I can select the partition that will be backed up. Rebooting the system [^]-When the backup is done, I get the following: -(0) Poweroff Then I press ENTER and get to the shell. I execute the commands: +
Screen "Select mode" [^]+Here I can select the desired operation. Next Screen [^]+
Next Screen [^]+
Starting the backup [^]+
sudo su - to reboot the system. @@ -3187,7 +3215,7 @@
|
+
