373 |
|
|
374 |
The boot parameters you can use are: |
The boot parameters you can use are: |
375 |
|
|
376 |
General boot options |
General boot options |
377 |
|
Press <TAB> to add additional options. |
378 |
|
|
379 |
* setkmap=xx: if you don't want to be asked for the keymap, you can |
* docache: causes the CD-ROM will be fully loaded into memory. A slower |
380 |
choose which keymap to load automatically. Replace xx with your keymap |
start but once complete, programs start faster and the CD drive will be |
381 |
(for example: setkmap=de for german keyboards) |
released allowing normal access to other CDs. This requires 400MB of memory |
382 |
* docache: this option is very useful if you need to insert another disc |
to cache everything (including the bootdisks and isolinux directories). Add |
383 |
in the CD drive after booting. The CD-ROM will be fully loaded into memory, |
lowmem if you have less that 400MB of memory of to prevent these directories |
384 |
and you will be able to remove the disc from the drive. The docache option |
to be copied. |
385 |
requires 400MB of memory if you want to cache everything (including the |
|
386 |
bootdisks and isolinux directories). You can add the lowmem option if you |
During boot you will be prompted for the keyboard configuration, avoid |
387 |
have less that 400MB of memory of to prevent these directories to be copied |
this by using |
388 |
into memory. |
|
389 |
* root=xxx: the root=<device> option {{ |
* setkmap=kk: which defines the keymap to load where kk (example: setkmap=de |
390 |
|
for German keyboards) |
391 |
|
* root=/dev/xdnp: the root=<device> option {{ |
392 |
http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/ |
http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/ |
393 |
}} lets you boot an existing linux system. For example, if you have a |
}} boots an existing linux system. For example, if you have linux |
394 |
linux gentoo installed on /dev/sda6, you can type rescuecd root=/dev/sda6 |
Gentoo installed on /dev/sda6, use rescuecd root=/dev/sda6 to start |
395 |
and Gentoo Linux will be started instead of the system that is on |
it. Keep in mind that you must use a 64bit kernel if your system is |
396 |
the CD-ROM. Keep in mind that you must use a 64bits kernel if your |
made of 64bit programs. This option works with LVM volumes. Use rescuecd |
397 |
system is made of 64bits programs. For instance, you can boot a 64bits |
root=/dev/VolGroup00/LogVol00. Support is also provided for root=auto, |
398 |
linux system installed on /dev/sda6 with rescue64 root=/dev/sda6. From |
which scans all the block devices tfor a linux system. The first linux |
399 |
SystemRescueCd-1.0.4, this option works with LVM disks, so you can write |
system found will be started. So with root=auto let you start the system |
|
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 |
|
400 |
installed from the CD-ROM in case you have problem with your boot loader or |
installed from the CD-ROM in case you have problem with your boot loader or |
401 |
with your kernel for instance. You can have more details about that option. |
kernel. It's also possible to specify a partition using its filesystem label |
402 |
* initscript=service:action: This options allows you to automatically |
or filesystem uuid. If the label of the partition where linux is installed |
403 |
start/stop a service at boot time. For instance if you need the |
is mylinux, then boot it using rescuecd root=LABEL=mylinux. Similarly |
404 |
samba service to be started, you can boot with the following option: |
root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. See more details. |
405 |
initscript=samba:start. This does the same thing as /etc/init.d/samba |
* initscript=service:action: This options allows start/stop a service |
406 |
start. You can use this option several times with different services. All |
at boot time. For instance if you need the samba service to be started, |
407 |
the action that are supported by an initscript can be used. This option |
you can boot with: initscript=samba:start. This does the same thing as |
408 |
is available with SystemRescueCd-1.0.2 and newer. |
/etc/init.d/samba start. Use this option multiple times for different |
409 |
* backstore=xxx: SystemRescueCd-1.1.x |
services. All the actions that are supported by an initscript can be used. |
410 |
comes with support for the backing-stores {{ |
* backstore=xxx: SystemRescueCd comes with support for the backing-stores {{ |
411 |
http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/ |
http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/ |
412 |
}}. Basically, a backing-store is a loopback filesystem which saves all |
}}. A backing-store saves all the changes you can make. so that you |
413 |
the changes you can make in SystemRescueCd when you use it. In other words |
keep these changes the next time you boot it. By default, sysresccd |
414 |
it allows you to save all the files which changes in SystemRescueCd while |
automatically scan removable devices (eg: USB sticks) at boot time and |
415 |
you use it, so that you keep these changes the next time you boot it. By |
uses the first backing-store it finds. A backing-store is not mandatory |
416 |
default, sysresccd automatically scan all your removable devices (eg: usb |
and it the scan fails it will store the files which change in memory. To |
417 |
sticks) at boot time and uses the first backing-store it finds if there is |
disable the disks scan at boot time specify backstore=off on the boot command |
418 |
one. A backing-store is not mandatory and it the scan fails it will just |
line. If you want to save your backing-store file on an harddisk, boot with |
419 |
store the files which change in memory. To disable the disks scan at boot |
backstore=alldev to scan all devices (not just removable devices). The |
420 |
time you can specify backstore=off on the boot command line. If you want |
default location for backing-stores file is any file named sysrcd.bs |
421 |
to save your backing-store file on an harddisk, you will have to boot |
located at the root of a disk which is often an USB stick. Change the path |
422 |
with backstore=alldev so that it scans all devices not just removable |
by using backstore=/sysrcd/mybackstore.bs. See backing-stores. |
423 |
devices. The default place for backing-stores file is any file named |
* isoloop=xxx: Grub2 (currently in development: grub-1.98) provides a new |
424 |
sysrcd.bs located at the root of a disk which is often an USB key. You can |
feature to boot from an ISO image which is stored from the hard disk. If you |
425 |
change the path by using an option such as backstore=/sysrcd/mybackstore.bs |
put a copy of systemrescuecd-x86-x.y.z.iso on a partition that Grub2 can read |
426 |
and then sysresccd will try to find a file named mybackstore.bs located |
then you can boot SystemRescueCd directly from the ISO image stored on your |
427 |
in /sysrcd in any block-device (partition, USB-stick, ...). You can find |
hard drive. This is very convenient if you frequently update SystemRescueCd |
428 |
more information about on the page about backing-stores. |
and you want to boot it directly from Grub2. Grub2 knows what an ISO image |
429 |
|
is and it will load the kernel image (rescuecd/rescue64) and the initramfs |
430 |
Hardware, drivers and troubleshooting options |
(initram.igz) from the ISO into memory. It will then do its normal job and |
431 |
|
execute the kernel. The SystemRescueCd init script must then be aware that |
432 |
|
its sysrcd.dat file is in an ISO and not directly on the partition. For that |
433 |
|
reason, this isoloop=xxx boot option is required so you must use it in your |
434 |
|
grub.cfg. This option is only supported in SystemRescueCd-1.4.0 and more |
435 |
|
recent. This option specifies the path of the ISO image in the partition |
436 |
|
that grub considers as its root partition. It's important to understand |
437 |
|
that the path of the ISO image may be different from the path on your |
438 |
|
linux system. If you have a separate boot partition mounted on /boot and if |
439 |
|
you copy this ISO image to /boot/sysrcd/systemrescuecd-x86-x.y.z.iso then |
440 |
|
the option has to be isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This |
441 |
|
is because the boot partition is what Grub2 will consider as its root |
442 |
|
partition during the boot process. Please read the section about isoloop {{ |
443 |
|
http://www.sysresccd.org/Sysresccd-manual-en_Easy_install_SystemRescueCd_on_harddisk#Boot_the_ISO_image_from_the_disk_using_Grub2 |
444 |
|
}} for more details. |
445 |
|
|
446 |
|
Hardware, drivers and troubleshooting options |
447 |
|
* dodebug: Enables verbose messages in linuxrc |
448 |
|
|
449 |
|
* doload=xxx: loads needed modules, multiple occurrences are permitted |
450 |
|
(example: doload=3c59x) |
451 |
|
* noload=xxx: prevents loading modules, multiple occurrences are permitted |
452 |
|
(example: noload=3c59x). Use this option if you have a problem when the |
453 |
|
system loads a particular module. |
454 |
* nonet: this will disable the network auto detection at startup |
* nonet: this will disable the network auto detection at startup |
455 |
|
|
456 |
* scandelay=x: pauses x seconds during the startup to allow slow devices |
* scandelay=x: pauses x seconds during the startup to allow slow devices |
457 |
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 |
458 |
only few seconds should be enough. |
only few seconds should be enough. |
459 |
|
|
460 |
* 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 |
461 |
itself, and then mkxf86config is disabled by default. This option forces |
itself, mkxf86config is disabled by default. This option forces the system to |
462 |
the system to run the mkxf86config startup script to run the hardware |
run the mkxf86config startup script and to run the hardware auto-detection |
463 |
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 |
464 |
the graphical environment configuration. This option replaces the option |
environment configuration. This option replaces the option noxdetect that |
465 |
noxdetect that was useful in previous versions. |
was useful in previous versions. |
466 |
* nodetect: prevents the generic hardware auto-detection. Use this option |
* nodetect: prevents generic hardware auto-detection. Use this option if |
467 |
if you have problems with the hardware auto-detection. |
you have problems with the hardware auto-detection. |
468 |
* doload=xxx: forces to load one/several modules at startup (example: |
|
469 |
doload=3c59x) |
* dostartx: load the X.Org graphical environment. |
470 |
* 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 |
471 |
(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 |
472 |
system loads a particular module at boot time. |
get the graphical environment working with the default options. |
473 |
* dostartx: This option will force the system to load the X.Org graphical |
* forcevesa=xxx: The startx command will load the Xvesa server instead |
474 |
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, |
475 |
* forcevesa: Forces X.Org to work with the safe vesa driver instead of |
1280x1024x32). |
476 |
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. |
|
477 |
* 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 |
478 |
enable this option (eg rescuecd all-generic-ide) |
enable this option (eg rescuecd all-generic-ide) |
479 |
* acpi-off / noapic / irqpool: use these options if you have any problem |
* nodmraid: Disable dmraid, for some motherboards with built-in RAID |
480 |
when the kernel boots: if it hangs on a driver or if it crashes, ... |
controller. |
481 |
* dodebug: Enables verbose messages in the linuxrc script. |
* nomdadm: Disable mdadm, for software RAID. |
482 |
* lowmem: Prevents non critical things to be loaded into memory (like the |
|
483 |
sshd and nfsd services) |
* acpi-off / noapic / irqpool: use these options if you have problem when |
484 |
|
the kernel boots: if it hangs on a driver or if it crashes, ... |
485 |
|
|
486 |
|
* lowmem: For systems with smaller memory, some daemons are not started |
487 |
|
including sshd and nfsd. |
488 |
|
|
489 |
* skipmount=/dev/xxx: The system mounts all the storage devices at boot |
* skipmount=/dev/xxx: The system mounts all the storage devices at boot |
490 |
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 |
491 |
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 |
492 |
system. You can just boot with skipmount=/dev/sda1 skipmount=/dev/sda2 if |
these two partitions. |
493 |
you want SystemRescueCd to ignore these two partitions. This boot option |
|
494 |
requires SystemRescueCd-1.0.1 or more recent. |
Network configuration and remote access |
495 |
* nodmraid: Disable dmraid, which is the program that drives RAID disks |
* dodhcp: to request a DHCP server provide network attributes including |
496 |
based on cheap RAID controller built-in motherboards. |
an IP address, gateway... . otherwise, |
497 |
* nomdadm: Disable mdadm, which is the program that drives software RAID. |
* ethx=ipaddr/cidr: Sets the static IP address of all the ethernet |
498 |
|
interfaces on the system. The /cidr extension is optional. For instance, |
499 |
Network auto-configuration and remote access |
if you use option ethx=192.168.0.1 on a machine with two ethernet adapters, |
500 |
|
both eth0 and eth1 will be configured with 192.168.0.1. You can use the |
501 |
* dodhcp: Use dodhcp if you have a DHCP server on your network and you |
format ethx=10.0.0.1/24 (using the cidr notation) if you don't use the |
502 |
want the system to get a dynamic IP address at boot time. |
default netmask. |
503 |
* ethx=ipaddr/cidr: Sets the static IP address of all the ethernet interfaces |
* eth0=ipaddr/cidr: This option is similar to ethx=ipaddr/cidr but it |
504 |
found on the system. The /cidr extension is optional. For instance, if |
configures only one interface at a time. To configure the network on a |
505 |
you use option ethx=192.168.0.1 on a machine with two ethernet adapters, |
server that has two interfaces, use: eth0=192.168.10.1/24 eth1=192.168.20.1. |
|
both eth0 and eth1 will be configured with 192.168.0.1. You can also write |
|
|
something like ethx=10.0.0.1/24 (using the cidr notation) if you don't |
|
|
use the default netmask. |
|
|
* eth0=ipaddr/cidr: This option is similar to |
|
|
ethx=ipaddr/cidr but it configures only one interface |
|
|
at a time. Of course, you can use the eth0=ipaddr/cidr option {{ |
|
|
http://www.sysresccd.org/news/2008/04/13/new-boot-options-for-advanced-ethernet-ip-configuration/ |
|
|
}} it for all the ethernet interfaces, not just eth0. For instance if you |
|
|
want to configure the network on a server that has two interfaces, you can |
|
|
write something like this: eth0=192.168.10.1/24 eth1=192.168.20.1. This |
|
|
option requires SystemRescueCd-1.0.2 or newer. |
|
506 |
* 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 |
507 |
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 |
508 |
you want to use 192.168.0.254 as the DNS server. |
you want to use 192.168.0.254 as the DNS server. |
534 |
careful, you have to respect the separator (comma between the interfaces |
careful, you have to respect the separator (comma between the interfaces |
535 |
and exclamation marks between the name and the mac address). |
and exclamation marks between the name and the mac address). |
536 |
|
|
537 |
Options provided by the autorun |
Network boot using PXE |
538 |
|
SystemRescueCd provides several options for booting from the network |
539 |
|
using PXE. |
540 |
|
These options can be combined with other network boot options |
541 |
|
such as ethx (cf previous section). See PXE network booting {{ |
542 |
|
http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting }} to |
543 |
|
get a global overview of SystemRescueCd and PXE and Manage remote servers |
544 |
|
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 |
|
For information on activating speakup, see the speakup info page {{ |
569 |
|
http://www.sysresccd.org/Speakup-info }}. |
570 |
|
|
571 |
|
Options provided for autorun |
572 |
* ar_source=xxx: place where the autorun are stored. It may |
* ar_source=xxx: place where the autorun are stored. It may |
573 |
be the root directory of a partition (/dev/sda1), an nfs |
be the root directory of a partition (/dev/sda1), an nfs |
574 |
share (nfs://192.168.1.1:/path/to/scripts), a samba share |
share (nfs://192.168.1.1:/path/to/scripts), a samba share |
575 |
(smb://192.168.1.1/path/to/scripts), or an http directory |
(smb://192.168.1.1/path/to/scripts), or an http directory |
576 |
(http://192.168.1.1/path/to/scripts). |
(http://192.168.1.1/path/to/scripts). |
577 |
* 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 |
578 |
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 |
579 |
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. |
|
580 |
* ar_ignorefail: continue to execute the scripts chain even if a script |
* ar_ignorefail: continue to execute the scripts chain even if a script |
581 |
failed (returned a non-zero status) |
failed (returned a non-zero status) |
582 |
* 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 |
623 |
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 |
624 |
Clonezilla live. |
Clonezilla live. |
625 |
e.g. ocs_live_run="ocs-live-general" |
e.g. ocs_live_run="ocs-live-general" |
626 |
|
//NOTE// You might have to use "sudo" command inside your own script, |
627 |
|
or you can assign it like: ocs_live_run="sudo bash /my-clonezilla" |
628 |
* 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 |
629 |
(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 |
630 |
ocs-sr. Therefore these parameters are actually those of ocs-sr. |
ocs-sr. Therefore these parameters are actually those of ocs-sr. |
656 |
only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= |
only. (It was also on /dev/ttyS0 before, but since Clonezilla live >= |
657 |
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 |
658 |
example, add live-getty and console=ttyS0,38400n81 in the boot parameter. |
example, add live-getty and console=ttyS0,38400n81 in the boot parameter. |
659 |
|
//NOTE// |
660 |
|
* This parameter was added in Clonezilla live 1.2.3-22 or later. |
661 |
|
* If "live-getty console=$tty,38400n81" are assigned in the boot parameters, |
662 |
|
ocs_live_run_tty will honor $tty, even other value is assigned to |
663 |
|
ocs_live_run_tty in boot parameter. |
664 |
|
* It's recommended to assign ocs_lang and ocs_live_keymap in the boot |
665 |
|
parameters too. |
666 |
|
* ip, this option allows you to specify the network parameters for |
667 |
|
network card. In Clonezilla live a patched live-initramfs is used, which |
668 |
|
is different from the original live-initramfs so that you can assign |
669 |
|
DNS server, too. Its format is: ip=ethernet port,IP address, netmask, |
670 |
|
gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1, |
671 |
|
netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can |
672 |
|
assign the following in the boot parameter: |
673 |
|
ip=eth0,10.0.100.1,255.255.255.0,10.0.100.254,8.8.8.8 |
674 |
|
If more than one network card, you can use ":" to separate them, e.g.: |
675 |
|
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,, |
676 |
* Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when |
* Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when |
677 |
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 |
678 |
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 |