[SOLVED] Failed to lookup 'crypto_user' : function not implemented

plebeian · 2018-07-27 02:05:55

Hello again, apparently, the problem from my last topic is not really solved, as when I do pacman -Syu before installing several packages earlier, the problem appears again. But fortunately, the boot process is not quiet so it spew out some info that might be useful. The info showed that the kernel failed to load the modules, then proceed to continue the boot process. After the process done, the display manager didn't show up, again like last time, so I tried logging in from CLI with alt+f2 and it works.

So, I checked uname -a again, and just like last time, the installed kernel is different with the one running (somehow it's back to 4.16.8-1 while the installed is 4.17.9-1). Since there's an info on why the kernel failed to load, I try to check it, and here's the result:

● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled) 
        Active: failed (Result: exit-code) since Fri 2018-07-27 05:52:19 WIB; 1min 22s ago
        Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 225 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) 
        Main PID: 225 (code=exited, status=1/FAILURE)
Jul 27 05:52:19 toasty systemd-modules-load[225]: Failed to lookup alias 'crypto_user': Function not implemented 
Jul 27 05:52:19 toasty systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE 
Jul 27 05:52:19 toasty systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. 
Jul 27 05:52:19 toasty systemd[1]: Failed to start Load Kernel Modules. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

And like last time, I downgrade the kernel to the one currently running, and display manager works again. Any idea why this happen? Keep in mind that I don't have a separate boot partition, so my fstab doesn't have a line about it

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda6
UUID=cf1e3f36-b9bf-47ce-b420-e9a4a9a7e9f6       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sda8
UUID=aa3bc63c-9bf5-4b58-ae9c-18c56f195f6e       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sda7
UUID=72047c9f-c6dc-4824-ac02-29699d7e9fe6       none            swap            defaults,pri=-2 0 0

Could this be the cause of why this happens after I do system wide upgrade? Or is it just some module 'magically' decided doesn't want to load ? Also, I have yet to try upgrade the system again, I'll report back with the result after I do pacman -Syu again

EDIT: Apparently, the first install of the linux kernel goes to the /dev/sda1, which is the first bootable partition in the table. So, the problem is solved when I mount /dev/sda1 as the /boot then upgrade the kernel again as suggested by seth, and make sure the partition can be written, considering it's an NTFS because of dual booting w10

Last edited by plebeian (2018-07-27 12:22:11)

seth · 2018-07-27 04:59:36

And did you this time mount /boot before updating?

plebeian · 2018-07-27 07:21:21

seth wrote:

And did you this time mount /boot before updating?

Since Trillby told me that it's actually a bad thing to do, I didn't. I only do pacman -Syu without mounting anything, then install the packages, mostly codecs for cmus and mpv, after it's done, I checked the installed vmlinuz-linux image in /boot with file, and it showed 4.17.9-1 kernel, so I thought there's nothing wrong. I rebooted then the problem came back up

loqs · 2018-07-27 08:33:38

plebeian wrote:

seth wrote:
And did you this time mount /boot before updating?
Since Trillby told me that it's actually a bad thing to do, I didn't.

Please reread what Trilby actually wrote.

Trilby wrote:

plebeian wrote:
So recently I did a system wide upgrade, but unfortunately, as the title say, when I reboot, it keeps booting to a different kernel. I've searched for a few solution but to no avail, one solution mentioned that I need to downgrade, reboot, mount the boot, then upgrade again, so I did, ended up with a downgraded kernel, and luckily, everything works fine so far. So I tried to upgrade again, this time mounting the root as the /boot
What? No no no. Don't do that. That solution was for a similar symptom when the user did have a separate boot partiton but failed to have it mounted during the upgrade - then they would mount the boot partition at /boot. Never mount your root partition at /boot - in fact doing so would cause the symptoms you are having (as well as some stray files like a kernel and initrd image in the root of your filesystem).
So go back to the start. Describe the original problem. Run `pacman -Syu` normally (e.g. with no crazy remounting of anything). Then reboot.

seth · 2018-07-27 09:06:37

The problem with the other thread is that your assumption you were *not* using a boot partition is likely bonkers.
Look at "file /boot/vmlinuz-linux" for sda1 mounted to /boot and not mounted to /boot…

plebeian · 2018-07-27 09:07:45

loqs wrote:

plebeian wrote:
seth wrote:
And did you this time mount /boot before updating?
Since Trillby told me that it's actually a bad thing to do, I didn't.
Please reread what Trilby actually wrote.

