I have broken my system by running an update while power went out. My boot manager only shows the option to boot into firmware, not into linux. If I chroot into the system, I am unable to run mkinitcpio -P as I get the error "no presets found in /etc/mkinitcpio.p" because I removed the empty linux.preset file in there. I did so because that was a recommendation from an old forum comment. The same comment recommended to the run pacman -S linux, which gives errors in the form of linux: _____ exists in filesystem
#Arch broken system due to power loss during update
19 messages · Page 1 of 1 (latest)
also my mstab file is missing
Run the same basic installation steps except anything that may cause data loss, ie formatting and partitioning, disk dupe(dd), just go with the basics such as mounting, lsblk, filesystem integrity checks, pacstrap and firmware installation, recovery of anything you may have lost or corrupted
By this are you referring to fstab or mtab?
mtab, my bad
Can you show the error?
oops, it wasn't there when I accidentally used chroot, but it is there when I use arch-chroot
anyways, the wiki tells me to arch-chroot into the systemd and use pacman -S ___ for every package that was updated, but there's too many to type in and I don't think it'll work anyways because if I do individual packages I get the same errors as in my first message
So don't install linux
what should I do instead then?
Is it a fresh install
no it's not
also, running pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syu before arch-chroot seems promising but it complains about the semver key having unknown trust
I ran # pacman -Qqn | pacman --overwrite "*" -S - and now have a half working system
sudo pacman -Qkk tells me about a lot of packages that have something wrong
Try -Qtdq to check for any orphans and get rid of them
don't ever do that