ALT Linux users (in English only)
 help / color / mirror / Atom feed
From: Michael Shigorin <mike@altlinux.org>
To: TheGrove <admin@thegrove.in.nf>
Cc: ALT Linux <community-en@lists.altlinux.org>
Subject: Re: [Comm-en] Recover missing boot option in GRUB after upgrade
Date: Mon, 29 Jan 2024 08:47:51 +0300
Message-ID: <20240129054751.GR4332@imap.altlinux.org> (raw)
In-Reply-To: <02eed1a2-23ac-66a1-daa8-9b22d7fc1c6d@thegrove.in.nf>

On Sun, Jan 28, 2024 at 11:11:35PM -0600, TheGrove wrote:
> Although my main objective was to upgrade to p10, I would still like to
> experiment with Sisyphus from time to time.  Is there an easy way for me
> to recover the option in GRUB to boot into Sisyphus on /dev/sda5?

I'm not a GRUB expert (having not maintained it for many years
and never having really loved it), but:

1) is os-prober package installed on "stable" system"?
   (it *might* be related to non-Linux OS detection in dual-boot,
   in which case I'd dig for some discussions on "grub multiboot"
   or "grub dual-root" maybe)

2) there's a Russian ALT wiki page on the topic:
   http://altlinux.org/Grub#Как_установить/восстановить_загрузочную_запись_grub?
   
   "mount-system" is ALT Rescue specific script that
   basically finds a probable rootfs, mounts it as
   /mnt/system1 and bind-mounts the virtual FSes there:

   for i in proc sys dev; do mount --bind $i /mnt/system1/$i; done
   
   -- this can perfectly be done by hand from an already running
   system, of course :-) -- but the recipe results in *that* copy
   of grub installing its boot record/files/configs, potentially
   ignoring the other systems like what you observe currently.

If these don't help, well, let's think on.

PS: do backup *both* of your /boot directories just in case,
even if it's a simple "cp -a /boot /root".

-- 
Michael Shigorin
http://altlinux.org/elbrus


      reply	other threads:[~2024-01-29  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  5:11 TheGrove
2024-01-29  5:47 ` Michael Shigorin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240129054751.GR4332@imap.altlinux.org \
    --to=mike@altlinux.org \
    --cc=admin@thegrove.in.nf \
    --cc=community-en@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux users (in English only)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community-en/0 community-en/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community-en community-en/ http://lore.altlinux.org/community-en \
		community-en@lists.altlinux.org community-en@lists.altlinux.ru community-en@lists.altlinux.com
	public-inbox-index community-en

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community-en


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git