The following options are supported in SystemRescueCd versions up to 5. Please refer to Booting SystemRescueCd (boot options) if you are interested in SystemRescueCd version 6.
copytoramoption in recent verisons. A slower start but once complete, the system will be more responsive and also it wont require the original device to run. It means you can actually work on the device where SystemRescueCd is installed. This requires 2GB of memory to cache the system.
rescue32 root=/dev/sda6to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use
rescue32 root=/dev/VolGroup00/LogVol00. Support is also provided for
root=auto, which scans all the block devices for a linux system. The first linux system found will be started. So
root=autolets you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It’s also possible to specify a partition using its
filesystem uuid. If the label of the partition where linux is installed is
mylinux, then boot it using
rescue32 root=LABEL=mylinux. Similarly
root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7. Read root=device option for more details.
initscript=samba:start. This does the same thing as
/etc/init.d/samba start. Use this option a multiple of times for different services. All the actions that are supported by an initscript can be used.
backstore=offon the boot command line. If you want to save your backing-store file on a harddisk, boot with
backstore=alldevto scan all devices (not just removable devices). The default location for a backing-stores file is any file named
sysrcd.bslocated at the root of a disk which is often a USB stick. Change the path by using
backstore=/sysrcd/mybackstore.bs. See backing-stores.
systemrescuecd-x86-x.y.z.isoon a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescue32/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its
sysrcd.datfile is in an ISO and not directly on the partition. For that reason, this
isoloop=xxxboot option is required so you must use it in your
grub.cfg. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It’s important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on
/bootand if you copy this ISO image to
/boot/sysrcd/systemrescuecd-x86-x.y.z.isothen the option has to be
isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read the section about isoloop for more details.
noload=3c59x,e1000). Use this option if you have a problem when the system loads a particular module.
noxdetectthat was useful in previous versions.
startxcommand will load the
Xvesaserver instead of
Xorg, and use the screen resolution given as parameter (eg:
skipmount=/dev/sda1 skipmount=/dev/sda2to ignore these two partitions.
ip. You can use this option if you want to configure the network using these commands. This option is not necessary when SystemRescueCd is booting from the network since the service is automatically stopped in that case.
dodhcp=eth0,eth2 eth1=192.168.128.1/24to use dhcp for eth0 and eth2 and a static address on eth1.
/cidrextension is mandatory. For instance, if you use option
ethx=192.168.0.1/24on a machine with two ethernet adapters, both
eth1will be configured with
ethx=ipaddr/cidrbut it configures only one interface at a time. To configure the network on a server that has two interfaces, use, for example:
dns=192.168.0.254means that you want to use
192.168.0.254as the DNS server.
gateway=192.168.0.254means that the computer can connect to a computer outside of the local network via
123456. That way you can connect from the network and ssh on the livecd and give
123456password as the root password.
xwith the number of displays you want, and
123456with your password. The password must be between 6 and 8 characters, else the boot option will be ignored. In other words the
vncserver=2:MyPaSsWdoption will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org. This option accepts a password longer than 8 chars (between 5 and 12 chars)
nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address). You can also use the magic keyword BOOTIF when you boot from pxelinux. The pxeboot loader will set BOOTIF to the name of the interface used to boot. You can then use something like
nameif=eth0!BOOTIFif you want the boot interface to be called
eth0on a computer with several Ethernet interfaces.
SystemRescueCd provides several options for booting from the network using PXE.
These options can be combined with other network boot options such as
(cf previous section). Refer to PXE network booting
to get a global overview of SystemRescueCd and PXE and Manage remote servers using
The second stage downloads the kernel and the initramfs using DHCP/TFTP.
The third stage of the PXE boot process acquires the root files system.
Several protocols are available.
netboot=tftp://ip/path/sysrcd.dat: from a TFTP server. The filesystem is loaded into memory. As a consequence computers with less than 800MB of memory won’t be able to boot this way. The system will continue to work if the network is disconnected after the boot process.
netboot=http://ip:port/path/sysrcd.dat: from a Web server. The file system is loaded into memory. Computers with smaller memory won’t be able to boot this way. The the system continues to work if the network is disconnected after the boot process.
netboot=nfs://ip:/path: mount an NFSv3 directory. The NFS url must be the path of the directory that contains
sysrcd.dat. Only NFSv3 can be used, NFSv4 is not supported. NFS allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, continued network connection is required or you will loose access to the root file system.
netboot=nbd://ip:port: connect to an NBD server configured with
sysrcd.daton ip:port. NBD is easier to configure than NFS (only one TCP port involved) and it allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, the network connection continues to be required to access the root file system.
For information on activating speakup, see the speakup info page
SystemRescueCd comes with the
loadsrm boot option that allows you to
control which SRM modules are going to be loaded.
/dev/sda1), an nfs share (
nfs://192.168.1.1:/path/to/scripts), a samba share (
smb://192.168.1.1/path/to/scripts), or an http directory (
autoruns=0,2,7the autorun scripts
autorun7are run. Use
autoruns=noto disable all the autorun scripts with a number.
autorunscript will not be executed
For more details, please read the page about autorun
It is also possible to boot SystemRescueCd from the network. Since the installation is not simple, there is a dedicated page to PXE network booting