This page explains how to perform a regular Arch installation onto removable media (e.g. a USB flash drive). In contrast to having a LiveUSB as covered in USB flash installation media, the result will be a persistent installation identical to normal installation to HDD.
Installation
The other day I was testing the latest Arch Linux live ISO in VirtualBox. Before installing Arch Linux on disk, I booted into the live system and wanted to try some applications to see how it performs in Arch Linux. As expected, everything worked fine out of the box. I started to install some more applications as well. Arch linux is extremely simple OS. It is made for people who want to build a system for themselves, i.e. It does not come with packages that you don't need. That means, you have to install by yourself almost everything you need, including window system. Arch Linux ARM is a distribution of Linux for ARM computers. We provide targeted kernel and software support for soft-float ARMv5te, hard-float ARMv6 and ARMv7, and ARMv8 AArch64 instruction sets on a variety of consumer devices and development platforms. Arch Linux USB OS Arch Linux Live USB Brought to you by: prrats. Downloads: 47 This Week Last Update: 7 days ago. Get project updates, sponsored content from our select partners, and more. Discussions specifically regarding the Arch Linux distribution and community. NOT generally a place for technical issues unless systemic in nature. ( Moderated by 2ManyDogs, ewaller, fukawi2, HalosGhost, R00KIE, Slithery, V1del, WorMzy, Xyne).
There are various ways of installing Arch on removable media, depending on the operating system you have available:
- If you have another Linux computer available (it need not be Arch), you can follow the instructions at Install from existing Linux.
- An Arch Linux CD/USB can be used to install Arch onto the removable medium, via booting the CD/USB and following the installation guide. If booting from a Live USB, the installation cannot be made to the same removable medium you are booting from.
- If you run Windows or macOS, download VirtualBox, install VirtualBox Extensions, attach your removable medium to a virtual machine running Linux (either already installed or via a live ISO), and point the installation into the now attached drive while using the instructions at the Installation guide.
Installation tweaks
- Before creating the initial RAM disk, in
/etc/mkinitcpio.conf
move theblock
andkeyboard
hooks before theautodetect
hook. This is necessary to allow booting on multiple systems each requiring different modules in early userspace. - If you have chosen to install Arch onto a USB mass storage device and want to be able to continue to use it as a cross-platform removable drive, this can be accomplished by creating a partition housing an appropriate file system (most likely NTFS or exFAT). Note that the data partition may need to be the first partition on the device, as Windows assumes that there can only be one partition on a removable device, and will happily automount an EFI system partition otherwise. Remember to install dosfstools and ntfs-3g. Some tools are available online that may allow you to flip the Removable Medium Bit (RMB) on your USB mass storage device. This would trick operating systems into treating your USB mass storage device as an external hard disk and allow you to use whichever partitioning scheme you choose.
- If your Arch installation is on a removable drive that needs to have microcode for both manufacturer processors, install both amd-ucode and intel-ucode packages. See Microcode#Installation.
Configuration
- Make sure that
/etc/fstab
includes the correct partition information for/
, and for any other partitions on the disk. If the drive is to be booted on several machines, it is quite likely that devices and number of available hard disks vary. So it is advised to use UUID or label.
To get the proper UUIDs for your partitions use lsblk of blkid. See Persistent block device naming#by-uuid for more information.
Note:- When GRUB is installed on the disk, the disk will always be
hd0,0
. - It seems that current versions of GRUB will automatically default to using uuid. The following directions are for GRUB legacy.
GRUB legacy
menu.lst
, the GRUB legacy configuration file, should be edited to (loosely) match the following.
When using file system labels your menu.lst
should look like this:
And for UUID, it should be like this:
GRUB
Follow the instructions on GRUB#BIOS systems and GRUB#UEFI systems to install GRUB for both BIOS and UEFI booting:
/boot/grub/device.map
already exists. You should use this option whenever you add/remove a disk into/from your computer. [1]Syslinux
Using your UUID:
Tips and tricks
Using your portable install on multiple machines
Compatibility for BIOS systems
This article or section needs expansion.
Since this setup will be run on multiple machines and there are still plenty of BIOS only systems around, you might want to consider enabling compatibility for both UEFI GPT and BIOS GPT/MBR systems. See Multiboot USB drive#Hybrid UEFI GPT + BIOS GPT/MBR boot
Video drivers
Note:- The use of proprietary video drivers is not recommended for this type of installation.
- See the note about xf86-video-intel in Intel graphics#Installation.
To support most common GPUs, install xf86-video-vesa, xf86-video-ati, xf86-video-intel, xf86-video-amdgpu, xf86-video-nouveau and xf86-video-fbdev.
Persistent block device naming
It is recommended to use UUID in both fstab and boot loader configuration. See Persistent block device naming for details.
Alternatively, you may create udev rule to create custom symlink for your disk. Then use this symlink in fstab and boot loader configuration. See udev#Setting static device names for details.
Kernel parameters
You may want to disable KMS for various reasons, such as getting a blank screen or a 'no signal' error from the display, when using some Intel video cards, etc. To disable KMS, add nomodeset
as a kernel parameter. See Kernel parameters for more info.
nomodeset
as a kernel parameter as a preemptive measure you may have to adjust the display resolution manually when using machines with Nvidia video cards. See Xrandr for more info.Compatibility
The fallback image should be used for maximum compatibility.
Minimizing disk access
When installing to a device that offers a limited number of writes before it wears out, such as a USB drive, SD card, or similar, reduce the number of writes to increase the device lifetime. This also reduces the performance impact of slow writes.
- It is highly recommended to review the Improving performance#Reduce disk reads/writes article prior to selecting a file system. To sum it up, for flash-based media such as USB flash drives or SD cards, ext4 without a journal should be fine, which can be created with
mkfs.ext4 -O '^has_journal' /dev/sdXX
. The obvious drawback of using a file system with journaling disabled is data loss as a result of an ungraceful dismount. Recognize that flash has a limited number of writes, and a journaling file system will take some of these as the journal is updated. For this same reason, it is best to forget the swap partition. Note that this does not affect installing onto a portable hard drive. - You may want to configure systemd journal to store its journals in RAM, e.g. by creating a custom configuration file:
- To disable
fsync
and related system calls in web browsers and other applications that do not write essential data, use theeatmydata
command from libeatmydata to avoid such system calls:
See also
- ALMA - A utility written in Rust to automatically create persistent Arch Linux Live USB installations.
- ArchLinux USB - c-magyar's excellent writeup on creating a persistent Live USB installation.
- archuseriso - Profiles for building Arch Linux Live ISO images. Bootable USB drives creation tools featuring persistent storage and encryption.
Arch Linux Netboot
About Netboot
Netboot images are small (<1MB) images that can be used to download the latest Arch Linux release on the fly upon system boot.It is unnecessary to update the netboot image, the newest release will be available automatically.
Netboot uses customized iPXE builds.The Linux kernel, initramfs and squashfs files for the live system are downloaded from an Arch Linux mirror.The integrity of all downloaded files is verified with cryptographic signatures.
Requirements
Arch Linux Livecd
To use netboot, the following requirements must be met:
- Wired (ethernet) internet connection with DHCP autoconfiguration
- Sufficient memory to store and run the live system
Download
Arch Linux Live Image
BIOS
- ipxe.lkrn (PGP signature) - Linux kernel-like image that can be started with any Linux bootloader
- ipxe.pxe (PGP signature) - PXE image for chainloading from a PXE environment
UEFI
Arch Linux Live Distro
- ipxe.efi (PGP signature) - x86_64 UEFI executable
You can build your own iPXE images compatible with netboot.For details, check out the ipxe-netboot AUR package.
More information
Linux Os Download 32 Bit
For detailed usage instructions, check out the netboot wiki page.
Comments are closed.