Document Keyring Issue Resolution [DOCS]

docs/.vitepress/config.ts

@@ -45,6 +45,7 @@ export default defineConfig({
         collapsible: true,
         collapsed: false,
         items: [
+          { text: 'Keyring Issues', link: '/installation/keyrings.md' },
           { text: 'Base Installation', link: '/installation/baseinstall.md' },
           { text: 'Post-Installation Configuration', link: '/installation/post-installation.md' },
           { text: 'Bootloader Setup', link: '/installation/grubinstall.md' },

docs/installation/keyrings.md

@@ -0,0 +1,92 @@
+> [!NOTE]
+> **Refer to this only if you encounter keyring or package installation errors; otherwise, proceed to the base installation.**
+
+# Resolving Arch Linux Keyring Trusted Issue
+
+When installing Arch Linux, you may encounter issues with the keyring trust. This typically happens when GPG keys used for verifying package signatures are outdated or missing. Follow the steps below to resolve this problem effectively.
+
+## **Solution 1: Update Keyrings**
+- **Synchronize the system clock** to avoid timing-related issues:
+   ```sh
+   timedatectl set-ntp true
+   ```
+
+- **Update the Arch Linux keyrings**:
+   ```sh
+   pacman -Sy archlinux-keyring
+   ```
+
+- **Reinitialize the keyring** (if required):
+   ```sh
+   pacman-key --init
+   pacman-key --populate archlinux
+   ```
+
+- Try your installation or package operation again.
+
+## **Solution 2: Refresh the Keyring Manually**
+If the automatic update fails, refresh the keyring manually:
+
+- **Reinitialize the GPG database**:
+   ```sh
+   rm -rf /etc/pacman.d/gnupg
+   pacman-key --init
+   pacman-key --populate archlinux
+   ```
+
+- **Manually import and trust any missing keys**:
+   ```sh
+   pacman-key --recv-keys <KEY_ID>
+   pacman-key --lsign-key <KEY_ID>
+   ```
+
+   Replace `<KEY_ID>` with the specific ID of the missing or invalid key.
+
+## **Solution 3: Temporarily Disable Signature Verification**
+If updating the keyring doesn’t work and you urgently need to proceed, temporarily disable signature checking:
+
+- Open `/etc/pacman.conf` and set:
+   ```int
+   [options]
+   SigLevel = Never
+   ```
+
+- **Update the keyrings**:
+   ```sh
+   pacman -Sy archlinux-keyring
+   ```
+
+- Once resolved, **restore signature verification** by setting `SigLevel` back to `Required DatabaseOptional`.
+
+> [!WARNING]
+> Disabling signature checking is not recommended for regular use and should only be used as a temporary workaround.
+
+## **Solution 4: Use Reflector for Updated Mirrors**
+Outdated mirrors can also cause keyring issues. Update your mirrors using `reflector`:
+
+- Install Reflector:
+   ```sh
+   pacman -S reflector
+   ```
+- Fetch the latest and fastest mirrors:
+   ```sh 
+   reflector --latest 10 --sort rate --save /etc/pacman.d/mirrorlist
+   ```
+
+- Synchronize and update the system:
+   ```sh
+   pacman -Syyu
+   ```
+
+---
+
+## 💡 **Tips and Notes**
+- Ensure your **internet connection is stable** during these steps.
+- Always use **official Arch mirrors** to avoid additional issues.
+- If you’re in a live environment, you may need to fix the keyring in a chroot:
+   ```sh
+   arch-chroot /mnt
+   ```
+
+*By following these steps, you should be able to resolve the keyring trust issues effectively and proceed with your Arch Linux installation.*
+