Mailinglist Archive: opensuse (795 mails)

< Previous Next >
Re: [opensuse] Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"
  • From: stakanov <stakanov@xxxxxxxxxx>
  • Date: Wed, 08 Nov 2017 16:22:57 +0100
  • Message-id: <14118889.ykkgh9fXYf@roadrunner>
In data mercoledì 8 novembre 2017 13:24:37 CET, hai scritto:
On Wed, Nov 8, 2017 at 12:38 PM, stakanov <stakanov@xxxxxxxxxx> wrote:
In data martedì 7 novembre 2017 19:00:32 CET, Andrei Borzenkov ha scritto:
05.11.2017 21:45, stakanov пишет:
In data martedì 31 ottobre 2017 04:26:43 CET, Andrei Borzenkov ha
30.10.2017 21:45, stakanov пишет:
This is a very puzzling error as I did not install trusted grub and I
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
now in rescue mode).
Did anybody encounter this or does understand what the issue actually

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
point you used grub2-install manually on the "wrong" device (device
does not match YaST configuration). So now after grub2 update new
core.img was written somewhere else and you continue to boot old

It may also happen if you ever changed bootloader location in YaST as
probably does not wipe out bootloader in old location. If this is
what happened, this warrants bug report.

Boot from live image and provide content of
/etc/default/grub_installdevice as well as result of bootinfoscript
(get it from github, sourceforge one is way outdated).

Ok. I have now the content of grubinstalldevice and for comparison the
version of it (that was bootable).
I tried to run the script but I do get an error message that is:
line 7: syntaxerror near to the unattendet token "newline"
line 7: '<!DOCTYPE html >

You need to save raw file, not HTML page. Or you can simply download
release tarball to avoid any confusion.

Now the content of the files:
current is


As opposed to the "old" version


The change came only into being with the update from 42.2 to 42.3

Well, .old file confirms my hypothesis (although we still do not know
actual boot block content). I have no idea what and when changed it, I
would not expect any change without you going into YaST bootloader and
trying to modify configuration.

As a general comment, having multiple location can lead to other sort of
problems and should better be avoided. There is no real reason to have
it (and I suspect it is leftover from the legacy grub which was far less
sensitive to it).

Here you have the result of bootinfoscript (from git-hub)

Well, you have grub2 installed in MBR of /dev/sda and /dev/sdb (as
seen from your live system) and referring to /boot/grub2 on /dev/sdb6,
but all entries in /etc/default/grub_installdevice point only to sdb.
So assuming your BIOS boot device is sda, it perfectly explains what

Now the question is, why did this happen after a simple "zypper dup"?
Should I simple accept the fact as is and rename the .old file to current?
Would this happen again after a regular zypper dup for 15 and especially is
there anything I can do on this (admittedly historical) system, that received
a lot of hardware upgrades (besides others you may expect a lot of new hdd
during the years.
I personally do not know how to "clean" an mbr of former grub entries without
having to format the whole disk....

Sorry for sending this first as pm, my error.
Therefore redirected to the list.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >