I don’t see how I can get to dmesg since I wasn’t able to get into the system at all. The drive is completely luks encrypted except the efi and boot partition.
I am guessing it has something to do with the UUID. Maybe somewhere I should use something else instead of UUID?
Sorry, it was not clear from your original message. Try booting with plymouth.enable=0 on kernel command line. At least you will see actual messages during boot and where it stops.
I could switch between the plymouth background and the output messages fine (with pressing the arrow key). There was no extra output at this stage. But it does remind me about the plymouth bug that causes LUKS prompt to disappear. I will try to disable plymouth and try. Disassembling two laptops is bit tiresome so I hope to gather more info before giving another go.
I did google the error and found the same info. But I noticed that the BIOS on the new Dell laptop is quite recent (read to be released in 2017/03), as the laptop’s production date is also in this March. On the other hand, my lenovo BIOS hasn’t been updated for more than a year.
On the first picture one can see SATA errors, so it looks like problems accessing hard drive. Can you boot from CD, DVD or USB stick? If yes, try booting any live distro - can you access hard drive?
I boot to windows 10 and the opensuse drive can be seen there in the disk manager of windows 10. The partition etc can all be seen without any sign of error (luks encrypted though).