Install Arch Linux from existing Linux (简体中文)
本指南给出了从当前 Linux 发行版安装 Arch Linux 所需的准备步骤。 准备完成后的安装参考Installation guide (简体中文)。
从当前 Linux 发行版安装 Arch Linux 对以下情形有所帮助：
- 远程安装 Arch Linux，如一台（虚拟的）根服务器
- 无需 LiveCD 替换当前 Linux 发行版（参见#无 LiveCD 替换当前系统）
- 创建基于 Arch Linux 的新 Linux 发行版或 LiveCD
- 创建 Arch Linux 的 chroot 环境，如可为 Docker 基础容器创建
- 为无盘机器准备 rootfs-over-NFS
这些准备步骤的目的在于为搭建一个 arch-install-scripts（如 pacstrap 和 arch-root）可运行的环境。
这个目的可通过在当前系统安装 arch-install-scripts 或搭建基于 Arch Linux-based 的 chroot 环境达成。
若当前发行版为 Arch Linux，可直接安装 arch-install-scripts。
从一个主机运行Arch Linux
安装 arch-install-scripts 通过 official repositories.
安装和配置
参考 Installation guide#Mount the partitions[broken link: invalid section]。如果 /mnt文件夹已经被占用 , 只要新建一个文件夹，比如 /mnt/install用来替代即可。
然后参考 Installation guide#Installation。你可以跳过 Installation guide#Select the mirrors，因为主机中应该已经有了合适的镜像列表。
从一个主机运行另一个Linux发行版
下列是多个可以自动处理大量步骤的工具。具体方法可以参考他们各自主页的相关说明。
- arch-bootstrap (Bash)
- image-bootstrap (Python)
- vps2arch (Bash)
- archcx (Bash, from Hetzner CX Rescue System)
以下是介绍手动处理的办法。具体思路是在主机系统中运行Arch系统，并且是在Arch系统中进行的实际安装。这个嵌套系统是位于chroot中。
创建 chroot
以下是两个创建并进入chroot的方法，从最简单到最复杂。二者选其一，然后参考#Using the chroot environment[broken link: invalid section].
方法一：使用 Bootstrap 镜像（推荐）
从镜像站下载 bootstrap 镜像：
$ curl -O https://mirrors.kernel.org/archlinux/iso/latest/archlinux-bootstrap-2018.05.01-x86_64.tar.gz
解压 tarball：
# cd /tmp # tar xzf <path-to-bootstrap-image>/archlinux-bootstrap-2017.08.01-x86_64.tar.gz
选择软件仓库服务器：
# nano /tmp/root.x86_64/etc/pacman.d/mirrorlist
进入 chroot
- 若安装了4或更高版本的 bash：
# /tmp/root.x86_64/bin/arch-chroot /tmp/root.x86_64/
- 若无，执行：
# cd /tmp/root.x86_64
# cp /etc/resolv.conf etc
# mount --rbind /proc proc
# mount --rbind /sys sys
# mount --rbind /dev dev
# mount --rbind /run run
（假设 /run 存在）
# chroot /tmp/root.x86_64 /bin/bash
方法二：使用 LiveCD 镜像
挂载最新的 Arch Linux 安装介质并 chroot 是可能的。这种方法为当前系统提供了可运作的 Arch Linux 安装程序而无需另外准备。
- 依据构架的不同，根镜像能在镜像站的 arch/x86_64/ 或 arch/i686/ 目录下找到。squashfs 格式无法编辑，因此需要解压出根镜像并挂载。
- 解压，运行
# unsquashfs -d /squashfs-root root-image.fs.sfs
- 以 loop 挂载根镜像
# mkdir /arch # mount -o loop /squashfs-root/root-image.fs /arch
- chroot 前需设置些挂载点并为网络连接复制 resolv.conf。
# mount -t proc none /arch/proc # mount -t sysfs none /arch/sys # mount -o bind /dev /arch/dev # mount -o bind /dev/pts /arch/dev/pts # pacman 所需（用于签名检查） # cp -L /etc/resolv.conf /arch/etc # 网络连接所需
- 准备完毕，chroot 入新系统
# chroot /arch bash
使用 chroot 环境
初始化 pacman 密匙环
开始安装前，需要设置 pacman 密匙。执行以下命令前请阅读Pacman-key (简体中文)#初始化密钥环以理解其对熵的要求：
# pacman-key --init # pacman-key --populate archlinux
选择镜像和下载基本工具
After selecting a mirror, refresh the package lists and install what you need: base, base-devel, parted etc.
安装提示
请按照Installation guide (简体中文)中的挂载分区[broken link: invalid section]和安装基本系统[broken link: invalid section]小节进行安装。
基于 Debian 的当前系统
/dev/shm
在基于 Debian 的当前系统上，pacstrap 会发生以下错误：
# pacstrap /mnt base # ==> Creating install root at /mnt # mount: mount point /mnt/dev/shm is a symbolic link to nowhere # ==> ERROR: failed to setup API filesystems in new root
Debian 中，/dev/shm 指向 /run/shm。而在基于 Arch 的 chroot 中，/run/shm 并不存在，因而链接失效。创建 /run/shm 目录可修复此错误：
# mkdir /run/shm
/dev/pts
While installing archlinux-2015.07.01-x86_64 from a Debian 7 host, the following error prevented both pacstrap and arch-chroot from working:
# pacstrap -i /mnt
mount: mount point /mnt/dev/pts does not exist ==> ERROR: failed to setup chroot /mnt
Apparently, this is because these two scripts use a common function. chroot_setup()[1] relies on newer features of util-linux, which are incompatible with Debian 7 userland (see FS#45737).
The solution for pacstrap is to manually execute its various tasks, but use the regular procedure to mount the kernel filesystems on the target directory ("$newroot"):
# newroot=/mnt
# mkdir -m 0755 -p "$newroot"/var/{cache/pacman/pkg,lib/pacman,log} "$newroot"/{dev,run,etc}
# mkdir -m 1777 -p "$newroot"/tmp
# mkdir -m 0555 -p "$newroot"/{sys,proc}
# mount -t proc /proc "$newroot/proc"
# mount --rbind /sys "$newroot/sys"
# mount --rbind /run "$newroot/run"
# mount --rbind /dev "$newroot/dev"
# pacman -r "$newroot" --cachedir="$newroot/var/cache/pacman/pkg" -Sy base base-devel ... ## add the packages you want
# cp -a /etc/pacman.d/gnupg "$newroot/etc/pacman.d/" ## copy keyring
# cp -a /etc/pacman.d/mirrorlist "$newroot/etc/pacman.d/" ## copy mirrorlist
Instead of using arch-chroot for Installation guide#Chroot, simply use chroot "$newroot".
lvmetad
Trying to create LVM logical volumes from an archlinux-bootstrap-2015.07.01-x86_64 environment on a Debian 7 host resulted in the following error:
# lvcreate -L 20G lvm -n root
/run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. /dev/lvm/root: not found: device not cleared Aborting. Failed to wipe start of new LV.
(Physical volume and volume group creation worked despite /run/lvm/lvmetad.socket: connect failed: No such file or directory being displayed.)
This could be easily worked around by creating the logical volumes outside the chroot (from the Debian host). They are then available once chrooted again.
Also, if the system you are using has lvm, you might have the following output:
# grub-install --target=i386-pc --recheck /dev/mapper/main-archroot
Installing for i386-pc platform. /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
This is because debian does not use lvmetad by default. You need to edit /etc/lvm/lvm.conf and set use_lvmetad to 0:
use_lvmetad = 0
This will trigger later an error on boot in the initrd stage. Therefore, you have to change it back after the grub generation. In a software RAID + LVM, steps would be the following:
- After installing all the system, when you have to do all the initramfs (mkinitcpio) and grub thing.
- Change /etc/mdadm.conf to reflect your RAID config (if any)
- Change HOOKS and MODULES according to lvm and raid requirements:
MODULES="dm_mod" HOOKS="base udev mdadm_udev ... block lvm2 filesystems ..." - Generate initrd images with mkinitcpio
- Change /etc/lvm/lvm.conf to put use_lvmetad = 0
- Generate grub config (grub-mkconfig)
- Change /etc/lvm/lvm.conf to put use_lvmetad = 1
基于Fedora的当前系统
On Fedora based hosts and live USBs you may encounter problems when using genfstab to generate your fstab. Remove duplicate entries and the "seclabel" option where it appears, as this is Fedora-specific and will keep your system from booting normally.
无 LiveCD 替换当前系统
在硬盘上划分出 ~650MB 的空闲空间，如分割 swap 分区。若空闲空间小于 600 MB，则须筛选软件包，恰好使系统能在该分区上运行建立网络连接。这意味着需要为 pacstrap 通过选项 -c 指定软件包，以免占满了宝贵的空间。
一旦完成安装，重启进入该系统并rsync 整个系统至主分区。 重启前须修改引导器配置。
配置系统
请按照Installation guide (简体中文)中的挂载分区[broken link: invalid section]及余下小节完成配置。