sinsinewave

SIN001E/R

@sinsinewave

Queen of Sinewave Technologies

20+ y/o finnish robotgirlthing :: artist sometimes :: cursed tech specialist :: if you train an AI with my art i may stab you with a stylus, so don't

log inask
sinsinewave
@sinsinewave
blackle
@blackle
mia
@mia

2024 is finally the year of linux gaming attempts to play halo and my entire install immediately breaks so bad even the recovery mode can’t use a keyboard

mia
@mia

if any of you linux freaks know the first thing about fixing something like this on arch i would greatly appreciate it

all i did was a pacman -Syu and the piece of shit terrible disaster garbage fire OS flew apart on the next reboot

sinsinewave
@sinsinewave

filesystems failed to mount, so i'm assuming your /etc/fstab got corrupted

i think Arch has a script for regenerating it called genfstab, can't remember the syntax but the archwiki should have it somewhere, which can regenerate it; mount the offending volumes in the recovery shell and run that and it may or may not work

alternatively your disk might've broken but since this is right after an update i think it's just a corrupted fstab or other filesystem failure like missing drivers and not a hardware fault

also i would suggest Void instead of Arch for stability since this thing doesn't break on updates like, ever, but also Void is a weirdass distro in other ways so maybe not the best choice unless you're a weirdo like me

You must log in to comment.

in reply to @mia's post:

MorningSong
@MorningSong

If that happened as part of a system update, 99% that's the new kernel not being able to find the drivers to mount those particular filesystems. If you call up your grub menu (holding shift at boot should do the trick if yours hides by default), can you boot up an older kernel version? (It might be under an "advanced options" submenu)

login to reply
ionchy
@ionchy

lmao I've done a similar thing (twice!) where I updated via pacman -Syu, ran out of storage, rebooted, and then just couldn't boot back in bc for some reason pacman just straight up deleted my kernel...... I had to boot into a live usb boot to mount the partition and install the kernel back
I have no idea if this is the problem you have but if you're missing a vmlinuz-* in /boot then I can help. otherwise good luck

login to reply
eclairwolf
@eclairwolf

You can log into your install from the installer disk.
Mount the drives and setup wifi like you did when you installed arch, then run arch-chroot /mnt and pacman -Syu linux-lts to install the long-term support kernel. That miiight fix the issue, assuming that's the package that broke the install.

login to reply
wffl
@wffl

I can't help you, but if you'll allow me to trauma dump for a little...

my arch almost consistently kernel-crashes while pacman -Syu'ing (similarly with an aur helper). consistently as in: this happened like 3 times in this month and a million times while fixing those. and since pacman -Syu may update the kernel image, almost every time this required booting with live cd and reinstalling the broken boot...

I thought that we fixed that (by disabling PCIe power saving, so ssd does not spontaneously disconnect) but today it happened again 🥲

login to reply
WISHETH
@WISHETH

Doubt this is the issue but I'll bring it up anyways because I have no background here and this happened to me while I was clueless (I still am): Could this be an fstab issue? If your external hard drives paths are hardcoded in fstab there's a chance that the drive just Doesn't Mount In Time and your computer supershits itself unless those drives are unplugged

login to reply
Pinned Tags