Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #211249 > unrolled thread

Repair Grumb

Back to article view | Back to linux.debian.user

Contents

  Repair Grumb "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-07-11 21:10 +0200
    Re: Repair Grumb David <bouncingcats@gmail.com> - 2019-07-12 05:20 +0200
      Re: Repair Grumb (grub) "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2019-07-12 12:10 +0200
        Re: Repair Grumb (grub) Brian <ad44@cityscape.co.uk> - 2019-07-12 13:20 +0200
        Re: Repair Grumb (grub) Jimmy Johnson <field.engineer@gmail.com> - 2019-07-12 15:00 +0200
    Re: Repair Grumb songbird <songbird@anthive.com> - 2019-07-12 14:20 +0200

#211249 — Repair Grumb

I have Stretch installed  on sda1 and Buster installed on sdd1 on my 
64bit Linux platform.

Unfortunately, grub on sdd1 became corrupted and the boot process fails 
after Buster is selected. Fortunately, the Stretch grub still boots the 
system.  Also, I can access the Buster install on sdd1 without any problems

At this point I have downloaded  the Boot Repair dist from Soourceforge 
-boot-repair-disk-64bit.iso and burned it to a DVD. The repair disk 
boots without any problems.  However, I am a bit hesitant to use the 
repair tool.  If I select sdd1 as the location for the repair in the 
advanced tab is there any danger of corrupting the Stretch grub on sda1?

Of course, the safest thing would be to just reinstall Buster on sdd1. I 
hav already backed up the files.

Comments and guidance will be much appreciated.

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.            Life is a fuzzy set
http://www.Molecular-Modeling.net   Multivariate and stochastic
614.312.7528 (c)
Skype:  smolnar1

[toc] | [next] | [standalone]

#211264

On Fri, 12 Jul 2019 at 05:09, Stephen P. Molnar <s.molnar@sbcglobal.net> wrote:
>
> I have Stretch installed  on sda1 and Buster installed on sdd1 on my
> 64bit Linux platform.
>
> Unfortunately, grub on sdd1 became corrupted and the boot process fails
> after Buster is selected.

Everyone reading this wonders:
1) why are you hiding the most important facts in your question?
2) what exact symptoms cause you to conclude that "grub on sdd1 became
    corrupted"?
3) did it ever work properly after installation, ie are we discussing a borked
    installation attempt, or did it work for a while and then "became"
non-working?
4) what is the method that you use to change from attempting to boot sda1,
    or attempting to boot sdd1?
5) at what point in that method does "boot process fails" occur, and
    what are its exact symptoms?
6) is EFI involved?

Your chances of receiving useful assistance are always improved by
providing a detailed description of *the failure*. Without them, readers
can only guess at what the problem might be, and readers with expertise
are unlikely to respond because they have more interesting things to
do than try to guess what someone is talking about.

It is possible that the only "repair tool" you need is grub itself.
You might just need to run 'grub-install' and specify sdd (not sdd1)
as the target device (but I'm not certain, due to the lack of facts).
See here:
https://www.gnu.org/software/grub/manual/grub/grub.html#Invoking-grub_002dinstall
Please be aware that if this command is misused it could make
your machine unbootable. But if used correctly it should be fine.

> Comments and guidance will be much appreciated.
> Thanks in advance.

I did my best. Hope it helps. If you provide the additional details
requested, we might be able to offer better help. Good luck :)

[toc] | [prev] | [next] | [standalone]

#211283 — Re: Repair Grumb (grub)

Plese see responses to questions. .  .  .  .

On 07/11/2019 11:16 PM, David wrote:
> On Fri, 12 Jul 2019 at 05:09, Stephen P. Molnar <s.molnar@sbcglobal.net> wrote:
>> I have Stretch installed  on sda1 and Buster installed on sdd1 on my
>> 64bit Linux platform.
>>
>> Unfortunately, grub on sdd1 became corrupted and the boot process fails
>> after Buster is selected.
> Everyone reading this wonders:
> 1) why are you hiding the most important facts in your question?
> 2) what exact symptoms cause you to conclude that "grub on sdd1 became
>      corrupted"?
After allowing choice of Buster the boot hung with a '>' prompt.
> 3) did it ever work properly after installation, ie are we discussing a borked
>      installation attempt, or did it work for a while and then "became"
> non-working?
Worked fine after installation, until it no longer did.  I don't have 
the faintest idea as to why.
> 4) what is the method that you use to change from attempting to boot sda1,
>      or attempting to boot sdd1?
F8 during post brings up a window listing drives and allowing choice of 
either sda or sdd. Ir I choise sdd the system hangs, if I chaise sda 
Stretch boots.
> 5) at what point in that method does "boot process fails" occur, and
After the choice for the process to continue to Buster.
>      what are its exact symptoms?
> 6) is EFI involved?
No
>
> Your chances of receiving useful assistance are always improved by
> providing a detailed description of *the failure*. Without them, readers
> can only guess at what the problem might be, and readers with expertise
> are unlikely to respond because they have more interesting things to
> do than try to guess what someone is talking about.
>
> It is possible that the only "repair tool" you need is grub itself.
> You might just need to run 'grub-install' and specify sdd (not sdd1)
> as the target device (but I'm not certain, due to the lack of facts).
> See here:
> https://www.gnu.org/software/grub/manual/grub/grub.html#Invoking-grub_002dinstall
> Please be aware that if this command is misused it could make
> your machine unbootable. But if used correctly it should be fine.
>
>> Comments and guidance will be much appreciated.
>> Thanks in advance.
> I did my best. Hope it helps. If you provide the additional details
> requested, we might be able to offer better help. Good luck :)
>
>

