Description of problem: while booting the system fails to activate random VGs. System drops to emergency shell and fails to boot. Version-Release number of selected component (if applicable): 2.02.103(2) (2013-10-04) How reproducible: Everytime Steps to Reproduce: 1. Boot system 2. 3. Actual results: System fails to activate VGs and mount filesystems, fails to boot. Expected results: On boot system activates all VGs, LVs, and mounts filesystems. Boots to default run mode. Additional info: getting messages like this in journal: Mar 18 09:08:11 buttercup.redzone.thehillhome.net pvscan[967]: Request to update PV 15nr2D-jDIM-Rytj-pYJl-Qrhv-tR0z-wCg57t in lvmetad gave respo Mar 18 09:08:11 buttercup.redzone.thehillhome.net pvscan[967]: Update of lvmetad failed. This is a serious problem. Mar 18 09:08:11 buttercup.redzone.thehillhome.net pvscan[967]: It is strongly recommended that you restart lvmetad immediately. Mar 18 09:08:11 buttercup.redzone.thehillhome.net systemd[1]: lvm2-pvscan@8:4.service: main process exited, code=exited, status=5/NOTINSSTALLED Mar 18 09:08:11 buttercup.redzone.thehillhome.net systemd[1]: Failed to start LVM2 PV scan on device 8:4. Mar 18 09:08:11 buttercup.redzone.thehillhome.net systemd[1]: Unit lvm2-pvscan@8:4.service entered failed state. When in emergency shell, I can manually activate VGs. File systems mount and I can proceed to default run mode.
Please, take these steps and provide following information for analysis: - add "systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M" to kernel command line - boot your system, when dropped to shell after failure, run "journalctl -b" and save the output and attach it here - save the output from "lsblk" and "lvmdump -ul" command and attach it here too - then manually activate the volumes and when the system if fully started, run "lsblk" and "lvmdump -ul" again and attach the output Thanks.
Created attachment 876315 [details] output of journalctl -b at emergency shel
Created attachment 876316 [details] output of lsblk at emergency shell
Created attachment 876317 [details] lvmdump at emergency shell
Created attachment 876318 [details] output of lsblk at default run level
Created attachment 876319 [details] lvmdump at default run level
From the logs: Mar 19 05:32:49 buttercup pvscan[982]: Request to update PV 15nr2D-jDIM-Rytj-pYJl-Qrhv-tR0z-wCg57t in lvmetad gave response token_mismatch. Reason: token mismatch Mar 19 05:32:49 buttercup pvscan[1099]: Request to update PV VCCQ01-bD2t-yp6W-vVvr-6bgM-xglo-EUFXd6 in lvmetad gave response token_mismatch. Reason: token mismatch Mar 19 05:32:51 buttercup pvscan[991]: Request to update PV E2eYRG-lud2-qSjw-LIGA-3sae-Si5f-wkPF51 in lvmetad gave response token_mismatch. Reason: token mismatch ...we've recently added some fixes in this area, mainly https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=1769eddde7dcdd16716d646e14487cc1df6a3efc Could you please try this build - it includes the latest upstream changes: http://koji.fedoraproject.org/koji/taskinfo?taskID=6654431
Peter, I installed the build. Have booted multiple times successfully. This seems to have fixed my issue. Thanks!
OK, there should be a new LVM2 upstream release soon - I'll do an official update for F20 then. The package you tested contained all we currently have in upstream and which is prepared for the upcoming LVM2 v2.02.106.
lvm2-2.02.106-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/lvm2-2.02.106-1.fc20
Package lvm2-2.02.106-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing lvm2-2.02.106-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-5241/lvm2-2.02.106-1.fc20 then log in and leave karma (feedback).
lvm2-2.02.106-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.