Setting up disks manually: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
* Call [[Alpine_setup_scripts#setup-disk|setup-disk]] directly, instead of through <code>setup-alpine</code>, and pass some specific partitioning parameters to it. | * Call [[Alpine_setup_scripts#setup-disk|setup-disk]] directly, instead of through <code>setup-alpine</code>, and pass some specific partitioning parameters to it. | ||
* | * Set up the partitions and filesystems manually (to the desired details) and [[Alpine_setup_scripts#Partitioning|tell setup-disk]] to install to the prepared target mountpoint. | ||
| Line 15: | Line 15: | ||
== For "diskless" and "data" disk mode installs == | == For "diskless" and "data" disk mode installs == | ||
This requires some manual steps, as long as the setup-scripts | This requires some manual steps, as long as the setup-scripts auto-detect usable partitions only on *removable* devices (not internal harddisks). They do not support creating new, writable partitions to be used by Alpine. | ||
How to prepare writable storage space is explained in the section | How to prepare writable storage space is explained in the section [[Setting_up_disks_manually#Manual_partitioning| manual partitioning]], below. | ||
== For "sys" disk mode installs == | == For "sys" disk mode installs == | ||
| Line 25: | Line 25: | ||
=== Disk layouts === | === Disk layouts === | ||
It is possible to have one or more of RAID, | It is possible to have one or more of RAID, encrypted, and/or Logical Volume on your {{Path|/}} (root) volume. However, the Alpine init script only knows how to handle them when they're layered in that order, and your initram and extlinux.conf files in the {{Path|/boot}} partition are configured properly. | ||
Your {{Path|/boot}} cannot reside on an encrypted or LVM volume, at least not with Alpine's default bootloader (extlinux). (Grub2 can deal with {{Path|/boot}} being on an LVM volume.) The usual practice is to create a small partition for {{Path|/boot}}, | Your {{Path|/boot}} directory cannot reside on an encrypted or LVM volume, at least not with Alpine's default bootloader (extlinux). (Grub2 can deal with {{Path|/boot}} being on an LVM volume.) The usual practice is to create a small partition for {{Path|/boot}}, then devote the rest of your disk to a separate partition on which you layer one or more of RAID, encryption, and/or Logical Volumes. | ||
Sometimes {{Path|/boot}} is also | Sometimes {{Path|/boot}} is also set up as a mirrored (RAID1) volume. However, this is just for post-init access. That way, when you write a new kernel or bootloader config file to {{Path|/boot}}, it gets written to multiple physical partitions. During the pre-init, bootloader phase, only one of those partitions will be read from. | ||
A typical setup might look like this: | |||
<pre> | <pre> | ||
| Line 74: | Line 74: | ||
</pre> | </pre> | ||
In a three-disk system, the {{Path|/boot}} would still be RAID1, but the larger partition might in that case be RAID5. | In a three-disk system, the {{Path|/boot}} would still be RAID1, but the larger partition might, in that case, be RAID5. | ||
| Line 81: | Line 81: | ||
<code>setup-disk</code> will automatically build a RAID array if you supply the '''-r''' switch, or if you specify more than one device. | <code>setup-disk</code> will automatically build a RAID array if you supply the '''-r''' switch, or if you specify more than one device. | ||
If you | If you want to build your RAID array manually, see [[Setting up a software RAID array]]. Then you can add additional layers of encryption and/or Logical Volumes, or just assemble the RAID array, and supply the {{Path|/dev/md<i>i</i>}} device directly to [[setup-disk]]. When you're finished, be sure to disassemble the RAID array before rebooting. | ||
If <code>setup-disk</code> sees that you're using RAID | If <code>setup-disk</code> sees that you're using RAID, either because you gave it the <code>-r</code> switch, or multiple devices, or a {{Path|/dev/md<i>i</i>}} device, then it will set up your initramfs and extlinux.conf file properly. However, in other cases, such as when you're also using encryption, or you invoke <code>setup-disk</code> with a mounted directory argument, these might not be properly set up for RAID. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into: | ||
{{Cmd|1=echo "/sbin/mdadm" > $MNT/etc/mkinitfs/files.d/raid | {{Cmd|1=echo "/sbin/mdadm" > $MNT/etc/mkinitfs/files.d/raid | ||
| Line 102: | Line 102: | ||
=== Encryption === | === Encryption === | ||
See [[Setting up encrypted volumes with LUKS]]. | See [[Setting up encrypted volumes with LUKS]]. You can add an additional Logical Volume layer, or just unlock the volume you've created (using <code>cryptsetup luksOpen ...</code>), and supply the {{Path|/dev/mapper/<i>something</i>}} device directly to [[setup-disk]]. When you're finished, be sure to relock the volume (using <code>cryptsetup luksClose ...</code>) before rebooting. | ||
If you install your {{Path|/}} (root) on an encrypted volume, you'll need to manually edit/rebuild your initram and your extlinux.conf file. The following assumes that <code>$MNT</code> holds the root directory you're installing into, that you've created the cryptvolume on the device {{Path|/dev/md2}}, and that you want to unlock the encrypted volume into a virtual volume named "crypt": | If you install your {{Path|/}} (root) on an encrypted volume, you'll need to manually edit/rebuild your initram and your extlinux.conf file. The following assumes that <code>$MNT</code> holds the root directory you're installing into, that you've created the cryptvolume on the device {{Path|/dev/md2}}, and that you want to unlock the encrypted volume into a virtual volume named "crypt": | ||
| Line 131: | Line 131: | ||
If <code>setup-disk</code> sees that you're using LVM | If <code>setup-disk</code> sees that you're using LVM, perhaps because you gave it the <code>-L</code> switch, then it will set up your initram and extlinux.conf file properly. However, in other cases, these might not be properly set up. In that case, you may need to manually edit/rebuild them. The following assumes that <code>$MNT</code> holds the root directory you're installing into: | ||
{{Cmd|1=# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..." | {{Cmd|1=# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..." | ||
| Line 152: | Line 152: | ||
== For "diskless" and "data" disk mode installs == | == For "diskless" and "data" disk mode installs == | ||
The enviroment | The installation image enviroment may have only the very basic busybox built-in <code>fdisk</code> command available. However, alpine allows you to install more complete partitioning tool packages like <code>sfdisk</code> (scriptable fdisk), <code>gptfdisk</code>, <code>parted</code> (CLI), <code>cfdisk</code> (text menus), or even <code>gparted</code> (after [[Installation#Post-Install|setting up a graphical environment]]). | ||
The following example installs <code>cfdisk</code>, looks for existing partitions, and | The following example installs <code>cfdisk</code>, looks for existing partitions, and runs cfdisk against <code>/dev/sdX</code>: | ||
# apk add cfdisk | # apk add cfdisk | ||
# blkid | # blkid | ||
| Line 162: | Line 162: | ||
* Be aware of this Bug: [https://gitlab.alpinelinux.org/alpine/aports/-/issues/11589 The APKOVL loading of diskless setups doesn't work on btrfs and xfs filesystems, or nvme-based devices] => So, for the moment, use | * Be aware of this Bug: [https://gitlab.alpinelinux.org/alpine/aports/-/issues/11589 The APKOVL loading of diskless setups doesn't work on btrfs and xfs filesystems, or nvme-based devices] => So, for the moment, use only ext4 filesystem partitions on classic drives to store diskless mode states. | ||
The following creates an ext4 partition with disabled journaling, to reduce write operations and allow the disk to spin down after the .apkovl and the packages have been read from the partition during the boot. | The following creates an ext4 partition with disabled journaling, to reduce write operations and allow the disk to spin down after the .apkovl and the packages have been read from the partition during the boot. | ||
# apk add e2fsprogs | # apk add e2fsprogs | ||
# mkfs.ext4 -O ^has_journal /dev/sdXY # the "-O ^has_journal" DISABLES journaling ("^" | # mkfs.ext4 -O ^has_journal /dev/sdXY # the "-O ^has_journal" DISABLES journaling ("^" means "not") | ||
{{Note|IMPORTANT! There may | {{Note|IMPORTANT! There may be additional steps necessary to make proper use of the partition, see | ||
[[Alpine_local_backup#Saving_and_loading_ISO_image_customizations|Saving_and_loading_ISO_image_customizations]]. | [[Alpine_local_backup#Saving_and_loading_ISO_image_customizations|Saving_and_loading_ISO_image_customizations]]. | ||
}} | }} | ||
| Line 174: | Line 174: | ||
== For "sys" disk mode installs == | == For "sys" disk mode installs == | ||
<code>setup-disk</code> will by default set up a root partition, a separate /boot partition and a swap. If you want a different layout you can manually create the partitions, filesystems and mount them | <code>setup-disk</code> will by default set up a root partition, a separate /boot partition and a swap partition. If you want a different layout, you can manually create the partitions, filesystems and mount them on {{Path|/mnt}} (or any other mount point) then run: | ||
{{Cmd|setup-disk /mnt}} | {{Cmd|setup-disk /mnt}} | ||
<code>setup-disk</code> will install your running system on the mounted root, detect your file system layout and generate | <code>setup-disk</code> will install your running system on the mounted root, detect your file system layout and generate an fstab. | ||
If you're | If you're using the MBR, you are responsible for making the proper partition bootable and make sure the MBR is OK for extlinux. If you're going to use EFI, make sure you set <code>BOOTLOADER=grub</code> and <code>USE_EFI=1</code>, and that {{Pkg|grub-efi}} and {{Pkg|efibootmgr}} are installed before running <code>setup-disk</code>. | ||
See also [https://github.com/itoffshore/alpine-linux-scripts setup-partitions] | See also [https://github.com/itoffshore/alpine-linux-scripts setup-partitions] | ||
| Line 210: | Line 210: | ||
<!-- | <!-- | ||
== Setting up | == Setting up RAID == | ||
Set up a raid array as described [[Setting up a software RAID1 array|here]]. | Set up a raid array as described [[Setting up a software RAID1 array|here]]. | ||
In this document two raid arrays are configured: md0 for swap (512MB) and md1 for /var. | In this document, two raid arrays are configured: md0 for swap (512MB) and md1 for /var. | ||
== Create filesystem == | == Create filesystem == | ||
| Line 240: | Line 240: | ||
== Move the data == | == Move the data == | ||
Stop aall services running that put anything in /var (syslog for example). If you have booted on a clean installation and not run setup-alpine, then no services should be running. However, some packages might have created dirs in /var, so we need to backup /var, mount the new /var directory and move all backed up dirs to the raided /var. | |||
mv /var /var.tmp | mv /var /var.tmp | ||
| Line 277: | Line 277: | ||
chmod +x /etc/init.d/mountdisk | chmod +x /etc/init.d/mountdisk | ||
'''NOTE:''' Since Alpine-1.7.3 | '''NOTE:''' Since Alpine-1.7.3 a script named ''localmount'' is included so you will not need to create your own ''mountdisk'' script. | ||
/var needs to be mounted *after* raid is created. The -k option will make alpine unmount the /var partition during boot. Add start swap to boot: | |||
rc_add -k -s 06 mountdisk | rc_add -k -s 06 mountdisk | ||
rc_add -k -s 06 swap | rc_add -k -s 06 swap | ||
The /dev/md* device nodes will not be created automatically so we need to put | The /dev/md* device nodes will not be created automatically, so we need to put them on floppy too. | ||
lbu include /dev/md* | lbu include /dev/md* | ||
| Line 291: | Line 291: | ||
ln -s /var/home/* /home/ | ln -s /var/home/* /home/ | ||
'''NOTE:''' You cannot just replace /home with a link that points to /var/home since the base has a /home directory. When the | '''NOTE:''' You cannot just replace /home with a link that points to /var/home since the base has a /home directory. When the system tries to copy the config from floppy it will fail because of the already existing /home directory. | ||
Make sure the links are stored to floppy: | Make sure the links are stored to floppy: | ||
| Line 305: | Line 305: | ||
lbu commit floppy | lbu commit floppy | ||
== Test | == Operational Test == | ||
Reboot computer. Now | Reboot computer. Now the raid should start and /var should be mounted. Check with df: | ||
~ $ df | ~ $ df | ||
Filesystem 1k-blocks Used Available Use% Mounted on | Filesystem 1k-blocks Used Available Use% Mounted on | ||
| Line 315: | Line 315: | ||
== Upgrades == | == Upgrades == | ||
Since the package database is | Since the package database is on disk, you cannot update by simply replacing the CDROM. You will have to either run the upgrade on the new CDROM or run ''apk_add -u ... && update-conf'' manually. | ||
--> | --> | ||
== Setting up swap == | == Setting up swap == | ||
# create partition with type "linux swap" (82) (If you're going to use | # create a partition with the type set to "linux swap" (82) (If you're going to use a logical volume for swap, skip this step and <code>lvcreate</code> that instead.) | ||
# <code>mkswap /dev/sda2</code> | # <code>mkswap /dev/sda2</code> | ||
# <code>echo -e "/dev/sda2 none swap sw 0 0" >> /mnt/etc/fstab</code> | # <code>echo -e "/dev/sda2 none swap sw 0 0" >> /mnt/etc/fstab</code> | ||
# <code>swapon /dev/sda2</code> (or <code>rc-service swap start</code>) | # <code>swapon /dev/sda2</code> (or <code>rc-service swap start</code>) | ||
{{Cmd|free -m}} will show how much swap space is available (in MB). | |||
If you prefer maximum speed, you don't need configure any raid devices for swap. Just add 2 swap partitions on different disks and linux will stripe them automatically. The downside is that | If you prefer maximum speed, you don't need configure any raid devices for swap. Just add 2 swap partitions on different disks and linux will stripe them automatically. The downside is that the moment one disk fails, the system will go down. For better reliability, put swap on RAID1. | ||
{{Todo|Instructions for cryptswap?}} | {{Todo|Instructions for cryptswap?}} | ||
Revision as of 15:12, 28 June 2021
The menu choices that are provided by setup-alpine can not cover all needs, however, it's possible to:
- Call setup-disk directly, instead of through
setup-alpine, and pass some specific partitioning parameters to it. - Set up the partitions and filesystems manually (to the desired details) and tell setup-disk to install to the prepared target mountpoint.
(Beta refenence: beta.docs.alpinelinux.org )
Using setup-alpine (setup-disk) features
For "diskless" and "data" disk mode installs
This requires some manual steps, as long as the setup-scripts auto-detect usable partitions only on *removable* devices (not internal harddisks). They do not support creating new, writable partitions to be used by Alpine.
How to prepare writable storage space is explained in the section manual partitioning, below.
For "sys" disk mode installs
 Some information on this page may be incomplete or outdate. |
Disk layouts
It is possible to have one or more of RAID, encrypted, and/or Logical Volume on your / (root) volume. However, the Alpine init script only knows how to handle them when they're layered in that order, and your initram and extlinux.conf files in the /boot partition are configured properly.
Your /boot directory cannot reside on an encrypted or LVM volume, at least not with Alpine's default bootloader (extlinux). (Grub2 can deal with /boot being on an LVM volume.) The usual practice is to create a small partition for /boot, then devote the rest of your disk to a separate partition on which you layer one or more of RAID, encryption, and/or Logical Volumes.
Sometimes /boot is also set up as a mirrored (RAID1) volume. However, this is just for post-init access. That way, when you write a new kernel or bootloader config file to /boot, it gets written to multiple physical partitions. During the pre-init, bootloader phase, only one of those partitions will be read from.
A typical setup might look like this:
One-disk system --------------- +------------------------------------------------+ | small partition (32--100M), holding | | only /boot, filesystem needn't be journaled | +------------------------------------------------+ | rest of disk in second partition | | +------------------------------------------+ | | | cryptsetup volume | | | | +-------------------------------------+ | | | | | LVM PV, containing single VG, | | | | | | containing multiple LVs, holding | | | | | | /, /home, swap, etc | | | | | +-------------------------------------+ | | | +------------------------------------------+ | +------------------------------------------------+ Two-disk system --------------- +------------------------------------------------+ +------------------------------------------------+ | small partition (32--100M), holding | | small partition (32--100M), holding | These 2 partitions might | only /boot, filesystem needn't be journaled | | only /boot, filesystem needn't be journaled | form a mirrored (RAID1) +------------------------------------------------+ +------------------------------------------------+ volume | rest of disk in second partition | | rest of disk in second partition | | T================================================================================================T | These 2 partitions form | T +--------------------------------------------------------------------------------------------+ T | a second mirrored | T | cryptsetup volume | T | (RAID1) volume | T | +---------------------------------------------------------------------------------------+ | T | | T | | LVM PV, containing single VG, | | T | | T | | containing multiple LVs, holding | | T | | T | | /, /home, swap, etc | | T | | T | +---------------------------------------------------------------------------------------+ | T | | T +--------------------------------------------------------------------------------------------+ T | | T================================================================================================T | | | | | +------------------------------------------------+ +------------------------------------------------+
In a three-disk system, the /boot would still be RAID1, but the larger partition might, in that case, be RAID5.
RAID
setup-disk will automatically build a RAID array if you supply the -r switch, or if you specify more than one device.
If you want to build your RAID array manually, see Setting up a software RAID array. Then you can add additional layers of encryption and/or Logical Volumes, or just assemble the RAID array, and supply the /dev/mdi device directly to setup-disk. When you're finished, be sure to disassemble the RAID array before rebooting.
If setup-disk sees that you're using RAID, either because you gave it the -r switch, or multiple devices, or a /dev/mdi device, then it will set up your initramfs and extlinux.conf file properly. However, in other cases, such as when you're also using encryption, or you invoke setup-disk with a mounted directory argument, these might not be properly set up for RAID. In that case, you may need to manually edit/rebuild them. The following assumes that $MNT holds the root directory you're installing into:
echo "/sbin/mdadm" > $MNT/etc/mkinitfs/files.d/raid echo "/etc/mdadm.conf" >> $MNT/etc/mkinitfs/files.d/raid # edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..." # includes raid (this field is space-separated and quoted) mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT # edit $MNT/etc/update-extlinux.conf to make sure modules=... contains # raid1 or raid456 (whichever your / is on; this field is comma-separated) # also check the root= setting extlinux --raid --install $MNT/boot --update
--update option to extlinux ... suffice to make /boot/extlinux.conf be regenerated? Or do we need to manually tweak that file, or run update-extlinux, as well?
You might also need to manually tweak $MNT/etc/fstab. And you might need to copy /usr/share/syslinux/mbr.bin to your disk's MBR.
Encryption
See Setting up encrypted volumes with LUKS. You can add an additional Logical Volume layer, or just unlock the volume you've created (using cryptsetup luksOpen ...), and supply the /dev/mapper/something device directly to setup-disk. When you're finished, be sure to relock the volume (using cryptsetup luksClose ...) before rebooting.
If you install your / (root) on an encrypted volume, you'll need to manually edit/rebuild your initram and your extlinux.conf file. The following assumes that $MNT holds the root directory you're installing into, that you've created the cryptvolume on the device /dev/md2, and that you want to unlock the encrypted volume into a virtual volume named "crypt":
# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..." # includes cryptsetup (this field is space-separated and quoted) mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT # edit $MNT/etc/update-extlinux.conf to make sure default_kernel_opts="..." # contains cryptroot=/dev/md1 and cryptdm=crypt (this field is also space-separated and quoted) # also check the root= setting extlinux --install $MNT/boot --update
--update option to extlinux ... suffice to make /boot/extlinux.conf be regenerated? Or do we need to manually tweak that file, or run update-extlinux, as well?
You might also need to manually tweak $MNT/etc/fstab.
LVM
setup-disk will automatically build and use volumes in a LVM group if you supply the -L switch.
If you instead want to build your LVM system manually, see Setting up Logical Volumes with LVM. Then vgchange -ay, format and mount your volumes, and supply the root mountpoint to setup-disk. When you're finished, be sure to
umount ... vgchange -an
before rebooting.
If setup-disk sees that you're using LVM, perhaps because you gave it the -L switch, then it will set up your initram and extlinux.conf file properly. However, in other cases, these might not be properly set up. In that case, you may need to manually edit/rebuild them. The following assumes that $MNT holds the root directory you're installing into:
# edit $MNT/etc/mkinitfs/mkinitfs.conf to make sure features="..." # includes lvm (this field is space-separated and quoted) mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT # edit $MNT/etc/update-extlinux.conf to make sure root= is set correctly extlinux --install $MNT/boot --update
--update option to extlinux ... suffice to make /boot/extlinux.conf be regenerated? Or do we need to manually tweak that file, or run update-extlinux, as well?
You might also need to manually tweak $MNT/etc/fstab.
Manual partitioning
For "diskless" and "data" disk mode installs
The installation image enviroment may have only the very basic busybox built-in fdisk command available. However, alpine allows you to install more complete partitioning tool packages like sfdisk (scriptable fdisk), gptfdisk, parted (CLI), cfdisk (text menus), or even gparted (after setting up a graphical environment).
The following example installs cfdisk, looks for existing partitions, and runs cfdisk against /dev/sdX:
# apk add cfdisk # blkid /dev/sdX1: LABEL="some" UUID="..." TYPE="vfat" /dev/sdX2: LABEL="other" UUID="..." TYPE="ext4" # cfdisk /dev/sdX
- Be aware of this Bug: The APKOVL loading of diskless setups doesn't work on btrfs and xfs filesystems, or nvme-based devices => So, for the moment, use only ext4 filesystem partitions on classic drives to store diskless mode states.
The following creates an ext4 partition with disabled journaling, to reduce write operations and allow the disk to spin down after the .apkovl and the packages have been read from the partition during the boot.
# apk add e2fsprogs
# mkfs.ext4 -O ^has_journal /dev/sdXY # the "-O ^has_journal" DISABLES journaling ("^" means "not")
For "sys" disk mode installs
setup-disk will by default set up a root partition, a separate /boot partition and a swap partition. If you want a different layout, you can manually create the partitions, filesystems and mount them on /mnt (or any other mount point) then run:
setup-disk /mnt
setup-disk will install your running system on the mounted root, detect your file system layout and generate an fstab.
If you're using the MBR, you are responsible for making the proper partition bootable and make sure the MBR is OK for extlinux. If you're going to use EFI, make sure you set BOOTLOADER=grub and USE_EFI=1, and that grub-efi and efibootmgr are installed before running setup-disk.
See also setup-partitions
Dual-booting
See Install to HDD with dual-boot
Other needs
Setting up swap
- create a partition with the type set to "linux swap" (82) (If you're going to use a logical volume for swap, skip this step and
lvcreatethat instead.) mkswap /dev/sda2echo -e "/dev/sda2 none swap sw 0 0" >> /mnt/etc/fstabswapon /dev/sda2(orrc-service swap start)
free -m
will show how much swap space is available (in MB).
If you prefer maximum speed, you don't need configure any raid devices for swap. Just add 2 swap partitions on different disks and linux will stripe them automatically. The downside is that the moment one disk fails, the system will go down. For better reliability, put swap on RAID1.