No idea what these .kver files are all about, but the both my 5.4 and 4.19 kernel links aren’t here as expected.
After some more investigation I decided to go with a live USB and manjaro-chroot to fix the issue. Since I’ve got encryption for all partitions except the UEFI Fat32 partitions (one for Windows, one Grub/Manjaro) I ran into some more issues that I’d appreciate help with. I went as follows:
Enable UEFI only boot and disabled csm in my bios
Live boot of Manjaro via UEFI boot loader
Via sudo gparted “open encryption” on my Manjaro / partition /dev/nvme0n1p6
sudo mount -t ext4 /dev/nvme0n1p6 /mnt which is where I am stuck:
mount: /mnt: /dev/nvme0n1p6 already mounted or mount point busy.
My investigation on this issue yielded multiple suggestions, I unsuccessfully tried the following and more for the last couple of hours:
Booting live-usb via UEFI only (I didn’t do this at first) but it didn’t solve the issue.
Trying to mount via Gparted (doesn’t work, option to mount there is disabled/grayed out)
lsof | grep nvme0n1p6 shows nothing. so it seems the mount point is in fact not busy.
sudo umount /dev/nvme* lists me all the partitoins and says neither of them is currently mounted.
Any idea how I can get the partition mounted to get into manjaro-chroot? Thank you, any help is appreciated!
Here’s some more relevant info:
$ sudo manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
==> ERROR: You can't mount 0!
nvme0n1p6 is the only partition I decrypted via Gparted since that should be my Manjaro’s / which I’d like to mount to use with manjaro-chroot. I successfully mounted and unmounted nvme0n1p4 which is the UEFI Fat32 partition, but that doesn’t help.
Thank you so much flipper, /dev/mapper is exactly the missing part here that I wasn’t aware of , also thanks for mount /dev/nvme0n1p4 /mnt/boot/efi, I am finally able to manjaro-chroot.
I am trying pacman -Sy linux54 now and naturally get
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
as my machine got a power outage during an update.
Going with pacman -Qkk I get lots of warnings.
What would be the recommended course of action in this case? Simply go ahead and delete db.lck and run pacman -S?
Great progress, I re-installed my kernels and am finally able to progress in the booting of my original Manjaro installation. But now I am getting
[FAILED] Failed to start light display manager.
I guess the failed update damaged more stuff, but I also ran pacman -Syyu already. Perhaps related to the latest Nvidia issues? Probably not though. Will investigate later, got to head out for now.
I am actually no longer getting [FAILED] Failed to start light display manager. But booting simply gets stuck. Doing it without the quiet grub option, the last thing I see is [ OK ] Started hostname Service. Using the TTY, sudo journalctl reveals a couple of things:
...
kernel: proc: Bad value for 'hidepid'
...
bumblebeed[977]: Module 'nvidia' is not found.
...
bumblebeed.service: Failed with result 'exit-code'
...
And then
systemd-coredump[1707]: Process 1704 (lightdm-gtk-gre) of user 620 dumped core.
Stack trace of thread 1704:
#0 0x00007f733c1a1693 memset (ld-linux-x86-64.so.2 + 0x22693)
#1 ...
...
systemd[1]: lightdm.service: Failed with result 'exit-code'.
After that we get a systemd[1]: lightdm.service: Scheduled restart job, restart counter is at ... multiple times with the above lightdm stack trace inbetween each try.
Sorry for any typos, I typed this manually from some pics I took with the phone. I could upload them but not sure there’s anything else interesting.
Trying sudo lightdm –-test-mode --debug next I guess. Not sure it’s related to Nvidia, I think I’ve actually been using my integrated Intel graphics card before, dedicated graphics is Nvidia Quadro P2000 Max-Q.
Yes, weirdly inxi -G gives no output at all. pacman -Sy inxi complained about existing files, they don’t belong to any installed package acording to pacman -Qo inxi though, so I deleted and installed inxi again from within the live-usb’s chroot.
Now inxi -G gives
Graphics: Device-1: Intel driver: i915 v: kernel
Device-2: NVIDIA GP107GLM [Quadro P2000 Mobile] driver: nouveau v: kernel
Display: x11 server X.org 1.20.10 driver: intel
Message: Advanced graphics data unavailable for root.
If I do the same using the live-usb (I chose the open source drivers option), the last two lines change:
Not sure whether bumblebee came with Manjaro, perhaps I installed it at some point. Doesn’t seem to be part of the live-usb, although it apparently has both drivers (intel,nouveau) but probably doesn’t support Nvidia optimius (graphics hot-swapping) by default but rather via some command I assume. I guess I chose the proprietary (non-ope source) graphic drivers when installing Manjaro which might be powered by bumblebee.
lightdm –-test-mode --debug wasn’t helpful at all, it just gets me stuck in the loader.
I tried sudo mhwd -i pci video-hybrid-intel-nvidia-390xx-bumblebee and it failed, pacman indicating that it already exists in my filesystem just like it did with inxi.
I also noticed that I can’t run e.g. vim, nothing happens, like with inxi before I deleted files and reinstalled it… I suspect that some packages are still in some kind of corrupted state due to the crash during the system update… Does that make any sense? If that’s right, then fixing these corruptions somehow should also fix all my boot issues.
I can get into terminal since I sucessfully chrooted. But doing it from the live-usb is a bit more convenient really (wifi running, web browser to check stuff…)
Yes, I think I’ll open a new topic and mark this as solved if I still need help with graphic drivers. But I am also thinkink about just re-installing Manjaro, just not sure how complex it would be to do that within my current encryption setup and then mounting /home which I’ve got on a separate partition nvme0n1p7
, also thanks for 
