Linux failed to start load kernel modules

Arch Linux

Then I get a message saying I am in emergency mode and asking for my root password.

Here is the result of the commands suggested:

[tan@bobby ~]$ systemctl status systemd-modules-load.service ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled) 1 Active: failed (Result: exit-code) since Sun 2018-01-28 02:10:16 NZDT; 7min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 224 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 224 (code=exited, status=1/FAILURE) Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. [tan@bobby ~]$ systemctl status boot-efi.mount ● boot-efi.mount - /boot/efi Loaded: loaded (/etc/fstab; generated) Active: failed (Result: exit-code) since Sun 2018-01-28 02:10:17 NZDT; 7min ago Where: /boot/efi What: /dev/disk/by-uuid/F62F-E8CB Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 227 ExecStart=/usr/bin/mount /dev/disk/by-uuid/F62F-E8CB /boot/efi -t vfat -o rw,realtime,fmask-0022,codepage=437,iocharset=iso-8859-1,shortname=mixed,utf8,errors=remount-ro (code=exited, status=32)

I tried restarting with systemctl status systemd-modules-load.service but it says the control process exited. For boot-efi.mount, it just says mount failed. I notice that many modules must be missing. For example I don’t even see my wireless interface.

The only thing I can think of that could have caused this is that I created a package, and then installed it with pacman -U —force. I did this because I had previously installed that software from source without creating a package and wanted a «cleaner» install of it. I guess I was wrong, or I screwed up the package creation part.

Can anyone help me troubleshoot this?

Last edited by eichan (2018-01-28 17:58:38)

Источник

Failed to start Load kernel modules

Xubuntu 16.04 (В 15.10 было то же самое). Решил разобраться. При старте системы ошибка вышеописанная, предлагается ввести systemctl status systemd-modules-load.service Ну я ввожу. И что я вижу?

vodka@vodka-PC:~$ systemctl status systemd-modules-load.service ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-05-16 18:15:51 MSK; 4h 38min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 540 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 540 (code=exited, status=1/FAILURE) May 16 18:15:51 vodka-PC systemd[1]: Starting Load Kernel Modules. May 16 18:15:51 vodka-PC systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE May 16 18:15:51 vodka-PC systemd[1]: Failed to start Load Kernel Modules. May 16 18:15:51 vodka-PC systemd[1]: systemd-modules-load.service: Unit entered failed state. May 16 18:15:51 vodka-PC systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. 

Кажется ничего интересного.

Дальше ввожу journalctl -u systemd-modules-load.service:

vodka@vodka-PC:~$ journalctl -u systemd-modules-load.service -- Logs begin at Mon 2016-05-16 18:15:44 MSK, end at Mon 2016-05-16 22:48:45 MSK. -- May 16 18:15:44 vodka-PC systemd-modules-load[236]: Inserted module 'lp' May 16 18:15:44 vodka-PC systemd-modules-load[236]: Inserted module 'ppdev' May 16 18:15:44 vodka-PC systemd-modules-load[236]: Inserted module 'parport_pc' May 16 18:15:44 vodka-PC systemd-modules-load[236]: Inserted module 'coretemp' May 16 18:15:44 vodka-PC systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE May 16 18:15:44 vodka-PC systemd[1]: Failed to start Load Kernel Modules. May 16 18:15:44 vodka-PC systemd[1]: systemd-modules-load.service: Unit entered failed state. May 16 18:15:44 vodka-PC systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. May 16 18:15:51 vodka-PC systemd[1]: Starting Load Kernel Modules. May 16 18:15:51 vodka-PC systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE May 16 18:15:51 vodka-PC systemd[1]: Failed to start Load Kernel Modules. May 16 18:15:51 vodka-PC systemd[1]: systemd-modules-load.service: Unit entered failed state. May 16 18:15:51 vodka-PC systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. vodka@vodka-PC:~$ 

И опять пусто! Я не вижу имя модуля\демона\службы, из-за которой возникает ошибка. Так как узнать, что вызывает ошибку? Всё работает нормально, но хочу разобраться. Или я чего-то упустил?

