If a partition, being mounted by the** /etc/fstab** file fails to mount, you can get this message. It seems that your boot works and perhaps root / mounts, but something else fails. For any partition that is NOT root /, /home or SWAP, you could add the fstab load option nofail as root. Try mc at the terminal prompt for Midnight Commander, a file manager with editor. The nofail option works good for USB drives and any none essential partition you want to ignor if it does not mount.
If the boot works, because the BIOS finds it OK, but the root / partition does not mount because it is a RAID, not understood by the kernel initrd image, you may be unable to startup. If you could move root / to a standard drive partition, it may be able to bring up the RAID once the full kernel is loaded. I don’t know what is wrong for sure, but it sounds like a required partition like root / does not mount.
By standard boot, imagine that you add a hard drive, as small as 40 GB, install boot and root / all on this drive and let it startup your RAID. Its sounds like once the boot finishes, it can locate the real root on the RAID partition, but something there is not working at the very start. Using a second hard drive for booting is like using the ARCH Linux to boot.
Do you mean hardware RAID or fake RAID or Linux MD RAID? Your description is too vague.
The installation seemed fine but after the reboot I got this error message:
file /boot/grub2/x86_64_efi/normal.mod not found.
Entering rescue mode…
This means grub2 cannot find device where filesystem with /boot/grub2 is located. One common case would be adapter that requires special driver but does not support booting from it (i.e. is not accessible via BIOS/EFI).
I’ve downloaded Rescatux (linux rescue cd) and with that I am able to boot opensuse but it doesn’t fix grub anyway. I can access to opensuse only with that cd but I need a permanent solution… any other idea?
Edit: I have succeed in installing grub2-efi and now it works!