Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

classic Classic list List threaded Threaded
32 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Stakanov Schufter
In data giovedì 9 novembre 2017 12:51:12 CET, Carlos E. R. ha scritto:

> Content-ID: <[hidden email]>
>
> On Thursday, 2017-11-09 at 09:52 +0100, stakanov wrote:
> >> In data giovedì 9 novembre 2017 00:25:46 CET, Carlos E. R. ha scritto:
> >>> Well, can you boot the system? I guess not.
> >>
> >> No, it gives the error as of above.
> >>
> >> sdc2 and sdc5 are extrange. :-?
> >
> > This is easily explained. The Acronis Software for windows is a backup
> > programm that creates a proprietary formatting on the disk and compresses
> > data with it. Therefore only Acronis Software can access this system
> > backup. Linux certainly can not nor can grub.
>
> Right, I understand that it manages the *contents* of the partition, raw.
> But what it can not manage is the partition definition itself, not if the
> resulting partition is inconsistent with others.
>
> >> 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.
> >
> > Well, that I am subscribing without hesitations. I should not even have an
> > sde disc!
>
> It is very small, 28,9 GiB
>
> >>> Boot an openSUSE live system. Mount sdb6 on /mnt, for instance.
> >
> > Well, this is a main problem, how to find a openSUSE live system as AFAIK,
> > leap does not have one. If I take TW I am not sure a) that it exists b)
> > that it will be compatible , TW is quite far from current leap 42.3. Would
> > live DVD of Mageia do.... I do not know that either.
>
> No, it must be an openSUSE disk because you intend to fire up YaST.
>
> You can try with the rescue ISO for 13.2, or the one for TW (yes, there is
> one, I don't know if it is finished).
>
> Or you can do what I did: Install Leap in a very small spare partition in
> another disk. 8 or 9 GB would suffice.
>
>
> For this job, I think you do not need any: just boot Leap install media:
> there is an option (or there should be, I have not looked or I don't
> remember) to boot a very small text rescue image. Very few tools, but
> enough for the procedure I described. If you don't have any, download the
> NET install disk for the same Leap as you are recovering.
>
> >>> Do:
> >>>      mount --bind /proc /mnt/proc
> >>>      mount --bind /sys /mnt/sys
> >>>      mount --bind /dev /mnt/dev
> >>>      
> >>>      cd /mnt
> >>>      chroot /mnt
> >>>      yast   (text mode)
> >
> > O.K. up to here I am with you. Just will need the live DVD.
>
> Right.
>
> yast:
>
> (notice that it runs yast from the installed system, not from the rescue
> system)
>
> >>> 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
> >
> > Is this the yast menu point: "personalized boot partition"?
> >
> >>> 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.
> >
> > This part I do not understand. How would I do this?
>
> Ok, I will look later at how my laptop is done, because I don't remember;
> but I have to do it later, I can't access it right now.
>
> > I think once I manage to do all this, it would be nice to migrate only
> > linux to a new ssd and then to format and reuse the former system disc.
> > But I do not know if this is possible to do this without a fresh install.
> > (it is just that he has a lot of specific graphics programms installed
> > (believe it or not, he is using blender and other programs. So I would
> > like to avoid to have to search for all programms installed again.
>
> Perfectly possible, I did it myself less than a month ago.
>
> > P.S. thank you for your help. Also thank you to Andrei.
>
> Welcome :-)
>
> --
> Cheers,
>         Carlos E. R.
>         (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)

This is somewhat complicated.
I get (with either option rescure leap and mageia) the following answer:
mount.bin: mount point /mnt/proc does not exist.

Do I  have to create manually a folder with the corresponding names in /mnt in
order to do this?




--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Andrei Borzenkov
In reply to this post by Stakanov Schufter
09.11.2017 00:59, stakanov пишет:

> In data mercoledì 8 novembre 2017 18:16:15 CET, Andrei Borzenkov ha scritto:
>> 08.11.2017 18:22, stakanov пишет:
>> [... trimming so I am not jumped on by self-appointed police of this
>> list ...]
> [Well said. I hope that is not too much trimmed. Maybe there is an important
> netiquette on this too....?]
>>
>> 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.
> 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)
> 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)
> 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)
> 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
>
> The system should start from sdb, as I have not a /boot, the MBR therefore.

