Installation issue

Support
,
1

Hello. I am trying to install Manjaro on a desktop which has worked before but now it is not. I have tried many options and ways to get it to install but nothing at every attempt. The installation fails every time.

I am trying to install through a bootable USB which has worked previously. I have tried a different USB and that still produces the same errors. I have tried a different USB port and still the same.

The only change that I did was I swapped the HDD and only then did the errors start appearing. I went back to the original HDD and still nothing.

Will flashing the USB on a laptop matter as that is what I have been doing? I use Etcher from the AUR repo to flash the USB. This has worked before but I was flashing on the desktop not the laptop so I am thinking maybe that is why I get errors as the hardware between a desktop and laptop are different.

I have tried 21.2.5 and 21.2.6 and both builds produce the same end result.

I can provide an error log from the installation.

2

Please do so.

3 
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.28-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
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: file not found: `fsck.fuseblk'
==> WARNING: No fsck helpers found. fsck will not be run on boot.
==> 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.28-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful

^ This is all I get after installation fails.

5

A post was split to a new topic: Calamares Problem

6

Hi. You need to create your own thread instead of jumping into mine.

Just another update on my issue. The checksums on both images are correct as I checked them before flashing the USB drives.

2 Likes
7

:thinking:

8

It is a weird one. The only thing I can think of is that flashing on a laptop is different to flashing on a desktop.

I will try a different Linux distro and see if the same result occurs.

9

Sorry for the double post. I have an update. Manjaro now works on my desktop.

I installed Ubuntu 22.04 LTS and that went through fine without any issues. Before the Ubuntu installation, I selected the option to allow the system to partition the drive instead of myself. I then realised maybe that might work and it did.

The funny thing is that I have been self-partitioning and it worked every time. This occasion, it did not so I let the system do the partitioning and it went through without any errors.

Thank you to megavolt and andreas85 for your time. This thread can now be closed.