After this, start with mounting your @ subvolume first
sudo mount -o subvol=@ /dev/nvme0n1p2 /mnt
followed by the others:
Yeah, I haven’t done chroot for some years so of course I have forgotten how to do it and still bit too jet-lagged to be able to follow simple instructions 
now everything is mounted, and
[liveuser@eos-2023.03.06 ~]$ sudo mount /dev/nvme0n1p2 /mnt/home
mount: /mnt/home: /dev/nvme0n1p2 already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.
this seems to be working, will make sendlog now and edit this post.
*Edit
@pebcak the send log doesn’t seem to be available at all, not sure if I should umount before doing this.
[liveuser@eos-2023.03.06 ~]$ tail -n200 /var/log/pacman.log | eos-sendlog
tail: cannot open '/var/log/pacman.log' for reading: No such file or directory
[liveuser@eos-2023.03.06 ~]$
This should have been:
sudo mount -o subvol=@home /dev/nvme0n1p2 /mnt/home
but for what you would need to do now it is not relevant.
I did that correctly
[liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@ /dev/nvme0n1p2 /mnt
[liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@cache /dev/nvme0n1p2 /mnt/var/cache
[liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@home /dev/nvme0n1p2 /mnt/home
[liveuser@eos-2023.03.06 ~]$ sudo mount -o subvol=@log /dev/nvme0n1p2 /mnt/var/log
[liveuser@eos-2023.03.06 ~]$ sudo mount /dev/nvme0n1p2 /mnt/home
mount: /mnt/home: /dev/nvme0n1p2 already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2023.03.06 ~]$ tail -n200 /var/log/pacman.log | eos-sendlog
tail: cannot open '/var/log/pacman.log' for reading: No such file or directory
I forgot the /efi mount
Yes, mount that as well.
Yes, this fine.
You wouldn’t need to do this afterwards:
Then you seem to have forgotten the last step, the arch-chroot part:
sudo arch-chroot /mnt
Personally, I would run an update at this stage.
I don’t think what may have gone wrong by some updates one month ago is interesting anymore 
I did the log, can be found here http://ix.io/4CpZ
Maybe it is interesting, but this only took seconds to make.
Now to install kernel and dracut.
I would update the system first.
only 209 updates 
bit less than I was expecting.
I did rebuilt dracut before you mentioned that I should update first… got a bit exited over here, throwing out some errors, maybe I just need to restart… Worst case I take backup and reinstall.
The more the merrier!
This doesn’t matter now.
Do the updates. Most probably they include update to the kernel as well so rebuilding the kernel images should happen automatically.
Post any error messages you get, if any.
I am getting error, and now I can’t copy/paste from terminal, so I’ll write it as well as I can
-> error fetching gklib: System has not been booted with systemd as init system (PID1). Can't operate. Failed to connect to bus: Host is down
context: exit status 1
error fetching jdk: System has not been booted with systemd as init system (PID1). Cant operate. Failed to connect to bus: Host is down
context: exit status 1
error fetching python-protonvpn-nm-lib: System has not been booted with sys temd as init system (PID1). Can't operate. Failed to connect to bus: Host is down
context: exit status 1
error fetching metis: system has not been booted with systemd as init system (PID1). Can't operate. Failed to connect to bus: Host is down
context: exit status 1
I am guessing I could just skip those and get all the other updates.
Don’t do yay, do:pacman -Syyu
I saw dracut in there as well. Update is going.
All updates whent fine, will try rebooting now and see what is what 
Oh my, my own desktop again, everything smooth, everything nice… I love it. Thank you for your time and patient @pebcak
1 Like
That’s great! I am glad you got it all back up and running!
Enjoy your system and a nice weekend after what I suppose to have been a marvelous vacation in 
.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.