On 31/10/17 03:26, Andrei Borzenkov wrote:
This is a very puzzling error as I did not install trusted grub and I do not have tpm on the system. The system is also not UEFI. The update was from 42.2 (working well) to 42.3 (screwed it up and I am now in rescue mode). Did anybody encounter this or does understand what the issue actually is?
TPM support was added to stock grub2. The error suggests that your core.img does not match /boot/grub2. The usual reason is that at some
30.10.2017 21:45, stakanov пишет: point you used grub2-install manually on the "wrong" device (device that does not match YaST configuration). So now after grub2 update new core.img was written somewhere else and you continue to boot old version.
It may also happen if you ever changed bootloader location in YaST as it probably does not wipe out bootloader in old location. If this is indeed what happened, this warrants bug report.
Sounds to me like YaST gets confused if you've got a multiboot situation (or the user gets confused and screws things up ...) I've got the stock MBR that chained into gentoo-grub on my gentoo partition, that I then chained SUSE-grub on my SUSE partition if that's what I wanted. I don't know what's happened with my upgrade from 42.2 to 42.3, but it now boots straight into SUSE-grub. I *think* it's probably just changed the active partition, but YaST certainly seems to play fast and loose with the previous setup ... Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org