I did, but this part

Trilby wrote:

That solution was for a similar symptom when the user did have a separate boot partiton but failed to have it mounted during the upgrade - then they would mount the boot partition at /boot. Never mount your root partition at /boot - in fact doing so would cause the symptoms you are having (as well as some stray files like a kernel and initrd image in the root of your filesystem).

is what made me think that I don't need to actually mount the boot partition to the root, as I have mentioned before, I don't have a boot partition, and the /boot is located in my root folder.

So I thought since I don't have a separate boot partition, aside from /dev/sda/1 which is used for the w10 boot, I don't need to mount the boot partition to my root partition, where the boot folder is located when upgrading. Or do I actually need to mount /boot on my root partition when upgrading my system? I'm sorry if this sound stupid, this is the first time I tried to use setup without the boot partition since my arch partition is on an extended partition

plebeian · 2018-07-27 09:26:41

seth wrote:

The problem with the other thread is that your assumption you were *not* using a boot partition is likely bonkers.
Look at "file /boot/vmlinuz-linux" for sda1 mounted to /boot and not mounted to /boot…

Sorry, I worded it very poorly, what I mean is a separate boot partition for my linux, as for now, I have my root as the boot partition too but not mounted as /boot, only as root, as you can see from here:

Device     Boot     Start        End    Sectors   Size Id Type
/dev/sda1  *         2048    1026047    1024000   500M  7 HPFS/NTFS/exFAT
/dev/sda2         1026048  208099447  207073400  98.8G  7 HPFS/NTFS/exFAT
/dev/sda3       208101376  209713151    1611776   787M 27 Hidden NTFS WinRE
/dev/sda4       209713152 1953521663 1743808512 831.5G  f W95 Ext'd (LBA)
/dev/sda5       209715200  524287999  314572800   150G  7 HPFS/NTFS/exFAT
/dev/sda6  *    524290048  775948287  251658240   120G 83 Linux
/dev/sda7       775950336  943722495  167772160    80G 82 Linux swap / Sola
/dev/sda8       943724544 1953521663 1009797120 481.5G 83 Linux

And the mounted partition, not omitted this time:

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=3537988k,nr_inodes=884497,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda6 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=925)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
configfs on /sys/kernel/config type configfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
/dev/sda8 on /home type ext4 (rw,relatime,data=ordered)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=708768k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sda1 on /boot type ntfs (ro,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=utf8,errors=continue,mft_zone_multiplier=1)

The sda1 is mounted on /boot as per your recommendation, but as for now, both have the same kernel version (4.16.8-1-ARCH) because I downgraded the currently installed kernel. I'll post result again after I run pacman -Syu, hopefully it still doesn't work , at least so we could figure out what is wrong

plebeian · 2018-07-27 11:52:14

seth wrote:

The problem with the other thread is that your assumption you were *not* using a boot partition is likely bonkers.
Look at "file /boot/vmlinuz-linux" for sda1 mounted to /boot and not mounted to /boot…

Welp, I found the culprit, the old kernel is inside /dev/sda1, sorry for being such a hard head, should I try to remove it or just mount the /dev/sda1 as /boot then do -Syu?

seth · 2018-07-27 11:55:50

The latter.
If things work fine afterwards, you should empty the unmounted /boot directory to spare you this kind of confusion and maybe consider adding sda1 to your fstab…

plebeian · 2018-07-27 12:19:16

seth wrote:

The latter.
If things work fine afterwards, you should empty the unmounted /boot directory to spare you this kind of confusion and maybe consider adding sda1 to your fstab…

Alright, all good now, I guess when dual booting, if we don't separate the linux boot partition, it'll take the first bootable partition as the place to put the boot then? Well, anyway, I still have a lot to learn and this has been very educational , thank you very much for your help, marking this as solved

Arch Linux

#1 2018-07-27 02:05:55

[SOLVED] Failed to lookup 'crypto_user' : function not implemented

#2 2018-07-27 04:59:36

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#3 2018-07-27 07:21:21

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#4 2018-07-27 08:33:38

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#5 2018-07-27 09:06:37

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#6 2018-07-27 09:07:45

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#7 2018-07-27 09:26:41

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#8 2018-07-27 11:52:14

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#9 2018-07-27 11:55:50

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

#10 2018-07-27 12:19:16

Re: [SOLVED] Failed to lookup 'crypto_user' : function not implemented

Board footer