It's more likely that the primary will have the partitions setup correctly.

We were missing two crucial steps:

 1. the partitions had to be created *before* the device was passed to
    the VM, otherwise it gets completely confused and just creates one
    gigantic filesystem

 2. each partition needs to be adopted separately

Closes: team#40775.

changes merged in tpa-rfc-2 through !29

TPA-RFC-28: alphabetical triage

See merge request !29

The blockchain-less procedure didn't work: NBXplorer was stuck and
would have seemingly never synchronized. This procedure actually
worked in the end, by doing a full rsync.

See team#33750

see nextcloud#6

also regroup issues by type now that this list is growing a bit large

We probably need a clearer workflow for this, but it seems clear to me
those don't need to stay "standard" forever...

Closes: team#33949

Under bullseye the old command aborts with: "Failed to reload
local-fs.target: Job type reload is not applicable for unit
local-fs.target."

The restart operation seems to work, and the new .mount unit is created
as expected.

-l and -L are easy to confuse, just use --size here

Document the chroot remount procedure with environment variables instead
of hardcoding all the paths, making it easier to use this in different
hardware environments.

Also, assume that the "rebuild grub" set of commands occur within the
chroot as this is the expected result of the previous set of commands.

Permalinks ftw. Unfortuntaly, the immerda one is dead and I can't find
an alternative.

This is proving necessary to fast-track at least a proposal on this
considering the state of Python 2 in bullseye.