/[clonezilla-sysresccd]/trunk/www/2doc/README.txt
ViewVC logotype

Diff of /trunk/www/2doc/README.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 28 by sng, Wed Mar 17 23:46:34 2010 UTC revision 77 by sng, Thu Jun 17 22:25:06 2010 UTC
# Line 32  your home directory, and your USB device Line 32  your home directory, and your USB device
32  the commands:  the commands:
33    
34  umount /dev/sdc4  umount /dev/sdc4
35  dd if=~/clonezilla-sysresccd-full-mod-"myVersion".iso of=/dev/sdc4 bs=512  dd if=~/clonezilla-sysresccd-full-mod-"myVersion".iso of=/dev/sdc bs=512
36    
37  And that's it. Your usb device is ready to boot!!!  And that's it. Your usb device is ready to boot!!!
38    
39    Using the extra space
40    ---------------------
41    If your usb device is more than 400MB in size, the above command will
42    leave the remaining space unused. To verify it, execute the command:
43    
44    fdisk -l /dev/sdc
45    
46    You should get something similar to this:
47    
48    Disk /dev/sdc: 1048 MB, 1048576000 bytes
49    64 heads, 32 sectors/track, 1000 cylinders, total 2048000 sectors
50    Units = sectors of 1 * 512 = 512 bytes
51    Sector size (logical/physical): 512 bytes / 512 bytes
52    I/O size (minimum/optimal): 512 bytes / 512 bytes
53    Disk identifier: 0x77a5188f
54    
55       Device Boot  Start  End  Blocks  Id  System
56    /dev/sdc1    *      1  384  393216  17  Hidden HPFS/NTFS
57    
58    As you can see, we are currently using 348 out of 1000 cylinders of the
59    disk. The remaining disk space (~600MB) can still be used, executing the
60    following commands:
61    
62    fdisk /dev/sdc
63    command (m for help): n (create new partition)
64    command action
65     e extended
66     p primary partition (1-4)
67    p
68    partition number (1-4): 4 (create partition sdc4)
69    first cylinder (385-1000, default 385):
70    using default value 385
71    last cylinder, +cylinders or +size{k,m,g} (385-1000, default 1000):
72    using default value 1000
73    
74    command (m for help): p (display partition table)
75    
76    disk /dev/sdc: 1048 mb, 1048576000 bytes
77    64 heads, 32 sectors/track, 1000 cylinders
78    units = cylinders of 2048 * 512 = 1048576 bytes
79    sector size (logical/physical): 512 bytes / 512 bytes
80    i/o size (minimum/optimal): 512 bytes / 512 bytes
81    disk identifier: 0x77a5188f
82    
83       device boot  start   end  blocks   id  system
84    /dev/sdc1   *       1   384  393216   17  hidden hpfs/ntfs
85    /dev/sdc4         385  1000  630784   83  linux
86    
87    command (m for help): t (change partition type)
88    partition number (1-4): 4
89    hex code (type l to list codes): b
90    changed system type of partition 4 to b (w95 fat32)
91    
92    command (m for help): p (display partition table)
93    
94    disk /dev/sdc: 1048 mb, 1048576000 bytes
95    64 heads, 32 sectors/track, 1000 cylinders
96    units = cylinders of 2048 * 512 = 1048576 bytes
97    sector size (logical/physical): 512 bytes / 512 bytes
98    i/o size (minimum/optimal): 512 bytes / 512 bytes
99    disk identifier: 0x77a5188f
100    
101       device boot  start   end  blocks   id  system
102    /dev/sdc1   *       1   384  393216   17  hidden hpfs/ntfs
103    /dev/sdc4         385  1000  630784    b  w95 fat32
104    
105    command (m for help): w (write partition table to disk and exit)
106    The partition table has been altered!
107    
108    Calling ioctl() to re-read partition table.
109    
110    WARNING: Re-reading the partition table failed with error 16: Device or
111    resource busy.
112    The kernel still uses the old table. The new table will be used at
113    the next reboot or after you run partprobe(8) or kpartx(8)
114    Syncing disks.
115    
116    At this point you should disconnect and reconnect your usb device. When
117    it's recognised, you can format the partition you've just created
118    
119    mkdosfs -F 32 /dev/sdc4
120    
121    The partition is now ready for use!!!
122    
123  Installing the "hard" way  Installing the "hard" way
124  ****************************************  ****************************************
125  If the "easy" way does not work there is an alternative; you will use  If the "easy" way does not work there is an alternative; you will use
# Line 193  Disk /dev/sdc: 1031 MB, 1031798272 bytes Line 277  Disk /dev/sdc: 1031 MB, 1031798272 bytes
277  64 heads, 32 sectors/track, 983 cylinders  64 heads, 32 sectors/track, 983 cylinders
278  Units = cylinders of 2048 * 512 = 1048576 bytes  Units = cylinders of 2048 * 512 = 1048576 bytes
279    
280  Device     Boot     Start     End     Blocks     Id     System     Device  Boot  Start  End   Blocks  Id  System
281  /dev/sdc4     *     1     983     1006576     6     FAT16  /dev/sdc4     *      1  983  1006576   6  FAT16
282    
283  If the partition is not active (no astrisk), execute:  If the partition is not active (no astrisk), execute:
284  fdisk /dev/sdc  fdisk /dev/sdc
# Line 222  mode. Line 306  mode.
306  In this case you will have to format your USB disk.  In this case you will have to format your USB disk.
307    
308  If you are using linux to perform the installation, execute the command:  If you are using linux to perform the installation, execute the command:
309    
310  mkdosfs -F 16 /dev/sdc4  mkdosfs -F 16 /dev/sdc4
311    
312  to create a FAT16 file system, or  to create a FAT16 file system, or
313    
314  mkdosfs -F 32 /dev/sdc4  mkdosfs -F 32 /dev/sdc4
315    
316  to create a FAT32 file system.  to create a FAT32 file system.
317    
318  When you are done go back to section "Installation from Linux".  When you are done go back to section "Installation from Linux".
# Line 342  certainty make it unbootable. When you a Line 430  certainty make it unbootable. When you a
430  SystemRescueCD boot parameters  SystemRescueCD boot parameters
431  ****************************************  ****************************************
432  [[ info.png ]]  [[ info.png ]]
433  The following info applies to SystemRescueCD v. 1.3.5. In case  The following info applies to SystemRescueCD v. 1.5.5. In case
434   you need to get info for a more recent version of SystemRescueCD   you need to get info for a more recent version of SystemRescueCD
435  please see the page "Sysresccd-manual-en Booting the CD-ROM {{  please see the page "Sysresccd-manual-en Booting the CD-ROM {{
436  http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}"  http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}"
# Line 357  boot parameter. Line 445  boot parameter.
445    
446  Available kernels (boot images):  Available kernels (boot images):
447    
448  * rescuecd This is the default choice for 32bits systems, with Framebuffer  * rescuecd Default for 32bit systems, with Framebuffer disabled, best choice.
449  disabled, best choice.  * rescue64 Default 64 bit kernel. Use it if you want to chroot to a 64bit
450  * altker32 This is an alternative kernel for 32bits systems. Boot with  linux system installed on your hard disk, or if you have to run 64 bits
451  this kernel in case you have problems with rescuecd. altker32 was named  programs. This kernel is able to boot with 32bit programs, and it requires
452  vmlinuz2 in versions prior to SystemRescueCd-1.0.0.  a processor with 64bit instructions (amd64 / em64t).
453  * rescue64 This is the default 64 bits kernel. Use it if you want to chroot  * altker32 an alternative kernel for 32bit systems. Boot with this kernel
454  to a 64bits linux system installed on your hard disk, or if you have to run  if you have problems with rescuecd
455  64 bits programs. This kernel is able to boot SystemRescueCd from the cdrom  * altker64 an alternative kernel for 64bit systems. Boot with this kernel
456  with 32bits programs, and it required a processor with 64bits instructions  in case you have problems with rescue64.
 (amd64 / em64t).  
 * altker64 This is an alternative kernel for 64bits systems. Boot with  
 this kernel in case you have problems with rescue64. Only available from  
 SystemRescueCd-1.0.0 and newer.  
457    
458  The boot parameters you can use are:  The boot parameters you can use are:
459    
460  General boot options   General boot options
461    Press <TAB> to add additional options (in SystemRescueCd-1.5 and more recent)
 * setkmap=xx: if you don't want to be asked for the keymap, you can  
 choose which keymap to load automatically. Replace xx with your keymap  
 (for example: setkmap=de for german keyboards)  
 * docache: this option is very useful if you need to insert another disc  
 in the CD drive after booting. The CD-ROM will be fully loaded into memory,  
 and you will be able to remove the disc from the drive. The 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.  
 * root=xxx: the root=<device> option {{  
 http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/  
 }} lets you boot an existing linux system. For example, if you have a  
 linux gentoo installed on /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=service:action: This options allows you to automatically  
 start/stop a service at boot time. For instance if you need the  
 samba service to be started, you can boot with the following 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=xxx: SystemRescueCd-1.1.x  
 comes with support for the backing-stores {{  
 http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/  
 }}. Basically, a backing-store is a loopback filesystem which saves all  
 the changes you can make in SystemRescueCd when you use it. In other words  
 it allows you to save all the files which changes in SystemRescueCd while  
 you use it, so that you keep these changes the next time you boot it. By  
 default, sysresccd automatically scan all your removable devices (eg: usb  
 sticks) at boot time and uses the first backing-store it finds if there is  
 one. A backing-store is not mandatory and it the scan fails it will just  
 store the files which change in memory. To disable the disks scan at boot  
 time you can specify 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.  
   
 Hardware, drivers and troubleshooting options  
462    
463    * docache: causes the CD-ROM will be fully loaded into memory. A slower
464    start but once complete, programs start faster and the CD drive will be
465    released allowing normal access to other CDs. This requires 400MB of memory
466    to cache everything (including the bootdisks and isolinux directories). Add
467    lowmem if you have less that 400MB of memory of to prevent these directories
468    to be copied.
469    * setkmap=kk: which defines the keymap to load where kk (example: setkmap=de
470    for German keyboards). This way you won't be prompted for the keyboard
471    configuration during the boot.
472    * root=/dev/xdnp: the root=<device> option boots an existing linux
473    system. For example, if you have linux Gentoo installed on /dev/sda6,
474    use rescuecd root=/dev/sda6 to start it. Keep in mind that you must use a
475    64bit kernel if your system is made of 64bit programs. This option works
476    with LVM volumes. Use rescuecd root=/dev/VolGroup00/LogVol00. Support
477    is also provided for root=auto, which scans all the block devices tfor
478    a linux system. The first linux system found will be started. So with
479    root=auto let you start the system installed from the CD-ROM in case
480    you have problem with your boot loader or kernel. It's also possible
481    to specify a partition using its filesystem label or filesystem
482    uuid. If the label of the partition where linux is installed is
483    mylinux, then boot it using rescuecd root=LABEL=mylinux. Similarly
484    root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. See more details.
485    * initscript=service:action: This options allows start/stop a service
486    at boot time. For instance if you need the samba service to be started,
487    you can boot with: initscript=samba:start. This does the same thing as
488    /etc/init.d/samba start. Use this option multiple times for different
489    services. All the actions that are supported by an initscript can be used.
490    * backstore=xxx: SystemRescueCd comes with support for the backing-stores. A
491    backing-store saves all the changes you can make. so that you keep these
492    changes the next time you boot it. By default, sysresccd automatically
493    scan removable devices (eg: USB sticks) at boot time and uses the first
494    backing-store it finds. A backing-store is not mandatory and it the
495    scan fails it will store the files which change in memory. To disable
496    the disks scan at boot time specify backstore=off on the boot command
497    line. If you want to save your backing-store file on an harddisk, boot with
498    backstore=alldev to scan all devices (not just removable devices). The
499    default location for backing-stores file is any file named sysrcd.bs
500    located at the root of a disk which is often an USB stick. Change the path
501    by using backstore=/sysrcd/mybackstore.bs. See backing-stores.
502    * isoloop=xxx: Grub2 (currently in development: grub-1.98) provides a new
503    feature to boot from an ISO image which is stored from the hard disk. If you
504    put a copy of systemrescuecd-x86-x.y.z.iso on a partition that Grub2 can read
505    then you can boot SystemRescueCd directly from the ISO image stored on your
506    hard drive. This is very convenient if you frequently update SystemRescueCd
507    and you want to boot it directly from Grub2. Grub2 knows what an ISO image
508    is and it will load the kernel image (rescuecd/rescue64) and the initramfs
509    (initram.igz) from the ISO into memory. It will then do its normal job and
510    execute the kernel. The SystemRescueCd init script must then be aware that
511    its sysrcd.dat file is in an ISO and not directly on the partition. For that
512    reason, this isoloop=xxx boot option is required so you must use it in your
513    grub.cfg. This option is only supported in SystemRescueCd-1.4.0 and more
514    recent. This option specifies the path of the ISO image in the partition that
515    grub considers as its root partition. It's important to understand that the
516    path of the ISO image may be different from the path on your linux system. If
517    you have a separate boot partition mounted on /boot and if you copy this
518    ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then the option has
519    to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This is because the
520    boot partition is what Grub2 will consider as its root partition during
521    the boot process. Please read the section about isoloop for more details.
522    
523     Hardware, drivers and troubleshooting options
524    * dodebug: Enables verbose messages in linuxrc
525    
526    * doload=xxx: loads needed kernel modules, multiple comma separated
527    occurrences are permitted (example: doload=3c59x,e1000)
528    * noload=xxx: prevents loading kernel modules, multiple comma separated
529    occurrences are permitted (example: noload=3c59x,e1000). Use this option
530    if you have a problem when the system loads a particular module.
531  * nonet: this will disable the network auto detection at startup  * nonet: this will disable the network auto detection at startup
532    
533  * scandelay=x: pauses x seconds during the startup to allow slow devices  * scandelay=x: pauses x seconds during the startup to allow slow devices
534  to initialize. This is required when you boot an usb device. A delay of  to initialize. This is required when you boot an USB device. A delay of
535  only few seconds should be enough.  only few seconds should be enough.
536    
537  * doxdetect: Since version 0.3.5 the auto-configuration is done in X.Org  * doxdetect: Since version 0.3.5 the auto-configuration is done in X.Org
538  itself, and then mkxf86config is disabled by default. This option forces  itself, mkxf86config is disabled by default. This option forces the system to
539  the system to run the mkxf86config startup script to run the hardware  run the mkxf86config startup script and to run the hardware auto-detection
540  auto-detection from this script. Use this option if you have problems with  from this script. Use this option if you have problems with the graphical
541  the graphical environment configuration. This option replaces the option  environment configuration. This option replaces the option noxdetect that
542  noxdetect that was useful in previous versions.  was useful in previous versions.
543  * nodetect: prevents the generic hardware auto-detection. Use this option  * nodetect: prevents generic hardware auto-detection. Use this option if
544  if you have problems with the hardware auto-detection.  you have problems with the hardware auto-detection.
545  * doload=xxx: forces to load one/several modules at startup (example:  
546  doload=3c59x)  * dostartx: load the X.Org graphical environment.
547  * noload=xxx: prevents the system to load one/several modules at startup  * forcevesa: Forces X.Org to use the safe VESA driver instead of the best
548  (example: noload=3c59x). Use this option if you have a problem when the  video driver detected for your video card. Use this option if you cannot
549  system loads a particular module at boot time.  get the graphical environment working with the default options.
550  * dostartx: This option will force the system to load the X.Org graphical  * forcevesa=xxx: The startx command will load the Xvesa server instead
551  environment at boot time. You won't have to type startx by hand to get it.  of Xorg, and use the screen resolution given as parameter (eg: 1024x768,
552  * forcevesa: Forces X.Org to work with the safe vesa driver instead of  1280x1024x32).
553  the best video driver detected for your video card. Use this option if  
 you cannot get the graphical environment working with the default options.  
 * forcevesa=xxx: The 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.  