Источник

Arch Linux

Hi, I did some moving around drives (with a gparted live volume) and repartitioning/copying stuff, and finally got my EFI bootloader to show the Arch linux option.

The only problem is, I’m getting this error:

[FAILED] Failed to start Load Kernel Modules. [FAILED] Failed to mount /boot. [DEPEND] Dependency failed for Local File Systems. [FAILED] Failed to mount /c. [FAILED] Failed to mount /d. You are in emergency mode. 

My /etc/fstab looks like this

# /dev/sda3 LABEL=archlinux UUID=924bc4b4-47c6-4264-b17b-a9d854b819fc / ext4 rw,relatime 0 1 # /dev/sda2 LABEL=Windows10 UUID=60306AE7306AC41E /c ntfs rw,nosuid,nodev,user_id=0,group_id=0,allow_other,blksize=4096 0 0 # /dev/sdb1 LABEL=CRUCIAL\134x202TB UUID=24A21F40A21F1640 /d ntfs rw,nosuid,nodev,user_id=0,group_id=0,allow_other,blksize=4096 0 0 # /dev/sdb2 LABEL=EFI UUID=67E3-17ED /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2 # /dev/sda4 UUID=cb5c0b12-4a3d-46a2-bb16-4040d75bdeff none swap defaults 0 0

I can boot into my arch live usb volume just fine, and everything looks normal, the .img file is in place, the partition UUIDs are correct in my Clover configuration xml file. (This was a hackintosh machine, I nuked the hackintosh partition but kept the Clover EFI bootloader)

What else can I do to figure out what’s going on?

Last edited by n8jadams (2022-07-10 15:27:47)

#2 2022-07-09 03:43:41

Re: [SOLVED] Failed to start Load Kernel Modules

If you repartitioned, the UUIDs chage. You say they are correct in your clover config, but that’s not relevant as the kernel is booting. What is relevant is your fstab. Old UUIDs there would explain all your symptoms.

«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman

#3 2022-07-09 14:58:41

Re: [SOLVED] Failed to start Load Kernel Modules

I mounted all of my drives while using the live install volume. Wouldn’t the genfstab command have accounted for this?

#4 2022-07-09 15:06:55

Re: [SOLVED] Failed to start Load Kernel Modules

With the ‘Failed to start Load Kernel Modules’ in there, this almost certainly means your bootloader is loading a different kernel than what’s installed. Did you update the system with the /boot partition mounted?

#5 2022-07-09 15:07:37

Re: [SOLVED] Failed to start Load Kernel Modules

I mounted all of my drives while using the live install volume. Wouldn’t the genfstab command have accounted for this?

Depends on when where and how you ran it.
Compare your fstab to «lsblk -f»

Last edited by seth (2022-07-09 15:08:14)

#6 2022-07-09 15:11:50

ewaller Administrator From: Pasadena, CA Registered: 2009-07-13 Posts: 19,347

Re: [SOLVED] Failed to start Load Kernel Modules

Scimmia’s point seems relevant.
Compare the version numbers reported by uname -a and by pacman -Q linux (assuming you are running the stock kernel)

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#7 2022-07-09 15:14:17

Re: [SOLVED] Failed to start Load Kernel Modules

I mounted all of my drives while using the live install volume. Wouldn’t the genfstab command have accounted for this?

Live install medium, or the gparted live medium? If you only ran genfstab with the initial install, then later used gparted to repartition and «copy stuff» as you said in your first post, then the UUIDs have changed and will need to be updated.

«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman

#8 2022-07-09 16:26:12

Re: [SOLVED] Failed to start Load Kernel Modules

While booted into my arch installation live usb volume, after running arch-chroot /mnt I ran this:

$ uname -a Linux archiso 5.12.13-arch1-2 #1 SMP PREEMPT Fri, 25 Jun 2021 22:56:51 +0000 x86_64 GNU/Linux $ pacman -Q linux error: package 'linux' was not found $ pacman -Q linux-zen linux-zen 5.18.7.zen1-1

