#[SOLVED] Can't login on my LUKS LVM Arch Linux system.
1427 messages ยท Page 2 of 2 (latest)
That includes what we say too because you should have known you had applied the old snapshot
because it's your pc
Yeah I got confused with the snapshot but I thought it would only delete those old configs 4 months old
loading the liveCD now
and do iwctl to connect to my wireless
Nope but you applied the old snapshot before removing
yeah that's it, I screwed up ๐ฆ
And that is what started your issues
fyi, this is why I use ext4 it's simple
I opted for btrfs mostly for the snapshot recovery stuff iirc. Ended up causing way more trouble than what was worth obviously
OK gonna mount now
I should mount everything, including boot, right?
yup
I always forget the Luks open command, hold on
having issues with the mount
mount /dev/mapper/arch-root /mnt
mount /dev/mapper/arch-home /mnt/home
the second command is not working
And it's now the right subvol right?
haven't checked, still trying to mount home
yeah, something weird going on with the mount
Welll did you check that it exists
says it's a read only filesystem /root.zdirs
when I do cd /mnt I can only see a few folders, namely bin lib lib64 and sbin. All red for some reason
What do you mean?
the dir
what subvol are you mounting now
you still didn't set the default subvol ?
I am trying to mount arch-root
you're mounting some random subvol
I am still on the liveCD, haven't chrooted or anything
you have to specify the subvol since you still haven't fixed that issue
You're mounting the default subvol
which is something
oh right, because I am using the "old" one from snapshots, is that it?
ยฏ_(ใ)_/ยฏ
I'm confused, am I missing something?
or did I do some wrong step?
I connected wifi through iwctl, made sure it was on, checked with lsblk, open the encrypted media and now trying to mount root but it is the wrong subvolid, is that it?
Maybe the * in the snapper list was the snapshot in use or something
Did you read the snapper docs
https://documentation.suse.com/sles/12-SP5/html/SLES-all/cha-snapper.html#sec-snapper-snapshot-boot did you run rollback at one point
Probably you did
Yeah but never saw anything like "number+" and I know snapper-rollback is not to be used but snapper rollback instead. I created 2 configs and deleted one, or I thought I did
not since this entire thing started
at some point being weeks or months ago then probably
so only the root, no home or anything?
.
oh so do that as in mount -o /dev/mapper/arch-root subvol=/ /mnt?
-o subvol=/
Also mounted home and boot. Should I mount efi under mnt as well?
since the issue is with firmware, it's necessary, right?
BIOS, that is
hmm says that mountpoint does not exist. I suppose it's because that entry is commented in fstab, right?
congrats, this thread hit 1k+ without a bios update
yeah, I am trying (
so should I chroot now?
is it properly mounted?
ok I think I am chrooted properly
ok doing that.
The bios update isn't relevant to this issue
you're gonna have lots of those
Should I just click y in all of these?
hold on
pacman -Rns electron33
read this, https://archlinux.org/news/manual-intervention-for-pacman-700-and-local-repositories-required/ then do that
That is to remove electron and respective cache, right?
yes
Doesn't seem relevant
Yeah I am reading that link now
Remember to update/rebuild your aur packages too @sweet arrow
yet
It seems to be talking about permissions to download the files if I don't have them, is that it?
So do pacman -Rns next step, right?
photo please
It's from 2014-09-14 while this snapshot is from early this year
Just trying to make sure I don't screw up anything
So clear on the pacman -Rns electron, I'm not gonna do anything wrong?
@sweet arrow electron33 not electron
So now I am gonna have to delete vesktop and probably discord, right?
just vesktop
Yeah it's just that Discord also has that dependency iirc
OK I removed vesktop bin
Should I do pacman -Syu again?
yes
yes
My internet connection is not very fast so this one will take a while...
But it seems like good news if I am following right
yes
Yeah installing 3G, I'll message once it's done
This is because the aur package is out of date
When the system is not doing a big jump like this then presumably you have already updated vesktop-bin at some point and thus electron33 is a orphan
Either way not a major issue, worst case scenario, just have to get vesktop again after. If that is the only loss all good
And after pacman, I have to do yay -Syu as well? But outside of chroot since doing yay as root is not safez right?
su -l yourusername to switch to your user
yay, or makepkg as a whole, does not allow it to be ran as root
Oh that's right
Yeah makes sense
It finished downloading this month's firmware
And after all this, do the fwupdmgr-get updates refresh
correct?
Dunno if it works in chroot since it didn't work outside
but that was because it was with the wrong subvolid back then, no?
and if it's downloading linux-firmware, shouldn't that have BIOS update as well?
no
at two thirds of the way now
so assuming all the updates go well, it's su -l next for the yay updates? Or fwupdmgr first?
@sweet arrow try fwupd
then do the yay out of the chroot, in y our booted partition
ok so fwupd in the chroot live CD then reboot to the booted thing
yes
and should boot without issues or needing to change the subvolid this time, if I understood correctly
yes, you are right
Fwupd didn't work because it was a partial upgrade
So maybe in chroot it'll work because it was a full update
ok just a couple more minutes until pacman finishes
and it's fwupdmgr get-updates and then refresh, are those the only 2?
Nop
get devices first
and then a couple more commands after
finished downloading and verifying, installing now
You dont even need to update the bios now because it's not related to the issue
regen the grub config
Now, in the liveCD?
in the chroot
if using grub
Yeah I have GRUB
so we hopefully can get rid of the default snapshot subvol thing
So I should do grub -o ... command now, right?
so not install but skip to the config section
yeah this one grub-mkconfig -o /boot/grub/grub.cfg
yup
nope
also check if the top entry in the grub menu will boot the snapshot subvol, if it does then find the one which doesn't boot it
So you don't have to keep editing it
it ought to do the correct one automatically with just the command, right?
It still has that 178 snapshot and created more apparently, if I understand it right
Hold on, snapshots inside snapshot
So you were running 178
without doing something to correctly continue from it
so there's snapshots in there
maybe you could restore one of those
So is that good news?
Well, would it not be redundant now since I did the pacman Syu?
And the home was not affected?
Is it the correct GRUB though, is it how it was supposed?
Your grub is on the separate partition
Can you boot 1696 snapshot
So you want me to leave chroot and try booting normally now, no live CD?
yeah
Got rid of my GRUB theme
Show the snapshots menu
This is the default it has
1696 is a couple days old so before bricking this, I guess
Should I boot that one?
ye
Then I boot on the second option, right?
just boot it
Not good
And I meant second option because clicking enter on the first was not doing anything
I wonder what those snapshots have
So I went with the initramfs fallback img
Well, apparently nothing good or are only in read only
So should I try booting normally, no snapshot this time? First option?
Boot the iso and mount 1696 with it's subvolid
Boot the iso, you mean the liveCD again?
Gonna try to boot into the system normally, no snapshots first
This says you should be able to boot a snapshot and then rollback to it https://documentation.suse.com/sles/12-SP5/html/SLES-all/cha-snapper.html#sec-snapper-snapshot-boot
Maintain, monitor and customize SLES
but maybe you use some weeird stuff
idk what snapper-rollback does
you need to verify what's in those and then apply it if you want
Gives me some weird no IRQ handler but let's me input password. Should I go for it anyway?
No risk in just trying to boot that, right?
Yeah same error
Says sbin init does not exist
mount
In the liveCD?
Yeah I am turning liveCD again
Does the fs have /sbin/init now
It's possible, I should have regenerated that, I think that was that second step that I was thinking about, no?
Are you sure you didn't just boot the previous snapshot now
because the choice was saved?
Oh it's possible but I don't think so. I checked and said root, did not mention the snapshot in the options
How about booting the 184 snapshot
or specifying the / subvol
or looking in advanced options and booting something from there
I'm on the liveCD now
mount 1696 and see what it has
So just mounting arch root as /mnt
And not chrooting but only looking at what's inside 1696?
This?
I suppose the default subvol now the one with all those snaphsots inside it
It's weird... Inside home has another user which I created once when I screwed up something with PAM
So I am not sure what I am looking for
Maybe you just gotta boot the newest snapshot
and the top entry in the grub was booting that now
because it was now the default subvol
So it updated automatically?
ยฏ_(ใ)_/ยฏ
Should I leave liveCD again?
ยฏ_(ใ)_/ยฏ
If you don't want to do anything else there
just boot then Ig
and specify the / subvol if booting the newest subvol does nothing
and set it as the default then
I am not sure, shouldn't I try the mkinitcpio thing first?
or set it now
How?
Not relevant anymore because there was no stuff in there
it was mounted but no sbin
you can now change the default to / because you now have free space
previously you couldn't
I wonder what snapshot this updating was done in lol
So change the default to / while on the liveCD?
btrfs subvolume set-default 5 /
Is that the command I should do?
adjust the path depending on if chrooted or not
So without being chrooted I should do /mnt and chrooted /?
yep
But better to be chrooted?
Doesn't matter
yeah
also I found this
Grub will look for grub.cfg in the subvolume that you chrooted to and executed grub-install. So to get grub to read the correct grub.cfg in the correct subvolume:
SO INSTALL GRUB AGAIN IF IT DOES NOT WORK
AND DO IT IN THE RIGHT SUBVOL NOT LIKE IT"S NOW
Adjust the path...
Yeah, grub-install I missed that
You're right, sorry
OK did that, no error message, what now?
I'm sorry, really. I'm just having a difficult time
How do I know if it worked?
I take it I have to do grub-install now, not chrooted?
The generate another GRUB config?
Remember to have the esp mounted
and the install is done in chroot
esp? the EFI?
yeah can't mount anything under /mnt but I can mount /home
and /boot
just not under /mnt
...
and can't mount the EFI partition
the path depends on if chrooted or not
you are right, let me chroot then
bruh
sorry, once again, it's just that it's late and I can't think straight. I appreciate your patience ofc
Still can't mount efi even chrooted
Like this?
yep
so do the grub config again now?
install and grub config
.aw grub
yep
now boot and use the default grub menu entry
OK so if I am following right, what this now did is, HOPEFULLY, generated a new GRUB entry but this time with the correct, updated mount points
fyi, you can limit how many snapshots are made
Yeah so leave chroot amount and try to boot normally but confirm first in the boot entry what I'm booting into, right?
yes
While doing the GRUB config or after?
no
either or
You should later look in to the 1696 snapshot or something to see if you can restore your state the one with all your configs
or copy your necessary config
and the package list
boot
with wifi?
But with that login, not autologin
Let's see
Possibly. It recognises the adapter at least
ping -c3 archlinux.org
Aka did you do the update in the correct subvol
Well, the touchpad now works
Let me try to connect to a hotspot from my phone
Yeah, seems like it
Sound works as well
What should I do now?
Oh right, I should do fwupdmgr update now, right?
As well as yay
Hypridle.service now runs automatically but still have this error
welp now you have a functioning system
You'll need to decide if you want to get back to a state that was not 5 months ago
Yeah, so yay, double meaning right?
Shouldn't this state be the updated one?
Is it?
Did grub have the theme?
It could be the updated one but not the same as the one new one
So 5 months of state lost
Oh yeah, the theme seems to be reset but the rest ought to be updated
Or maybe not, you are right... Hour went back to UTC so... Not sure
It's just that the home with all the configs and quality of life stuff is the same so not easy to tell right away
No, it didn't
So should I do a yay -Syu fwupdmgr and then try to fix the rest step by step later on?
There is certainly some oddities still, can't access my WiFi only hotspot, strange
Driver?
Doing a yay update now. Then gonna do the fwupdmgr update
I prolly just would have backed up my most recent files and then reinstalled
Taken a list of my packages and then backed up the etc and then copied what I need from it
Possible but strange that links to the hotspot
With lspci -k?
Yeah
It's either some certificate or my WiFi itself acting up. Or the way it's configured
Maybe it's just because it is connecting automatically to the VPN and that is causing issues
But seems like a reasonably functional system now, right?
Guess so
Reinstall the system (dont reformat home, only root) if it doesn't work by tomorrow
Check if you can copy your etc and package list from the old but new snapshot
You can chroot in to it while in the installed system
Just gotta install the install utils
Them you can run the pacman command to make a package list
It's on the wiki
I am doing the yay now, still
then doing the fwupdmgr then I need to rest, honestly haha
still need to go through carefully about what changed and if there is stuff missing
OK done with yay
Also, it was an issue with VPN. It connects automatically to VPN which is not working for some reason, so I disabled that and works now, my WiFi, that is
And just did the fwupdmgr get devices get updates and refresh
I think it worked fine
Just downloading vesktop because it was the only thing I had to uninstall in the liveCD iirc
Still gotta figure out the issue with the VPN, Bluetooth and time
@sweet arrow is this solved?
I think so, even though I still need to figure out about the boot and the snapshots
Thanks to both of you!
You have lots of patience haha
also already changed the time back to correct, done the fwupdmgr without issues (I think) WiFi no issues, downloaded another VPN config, no issue, Bluetooth bit weird but probably fixable without much hassle
as for the snapshots I have rn:
โโโโโผโโโโโโโโโผโโโโโโโโผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโผโโโโโโโโโโโผโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโ
0 โ single โ โ โ root โ โ current โ
178 โ single โ โ Thu 09 Jan 2025 06:51:01 PM WET โ root โ โ writable copy of #160 โ
179 โ single โ โ Wed 21 May 2025 06:23:43 PM WEST โ root โ number โ boot โ
180 โ single โ โ Wed 21 May 2025 07:00:01 PM WEST โ root โ timeline โ timeline โ
181 โ single โ โ Wed 21 May 2025 08:00:01 PM WEST โ root โ timeline โ timeline โ
182 โ single โ โ Wed 21 May 2025 08:29:04 PM WEST โ root โ number โ boot โ
183 โ single โ โ Wed 21 May 2025 09:00:07 PM WEST โ root โ timeline โ timeline โ
184 โ single โ โ Wed 21 May 2025 10:00:09 PM WEST โ root โ timeline โ timeline โ
185 โ single โ โ Thu 22 May 2025 01:08:25 AM WEST โ root โ number โ boot โ
186 โ single โ โ Thu 22 May 2025 02:00:15 AM WEST โ root โ timeline โ timeline โ
so it is making automatic snapshots as intended but gotta figure that out otherwise I risk getting similar issues in the future, right?
... solved
#9742 ๐ฃ If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.
- You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
- You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".
Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you
@sweet arrow
[SOLVED] Can't login on my LUKS LVM Arch Linux system.
178 has the weird snapshots inside it
Remember that
from what I gather from 178, looking through the info, it's a writable copy of 160 which does not exist anymore and is from January. I only seem to have one config list for snaphots, I assume it's still doing the regular autocleanup, making one per boot, regular stuff. I don't see any 1698 folder, it is starting on 178, I assume those are gonna be loaded as snapshots on boot as well. Not sure if there is an issue at this point ๐
but so far seems to be working as intended
the only weird things so far was an app was uninstalled since it was not from pacman nor yay but downloads and such seem to be the same so maybe some temp files deleted? And still can't make the sddm autologin work and haven't tried to make the GRUB themes back, gotta make sure I don't mess anything up in that regard. I assume I don't have to change anything in the PAM
Also, I think I figured out how so many space was freed. My Steam games seem to have been uninstalled which would account for the extra 40/50G of space, probably
it does seem, however, to be a snapshot from January. I checked and the one game that was not uninstalled had the last hard save being from May 16, almost a week ago, even though I had made other saves at least until a couple of days after that. However, the autosaves were all from early January
You only rollbacked root, your home was not affected
Unless you also did something with your home snapshots, if you even take those
Or you save your games in the root for some reason
Yes, I do save games in root, Steam is there. I used to take home snapshots but I delete (or I think I did) that config. At least it does not show. So only root is snapshotted
Wtf
Then you'll have to get them from or restore the new snapshot
Or maybe rsync with all the correct flags
Yeah, I did that because I made my home folder too small so it would not be possible so the Steam directory is there.
I don't think there's a snapshot of those anymore, it's either the original one from January or the ones being done from yesterday onward. It was just odd that there were still any saved games at all and pointing the discrepancy between the last autosave bein from January yet having hard saves from under a week ago
There were snapshots inside of a snapshot