554  * all-generic-ide: In case of problems related to your hard disk, try to  * all-generic-ide: In case of problems related to your hard disk, try to
555  enable this option (eg rescuecd all-generic-ide)  enable this option (eg rescuecd all-generic-ide)
556  * acpi-off / noapic / irqpool: use these options if you have any problem  * nodmraid: Disable dmraid, for some motherboards with built-in RAID
557  when the kernel boots: if it hangs on a driver or if it crashes, ...  controller.
558  * dodebug: Enables verbose messages in the linuxrc script.  * nomdadm: Disable mdadm, for software RAID.
559  * lowmem: Prevents non critical things to be loaded into memory (like the  
560  sshd and nfsd services)  * acpi-off / noapic / irqpool: use these options if you have problem when
561    the kernel boots: if it hangs on a driver or if it crashes, ...
562    
563    * lowmem: For systems with smaller memory, some daemons are not started
564    including sshd and nfsd.
565    
566  * skipmount=/dev/xxx: The system mounts all the storage devices at boot  * skipmount=/dev/xxx: The system mounts all the storage devices at boot
567  time to find the sysrcd.dat file. You may not want it to mount a device,  time to find the sysrcd.dat file. If your hard disk is broken it should
568  for instance if your hard disk is broken because it would crash the  be mounted. Boot with skipmount=/dev/sda1 skipmount=/dev/sda2 to ignore
569  system. You can just boot with skipmount=/dev/sda1 skipmount=/dev/sda2 if  these two partitions.
570  you want SystemRescueCd to ignore these two partitions. This boot option  
571  requires SystemRescueCd-1.0.1 or more recent.   Network configuration and remote access
572  * nodmraid: Disable dmraid, which is the program that drives RAID disks  * nonm: to disable the Network-Manager service that conflicts with the
573  based on cheap RAID controller built-in motherboards.  standard network command line tools such as ifconfig and ip. You can use
574  * nomdadm: Disable mdadm, which is the program that drives software RAID.  this option if you want to configure the network using these commands. This
575    option is not necessary when SystemRescueCd is booting from the network
576  Network auto-configuration and remote access  since the service is automatically stopped in that case. This option
577    requires SystemRescueCd-1.5.5 or more recent.
578  * dodhcp: Use dodhcp if you have a DHCP server on your network and you  * dodhcp: to request a DHCP server provide network attributes including
579  want the system to get a dynamic IP address at boot time.  an IP address, gateway...
580  * ethx=ipaddr/cidr: Sets the static IP address of all the ethernet interfaces  * nodhcp: never run the dhcp client in the initramfs boot
581  found on the system. The /cidr extension is optional. For instance, if  script. May be useful if you use PXE boot on a computer with
582  you use option ethx=192.168.0.1 on a machine with two ethernet adapters,  several ethernet interfaces. Support for this option is available in
583  both eth0 and eth1 will be configured with 192.168.0.1. You can also write  SystemRescueCd-1.5.5-beta2 and more recent
584  something like ethx=10.0.0.1/24 (using the cidr notation) if you don't  * ethx=ipaddr/cidr: Sets the static IP address of all the ethernet
585  use the default netmask.  interfaces on the system. The /cidr extension is optional. For instance,
586  * eth0=ipaddr/cidr: This option is similar to  if you use option ethx=192.168.0.1 on a machine with two ethernet adapters,
587  ethx=ipaddr/cidr but it configures only one interface  both eth0 and eth1 will be configured with 192.168.0.1. You can use the
588  at a time. Of course, you can use the eth0=ipaddr/cidr option {{  format ethx=10.0.0.1/24 (using the cidr notation) if you don't use the
589  http://www.sysresccd.org/news/2008/04/13/new-boot-options-for-advanced-ethernet-ip-configuration/  default netmask.
590  }} it for all the ethernet interfaces, not just eth0. For instance if you  * eth0=ipaddr/cidr: This option is similar to ethx=ipaddr/cidr but it
591  want to configure the network on a server that has two interfaces, you can  configures only one interface at a time. To configure the network on a
592  write something like this: eth0=192.168.10.1/24 eth1=192.168.20.1. This  server that has two interfaces, use: eth0=192.168.10.1/24 eth1=192.168.20.1.
 option requires SystemRescueCd-1.0.2 or newer.  
593  * dns=ipaddr: Sets the static IP address of the DNS nameserver you want  * dns=ipaddr: Sets the static IP address of the DNS nameserver you want
594  to use to resolve the names. For instance dns=192.168.0.254 means that  to use to resolve the names. For instance dns=192.168.0.254 means that
595  you want to use 192.168.0.254 as the DNS server.  you want to use 192.168.0.254 as the DNS server.
# Line 504  in SystemRescueCd-1.3.5. Line 603  in SystemRescueCd-1.3.5.
603  * rootpass=123456: Sets the root password of the system running on the  * rootpass=123456: Sets the root password of the system running on the
604  livecd to 1234. That way you can connect from the network and ssh on the  livecd to 1234. That way you can connect from the network and ssh on the
605  livecd and give 123456 password as the root password.  livecd and give 123456 password as the root password.
606  * vncserver=x:123456: The vncserver boot option {{  * vncserver=x:123456: The vncserver boot option has been introduced in
607  http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/  SystemRescueCd-1.0.2. This options forces the system to configure the
608  }} has been introduced in SystemRescueCd-1.0.2. This options forces the  VNC-server and to start it automatically at boot time. You have to replace
609  system to configure the VNC-server and to start it automatically at boot  x with the number of displays you want, and 123456 with your password The
610  time. You have to replace x with the number of displays you want, and 123456  password must be between 5 and 8 characters, else the boot option will be
611  with your password The password must be between 5 and 8 characters, else the  ignored. In other words the vncserver=2:MyPaSsWd option will give you access
612  boot option will be ignored. In other words the vncserver=2:MyPaSsWd option  to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display
613  will give you access to two displays (display=1 on tcp/5901 and display=2  0 is reserved for X.Org since SystemRescueCd-1.1.0.
614  on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.  * nameif=xxx: You can can specify what interface name to give to a
615  * nameif=xxx: You can can specify what interface name to give {{  particular interface using the mac address. You need SystemRescueCd-1.1.0
616  http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/  or newer to do that. Here is how you can specify which interface
617  }} to a particular interface using the mac address. You need  is using which mac address on a machine with two network interfaces:
618  SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify  nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64. Be careful, you have
619  which interface is using which mac address on a machine with two network  to respect the separator (comma between the interfaces and exclamation
620  interfaces: nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64. Be  marks between the name and the mac address). You can also use the magic
621  careful, you have to respect the separator (comma between the interfaces  keyword BOOTIF with SystemRescueCd-1.5.4 and more recent when you boot from
622  and exclamation marks between the name and the mac address).  pxelinux. The pxeboot loader will set BOOTIF to the name of the interface
623    used to boot. You can then use something like nameif=eth0!BOOTIF if you
624    want the boot interface to be called eth0 on a computer with several
625    Ethernet interfaces.
626    
627     Network boot using PXE
628    SystemRescueCd provides several options for booting from the network
629    using PXE.
630    These options can be combined with other network boot options such as ethx
631    (cf previous section). See PXE network booting to get a global overview
632    of SystemRescueCd and PXE and Manage remote servers using PXE.
633    The second stage downloads the kernel + initramfs using DHCP/TFTP.
634    The third stage of the PXE boot process acquires the root files system.
635    Several protocols are available.
636    
637    * netboot=tftp://ip/path/sysrcd.dat: from a TFTP server. The filesystem
638    is loaded into memory. As a consequence computers with less than 400MB of
639    memory won't be able to boot this way. The system will continue to work
640    if the network is disconnected after the boot process.
641    * netboot=http://ip:port/path/sysrcd.dat: from a Web server. The file system
642    is loaded into memory. Computers with smaller memory won't be able to boot
643    this way. The the system continues to work if the network is disconnected
644    after the boot process.
645    * netboot=nfs://ip:/path: mount an NFSv3 directory. The NFS url must be
646    the path of the directory that contains sysrcd.dat. Only NFSv3 can be used,
647    NFSv4 is not supported. NFS it allows computers with smaller memory to boot
648    SystemRescueCd from the network. After the boot process, the connection
649    is required or you will loose the access to the root file system.
650    * netboot=nbd://ip:port: connect to an NBD server configured with sysrcd.dat
651    on ip:port. NBD is easier to configure than NFS (only one TCP port involved)
652    and it allows computers with smaller memort to boot SystemRescueCd from
653    the network. After the boot process, the connection is required the access
654    to the root system.
655    
656  Options provided by the autorun  For information on activating speakup, see the speakup info page.
657    
658     Options provided for autorun
659  * ar_source=xxx: place where the autorun are stored. It may  * ar_source=xxx: place where the autorun are stored. It may
660  be the root directory of a partition (/dev/sda1), an nfs  be the root directory of a partition (/dev/sda1), an nfs
661  share (nfs://192.168.1.1:/path/to/scripts), a samba share  share (nfs://192.168.1.1:/path/to/scripts), a samba share
662  (smb://192.168.1.1/path/to/scripts), or an http directory  (smb://192.168.1.1/path/to/scripts), or an http directory
663  (http://192.168.1.1/path/to/scripts).  (http://192.168.1.1/path/to/scripts).
664  * autoruns=[0-9]: comma separated list of the autorun script that have to  * autoruns=[0-9]: comma separated list of the autorun scrip to be run. For
665  be run. For instance if you use autoruns=0,2,7 then the following autorun  example autoruns=0,2,7 the autorun sc autorun0, autorun2, autorun7 are
666  scripts will be executed: autorun0, autorun2, autorun7. Use autoruns=no  run. Use autoruns=no to disable all the autorun scripts with a number.
 to disable all the autorun scripts with a number.  
667  * ar_ignorefail: continue to execute the scripts chain even if a script  * ar_ignorefail: continue to execute the scripts chain even if a script
668  failed (returned a non-zero status)  failed (returned a non-zero status)
669  * ar_nodel: do not delete the temporary copy of the autorun scripts located  * ar_nodel: do not delete the temporary copy of the autorun scripts located
# Line 545  been executed. Line 676  been executed.
676  Clonezilla Live boot parameters  Clonezilla Live boot parameters
677  ****************************************  ****************************************
678  [[ info.png ]]  [[ info.png ]]
679  The following info applies to Clonezilla Live v. 1.2.3-27  The following info applies to Clonezilla Live v. 1.2.5-17
680  In case you need to get info for a more recent version of Clonezilla Live  In case you need to get info for a more recent version of Clonezilla Live
681  please see the page "The boot parameters for Clonezilla live {{  please see the page "The boot parameters for Clonezilla live {{
682  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc
# Line 567  page titled The boot parameters for Clon Line 698  page titled The boot parameters for Clon
698  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc  http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc
699  }}.  }}.
700    
701  Clonezilla live is based on Debian live {{ http://wiki.debian.org/DebianLive/  Clonezilla live is based on Debian live with clonezilla installed. Therefore
702  }} with clonezilla installed. Therefore there are 2 kinds of boot parameters:  there are 2 kinds of boot parameters:
703    
704  * Boot parameters from live-initramfs. You can refer to this manual of  * Boot parameters from live-initramfs. You can refer to this manual of
705  live-initramfs.  live-initramfs.
# Line 579  live-initramfs. Line 710  live-initramfs.
710   ocs-live-restore or any command you write. Use the Absolute path in   ocs-live-restore or any command you write. Use the Absolute path in
711   Clonezilla live.   Clonezilla live.
712   e.g. ocs_live_run="ocs-live-general"   e.g. ocs_live_run="ocs-live-general"
713     //NOTE// You might have to use "sudo" command inside your own script,
714     or you can assign it like: ocs_live_run="sudo bash /my-clonezilla"
715   * ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore   * ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore
716   (not for ocs-live-general or any other), then it will be passed to   (not for ocs-live-general or any other), then it will be passed to
717   ocs-sr. Therefore these parameters are actually those of ocs-sr.   ocs-sr. Therefore these parameters are actually those of ocs-sr.
# Line 610  e.g. ocs_numlk=on to turn on numberlock Line 743  e.g. ocs_numlk=on to turn on numberlock
743   only. (It was also on /dev/ttyS0 before, but since Clonezilla live >=   only. (It was also on /dev/ttyS0 before, but since Clonezilla live >=
744   1.2.3-22 no more this due to a problem). If you want to use ttyS0, for   1.2.3-22 no more this due to a problem). If you want to use ttyS0, for
745   example, add live-getty and console=ttyS0,38400n81 in the boot parameter.   example, add live-getty and console=ttyS0,38400n81 in the boot parameter.
746     //NOTE//
747     * This parameter was added in Clonezilla live 1.2.3-22 or later.
748     * If "live-getty console=$tty,38400n81" are assigned in the boot parameters,
749     ocs_live_run_tty will honor $tty, even other value is assigned to
750     ocs_live_run_tty in boot parameter.
751     * It's recommended to assign ocs_lang and ocs_live_keymap in the boot
752     parameters too.
753     * ip, this option allows you to specify the network parameters for
754     network card. In Clonezilla live a patched live-initramfs is used, which
755     is different from the original live-initramfs so that you can assign
756     DNS server, too. Its format is: ip=ethernet port,IP address, netmask,
757     gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1,
758     netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can
759     assign the following in the boot parameter:
760    ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8
761    If more than one network card, you can use ":" to separate them, e.g.:
762    ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8:eth1,192.168.120.1,255.255.255.0,192.168.120.254,,
763   * Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when   * Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when
764   using PXE booting, you can force to assign the network device to get   using PXE booting, you can force to assign the network device to get
765   filesystem.squashfs. This is useful when there are two or more NICs are   filesystem.squashfs. This is useful when there are two or more NICs are
# Line 748  aufs, for Debian like systems to boot fr Line 898  aufs, for Debian like systems to boot fr
898  You probably do not want to install this package onto a non-live system,  You probably do not want to install this package onto a non-live system,
899  although it will do no harm.  although it will do no harm.
900    
901  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of casper.
902  casper was originally written by Tollef Fog Heen <tfheen@canonical.com>  casper was originally written by Tollef Fog Heen
903  and Matt Zimmerman <mdz@canonical.com>.  &lt;tfheen@canonical.com&amp;gt;
904    and Matt Zimmerman &lt;mdz@canonical.com&amp;gt;.
905    
906  Boot options  Boot options
907  ------------  ------------
# Line 796  If specified, an MD5 sum is calculated o Line 947  If specified, an MD5 sum is calculated o
947  compared to the value found in md5sum.txt found in the root directory of the  compared to the value found in md5sum.txt found in the root directory of the
948  live media.  live media.
949    
950   ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]   ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
951   [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***::   [DEVICE]:[AUTOCONF]
952     [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
953     [DEVICE]:[AUTOCONF]]***::
954    
955  Let you specify the name(s) and the options of the interface(s) that  Let you specify the name(s) and the options of the interface(s) that
956  should be  should be
# Line 817  instead. Line 970  instead.
970   {keyb|kbd-chooser/method}=**KEYBOARD**,   {keyb|kbd-chooser/method}=**KEYBOARD**,
971   {klayout|console-setup/layoutcode}=**LAYOUT**,   {klayout|console-setup/layoutcode}=**LAYOUT**,
972   {kvariant|console-setup/variantcode}=**VARIANT**,   {kvariant|console-setup/variantcode}=**VARIANT**,
973   {kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**::   {kmodel|console-setup/modelcode}=
974     **CODE**, koptions=**OPTIONS**::
975    
976  Configure the running keyboard as specified, if this one misses  Configure the running keyboard as specified, if this one misses
977  live-initramfs  live-initramfs
# Line 1060  this list will be on the "top" of the au Line 1214  this list will be on the "top" of the au
1214  this file, any images in the "/live" directory are loaded in alphanumeric  this file, any images in the "/live" directory are loaded in alphanumeric
1215  order.  order.
1216    
1217  /etc/live-persistence.binds   /etc/live-persistence.binds
1218    
1219  This optional file (which resides in the rootfs system, not in the live  This optional file (which resides in the rootfs system, not in the live
1220  media)  media)
# Line 1083  Bugs Line 1237  Bugs
1237  ----  ----
1238    
1239  Report bugs against live-initramfs  Report bugs against live-initramfs
1240  link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs].  http://packages.qa.debian.org/live-initramfs.
1241    
1242  Homepage  Homepage
1243  --------  --------
1244    
1245  More information about the Debian Live project can be found at  More information about the Debian Live project can be found at
1246  link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/]  http://debian-live.alioth.debian.org/ and
1247  and  http://wiki.debian.org/DebianLive/.
 link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/].  
