Impossible to install manjaro - KDE Plasma 21.2.4 -- plymouth ERROR at the end

I’ve been stuck trying to install the latest version of manjaro (KDE Plasma edition), 21.2.4, on my Lenovo Thinkpad t530. 16GB RAM. One disk for the system (110GB) and one for home and swap (900GB). Both SSD.

I format the system one with 300MB for /boot/efi, fat32, the rest ext4. I make the other one to be mounted as /home (I have all my data there).

Well, the installation seems to go ok but when everything should be over, I get this message:

Command <i>mkinitcpio</i> finished with exit code 1.
Output:
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.25-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: [consolefont]
==> WARNING: consolefont: no font found in configuration
==> ERROR: Hook 'plymouth' cannot be found
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
  -> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.25-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: [consolefont]
==> WARNING: consolefont: no font found in configuration
==> ERROR: Hook 'plymouth' cannot be found
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.

What is this plymouth that cannot be found? What can I do to finish the installation?

BTW, just by chance I had another USB stick with a (much older) NEON kde distribution and this one I can install with no problem.

It is any custom boot logo with possible animation and (password entry for decryption disk) at startup.

But I wounder why it was installed by default? Have you selected “full disk encryption” before installation?

No, no disk encryption at all.

Okay, you can remove plymouth in HOOKS in the file /etc/mkinitcpio.conf, then sudo mkinitcpio -P linux

Ok, I’ll try it. Thanks.

Not there:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

Try to run this command line, what happens it?

While I was posting this here I was trying other things. I made a chroot and from there a grub-install. I’ve rebooted and… I’ve seen the NEON animation! So I’ve deduced that’s were the plymouth thing was coming from.

So, I’ve decided to make a new installation but, before installing, I’ve formated both partitions, /boot/efi and / by hand,

sudo umount /dev/sdb2
sudo mkfs.ext4 /dev/sdb2                                                                                                                                                            
sudo mkfs.vfat /dev/sdb1

And then I’ve proceeded to the normal installation. Now I’ve got no error and, well, I’ll now do the reboot and see what happens.

It seems if there was a previous animation you can not install manjaro if you do not format, by hand, the partitions.

And yeah, it’s working.

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