Hello Manjaro Community,
This is my first post here and I am by no means an expert. Actually I would like to learn how to tackle the issue I’m having here and that might arise in the future.
Background: I’ve been delighted by the ease of switching kernels in Manjaro and used it whenever I encountered some issue with a package. Instead of rolling back or fixing old issues, I went ahead and jumped to the next kernel. This started in 4.19, continued in 5.4 and made me update to 5.10 a few weeks back.
Since then I experienced weird behavior of my machine; namely the file system usage:
- after hibernation it wasn’t possible to access the fs anymore (IOError when calling poweroff in the
terminal). Rebooting fixed this.
- Not being able to boot the system anymore (screen goes black after booting, when shutting the system down via the power button, I can shorty see that there was some issue with the filesystem). Booting into Kernel version 4 “fixed” this. However I’d prefer to be able to use the newest Kernel.
So what to look for first?
The following info might be helpful:
grep -i -e linux[0-9] /var/log/pacman.log | grep \\[ALPM\]
[2021-02-09T16:22:42+0100] [ALPM] upgraded linux419 (4.19.167-1 -> 4.19.173-1) [2021-02-09T16:22:58+0100] [ALPM] upgraded linux54 (5.4.89-1 -> 5.4.95-1) [2021-02-17T13:32:29+0100] [ALPM] installed linux510 (5.10.15-1) [2021-03-01T09:43:52+0100] [ALPM] upgraded linux419 (4.19.173-1 -> 4.19.177-1) [2021-03-01T09:43:55+0100] [ALPM] upgraded linux510 (5.10.15-1 -> 5.10.18-1) [2021-03-01T09:43:58+0100] [ALPM] upgraded linux54 (5.4.95-1 -> 5.4.100-1)
lsblk -f | grep -e ^[^l] #don't show loop devs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT nvme0n1 ├─nvme0n1p1 vfat FAT32 36B3-C634 299M 0% /boot/efi └─nvme0n1p2 crypto_LUKS 1 0c221974-333d-4860-b4bd-0464f65c392f └─luks-0c221974-333d-4860-b4bd-0464f65c392f ext4 1.0 48e1e467-5f06-4d58-a252-09a1a9e7cfa6 50,2G 73% /
Thanks for any help