--- trunk/www/onepage.html 2010/03/26 15:21:13 38 +++ trunk/www/onepage.html 2010/05/31 18:11:36 70 @@ -72,8 +72,8 @@
-Installation package: create-clonezilla-sysresccd-3.1.0.tar.gz [~ 1.7 MB]
-ISO file: clonezilla-sysresccd-full-mod-3.1.0.iso [~ 366 MB]
+Installation package: create-clonezilla-sysresccd-3.1.0.tar.gz [~ B]
+ISO file: clonezilla-sysresccd-full-mod-3.1.0.iso [~ B]
md5sum file: md5sum.txt
ISO file md5sum:
-The following info applies to SystemRescueCD v. 1.3.5. In case +The following info applies to SystemRescueCD v. 1.5.4. In case you need to get info for a more recent version of SystemRescueCD please see the page "Sysresccd-manual-en Booting the CD-ROM" |
The kernel used is rescuecd, and anything after the word append is a boot parameter.
Available kernels (boot images):
The boot parameters you can use are:
General boot options
-xx
with your keymap (for example: setkmap=de
for german keyboards)
-docache
option requires 400MB of memory if you want to cache everything (including the bootdisks
and isolinux
directories). You can add the lowmem
option if you have less that 400MB of memory of to prevent these directories to be copied into memory.
-/dev/sda6
, you can type rescuecd root=/dev/sda6
and Gentoo Linux will be started instead of the system that is on the CD-ROM. Keep in mind that you must use a 64bits kernel if your system is made of 64bits programs. For instance, you can boot a 64bits linux system installed on /dev/sda6 with rescue64 root=/dev/sda6
. From SystemRescueCd-1.0.4, this option works with LVM disks, so you can write something like rescuecd root=/dev/VolGroup00/LogVol00
. SystemRescueCd-1.0.4 and newer versions also supports root=auto
, that will scan all the block devices of the computer to find a linux system. The first linux system found on the disks will be started. So with root=auto
let you start the system installed from the CD-ROM in case you have problem with your boot loader or with your kernel for instance. You can have more details about that option.
-initscript=samba:start
. This does the same thing as /etc/init.d/samba start
. You can use this option several times with different services. All the action that are supported by an initscript can be used. This option is available with SystemRescueCd-1.0.2 and newer.
-backstore=off
on the boot command line. If you want to save your backing-store file on an harddisk, you will have to boot with backstore=alldev
so that it scans all devices not just removable devices. The default place for backing-stores file is any file named sysrcd.bs
located at the root of a disk which is often an USB key. You can change the path by using an option such as backstore=/sysrcd/mybackstore.bs
and then sysresccd will try to find a file named mybackstore.bs
located in /sysrcd
in any block-device (partition, USB-stick, ...). You can find more information about on the page about backing-stores.
+General boot options
+Press <TAB> to add additional options. +
+bootdisks
and isolinux
directories). Add lowmem
if you have less that 400MB of memory of to prevent these directories to be copied.
+During boot you will be prompted for the keyboard configuration, avoid this by using +
+kk
(example: setkmap=de
for German keyboards)
+/dev/sda6
, use rescuecd root=/dev/sda6
to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use rescuecd root=/dev/VolGroup00/LogVol00
. Support is also provided for root=auto
, which scans all the block devices tfor a linux system. The first linux system found will be started. So with root=auto
let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its filesystem label
or filesystem uuid
. If the label of the partition where linux is installed is mylinux
, then boot it using rescuecd root=LABEL=mylinux
. Similarly root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7
. See more details.
+initscript=samba:start
. This does the same thing as /etc/init.d/samba start
. Use this option multiple times for different services. All the actions that are supported by an initscript can be used.
+backstore=off
on the boot command line. If you want to save your backing-store file on an harddisk, boot with backstore=alldev
to scan all devices (not just removable devices). The default location for backing-stores file is any file named sysrcd.bs
located at the root of a disk which is often an USB stick. Change the path by using backstore=/sysrcd/mybackstore.bs
. See backing-stores.
+systemrescuecd-x86-x.y.z.iso
on a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescuecd/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its sysrcd.dat
file is in an ISO and not directly on the partition. For that reason, this isoloop=xxx
boot option is required so you must use it in your grub.cfg
. This option is only supported in SystemRescueCd-1.4.0 and more recent. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It's important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on /boot
and if you copy this ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso
then the option has to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso
. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read the section about isoloop for more details.
+
Hardware, drivers and troubleshooting options
doload=3c59x
)
+noload=3c59x
). Use this option if you have a problem when the system loads a particular module.
+noxdetect
that was useful in previous versions.
+startx
command will load the Xvesa
server instead of Xorg
, and use the screen resolution given as parameter (eg: 1024x768
, 1280x1024x32
).
Hardware, drivers and troubleshooting options
noxdetect
that was useful in previous versions.
-doload=3c59x
)
-noload=3c59x
). Use this option if you have a problem when the system loads a particular module at boot time.
-startx
by hand to get it.
-startx
command will load the Xvesa
server instead of Xorg
, and Xvesa will use the screen resolution given as parameter (eg: 1024x768
, 1280x1024x32
). The forcevesa
option can take a parameter from SystemRescueCd-1.0.0 and more recent.
-rescuecd all-generic-ide
)
-skipmount=/dev/sda1 skipmount=/dev/sda2
if you want SystemRescueCd to ignore these two partitions. This boot option requires SystemRescueCd-1.0.1 or more recent.
-rescuecd all-generic-ide
)
+
Network auto-configuration and remote access
dodhcp
if you have a DHCP server on your network and you want the system to get a dynamic IP address at boot time.
-/cidr
extension is optional. For instance, if you use option ethx=192.168.0.1
on a machine with two ethernet adapters, both eth0
and eth1
will be configured with 192.168.0.1
. You can also write something like ethx=10.0.0.1/24
(using the cidr notation) if you don't use the default netmask.
-ethx=ipaddr/cidr
but it configures only one interface at a time. Of course, you can use the eth0=ipaddr/cidr option it for all the ethernet interfaces, not just eth0. For instance if you want to configure the network on a server that has two interfaces, you can write something like this: eth0=192.168.10.1/24 eth1=192.168.20.1
. This option requires SystemRescueCd-1.0.2 or newer.
+skipmount=/dev/sda1 skipmount=/dev/sda2
to ignore these two partitions.
+
Network configuration and remote access
/cidr
extension is optional. For instance, if you use option ethx=192.168.0.1
on a machine with two ethernet adapters, both eth0
and eth1
will be configured with 192.168.0.1
. You can use the format ethx=10.0.0.1/24
(using the cidr notation) if you don't use the default netmask.
+ethx=ipaddr/cidr
but it configures only one interface at a time. To configure the network on a server that has two interfaces, use: eth0=192.168.10.1/24 eth1=192.168.20.1
.
dns=192.168.0.254
means that you want to use 192.168.0.254
as the DNS server.
gateway=192.168.0.254
means that the computer can connect to a computer outside of the local network via 192.168.0.254
.
1234
. That way you can connect from the network and ssh on the livecd and give 123456
password as the root password.
-x
with the number of displays you want, and 123456
with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the vncserver=2:MyPaSsWd
option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.
-nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64
. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address).
+x
with the number of displays you want, and 123456
with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the vncserver=2:MyPaSsWd
option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.
+nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64
. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address).
+
Network boot using PXE
SystemRescueCd provides several options for booting from the network using PXE.
+These options can be combined with other network boot options such as ethx
(cf previous section). See PXE network booting to get a global overview of SystemRescueCd and PXE and Manage remote servers using PXE.
+
The second stage downloads the kernel + initramfs using DHCP/TFTP. +
The third stage of the PXE boot process acquires the root files system. +
Several protocols are available. +
+sysrcd.dat
. Only NFSv3 can be used, NFSv4 is not supported. NFS it allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, the connection is required or you will loose the access to the root file system.
+sysrcd.dat
on ip:port. NBD is easier to configure than NFS (only one TCP port involved) and it allows computers with smaller memort to boot SystemRescueCd from the network. After the boot process, the connection is required the access to the root system.
Options provided by the autorun
/dev/sda1
), an nfs share (nfs://192.168.1.1:/path/to/scripts
), a samba share (smb://192.168.1.1/path/to/scripts
), or an http directory (http://192.168.1.1/path/to/scripts
).
-autoruns=0,2,7
then the following autorun scripts will be executed: autorun0
, autorun2
, autorun7
. Use autoruns=no
to disable all the autorun scripts with a number.
+For information on activating speakup, see the speakup info page. +
+
Options provided for autorun
/dev/sda1
), an nfs share (nfs://192.168.1.1:/path/to/scripts
), a samba share (smb://192.168.1.1/path/to/scripts
), or an http directory (http://192.168.1.1/path/to/scripts
).
+autoruns=0,2,7
the autorun sc autorun0
, autorun2
, autorun7
are run. Use autoruns=no
to disable all the autorun scripts with a number.
/var/autorun/tmp
after execution
autorun
script will not be executed
-The following info applies to Clonezilla Live v. 1.2.3-27 +The following info applies to Clonezilla Live v. 1.2.5-17 In case you need to get info for a more recent version of Clonezilla Live please see the page "The boot parameters for Clonezilla live" |
The kernel used is vmlinuz, and anything after the word append is a boot parameter.
The following info comes from the page titled The boot parameters for Clonezilla live.
-This is the manual of live-initramfs
+live-initramfs(7) ================= Name @@ -727,78 +768,79 @@ aufs, for Debian like systems to boot from. You probably do not want to install this package onto a non-live system, although it will do no harm. -live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper]. -casper was originally written by Tollef Fog Heen <tfheen@canonical.com> -and Matt Zimmerman <mdz@canonical.com>. +live-initramfs is a fork of casper. +casper was originally written by Tollef Fog Heen <tfheen@canonical.com> +and Matt Zimmerman <mdz@canonical.com>. Boot options ------------ Here is the complete list of recognized boot parameters by live-initramfs. - access=*ACCESS*:: + access=*ACCESS*:: Set the accessibility level for physically or visually impared users. ACCESS must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor difficulties. - console=*TTY,SPEED*:: + console=*TTY,SPEED*:: Set the default console to be used with the "live-getty" option. Example: "console=ttyS0,115200" - debug:: + debug:: Makes initramfs boot process more verbose. - fetch=*URL*:: + fetch=*URL*:: Another form of netboot by downloading a squashfs image from a given url, copying to ram and booting it. - hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*:: + hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*:: Those parameters lets you override values read from the config file. - ignore_uuid + ignore_uuid Do not check that any UUID embedded in the initramfs matches the discovered medium. live-initramfs may be told to generate a UUID by setting LIVE_GENERATE_UUID=1 when building the initramfs. - integrity-check:: + integrity-check:: If specified, an MD5 sum is calculated on the live media during boot and compared to the value found in md5sum.txt found in the root directory of the live media. - ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF] - [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***:: + ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]: + [DEVICE]:[AUTOCONF] [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]: + [DEVICE]:[AUTOCONF]]***:: Let you specify the name(s) and the options of the interface(s) that should be configured at boot time. Do not specify this if you want to use dhcp (default). It will be changed in a future release to mimick official kernel boot param specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp). - ip[=**frommedia**]:: + ip[=**frommedia**]:: If this variable is set, dhcp and static configuration are just skipped and the system will use the (must be) media-preconfigured /etc/network/interfaces instead. - {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**, - {kvariant|console-setup/variantcode}=**VARIANT**, - {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**:: + {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**, + {kvariant|console-setup/variantcode}=**VARIANT**, {kmodel|console-setup/modelcode}= + **CODE**, koptions=**OPTIONS**:: Configure the running keyboard as specified, if this one misses live-initramfs behaves as if "keyb=us" was specified. It will be interfered from "locale=" if locale is only 2 lowecase letters as a special case. You could also specify console layout, variant, code, and options (no defaults). - live-getty:: + live-getty:: This changes the auto-login on virtual terminals to use the (experimental) live-getty code. With this option set the standard kernel argument "console=" is parsed and if a serial console is specified then live-getty is used to autologin on the serial console. - {live-media|bootfrom}=**DEVICE**:: + {live-media|bootfrom}=**DEVICE**:: If you specify one of this two equivalent forms, live-initramfs will first try to find this device for the "/live" directory where the read-only root filesystem should reside. If it did not find something usable, the normal scan for block devices is performed. - {live-media-encryption|encryption}=**TYPE**:: + {live-media-encryption|encryption}=**TYPE**:: live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase, useful to build paranoid live systems :-). TYPE supported so far are "aes" for loop-aes encryption type. - live-media-offset=**BYTES**:: + live-media-offset=**BYTES**:: This way you could tell live-initramfs that your image starts at offset BYTES in the above specified or autodiscovered device, this could be useful to hide the Debian Live iso or image inside another iso or image, to create "clean" images. - live-media-path=**PATH**:: + live-media-path=**PATH**:: Sets the path to the live filesystem on the medium. By default, it is set to '/live' and you should not change that unless you have customized your media accordingly. - live-media-timeout=**SECONDS**:: + live-media-timeout=**SECONDS**:: Set the timeout in seconds for the device specified by "live-media=" to become ready before giving up. - {locale|debian-installer/locale}=**LOCALE**:: + {locale|debian-installer/locale}=**LOCALE**:: Configure the running locale as specified, if not present the live-media rootfs configured locale will be used and if also this one misses live-initramfs behave as "locale=en_US.UTF-8" was specified. If only 2 lowercase letter are specified @@ -806,41 +848,41 @@ case if also "keyb=" is unspecified is set with those 2 lowercase letters (keyb=us). Beside that facility, only UTF8 locales are supported by live-initramfs. - module=**NAME**:: + module=**NAME**:: Instead of using the default optional file "filesystem.module" (see below) another file could be specified without the extension ".module"; it should be placed on "/live" directory of the live medium. - netboot[=**nfs**|**cifs**]:: + netboot[=**nfs**|**cifs**]:: This tells live-initramfs to perform a network mount. The parameter "nfsroot=" (with optional "nfsopts="), should specify where is the location of the root filesystem. With no args, will try cifs first, and if it fails nfs. - nfsopts=:: + nfsopts=:: This lets you specify custom nfs options. - noautologin:: + noautologin:: This parameter disables the automatic terminal login only, not touching gdk/kdm. - noxautologin:: + noxautologin:: This parameter disables the automatic login of gdm/kdm only, not touching terminals. - nofastboot:: + nofastboot:: This parameter disables the default disabling of filesystem checks in /etc/fstab. If you have static filesystems on your harddisk and you want them to be checked at boot time, use this parameter, otherwise they are skipped. - nopersistent:: + nopersistent:: disables the "persistent" feature, useful if the bootloader (like syslinux) has been installed with persistent enabled. - noprompt + noprompt Do not prompt to eject the CD on reboot. - nosudo:: + nosudo:: This parameter disables the automatic configuration of sudo. - swapon:: + swapon:: This parameter enables usage of local swap partitions. - nouser:: + nouser:: This parameter disables the creation of the default user completely. - noxautoconfig:: + noxautoconfig:: This parameter disables Xorg auto-reconfiguration at boot time. This is valuable if you either do the detection on your own, or, if you want to ship a custom, premade xorg.conf in your live system. - persistent[=nofiles]:: + persistent[=nofiles]:: live-initramfs will look for persistent and snapshot partitions or files labeled "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to, in order: mount as /cow the first, mount the second in /home, and just copy the @@ -849,52 +891,52 @@ informations. If "nofiles" is specified, only filesystems with matching labels will be searched; no filesystems will be traversed looking for archives or image files. This results in shorter boot times. - {preseed/file|file}=**FILE**:: + {preseed/file|file}=**FILE**:: A path to a file present on the rootfs could be used to preseed debconf database. - package/question=**VALUE**:: + package/question=**VALUE**:: All debian installed packages could be preseeded from command-line that way, beware of blanks spaces, they will interfere with parsing, use a preseed file in this case. - quickreboot:: + quickreboot:: This option causes live-initramfs to reboot without attempting to eject the media and without asking the user to remove the boot media. - showmounts:: + showmounts:: This parameter will make live-initramfs to show on "/" the ro filesystems (mostly compressed) on "/live". This is not enabled by default because could lead to problems by applications like "mono" which store binary paths on installation. - textonly + textonly Start up to text-mode shell prompts, disabling the graphical user interface. - timezone=**TIMEZONE**:: + timezone=**TIMEZONE**:: By default, timezone is set to UTC. Using the timezone parameter, you can set it to your local zone, e.g. Europe/Zurich. - todisk=**DEVICE**:: + todisk=**DEVICE**:: Adding this parameter, live-initramfs will try to copy the entire read-only media to the specified device before mounting the root filesystem. It probably needs a lot of free space. Subsequent boots should then skip this step and just specify the "live-media=DEVICE" boot parameter with the same DEVICE used this time. - toram:: + toram:: Adding this parameter, live-initramfs will try to copy the whole read-only media to the computer's RAM before mounting the root filesystem. This could need a lot of ram, according to the space used by the read-only media. - union=**aufs**|**unionfs**:: + union=**aufs**|**unionfs**:: By default, live-initramfs uses aufs. With this parameter, you can switch to unionfs. - utc=**yes**|**no**:: + utc=**yes**|**no**:: By default, Debian systems do assume that the hardware clock is set to UTC. You can change or explicitly set it with this parameter. - xdebconf:: + xdebconf:: Uses xdebconfigurator, if present on the rootfs, to configure X instead of the standard procedure (experimental). - xvideomode=**RESOLUTION**:: + xvideomode=**RESOLUTION**:: Doesn't do xorg autodetection, but enforces a given resolution. Files ----- - /etc/live.conf + /etc/live.conf Some variables can be configured via this config file (inside the live system). - /live/filesystem.module + /live/filesystem.module This optional file (inside the live media) contains a list of white-space or carriage-return-separated file names corresponding to disk images in the "/live" directory. If this file exists, only images listed here will be merged into the @@ -902,7 +944,7 @@ in this file will be the "lowest" point in the aufs, and the last file in this list will be on the "top" of the aufs, directly below /cow. Without this file, any images in the "/live" directory are loaded in alphanumeric order. -/etc/live-persistence.binds + /etc/live-persistence.binds This optional file (which resides in the rootfs system, not in the live media) is used as a list of directories which not need be persistent: ie. their content does not need to survive reboots when using the persistence features. @@ -917,19 +959,20 @@ Bugs ---- Report bugs against live-initramfs -link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs]. +http://packages.qa.debian.org/live-initramfs. Homepage -------- More information about the Debian Live project can be found at -link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/] and -link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/]. +http://debian-live.alioth.debian.org/ and +http://wiki.debian.org/DebianLive/. Authors ------- -live-initramfs is maintained by Daniel Baumann <daniel@debian.org> +live-initramfs is maintained by Daniel Baumann <daniel@debian.org> for the Debian project. -live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper]. -casper was originally written by Tollef Fog Heen <tfheen@canonical.com> -and Matt Zimmerman <mdz@canonical.com>.+live-initramfs is a fork of casper. +casper was originally written by Tollef Fog Heen <tfheen@canonical.com> +and Matt Zimmerman <mdz@canonical.com>. +About Clonezilla Live [^]
@@ -974,8 +1017,7 @@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.
-Before you are able to insert the image file name, a list of partitions will be presented to you, so that you can choose where it should be saved/found. When you select one of them, it will be mounted under /home/partimag.
-This folder is very important for Clonezilla Live; the image file must be located under this directory, which means that the image file must be on the root directory of the mounted partition. So you can not, for example, create a folder called all_my_images and move all your image files in there; Clonezilla Live will not be able to find them!!!
+Before you are able to insert the image file name, a list of partitions will be presented to you, so that you can choose where it should be saved/found. When you select one of them, it will be mounted and a list of folders will be presented to you, so you can select the base image directory (first level directory within the partition), which will then be mounted under /home/partimag. This way you can, for example, create a folder called all_my_images in one of your disk partitions, and move all your image files in there; Clonezilla Live will be able to find them!!!
Another thing that should be pointed out is that only unmounted partitions will be included in the above list. This means that if you have stopped the program at some point after specifying the partition where the image file resides, and it has been mounted, it will not be present in the list the next time it is presented to you, and you will not be able to use it.
There are two things you can do in this case; either unmount the partition, as stated above, or selectskip Use existing /home/partimag
@@ -1005,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
+-z1 gzip compression (fast with a smaller image)
+-z2p Use parallel bzip2 compression (testing), for multicore/CPU
-z2 bzip2 compression (slowest but smallest image)
-z3 lzo compression (faster with image size approx. to that of gzip)(NOTE!!)
--z4 lzma compression (slowest but also small image, faster decompression than bzip2)
+-z4 lzma_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)
+-z5p Use_parallel_xz_compression_(testing),_for_multicore/CPU
+-z5 xz_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)
+-z6p Use_parallel_lzip_compression_(testing),_for_multicore/CPU
+-z6 lzip_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)
-z0 No compression (fastest but largest image size)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.
Splitting [^]
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.
Postaction [^]
-p true Do nothing when the clone finishes
-p reboot Reboot client when the clone finishes
@@ -1056,6 +1112,8 @@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
@@ -1085,7 +1143,7 @@-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.
-
We read in DRBL FAQ/Q&A: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 ?
Usually this is because GNU/Linux and M$ windows interpret the CHS (cylinder, head, sector) value of harddrive differently. Some possible solutions:
1. Maybe you can change the IDE harddrive setting in BIOS, try to use LBA instead of auto mode.
2. Try to choose
@@ -1115,10 +1173,10 @@ prompt, execute the command: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 Windows version you use is not XP, boot into SystemRescueCD (graphical mode is not needed) and run the following command: +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 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 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 -
ntfs-3g -o force /dev/hda1 /home/partimag
@@ -3144,13 +3202,13 @@
- In Clonezilla Live
Type -less /live/image/README.txt
+less /README.txt
- In SystemRescueCD
Type -less /mnt/livecd/README.txt
+less /livemnt/boot/README.txt
or -links /mnt/livecd/README.html
+links /livemnt/boot/README.html
to view the html pages in links web browser.Searching for text [^]