Regular system maintenance is necessary for the proper function of Arch over a period of time. Timely maintenance is a practice many users get accustomed to.
Check for errors
Failed systemd services
Check if any systemd services have entered in a failed state:
$ systemctl --failed
See systemd#Using units for more information.
Look for errors in the log files located at
/var/log, as well as high priority errors in the systemd journal:
# journalctl -p 3 -b
See systemd/Journal for more information.
Create backups of important data at regular intervals. See Synchronization and backup programs for many alternative applications that may better suit your case. See Category:System recovery for other articles of interest.
It is encouraged to automate backups, see Autostarting#On time events.
Before editing any configuration files, create a backup so that you can revert to a working version in case of problems. Editors like vim and emacs can do this automatically, as well as tools like etckeeper which keep
/etc in a version control system (VCS); see dotfiles#Tracking dotfiles directly with Git for more.
List of installed packages
Maintain a list of all installed packages, so that if a complete re-installation is inevitable, it is easier to re-create the original environment.
See Pacman tips#List of installed packages for details.
System and user data
See System backup.
Upgrading the system
It is recommended to perform full system upgrades regularly via Pacman#Upgrading packages, to enjoy both the latest bug fixes and security updates, and also to avoid having to deal with too many package upgrades that require manual intervention at once. When requesting support from the community, it will usually be assumed that the system is up to date.
Make sure to have the Arch install media or another Linux "live" CD/USB available so you can easily rescue your system if there is a problem after updating. If you are running Arch in a production environment, or cannot afford downtime for any reason, test changes to configuration files, as well as updates to software packages, on a non-critical duplicate system first. Then, if no problems arise, roll out the changes to the production system.
If the system has packages from the AUR, carefully upgrade all of them.
pacman is a powerful package management tool, but it does not attempt to handle all corner cases. Users must be vigilant and take responsibility for maintaining their own system.
Read before upgrading the system
Before upgrading, users are expected to visit the Arch Linux home page to check the latest news, or alternatively subscribe to the RSS feed or the arch-announce mailing list. When updates require out-of-the-ordinary user intervention (more than what can be handled simply by following the instructions given by pacman), an appropriate news post will be made.
Users must equally be aware that upgrading packages can raise unexpected problems that could need immediate intervention; therefore, it is discouraged to upgrade a stable system shortly before it is required for carrying out an important task. It is wise to wait instead to have enough time in order to be able to deal with possible post-upgrade issues.
Avoid certain pacman commands
Avoid doing partial upgrades. In other words, never run
pacman -Sy; instead, always use
Generally avoid using the
--overwrite option with pacman. The
--overwrite option takes an argument containing a glob. When used pacman will bypass file conflict checks for files that match the glob. In a properly maintained system, it should only be used when explicitly recommended by the Arch developers. See the #Read before upgrading the system section.
Avoid using the
-d option with pacman.
pacman -Rdd package skips dependency checks during package removal. As a result, a package providing a critical dependency could be removed, resulting in a broken system.
Partial upgrades are unsupported
Arch Linux is a rolling release distribution. That means when new library versions are pushed to the repositories, the developers and Trusted Users rebuild all the packages in the repositories that need to be rebuilt against the libraries. For example, if two packages depend on the same library, upgrading only one package might also upgrade the library (as a dependency), which might then break the other package which depends on an older version of the library.
That is why partial upgrades are not supported. Do not use
pacman -Sy package or any equivalent such as
pacman -Sy followed by
pacman -S package. Note that
pacman -Syuw does imply the same risks like
pacman -Sy, as it will update the pacman sync database without installing the newer packages. Always upgrade (with
pacman -Syu) before installing a package. Note that if
pacman -Syu does not perform the upgrade because of an error, the end result is the same as running
pacman -Sy. Therefore, the error must be resolved and the upgrade operation completed as soon as possible. Be very careful when using
IgnoreGroup for the same reason. If the system has locally built packages (such as AUR packages), users will need to rebuild them when their dependencies receive a soname bump.
If a partial upgrade scenario has been created, and binaries are broken because they cannot find the libraries they are linked against, do not "fix" the problem simply by symlinking. Libraries receive soname bumps when they are not backwards compatible. A simple
pacman -Syu to a properly synced mirror will fix the problem as long as pacman is not broken.
The bash script checkupdates, included with thepackage, provides a safe way to check for upgrades to installed packages without running a system update at the same time.
Act on alerts during an upgrade
When upgrading the system, be sure to pay attention to the alert notices provided by pacman. If any additional actions are required by the user, be sure to take care of them right away. If a pacman alert is confusing, search the forums and the recent news posts for more detailed instructions.
Deal promptly with new configuration files
When pacman is invoked,
.pacsave files can be created. Pacman provides notice when this happens and users must deal with these files promptly. Users are referred to the Pacman/Pacnew and Pacsave wiki page for detailed instructions.
Also, think about other configuration files you may have copied or created. If a package had an example configuration that you copied to your home directory, check to see if a new one has been created.
Restart or reboot after upgrades
Upgrades are typically not applied to existing processes. You must restart processes to fully apply the upgrade.
The kernel is particularly difficult to patch without a reboot. A reboot is always the most secure option, but if this is very inconvenient kernel live patching can be used to apply upgrades without a reboot.
Revert broken updates
If a package update is expected/known to cause problems, packagers will ensure that pacman displays an appropriate message when the package is updated. If experiencing trouble after an update, double-check pacman's output by looking at
At this point, only after ensuring there is no information available through pacman, there is no relative news on https://archlinux.org/, and there are no forum posts regarding the update, consider seeking help on the forum, over IRC, or by downgrading the offending package.
Check for orphans and dropped packages
After upgrading you may now have packages that are no longer needed or that are no longer in the official repositories.
pacman -Qtd to check for packages that were installed as a dependency but now, no other packages depend on them. If an orphaned package is still needed, it is recommended to change the installation reason to explicit. Otherwise, if the package is no longer needed, it can be removed.
Additionally, some packages may no longer be in the remote repositories, but they still may be on your local system. To list all foreign packages use
pacman -Qm. Note that this list will include packages that have been installed manually (e.g., from the AUR). To exclude packages that are (still) available on the AUR, use the AUR tool.
Use the package manager to install software
Pacman does a much better job than you at keeping track of files. If you install things manually you will, sooner or later, forget what you did, forget where you installed to, install conflicting software, install to the wrong locations, etc.
- Install packages from the official repositories using the method in the Pacman#Installing packages section.
- If the program you desire is not available, check to see if someone has created a package in the AUR. Follow the method in that article for installation.
- Lastly, if the program you want is not in the official repositories or in the AUR, learn how to create a package for it.
To clean up improperly installed files, see Pacman/Tips and tricks#Identify files not owned by any package.
Choose open-source drivers
Always try open source drivers before resorting to proprietary drivers. Most of the time, open source drivers are more stable and reliable than proprietary drivers. Open source driver bugs are fixed more easily and quickly. While proprietary drivers can offer more features and capabilities, this can come at the cost of stability. To avoid this dilemma, try to choose hardware components known to have mature open source driver support with full features. Information about hardware with open source Linux drivers is available at linux-drivers.org.
Be careful with unofficial packages
Use precaution when using packages from the AUR or an unofficial user repository. Most are supplied by regular users and thus may not have the same standards as those in the official repositories. Avoid AUR helpers which automate installation of AUR packages. Always check PKGBUILDs for sanity and signs of mistake or malicious code before building and/or installing the package.
To simplify maintenance, limit the amount of unofficial packages used. Make periodic checks on which are in actual use, and remove (or replace with their official counterparts) any others. See pacman/Tips and tricks#Maintenance for useful commands.
Update the mirrorlist
Update pacman's mirrorlist, as the quality of mirrors can vary over time, and some might go offline or their download rate might degrade.
See mirrors for details.
Clean the filesystem
When looking for files to remove, it is important to find the files that take up the most disk space. Programs that help with this are found in:
.pkg files from
/var/cache/pacman/pkg/ to free up disk space.
See Pacman#Cleaning the package cache for more information.
Unused packages (orphans)
Remove unused packages from the system to free up disk space and simplify maintenance.
See Pacman/Tips and tricks#Removing unused packages (orphans) for details.
Old configuration files
Old configuration files may conflict with newer software versions, or corrupt over time. Remove unneeded configurations periodically, particularly in your home folder and
~/.config. For similar reasons, be careful when sharing home folders between installations.
Look for the following folders:
~/.config/-- where apps stores their configuration
~/.cache/-- cache of some programs may grow in size
~/.local/share/-- old files may be lying there
See XDG Base Directory support for more information.
To keep the home directory clean from temporary files created at the wrong place, it is a good idea to manage a list of unwanted files and remove them regularly, for example with rmshit.py.
can be used to find and optionally remove duplicate files, empty files, recursive empty directories and broken symlinks.
Old, broken symbolic links might be sitting around your system; you should remove them. Examples on achieving this can be found here and here. However, you should not blindly delete all broken symbolic links, as some of them serve a purpose .
To quickly list all the broken symlinks of your system, use:
# find / -xtype l -print
Then inspect and remove unnecessary entries from this list.
Tips and tricks
The following tips are generally not required, but certain users may find them useful.
Use proven software packages
Arch's rolling releases can be a boon for users who want to try the latest features and get upstream updates as soon as possible, but they can also make system maintenance more difficult. To simplify maintenance and improve stability, try to avoid cutting edge software and install only mature and proven software. Such packages are less likely to receive difficult upgrades such as major configuration changes or feature removals. Prefer software that has a strong and active development community, as well as a high number of competent users, in order to simplify support in the event of a problem.
Avoid any use of the testing repository, even individual packages from testing. These packages are experimental and not suitable for a stable system. Similarly, avoid packages which are built directly from upstream development sources. These are usually found in the AUR, with names including things like: "dev", "devel", "svn", "cvs", "git", etc.
Install the linux-lts package
The core repository. This particular kernel version has long-term support (LTS) from upstream, including security fixes and some feature backports. It is useful if you prefer the stability of less-frequent kernel updates or if you want a fallback kernel in case a new kernel version causes problems.package is an alternative Arch kernel package, and is available in the
To make it available as a boot option, you will need to update your bootloader's configuration file to use the LTS kernel and ram disk: