armistace/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Human edit and pelican metadata

Browse Source
This commit is contained in:
armistace 2025-07-01 17:12:06 +10:00
parent 9b9863c230
commit b5267eb3ac
1 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
src/content/recovering_an_archlinux_qemu_vm_in_proxmox.md
View File

@ -1,3 +1,17 @@
Title: Recovering Archlinux Qemu VM in Proxmox
Date: 2025-07-01 20:00
Modified: 2025-07-01 20:00
Category: SysAdmin
Tags: System Admin, Proxmox, Qemu, Arch, Kubernetes
Slug: recovering-arch-vm-proxmox
Authors: Andrew Ridgway
Summary: An absolute nightmare of a day trying to recover my kube cluster from a silly update error
### Human Edit
This is probably the most amazing run of the blog creator, I've started using the new gemma3n and also upgrade the box ollama runs on so it can run slightly bigger models. Using phi4 and gemma:27b has produced some amazing results see below
I *did* need to update some of the pacman stuff as it conflated to seperate issues so bear in mind I have made some little edits in that place but otherwise... this is straight from the mouth of the llm. Enjoy!
# Recovering an Archlinux QEMU VM in Proxmox: A Day in Hell and Back Again
Well that was a morning. Today I wanted to try and fix my Longhorn installation in Kube... (again 😥). It turns out, things didn't go as planned.
@ -42,7 +56,14 @@ Oh boy, pacman threw 23 million permission errors my way. Last year they changed
```bash
# Disable DefaultUser temporarily for this session (or remove if permanent)
pacman -Syu --noprofile --overwrite "*"
pacman -Syu
```
I did have a couple issues installing the kernel (which is what got borked in the update)
```bash
# Sometimes some files got written so use overwrite to get rid of them
# be warned this *could* be destructive
pacman -S linux --overwrite "*"
```
### Clean Up and Exit