unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Emmanuel Beffara <manu@beffara.org>
Cc: 62140@debbugs.gnu.org, Michael Rohleder <mike@rohleder.de>,
	44877@debbugs.gnu.org
Subject: bug#62140: enable LVM in Grub
Date: Fri, 24 Mar 2023 08:24:30 -0400	[thread overview]
Message-ID: <87edpe1gn5.fsf@gmail.com> (raw)
In-Reply-To: <20230323155819.GC5268@beffara.org> (Emmanuel Beffara's message of "Thu, 23 Mar 2023 15:58:19 +0100")

Hi,

Emmanuel Beffara <manu@beffara.org> writes:

> Hello,
>
> De Maxim Cournoyer le 23/03/2023 à 13:48:
>> It seems to me that since we produce grub.cfg ourselves if there's something
>> to add there for LVM support (which I'm not sure there is -- apparently it
>> already works for you ?), it should be explicitly coded in (gnu bootloader
>> grub).
>
> It does not work for me, that is why I reported this! The system does not boot
> unless I manually add `insmod lvm` in `grub.cfg` because Grub does not find
> the partition that contains the store.
>
> So I agree something has to be done there.

OK, thanks for explaining.  Could you please try
https://issues.guix.gnu.org/60442 (by applying the patch to a local guix
checkout, building it, then 'sudo -E ./pre-inst-env sudo guix system
reconfigure /path/to/your/config.scm)?  The test suite was broken it
seems (it passed without the fix), but perhaps the fix still does work?

-- 
Thanks,
Maxim




  reply	other threads:[~2023-03-24 22:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 18:02 bug#62140: enable LVM in Grub Emmanuel Beffara
2023-03-13 13:56 ` bug#44877: " Michael Rohleder
2023-03-14 21:26   ` Emmanuel Beffara
2023-03-23 12:48     ` Maxim Cournoyer
2023-03-23 14:58       ` Emmanuel Beffara
2023-03-24 12:24         ` Maxim Cournoyer [this message]
2023-03-28 12:32           ` Emmanuel Beffara
2023-03-28 14:10             ` Maxim Cournoyer
2024-01-23 16:36 ` Erik Eduardo via Bug reports for GNU Guix

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87edpe1gn5.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=44877@debbugs.gnu.org \
    --cc=62140@debbugs.gnu.org \
    --cc=manu@beffara.org \
    --cc=mike@rohleder.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).