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

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

New install Jesse 8.6.0...grub2 problem

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

Contents

  New install Jesse 8.6.0...grub2 problem Mark Neidorff <mark@neidorff.com> - 2016-10-06 19:30 +0200
    Re: New install Jesse 8.6.0...grub2 problem Felix Miata <mrmazda@earthlink.net> - 2016-10-06 20:20 +0200
      Re: New install Jesse 8.6.0...grub2 problem Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-10-06 20:40 +0200
        Re: New install Jesse 8.6.0...grub2 problem Felix Miata <mrmazda@earthlink.net> - 2016-10-06 21:00 +0200
    Re: New install Jesse 8.6.0...grub2 problem Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-10-06 20:20 +0200
      Re: New install Jesse 8.6.0...grub2 problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-30 13:20 +0100
        Re: New install Jesse 8.6.0...grub2 problem Pascal Hambourg <pascal@plouf.fr.eu.org> - 2016-10-30 14:40 +0100
          Re: New install Jesse 8.6.0...grub2 problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-30 15:10 +0100
          Re: New install Jesse 8.6.0...grub2 problem Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-10-30 15:40 +0100
            Re: New install Jesse 8.6.0...grub2 problem Mark Fletcher <mark27q1@gmail.com> - 2016-10-30 16:50 +0100
              Re: New install Jesse 8.6.0...grub2 problem Lisi Reisz <lisi.reisz@gmail.com> - 2016-10-30 17:00 +0100

#173241 — New install Jesse 8.6.0...grub2 problem

Hello,

I'm building a server PC to perform backups of the PCs on my local network.  
The server has 2 HDDs--750 Gb and 2 Tb.  The intention is to use the 750 Gb 
drive for the OS and the 2 Tb drive for the backup data. I'll get there in 
stages.  I'll be using backuppc to do the actual backups.

I tried using a different distro--OpenSUSE and it didn't work out.  I installed 
the distro on the 750 Gb drive (and it boots via grub2 from the 750 Gb drive), 
but couldn't get backuppc working.  I didn't want to just wipe out the 
OpenSUSE installation, so I carved a partition out on the 2Tb data drive and 
installed debian there.  

The install went fine, up to installing grub2.  The installer didn't find grub2 
on the 750Gb drive, and it reported no other OS detected.  I then selected the 
2 Tb drive as the boot drive and it errored out when I asked to install grub2 
on the 2 Tb drive.  So, I installed grub2 on the 750 Gb drive.

My problem is that when I boot the machine, it boots into OpenSUSE, and 
doesn't give me a menu to choose from.

I don't know how to proceed from here.

My question(s):
Is there more information that you need to help me?

How do I go about fixing this boot problem so that I can boot into Debian?

Many thanks,

Mark

[toc] | [next] | [standalone]

#173247

Mark Neidorff composed on 2016-10-06 13:22 (UTC-0400):

> I'm building a server PC to perform backups of the PCs on my local network.
> The server has 2 HDDs--750 Gb and 2 Tb.  The intention is to use the 750 Gb
> drive for the OS and the 2 Tb drive for the backup data. I'll get there in
> stages.  I'll be using backuppc to do the actual backups.

> I tried using a different distro--OpenSUSE and it didn't work out.  I installed
> the distro on the 750 Gb drive (and it boots via grub2 from the 750 Gb drive),
> but couldn't get backuppc working.  I didn't want to just wipe out the
> OpenSUSE installation, so I carved a partition out on the 2Tb data drive and
> installed debian there.

> The install went fine, up to installing grub2.  The installer didn't find grub2
> on the 750Gb drive, and it reported no other OS detected.  I then selected the
> 2 Tb drive as the boot drive and it errored out when I asked to install grub2
> on the 2 Tb drive.  So, I installed grub2 on the 750 Gb drive.

> My problem is that when I boot the machine, it boots into OpenSUSE, and
> doesn't give me a menu to choose from.

Because when it was installed there was no other OS, so it defaulted to the 
only one, without any timeout or need for a menu.

> I don't know how to proceed from here.

> My question(s):
> Is there more information that you need to help me?

