Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-10-01 01:25:40 -04:00
Code Issues Packages Projects Releases Wiki Activity

Add and update links; wrap text

Browse Source
This commit is contained in:
Andrew David Wong 2021-10-11 16:20:24 -07:00
parent f5ca579fe0
commit 5134fe46da
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17
2 changed files with 59 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

66
user/downloading-installing-upgrading/upgrade/4_1.md
View File

@ -5,29 +5,46 @@ permalink: /doc/upgrade/4.1/
title: How to upgrade to Qubes 4.1
---
This page explains how to perform an in-place upgrade from Qubes 4.0 to Qubes 4.1. It is not possible to upgrade directly from releases earlier than 4.0. If you're still on an earlier release, please either perform a [clean installation of 4.1](#clean-installation) or [upgrade to 4.0](/doc/upgrade/4.0/) first.
This page explains how to perform an in-place upgrade from Qubes 4.0 to Qubes
4.1. It is not possible to upgrade directly from releases earlier than 4.0. If
you're still on an earlier release, please either perform a [clean installation
of 4.1](#clean-installation) or [upgrade to 4.0](/doc/upgrade/4.0/) first.
## Back up
Before attempting either an in-place upgrade or a clean installation, we strongly recommend that you first [back up your system](/doc/how-to-back-up-restore-and-migrate/).
Before attempting either an in-place upgrade or a clean installation, we
strongly recommend that you first [back up your
system](/doc/how-to-back-up-restore-and-migrate/).
## Clean installation
If you would prefer to perform a clean installation rather than upgrading in-place:
If you would prefer to perform a clean installation rather than upgrading
in-place:
1. Create a [backup](/doc/how-to-back-up-restore-and-migrate/#creating-a-backup) of your current installation.
2. Follow the [installation guide](/doc/installation-guide/) to install Qubes 4.1.
3. [Restore from your backup](/doc/how-to-back-up-restore-and-migrate/#restoring-from-a-backup) on your new 4.1 installation.
1. Create a
[backup](/doc/how-to-back-up-restore-and-migrate/#creating-a-backup) of your
current installation.
2. Follow the [installation guide](/doc/installation-guide/) to install Qubes
4.1.
3. [Restore from your
backup](/doc/how-to-back-up-restore-and-migrate/#restoring-from-a-backup) on
your new 4.1 installation.
## In-place upgrade
The upgrade may take several hours, and will download several gigabytes of data.
The upgrade may take several hours, and will download several gigabytes of
data.
In place upgrade is a complex operation. For this reason, we provide a `qubes-dist-upgrade` tool to handle all the necessary steps automatically. You can install it with the following command in the dom0 terminal:
In place upgrade is a complex operation. For this reason, we provide a
`qubes-dist-upgrade` tool to handle all the necessary steps automatically. You
can install it with the following command in the dom0 terminal:
sudo qubes-dom0-update -y qubes-dist-upgrade
The upgrade consists of 7 stages - 6 before restarting the system - marked as "STAGE 0" through "STAGE 6" in the options list below. And the 7th stage is rebuilding the applications and features list - started with a `--resync-appmenus-features` option.
The upgrade consists of 7 stages - 6 before restarting the system - marked as
"STAGE 0" through "STAGE 6" in the options list below. And the 7th stage is
rebuilding the applications and features list - started with a
`--resync-appmenus-features` option.
Full list of options can be obtained with `qubes-dist-upgrade --help`:
@ -64,11 +81,14 @@ After installing the tool, upgrade can be performed all at once with:
sudo qubes-dist-upgrade --all
Optionally, an `--assumeyes` (or `-y`) option can be used to automatically accept all the actions without confirmation.
Optionally, an `--assumeyes` (or `-y`) option can be used to automatically
accept all the actions without confirmation.
Alternatively, each upgrade stage can be started separately (see the list of options above).
Alternatively, each upgrade stage can be started separately (see the list of
options above).
After completing "STAGE 0" through "STAGE 6", restart the system. Then perform the final step:
After completing "STAGE 0" through "STAGE 6", restart the system. Then perform
the final step:
sudo qubes-dist-upgrade --resync-appmenus-features
@ -76,12 +96,24 @@ When this completes, you can start using Qubes OS 4.1.
### Known issues
1. The script does not convert LUKS1 to LUKS2 disk encryption format (fresh Qubes 4.1 install uses LUKS2 for disk encryption, while earlier versions use LUKS1).
2. Early Qubes 4.0 pre-releases (before R4.0-rc2) made `/boot/efi` partition only 200MB, which is too small for R4.1. In case of such partition layout, clean installation is necessary.
3. If user has created some custom qrexec policy entries, they may not be correctly handled in R4.1, resulting in denying all the calls. It is advised to verify if there are not qrexec policy errors in the log after the system restart - using `journalctl -b` command.
1. The script does not convert LUKS1 to LUKS2 disk encryption format (fresh
Qubes 4.1 install uses LUKS2 for disk encryption, while earlier versions use
LUKS1).
2. Early Qubes 4.0 pre-releases (before R4.0-rc2) made `/boot/efi` partition
only 200MB, which is too small for R4.1. In case of such partition layout,
clean installation is necessary.
3. If user has created some custom qrexec policy entries, they may not be
correctly handled in R4.1, resulting in denying all the calls. It is advised
to verify if there are not qrexec policy errors in the log after the system
restart - using `journalctl -b` command.
If any early upgrade stage fails, the `qubes-dist-upgrade` tool will try to restore previous system state. After fixing an issue, the tool can be started again, to retry the operation. If a later stage (number 3 or later) fails, the tool may not be able to rollback the changes. But it may still be possible to retry the upgrade.
If any early upgrade stage fails, the `qubes-dist-upgrade` tool will try to
restore previous system state. After fixing an issue, the tool can be started
again, to retry the operation. If a later stage (number 3 or later) fails, the
tool may not be able to rollback the changes. But it may still be possible to
retry the upgrade.
## Update
After upgrading or performing a clean installation, we strongly recommend [updating your system](/doc/how-to-update/).
After upgrading or performing a clean installation, we strongly recommend
[updating your system](/doc/how-to-update/).

19
user/downloading-installing-upgrading/upgrade/upgrade.md
View File

@ -8,13 +8,14 @@ title: Upgrade guides
These guides are for upgrading from one version of Qubes to another.
If you're just looking to update your system while staying on the same version,
see [How to Update](/doc/how-to-update/).
see [how to update](/doc/how-to-update/).
* [Upgrading from R1 to R2 Beta 1](/doc/upgrade-to-r2b1/)
* [Upgrading from R1 to R2 Beta 2](/doc/upgrade-to-r2b2/)
* [Upgrading from R2 Beta 2 to R2 Beta 3](/doc/upgrade-to-r2b3/)
* [Upgrading from R2 Beta 3 to R2](/doc/upgrade-to-r2/)
* [Upgrading from R2 to R3.0](/doc/upgrade-to-r3.0/)
* [Upgrading from R3.0 to R3.1](/doc/upgrade-to-r3.1/)
* [Upgrading from R3.1 to R3.2](/doc/upgrade-to-r3.2/)
* [Upgrading from R3.2 to R4.0](/doc/upgrade-to-r4.0/)
* [Upgrade from 1 to 2 Beta 1](/doc/upgrade/2b1/)
* [Upgrade from 1 to 2 Beta 2](/doc/upgrade/2b2/)
* [Upgrade from 2 Beta 2 to 2 Beta 3](/doc/upgrade/2b3/)
* [Upgrade from 2 Beta 3 to 2](/doc/upgrade/2/)
* [Upgrade from 2 to 3.0](/doc/upgrade/3.0/)
* [Upgrade from 3.0 to 3.1](/doc/upgrade/3.1/)
* [Upgrade from 3.1 to 3.2](/doc/upgrade/3.2/)
* [Upgrade from 3.2 to 4.0](/doc/upgrade/4.0/)
* [Upgrade from 4.0 to 4.1](/doc/upgrade/4.1/)