Description of problem: Version-Release number of selected component: anaconda-23.19.10-1 The following was filed automatically by anaconda: anaconda 23.19.10-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.4/site-packages/gi/overrides/BlockDev.py", line 416, in wrapped raise transform[1](msg) File "/usr/lib/python3.4/site-packages/blivet/devices/lvm.py", line 700, in _setup blockdev.lvm.lvactivate(self.vg.name, self._name) File "/usr/lib/python3.4/site-packages/blivet/devices/storage.py", line 386, in setup self._setup(orig=orig) File "/usr/lib/python3.4/site-packages/blivet/osinstall.py", line 619, in mountFilesystems device.setup() File "/usr/lib/python3.4/site-packages/blivet/blivet.py", line 1405, in mountFilesystems readOnly=readOnly, skipRoot=skipRoot) File "/usr/lib/python3.4/site-packages/blivet/osinstall.py", line 1105, in turnOnFilesystems storage.mountFilesystems() File "/usr/lib64/python3.4/site-packages/pyanaconda/install.py", line 195, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) File "/usr/lib64/python3.4/threading.py", line 868, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 253, in run threading.Thread.run(self, *args, **kwargs) gi.overrides.BlockDev.LVMError: Process reported exit code 1280: Volume group "vg3" not found Cannot process volume group vg3 Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=Fedora-23-x86_64/vmlinuz initrd=Fedora-23-x86_64/initrd.img ks=http://dist.control.lth.se/private/kickstart/Fedora-23-x86_64 hostname=fay-04 keymap=se-latin1 BOOTIF=01-54-be-f7-08-3c-2d dnf.rpm.log: Dec 07 09:56:47 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.2.3-300.fc23.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 23
Created attachment 1103106 [details] File: anaconda-tb
Created attachment 1103107 [details] File: anaconda.log
Created attachment 1103108 [details] File: dnf.log
Created attachment 1103109 [details] File: environ
Created attachment 1103110 [details] File: ks.cfg
Created attachment 1103111 [details] File: lsblk_output
Created attachment 1103112 [details] File: nmcli_dev_list
Created attachment 1103113 [details] File: os_info
Created attachment 1103114 [details] File: storage.log
Created attachment 1103115 [details] File: syslog
Created attachment 1103116 [details] File: ifcfg.log
Created attachment 1103117 [details] File: packaging.log
Created attachment 1103118 [details] File: program.log
*** Bug 1289227 has been marked as a duplicate of this bug. ***
Created attachment 1103308 [details] The file included from ks.cfg
Seems to be related lvmetad, after the error has occured, vg3 is no longer visible, but clearing the cache and rescanning makes it visible again. The problem seems to depend on disks being > 2TB. # pvscan PV /dev/md126 VG vg0 lvm2 [499.87 GiB / 191.87 GiB free] PV /dev/sda4 VG vg1 lvm2 [1.32 TiB / 0 free] PV /dev/sdb4 VG vg2 lvm2 [1.32 TiB / 0 free] Total: 3 [3.13 TiB] / in use: 3 [3.13 TiB] / in no VG: 0 [0 ] # pvscan --cache # pvscan PV /dev/md126 VG vg0 lvm2 [499.87 GiB / 191.87 GiB free] PV /dev/sda4 VG vg1 lvm2 [1.32 TiB / 0 free] PV /dev/sdb4 VG vg2 lvm2 [1.32 TiB / 0 free] PV /dev/md127 VG vg3 lvm2 [5.46 TiB / 4.68 TiB free] Total: 4 [8.59 TiB] / in use: 4 [8.59 TiB] / in no VG: 0 [0 ] #
Created attachment 1103336 [details] Log from '/usr/sbin/lvmetad -f -l all'
The following pre script solves thee problem nicely: %pre /bin/sed -i -e 's/use_lvmetad\s*=\s*1/use_lvmetad = 0/' /etc/lvm/lvm.conf /bin/systemctl stop lvm2-lvmetad.socket /bin/systemctl stop lvm2-lvmetad.service %end
*** Bug 1285030 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1226244 ***