How to install image directly from the Rescue System on your server

installimage Script

The installimage script provided by is an easy and fast method of installing various Linux distributions.

You can run installimage directly from the Rescue System on your server. It's menu interfaces makes it easy to select the Linux distribution you want. You have full control over the how to partition your drive(s). And you can use a simple editor to define how you want to use sofware RAID and LVM.

Running installimage

To use installimage, you first need to activate the Rescue System and then boot into it Rescue System.

Use the password displayed on client area to log into the Rescue System as "root". Then type installimage to start the installimage script:

root@rescue ~ #installimage

In the following menu, you should see:

After choosing an image, you will receive a note that the editor will be started, and this will open the configuration file.

Midnight Commander (mcedit) is used as editor.

OS Choices

We offer a number of standard images that you can use. These are typically the latest version of the particular distribution.

Advanced users can also install older versions of these distributions, by going to the old\_images folder. Important note: We don't offer any support for these older images.

In addition, advanced users can also create their own OS images and install them. Please check the guide on how to install your own OS images for information on how this is possible and for a list of the requirements.

autosetup

If installimage finds an /autosetup file in the Rescue System, it will automatically use this as the configuration file. Unless there are errors in the files, you will not see a menu and or editor.

Variables

You can adjust the following variables to customize the installation.

Drives

The drives that are present in the server are identified in the first row with the variable DRIVE. Above each line, you can see the type of drive.

Here, you can select which drives you want the OS to be installed on. The drives will be completely wiped, and all data currently on them will be lost.

If you want to leave a drive in its current state and not make any changes to it, you can leave it out (remove it) by placing a # before it. Important note: Doing this means that you need to properly adjust the number after the next DRIVE variable.

Example:

# SSDSC2BB480G4
#DRIVE1 /dev/sda
# SSDSC2BB480G4
DRIVE1 /dev/sdb

SWRAID

If the server has multiple drives, you can use the variables SWRAID and SWRAIDLEVEL to create different software RAID levels. Any software RAID levels are always applied to all drives. (That means drives marked with DRIVE, as discussed above.) drives. If you don't want software RAID on a particular drive, you'll need to remove it accordingly.

The script can create software RAID with levels 0, 1, 5, 6 or 10.

Bootloader

The bootloader Grub is pre-configured. (In the past we also offered Lilo). Depending on the operating system, GRUB2 or GRUB1 (legacy Grub) is installed.

Hostname

The variable HOSTNAME sets the corresponding host name in the system.

Partitions / file systems

The installimage also supports adjustments to the partitioning scheme (including the use of LVM). You can find the designated syntax in the examples in the editor.

Operating system image

This is the full path to the operating system image; you only need to specify it if you are installing a custom image.

Installation

After leaving the editor with F10 (save and quit), the syntax of the config file is checked. Should it contain errors, you will be returned to the editor.

If you see this output after 1-5 minutes (depending on the image and partitioning you're using), the system is ready and bootable.

The root password is set to the current password of the Rescue System.

After a reboot in the Rescue System,

root@rescue ~ # reboot

the newly installed system is booted and you can log in with the previous Rescue System password.

 


Was this answer helpful?