Well, have a look at the code (it’s ruby, i.e. standard text, anyway, you find it in /usr/share/YaST), find out why it crashes, and change it accordingly…
What is it? It’s a bug. Apparently YaST cannot cope with one of your devices.
It seems I solved this issue (bug, whatever).
ata-ST330621A_5EE01XNP-part2 did not exist in /dev/disk/by-id/
then I remembered I’d had an old disk with Debian, which I’d used some years ago and it was ST330621A.
So, I plugged it in, it appeared in the system and cleaned Boot Loader. I had to remove this name (with ST33…) and put an existing one, on which OpenSuse 13.2 runs.
And it’s clean now.
But it amazes me how installation got this disk and settings (disk was physically disconnected) and how my system (13.2) booted with such settings.
If I understand you correctly, you had entries referring to no more existing disk (where, in which file? you never explained). So I personally would say - it is still a bug; installer must not abort in this case. Bug report would help others …
I met this problem too and finally solved it. However, that’s …
I just put the result:
You should just edit this file: /etc/default/grub_installdevice
You open it, then you will found that there are several lines, except the final line only a word “activate”, lines before are all different “disk-id-by-id”(forgive my expression). Delete these lines for id, then save. OK.
How can I find it?
I go to /var/log/ and found that the file pbl.log contains the id, then …