1 |
On Tuesday, May 28, 2019 5:14:42 P.M. AEST Michael Haubenwallner wrote: |
2 |
> Hi Paul, |
3 |
> |
4 |
> as an LVM user without deeper knowledge, stumbled upon your question without |
5 |
> any reply yet, and my fear was to run into the same when updating lvm2. |
6 |
> On 5/17/19 2:26 PM, Paul Colquhoun wrote: |
7 |
> > Recently I found that new kernels were not booting for me, because they |
8 |
> > could not assemble the LVM partition that I use for the root filesystem. |
9 |
> > |
10 |
> > Booting back to my old kernel still worked. |
11 |
> > |
12 |
> > I have tracked this back to the lvm2 version. |
13 |
> > |
14 |
> > After booting with the old kernel, I ran lvm and tried the 'fullreport' |
15 |
> > command. |
16 |
> > |
17 |
> > sys-fs/lvm2-2.02.184-r3 gives an error: |
18 |
> > |
19 |
> > lvm> fullreport |
20 |
> > |
21 |
> > LV root invalid: visible raid meta LV for raid1 segment |
22 |
> > LV root invalid: visible raid meta LV for raid1 segment |
23 |
> > Internal error: LV segments corrupted in root. |
24 |
> |
25 |
> Searching the web with parts of this error messages leads me to this commit: |
26 |
> https://github.com/lvmteam/lvm2/commit/dd5716ddf258c4a44819fa90d3356833ccf7 |
27 |
> 67b4 |
28 |
> |
29 |
> While I have no idea about "visible SubLVs", maybe that commit message can |
30 |
> tell something to you? |
31 |
> |
32 |
> > After backing out to an earlier version, sys-fs/lvm2-2.02.183 |
33 |
> > the 'fullreport' actually gives a report. |
34 |
> > |
35 |
> > I'm assuming the only reason the old kernel boots is that it has the older |
36 |
> > lvm in the initramfs, and once assembled the handover to the live system |
37 |
> > still works. |
38 |
> > |
39 |
> > I can't find anything online that looks like the same thing to me, so I |
40 |
> > was |
41 |
> > wondering if anyone here had encountered a similar problem? |
42 |
> > |
43 |
> > The next step is to try and find how to update the on-disk lvm meta data |
44 |
> > so the later versions understand it, hopefully without having to rebuild |
45 |
> > my system from scratch. |
46 |
> |
47 |
> As far as I understand, this doesn't seem like a metadata format _change_, |
48 |
> but a rare metadata consistency problem that goes unnoticed by the older |
49 |
> version. |
50 |
|
51 |
|
52 |
Once I deleted & re-created the logical volume the newer versions had no |
53 |
problem. |
54 |
|
55 |
Unfortunately, since it was my root partition, that took moving data to a |
56 |
temporary volume, rebooting from there, re-creating the old LV, moving the |
57 |
data back, and rebooting again. Not a quick fix, even if it wasn't that |
58 |
difficult. |
59 |
|
60 |
|
61 |
-- |
62 |
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ |
63 |
Asking for technical help in newsgroups? Read this first: |
64 |
http://catb.org/~esr/faqs/smart-questions.html#intro |