I cannot parse this sentence.

> 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.

All this information is in BIS output. What BIS cannot know is what disk
your BIOS boots from. You still did not answer that.


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Stakanov Schufter
In data giovedì 9 novembre 2017 18:53:15 CET, Andrei Borzenkov ha scritto:
> 09.11.2017 00:59, stakanov пишет:
> > In data mercoledì 8 novembre 2017 18:16:15 CET, Andrei Borzenkov ha
scritto:

> >> 08.11.2017 18:22, stakanov пишет:
> >> [... trimming so I am not jumped on by self-appointed police of this
> >> list ...]
> >
> > [Well said. I hope that is not too much trimmed. Maybe there is an
> > important netiquette on this too....?]
> >
> >> 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.
> > 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)
> > 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)
> > 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)
> > 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
> >
> > The system should start from sdb, as I have not a /boot, the MBR
> > therefore.
>
> I cannot parse this sentence.
>
> > 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.
>
> All this information is in BIS output. What BIS cannot know is what disk
> your BIOS boots from. You still did not answer that.

LOL, this is because I am tarded :-)
I looked into the BIOS. So:
sda is the fist boot device in the BIOS.
sdb is only the second in boot order.

If I change the boot order to sdb as first device, can that work already? Could
it be so easy?
So to answer your question: sda is the boot device
HDD boot priority in order
1. SCSI-1 : HD321KJ
2. SCSI-2 : HD502HI
3. SCSI-0 : WDC WD20EYRX-00D
4. SCSI-3 : WD2500JS-00MHB0

sorry that it took so long for me to understand.




--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Andrei Borzenkov
09.11.2017 21:32, stakanov пишет:

> In data giovedì 9 novembre 2017 18:53:15 CET, Andrei Borzenkov ha scritto:
>> 09.11.2017 00:59, stakanov пишет:
>>> In data mercoledì 8 novembre 2017 18:16:15 CET, Andrei Borzenkov ha
> scritto:
>>>> 08.11.2017 18:22, stakanov пишет:
>>>> [... trimming so I am not jumped on by self-appointed police of this
>>>> list ...]
>>>
>>> [Well said. I hope that is not too much trimmed. Maybe there is an
>>> important netiquette on this too....?]
>>>
>>>> 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.
>>> 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)
>>> 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)
>>> 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)
>>> 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
>>>
>>> The system should start from sdb, as I have not a /boot, the MBR
>>> therefore.
>>
>> I cannot parse this sentence.
>>
>>> 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.
>>
>> All this information is in BIS output. What BIS cannot know is what disk
>> your BIOS boots from. You still did not answer that.
>
> LOL, this is because I am tarded :-)
> I looked into the BIOS. So:
> sda is the fist boot device in the BIOS.
> sdb is only the second in boot order.
>
> If I change the boot order to sdb as first device, can that work already? Could
> it be so easy?

Yes, I expect it to boot in this case.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found" [SOLVED]

Stakanov Schufter
In data giovedì 9 novembre 2017 19:40:59 CET, Andrei Borzenkov ha scritto:
> Yes, I expect it to boot in this case.

O.K. it is official I am tarded. The BIOS setting solved the issue. I would have
never thought at the BIOS. Still I am not sure that I really did understand
why grub legacy with the same settings worked...and grub2 didn't. Anyway, now
it works and I can repair all the "damage" from failed migration (post did not
migrate, I had archives fortunately). Same for passwords, server settings, all
email had to be set up. The rest seems to work but I get three error messages
at boot:
postfix transport server failed to start
kernel modules failed to load
and a third one that I do not recall at the moment.
Will try to open a thread on this to get rid of the error and speed up boot,
maybe you will have an input on the kernel module thing. See you then in case.

