ERROR: module not found: 'dm_integrity' with mkinitcpio when installing through Manjaro Architect

Hello!

I'm currently trying to install Manjaro through Manjaro Architect and I'm getting error at the end with mkinitcpio

This is how my scheme is:

I previosly had Manjaro running fine, but I wanted to learn to install it from the Manjaro Architect and try encrypting my system.

This is the error that pops up after running mkinitcpio:

When chroot and running mkinitcpio -P

[manjaro /]# mkinitcpio -P

==> Building image from preset: /etc/mkinitcpio.d/linux44.preset: 'default'

  -> -k /boot/vmlinuz-4.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.4-x86_64.img

==> Starting build: 4.4.210-1-MANJARO

  -> Running build hook: [base]

  -> Running build hook: [udev]

  -> Running build hook: [autodetect]

  -> Running build hook: [keymap]

  -> Running build hook: [modconf]

  -> Running build hook: [block]

  -> Running build hook: [encrypt]

==> ERROR: module not found: `dm_integrity'

  -> Running build hook: [lvm2]

  -> Running build hook: [filesystems]

  -> Running build hook: [keyboard]

  -> Running build hook: [fsck]

==> ERROR: module not found: `dm_integrity'

==> Generating module dependencies

==> Creating gzip-compressed initcpio image: /boot/initramfs-4.4-x86_64.img

==> WARNING: errors were encountered during the build. The image may not be complete.

Full output: https://pastebin.com/m8yGi0rv

I can't find much troubleshooting about dm_integrity, I've only tried to add dm_integrity in mkinitcpio.conf "modules"... Please keep in mind that I'm very new to Linux so I might be forgetting something. I've backed up my previous installation with rsync to an external drive so my files and configs are fine (I presume). Also, I've tried it without LVM and was getting the same error. Any insights?

I also have this error when I run mkinitcpio -P

~ ❯ sudo mkinitcpio -P 
==> Building image from preset: /etc/mkinitcpio.d/linux316.preset: 'default'
  -> -k /boot/vmlinuz-3.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-3.16-x86_64.img
==> Starting build: 3.16.81-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> ERROR: module not found: `dm_integrity'
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-3.16-x86_64.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux316.preset: 'fallback'
  -> -k /boot/vmlinuz-3.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-3.16-x86_64-fallback.img -S autodetect
==> Starting build: 3.16.81-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> ERROR: module not found: `dm_integrity'
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-3.16-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'default'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.17-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback'
  -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect
==> Starting build: 5.4.17-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> Image generation successful

@linux-aarhus Do you have any ideas here?

EDIT: Based on this it seems this is a Manjaro-specific problem, as no results for any other distros appear. But it could be that dm_integrity is a unique spelling in Manjaro. There's also cryptsetup with references to dm-integrity. :thinking:

EDIT: Ooooh, Wait, I see this is failing only for Kernel 3.16. Why do I have Kernel 3.16 anyways? @linux-aarhus Is that from when I installed virtualbox with pacman -Sy --noconfirm virtualbox, and because it installed linux316-virtualbox-host-modules it required for the 3.16 kernal to be installed? I had that --noconfirm option because I added that to a script that sets up my whole system.

Does the default Calamares installer only install one kernel? I have started to think I should delete the 3.16 kernel, but I thought it was simply there as part of the Manjaro install, but now that I think about it think it isn't.

Bad idea - especially when you make errors in the script

Yes - the kernel included on the ISO

Good idea

this could be your previous virtualbox host modules still haunting you.

sudo mhwd-kernel -r linux316

@linux-aarhus Thanks, I cleaned it up.

Do you know how can I script the pacman installs without blindly accepting only the first package of package selections?

You can't - at least to my knowledge.

You can use the --noconfirm option but that will select a preset or the first in a list op packages providing a given functionality. In some cases the preset is a no causing the install/update to exit.

Interesting about the no preset exiting. Wish we had more control somehow, perhaps a way to specify a selection for some package by name.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by