Comment # 12 on bug 985346 from Michael Chang

(In reply to James Ye from comment #8)
> There appears to be multiple issues at play here:

> 3. GRUB is unable to boot with cryptodisk (maybe to do with UEFI Secure
> Boot?). This causes "error: Couldn't load sha256 hash." and "error: no such
> cryptodisk foud."

It's fixed in Tumbleweed snapshot 20160826. And yes, it's UEFI Secure Boot
related, as the sha256 module is missing from the signed grub.efi image. The
new cryptsetup has changed it's default to sha256 for luks.