From ArchWiki
Jump to navigation Jump to search

Archboot is an unofficial set of scripts to generate bootable media for CD/USB/PXE, designed for installation or rescue operation.

It only runs in RAM, without any special filesystems like squashfs, thus it is limited to the RAM which is installed in your system.


Install the archboot package.

The difference to the archiso install media

  • It provides an additional interactive setup and quickinst script.
  • It contains [core] repository on media.
  • It runs a modified Arch Linux system in initramfs.
  • It is restricted to RAM usage, everything which is not necessary like
man or info pages etc. is not provided.
  • It does not mount anything during boot process.
  • It supports remote installation through ssh.
  • It uses netctl for network setup.

Archboot ISO Releases

  • Hybrid image files and torrents are provided, which include x86_64 and [core] repository,
network labeled images do not include [core] repository.
kernel: 5.7.9.arch1-1
pacman: 5.2.2-1
systemd: 245.6-8
RAM recommendations: 2048 MB

Burning Release

Hybrid image file is a standard CD-burnable image and also a raw disk image.

  • Can be burned to CD(RW) media using most CD-burning utilities.
  • Can be raw-written to a drive using 'dd' or similar utilities. This method is intended for use with USB thumb drives.
'dd if=<imagefile> of=/dev/<yourdevice> bs=1M'

PXE booting / Rescue system

Download 2020.07 „2k20-R1“ needed files from the directory.

  • vmlinuz_x86_64 + initramfs_x86_64.img(x86_64)
  • intel-ucode.img (x86_64)
  • For PXE booting add the kernel and initrd to your tftp setup and you will get a running installation/rescue system.
  • For Rescue booting add an entry to your bootloader pointing to the kernel and initrd.

Supported boot modes of Archboot media

  • It supports BIOS booting with syslinux.
  • It supports UEFI/UEFI_CD booting with systemd-boot and EFISTUB.
  • It support UEFI_MIX_MODE booting with grub.
  • It supports Secure Boot with prebootloader.
  • It supports grub(2)'s iso loopback support.
variables used (below for example):
menuentry "Archboot" --class iso {
loopback loop (hdX,X)/<archboot.iso>
linux (loop)/boot/vmlinuz_x86_64 iso_loop_dev=/dev/sdXX iso_loop_path=/<archboot.iso>
initrd (loop)/boot/initramfs_x86_64.img
  • It supports booting using syslinux's memdisk (only in BIOS mode).
menuentry "Archboot Memdisk" {
   linux16 /memdisk iso
   initrd16 hd(X,X)/<archboot.iso>

How to do a remote installation with ssh?

  • During boot all network interfaces will try to obtain an IP address through dhcp.
  • root password is not set by default! If you need privacy during installation set a password.
'ssh root@<yourip>'

Interactive setup features

  • Media and Network installation mode
  • Changing keymap and consolefont
  • Changing time and date
  • Setup network with netctl
  • Preparing storage disk, like auto-prepare, partitioning, GUID (gpt) support, 4k sector drive support etc.
  • Creation of software raid/raid partitions, lvm2 devices and luks encrypted devices
  • Supports standard linux,raid/raid_partitions,dmraid/fakeraid,lvm2 and encrypted devices
  • Filesystem support: ext2/3/4, btrfs, f2fs, nilfs2, reiserfs,xfs,jfs,ntfs-3g,vfat
  • Mount support of grub(2) loopback and memdisk installation media
  • Package selection support
  • hwdetect script is used for preconfiguration
  • Auto/Preconfiguration of fstab, kms mode, ssd, mkinitcpio.conf, systemd, crypttab and mdadm.conf
  • Configuration of basic system files
  • Setting root password
  • grub(2) (BIOS and UEFI), refind-efi, systemd-boot, syslinux (BIOS and UEFI) bootloader support

FAQ, Known Issues and limitations

  • Release specific known issues and workarounds are posted in changelog files.
  • Check also the forum threads for posted fixes and workarounds.
  • Why screen stays blank or other weird screen issues happen?
Some hardware does not like the KMS activation, use radeon.modeset=0, i915.modeset=0 or nouveau.modeset=0 on boot prompt.
  • dmraid/fakeraid might be broken on some boards, support is not perfect here.
The reason is there are so many different hardware components out there. At the moment 1.0.0rc16 is included, with latest fedora patchset, development has been stopped.
mdadm supports some isw and ddf fakeraid chipsets, but assembling during boot is deactivated in /etc/mdadm.conf!
  • grub2 cannot detect correct bios boot order:
It may happen that hd(x,x) entries are not correct, thus first reboot may not work.
Reason: grub cannot detect bios boot order.
Fix: Either change bios boot order or change menu.lst to correct entries after successful boot. This cannot be fixed it is a restriction in grub2!


History of old releases can be found here.


Arch Linux Bugtracker

Archboot BETA ISO Release

  • Hybrid image file is provided, which only supports network installation.
  • Please read the according Changelog files for RAM limitations.
  • Please check md5sum before using it.
  • No beta ISO available at the moment.


Howto: Create image files

(Quick regeneration of installation media with latest available core packages)


  • ~ 7GB free space on disk

Create archboot chroot

  • Install archboot:

run as root:

mkdir -p x86_64_chroot/var/lib/pacman
pacman --root "x86_64_chroot" -Sy base archboot --noconfirm --noprogressbar
  • Enter archboot first usage x86_64 container:

Start container, run as root:

systemd-nspawn --capability=CAP_MKNOD --register=no -M archboot -D x86_64_chroot

Generate localisation:

echo "en_US ISO-8859-1" >> /etc/locale.gen
echo "en_US.UTF-8 UTF-8" >> /etc/locale.gen

Configure pacman:

vim /etc/pacman.d/mirrorlist
pacman-key --init
pacman-key --populate archlinux

reinstall linux to get images in /boot:

pacman -S linux

Update to latest packages

update to latest available packages.

Generate images

  • Startup container, run as root:
systemd-nspawn --capability=CAP_MKNOD --register=no -M archboot -D x86_64_chroot
  • Allow loop devices, run in main system as root:
echo 'b 7:* rwm' > /sys/fs/cgroup/devices/machine.slice/archboot.scope/devices.allow
echo 'c 10:237 rwm' > /sys/fs/cgroup/devices/machine.slice/archboot.scope/devices.allow
  • Create images, run in container (needs quite some time ...) -t -g
  • Finished you get a bunch of images.