Anyway,Большое спасибо!





--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Carlos E. R.-2
In reply to this post by Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



El 2017-11-09 a las 12:51 +0100, Carlos E. R. escribió:
> On Thursday, 2017-11-09 at 09:52 +0100, stakanov wrote:
>>>  In data giovedì 9 novembre 2017 00:25:46 CET, Carlos E. R. ha scritto:

>>>>  Do:
>>>>       mount --bind /proc /mnt/proc
>>>>       mount --bind /sys /mnt/sys
>>>>       mount --bind /dev /mnt/dev
>>>>
>>>>       cd /mnt
>>>>       chroot /mnt
>>>>       yast   (text mode)
>>
>>
>>  O.K. up to here I am with you. Just will need the live DVD.
>
> Right.
>
> yast:
>
> (notice that it runs yast from the installed system, not from the rescue
> system)
>
>>>>  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
...

>>  This part I do not understand. How would I do this?
>
>
> Ok, I will look later at how my laptop is done, because I don't remember;
> but I have to do it later, I can't access it right now.

Here goes:

(watch out for possible line wrap at your end)


  YaST2 - menu @ minas-tirith.valinor

   ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
   │                                               YaST Control Center                                                │
   └──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

   ┌────────────────────────────────┐ ┌───────────────────────────────────────────────────────────────────────────────┐
   │Software                        │ │/etc/sysconfig Editor                                                          │
   │System                          │ │Boot Loader  <===================                                              │
   │Hardware                        │ │Date and Time                                                                  │
   │Network Services                │ │Fonts                                                                          │
   │Security and Users              │ │Kernel Settings                                                                │
   │Virtualization                  │ │Language                                                                       │
   │Support                         │ │Network Settings                                                               │
   │Miscellaneous                   │ │Partitioner                                                                    │
   │                                │ │Services Manager                                                               │
   │                                │ │                                                                               │
...
   │                                │ │                                                                               │
   └────────────────────────────────┘ └───────────────────────────────────────────────────────────────────────────────┘

   [Help]                                                                                                    [Run][Quit]


  F1 Help  F9 Quit




YaST2 - bootloader @ minas-tirith.valinor

   Boot Loader Settings
   ┌Boot Code Options──Kernel Parameters──Bootloader Options───────────────────────────────────────────────────────────┐
   │ ================                                 Boot Loader                                                      │
   │                                                  GRUB2▒▒▒▒▒▒▒▒▒↓                                                  │
   │                                                                                                                   │
   │                                                                                                                   │
   │ ┌Boot Loader Location───────────────────────────────────────────────────────────────────────────────────────────┐ │
   │ │ [ ] Boot from Boot Partition                                                                                  │ │
   │ │ [ ] Boot from Master Boot Record                                                                              │ │
   │ │ [x] Boot from Extended Partition                                                                              │ │
   │ │ [ ] Custom Boot Partition                                                                                     │ │
   │ │ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ │
   │ └───────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ │
   │                                                                                                                   │
   │                                                                                                                   │
   │                                                                                                                   │
   │ [ ] Set active Flag in Partition Table for Boot Partition                                                         │
   │                                                                                                                   │
   │                                                                                                                   │
   │ [x] Write generic Boot Code to MBR                                                                                │
   │                                                                                                                   │
   │                                                                                                                   │
   │ [ ] Enable Trusted Boot Support                                                                                   │
   │                                                                                                                   │
   │                                                                                                                   │
   │ [Edit Disk Boot Order]                                                                                            │
   │                                                                                                                   │





  YaST2 - bootloader @ minas-tirith.valinor

   Boot Loader Settings
   ┌Boot Code Options──Kernel Parameters──Bootloader Options───────────────────────────────────────────────────────────┐
   │                                      ===================                                                          │
   │                                                                                                                   │
   │ Timeout in Seconds                                     [x] Probe Foreign OS                                       │
   │              ↓  8↑  <========= (1)                                                                                │
   │                                                        [ ] Hide Menu on Boot                                      │
   │                                                                                                                   │
   │                                                                                                                   │
   │                                      Default Boot Section                                                         │
   │                                      openSUSE Leap 42.2▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒↓                                      │
   │                                                                                                                   │
   │                                                                                                                   │
   │ ┌[ ] Protect Boot Loader with Password──────────────────────────────────────────────────────────────────────────┐ │
   │ │  [x] Protect Entry Modification Only                                                                          │ │
   │ │  Password for GRUB2 User 'root'                      Retype Password                                          │ │
   │ │  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒                      │ │
   │ └───────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ │
   │                                                                                                                   │
   │                                                                                                                   │
   │                                                                                                                   │


(1)  Changing the Timeout in seconds just 1 second forces the whole thing
to be saved to disk on exit. It is a trick to force reinstall of grub with
YaST.




- --
Cheers
        Carlos E. R.

        (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))

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

iF4EAREIAAYFAloE1vQACgkQja8UbcUWM1xOswD7BWeD4G4OBoL6a7Y03/c3CafW
dd7ETdOTG4G+XwDxOW8BAJztXtZzg81sMUyjGV/nvz8XGphC8HRG6mFQUHkG0PHT
=4oJk
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Carlos E. R.-2
In reply to this post by Felix Miata-3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



El 2017-11-09 a las 07:49 -0500, Felix Miata escribió:

> Carlos E. R. composed on 2017-11-09 12:51 (UTC+0100):
>
>>> Well, this is a main problem, how to find a openSUSE live system as AFAIK,
>>> leap does not have one. If I take TW I am not sure a) that it exists b)
>>> that it will be compatible , TW is quite far from current leap 42.3. Would
>>> live DVD of Mageia do.... I do not know that either.
>
>> No, it must be an openSUSE disk because you intend to fire up YaST.
>
> ???...
>
>> You can try with the rescue ISO for 13.2, or the one for TW (yes, there is
>> one, I don't know if it is finished).
>
>> Or you can do what I did: Install Leap in a very small spare partition in
>> another disk. 8 or 9 GB would suffice.
>
>> For this job, I think you do not need any: just boot Leap install media:
>> there is an option (or there should be, I have not looked or I don't
>> remember) to boot a very small text rescue image. Very few tools, but
>> enough for the procedure I described. If you don't have any, download the
>> NET install disk for the same Leap as you are recovering.
>
>>> O.K. up to here I am with you. Just will need the live DVD.
>
>> Right.
>
>> yast:
>
>> (notice that it runs yast from the installed system, not from the rescue
>> system)
>
> So then why do you say the live media must be openSUSE rather than Mageia? The
> way I understand chroot, only the kernel plus the content of the bind mounts
> comes from the booted media, while the rest, including YaST2, comes from the
> chrooted-to filesystem.
Same kernel, same libs, same versions, same directories.

- --
Cheers
        Carlos E. R.

        (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))

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

iF4EAREIAAYFAloE10wACgkQja8UbcUWM1z3NQEAjmpZK8IaSaXUusPv19ONBIaQ
0zAuRiITNB+sgbiP9TwBAJ6WKQL9C7lvPt4GvgY08C9ar/PdyV3T+XjKazAPKXko
=UJxw
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Stakanov Schufter
In reply to this post by Carlos E. R.-2
In data giovedì 9 novembre 2017 23:30:05 CET, Carlos E. R. ha scritto:

