--- trunk/www/2doc/README.txt 2010/05/26 10:24:27 60 +++ trunk/www/2doc/README.txt 2010/06/01 13:23:50 75 @@ -342,7 +342,7 @@ SystemRescueCD boot parameters **************************************** [[ info.png ]] -The following info applies to SystemRescueCD v. 1.5.4. In case +The following info applies to SystemRescueCD v. 1.5.5. 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 {{ http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}" @@ -370,7 +370,7 @@ The boot parameters you can use are: General boot options -Press to add additional options. +Press to add additional options (in SystemRescueCd-1.5 and more recent) * docache: causes the CD-ROM will be fully loaded into memory. A slower start but once complete, programs start faster and the CD drive will be @@ -378,12 +378,9 @@ to cache everything (including the 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 - * setkmap=kk: which defines the keymap to load where kk (example: setkmap=de -for German keyboards) +for German keyboards). This way you won't be prompted for the keyboard +configuration during the boot. * root=/dev/xdnp: the root= option boots an existing linux system. For example, if you have linux Gentoo installed on /dev/sda6, use rescuecd root=/dev/sda6 to start it. Keep in mind that you must use a @@ -438,11 +435,11 @@ Hardware, drivers and troubleshooting options * dodebug: Enables verbose messages in linuxrc -* doload=xxx: loads needed modules, multiple occurrences are permitted -(example: doload=3c59x) -* noload=xxx: prevents loading modules, multiple occurrences are permitted -(example: noload=3c59x). Use this option if you have a problem when the -system loads a particular module. +* doload=xxx: loads needed kernel modules, multiple comma separated +occurrences are permitted (example: doload=3c59x,e1000) +* noload=xxx: prevents loading kernel modules, multiple comma separated +occurrences are permitted (example: noload=3c59x,e1000). Use this option +if you have a problem when the system loads a particular module. * nonet: this will disable the network auto detection at startup * scandelay=x: pauses x seconds during the startup to allow slow devices @@ -484,8 +481,18 @@ these two partitions. Network configuration and remote access +* nonm: to disable the Network-Manager service that conflicts with the +standard network command line tools such as ifconfig and ip. You can use +this option if you want to configure the network using these commands. This +option is not necessary when SystemRescueCd is booting from the network +since the service is automatically stopped in that case. This option +requires SystemRescueCd-1.5.5 or more recent. * dodhcp: to request a DHCP server provide network attributes including -an IP address, gateway... . otherwise, +an IP address, gateway... +* nodhcp: never run the dhcp client in the initramfs boot +script. May be useful if you use PXE boot on a computer with +several ethernet interfaces. Support for this option is available in +SystemRescueCd-1.5.5-beta2 and more recent * ethx=ipaddr/cidr: Sets the static IP address of all the ethernet interfaces on the system. The /cidr extension is optional. For instance, if you use option ethx=192.168.0.1 on a machine with two ethernet adapters, @@ -522,7 +529,12 @@ is using which mac address on a machine with two network interfaces: 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). +marks between the name and the mac address). You can also use the magic +keyword BOOTIF with SystemRescueCd-1.5.4 and more recent when you boot from +pxelinux. The pxeboot loader will set BOOTIF to the name of the interface +used to boot. You can then use something like nameif=eth0!BOOTIF if you +want the boot interface to be called eth0 on a computer with several +Ethernet interfaces. Network boot using PXE SystemRescueCd provides several options for booting from the network @@ -1241,14 +1253,12 @@ 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!!! +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 @@ -1334,9 +1344,22 @@ 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 +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. @@ -1347,12 +1370,20 @@ > Compression method +-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 @@ -1368,10 +1399,29 @@ 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 @@ -1384,6 +1434,12 @@ 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 @@ -1477,6 +1533,12 @@ 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 @@ -1616,18 +1678,19 @@ 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: -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 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 @@ -1651,8 +1714,8 @@ Intro **************************************** In this page I will demonstrate the creation of an image file by getting -a backup of a virtual partition (/dev/hdb1). The image file will be saved -in another virtual partition (/dev/hda1). +a backup of a virtual partition (/dev/sdb1). The image file will be saved +in another virtual partition (/dev/sda1). The first thing you do when you want to get a backup of a disk/partition, is make sure both the souce (to be backed up) and target (to hold the @@ -1666,7 +1729,7 @@ Having done all of the above, I am ready to boot from Clonezilla-SysRescCD. [[ info.png ]] -The following pressentation has been made usingClonezilla Live v 1.2.3-27 +The following pressentation has been made usingClonezilla Live v 1.2.5-17 Getting the backup **************************************** @@ -1744,14 +1807,14 @@ at the root directory of the selected partition. [[ backup-06.png ]] -I select partition hda1 and press ENTER. +I select partition sda1 and press ENTER. [[ backup-07.png ]] and then ENTER again. [[ backup-08.png ]] This screen displays the mounting result. -As we can see, /dev/hda1 has been successfully mounted under /tmp/local-dev. +As we can see, /dev/sda1 has been successfully mounted under /tmp/local-dev. Next Screen --------------------- @@ -1771,7 +1834,7 @@ --------------------- [[ backup-11.png ]] In this screen I select the image name. -I type "Backup_5-2010_hdb", which in my opinion is more informative name +I type "Backup_22-2010_sdb", which in my opinion is more informative name than the default. Next Screen @@ -1791,8 +1854,14 @@ After that, the backup begins [[ backup-15.png ]] -and when it's successfully completed, I will be able to reboot the system -by pressing 1 and ENTER. +and when it's successfully completed, I press ENTER to get to the +shell. Then, I execute the commands: +sudo su - +cd +umount -a +reboot + +to reboot the system. @@ -1813,10 +1882,10 @@ file there. Then you can boot that PC using SystemRescueCD and create a restore DVD. -In this page I will demonstrate the creation of an image file by getting a -backup of my Windows partition (/dev/hda1). The image file will be save in -my Samba server which is my laptop (ip: 10.0.0.2, Windows share resource -name: data). +In this page I will demonstrate the creation of an image file by getting +a backup of my second disk (/dev/sdb). The image file will be save in my +Samba server which is my laptop (ip: 10.0.0.3, Windows share resource name: +all_my_images). What is Samba? --------------------- @@ -1869,103 +1938,103 @@ Screen "Start Clonezilla" --------------------- +[[ backup-03.png ]] I select "Start Clonezilla" and press ENTER. Screen "Clonezilla" --------------------- +[[ backup-04.png ]] 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". +[[ backup-smb-05.png ]] I select "samba server" and press ENTER. Screen "Mount Samba Server" --------------------- -This is where I have to enter the IP address of my Samba server. I type -"10.0.0.2" and press ENTER. +This is where I have to enter the IP address of my Samba server. +[[ backup-smb-06.png ]] +I type "10.0.0.3" and press ENTER. Screen "Mount Samba Server" (second time) --------------------- -This is where I have to enter the account (user) name on my Samba server. I -type "spiros" and press ENTER. +This is where I have to enter the domain name on my Samba server. +[[ backup-smb-07.png ]] +I just press ENTER, as there is no domain in my LAN. If there is a domain +in your network, you have to type its name (something like my_company.com) +and press ENTER. Screen "Mount Samba Server" (third time) --------------------- -This is where I have to enter the domain name on my Samba server. I select -"Cancel" and press ENTER, as there is no domain in my LAN. If there -is a domain in your network, you have to type its name (something like -my_company.com) and press ENTER. +This is where I have to enter the account (user) name on my Samba server. +[[ backup-smb-08.png ]] +I type "spiros" and press ENTER. 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. I type "/data" and press ENTER. - -At this point I will be asked for the password for user spiros. I will be -able to continue only after entering it correctly. +This is where I have to enter the directory name on my Samba server, in +which the image file will be saved. I type "/all_my_images" and press ENTER. +[[ backup-smb-09.png ]] + +At this point I'm informed I'm going to be asked for the password for +user spiros. +[[ backup-smb-10.png ]] +I will be able to continue only after entering it correctly. +[[ backup-smb-11.png ]] Screen "Clonezilla - Opensource Clone System (OCS)" --------------------- -I select Beginner mode to accept the default backup options. If you select +[[ backup-09.png ]] +I select Beginer 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" +Screen "Select mode" --------------------- -Here I can select the desired operation. Available options are: - -savedisk - Save entire disk to image - -restoredisk - Restore entire disk from image - -saveparts - Save partition to image - -restoreparts - Restore partition from image - -recovery-iso-zip - Create an automated restore CD/DVD/USB drive +Here I can select the desired operation. -I select "saveparts" and press ENTER. +[[ backup-10.png ]] +I select "savedisk" and press ENTER. -Screen "Clonezilla - Opensource Clone System (OCS) | Mode: saveparts" +Next Screen --------------------- -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. +[[ backup-11.png ]] +In this screen I select the image name. +I type "Backup_22-2010_sdb", which in my opinion is more informative name +than the default. -I insert "win_img" and press ENTER. +Next Screen +--------------------- +[[ backup-12.png ]] +Finally I am asked to select the partition to save. +I just press ENTER again. -Next screen +Starting the backup --------------------- -Here I can select the partition that will be backed up. I select "( ) -hda1 ntfs" by pressing SPACE and press ENTER, and ENTER again. +[[ backup-13.png ]] +Then the program will display the command that will be executed and will +ask me to press ENTER. +Then I will be asked to confirm the operation by pressing y and ENTER. -Then a message is displayed asking for confirmation in order to continue. I -just press y, and the backup procedure begins. +[[ backup-14.png ]] +After that, the backup begins -Rebooting the system -**************************************** -When the backup is done, I get the following: -(0) Poweroff -(1) Reboot -(2) Enter command line prompt -(3) Start over -[2] -Then I press ENTER and get to the shell. I execute the commands: +[[ backup-15.png ]] +and when it's successfully completed, I press ENTER to get to the +shell. Then, I execute the commands: sudo su - cd umount -a reboot +to reboot the system. + @@ -2584,15 +2653,16 @@ Finally, add the image file to the disc: -growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" --publisher "Your Name" --graft-points /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb +growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" \ +--publisher "Your Name" -graft-points \ +/Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb Note: In the command replace Your Name with anything you want to be the publisher ID of the disc. If you don't want the disc to have any publisher ID, run this command instead: -growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" -graft-points -/Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb +growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" \ +-graft-points /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb [[ restore-20.png ]]