From mboxrd@z Thu Jan  1 00:00:00 1970
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: Tue, 17 May 2022 12:22:00 +0100
Message-ID: <BA5749B3-7986-4222-B63A-66A9B8653EDB@ipfire.org>
In-Reply-To: <ac520f28-7647-a83a-110f-468d6d397c49@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7089188952988152032=="
List-Id: <development.lists.ipfire.org>

--===============7089188952988152032==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Peter,

> On 16 May 2022, at 19:38, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>=20
> Hello Michael,
>=20
> thanks for your mail, which I unfortunately noticed too late.

LOL

> So, we have this patch in "next" for the time being, which I consider accep=
table, since
> it will not reach anybody aside people running IPFire from the "unstable" t=
ree - which
> is just as the name implies.

Indeed this change will only affect new installations from next and not chang=
e any existing ones.

> Feel free to revert the patch in "next" at your discretion. I do, however, =
not consider
> it overly problematic to stay there. :-)

Not right now, but there is more required to make this work. I will need some=
 time to find out how to do this and until then this sadly will have to block=
 the release:

See my latest comment here: https://bugzilla.ipfire.org/show_bug.cgi?id=3D128=
62#c37

-Michael

>=20
> Thanks, and best regards,
> Peter M=C3=BCller
>=20
>=20
>> Please do not merge this yet.
>>=20
>> This will have to go into c168, but I am not entirely sure what side-effec=
ts it might have for those people who have been running their systems on c167=
 and did a reboot.
>>=20
>> -Michael
>>=20
>>> On 16 May 2022, at 16:17, Peter M=C3=BCller <peter.mueller(a)ipfire.org> =
wrote:
>>>=20
>>> Reviewed-by: Peter M=C3=BCller <peter.mueller(a)ipfire.org>
>>>=20
>>>> 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=3D5
>>>> GRUB_DISTRIBUTOR=3D"$(sed 's, release .*$,,g' /etc/system-release)"
>>>> GRUB_DEFAULT=3Dsaved
>>>> -GRUB_CMDLINE_LINUX=3D"panic=3D10"
>>>> +GRUB_CMDLINE_LINUX=3D"rd.auto panic=3D10"
>>>> GRUB_DISABLE_RECOVERY=3D"true"
>>>> GRUB_BACKGROUND=3D"/boot/grub/splash.png"
>>=20


--===============7089188952988152032==--