[lubuntu-devel] [not fixed?] running update/upgrade in Lu 20.04 . .. grub connections wiped??

[Fritz Hudnut]

Update: Got over to my U-MATE 20.04 partition yesterday and in the interest
of science I ran an apt update/upgrade . . . and again I got the "Where is
grub?" question in the GUI.  This time I checked all three options, which
turned out to again be "wrong" . . . as following the reboot ONLY U-MATE
was available.  I searched the U-MATE forum and found reference to "grub
hidden" ?? which seemed "similar" and I added myself to the bug report
associated with it.

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/



On Sat, Apr 11, 2020 at 2:51 PM Fritz Hudnut <este.el.paz at gmail.com> wrote:

> Oh the lonely life of the free-style multi-booter . . . I am under the
> impression that the problem has been abated . . . not exactly sure why . .
> . moved the hard drives around in the computer, physically . . . .  Then
> chrooted from Lu 20 into TW Yast and got to their "os-prober" . . . and
> that seems to have gotten me back into the nice OpenSUSE grub window!!!
>
> 1.) Question is why does this seem to only work via chroot-ing, because I
> went through each of the OSs and ran their version of "update-grub" and it
> didn't work, but the chrooting from one HD to another one does seem to snap
> grub back into play?
>
> 2.) What was going on in Lubuntu update/upgrade that brought out the
> console GUI inquiry about "What should we do with grub?" . . . have never
> seen anything like that in many years of "apt-get" or "apt" reaching across
> and cleaning grub connections as happened yesterday . . . ???
>
> I'll report back if there are any salient updates on the problem . . .
> otherwise problem seems to have been resolved . . . .
>
>
> On Fri, Apr 10, 2020 at 2:35 PM Fritz Hudnut <este.el.paz at gmail.com>
> wrote:
>
>> Folks:
>>
>> Did a routine apt update/upgrade today and in the list was "grub" . . . I
>> didn't notice if anything else relating to "grub" was in there . . . but
>> toward the end of installing something like 174 packages in the console . .
>> . a "GUI" window opened saying something, "Grub is confused, where do you
>> want Grub to go?"  And it showed three lines for the 3 drives I have with
>> the "[ *]"  sdb box checked . . . sda only has OSX and that "[ ]" was empty
>> and so was sdc "[ ]" . . . since sdc is where Lubuntu is installed I tried
>> to check it, but didn't remember how to do that, tab was moving the cursor
>> . . . arrow was moving it up or down . . . so I hit return . . . and
>> "Bazinga" the GUI window disappeared, the little man went behind the
>> curtain . . . and the console finished up its process.  But in actuality I
>> didn't change anything that the updater was showing me . . . only sdb was
>> checked and that wasn't changed . . . .
>>
>> On reboot I tried to get into my "main" EFI boot disk where all of the 5
>> linux OSs are listed, and, oops . . . a line of errors . . . went to grub
>> rescue.  I am able to get directly to Lu && U-MATE 20 via their own EFI
>> disks . . . but the other three I have to use SG2 to get into an old???
>> Grub window that does load all of the systems, but it won't show up in
>> normal boot.  I have a somewhat "complicated" set up, but I haven't had any
>> apt update run in such a way that this special window opens asking me to
>> target the drive for grub . . . with the result that grub gets broken . . .
>> from "within"??  Usually it is OSX side that messes up grub.  I then ran
>> "grub-update" in Lu && U-MATE, got over to the OpenSUSE installs via SG2 .
>> . . ran Yast Bootloader, ran their console command to "set up grub" when I
>> do that it finds all of the systems, but trying to boot via grub itself . .
>> . goes to grub rescue window???  I even ran "update-grub" in Manjaro . . .
>> but only SG2 is getting me into those installs.
>>
>> Wha happen mon?  Wha happen?
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-devel/attachments/20200412/b667c381/attachment.html>