The versions are different, but I’m not exactly sure where to go from here.

#9 2022-07-09 16:28:24

Re: [SOLVED] Failed to start Load Kernel Modules

The uname output there is irrelevant as that’s the kernel from the live usb. Use the following:

# from within the chroot file /boot/vmlinuz-linux* # or outside the chroot but w/ partitions mounted under /mnt file /mnt/boot/vmlinux-linux*

Last edited by Trilby (2022-07-09 16:28:41)

«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman

#10 2022-07-09 16:33:08

Re: [SOLVED] Failed to start Load Kernel Modules

That’s not gonna help if the OP is booting the wrong device.
«uname -a» will also work from the rescue shell.

#11 2022-07-09 16:47:14

Re: [SOLVED] Failed to start Load Kernel Modules

$ file /boot/vmlinuz-linux* /boot/vmlinuz-linux-zen: Linux kernel x86 boot executable bzImage, version 5.18.9-zen1-1-zen (linux-zen@archlinux) #1 ZEN SMP PREEMPT_DYNAMIC Sat, 02 Jul 2022 21:03:08 +0000, RO-rootFS, swap_dev 0XA, Normal VGA

So pacman said 5.18.7.zen-1-1 and the file command says 5.18.9-zen-1-zen. What should I do now?

Last edited by n8jadams (2022-07-09 16:51:16)

#12 2022-07-09 16:54:34

Re: [SOLVED] Failed to start Load Kernel Modules

Is that /boot on sdb2 or sda3?

#13 2022-07-09 17:01:03

Re: [SOLVED] Failed to start Load Kernel Modules

Is that /boot on sdb2 or sda3?

sdb2, sda3 is my linux (root) partition

Last edited by n8jadams (2022-07-09 17:02:23)

#14 2022-07-09 17:07:19

Re: [SOLVED] Failed to start Load Kernel Modules

Is there a /boot/vmlinuz-linux* on sda3 as well (and is that 5.18.7.zen-1-1)?

Sidebar: how did you end up w/ a dated package but updated actual kernel? Did you at some point downgrade the kernel?

#15 2022-07-09 17:56:39

Re: [SOLVED] Failed to start Load Kernel Modules

To describe what I did, from my arch linux install live volume, I ran this

$ mount /dev/sdba3 /mnt $ mount /dev/sdb2 /mnt/boot $ arch-chroot /mnt # and then the rest of the commands. $ uname -a $ pacman -Q linux-zen $ file /boot/vmlinuz-linux*

#16 2022-07-09 19:50:41

ewaller Administrator From: Pasadena, CA Registered: 2009-07-13 Posts: 19,347

Re: [SOLVED] Failed to start Load Kernel Modules

As one would expect you are using the kernel from the install media in your chroot.

What happens when you boot your system directly? The next steps to solve this depend on the answer

This depends on the kernel that is installed in your boot volume and which kernel your bootloader picks. When that kernel, whatever it is, starts it will start to look for its kernels in your root partition. If the kernel from which you are booting is different than that from which is installed on your root volume, the kernel will not find its modules. This can happen a few ways. The usual cause is for the boot partition to have not been mounted on /boot when the kernel was installed. Another cause is that the boot loader is finding a kernel other than the one you would expect — sometimes this happens if you have two boot partitions and are not using the one you think you are using.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#17 2022-07-09 21:37:04

Re: [SOLVED] Failed to start Load Kernel Modules

I can’t seem to boot my system directly, it doesn’t show up in my motherboard’s boot menu. It shows up in the EFI bootloader, but when I boot into it, I get the original error message. Maybe I need to just nuke this partition and reinstall arch altogether, and just copy over my data once I get that working.

#18 2022-07-09 22:14:44

Re: [SOLVED] Failed to start Load Kernel Modules

Doesn’t the original error drop you into a rescue shell?

Is there a /boot/vmlinuz-linux* on sda3 as well (and is that 5.18.7.zen-1-1)?

Boot the iso, just mount sda3 to /mnt and check /mnt/boot/vmlinuz*

Источник