[opensuse] oss 13.1 and kernel 3.12
My OSS 13.1 systems upgraded (via zypper up) to kernel-default-3.12.53-40.1. However, after the upgrade, the system fails to boot up correctly, complaining about an incomplete lvm and being unable to contact lvmetad (sic?). Is anyone using oss 13.1 with this version of the kernel successfully on a system where root is on lvm? Thank in advance for any help, -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Moby wrote:
My OSS 13.1 systems upgraded (via zypper up) to kernel-default-3.12.53-40.1. However, after the upgrade, the system fails to boot up correctly, complaining about an incomplete lvm and being unable to contact lvmetad (sic?).
Is anyone using oss 13.1 with this version of the kernel successfully on a system where root is on lvm?
Being unable to contact lvmetad is only a warning and does not cause any problems as such. I don't have any systems that boot from LVM, can't help with that. -- Per Jessen, Zürich (6.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 08:17 AM, Per Jessen wrote:
Moby wrote:
My OSS 13.1 systems upgraded (via zypper up) to kernel-default-3.12.53-40.1. However, after the upgrade, the system fails to boot up correctly, complaining about an incomplete lvm and being unable to contact lvmetad (sic?).
Is anyone using oss 13.1 with this version of the kernel successfully on a system where root is on lvm?
Being unable to contact lvmetad is only a warning and does not cause any problems as such. I don't have any systems that boot from LVM, can't help with that.
Agree with comment about wanting about lvmetad. However 1 upgraded to series 4 kernel a long time ago. Currently on 4.4.4-1. The improvements in performance of the series 4 kernel was a noticeable step! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/10/2016 08:17 AM, Per Jessen wrote:
Moby wrote:
My OSS 13.1 systems upgraded (via zypper up) to kernel-default-3.12.53-40.1. However, after the upgrade, the system fails to boot up correctly, complaining about an incomplete lvm and being unable to contact lvmetad (sic?).
Is anyone using oss 13.1 with this version of the kernel successfully on a system where root is on lvm?
Being unable to contact lvmetad is only a warning and does not cause any problems as such. I don't have any systems that boot from LVM, can't help with that.
Agree with comment about wanting about lvmetad. However 1 upgraded to series 4 kernel a long time ago. Currently on 4.4.4-1. The improvements in performance of the series 4 kernel was a noticeable step!
I guess it might be a while before 13.1 moves to up to that. :-) -- Per Jessen, Zürich (7.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 07:33 AM, Per Jessen wrote:
Anton Aylward wrote:
On 03/10/2016 08:17 AM, Per Jessen wrote:
Moby wrote:
My OSS 13.1 systems upgraded (via zypper up) to kernel-default-3.12.53-40.1. However, after the upgrade, the system fails to boot up correctly, complaining about an incomplete lvm and being unable to contact lvmetad (sic?).
Is anyone using oss 13.1 with this version of the kernel successfully on a system where root is on lvm?
Being unable to contact lvmetad is only a warning and does not cause any problems as such. I don't have any systems that boot from LVM, can't help with that.
Agree with comment about wanting about lvmetad. However 1 upgraded to series 4 kernel a long time ago. Currently on 4.4.4-1. The improvements in performance of the series 4 kernel was a noticeable step!
I guess it might be a while before 13.1 moves to up to that. :-)
Thanks Anton and Per. Anton, what repo do you get the 4.X kernel for your OSS 13.1 systems? Per, I am familiar with the warning you speak of. However, with this new kernel, it then complains about an "incomplete lvm" and then fails to mount root etc. Reverting to previous kernel fixes these problems. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Moby wrote:
Per, I am familiar with the warning you speak of. However, with this new kernel, it then complains about an "incomplete lvm" and then fails to mount root etc. Reverting to previous kernel fixes these problems.
Sorry, I misunderstood. Incomplete sounds like hardware might be missing, but when an earlier kernel works, that's clearly not the problem. Might some hardware support have dropped out of the new kernel? Just thinking out loud. -- Per Jessen, Zürich (8.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 09:25 AM, Per Jessen wrote:
Moby wrote:
Per, I am familiar with the warning you speak of. However, with this new kernel, it then complains about an "incomplete lvm" and then fails to mount root etc. Reverting to previous kernel fixes these problems.
Sorry, I misunderstood. Incomplete sounds like hardware might be missing, but when an earlier kernel works, that's clearly not the problem. Might some hardware support have dropped out of the new kernel? Just thinking out loud.
No, its an ancient lvmetad problem with the 3 series kernels. Go back in this list a couple of years and we batted it back and forth a lot. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 08:43 AM, Moby wrote:
Thanks Anton and Per. Anton, what repo do you get the 4.X kernel for your OSS 13.1 systems? Per, I am familiar with the warning you speak of. However, with this new kernel, it then complains about an "incomplete lvm" and then fails to mount root etc. Reverting to previous kernel fixes these problems.
See other post. I see from my notes I had a similar LVM problem with one of the 3 series kernels. I went in to rescue mode on the DVD, mounted the HD rootFS and altered the lvmetad settings and chrooted and mkinitrd'd a new kernel. Yes, the rescue - mount- chroot is a bit fiddly, (and documented extensively on, for example, the Arch system wiki under "Boot Debugging", but sadly I find similar for openSuse) but sometimes its necessary. THIS IS NOT A SYSTEMD PROBLEM ! This is to do with system initialization and getting LVM working despite lvmetad being introduced. Ultimately what needs to be run is /sbin/lvm vgchange -aay --sysinit Yes, this can be, should be, done with a systemd unit. How to get there? But check the value (and comments) in /etc/lvm/lvm.conf for use_lvmetad when you have the real rootFS mounted with the LiveCD. I have it set to "0" https://wiki.archlinux.org/index.php/boot_debugging OOPS! they've changed that from my printed copy! Which is from https://wiki.archlinux.org/index.php?title=Boot_debugging&oldid=337625#Repairing_with_Arch_live_CD -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/10/2016 08:43 AM, Moby wrote:
Thanks Anton and Per. Anton, what repo do you get the 4.X kernel for your OSS 13.1 systems? Per, I am familiar with the warning you speak of. However, with this new kernel, it then complains about an "incomplete lvm" and then fails to mount root etc. Reverting to previous kernel fixes these problems.
See other post.
I see from my notes I had a similar LVM problem with one of the 3 series kernels.
I went in to rescue mode on the DVD, mounted the HD rootFS and altered the lvmetad settings and chrooted and mkinitrd'd a new kernel.
Yes, the rescue - mount- chroot is a bit fiddly, (and documented extensively on, for example, the Arch system wiki under "Boot Debugging", but sadly I find similar for openSuse) but sometimes its necessary.
THIS IS NOT A SYSTEMD PROBLEM !
This is to do with system initialization and getting LVM working despite lvmetad being introduced.
Ultimately what needs to be run is
/sbin/lvm vgchange -aay --sysinit
Yes, this can be, should be, done with a systemd unit. How to get there?
And why does it work with the previous kernel? -- Per Jessen, Zürich (8.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 10:18 AM, Per Jessen wrote:
And why does it work with the previous kernel?
I think that was when lvmetad changed. Check the archives. 2014 I think. We had a discussion about it then, but I'm not sure what kernel version that was for, but it was a 3 series on. https://bugzilla.novell.com/show_bug.cgi?id=862076 Perhaps lvmetad service or socket needs enabling? perhaps https://bugzilla.suse.com/show_bug.cgi?id=875307 for which the fix is, as i described previously, edit /etc/lvm/lvm.conf Or taking it, and much else, out altogether YMMV. https://lists.opensuse.org/opensuse-bugs/2014-02/msg00320.html https://bugzilla.novell.com/show_bug.cgi?id=862286 update of lvm2 create a dependency on lvmetad but this one is not present in initrd pertains to 13.1 Encrypted FS just confuses the issue. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
On 03/10/2016 10:18 AM, Per Jessen wrote:
And why does it work with the previous kernel?
I think that was when lvmetad changed. Check the archives. 2014 I think. We had a discussion about it then, but I'm not sure what kernel version that was for, but it was a 3 series on.
Yes, I think saw that one, but the kernel should not be touching any LVM settings and lvmetad is user-space. I don't see how upgrading to 3.12 should suddenly cause this issue. That's the weird thing.
Perhaps lvmetad service or socket needs enabling?
perhaps
https://bugzilla.suse.com/show_bug.cgi?id=875307
for which the fix is, as i described previously, edit /etc/lvm/lvm.conf
Or taking it, and much else, out altogether
Sure, but it doesn't explain why reverting to 3.11 fixed the problem. -- Per Jessen, Zürich (7.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 12:02 PM, Per Jessen wrote:
Sure, but it doesn't explain why reverting to 3.11 fixed the problem.
Perhaps there was something in the kernel. Or the initrd. A diff between the lsinitrd of each of them might reveal something. And lets not forget that you don't actually boot the kernel, you boot the initrd. look to your own initrd for anything to do with lvm. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/10/2016 08:33 AM, Per Jessen wrote:
Anton Aylward wrote:
On 03/10/2016 08:17 AM, Per Jessen wrote:
Moby wrote:
My OSS 13.1 systems upgraded (via zypper up) to kernel-default-3.12.53-40.1. However, after the upgrade, the system fails to boot up correctly, complaining about an incomplete lvm and being unable to contact lvmetad (sic?).
Is anyone using oss 13.1 with this version of the kernel successfully on a system where root is on lvm?
Being unable to contact lvmetad is only a warning and does not cause any problems as such. I don't have any systems that boot from LVM, can't help with that.
Agree with comment about wanting about lvmetad. However 1 upgraded to series 4 kernel a long time ago. Currently on 4.4.4-1. The improvements in performance of the series 4 kernel was a noticeable step!
I guess it might be a while before 13.1 moves to up to that. :-)
regular readers might recall that (a) I still use 13.1 (without Evergreen) and (b) that I use the Kernel_Stable repository for 13.1: http://download.opensuse.org/repositories/Kernel:/stable/standard/ Other 13.1 users might want to try out the 4.4 series kernels. Set the values in /etc/zypp/zypp.conf for multiversion.kernels to preserve what you have beforehand. Check out the revision notes ahead of time. I think some of the changes to BtrFS cannot be reversed to some 3.x kernels. That being said, I have no regrets whatsoever about moving to the series 4 kernels. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Anton Aylward -
Moby -
Per Jessen