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: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Thu, 9 Nov 2017 00:25:46 +0100 (CET)
  • Message-id: <alpine.LSU.2.21.1711082346540.957@Telcontar.valinor>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Wednesday, 2017-11-08 at 22:59 +0100, stakanov wrote:
In data mercoledì 8 novembre 2017 18:16:15 CET, Andrei Borzenkov ha scritto:



Start with telling us what is your boot disk.

O.K.
First of all: this is "my" system, in the sense that I took care for it. It is
my fathers system at my parents home. To be
honest I had not to care too much because it just worked.
Historically it was a windows system so this is what explains a few of the
weirdo things here.

Discs are sda, sdb, sdc, and sdd.

This can be seen in the bootinfo output you posted before. You just need to say which one you want to boot from :-)


Initially the sdb was the windows one and was the first disc but after a
repair it turns out that:
sda is in one only partition of 298 GB and should bear only data with NFTS
partition (windows)

sda1: __________________________________________________________________________

File system: ntfs
Boot sector type: Windows 2000/XP: NTFS
Boot sector info: No errors found in the Boot Parameter Block.

/dev/sda1 * 63 625,134,191 625,134,129 7 NTFS / exFAT /
HPFS

The sdb was historicall the first disc running with win.
sdb 1 160GB NTFS (seems the "own data of users" Windows
sdb 2 110GB NTFS (old system disk of Win)


/dev/sdb1 63 335,854,889 335,854,827 7 NTFS / exFAT /
HPFS
/dev/sdb2 335,854,890 566,982,044 231,127,155 7 NTFS / exFAT /
HPFS
/dev/sdb3 * 566,982,045 976,768,064 409,786,020 5 Extended
/dev/sdb5 655,435,998 976,768,064 321,332,067 83 Linux ext3
/dev/sdb6 566,982,171 650,857,409 83,875,239 83 Linux ext4
==> boot
/dev/sdb7 650,857,473 655,435,934 4,578,462 82 Linux swap /
Solaris

sdb6 is a boot partition of 40 GB? Or perhaps "root". Then sdb5 could be home.



Then the partitioner shows:
sdb6 with 40 GB ext4 (leap root)
sdb7 with 2 GB ext4 (leap swap)
sdb5 with 153 GB (? - I do not really recall if this got /var or /home or if
it was abandoned. I think it is part of home as LVM, it is ext4)

Hum. If you do not know what it is, check, format and reuse.

sdc is windows data disc, all dedicated to backup Acronis (so it should not
enter in the problem).
sdd is 1.8 TB of data with user /home

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 * 63 32,129 32,067 7 NTFS / exFAT /
HPFS
/dev/sdc2 32,130 488,397,167 488,365,038 5 Extended
/dev/sdc5 32,193 488,392,064 488,359,872 bc Acronis BackUp

/dev/sdc2 ends after the last sector of /dev/sdc


sdc2 and sdc5 are extrange. :-?




Festplatte /dev/sde: 28,9 GiB, 31004295168 Bytes, 60555264 Sektoren

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sde1 * 0 5,130,239 5,130,240 0 Empty
/dev/sde2 304 8,495 8,192 ef EFI (FAT-12/16/32)

/dev/sde1 overlaps with /dev/sde2 <=================

GUID Partition Table detected, but does not seem to be used. <==============

Partition Attrs Start Sector End Sector # of Sectors System
/dev/sde1 0 5,129,515 5,129,516 Data partition
(Windows/Linux)
/dev/sde2 304 8,495 8,192 Data partition
(Windows/Linux)


There are problems with sde.



/dev/sdd1 2,048 3,907,028,991 3,907,026,944 83 Linux HOME




sdb6/etc/fstab:

/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ1KS407054-part7 swap
swap defaults 0 0
/dev/disk/by-id/ata-SAMSUNG_HD502HI_S1VZJ1KS407054-part6 /
ext4 data=journal,acl,user_xattr 1 1
UUID=6c891ed2-3d73-4abd-a112-c3e33a055f22 /home ext4
defaults 1 2

Translated:

/dev/sdb7 swap swap defaults 0 0
/dev/sdb6 / ext4 data=journal,acl,user_xattr 1 1
/dev/sdd1 /home ext4 defaults 1 2


The system should start from sdb, as I have not a /boot, the MBR therefore.
Why it did have another location
or MBR is not known to me, with 42.2 it booted normally, with 42.3 it stopped
to work. And I did not change any setting in yast since at least 12.2.
I hope that was somewhat understandable.

Andrei explained why.

Probably "/etc/default/grub" is wrong.

My father is 91 years old and my
parents rely quite a lot on having a running Linux. I would just like to
recover the data and have a running system. If grub can be reconfigured to
start the otherwise well situated system, I will be happy to do this.
Otherwise I would have to know what exactly tell the installer (once read in
the existing partitions) in order to not run into this problem again.


Well, can you boot the system? I guess not.

Boot an openSUSE live system. Mount sdb6 on /mnt, for instance.


Do:
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /dev /mnt/dev

cd /mnt
chroot /mnt
yast (text mode)


navigate to the section on boot, and change the configuration to be correct: install generic MBR on sdb, install grub in "/dev/sdb3", mark it bootable (it already is), install grub files in /dev/sdb6

More or less, I know how to do it but not from memory.

Notice that grub has to be installed "partially" in the extended partition, and the files in a logical partition.



Alternatively, backup and install fresh in sdb telling Yast to take the entire disk, without a NEW home partition. Use the existing one in sdd1. I would probably do this, to reuse that unused space.



You also have to tell the bios to boot from the second disk.



- -- Cheers,
Carlos E. R.
(from openSUSE 42.2 x86_64 "Malachite" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAloDkoEACgkQtTMYHG2NR9UalQCfTbf52s9Ch5SqjF0tY+ConIUZ
xBIAoIxVjriMat2YQxf/p4VPG29cEURU
=Jdxr
-----END PGP SIGNATURE-----
< Previous Next >
Follow Ups