1248    
1249  Authors  Authors
1250  -------  -------
1251    
1252  live-initramfs is maintained by Daniel Baumann <daniel@debian.org>  live-initramfs is maintained by Daniel Baumann &lt;daniel@debian.org&amp;gt;
1253  for the Debian project.  for the Debian project.
1254    
1255  live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper].  live-initramfs is a fork of casper.
1256  casper was originally written by Tollef Fog Heen <tfheen@canonical.com>  casper was originally written by Tollef Fog Heen
1257  and Matt Zimmerman <mdz@canonical.com>.  &lt;tfheen@canonical.com&amp;gt;
1258    and Matt Zimmerman &lt;mdz@canonical.com&amp;gt;.
1259    
1260    
1261    
# Line 1187  you actually insert the folder name wher Line 1341  you actually insert the folder name wher
1341    
1342  Before you are able to insert the image file name, a list of partitions  Before you are able to insert the image file name, a list of partitions
1343  will be presented to you, so that you can choose where it should be  will be presented to you, so that you can choose where it should be
1344  saved/found. When you select one of them, it will be mounted under  saved/found. When you select one of them, it will be mounted and a list
1345  /home/partimag.  of folders will be presented to you, so you can select the base image
1346    directory (first level directory within the partition), which will then
1347  This folder is very important for Clonezilla Live; the image file must be  be mounted under /home/partimag. This way you can, for example, create a
1348  located under this directory, which means that the image file must be on  folder called all_my_images in one of your disk partitions, and move all
1349  the root directory of the mounted partition. So you can not, for example,  your image files in there; Clonezilla Live will be able to find them!!!
 create a folder called all_my_images and move all your image files in there;  
 Clonezilla Live will not be able to find them!!!  
1350    
1351  Another thing that should be pointed out is that only unmounted partitions  Another thing that should be pointed out is that only unmounted partitions
1352  will be included in the above list. This means that if you have stopped  will be included in the above list. This means that if you have stopped
# Line 1280  speeds the cloning process up a little. Line 1432  speeds the cloning process up a little.
1432  there is a risk that the filesystem is damaged and the image created from  there is a risk that the filesystem is damaged and the image created from
1433  it is useless.  it is useless.
1434    
1435    -rescue Continue reading next one when disk blocks read errors
1436    If this option is set, Clonezilla Live continues cloning even if a read
1437    error occurs. If there is one, the disk image will be corrupted, but
1438    failing hard drives can only be cloned with this option enabled.
1439    
1440    -fsck-src-part Check and repair source file system before saving
1441    This option causes Clonezilla Live to check the integrity of the partition(s)
1442    to be cloned. If the filesystem of the partition is damaged, Clonezilla Live
1443    also attempts to repair it automatically. Enabling this option reduces the
1444    risk that the image contains a damaged filesystem. However, the option is
1445    disabled by default because the automatic filesystem repair attempt may
1446    cause data loss.
1447    
1448  -gm Generate image MD5 checksums  -gm Generate image MD5 checksums
1449  Causes Clonezilla Live to calculate MD5 checksum(s) of image(s) created. If  Causes Clonezilla Live to calculate MD5 checksum(s) of image(s) created. If
1450  the image cets corrupted afterwards, the checksum allows to notice the  the image gets corrupted afterwards, the checksum allows to notice the
1451  corruption before the image is restored. Mind you, calculating the checksum  corruption before the image is restored. Mind you, calculating the checksum
1452  takes some time and slows the process down a little.  takes some time and slows the process down a little.
1453    
# Line 1293  but MD5 is more popular. Line 1458  but MD5 is more popular.
1458    
1459  > Compression method  > Compression method
1460    
1461    -z1p       Use parallel gzip compression (testing), for multicore/CPU
1462  -z1        gzip compression (fast with a smaller image)  -z1        gzip compression (fast with a smaller image)
1463    -z2p       Use parallel bzip2 compression (testing), for multicore/CPU
1464  -z2        bzip2 compression (slowest but smallest image)  -z2        bzip2 compression (slowest but smallest image)
1465  -z3        lzo compression (faster with image size approx. to that of  -z3        lzo compression (faster with image size approx. to that of
1466  gzip)(NOTE!!)  gzip)(NOTE!!)
1467  -z4        lzma compression (slowest but also small image, faster  -z4
1468  decompression than bzip2)  lzma_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)
1469    -z5p       Use_parallel_xz_compression_(testing),_for_multicore/CPU
1470    -z5
1471    xz_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)
1472    -z6p       Use_parallel_lzip_compression_(testing),_for_multicore/CPU
1473    -z6
1474    lzip_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)
1475  -z0        No compression (fastest but largest image size)  -z0        No compression (fastest but largest image size)
1476    
1477  This option chooses the method which is used to compress the image while  This option chooses the method which is used to compress the image while
# Line 1314  gzip, but creates slightly larger images Line 1487  gzip, but creates slightly larger images
1487  requires good-quality RAM, but I (the contributor who wrote this chapter)  requires good-quality RAM, but I (the contributor who wrote this chapter)
1488  think other compression methods require good RAM too.  think other compression methods require good RAM too.
1489    
1490  Bzip2 and lzma are powerful compression methods. Lzma creates a little  Bzip2, lzma, xz and lzip are powerful compression methods. Lzma creates a
1491  smaller images than bzip2, and decompressing lzma-compressed images is faster  little smaller images than bzip2, and decompressing lzma-compressed images
1492  than decompressing bzip2 images. But there is no free lunch: lzma compression  is faster than decompressing bzip2 images. But there is no free lunch:
1493  method is very slow compared even to bzip2, which isn't fast method either.  lzma compression method is very slow compared even to bzip2, which isn't
1494    fast method either.
1495    
1496    Lzma method is becoming obsolete, and both xz and lzip are attempting to
1497    become its successor. They are a bit less powerful compression methods than
1498    lzma, but much faster. The differences between xz and lzip are virtually
1499    non-existent.
1500    
1501    If you don't use the i486 version of Clonezilla-SysRescCD and your
1502    processor contains multiple cores and/or supports Hyper-Threading, parallel
1503    gzip, bzip2, xz and lzip compression methods are also available. Parallel
1504    compression means that each processor core compresses a different part of the
1505    image at a time. Without parallel compression one core compresses everything.
1506    
1507    The speed impact caused by parallel compression depends on the number
1508    of processor cores available. In addition, Hyper-Threading increases the
1509    speed by about 30 % if parallel compression is used. For example, if your
1510    processor contains four cores and supports Hyper-Threading, speed with
1511    parallel compression is nearly 5,2 times as high as without. However,
1512    parallel compression is currently an experimental feature.
1513    
1514  > Splitting  > Splitting
1515    
# Line 1330  splitting, so don't use it in that case. Line 1522  splitting, so don't use it in that case.
1522  big enough, enter any value which isn't too small (you don't want to split  big enough, enter any value which isn't too small (you don't want to split
1523  the image into too many pieces, do you?)  the image into too many pieces, do you?)
1524    
1525    Clonezilla Live warns that it is no longer safe to disable splitting because
1526    value 0 can confuse init. I (the contributor) don't know what the warning
1527    exactly means and haven't been able to reproduce the problem. Anyway,
1528    entering a very big value, for example 999999999999, is a safe way to keep
1529    the image in one piece.
1530    
1531  > Postaction  > Postaction
1532    
1533  -p true        Do nothing when the clone finishes  -p true        Do nothing when the clone finishes
# Line 1423  image is restored or that the option -k1 Line 1621  image is restored or that the option -k1
1621  Force to use the saved CHS (cylinders, heads, sectors) when using sfdisk. Of  Force to use the saved CHS (cylinders, heads, sectors) when using sfdisk. Of
1622  cource, there is no use of it when using any of -j0, -k or -k2 options.  cource, there is no use of it when using any of -j0, -k or -k2 options.
1623    
1624    -icrc Ignore CRC checking of partclone
1625    This option causes partclone to skip checking the CRC32 checksums of
1626    the image. Enabling this option speeds the restore process up. However,
1627    if this option is enabled and the -cm and -cs options are disabled, there
1628    is no way to notice if the image has corrupted.
1629    
1630  -j1 Write MBR (512 B) again after image is restored. Not OK for partition  -j1 Write MBR (512 B) again after image is restored. Not OK for partition
1631  table diffe  table diffe
1632  When a disk image is restored, the partition table must be updated to  When a disk image is restored, the partition table must be updated to
# Line 1562  chkdsk /f X: Line 1766  chkdsk /f X:
1766  where X: is the drive letter of the disk. When done, boot back into  where X: is the drive letter of the disk. When done, boot back into
1767  Clonezilla Live and repeat the backup procedure.  Clonezilla Live and repeat the backup procedure.
1768    
 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.  
   
1769  If the disk/partition you are trying to backup is not the Windows System  If the disk/partition you are trying to backup is not the Windows System
1770  disk (usually C:), you can boot Windows, and execute the command in a DOS  disk (usually C:), you can boot Windows, and execute the command in a DOS
1771  window. To open a DOS window click Start / Run... and at the prompt Open:  window. To open a DOS window click Start / Run... and at the prompt Open:
1772  type cmd.  type cmd.
1773    
1774    If the Windows version you use is not XP and you're trying to backup the
1775    Windows System drive, boot into SystemRescueCD (graphical mode is not
1776    needed) and run the following command:
1777    ntfsfix /dev/hda1
1778    
1779    where /dev/hda1 is the partition name in GNU/Linux. When done, boot back
1780    into Clonezilla Live and repeat the backup procedure.
1781    
1782  * If Windows XP Recovery Console is not available, you don't have the time  * If Windows XP Recovery Console is not available, you don't have the time
1783  to execute the procedure described above, or even if you have executed it  to execute the procedure described above, or even if you have executed it
1784  but you still get the same message, and you are absolutely sure that you  but you still get the same message, and you are absolutely sure that you
# Line 1597  Getting backups Line 1802  Getting backups
1802  Intro  Intro
1803  ****************************************  ****************************************
1804  In this page I will demonstrate the creation of an image file by getting  In this page I will demonstrate the creation of an image file by getting
1805  a backup of a virtual partition (/dev/hdb1). The image file will be saved  a backup of a virtual partition (/dev/sdb1). The image file will be saved
1806  in another virtual partition (/dev/hda1).  in another virtual partition (/dev/sda1).
1807    
1808  The first thing you do when you want to get a backup of a disk/partition,  The first thing you do when you want to get a backup of a disk/partition,
1809  is make sure both the souce (to be backed up) and target (to hold the  is make sure both the souce (to be backed up) and target (to hold the
# Line 1612  boot settings are correct, in order to b Line 1817  boot settings are correct, in order to b
1817  Having done all of the above, I am ready to boot from Clonezilla-SysRescCD.  Having done all of the above, I am ready to boot from Clonezilla-SysRescCD.
1818    
1819  [[ info.png ]]  [[ info.png ]]
1820  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
1821    
1822  Getting the backup  Getting the backup
1823  ****************************************  ****************************************
# Line 1690  This is where I choose the location of t Line 1895  This is where I choose the location of t
1895  at the root directory of the selected partition.  at the root directory of the selected partition.
1896    
1897  [[ backup-06.png ]]  [[ backup-06.png ]]
1898  I select partition hda1 and press ENTER.  I select partition sda1 and press ENTER.
1899    
1900  [[ backup-07.png ]]  [[ backup-07.png ]]
1901  and then ENTER again.  and then ENTER again.
1902    
1903  [[ backup-08.png ]]  [[ backup-08.png ]]
1904  This screen displays the mounting result.  This screen displays the mounting result.
1905  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.
1906    
1907  Next Screen  Next Screen
1908  ---------------------  ---------------------
# Line 1717  Next Screen Line 1922  Next Screen
1922  ---------------------  ---------------------
1923  [[ backup-11.png ]]  [[ backup-11.png ]]
1924  In this screen I select the image name.  In this screen I select the image name.
1925  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
1926  than the default.  than the default.
1927    
1928  Next Screen  Next Screen
# Line 1737  Then I will be asked to confirm the oper Line 1942  Then I will be asked to confirm the oper
1942  After that, the backup begins  After that, the backup begins
1943    
1944  [[ backup-15.png ]]  [[ backup-15.png ]]
1945  and when it's successfully completed, I will be able to reboot the system  and when it's successfully completed, I press ENTER to get to the
1946  by pressing 1 and ENTER.  shell. Then, I execute the commands:
1947    sudo su -
1948    cd
1949    umount -a
1950    reboot
1951    
1952    to reboot the system.
1953    
1954    
1955    
# Line 1759  Samba share resource), from within Clone Line 1970  Samba share resource), from within Clone
1970  file there. Then you can boot that PC using SystemRescueCD and create a  file there. Then you can boot that PC using SystemRescueCD and create a
1971  restore DVD.  restore DVD.
1972    
1973  In this page I will demonstrate the creation of an image file by getting a  In this page I will demonstrate the creation of an image file by getting
1974  backup of my Windows partition (/dev/hda1). The image file will be save in  a backup of my second disk (/dev/sdb). The image file will be save in my
1975  my Samba server which is my laptop (ip: 10.0.0.2, Windows share resource  Samba server which is my laptop (ip: 10.0.0.3, Windows share resource name:
1976  name: data).  all_my_images).
1977    
1978  What is Samba?  What is Samba?
1979  ---------------------  ---------------------
# Line 1815  instructions . Line 2026  instructions .
2026    
2027  Screen "Start Clonezilla"  Screen "Start Clonezilla"
2028  ---------------------  ---------------------
2029    [[ backup-03.png ]]
2030  I select "Start Clonezilla" and press ENTER.  I select "Start Clonezilla" and press ENTER.
2031    
2032  Screen "Clonezilla"  Screen "Clonezilla"
2033  ---------------------  ---------------------
2034    [[ backup-04.png ]]
2035  I select "device-image" and press ENTER.  I select "device-image" and press ENTER.
2036    
2037  Screen "Mount clonezilla image directory" [^  Screen "Mount clonezilla image directory"
2038  ---------------------  ---------------------
2039  In this screen I can select the way the image file directory will be saved.  In this screen I can select the way the image file directory will be saved.
2040  Available options are local directory, remote directory through ssh,  Available options are local directory, remote directory through ssh,
2041  samba or nfs and skip, to use the previously used directory. More info  samba or nfs and skip, to use the previously used directory. More info
2042  about the image file can be found at section "About the Image file".  about the image file can be found at section "About the Image file".
2043    
2044    [[ backup-smb-05.png ]]
2045  I select "samba server" and press ENTER.  I select "samba server" and press ENTER.
2046    
2047  Screen "Mount Samba Server"  Screen "Mount Samba Server"
2048  ---------------------  ---------------------
2049  This is where I have to enter the IP address of my Samba server. I type  This is where I have to enter the IP address of my Samba server.
2050  "10.0.0.2" and press ENTER.  [[ backup-smb-06.png ]]
2051    I type "10.0.0.3" and press ENTER.
2052    
2053  Screen "Mount Samba Server" (second time)  Screen "Mount Samba Server" (second time)
2054  ---------------------  ---------------------
2055  This is where I have to enter the account (user) name on my Samba server. I  This is where I have to enter the domain name on my Samba server.
2056  type "spiros" and press ENTER.  [[ backup-smb-07.png ]]
2057    I just press ENTER, as there is no domain in my LAN. If there is a domain
2058    in your network, you have to type its name (something like my_company.com)
2059    and press ENTER.
2060    
2061  Screen "Mount Samba Server" (third time)  Screen "Mount Samba Server" (third time)
2062  ---------------------  ---------------------
2063  This is where I have to enter the domain name on my Samba server. I select  This is where I have to enter the account (user) name on my Samba server.
2064  "Cancel" and press ENTER, as there is no domain in my LAN. If there  [[ backup-smb-08.png ]]
2065  is a domain in your network, you have to type its name (something like  I type "spiros" and press ENTER.
 my_company.com) and press ENTER.  
2066    
2067  Screen "Mount Samba Server" (fourth time)  Screen "Mount Samba Server" (fourth time)
2068  ---------------------  ---------------------
2069  This is where I have to enter the directory name on my Samba server,  This is where I have to enter the directory name on my Samba server, in
2070  in which the image file will be saved. I type "/data" and press ENTER.  which the image file will be saved. I type "/all_my_images" and press ENTER.
2071    [[ backup-smb-09.png ]]
2072  At this point I will be asked for the password for user spiros. I will be  
2073  able to continue only after entering it correctly.  At this point I'm informed I'm going to be asked for the password for
2074    user spiros.
2075    [[ backup-smb-10.png ]]
2076    I will be able to continue only after entering it correctly.
2077    [[ backup-smb-11.png ]]
2078    
2079  Screen "Clonezilla - Opensource Clone System (OCS)"  Screen "Clonezilla - Opensource Clone System (OCS)"
2080  ---------------------  ---------------------
2081  I select Beginner mode to accept the default backup options. If you select  [[ backup-09.png ]]
2082    I select Beginer mode to accept the default backup options. If you select
2083  Expert mode, you can choose the options yourself. More details can be  Expert mode, you can choose the options yourself. More details can be
2084  found here.  found here.
2085    
2086  Screen "Clonezilla: Select mode"  Screen "Select mode"
2087  ---------------------  ---------------------
2088  Here I can select the desired operation. Available options are:  Here I can select the desired operation.
   
 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  
2089    
2090  I select "saveparts" and press ENTER.  [[ backup-10.png ]]
2091    I select "savedisk" and press ENTER.
2092    
2093  Screen "Clonezilla - Opensource Clone System (OCS) | Mode: saveparts"  Next Screen
2094  ---------------------  ---------------------
2095  This is the name of the image file. You can insert anything you like,  [[ backup-11.png ]]
2096  as long as it makes sence to you, so that you can distinguish the image  In this screen I select the image name.
2097  file afterwards.  I type "Backup_22-2010_sdb", which in my opinion is more informative name
2098    than the default.
2099    
2100  I insert "win_img" and press ENTER.  Next Screen
2101    ---------------------
2102    [[ backup-12.png ]]
2103    Finally I am asked to select the partition to save.
2104    I just press ENTER again.
2105    
2106  Next screen  Starting the backup
2107  ---------------------  ---------------------
2108  Here I can select the partition that will be backed up. I select "( )  [[ backup-13.png ]]
2109  hda1        ntfs" by pressing SPACE and press ENTER, and ENTER again.  Then the program will display the command that will be executed and will
2110    ask me to press ENTER.
2111    Then I will be asked to confirm the operation by pressing y and ENTER.
2112    
2113  Then a message is displayed asking for confirmation in order to continue. I  [[ backup-14.png ]]
2114  just press y, and the backup procedure begins.  After that, the backup begins
2115    
2116  Rebooting the system  [[ backup-15.png ]]
2117  ****************************************  and when it's successfully completed, I press ENTER to get to the
2118  When the backup is done, I get the following:  shell. Then, I execute the commands:
 (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:  
2119  sudo su -  sudo su -
2120  cd  cd
2121  umount -a  umount -a
2122  reboot  reboot
2123    
2124    to reboot the system.
2125    
2126    
2127    
2128    
# Line 1951  restoring make sure you have backup of a Line 2162  restoring make sure you have backup of a
2162  disk/partition, even if the filesystem is corrupted.  disk/partition, even if the filesystem is corrupted.
2163    
2164  [[ info.png ]]  [[ info.png ]]
2165  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
2166    
2167  Restoring data  Restoring data
2168  ****************************************  ****************************************
# Line 2028  Next screen Line 2239  Next screen
2239  ---------------------  ---------------------
2240  This is where I choose the location of the image file.  This is where I choose the location of the image file.
2241  [[ restoration-06.png ]]  [[ restoration-06.png ]]
2242  I select partition hda1 and press ENTER.  I select partition sda1 and press ENTER.
2243    
2244  [[ backup-07.png ]]  [[ backup-07.png ]]
2245    
2246  [[ restoration-08.png ]]  [[ restoration-08.png ]]
2247  This screen displays the mounting result.  This screen displays the mounting result.
2248  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.
2249    
2250  Next Screen  Next Screen
2251  ---------------------  ---------------------
# Line 2082  the disk doesn't contain any important d Line 2293  the disk doesn't contain any important d
2293  After that, the restore process begins  After that, the restore process begins
2294    
2295  [[ restoration-16.png ]]  [[ restoration-16.png ]]
2296  and when it's successfully completed, I will be able to reboot the system  and when it's successfully completed, I press ENTER to get to the
2297  by pressing 1 and ENTER.  shell. Then, I execute the commands:
2298    sudo su -
2299    cd
2300    umount -a
2301    reboot
2302    
2303    to reboot the system.
2304    
2305    
2306    
# Line 2530  after ejecting it. Line 2747  after ejecting it.
2747    
2748  Finally, add the image file to the disc:  Finally, add the image file to the disc:
2749    
2750  growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" --publisher "Your Name"  growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" \
2751  -graft-points /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb  --publisher "Your Name" -graft-points \
2752    /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb
2753    
2754  Note: In the command replace Your Name with anything you want to be the  Note: In the command replace Your Name with anything you want to be the
2755  publisher ID of the disc. If you don't want the disc to have any publisher  publisher ID of the disc. If you don't want the disc to have any publisher
2756  ID, run this command instead:  ID, run this command instead:
2757    
2758  growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" -graft-points  growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" \
2759  /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb  -graft-points /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb
2760    
2761  [[ restore-20.png ]]  [[ restore-20.png ]]
2762    

Legend:
Removed from v.28  
changed lines
  Added in v.77

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26