Leap 15.5 clean installation from scratch, "dracut-initqueue timeout" and unable to boot

English Install/Boot/Login
#1

PC is laptop Acer Aspire A315-58
It has NVMe disk.

Just today I downloaded openSUSE Leap 15.5 NET ISO, and began installation.
Whole installation process went well, after reboot the MOK update prompt, did it, and when trying to boot:

Reached target Basic System
(a minute or two...)
-e [ /dev/mapper/system-root ]
[...]
Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks:
Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2f23fe245f-68fa-4619-8411-ba1aa5bbddfa.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
    [ -e "/dev/disk/by-uuid/<partition_id>" ]
fi"
Warning: starting timeout scripts
(this part loops itself several times)
Warning: Not all disks have been found.
Warning: You might want to regenerate your initramfs.

Happens with or without secure boot enabled.

There’s no point in entering advanced grub options since being this a from-zero installation there’s no other kernel to try.

Could someone please help?
Thanks.

#2

I have seen something similar, when using a randomly encrypted swap.

On the boot menu line of grub, hit ‘e’. That will allow you to edit the boot line.

Scroll down to the line that starts “linux”.

On that line see if there is a string of the form:

resume=some-swap-device-information

Change that to instead say:

noresume

Then CTRL-X resumes the boot with the edited boot line. If it is a problem with encrypted swap, then this should work around the problem (for this boot only).

#3

No such line there; still same problem…

Any more help?

#4

Are you able to identify the partition that is having problems? Perhaps check the UUID (see output of “blkid”).

#5

Where? If system doesn’t boot at all!

Also, I noticed during installation’s partitioning that it ALWAYS puts partitions home, root, swap in this order necessarily, with no option of moving.
I’m using separate home partition and LVM.

Could this order be related to not being able to find any disks?

#6

You should be able to boot the install media to the rescue system to run commands such as “blkid”. Your output seems to include part of the UUID of the partition that is having problems.

#7

The unable to be found partitions are root and swap, but more complain about root partition.

Please help with this:
Does Yast’s ordering of partitions home, root, swap, during openSUSE installation has to do with this failure?

#8

For sure, it is a problem if the root partition is not found.

I would try booting to the rescue system.

Mount the root partition at “/mnt” (if possible)

And then:

mount --bind /dev /mnt/dev
mount --rbind /sys /mnt/sys
mount --bind /proc /mnt/proc
chroot /mnt
mount -a
mkinitrd  ## remake the initrd
exit
shutdown -r now

and see whether that helps. Or report what goes wrong in the attempt.

#9

Ok, now already tried 3 times in a row to install, ALWAYS the same DAMN error

Seriously, what on hell is happening here?
Is it the freaking home → root → swap order?

Am I the only one in the world passing through this?

And I no longer have the DVD ISO to boot; the USB drive was broken and I have no more one right now… Only the NET installer…

And again, I use LVM

#10

I doubt that. I have never run into problems with that.

The rescue system is available from the NET installer media.

#11

Replaced the NVMe drive for one brand new one, and this done system was able to be installed and booted; would seem it was really an already faulty disk drive…