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

Groups > linux.debian.user > #229197

Re: Fixing a Grub Foul-up

Show all headers | View raw

On Mon, 30 Nov 2020 at 14:53, Martin McCormick <martin.m@suddenlink.net> wrote:

>  I typed sudo grub-install /dev/sdd.  It ran for a few
> seconds, announced that grub was installed without any errors and
> exited.

> After looking at /dev/sdd1/grub and seeing no updated
> date stamps, I had a sinking feeling and looked at /dev/sda1
> which is the boot partition on the system I haven't killed yet
> and, sure enough, grub-install had run on that drive.

> $ ls -lt /boot/grub
[...]
> It didn't even touch any part of /dev/sdd1.

The bootloader on /dev/sdd would have been updated.

[...]

> What am I failing to do to make the changes occur on the
> designated drive?

Your lack of success is because the the command you used has designed
behaviour to install the grub bootloader to the boot sector of
/dev/sdd, and also install the grub files you listed into the current
system /boot/grub (which was not on sdd at the time). That is the
reason why you see those files on /dev/sda1, because it was the boot
partition at the time you ran the command.

If you want a grub-install command that writes /boot/grub files
somewhere onto /dev/sdd then you will first have to mount the desired
target boot partiton of /dev/sdd on some mountpoint that you choose,
and then run a command something like this:
  sudo grub-install
--boot-directory=/some/mountpoint/where/is/the/sdd/boot /dev/sdd

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-16 20:00 +0100
  Re: Fixing a Grub Foul-up Dan Ritter <dsr@randomstring.org> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-17 04:00 +0100
    Re: Fixing a Grub Foul-up "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 05:00 +0100
      Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-12-01 15:40 +0100
        Re: Fixing a Grub Foul-up Solved! "Martin McCormick" <martin.m@suddenlink.net> - 2020-12-01 21:10 +0100
  Re: Fixing a Grub Foul-up John Boxall <jboxall47@gmail.com> - 2020-11-16 20:40 +0100
    Re: Fixing a Grub Foul-up Kenneth Parker <sea7kenp@gmail.com> - 2020-11-17 03:00 +0100
  Re: Fixing a Grub Foul-up David <bouncingcats@gmail.com> - 2020-11-17 00:00 +0100
    Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-21 20:00 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-21 20:40 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 00:10 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Felix Miata <mrmazda@earthlink.net> - 2020-11-22 01:20 +0100
          Re: Fixing a Grub Foul-up, Not There Yet. Kushal Kumaran <kushal@locationd.net> - 2020-11-22 02:10 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. Dan Ritter <dsr@randomstring.org> - 2020-11-22 01:10 +0100
        Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-22 04:50 +0100
      Re: Fixing a Grub Foul-up, Not There Yet. "Martin McCormick" <martin.m@suddenlink.net> - 2020-11-30 18:00 +0100

csiph-web