[Bug 997637] New: LVM volume disabled after installation
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 Bug ID: 997637 Summary: LVM volume disabled after installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: rdodopoulos@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I installed Leap 42.2 Beta 1 in a single disk with LVM (1 root volume and 1 home volume). However, it couldn't boot because the home (h) LVM volume was disabled. It was able to boot only after disabling lvm2-lvmetad.service and setting 'use_lvmetad = 0' in /etc/lvm/lvm.conf. disk/LVM info:
# fdisk -l Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 70046E07-2744-4188-A239-AE9BF70F5577
Device Start End Sectors Size Type /dev/sdb1 2048 2105343 2103296 1G EFI System /dev/sdb2 2105344 10489855 8384512 4G Microsoft basic data /dev/sdb3 10489856 500117503 489627648 233.5G Linux LVM
Disk /dev/mapper/cr_ata-SK_hynix_SC210_mSATA_256GB_EJ58N40021110821Q-part3: 233.5 GiB, 250687258624 bytes, 489623552 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/l-r: 25 GiB, 26843545600 bytes, 52428800 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/l-h: 193.5 GiB, 207727099904 bytes, 405716992 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes
# lvdisplay --- Logical volume --- LV Path /dev/l/h LV Name h VG Name l LV UUID FCdk4S-ep35-L6cO-WiMu-rLzh-04CD-wDLAtE LV Write Access read/write LV Creation host, time rwmanos, 2016-09-07 15:13:37 +0200 LV Status available # open 1 LV Size 193.46 GiB Current LE 49526 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 1024 Block device 254:2
--- Logical volume --- LV Path /dev/l/r LV Name r VG Name l LV UUID EJia6x-Yq0H-TMNr-uztr-DkKk-K3dZ-EQzgqu LV Write Access read/write LV Creation host, time rwmanos, 2016-09-07 15:13:39 +0200 LV Status available # open 1 LV Size 25.00 GiB Current LE 6400 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 1024 Block device 254:1
# vgdisplay --- Volume group --- VG Name l System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size 233.47 GiB PE Size 4.00 MiB Total PE 59768 Alloc PE / Size 55926 / 218.46 GiB Free PE / Size 3842 / 15.01 GiB VG UUID cM5z9A-cLuZ-FeUT-7iht-CUSd-9eRa-zeT81u
# pvdisplay --- Physical volume --- PV Name /dev/mapper/cr_ata-SK_hynix_SC210_mSATA_256GB_EJ58N40021110821Q-part3 VG Name l PV Size 233.47 GiB / not usable 2.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 59768 Free PE 3842 Allocated PE 55926 PV UUID t5xMc2-7LC1-5F0e-8kr9-esYo-xDVb-uAKh49
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 Martin Pluskal <mpluskal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c14 --- Comment #14 from Stakanov Schufter <stakanov@freenet.de> --- Maybe also good to know that (with beta2) I (bug 1000722) did not get any warning during install. Went through as if everything would be O.K. up to the moment when you hit the problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c15 --- Comment #15 from Stakanov Schufter <stakanov@freenet.de> --- Created attachment 694535 --> http://bugzilla.opensuse.org/attachment.cgi?id=694535&action=edit system starts up to my surprise without intervention (after changing the order of disks) this is the journal of the boot. The pertinent date is 27.09. I did want to apply the corrections for the start up, in the meanwhile I had changed the hardware to a three system disk and changed the sata with the beta from the first position to the second. I did choose to boot from the second disk and went away to get the info on how to change the setup. I came back....and found myself on the booted beta2 dektop. So the change of position makes the install work. If you need also or deem useful yast2 log, I will provide. No change but the hardware position (multiple disks present during boot instead of one) had taken place. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c16 --- Comment #16 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- I'll report what I'm seeing on this bug. I have 3 systems (call them system1, system2 and system3). I have tested all alpha/beta release of 42.2 on systems 1 and 2. The install on system3 is new for Beta2. On system1 and system3, I am having LVM issues. It seems to be intermittant. Sometimes it boots okay and sometimes it goes into emergency mode. (If I set "use_lvmetad = 0" then the system always boots okay). On system2, I have never had a problem. Here is what I suspect is the main difference. On system1 and system3, the root, swap and home all come from the encrypted LVM. On system2, the root file system is a separate (unencrypted) partition with only swap and home coming from the encrypted LVM. On system1 and system3, when boot fails (goes to emergency mode), I look at "/dev/mapper". Always the root volume and the swap volume have been mapped, but nothing else is mapped. When it boot successfully, everything is mapped. My best guess is that there is a timing issue. And maybe that has something to do with the switchover from using the initrd to using the root file system. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c17 Ludwig Nussel <lnussel@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers@suse.de | |, trenn@suse.com --- Comment #17 from Ludwig Nussel <lnussel@suse.com> --- let's CC systemd and dracut maintainers. Maybe they can help here. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c20 --- Comment #20 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Here's requested output (requested in comment 19): After a successful boot: ---- # systemctl status lvm2-lvmetad.service ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2016-09-28 09:03:49 CDT; 1min 48s ago Docs: man:lvmetad(8) Main PID: 1196 (lvmetad) Tasks: 1 (limit: 512) CGroup: /system.slice/lvm2-lvmetad.service └─1196 /sbin/lvmetad -f Sep 28 09:03:49 nwr8 systemd[1]: Started LVM2 metadata daemon. # systemctl status lvm2-pvscan@pv_major:pv_minor.service ● lvm2-pvscan@pv_major:pv_minor.service - LVM2 PV scan on device pv_major:pv_minor Loaded: loaded (/usr/lib/systemd/system/lvm2-pvscan@.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:pvscan(8) # systemctl status systemd-cryptsetup@home.service ● systemd-cryptsetup@home.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) # systemctl status systemd-cryptsetup@xhome.service ● systemd-cryptsetup@xhome.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) ---- I repeated that last one with "xhome" because I am actually mounting the home volume at "/xhome" on that system (and I then use symlinks into it from home directory). That's to avoid problems with using the same home volume on more than one system. I'm not sure that's checking anything, since cryptsetup would be for the LVM, rather than for the home volume. After an unsuccessful boot (I ran these from emergency mode before doing anything else: ---- # systemctl status lvm2-lvmetad.service ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2016-09-28 09:09:56 CDT; 2min 9s ago Docs: man:lvmetad(8) Main PID: 1142 (lvmetad) Tasks: 1 (limit: 512) CGroup: /system.slice/lvm2-lvmetad.service └─1142 /sbin/lvmetad -f Sep 28 09:09:56 nwr8 systemd[1]: Started LVM2 metadata daemon. # systemctl status lvm2-pvscan@pv_majorr:pv_minor.service ● lvm2-pvscan@pv_majorr:pv_minor.service - LVM2 PV scan on device pv_majorr:pv_minor Loaded: loaded (/usr/lib/systemd/system/lvm2-pvscan@.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:pvscan(8) ---- I'll add that I booted 3 times this morning. The first two boots were successful. The third took me to emergency mode with "/xhome" not mounted. I mention this as an indicator that the problem is intermittent. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c21 --- Comment #21 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- An additional comment. I'm not sure if this is relevant, but I will mention it. After a failed boot, I tried to manually access the LVM volumes. And I ran into this problem: ---- # vgchange -a y Request to list VGs in lvmetad gave response token_mismatch. Reason: lvmetad cache is invalid due to a global_filter change or due to a running rescan ---- I did not see that on the alpha releases of 42.2. I have seen that on both Beta releases. Additional information: the computer (system1 as identified in an earlier comment) has two hard drives, with an encrypted LVM on each. Install added "crypttab" entries for both of those encrypted LVMs. If I comment out the crypttab entry that is not actually needed, then I do not run into error above. If I leave both entries uncomments (thus active), then I seem to always run into that problem, which leaves no way of continuing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c23 --- Comment #23 from Neil Rickert <nwr10cst-oslnx@yahoo.com> ---
pv_major:pv_minor should be replaced by PV's major and minor number
Oops. Sorry about that. Let's try again. First, after a successful boot: ---- # systemctl status lvm2-lvmetad.service ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2016-09-28 22:30:34 CDT; 3min 38s ago Docs: man:lvmetad(8) Main PID: 1104 (lvmetad) Tasks: 1 (limit: 512) CGroup: /system.slice/lvm2-lvmetad.service └─1104 /sbin/lvmetad -f Sep 28 22:30:34 nwr8 systemd[1]: Started LVM2 metadata daemon. # systemctl status lvm2-pvscan@8:21.service ● lvm2-pvscan@8:21.service - LVM2 PV scan on device 8:21 Loaded: loaded (/usr/lib/systemd/system/lvm2-pvscan@.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:pvscan(8) ---- And next, from emergency mode after a failed boot: ---- # systemctl status lvm2-lvmetad.service ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2016-09-28 22:46:12 CDT; 2min 34s ago Docs: man:lvmetad(8) Main PID: 1162 (lvmetad) Tasks: 1 (limit: 512) CGroup: /system.slice/lvm2-lvmetad.service └─1162 /sbin/lvmetad -f Sep 28 22:46:12 nwr8 systemd[1]: Started LVM2 metadata daemon. # systemctl status lvm2-pvscan@8:21.service ● lvm2-pvscan@8:21.service - LVM2 PV scan on device 8:21 Loaded: loaded (/usr/lib/systemd/system/lvm2-pvscan@.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:pvscan(8) ---- The first two boots tonight were successful. The third went into emergency mode over the LVM problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c26 --- Comment #26 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- I realized the mistake on that "pvscan" check. The major:minor of 8:21 refers to the encrypted container. I should, instead, have used 254:0. That's what gives more interesting output on my 42.1 system (which does not use lvmetad). So I tried that, but still got about the same output as before. Hmm, shouldn't the scan be done by "lvmetad" rather than by "systemd"? Maybe that "systemctl" command is checking something that doesn't matter. On the udev rules: I'm seeing what Ludwig mentioned. That is, there is no mention of "SYSTEMD_WANTS" in that file. There is a rule: RUN+="/sbin/lvm pvscan --background --cache --activate ay --major $major --minor $minor", ENV{LVM_SCANNED}="1" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=997637 http://bugzilla.opensuse.org/show_bug.cgi?id=997637#c29 --- Comment #29 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- Encrypted LVM seems to be working correctly in 42.2 Beta3. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com