* -re0906.1 Got this traceback during an automated install test. There was no lvm in this install. The previous install did not have lvm either (although it did have root on /dev/md0 raid1). The machine had run an lvm case earlier that day, but afaict it had gone through about 9 successful installs of the same tree before it hit this traceback. Will attach details. Traceback (most recent call last): File "/usr/bin/anaconda", line 694, in ? intf.run(id, dispatch, configFileData) File "/usr/lib/anaconda/text.py", line 402, in run (step, args) = dispatch.currentStep() File "/usr/lib/anaconda/dispatch.py", line 251, in currentStep self.gotoNext() File "/usr/lib/anaconda/dispatch.py", line 150, in gotoNext self.moveStep() File "/usr/lib/anaconda/dispatch.py", line 215, in moveStep rc = apply(func, self.bindArgs(args)) File "/usr/lib/anaconda/partitioning.py", line 57, in partitionObjectsInitialize partitions.setFromDisk(diskset) File "/usr/lib/anaconda/partitions.py", line 184, in setFromDisk lvm.vgscan() File "/usr/lib/anaconda/lvm.py", line 38, in vgscan raise SystemError, "vgscan failed" SystemError: vgscan failed Local variables in innermost frame: rc: 11
Created attachment 75605 [details] ks.cfg from failed install
Created attachment 75606 [details] full traceback
Is this related to bug#73112 ?
Yes. There are still some cases where vgscan will segfault due to incomplete data being left on the drives. I have a newer lvm package that ought to fix it.
lvm tools in current tree should help this problem.
Well, haven't hit this in a long time. Closing.
Time tracking values updated