Setting up LVM on GPT-labeled disks

2022-03-26T22:26:08Z

Parke: /* Partitioning */ Added note about `mdev -s`

[[Category:Storage]]
This document describes how to set up a system booting from a logical volume in Alpine using lvm2 and GPT-labeled disks.

Begin by booting from Alpine installation media in the usual way. Log in as `root`, run `setup-alpine`, and answer `none` when asked to choose a disk.

=== Partitioning ===
We need to install some tools:
{{Cmd|apk add parted lvm2}}

Now we can create the partition table:
{{Cmd|parted -a optimal /dev/sda}}

unit MiB
mkpart 1 1 256
name 1 boot
set 1 legacy_boot on
mkpart 2 256 100%
set 2 lvm on

Now, exit `parted` and reboot to force a reread of the partition table (for some reason, `partprobe` doesn't work here). (Or, instead of rebooting, maybe try running `mdev -s`.)

=== LVM Creation ===
Once you've rebooted, run through `setup-alpine` again.

Install some more necessary tools:
{{Cmd|apk add lvm2 e2fsprogs syslinux}}

Create a PV, VG, and a LV for the root partition:
{{Cmd|pvcreate /dev/sda2}}
{{Cmd|vgcreate vg0 /dev/sda2}}
{{Cmd|lvcreate -n myhost.root -L 8G vg0}}
{{Cmd|rc-update add lvm}}
{{Cmd|vgchange -ay}}

Create file systems:
{{Cmd|mkfs.ext3 /dev/sda1}}
{{Cmd|mkfs.ext4 /dev/vg0/myhost.root}}

Mount the file systems:
{{Cmd|mount -t ext4 /dev/vg0/myhost.root /target}}
{{Cmd|mkdir /target/boot}}
{{Cmd|mount -t ext3 /dev/sda1 /target/boot}}

Now you can run `setup-disk` to install Alpine:
{{Cmd|setup-disk -m sys /target}}

Finally, install `syslinux` (note that we are installing to `/dev/sda`, *not* `/dev/sda1`):
{{Cmd|1=dd bs=440 conv=notrunc count=1 if=/usr/share/syslinux/gptmbr.bin of=/dev/sda}}

Reboot and enjoy your new Alpine installation!

Alpine local backup

2020-09-11T22:48:18Z

Parke: /* Saving and loading ISO image customizations */ fixed typo alpine-setup to setup-alpine

When Alpine Linux boots in diskless mode, initially it only loads a few required packages from the boot device by default.
But local adjustments in RAM are possible, e.g. by [[Alpine_package_management|installing a package]] or adjusting some configuration.

And all the modifications can be saved to an overlay file (.apkovl) to make them survive a reboot.

This is what the local backup utility <code>lbu</code> together with a [[Alpine_Linux_package_management#Local_Cache|local package cache]] is good for!

__TOC__

{{Note|If you installed Alpine on HDD you don't need to use <code>lbu</code>, because in this case all modifications are directly written to HDD. However, <code>lbu</code> may still be useful for some maintenance tasks.}}

The first thing you need to know is this: '''By default <code>lbu</code> only cares about modifications in {{Path|/etc}} and its subfolders, with the exception of {{Path|/etc/init.d}}!''' <BR>
Please have a look at [[#Include_special_files.2Ffolders_to_the_apkovl|lbu include]] to save files/folders located elsewhere than in {{Path|/etc}}.

Alpine has the following tools for permanently storing your modifications:
* lbu
* lbu commit ''(Same as 'lbu ci')''
* lbu package ''(Same as 'lbu pkg')''
* lbu status ''(Same as 'lbu st')''
* lbu list ''(Same as 'lbu ls')''
* lbu diff
* lbu include ''(Same as 'lbu inc' or 'lbu add')''
* lbu exclude ''(Same as 'lbu ex' or 'lbu delete')''
* lbu list-backup ''(Same as 'lbu lb')''
* lbu revert

In the below examples you will find some characters with special meaning:
* '''|''' = '''or''' ''('lbu commit|ci' means that you can type ether 'lbu commit' or 'lbu ci')''
* '''[ ]''' = '''optional''' ''(In 'lbu commit|ci [-nv]' you can just skip the '-n', '-v' or '-nv' part if you don't want it)''

== Committing your changes ==

=== Basic Command ===
When you "commit" or save changes you've made to your system, <code>lbu</code> will generate a file named something like {{Path|<var>myboxname</var>.apkovl.tar.gz}} ''('myboxname' will be the same as the hostname)''.
This file (that contains your modifications) is called your "apkovl".
You will need to save your apkovl on some suitable media (floppy, usb, cf, other).
<pre>
usage: lbu commit|ci [-nv] [<media>]

Options:
-d Remove old apk overlay files.
-e Protect configuration with a password.
-n Don't commit, just show what would have been committed.
-p <password> Give encryption password on the command-line
-v Verbose mode.

The following values for <media> is supported: floppy usb
If <media> is not specified, the environment variable LBU_MEDIA will be used.

Password protection will use aes-256-cbc encryption. Other ciphers can be
used by setting the DEFAULT_CIPHER or ENCRYPTION environment variables.
For possible ciphers, try: openssl -v

The password used to encrypt the file, can either be specified with the -p
option or using the PASSWORD environment variable.

The environment variables can also be set in /etc/lbu/lbu.conf
</pre>

=== Saving and loading ISO image customizations ===

Besides supporting a boot parameter that points to a web server for loading customizations, the "diskless" Alpine ISO images also seem to look for an .apkovl volume in system partitions, and offer to save local backups and the package cache to mountpoints below /media/, if they exist.

So
# Boot the diskless system from ISO, and if necessary create and format a partition.
# Edit /etc/fstab and mount the writable partition to /media/sda1 (if sda1 is your writable partition).
# Run setup-alpine and choose to save configs and package cache to the mounted partition.
# Customize the system.
# Generate an APKOVL file with [[Alpine_local_backup|lbu]] by executing <code>lbu commit</code>

Look at the '''[[Qemu#Live_mode|Qemu example]]''' to see how an ISO image is set up with .apkovl customizations in a virtual machine.

Notes:

* See [[Alpine_Linux_package_management#Local_Cache]] about managing included packages.
* See [[Alpine_local_backup|lbu]] about how to customize it to cover files outside of <code>/etc</code>.
* Any packages you add to /etc/apk/world of your lbu will also automatically be installed in the live system.
* If you don't have a web server you can run busybox's httpd temporarily - <code>busybox httpd -p 127.0.0.1:80</code>
* If you put the APKOVL file on a webserver, you will need to supply a custom url with the <code>APKOVL</code> kernel boot parameter.

=== Create a apkovl elsewhere than on your configured media ===

To "commit" changes, but overriding the destination of the generated apkovl file, use <code>lbu package</code> instead of <code>lbu commit</code>:

<pre>
usage: lbu package|pkg -v [<dirname>|<filename>]

Options:
-v Verbose mode.

If <dirname> is a directory, a package named <hostname>.apkovl.tar.gz will
be created in the specified directory.

If <filename> is specified, and is not a directory, a package with the
specified name will be created.

If neither <dirname> nor <filename> is specified, a package named
<hostname>.apkovl.tar.gz will be created in current work directory.
</pre>

=== Use SSH to create an apkovl on a different host ===

To create an apkovl of client on a centralized server, use <code>lbu package</code> with {{Path|-}} as the apkovl name:

On the server:
<pre>
ssh root@client "lbu package -" >client.apkovl.tar.gz
</pre>

== Check what will be added to your apkovl ==

<code>lbu status</code> lists what will be saved the next time you run <code>lbu commit</code>. Its default output is incremental, that is, to only show what files have changed since the last commit; but this can be overridden with the <code>-a</code> flag:

<pre>
usage: lbu status|st [-av]

Options:
-a Compare all files, not just since last commit.
-v Also show include and exclude lists.
</pre>

Another option is <code>lbu list</code>. This works like <code>lbu status -a</code> but the format of the output is a bit different. (It's strictly equivalent to <code>lbu package -v /dev/null</code>).

usage: lbu list|ls

A third option is <code>lbu diff</code>. This shows the same incremental changes that <code>lbu status</code> (without <code>-a</code>) does, but in a different format.

usage: lbu diff

== Include special files/folders to the apkovl ==
Assume that you have some files that you want to permanently save, but they are located somewhere else than in {{Path|/etc}}.<BR>
It could be {{Path|/root/.ssh/authorized_keys}} (used by <code>sshd</code> to authenticate ssh-users). Such files/folders can be added to lbu's ''include'' list with the following command:

<pre>
usage: lbu include|inc|add [-rv] <file> ...
lbu include|inc|add [-v] -l

Options:
-l List contents of include list.
-r Remove specified file(s) from include list instead of adding.
-v Verbose mode.
</pre>

{{Note|This information used to be maintained in {{Path|/etc/lbu/include}}; now it's instead maintained together with the ''exclude'' list in {{Path|/etc/apk/protected_paths.d/lbu.list}}. Either way, the command <code>lbu include</code> only modifies lbu's configuration; you will need to run <code>lbu commit</code> to actually create/modify your apkovl.}}

== Exclude specific files/folders from the apkovl ==
Assume that you have some files located in {{Path|/etc}} or one of its subfolders that you ''do not'' want to permanently save.
It could be some log file or status file that for some reason isn't in {{Path|/var/log/}} but in some location that would otherwise be tracked by <code>lbu</code>.
Such files/folders can be added to lbu's ''exclude'' list by manually editing that file or using the following command:
<pre>
usage: lbu exclude|ex|delete [-rv] <file> ...
lbu exclude|ex|delete [-v] -l

Options:
-l List contents of exclude list.
-r Remove specified file(s) from exclude list instead of adding.
-v Verbose mode.
</pre>
{{Note|As stated above, this information is now maintained in {{Path|/etc/apk/protected_paths.d/lbu.list}}. The command <code>lbu exclude</code> also only modifies lbu's configuration; you will need to run <code>lbu commit</code> to actually create/modify your apkovl.}}

== Execute a script as part of a backup ==

Sometimes it is necessary to run a script before or after a backup. Scripts in two optional directories allow for this:

/etc/lbu/pre-package.d
/etc/lbu/post-package.d

Files in those directories are run using run-script rules (meaning they must have the executable bit set, they are run in alphabetical order, and cannot contain an extension: {{Path|runme}} works, but {{Path|runme.sh}} does not.)

The scripts in {{Path|pre-package.d}} are run before the apkovl is created; scripts in {{Path|post-package.d}} are run after the apkovl is created.

=== Example ===

Rather than adding the raw database directories to {{Path|/etc/lbu/include}}, you can do a "database dump". For purposes of example, we use {{Pkg|postgresql}}:

* Create {{Path|/etc/lbu/pre-package.d/sqldump}} with the following contents: <pre>pg_dumpall -U postgres | gzip -c >/root/pgdatabases.gz</pre>
* Mark the file executable: <code>chmod +x /etc/lbu/pre-package.d/sqldump</code>
* Create {{Path|/etc/lbu/post-package.d/sqldumpdelete}} with the following contents: <pre>rm -f /root/pgdatabases.gz</pre>
* Mark the file executable: <code>chmod +x /etc/lbu/post-package.d/sqldumpdelete</code>
* Finally, add the database dump file to the list of files to back up: <code>lbu include root/pgdatabases.gz</code>

Now whenever you do a <code>lbu commit</code>, the sql databases are dumped and gzipped to {{Path|/root/pgdatabases.gz}}, and then the temporary file is deleted at the end of the lbu commit.

On a catastrophic restore, the databases are not automatically restored (that's not lbu's responsibility), but you will find a complete database dump in the {{Path|/root}} directory, where it can be restored manually.

== Multiple Backups ==
Lbu can now keep backups so you can revert to older, good known config.
Set BACKUP_LIMIT in {{Path|/etc/lbu/lbu.conf}} to the number of backups you want
to keep.

You can list the current backups with:

{{Cmd|lbu list-backup [<media>]}}

and you can revert to an older with:

{{Cmd|lbu revert <filename> [<media>]}}

Nothing is written to your main system when "reverting"; this only affects which apkovl is considered active. If you've set BACKUP_LIMIT, then the previously active apkovl will be backed up before being overwritten.

== See also ==
* [[Back Up a Flash Memory Installation]]
* [[Manually editing a existing apkovl]]

[[Category:Installation]]

[[Category:Booting]]
[[Category:Package Manager]]
[[category: LBU]]

Alpine Linux - User contributions [en]

Setting up LVM on GPT-labeled disks

Alpine local backup