I would like to share some more info. Yesterday I had a look at how
dracut (version 059-4) manages LVM activation. It uses the older LVM way
that allows partial VG activation:
-
mkdir /var/tmp/dracut
cd /var/tmp/dracut/
lsinitrd --unpack
I agree with all Melvin Vermeeren's points and would also kindly ask
Bastian to reconsider reopening this bug.
There are 2 proposed solutions, but each one has its own issues.
- Splitting the VG into 2 separate VGs certainly resolves the bug, but
it could make impossible to have fancy setups
Dear Bastian,
On 2023-05-11 17:42, Bastian Blank wrote:
Control: tags -1 wontfix
On Wed, May 10, 2023 at 03:09:04AM +0200, Guilhem Moulin wrote:
Please consider the enclosed patch. The aim is to also activate
incomplete VGs at early boot stage, like lvm2 used to do before
2.03.15-1, and be a
Hi,
My wording might be a bit over the top, apologies in advance. I do really mean
the best, just a bit baffled at the wontfix reply and lack of acknowledgement
of the problem.
I'm not really understanding the "Half VG was never a real thing" approach and
general dismissal of this bug, I
On Thu, May 11, 2023 at 06:25:00PM +0200, Guilhem Moulin wrote:
> On Thu, 11 May 2023 at 18:12:52 +0200, Bastian Blank wrote:
> > Nope, not really. Half VG was never a real thing. It might work in
> > some cases.
> And these use-cases are unbootable since 2.03.15…
Those still have access to an
On Thu, 11 May 2023 at 18:12:52 +0200, Bastian Blank wrote:
> Nope, not really. Half VG was never a real thing. It might work in
> some cases.
And these use-cases are unbootable since 2.03.15…
> Then, degraded is the default activation mode, so overriding that would
> not be appropriate. But
On Wed, May 10, 2023 at 03:09:04AM +0200, Guilhem Moulin wrote:
> There might be a better way to detect an initramfs-tools environment
> than checking whether ‘/run/initramfs’ exists (and ‘/run/systemd/system’
> doesn't).
The only acceptable way would be a different udev rules file for the
Hey Guilhem.
> There might be a better way to detect an initramfs-tools environment
I once faced the same question when writing a (cryptsetup) keyscript,
i.e. how to definitely find out whether one's "within" the initramfs.
With crypsetup it may seem easy - check for e.g. /scripts/local-
Control: severity -1 serious
Control: tag -1 + patch
Please consider the enclosed patch. The aim is to also activate
incomplete VGs at early boot stage, like lvm2 used to do before
2.03.15-1, and be a no op on “normal systems” once execution has been
handed over to init(1).
There might be a
Hello,
I've faced the same error for a while on an x86_64 computer running
Debian sid amd64, which has a VG spanning two PVs inside LUKS volumes
located on a SSD (rootfs) and a HDD (home).
Both LUKS volumes is declared into crypttab, as they should be.
This two-LUKS volume, two-PV setup was
Similar here. Had been getting error messages about missing PV during boot
for a while, but since everything worked fine once booted I didn't bother
to resolve that. Now I started getting boot errors instead. Turns out the
initramfs was missing a module (pata_atiixp) needed for the controller for
Package: lvm2
Version: 2.03.16-1
Severity: important
X-Debbugs-Cc: vermee...@vermwa.re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
Since LVM 2.03.15 or possibly 2.03.16 my system fails to boot during initramfs
because the root LVM LV is not activated. I did some digging and
12 matches
Mail list logo