No Linux distro needs more than a tiny fraction of a 750G HD. Once booted 
into Jessie you can shrink the openSUSE installation to a more reasonable 
size, leaving yourself room for at least a dozen other distros in multiboot 
on your 750G. Multiboot also offers the opportunity to perform repairs 
without any rescue media, and test new and/or beta distros without disturbing 
whatever you run normally. The main thing to remember about installing 
multiboot is to let at the very most only one distro to put Grub on the MBR. 
Otherwise, last installed or updated will always overwrite the previous, 
potentially causing no booting at all, similar to what you have now.

cf. http://fm.no-ip.com/PC/install-doz-after.html

> How do I go about fixing this boot problem so that I can boot into Debian?

If openSUSE is booting into the GUI, login and use YaST2 to configure the 
bootloader to find and add Jessie to its menu and make it the default boot 
selection. You can change the timeout value to anything you wish.

If all you get is a login prompt, login as root and run os-prober.

see also https://en.opensuse.org/GRUB
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

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

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

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

#173249

Le 06/10/2016 à 20:12, Felix Miata a écrit :
>
> No Linux distro needs more than a tiny fraction of a 750G HD.

Wise people would never use all 750 GB for a single OS if it does not 
need to contain as many data.

> Once
> booted into Jessie you can shrink the openSUSE installation to a more
> reasonable size, leaving yourself room for at least a dozen other
> distros in multiboot on your 750G.

Actually if the OP followed the openSUSE installer defaults, the root 
filesystem is btrfs and can be shrinked while mounted.


> If all you get is a login prompt, login as root and run os-prober.

os-prober just detects other OS'es, it does not change anything. You 
need to run update-grub (or update-grub2 as openSUSE may name it) to add 
boot menu entries for the discovered OS'es.

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

#173251

Pascal Hambourg composed on 2016-10-06 20:30 (UTC+0200):

> ...if the OP followed the openSUSE installer defaults, the root
> filesystem is btrfs and can be shrinked while mounted.

That depends on which openSUSE he installed, data he didn't provide. BTRFS 
became default between 13.2 and 42.1 releases.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

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

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

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

#173248

Le 06/10/2016 à 19:22, Mark Neidorff a écrit :
>
> Is there more information that you need to help me?

The result of bootinfoscript would be a good starting point.

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

#174025

On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> Le 06/10/2016 à 19:22, Mark Neidorff a écrit :
> > Is there more information that you need to help me?
>
> The result of bootinfoscript would be a good starting point.

I have Jessie fully updated and aptitude can't find bootinfoscript.

Lisi

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

#174031

Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
>>
>> The result of bootinfoscript would be a good starting point.
>
> I have Jessie fully updated and aptitude can't find bootinfoscript.

