Page 1 of 4 123 ... LastLast
Results 1 to 10 of 34

Thread: boot problem after lvm2 update

  1. #1
    Join Date
    Jan 2009
    Location
    Near Utrecht
    Posts
    8

    Default boot problem after lvm2 update

    Hi,

    Yesterday is installed the lvm2 udpate (version lvm2-2.02.98-0.28.5.1.x86_64). After I rebooted the system I had an issue with several filesystems that wouldn't mount. On one of my systems I have several volumegroups. Alle the logicalvolumes in those other volumegroups weren't available. On a system that has only one volumegroup I get this message when I use a lvm command:
    "WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning."

    The "fault" it seems is the change that was made to lvm.conf. With the update use_lvmetad was changed from 0 to 1 with the purpose of not useing lvm2 activation generation (bug 854413). I got my system working by booting with emergency.target and enabling the lvm2-lvmetad service. This helped for the system that didnt want to boot and for the lvm command giving a warning.

    Now my question is: should lvmetad be started automaticly by some other service or by the updated rpm, or did I do something unexpected that I need lvmetad?

    Regards,
    Arjan de Jong

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,822

    Default Re: boot problem after lvm2 update

    PLease, pleease, please. ALLWAYS tell which version of openSUSE you use!

    We are not clairvoyant.
    Henk van Velden

  3. #3

    Default Re: boot problem after lvm2 update

    Hello,

    same problem here. I run SuSE 13.1 and did a package update yesterday. Today my computer didn't boot anymore because the home lv was not activated on boot (it is in another vg than the system itself). So the boot process hung after a timeout.
    Booted with emergency stick, found this thread, deactivated use_lvmetad in lvm.conf and everything is back to normal.

  4. #4
    Join Date
    Jan 2009
    Location
    Near Utrecht
    Posts
    8

    Default Re: boot problem after lvm2 update

    Hi,

    Yes, you are absolutely right. I should have named the version I'm runnig. My apologsy.

    I'm running OpenSUSE 13.1 64bit.

    Regards,
    Arjan

  5. #5
    Join Date
    Aug 2010
    Location
    Linden, NJ, USA
    Posts
    42

    Unhappy Re: boot problem after lvm2 update

    Quote Originally Posted by susewochs View Post
    Hello,

    same problem here. I run SuSE 13.1 and did a package update yesterday. Today my computer didn't boot anymore because the home lv was not activated on boot (it is in another vg than the system itself). So the boot process hung after a timeout.
    Booted with emergency stick, found this thread, deactivated use_lvmetad in lvm.conf and everything is back to normal.
    I also had OpenSUSE 13.1, updated, and had the system unable to boot with the failed to connect to lvmetad message. The system also has a second volume group like you (which is where it seemed to fail). I'm going to try to reproduce this later in VirtualBox, but it seems like everyone with a second LVM volume group may have been rendered unbootable. I'm going to try the lvm.conf trick you suggested.

  6. #6
    Join Date
    Sep 2012
    Posts
    7,106

    Default Re: boot problem after lvm2 update

    LVM update was removed from mirrors.

  7. #7

    Default Re: boot problem after lvm2 update

    Same here (opensuse 13.1), after an update 2 days ago which included an lvm update, my 2nd VG failed to mount and that inhibited the boot. The 2nd VG contained the old suse 11.4 version so I could boot into 11.4 and modified /etc/fstab to add the "nofail" option to all non-essential file systems (seems like a good precaution anyway). That restored the boot of 13.1, but all LVs of the failing VG did not mount. This could be solved by "vgchange -ay VGname", after which all LVs were mounted. I have added the vgchange command to boot.local as a fudge to get around the lvm problems.

    In fact, this problem was earlier described in https://bugzilla.redhat.com/show_bug.cgi?id=989607

    Regards,


    Quote Originally Posted by duncreg View Post
    I also had OpenSUSE 13.1, updated, and had the system unable to boot with the failed to connect to lvmetad message. The system also has a second volume group like you (which is where it seemed to fail). I'm going to try to reproduce this later in VirtualBox, but it seems like everyone with a second LVM volume group may have been rendered unbootable. I'm going to try the lvm.conf trick you suggested.

  8. #8
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,352
    Blog Entries
    15

    Default Re: boot problem after lvm2 update

    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  9. #9
    Join Date
    Dec 2008
    Location
    Athens
    Posts
    279

    Default Re: boot problem after lvm2 update

    Hello community,

    I have the same problem (OS 13.1 64bit). However, my root partition is on an encrypted lvm (not the one cauding the problem) so I have some difficulties accessing it from the (12.2) live cd in order to change lvm.conf. I tried the following:
    Code:
    sudo modprobe dm-crypt
    sudo cryptsetup luksOpen /dev/sdd cheer
    but I get:
    Code:
     cannot open device sdd
    Any suggestions?
    Main box: OpenSuse 12.3)/KDE 4.10 64bit
    Older Box: OpenSuse 12.2/KDE 4.8.5 64bit (my mediabox)
    Laptop: Debian Wheezy/KDE 4.8.4 64bit

  10. #10
    Join Date
    Dec 2008
    Location
    Athens
    Posts
    279

    Default Re: boot problem after lvm2 update

    Code:
    sudo modprobe dm-crypt
    sudo cryptsetup luksOpen /dev/sda2 cheer
    is ok. (sorry for being to quick with asking, but the thing that it gives me errors about sdd is irritating (I only have three physical hdds in the box)
    Main box: OpenSuse 12.3)/KDE 4.10 64bit
    Older Box: OpenSuse 12.2/KDE 4.8.5 64bit (my mediabox)
    Laptop: Debian Wheezy/KDE 4.8.4 64bit

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •