Comment # 5 on bug 916014 from Darren Freeman

I have an update to this issue.

This server machine has been running 12.3 since my last post. I've been mostly
happy with it, but I think there is a kernel bug in the driver for my SATA
card. It randomly drops two drives from the RAID, then locks up the whole
machine. I have to manually start the rescue disc and forcibly assemble the
RAID, because those two drives are two events behind. So, as far as servers go,
it's totally unreliable.

I decided to try upgrading before I worry about whether this is a kernel bug.

Following, roughly:
https://en.opensuse.org/SDB:System_upgrade

I was able to update from 12.3 to 13.1 without a hitch. System boots first go.

Then I updated from 13.1 to 13.2. (Enter the dreaded Dracut.)

And now it won't boot automatically. It has forgotten how to ask for the LUKS
password, but at least if I boot into failsafe mode, it will eventually drop
into a Dracut shell. (Takes ages to time out though.)

>From here, I am able to do the following magic:

cryptsetup luksOpen /dev/md127 crypt
lvm lvchange -a y /dev/system

At this point I get a message that it has found the root volume, and I type
"exit", and it boots normally.

This is, by the way, what I have to do on an IBM Thinkpad running openSUSE
13.2. Every single time, I have to manually select failsafe, then manually run
the above two commands. I don't know why, but without failsafe, I can still do
all of the above, but there is no message that it's found the root volume, and
if I exit, nothing happens.

I think my main laptop was like this too. After much fiddling around, lots of
regenerating the initrd, I was eventually able to get it to work. But I don't
remember what I did.

I would really appreciate it if somebody could try to reproduce this. It is
100% reproducible for me. It is a regression and it happens every time on 13.2.
Boot from LUKS/LVM is simply broken.

Having manually booted this server, I will now give Tumbleweed a go, and see if
this has been fixed.