How did you search ? It is a command, not a package name. The package 
name is boot-info-script (don't ask me why hyphens were inserted).

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

#174033

On Sunday 30 October 2016 13:32:27 Pascal Hambourg wrote:
> Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
> > On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> >> The result of bootinfoscript would be a good starting point.
> >
> > I have Jessie fully updated and aptitude can't find bootinfoscript.
>
> How did you search ? It is a command, not a package name. The package
> name is boot-info-script (don't ask me why hyphens were inserted).

Ah!!  I tried to run it as command, first as my $USER and then as root.  I 
then searched for a package.  I then commented as above.

Now installed and functional.  Will have a good look later.  Thanks.

Lisi

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

#174036

On 10/30/16, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote:
> Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
>> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
>>>
>>> The result of bootinfoscript would be a good starting point.
>>
>> I have Jessie fully updated and aptitude can't find bootinfoscript.
>
> How did you search ? It is a command, not a package name. The package
> name is boot-info-script (don't ask me why hyphens were inserted).


I'm going to step out onto a limb and presume she did what I just did,
input "bootinfoscrript" into her preferred Debian package manager and
let 'er rip. In fact, Lisi referenced "aptitude", her preferred
package manager.

For mine, I use "apt-cache search". It returns feedback on anything
you input, not just package names. I a-sume aptitude and others
perform similarly.

When queried via "apt-cache search", "bootinfoscript" received back
zero possibilities here, too. However, querying "boot-info-script" did
return something. One returned possibility:

"boot-info-script - inspect boot environment"

Cool. Will be checking it out.

The hyphens in the middle of the name were likely injected as a
cognitive friendly addition to the name in the same way many other
packages do. I can understand those are a pain when keying them in a
lot. I detest underscores even more.

As a reminder tip for newcomers: When beginning to type in a terminal
command, especially the ones with characters that "annoy" you, one can
start typing the name and then hit the tab key a time or two to be
offered a chance to have the command autocompleted. If there's a list
of commands that start similarly,  you just have to keep trimming
things down by adding more characters (letters, numbers) until the
desired command is the only one left to be autocompleted.

With underscores, it recently crossed my reading path that once in a
great while hyphens and underscores are interchangeable. Haven't had a
situation come up to be able to test that one so it remains a
theoretical #toDo.

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

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

#174040

On Sun, Oct 30, 2016 at 10:35:59AM -0400, Cindy-Sue Causey wrote:
> On 10/30/16, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote:
> > Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
> >> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> >>>
> >>> The result of bootinfoscript would be a good starting point.
> >>
> >> I have Jessie fully updated and aptitude can't find bootinfoscript.
> >
> > How did you search ? It is a command, not a package name. The package
> > name is boot-info-script (don't ask me why hyphens were inserted).
> 
> 
> I'm going to step out onto a limb and presume she did what I just did,
> input "bootinfoscrript" into her preferred Debian package manager and
> let 'er rip. In fact, Lisi referenced "aptitude", her preferred
> package manager.
> 
> For mine, I use "apt-cache search". It returns feedback on anything
> you input, not just package names. I a-sume aptitude and others
> perform similarly.
> 
> When queried via "apt-cache search", "bootinfoscript" received back
> zero possibilities here, too. However, querying "boot-info-script" did
> return something. One returned possibility:
> 
> "boot-info-script - inspect boot environment"
> 
> Cool. Will be checking it out.
> 

A lot of people seem to forget or not know about apt-file. It allows 
searches in both directions -- apt-file show <package-name> will tell 
you what files are installed by the package and where they go. apt-file 
search <file> shows which package the file came from. The package does 
_not_ need to be installed for apt-file to do its work, but you do need 
to have run apt-file update before expecting up to date and correct 
answers.

Very similar, I think, to apt-cache search when doing apt-file show but 
with the additional ability to go the other way. For example I just did 
apt-file search bootinfoscript to find out that the file is contained in 
boot-info-script.

Mark

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

#174041

On Sunday 30 October 2016 15:47:59 Mark Fletcher wrote:
> On Sun, Oct 30, 2016 at 10:35:59AM -0400, Cindy-Sue Causey wrote:
> > On 10/30/16, Pascal Hambourg <pascal@plouf.fr.eu.org> wrote:
> > > Le 30/10/2016 à 13:13, Lisi Reisz a écrit :
> > >> On Thursday 06 October 2016 19:12:43 Pascal Hambourg wrote:
> > >>> The result of bootinfoscript would be a good starting point.
> > >>
> > >> I have Jessie fully updated and aptitude can't find bootinfoscript.
> > >
> > > How did you search ? It is a command, not a package name. The package
> > > name is boot-info-script (don't ask me why hyphens were inserted).
> >
> > I'm going to step out onto a limb and presume she did what I just did,
> > input "bootinfoscrript" into her preferred Debian package manager and
> > let 'er rip. In fact, Lisi referenced "aptitude", her preferred
> > package manager.
> >
> > For mine, I use "apt-cache search". It returns feedback on anything
> > you input, not just package names. I a-sume aptitude and others
> > perform similarly.
> >
> > When queried via "apt-cache search", "bootinfoscript" received back
> > zero possibilities here, too. However, querying "boot-info-script" did
> > return something. One returned possibility:
> >
> > "boot-info-script - inspect boot environment"
> >
> > Cool. Will be checking it out.
>
> A lot of people seem to forget or not know about apt-file. It allows
> searches in both directions -- apt-file show <package-name> will tell
> you what files are installed by the package and where they go. apt-file
> search <file> shows which package the file came from. The package does
> _not_ need to be installed for apt-file to do its work, but you do need
> to have run apt-file update before expecting up to date and correct
> answers.
>
> Very similar, I think, to apt-cache search when doing apt-file show but
> with the additional ability to go the other way. For example I just did
> apt-file search bootinfoscript to find out that the file is contained in
> boot-info-script.

lisi@Eros:~$ apt-file search bootinfoscript
boot-info-script: /usr/sbin/bootinfoscript
boot-info-script: /usr/share/man/man8/bootinfoscript.8.gz
lisi@Eros:~$ 

\o/ \o/

Thanks, Mark. :-)

Lisi

>
> Mark

[toc] | [prev] | [standalone]

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

csiph-web