342 |
SystemRescueCD boot parameters |
SystemRescueCD boot parameters |
343 |
**************************************** |
**************************************** |
344 |
[[ info.png ]] |
[[ info.png ]] |
345 |
The following info applies to SystemRescueCD v. 1.3.5. In case |
The following info applies to SystemRescueCD v. 1.5.5. In case |
346 |
you need to get info for a more recent version of SystemRescueCD |
you need to get info for a more recent version of SystemRescueCD |
347 |
please see the page "Sysresccd-manual-en Booting the CD-ROM {{ |
please see the page "Sysresccd-manual-en Booting the CD-ROM {{ |
348 |
http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}" |
http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM }}" |
357 |
|
|
358 |
Available kernels (boot images): |
Available kernels (boot images): |
359 |
|
|
360 |
* rescuecd This is the default choice for 32bits systems, with Framebuffer |
* rescuecd Default for 32bit systems, with Framebuffer disabled, best choice. |
361 |
disabled, best choice. |
* rescue64 Default 64 bit kernel. Use it if you want to chroot to a 64bit |
362 |
* 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 |
363 |
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 |
364 |
vmlinuz2 in versions prior to SystemRescueCd-1.0.0. |
a processor with 64bit instructions (amd64 / em64t). |
365 |
* 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 |
366 |
to a 64bits linux system installed on your hard disk, or if you have to run |
if you have problems with rescuecd |
367 |
64 bits programs. This kernel is able to boot SystemRescueCd from the cdrom |
* altker64 an alternative kernel for 64bit systems. Boot with this kernel |
368 |
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. |
|
369 |
|
|
370 |
The boot parameters you can use are: |
The boot parameters you can use are: |
371 |
|
|
372 |
General boot options |
General boot options |
373 |
|
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 |
|
374 |
|
|
375 |
|
* docache: causes the CD-ROM will be fully loaded into memory. A slower |
376 |
|
start but once complete, programs start faster and the CD drive will be |
377 |
|
released allowing normal access to other CDs. This requires 400MB of memory |
378 |
|
to cache everything (including the bootdisks and isolinux directories). Add |
379 |
|
lowmem if you have less that 400MB of memory of to prevent these directories |
380 |
|
to be copied. |
381 |
|
* setkmap=kk: which defines the keymap to load where kk (example: setkmap=de |
382 |
|
for German keyboards). This way you won't be prompted for the keyboard |
383 |
|
configuration during the boot. |
384 |
|
* root=/dev/xdnp: the root=<device> option boots an existing linux |
385 |
|
system. For example, if you have linux Gentoo installed on /dev/sda6, |
386 |
|
use rescuecd root=/dev/sda6 to start it. Keep in mind that you must use a |
387 |
|
64bit kernel if your system is made of 64bit programs. This option works |
388 |
|
with LVM volumes. Use rescuecd root=/dev/VolGroup00/LogVol00. Support |
389 |
|
is also provided for root=auto, which scans all the block devices tfor |
390 |
|
a linux system. The first linux system found will be started. So with |
391 |
|
root=auto let you start the system installed from the CD-ROM in case |
392 |
|
you have problem with your boot loader or kernel. It's also possible |
393 |
|
to specify a partition using its filesystem label or filesystem |
394 |
|
uuid. If the label of the partition where linux is installed is |
395 |
|
mylinux, then boot it using rescuecd root=LABEL=mylinux. Similarly |
396 |
|
root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. See more details. |
397 |
|
* initscript=service:action: This options allows start/stop a service |
398 |
|
at boot time. For instance if you need the samba service to be started, |
399 |
|
you can boot with: initscript=samba:start. This does the same thing as |
400 |
|
/etc/init.d/samba start. Use this option multiple times for different |
401 |
|
services. All the actions that are supported by an initscript can be used. |
402 |
|
* backstore=xxx: SystemRescueCd comes with support for the backing-stores. A |
403 |
|
backing-store saves all the changes you can make. so that you keep these |
404 |
|
changes the next time you boot it. By default, sysresccd automatically |
405 |
|
scan removable devices (eg: USB sticks) at boot time and uses the first |
406 |
|
backing-store it finds. A backing-store is not mandatory and it the |
407 |
|
scan fails it will store the files which change in memory. To disable |
408 |
|
the disks scan at boot time specify backstore=off on the boot command |
409 |
|
line. If you want to save your backing-store file on an harddisk, boot with |
410 |
|
backstore=alldev to scan all devices (not just removable devices). The |
411 |
|
default location for backing-stores file is any file named sysrcd.bs |
412 |
|
located at the root of a disk which is often an USB stick. Change the path |
413 |
|
by using backstore=/sysrcd/mybackstore.bs. See backing-stores. |
414 |
|
* isoloop=xxx: Grub2 (currently in development: grub-1.98) provides a new |
415 |
|
feature to boot from an ISO image which is stored from the hard disk. If you |
416 |
|
put a copy of systemrescuecd-x86-x.y.z.iso on a partition that Grub2 can read |
417 |
|
then you can boot SystemRescueCd directly from the ISO image stored on your |
418 |
|
hard drive. This is very convenient if you frequently update SystemRescueCd |
419 |
|
and you want to boot it directly from Grub2. Grub2 knows what an ISO image |
420 |
|
is and it will load the kernel image (rescuecd/rescue64) and the initramfs |
421 |
|
(initram.igz) from the ISO into memory. It will then do its normal job and |
422 |
|
execute the kernel. The SystemRescueCd init script must then be aware that |
423 |
|
its sysrcd.dat file is in an ISO and not directly on the partition. For that |
424 |
|
reason, this isoloop=xxx boot option is required so you must use it in your |
425 |
|
grub.cfg. This option is only supported in SystemRescueCd-1.4.0 and more |
426 |
|
recent. This option specifies the path of the ISO image in the partition that |
427 |
|
grub considers as its root partition. It's important to understand that the |
428 |
|
path of the ISO image may be different from the path on your linux system. If |
429 |
|
you have a separate boot partition mounted on /boot and if you copy this |
430 |
|
ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then the option has |
431 |
|
to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This is because the |
432 |
|
boot partition is what Grub2 will consider as its root partition during |
433 |
|
the boot process. Please read the section about isoloop for more details. |
434 |
|
|
435 |
|
Hardware, drivers and troubleshooting options |
436 |
|
* dodebug: Enables verbose messages in linuxrc |
437 |
|
|
438 |
|
* doload=xxx: loads needed kernel modules, multiple comma separated |
439 |
|
occurrences are permitted (example: doload=3c59x,e1000) |
440 |
|
* noload=xxx: prevents loading kernel modules, multiple comma separated |
441 |
|
occurrences are permitted (example: noload=3c59x,e1000). Use this option |
442 |
|
if you have a problem when the system loads a particular module. |
443 |
* nonet: this will disable the network auto detection at startup |
* nonet: this will disable the network auto detection at startup |
444 |
|
|
445 |
* scandelay=x: pauses x seconds during the startup to allow slow devices |
* scandelay=x: pauses x seconds during the startup to allow slow devices |
446 |
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 |
447 |
only few seconds should be enough. |
only few seconds should be enough. |
448 |
|
|
449 |
* 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 |
450 |
itself, and then mkxf86config is disabled by default. This option forces |
itself, mkxf86config is disabled by default. This option forces the system to |
451 |
the system to run the mkxf86config startup script to run the hardware |
run the mkxf86config startup script and to run the hardware auto-detection |
452 |
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 |
453 |
the graphical environment configuration. This option replaces the option |
environment configuration. This option replaces the option noxdetect that |
454 |
noxdetect that was useful in previous versions. |
was useful in previous versions. |
455 |
* nodetect: prevents the generic hardware auto-detection. Use this option |
* nodetect: prevents generic hardware auto-detection. Use this option if |
456 |
if you have problems with the hardware auto-detection. |
you have problems with the hardware auto-detection. |
457 |
* doload=xxx: forces to load one/several modules at startup (example: |
|
458 |
doload=3c59x) |
* dostartx: load the X.Org graphical environment. |
459 |
* 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 |
460 |
(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 |
461 |
system loads a particular module at boot time. |
get the graphical environment working with the default options. |
462 |
* dostartx: This option will force the system to load the X.Org graphical |
* forcevesa=xxx: The startx command will load the Xvesa server instead |
463 |
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, |
464 |
* forcevesa: Forces X.Org to work with the safe vesa driver instead of |
1280x1024x32). |
465 |
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. |
|
466 |
* 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 |
467 |
enable this option (eg rescuecd all-generic-ide) |
enable this option (eg rescuecd all-generic-ide) |
468 |
* acpi-off / noapic / irqpool: use these options if you have any problem |
* nodmraid: Disable dmraid, for some motherboards with built-in RAID |
469 |
when the kernel boots: if it hangs on a driver or if it crashes, ... |
controller. |
470 |
* dodebug: Enables verbose messages in the linuxrc script. |
* nomdadm: Disable mdadm, for software RAID. |
471 |
* lowmem: Prevents non critical things to be loaded into memory (like the |
|
472 |
sshd and nfsd services) |
* acpi-off / noapic / irqpool: use these options if you have problem when |
473 |
|
the kernel boots: if it hangs on a driver or if it crashes, ... |
474 |
|
|
475 |
|
* lowmem: For systems with smaller memory, some daemons are not started |
476 |
|
including sshd and nfsd. |
477 |
|
|
478 |
* skipmount=/dev/xxx: The system mounts all the storage devices at boot |
* skipmount=/dev/xxx: The system mounts all the storage devices at boot |
479 |
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 |
480 |
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 |
481 |
system. You can just boot with skipmount=/dev/sda1 skipmount=/dev/sda2 if |
these two partitions. |
482 |
you want SystemRescueCd to ignore these two partitions. This boot option |
|
483 |
requires SystemRescueCd-1.0.1 or more recent. |
Network configuration and remote access |
484 |
* nodmraid: Disable dmraid, which is the program that drives RAID disks |
* nonm: to disable the Network-Manager service that conflicts with the |
485 |
based on cheap RAID controller built-in motherboards. |
standard network command line tools such as ifconfig and ip. You can use |
486 |
* nomdadm: Disable mdadm, which is the program that drives software RAID. |
this option if you want to configure the network using these commands. This |
487 |
|
option is not necessary when SystemRescueCd is booting from the network |
488 |
Network auto-configuration and remote access |
since the service is automatically stopped in that case. This option |
489 |
|
requires SystemRescueCd-1.5.5 or more recent. |
490 |
* dodhcp: Use dodhcp if you have a DHCP server on your network and you |
* dodhcp: to request a DHCP server provide network attributes including |
491 |
want the system to get a dynamic IP address at boot time. |
an IP address, gateway... |
492 |
* ethx=ipaddr/cidr: Sets the static IP address of all the ethernet interfaces |
* nodhcp: never run the dhcp client in the initramfs boot |
493 |
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 |
494 |
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 |
495 |
both eth0 and eth1 will be configured with 192.168.0.1. You can also write |
SystemRescueCd-1.5.5-beta2 and more recent |
496 |
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 |
497 |
use the default netmask. |
interfaces on the system. The /cidr extension is optional. For instance, |
498 |
* eth0=ipaddr/cidr: This option is similar to |
if you use option ethx=192.168.0.1 on a machine with two ethernet adapters, |
499 |
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 |
500 |
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 |
501 |
http://www.sysresccd.org/news/2008/04/13/new-boot-options-for-advanced-ethernet-ip-configuration/ |
default netmask. |
502 |
}} 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 |
503 |
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 |
504 |
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. |
|
505 |
* 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 |
506 |
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 |
507 |
you want to use 192.168.0.254 as the DNS server. |
you want to use 192.168.0.254 as the DNS server. |
515 |
* rootpass=123456: Sets the root password of the system running on the |
* rootpass=123456: Sets the root password of the system running on the |
516 |
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 |
517 |
livecd and give 123456 password as the root password. |
livecd and give 123456 password as the root password. |
518 |
* vncserver=x:123456: The vncserver boot option {{ |
* vncserver=x:123456: The vncserver boot option has been introduced in |
519 |
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 |
520 |
}} 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 |
521 |
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 |
522 |
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 |
523 |
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 |
524 |
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 |
525 |
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. |
526 |
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 |
527 |
* nameif=xxx: You can can specify what interface name to give {{ |
particular interface using the mac address. You need SystemRescueCd-1.1.0 |
528 |
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 |
529 |
}} to a particular interface using the mac address. You need |
is using which mac address on a machine with two network interfaces: |
530 |
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 |
531 |
which interface is using which mac address on a machine with two network |
to respect the separator (comma between the interfaces and exclamation |
532 |
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 |
533 |
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 |
534 |
and exclamation marks between the name and the mac address). |
pxelinux. The pxeboot loader will set BOOTIF to the name of the interface |
535 |
|
used to boot. You can then use something like nameif=eth0!BOOTIF if you |
536 |
|
want the boot interface to be called eth0 on a computer with several |
537 |
|
Ethernet interfaces. |
538 |
|
|
539 |
|
Network boot using PXE |
540 |
|
SystemRescueCd provides several options for booting from the network |
541 |
|
using PXE. |
542 |
|
These options can be combined with other network boot options such as ethx |
543 |
|
(cf previous section). See PXE network booting to get a global overview |
544 |
|
of SystemRescueCd and PXE and Manage remote servers using PXE. |
545 |
|
The second stage downloads the kernel + initramfs using DHCP/TFTP. |
546 |
|
The third stage of the PXE boot process acquires the root files system. |
547 |
|
Several protocols are available. |
548 |
|
|
549 |
|
* netboot=tftp://ip/path/sysrcd.dat: from a TFTP server. The filesystem |
550 |
|
is loaded into memory. As a consequence computers with less than 400MB of |
551 |
|
memory won't be able to boot this way. The system will continue to work |
552 |
|
if the network is disconnected after the boot process. |
553 |
|
* netboot=http://ip:port/path/sysrcd.dat: from a Web server. The file system |
554 |
|
is loaded into memory. Computers with smaller memory won't be able to boot |
555 |
|
this way. The the system continues to work if the network is disconnected |
556 |
|
after the boot process. |
557 |
|
* netboot=nfs://ip:/path: mount an NFSv3 directory. The NFS url must be |
558 |
|
the path of the directory that contains sysrcd.dat. Only NFSv3 can be used, |
559 |
|
NFSv4 is not supported. NFS it allows computers with smaller memory to boot |
560 |
|
SystemRescueCd from the network. After the boot process, the connection |
561 |
|
is required or you will loose the access to the root file system. |
562 |
|
* netboot=nbd://ip:port: connect to an NBD server configured with sysrcd.dat |
563 |
|
on ip:port. NBD is easier to configure than NFS (only one TCP port involved) |
564 |
|
and it allows computers with smaller memort to boot SystemRescueCd from |
565 |
|
the network. After the boot process, the connection is required the access |
566 |
|
to the root system. |
567 |
|
|
568 |
Options provided by the autorun |
For information on activating speakup, see the speakup info page. |
569 |
|
|
570 |
|
Options provided for autorun |
571 |
* ar_source=xxx: place where the autorun are stored. It may |
* ar_source=xxx: place where the autorun are stored. It may |
572 |
be the root directory of a partition (/dev/sda1), an nfs |
be the root directory of a partition (/dev/sda1), an nfs |
573 |
share (nfs://192.168.1.1:/path/to/scripts), a samba share |
share (nfs://192.168.1.1:/path/to/scripts), a samba share |
574 |
(smb://192.168.1.1/path/to/scripts), or an http directory |
(smb://192.168.1.1/path/to/scripts), or an http directory |
575 |
(http://192.168.1.1/path/to/scripts). |
(http://192.168.1.1/path/to/scripts). |
576 |
* 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 |
577 |
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 |
578 |
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. |
|
579 |
* ar_ignorefail: continue to execute the scripts chain even if a script |
* ar_ignorefail: continue to execute the scripts chain even if a script |
580 |
failed (returned a non-zero status) |
failed (returned a non-zero status) |
581 |
* 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 |
588 |
Clonezilla Live boot parameters |
Clonezilla Live boot parameters |
589 |
**************************************** |
**************************************** |
590 |
[[ info.png ]] |
[[ info.png ]] |
591 |
The following info applies to Clonezilla Live v. 1.2.3-27 |
The following info applies to Clonezilla Live v. 1.2.5-17 |
592 |
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 |
593 |
please see the page "The boot parameters for Clonezilla live {{ |
please see the page "The boot parameters for Clonezilla live {{ |
594 |
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 |
610 |
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 |
611 |
}}. |
}}. |
612 |
|
|
613 |
Clonezilla live is based on Debian live {{ http://wiki.debian.org/DebianLive/ |
Clonezilla live is based on Debian live with clonezilla installed. Therefore |
614 |
}} with clonezilla installed. Therefore there are 2 kinds of boot parameters: |
there are 2 kinds of boot parameters: |
615 |
|
|
616 |
* Boot parameters from live-initramfs. You can refer to this manual of |
* Boot parameters from live-initramfs. You can refer to this manual of |
617 |
live-initramfs. |
live-initramfs. |
622 |
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 |
623 |
Clonezilla live. |
Clonezilla live. |
624 |
e.g. ocs_live_run="ocs-live-general" |
e.g. ocs_live_run="ocs-live-general" |
625 |
|
//NOTE// You might have to use "sudo" command inside your own script, |
626 |
|
or you can assign it like: ocs_live_run="sudo bash /my-clonezilla" |
627 |
* 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 |
628 |
(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 |
629 |
ocs-sr. Therefore these parameters are actually those of ocs-sr. |
ocs-sr. Therefore these parameters are actually those of ocs-sr. |
655 |
only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= |
only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= |
656 |
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 |
657 |
example, add live-getty and console=ttyS0,38400n81 in the boot parameter. |
example, add live-getty and console=ttyS0,38400n81 in the boot parameter. |
658 |
|
//NOTE// |
659 |
|
* This parameter was added in Clonezilla live 1.2.3-22 or later. |
660 |
|
* If "live-getty console=$tty,38400n81" are assigned in the boot parameters, |
661 |
|
ocs_live_run_tty will honor $tty, even other value is assigned to |
662 |
|
ocs_live_run_tty in boot parameter. |
663 |
|
* It's recommended to assign ocs_lang and ocs_live_keymap in the boot |
664 |
|
parameters too. |
665 |
|
* ip, this option allows you to specify the network parameters for |
666 |
|
network card. In Clonezilla live a patched live-initramfs is used, which |
667 |
|
is different from the original live-initramfs so that you can assign |
668 |
|
DNS server, too. Its format is: ip=ethernet port,IP address, netmask, |
669 |
|
gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1, |
670 |
|
netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can |
671 |
|
assign the following in the boot parameter: |
672 |
|
ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8 |
673 |
|
If more than one network card, you can use ":" to separate them, e.g.: |
674 |
|
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,, |
675 |
* Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when |
* Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when |
676 |
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 |
677 |
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 |
810 |
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, |
811 |
although it will do no harm. |
although it will do no harm. |
812 |
|
|
813 |
live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper]. |
live-initramfs is a fork of casper. |
814 |
casper was originally written by Tollef Fog Heen <tfheen@canonical.com> |
casper was originally written by Tollef Fog Heen |
815 |
and Matt Zimmerman <mdz@canonical.com>. |
<tfheen@canonical.com&gt; |
816 |
|
and Matt Zimmerman <mdz@canonical.com&gt;. |
817 |
|
|
818 |
Boot options |
Boot options |
819 |
------------ |
------------ |
859 |
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 |
860 |
live media. |
live media. |
861 |
|
|
862 |
ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF] |
ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]: |
863 |
[,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]]***:: |
[DEVICE]:[AUTOCONF] |
864 |
|
[,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]: |
865 |
|
[DEVICE]:[AUTOCONF]]***:: |
866 |
|
|
867 |
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 |
868 |
should be |
should be |
882 |
{keyb|kbd-chooser/method}=**KEYBOARD**, |
{keyb|kbd-chooser/method}=**KEYBOARD**, |
883 |
{klayout|console-setup/layoutcode}=**LAYOUT**, |
{klayout|console-setup/layoutcode}=**LAYOUT**, |
884 |
{kvariant|console-setup/variantcode}=**VARIANT**, |
{kvariant|console-setup/variantcode}=**VARIANT**, |
885 |
{kmodel|console-setup/modelcode}=**CODE**, koptions=**OPTIONS**:: |
{kmodel|console-setup/modelcode}= |
886 |
|
**CODE**, koptions=**OPTIONS**:: |
887 |
|
|
888 |
Configure the running keyboard as specified, if this one misses |
Configure the running keyboard as specified, if this one misses |
889 |
live-initramfs |
live-initramfs |
1126 |
this file, any images in the "/live" directory are loaded in alphanumeric |
this file, any images in the "/live" directory are loaded in alphanumeric |
1127 |
order. |
order. |
1128 |
|
|
1129 |
/etc/live-persistence.binds |
/etc/live-persistence.binds |
1130 |
|
|
1131 |
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 |
1132 |
media) |
media) |
1149 |
---- |
---- |
1150 |
|
|
1151 |
Report bugs against live-initramfs |
Report bugs against live-initramfs |
1152 |
link:http://packages.qa.debian.org/live-initramfs[http://packages.qa.debian.org/live-initramfs]. |
http://packages.qa.debian.org/live-initramfs. |
1153 |
|
|
1154 |
Homepage |
Homepage |
1155 |
-------- |
-------- |
1156 |
|
|
1157 |
More information about the Debian Live project can be found at |
More information about the Debian Live project can be found at |
1158 |
link:http://debian-live.alioth.debian.org/[http://debian-live.alioth.debian.org/] |
http://debian-live.alioth.debian.org/ and |
1159 |
and |
http://wiki.debian.org/DebianLive/. |
|
link:http://wiki.debian.org/DebianLive/[http://wiki.debian.org/DebianLive/]. |
|
1160 |
|
|
1161 |
Authors |
Authors |
1162 |
------- |
------- |
1163 |
|
|
1164 |
live-initramfs is maintained by Daniel Baumann <daniel@debian.org> |
live-initramfs is maintained by Daniel Baumann <daniel@debian.org&gt; |
1165 |
for the Debian project. |
for the Debian project. |
1166 |
|
|
1167 |
live-initramfs is a fork of link:http://packages.ubuntu.com/casper/[casper]. |
live-initramfs is a fork of casper. |
1168 |
casper was originally written by Tollef Fog Heen <tfheen@canonical.com> |
casper was originally written by Tollef Fog Heen |
1169 |
and Matt Zimmerman <mdz@canonical.com>. |
<tfheen@canonical.com&gt; |
1170 |
|
and Matt Zimmerman <mdz@canonical.com&gt;. |
1171 |
|
|
1172 |
|
|
1173 |
|
|
1253 |
|
|
1254 |
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 |
1255 |
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 |
1256 |
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 |
1257 |
/home/partimag. |
of folders will be presented to you, so you can select the base image |
1258 |
|
directory (first level directory within the partition), which will then |
1259 |
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 |
1260 |
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 |
1261 |
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!!! |
|
1262 |
|
|
1263 |
Another thing that should be pointed out is that only unmounted partitions |
Another thing that should be pointed out is that only unmounted partitions |
1264 |
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 |
1344 |
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 |
1345 |
it is useless. |
it is useless. |
1346 |
|
|
1347 |
|
-rescue Continue reading next one when disk blocks read errors |
1348 |
|
If this option is set, Clonezilla Live continues cloning even if a read |
1349 |
|
error occurs. If there is one, the disk image will be corrupted, but |
1350 |
|
failing hard drives can only be cloned with this option enabled. |
1351 |
|
|
1352 |
|
-fsck-src-part Check and repair source file system before saving |
1353 |
|
This option causes Clonezilla Live to check the integrity of the partition(s) |
1354 |
|
to be cloned. If the filesystem of the partition is damaged, Clonezilla Live |
1355 |
|
also attempts to repair it automatically. Enabling this option reduces the |
1356 |
|
risk that the image contains a damaged filesystem. However, the option is |
1357 |
|
disabled by default because the automatic filesystem repair attempt may |
1358 |
|
cause data loss. |
1359 |
|
|
1360 |
-gm Generate image MD5 checksums |
-gm Generate image MD5 checksums |
1361 |
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 |
1362 |
the image cets corrupted afterwards, the checksum allows to notice the |
the image gets corrupted afterwards, the checksum allows to notice the |
1363 |
corruption before the image is restored. Mind you, calculating the checksum |
corruption before the image is restored. Mind you, calculating the checksum |
1364 |
takes some time and slows the process down a little. |
takes some time and slows the process down a little. |
1365 |
|
|
1370 |
|
|
1371 |
> Compression method |
> Compression method |
1372 |
|
|
1373 |
|
-z1p Use parallel gzip compression (testing), for multicore/CPU |
1374 |
-z1 gzip compression (fast with a smaller image) |
-z1 gzip compression (fast with a smaller image) |
1375 |
|
-z2p Use parallel bzip2 compression (testing), for multicore/CPU |
1376 |
-z2 bzip2 compression (slowest but smallest image) |
-z2 bzip2 compression (slowest but smallest image) |
1377 |
-z3 lzo compression (faster with image size approx. to that of |
-z3 lzo compression (faster with image size approx. to that of |
1378 |
gzip)(NOTE!!) |
gzip)(NOTE!!) |
1379 |
-z4 lzma compression (slowest but also small image, faster |
-z4 |
1380 |
decompression than bzip2) |
lzma_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2) |
1381 |
|
-z5p Use_parallel_xz_compression_(testing),_for_multicore/CPU |
1382 |
|
-z5 |
1383 |
|
xz_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2) |
1384 |
|
-z6p Use_parallel_lzip_compression_(testing),_for_multicore/CPU |
1385 |
|
-z6 |
1386 |
|
lzip_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2) |
1387 |
-z0 No compression (fastest but largest image size) |
-z0 No compression (fastest but largest image size) |
1388 |
|
|
1389 |
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 |
1399 |
requires good-quality RAM, but I (the contributor who wrote this chapter) |
requires good-quality RAM, but I (the contributor who wrote this chapter) |
1400 |
think other compression methods require good RAM too. |
think other compression methods require good RAM too. |
1401 |
|
|
1402 |
Bzip2 and lzma are powerful compression methods. Lzma creates a little |
Bzip2, lzma, xz and lzip are powerful compression methods. Lzma creates a |
1403 |
smaller images than bzip2, and decompressing lzma-compressed images is faster |
little smaller images than bzip2, and decompressing lzma-compressed images |
1404 |
than decompressing bzip2 images. But there is no free lunch: lzma compression |
is faster than decompressing bzip2 images. But there is no free lunch: |
1405 |
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 |
1406 |
|
fast method either. |
1407 |
|
|
1408 |
|
Lzma method is becoming obsolete, and both xz and lzip are attempting to |
1409 |
|
become its successor. They are a bit less powerful compression methods than |
1410 |
|
lzma, but much faster. The differences between xz and lzip are virtually |
1411 |
|
non-existent. |
1412 |
|
|
1413 |
|
If you don't use the i486 version of Clonezilla-SysRescCD and your |
1414 |
|
processor contains multiple cores and/or supports Hyper-Threading, parallel |
1415 |
|
gzip, bzip2, xz and lzip compression methods are also available. Parallel |
1416 |
|
compression means that each processor core compresses a different part of the |
1417 |
|
image at a time. Without parallel compression one core compresses everything. |
1418 |
|
|
1419 |
|
The speed impact caused by parallel compression depends on the number |
1420 |
|
of processor cores available. In addition, Hyper-Threading increases the |
1421 |
|
speed by about 30 % if parallel compression is used. For example, if your |
1422 |
|
processor contains four cores and supports Hyper-Threading, speed with |
1423 |
|
parallel compression is nearly 5,2 times as high as without. However, |
1424 |
|
parallel compression is currently an experimental feature. |
1425 |
|
|
1426 |
> Splitting |
> Splitting |
1427 |
|
|
1434 |
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 |
1435 |
the image into too many pieces, do you?) |
the image into too many pieces, do you?) |
1436 |
|
|
1437 |
|
Clonezilla Live warns that it is no longer safe to disable splitting because |
1438 |
|
value 0 can confuse init. I (the contributor) don't know what the warning |
1439 |
|
exactly means and haven't been able to reproduce the problem. Anyway, |
1440 |
|
entering a very big value, for example 999999999999, is a safe way to keep |
1441 |
|
the image in one piece. |
1442 |
|
|
1443 |
> Postaction |
> Postaction |
1444 |
|
|
1445 |
-p true Do nothing when the clone finishes |
-p true Do nothing when the clone finishes |
1533 |
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 |
1534 |
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. |
1535 |
|
|
1536 |
|
-icrc Ignore CRC checking of partclone |
1537 |
|
This option causes partclone to skip checking the CRC32 checksums of |
1538 |
|
the image. Enabling this option speeds the restore process up. However, |
1539 |
|
if this option is enabled and the -cm and -cs options are disabled, there |
1540 |
|
is no way to notice if the image has corrupted. |
1541 |
|
|
1542 |
-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 |
1543 |
table diffe |
table diffe |
1544 |
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 |
1678 |
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 |
1679 |
Clonezilla Live and repeat the backup procedure. |
Clonezilla Live and repeat the backup procedure. |
1680 |
|
|
|
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. |
|
|
|
|
1681 |
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 |
1682 |
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 |
1683 |
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: |
1684 |
type cmd. |
type cmd. |
1685 |
|
|
1686 |
|
If the Windows version you use is not XP and you're trying to backup the |
1687 |
|
Windows System drive, boot into SystemRescueCD (graphical mode is not |
1688 |
|
needed) and run the following command: |
1689 |
|
ntfsfix /dev/hda1 |
1690 |
|
|
1691 |
|
where /dev/hda1 is the partition name in GNU/Linux. When done, boot back |
1692 |
|
into Clonezilla Live and repeat the backup procedure. |
1693 |
|
|
1694 |
* 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 |
1695 |
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 |
1696 |
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 |
1714 |
Intro |
Intro |
1715 |
**************************************** |
**************************************** |
1716 |
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 |
1717 |
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 |
1718 |
in another virtual partition (/dev/hda1). |
in another virtual partition (/dev/sda1). |
1719 |
|
|
1720 |
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, |
1721 |
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 |
1729 |
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. |
1730 |
|
|
1731 |
[[ info.png ]] |
[[ info.png ]] |
1732 |
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 |
1733 |
|
|
1734 |
Getting the backup |
Getting the backup |
1735 |
**************************************** |
**************************************** |
1807 |
at the root directory of the selected partition. |
at the root directory of the selected partition. |
1808 |
|
|
1809 |
[[ backup-06.png ]] |
[[ backup-06.png ]] |
1810 |
I select partition hda1 and press ENTER. |
I select partition sda1 and press ENTER. |
1811 |
|
|
1812 |
[[ backup-07.png ]] |
[[ backup-07.png ]] |
1813 |
and then ENTER again. |
and then ENTER again. |
1814 |
|
|
1815 |
[[ backup-08.png ]] |
[[ backup-08.png ]] |
1816 |
This screen displays the mounting result. |
This screen displays the mounting result. |
1817 |
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. |
1818 |
|
|
1819 |
Next Screen |
Next Screen |
1820 |
--------------------- |
--------------------- |
1834 |
--------------------- |
--------------------- |
1835 |
[[ backup-11.png ]] |
[[ backup-11.png ]] |
1836 |
In this screen I select the image name. |
In this screen I select the image name. |
1837 |
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 |
1838 |
than the default. |
than the default. |
1839 |
|
|
1840 |
Next Screen |
Next Screen |
1854 |
After that, the backup begins |
After that, the backup begins |
1855 |
|
|
1856 |
[[ backup-15.png ]] |
[[ backup-15.png ]] |
1857 |
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 |
1858 |
by pressing 1 and ENTER. |
shell. Then, I execute the commands: |
1859 |
|
sudo su - |
1860 |
|
cd |
1861 |
|
umount -a |
1862 |
|
reboot |
1863 |
|
|
1864 |
|
to reboot the system. |
1865 |
|
|
1866 |
|
|
1867 |
|
|
1882 |
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 |
1883 |
restore DVD. |
restore DVD. |
1884 |
|
|
1885 |
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 |
1886 |
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 |
1887 |
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: |
1888 |
name: data). |
all_my_images). |
1889 |
|
|
1890 |
What is Samba? |
What is Samba? |
1891 |
--------------------- |
--------------------- |
1938 |
|
|
1939 |
Screen "Start Clonezilla" |
Screen "Start Clonezilla" |
1940 |
--------------------- |
--------------------- |
1941 |
|
[[ backup-03.png ]] |
1942 |
I select "Start Clonezilla" and press ENTER. |
I select "Start Clonezilla" and press ENTER. |
1943 |
|
|
1944 |
Screen "Clonezilla" |
Screen "Clonezilla" |
1945 |
--------------------- |
--------------------- |
1946 |
|
[[ backup-04.png ]] |
1947 |
I select "device-image" and press ENTER. |
I select "device-image" and press ENTER. |
1948 |
|
|
1949 |
Screen "Mount clonezilla image directory" [^ |
Screen "Mount clonezilla image directory" |
1950 |
--------------------- |
--------------------- |
1951 |
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. |
1952 |
Available options are local directory, remote directory through ssh, |
Available options are local directory, remote directory through ssh, |
1953 |
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 |
1954 |
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". |
1955 |
|
|
1956 |
|
[[ backup-smb-05.png ]] |
1957 |
I select "samba server" and press ENTER. |
I select "samba server" and press ENTER. |
1958 |
|
|
1959 |
Screen "Mount Samba Server" |
Screen "Mount Samba Server" |
1960 |
--------------------- |
--------------------- |
1961 |
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. |
1962 |
"10.0.0.2" and press ENTER. |
[[ backup-smb-06.png ]] |
1963 |
|
I type "10.0.0.3" and press ENTER. |
1964 |
|
|
1965 |
Screen "Mount Samba Server" (second time) |
Screen "Mount Samba Server" (second time) |
1966 |
--------------------- |
--------------------- |
1967 |
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. |
1968 |
type "spiros" and press ENTER. |
[[ backup-smb-07.png ]] |
1969 |
|
I just press ENTER, as there is no domain in my LAN. If there is a domain |
1970 |
|
in your network, you have to type its name (something like my_company.com) |
1971 |
|
and press ENTER. |
1972 |
|
|
1973 |
Screen "Mount Samba Server" (third time) |
Screen "Mount Samba Server" (third time) |
1974 |
--------------------- |
--------------------- |
1975 |
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. |
1976 |
"Cancel" and press ENTER, as there is no domain in my LAN. If there |
[[ backup-smb-08.png ]] |
1977 |
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. |
|
1978 |
|
|
1979 |
Screen "Mount Samba Server" (fourth time) |
Screen "Mount Samba Server" (fourth time) |
1980 |
--------------------- |
--------------------- |
1981 |
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 |
1982 |
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. |
1983 |
|
[[ backup-smb-09.png ]] |
1984 |
At this point I will be asked for the password for user spiros. I will be |
|
1985 |
able to continue only after entering it correctly. |
At this point I'm informed I'm going to be asked for the password for |
1986 |
|
user spiros. |
1987 |
|
[[ backup-smb-10.png ]] |
1988 |
|
I will be able to continue only after entering it correctly. |
1989 |
|
[[ backup-smb-11.png ]] |
1990 |
|
|
1991 |
Screen "Clonezilla - Opensource Clone System (OCS)" |
Screen "Clonezilla - Opensource Clone System (OCS)" |
1992 |
--------------------- |
--------------------- |
1993 |
I select Beginner mode to accept the default backup options. If you select |
[[ backup-09.png ]] |
1994 |
|
I select Beginer mode to accept the default backup options. If you select |
1995 |
Expert mode, you can choose the options yourself. More details can be |
Expert mode, you can choose the options yourself. More details can be |
1996 |
found here. |
found here. |
1997 |
|
|
1998 |
Screen "Clonezilla: Select mode" |
Screen "Select mode" |
1999 |
--------------------- |
--------------------- |
2000 |
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 |
|
2001 |
|
|
2002 |
I select "saveparts" and press ENTER. |
[[ backup-10.png ]] |
2003 |
|
I select "savedisk" and press ENTER. |
2004 |
|
|
2005 |
Screen "Clonezilla - Opensource Clone System (OCS) | Mode: saveparts" |
Next Screen |
2006 |
--------------------- |
--------------------- |
2007 |
This is the name of the image file. You can insert anything you like, |
[[ backup-11.png ]] |
2008 |
as long as it makes sence to you, so that you can distinguish the image |
In this screen I select the image name. |
2009 |
file afterwards. |
I type "Backup_22-2010_sdb", which in my opinion is more informative name |
2010 |
|
than the default. |
2011 |
|
|
2012 |
I insert "win_img" and press ENTER. |
Next Screen |
2013 |
|
--------------------- |
2014 |
|
[[ backup-12.png ]] |
2015 |
|
Finally I am asked to select the partition to save. |
2016 |
|
I just press ENTER again. |
2017 |
|
|
2018 |
Next screen |
Starting the backup |
2019 |
--------------------- |
--------------------- |
2020 |
Here I can select the partition that will be backed up. I select "( ) |
[[ backup-13.png ]] |
2021 |
hda1 ntfs" by pressing SPACE and press ENTER, and ENTER again. |
Then the program will display the command that will be executed and will |
2022 |
|
ask me to press ENTER. |
2023 |
|
Then I will be asked to confirm the operation by pressing y and ENTER. |
2024 |
|
|
2025 |
Then a message is displayed asking for confirmation in order to continue. I |
[[ backup-14.png ]] |
2026 |
just press y, and the backup procedure begins. |
After that, the backup begins |
2027 |
|
|
2028 |
Rebooting the system |
[[ backup-15.png ]] |
2029 |
**************************************** |
and when it's successfully completed, I press ENTER to get to the |
2030 |
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: |
|
2031 |
sudo su - |
sudo su - |
2032 |
cd |
cd |
2033 |
umount -a |
umount -a |
2034 |
reboot |
reboot |
2035 |
|
|
2036 |
|
to reboot the system. |
2037 |
|
|
2038 |
|
|
2039 |
|
|
2040 |
|
|
2653 |
|
|
2654 |
Finally, add the image file to the disc: |
Finally, add the image file to the disc: |
2655 |
|
|
2656 |
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" \ |
2657 |
-graft-points /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb |
--publisher "Your Name" -graft-points \ |
2658 |
|
/Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb |
2659 |
|
|
2660 |
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 |
2661 |
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 |
2662 |
ID, run this command instead: |
ID, run this command instead: |
2663 |
|
|
2664 |
growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" -graft-points |
growisofs -M /dev/dvd -R -J -V "Backup_5-2010_hdb" \ |
2665 |
/Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb |
-graft-points /Backup_5-2010_hdb/=/media/usb/Backup_5-2010_hdb |
2666 |
|
|
2667 |
[[ restore-20.png ]] |
[[ restore-20.png ]] |
2668 |
|
|