** Changed in: lvm2 (Debian)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for
There are two things:
- On servers, ubuntu-server depends on mdadm, so removing mdadm also
removes ubuntu-server package, which means it's not really supported
- In general, the installers don't offer installing like that.
I don't know why we did not have a task for xenial.
** Description
Sorry, I didn't actually test Focal and Groovy.
Xenial will be supported for about a year, so I think it worth to fix it
there as well; however it's relative what worth to fix and what not, as
most users probably left Xenial behind already or applied a workaround
if they were ever affected by
That's certainly incorrect, lvm2 was fixed in focal (and hence groovy).
That only leaves xenial, but updating xenial close to its EOL for
something as unusual as this seems unneccessary. The supported
configuration for raid1 is mdadm after all, not removing mdadm and the
meta packages that depend
Hi Steve, Julian, Łukasz, everyone,
Sorry that I didn't test the package on time – my life circumstances
have significantly changed since I reported this bug, nowadays I don't
have enough free time to do as much testing as I did back in the day.
I've been using the workaround ever since then,
This bug was fixed in the package lvm2 - 2.03.02-2ubuntu6.1
---
lvm2 (2.03.02-2ubuntu6.1) eoan; urgency=medium
[ Steve Langasek ]
* Include raid1 in the list of modules installed by the initramfs hook,
as this is not a kernel module dependency of dm-raid but if the user's
This bug was fixed in the package lvm2 - 2.02.176-4.1ubuntu3.18.04.3
---
lvm2 (2.02.176-4.1ubuntu3.18.04.3) bionic; urgency=medium
[ Steve Langasek ]
* Include raid1 in the list of modules installed by the initramfs hook,
as this is not a kernel module dependency of dm-raid
The regressions in bionic seem unrelated to me adding the raid1 module
to the list of modules installed to the initramfs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
eoan verified.
So, eoan is tougher. I installed it with subiquity and tried to follow
the steps, but failed to convert to raid1, apparently, subiquity created
the LV 1 PE larger than before or something, so it needed 1 free PE in
the original PV to be able to add the raid1 metadata, which it did
** Tags added: id-5d0ba914f340e31a8e9f2cf1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status
verified in bionic
Did all the steps (install vm, create pv, extend pv, remove dmadm,
upgrade).
It booted after the upgrade to 2.02.176-4.1ubuntu3.18.04.3, and it
failed again following a downgrade to the 2.02.176-4.1ubuntu3.18.04.2
from updates pocket.
** Tags removed:
** Description changed:
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
[Test case]
1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert
** Description changed:
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
[Test case]
1. Install server with subiquity to LVM
- 2. Add second disk to it
- 3. Run pvcreate /dev/vdb
- 4. Run vgextend ubuntu-vg /dev/vdb
- 5. Run lvconvert
** Description changed:
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
[Test case]
- 1. Install server with subiquity to VM
+ 1. Install server with subiquity to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run
sorry, working on verifying it, got distracted by other stuff.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is
Hello MegaBrutal, or anyone else affected,
Accepted lvm2 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.03.02-2ubuntu6.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: lvm2 (Ubuntu Eoan)
Status: Triaged => In Progress
** Changed in: lvm2 (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Description changed:
- After upgrading to Wily, raid1 LVs don't activate during the initrd
- phase. Since the root LV is also RAID1-mirrored, the system doesn't
- boot.
+ [Impact]
+ system does not boot after converting lvm volume to raid1 w/o having mdadm
installed.
+
+ [Test case]
+
+ 1.
** Changed in: lvm2 (Ubuntu Disco)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1
This bug was fixed in the package lvm2 - 2.03.02-2ubuntu7
---
lvm2 (2.03.02-2ubuntu7) focal; urgency=medium
* Include raid1 in the list of modules installed by the initramfs hook,
as this is not a kernel module dependency of dm-raid but if the user's
root disk is configured
** Changed in: linux (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux (Ubuntu Cosmic)
Status: New => Invalid
** Changed in: linux (Ubuntu Disco)
Status: New => Invalid
** Changed in: lvm2 (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: lvm2
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status in linux package in
** Changed in: lvm2 (Debian)
Status: Unknown => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1
** Tags added: id-5d0ba914f340e31a8e9f2cf1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status
** Changed in: lvm2 (Ubuntu Eoan)
Milestone: ubuntu-16.03 => None
** Changed in: lvm2 (Ubuntu Eoan)
Assignee: Andy Whitcroft (apw) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Tags removed: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status in linux
** Also affects: lvm2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Eoan)
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status in
** Bug watch added: Debian Bug tracker #868268
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868268
** Also affects: lvm2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868268
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Also affects 18.04
The "easiest" fix I can see is to add the raid1 and raid10 modules to
the manually added modules in /usr/share/initramfs-tools/hooks/lvm2
(dm_raid.ko depends on raid456.ko, but not raid1.ko or raid10.ko)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: lvm2 (Ubuntu)
Milestone: ubuntu-16.02 => ubuntu-16.03
** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-16.02 => ubuntu-16.03
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
** Changed in: lvm2 (Ubuntu)
Milestone: ubuntu-16.01 => ubuntu-16.02
** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-16.01 => ubuntu-16.02
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Thanks for the workaround! It seems adding raid1 is enough.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not
** Changed in: lvm2 (Ubuntu)
Milestone: ubuntu-15.12 => ubuntu-16.01
** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-15.12 => ubuntu-16.01
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
As a workaround, you can add the relevant modules to the initramfs. A
quick walkthrough is as follows:
- Boot from the install media, and choose "Rescue a broken system."
- Run through all of the basic configuration steps, configuring location,
keyboard, networking, timezone, etc.
- When
** Changed in: lvm2 (Ubuntu)
Milestone: ubuntu-15.11 => ubuntu-15.12
** Changed in: initramfs-tools (Ubuntu)
Milestone: ubuntu-15.11 => ubuntu-15.12
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
It seems that that module is built and installed into /lib/modules, but
is not in the initramfs. Sounds like an initramfs-tools bug.
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in:
Reproducible: upgraded another Ubuntu installation in VM and got the same
result.
Since the bug prevents booting, I suggest to increase priority to High.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
I can't collect logs on non-booting system.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
** Tags added: regression-release wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1509717
Title:
Wily LVM-RAID1 – md: personality for level 1 is not loaded
Status in
40 matches
Mail list logo
