public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] dracut: Enable automatic assembly of any RAID/LVM devices
Date: Mon, 16 May 2022 16:18:49 +0100	[thread overview]
Message-ID: <98FDDFAD-80C6-4198-9E41-24C9DFC45C7D@ipfire.org> (raw)
In-Reply-To: <8245a52f-58e7-438f-530f-0fb333609906@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]

Please do not merge this yet.

This will have to go into c168, but I am not entirely sure what side-effects it might have for those people who have been running their systems on c167 and did a reboot.

-Michael

> On 16 May 2022, at 16:17, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>
> 
>> This has changed in dracut 24 and we have used various hacks to enable
>> this behaviour again when it would have been so easy to just enable this
>> parameter.
>> Fixes: #12862 - Upgrade from Core 166 to 167 does not use RAID anymore
>> Reported-by: Dirk Sihling <dsihling(a)web.de>
>> Reported-by: Adolf Belka <adolf.belka(a)ipfire.org>
>> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
>> ---
>>  config/grub2/default | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> diff --git a/config/grub2/default b/config/grub2/default
>> index c1b78237e..127d33445 100644
>> --- a/config/grub2/default
>> +++ b/config/grub2/default
>> @@ -1,6 +1,6 @@
>>  GRUB_TIMEOUT=5
>>  GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
>>  GRUB_DEFAULT=saved
>> -GRUB_CMDLINE_LINUX="panic=10"
>> +GRUB_CMDLINE_LINUX="rd.auto panic=10"
>>  GRUB_DISABLE_RECOVERY="true"
>>  GRUB_BACKGROUND="/boot/grub/splash.png"


  reply	other threads:[~2022-05-16 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 14:48 Michael Tremer
2022-05-16 15:17 ` Peter Müller
2022-05-16 15:18   ` Michael Tremer [this message]
2022-05-16 18:38     ` Peter Müller
2022-05-17 11:22       ` Michael Tremer

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=98FDDFAD-80C6-4198-9E41-24C9DFC45C7D@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox