On Mon, Jul 22, 2019 at 12:40:40PM -0400, Haines Brown wrote:
>On Mon, Jul 22, 2019 at 06:24:32AM -0400, fsmithred via Dng wrote:
>> On 7/22/19 1:48 AM, Steve Litt wrote:
>...
>
>I tried the chroot method, but with little luck. I'm set up for BIOS
>boot. My /root partion is /sdb1, and my broken out /boot partition is
>/dev/sdb2. So for grub-root-device I use /dev/sdb1; for my
>grub-boot-device I use /dev/sdb.
>
>> > > 2) use these incantations, lifted from a post elsewhere :
>...
>> > > chroot /sysroot
>> > > grub-install /dev/your-grub-boot-device (may be grub2-install on some
>> > > distro)
>

>So I do
>        ...

>

>        # chroot /sysroot

>

>        # grub-install /dev/sdb
>        bash grub-install: command not found

>

>        # ls -la /usr/sbin | grep grub-install
>        -rwxr-xr-x 1 root root 102046 Oct 28 2018 grub-install

>

>        # /usr/sbin/grub-install /dev/sdb
>        # bash: /usr/sbin/grub-install: No such file or directory

>
>At my wits end I remove and reinstall grub2-common. Did not help.
>

If your shell can't find /usr/sbin/grub-install, it might not be in your
PATH.
There are several ways to check this. You can type

    # which grub-install

and if you don't get a result, your shell doesn't know to look there.
You can also try

    # echo $PATH | grep '/usr/sbin:'

to get an immediate, easy-to-read result.

    Antoine

--
A computer once beat me at chess,
but it was no match for me at kickboxing.