> El 2017-11-09 a las 12:51 +0100, Carlos E. R. escribió:
> > On Thursday, 2017-11-09 at 09:52 +0100, stakanov wrote:
> >>>  In data giovedì 9 novembre 2017 00:25:46 CET, Carlos E. R. ha scritto:
> >>>>  Do:
> >>>>       mount --bind /proc /mnt/proc
> >>>>       mount --bind /sys /mnt/sys
> >>>>       mount --bind /dev /mnt/dev
> >>>>      
> >>>>       cd /mnt
> >>>>       chroot /mnt
> >>>>       yast   (text mode)
> >>  
> >>  O.K. up to here I am with you. Just will need the live DVD.
> >
> > Right.
> >
> > yast:
> >
> > (notice that it runs yast from the installed system, not from the rescue
> > system)
> >
> >>>>  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
>
> ...
>
> >>  This part I do not understand. How would I do this?
> >
> > Ok, I will look later at how my laptop is done, because I don't remember;
> > but I have to do it later, I can't access it right now.
>
> Here goes:
>
>
>
>
>
>
> --
> Cheers
>         Carlos E. R.
>
>         (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))

Thank so much, I will put it into my "library of solutions".
I solved with the BIOS setting. As told below, I will have still to debug
three fail messages during boot. Help will be appreciated.
BTW. The "update experience from 42.2 to 3 was astonishing rough.




--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Carlos E. R.-2
In reply to this post by Stakanov Schufter
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Content-ID: <[hidden email]>


El 2017-11-09 a las 17:47 +0100, stakanov escribió:
> In data giovedì 9 novembre 2017 12:51:12 CET, Carlos E. R. ha scritto:
>> Content-ID: <[hidden email]>
>> On Thursday, 2017-11-09 at 09:52 +0100, stakanov wrote:
>>>> In data giovedì 9 novembre 2017 00:25:46 CET, Carlos E. R. ha scritto:
>>>>> Well, can you boot the system? I guess not.

...

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

...

>> For this job, I think you do not need any: just boot Leap install media:
>> there is an option (or there should be, I have not looked or I don't
>> remember) to boot a very small text rescue image. Very few tools, but
>> enough for the procedure I described. If you don't have any, download the
>> NET install disk for the same Leap as you are recovering.
>>
>>>>> Do:
>>>>>      mount --bind /proc /mnt/proc
>>>>>      mount --bind /sys /mnt/sys
>>>>>      mount --bind /dev /mnt/dev
>>>>>
>>>>>      cd /mnt
>>>>>      chroot /mnt
>>>>>      yast   (text mode)
>>>
>>> O.K. up to here I am with you. Just will need the live DVD.

>
> This is somewhat complicated.
> I get (with either option rescure leap and mageia) the following answer:
> mount.bin: mount point /mnt/proc does not exist.
>
> Do I  have to create manually a folder with the corresponding names in /mnt in
> order to do this?

You get that error because you have not mounted the targed root partition
*in* /mnt.


Do an "ls /mnt" and you should see your root filesystem.


- --
Cheers
        Carlos E. R.

        (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAloE2IQACgkQja8UbcUWM1yftgD/Wt5l0cIIYWIimkFOTH1GY0ch
K4G5seI3xN+iYR4pYMYA/1tb845j1tvU7/ZlxQkVgqHu+GebPoBNrWbsQPWN3afj
=EdBj
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found" [SOLVED]

Carlos E. R.-2
In reply to this post by Stakanov Schufter
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



El 2017-11-09 a las 21:05 +0100, stakanov escribió:
> In data giovedì 9 novembre 2017 19:40:59 CET, Andrei Borzenkov ha scritto:
>> Yes, I expect it to boot in this case.
>
> O.K. it is official I am tarded. The BIOS setting solved the issue. I would have
> never thought at the BIOS. Still I am not sure that I really did understand
> why grub legacy with the same settings worked...and grub2 didn't. Anyway, now
> it works and I can repair all the "damage" from failed migration (post did not
> migrate, I had archives fortunately).

I do a full backup (image) before upgrades. If things go badly, I restore
backup and try again solving the problem appropriately.

> Same for passwords, server settings, all
> email had to be set up. The rest seems to work but I get three error messages
> at boot:
> postfix transport server failed to start
> kernel modules failed to load

Maybe you need mkinidrd.

- --
Cheers
        Carlos E. R.

        (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith))

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

iF4EAREIAAYFAloE3JAACgkQja8UbcUWM1ylMwD/SCyFw8yn4JhqMRDVbg4REx77
6+CZ43UcLuO4dcEV7bUBAILrq27VTCXitTd9PPmrwuSV+rVR7eBe+PECjKbcdLCt
=Sfm1
-----END PGP SIGNATURE-----
Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Felix Miata-3
In reply to this post by Carlos E. R.-2
Carlos E. R. composed on 2017-11-09 23:31 (UTC+0100):
...
>>> (notice that it runs yast from the installed system, not from the rescue
>>> system)

>> So then why do you say the live media must be openSUSE rather than Mageia? The
>> way I understand chroot, only the kernel plus the content of the bind mounts
>> comes from the booted media, while the rest, including YaST2, comes from the
>> chrooted-to filesystem.

> Same kernel, same libs, same versions, same directories.

Hence, as long as there isn't an obstacle on account of some obscure absence or
conflict in the substituted kernel, the libs, software versions and directories
are those needed, thos on the 42.3 repair target chrooted to, where the Grub
repair is needed, not those on the rescue media. Absent a kernel
incompatibility, it should not matter what distro is on the live media, which is
effectively bypassed while in the chroot.

Without actually testing the specific distro media suggested, I would expect a
lot better likelihood of repair success from a live Mageia release using a
matching 4.4 kernel version and Grub version than I would from a 4 years older
live openSUSE 13.1 kernel 3.11 or 3 years older live openSUSE 13.2 kernel 3.16,
with their correspondingly older Grubs, directory structure, software versions,
and libs.

Less than a week ago I did a chroot across distros, from Debian Stretch, but I
don't remember to what (or for what), whether an openSUSE, a Mageia, or a
Fedora. Whichever it was, it got the job done.
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"

Carlos E. R.-2
On 2017-11-10 00:35, Felix Miata wrote:

> Carlos E. R. composed on 2017-11-09 23:31 (UTC+0100):
> ...
>>>> (notice that it runs yast from the installed system, not from the rescue
>>>> system)
>
>>> So then why do you say the live media must be openSUSE rather than Mageia? The
>>> way I understand chroot, only the kernel plus the content of the bind mounts
>>> comes from the booted media, while the rest, including YaST2, comes from the
>>> chrooted-to filesystem.
>
>> Same kernel, same libs, same versions, same directories.
>
> Hence, as long as there isn't an obstacle on account of some obscure absence or
> conflict in the substituted kernel, the libs, software versions and directories
> are those needed, thos on the 42.3 repair target chrooted to, where the Grub
> repair is needed, not those on the rescue media. Absent a kernel
> incompatibility, it should not matter what distro is on the live media, which is
> effectively bypassed while in the chroot.
>
> Without actually testing the specific distro media suggested, I would expect a
> lot better likelihood of repair success from a live Mageia release using a
> matching 4.4 kernel version and Grub version than I would from a 4 years older
> live openSUSE 13.1 kernel 3.11 or 3 years older live openSUSE 13.2 kernel 3.16,
> with their correspondingly older Grubs, directory structure, software versions,
> and libs.
You can use the small live rescue system in the Leap install media.

> Less than a week ago I did a chroot across distros, from Debian Stretch, but I
> don't remember to what (or for what), whether an openSUSE, a Mageia, or a
> Fedora. Whichever it was, it got the job done.

Mmm.

--
Cheers / Saludos,

                Carlos E. R.
                (from 42.2 x86_64 "Malachite" at Telcontar)


signature.asc (188 bytes) Download Attachment
12