I used to have the same “no disk found error” in the past, but I never really paid much attention to it, because system automatically booted few seconds after without any further problems. Also, recently this error message ceased to appear (way before this error)
I checked the /boot/grub/grub.cfg as you suggested, but there are no dashes anywhere near cryptsetup.
Full config is here: manjaro-grubcfg - Pastebin.com.
I have removed “quiet” parameter to find out that system always hangs after Finished File System check on /dev/disk/by-uuid/12AE-EE30
Also it seems to me, that system is able to mount and decrypt encrypted partition, otherwise it wouldn’t get that far.
Btw. Strangely enough I managed to boot into 5.15 once. I did some editing in grub, booted. It failed and I got dropped into emergency shell. I restarted it, then it booted. When I restarted it again, I am back at the old problem.
Thank you, but I don’t think that it is a problem in this case.
I can boot 5.13 kernel into the same GUI fast and without any problem. 5.15 could as well, until the last update.
Also, the system freezes even when it should boot only to runlevel 3.
Nevertheless, I freed some space, but the problem persists.
I obtained it with journalctl -b -1 and journalctl -b 0
Is it the log you need?
When boot freezes, I usually hard kill it. Now just thinking:
All previous boot logs ends with kvě 25 22:46:55 automaton systemd-journald: Time spent on flushing to /var/log/journal/9b6b597c07c04b33ac94870b748879b7 is 16.957ms for 959 entries.
(With different ms time)
So I wonder whether I shouldn’t let it just be. However, once last week I let it frozen for 30+ minutes and there was no change. Also the disk utilization is 2.6 GB according to journalctl --disk-usage
And again, this doesn’t explain why it is not problem in 5.13