Chroot Rescue & Installer

FAQ

Q: The software I need is not available in Live Rescue. Can I install it somehow?

A: Please configure and start networking, then use poldek (TLD Linux package manager) to install the desired packages. Keep in mind that CRI system work in RAM. If you fill CRI filesystem, you will also fill your RAM and CRI system will probably crash badly. By default, CRI uses 1GB of RAM for the root filesystem. If you need more, please edit CRI boot options and change rootfssize=1GB to the desired value.

Q: How the hell can I install something using this poldek thing?

A: Run poldek -i some-package or just poldek for interactive mode where you can do install some-package. For more information about using poldek see poldek --help from shell or help while in interactive mode.

Q: Can I create bootable USB disk with CRI?

A: Yes, you can. You need to install GRUB2 on your USB disk and copy contents of CRI .iso image to it. To install GRUB2 run the following command: grub-install --force --no-floppy --boot-directory=/mnt/usb/boot /dev/sdX where /mnt/usb is the directory where your USB disk is mounted and /dev/sdX is the device name assigned to your USB disk.

Q: Can I add CRI to GRUB2 on my server/computer/VM?

A: Of course you can. Just download the boot images for your architecture (or extract them from any CRI .iso image), place them in /boot and add the following entry to your GRUB2 configuration, for x86_64 architecture:

menuentry "Chroot Rescue & Installer" {
  linux /boot/vmlinuz.x64 rootfstype=tmpfs rootfssize=1G net.ifnames=0
  initrd /boot/cri.x64.cpi /boot/mod.x64.cpi
}

or for i686 architecture:

menuentry "Chroot Rescue & Installer" {
  linux /boot/vmlinuz.x86 rootfstype=tmpfs rootfssize=1G net.ifnames=0
  initrd /boot/cri.x86.cpi /boot/mod.x86.cpi
}

If you have enough RAM and need more space while using CRI, you can adjust the boot option rootfssize to change the size of the CRI root filesystem.

You may also need to change the net.ifnames value, depending on the system you are installing or recovering. See next question for details.

Q: CRI created network configuration for device eth0, but installed system uses name ens33 and network does not work. How can I force CRI to use correct network interface names?

A: Network interface naming is controlled by udev and depends on the value of the net.ifnames kernel boot option. If set to 0 (default), CRI will use legacy network interface names such as eth0, eth1 and so on. If set to 1, CRI will use predictable network interface names such as ens33, enp2s1 or eno1.

Note that despite enabling predictable network interface names, legacy ethX names may still be used if udev is unable to determine the interface name.

The value of net.ifnames, and therefore the network interface names, must match between CRI and the system being installed/recovered for the CRI Network Configurator to work correctly.

When installing a system image with CRI, you will be asked whether you prefer to use legacy or predictable network interface names on the installed system.

Q: Can I customize CRI for my needs?

A: No. CRI development environment is not be publicly available.