mirrors/apparmor.d
1
0
Fork 0
mirror of https://github.com/roddhjav/apparmor.d.git synced 2024-12-24 14:06:47 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

recovery - Reword, fix spelling mistakes, specify instructions are not meant for subvolume installs

Browse source
This commit is contained in:
Stoppedpuma 2024-06-07 21:30:58 +02:00 committed by Alex
parent 57dd775424
commit 491cb28f2a
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/recovery.md
View file

@ -2,15 +2,15 @@
title: System Recovery
---
Issue in some core profiles like the systemd suite, or the desktop environment can fully break your system. This should not happen a lot, but if it does here is the process to recover your system on Archlinux:
An issue in some core profiles like the systemd suite, or the desktop environment can prevent your system from starting correctly. This is rare, but if it does happen this is the process to recover your system on an Arch Linux system **without subvolumes**:
1. Boot from a Archlinux live USB
1. If you root partition is encryped, decrypt it: `cryptsetup open /dev/<your-disk-id> vg0`
1. Boot from an Arch Linux live USB
1. If you root partition is encrypted, decrypt it: `cryptsetup open /dev/<your-disk-id> vg0`
1. Mount your root partition: `mount /dev/<your-plain-disk-id> /mnt`
1. Chroot into your system: `arch-chroot /mnt`
1. Check the AppArmor messages to see what profile is faulty: `aa-log`
1. Check the AppArmor logs to see which profile is faulty: `aa-log`
1. Temporarily fix the issue with either:
- When only one profile is faultily, remove it: `rm /etc/apparmor.d/<profile-name>`
- When only one profile is causing problems, remove it: `rm /etc/apparmor.d/<profile-name>`
- Otherwise, you can also remove the package: `pacman -R apparmor.d`
- Alternatively, you may temporarily disable apparmor as it will allow you to
boot and study the log: `systemctl disable apparmor`