-- 
Stephen P. Molnar, Ph.D.            Life is a fuzzy set
http://www.Molecular-Modeling.net   Multivariate and stochastic
614.312.7528 (c)
Skype:  smolnar1

[toc] | [prev] | [next] | [standalone]

#211286 — Re: Repair Grumb (grub)

On Fri 12 Jul 2019 at 06:08:13 -0400, Stephen P. Molnar wrote:

> Plese see responses to questions. .  .  .  .
> 
> On 07/11/2019 11:16 PM, David wrote:
> > On Fri, 12 Jul 2019 at 05:09, Stephen P. Molnar <s.molnar@sbcglobal.net> wrote:
> > > I have Stretch installed  on sda1 and Buster installed on sdd1 on my
> > > 64bit Linux platform.
> > > 
> > > Unfortunately, grub on sdd1 became corrupted and the boot process fails
> > > after Buster is selected.
> > Everyone reading this wonders:
> > 1) why are you hiding the most important facts in your question?
> > 2) what exact symptoms cause you to conclude that "grub on sdd1 became
> >      corrupted"?
> After allowing choice of Buster the boot hung with a '>' prompt.

At the prompt type 'ls' and post the output.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#211296 — Re: Repair Grumb (grub)

On 7/12/19 3:08 AM, Stephen P. Molnar wrote:
> Plese see responses to questions. .  .  .  .
> 
> On 07/11/2019 11:16 PM, David wrote:
>> On Fri, 12 Jul 2019 at 05:09, Stephen P. Molnar 
>> <s.molnar@sbcglobal.net> wrote:
>>> I have Stretch installed  on sda1 and Buster installed on sdd1 on my
>>> 64bit Linux platform.
>>>
>>> Unfortunately, grub on sdd1 became corrupted and the boot process fails
>>> after Buster is selected.
>> Everyone reading this wonders:
>> 1) why are you hiding the most important facts in your question?
>> 2) what exact symptoms cause you to conclude that "grub on sdd1 became
>>      corrupted"?
> After allowing choice of Buster the boot hung with a '>' prompt.

AMD computers and complete buster update with wayland cause problems 
like x not starting or sometimes the user space will freeze with only 
background service running, input device's stop working. I don't know 
the fix.
-- 
Jimmy Johnson

Slackware 14.2 - KDE 4.14.32 - EXT4 at sda5
Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]

#211291

Stephen P. Molnar wrote:
> I have Stretch installed  on sda1 and Buster installed on sdd1 on my 
> 64bit Linux platform.
>
> Unfortunately, grub on sdd1 became corrupted and the boot process fails 
> after Buster is selected. Fortunately, the Stretch grub still boots the 
> system.  Also, I can access the Buster install on sdd1 without any problems
>
> At this point I have downloaded  the Boot Repair dist from Soourceforge 
> -boot-repair-disk-64bit.iso and burned it to a DVD. The repair disk 
> boots without any problems.  However, I am a bit hesitant to use the 
> repair tool.  If I select sdd1 as the location for the repair in the 
> advanced tab is there any danger of corrupting the Stretch grub on sda1?

  i'm not familiar with this tool and don't know what
it does.

  is there some reason you cannot use the original
Buster install media which has a rescue menu/option?

  adding someone else's idea of what the device should
have on it aside from the Debian version sounds like
a complicating factor which is usually not a good idea
when trying to troubleshoot.


> Of course, the safest thing would be to just reinstall Buster on sdd1. I 
> hav already backed up the files.

  i think so.  i would unplug sda first (after turning
off the machine) to make sure you don't change it.

  once you have the system booting from sdd then you
can turn the machine off again, plug sda back in and
boot it and make sure that still works and run your
update-grub from there to pick up buster.


> Comments and guidance will be much appreciated.

  i see in your other note that you say you have no
clue as to what happened.

  to me this really indicates that you are not suited
for the things you are doing.  in other words, if you
want to get better at this sort of thing you need to
take notes or record your terminal sessions because
none of us can tell what you're doing either.


  songbird

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web