This bug was filed automatically by anaconda.
Created attachment 323682 [details] Attached traceback automatically from anaconda.
What kind of installation were you doing? It sort of looks like an upgrade, but at the same time there's log messages about formatting /boot and swap but not /. Any extra information you can provide about what you did would be helpful.
I had an existing Fedora 9 installation with encrypted partitions (/ /home /boot and swap). I formatted everything except /home and encrypted them as usual. This is how I typically upgrade from one stable release to another. I guess the formatting went on without a problem and as soon as the installation started, the error occurred. Hope this helps. Let me know if you need any other information.
Created attachment 324617 [details] Attached traceback automatically from anaconda.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Created attachment 324714 [details] Attached traceback automatically from anaconda.
*** Bug 475812 has been marked as a duplicate of this bug. ***
*** Bug 493334 has been marked as a duplicate of this bug. ***
*** Bug 494259 has been marked as a duplicate of this bug. ***
*** Bug 494295 has been marked as a duplicate of this bug. ***
To anyone who is able to reproduce this problem - when you hit the exception, can you press ctrl-alt-f2 and paste the output of mount into this bug report? It's almost like we're trying to read the __db* files from a previously installed system but I don't see how that should be happening here.
I is probably not the same issue - but the rpmdb will not open too: with fedora/test/11-Preview at the end of an automatical kickstart install: %post rpm -q glibc >/tmp/x.x 2>&1 %end the following output appears: error: cannot open Packages index using db3 - No such file or directory (2) error: cannot open Packages database in /var/lib/rpm error: cannot open Packages database in /var/lib/rpm package glibc is not installed After reboot there are no problems to connect to the rpm db!
Created attachment 345207 [details] Attached traceback automatically from anaconda.
Given that we've been unable to ever reproduce this problem and can't get a reliable reproducer from a reporter, I'm going to have to close this as CANTFIX. If someone can reliably reproduce it AND explain their setup in detail, feel free to reopen this bug. Thanks.
The issue seem to be that you are not re-formating /var and anaconda is having a problem with an rpmdb file that still exists in /var/lib (I think). If you get this error and type ctl-alt-f1, you'll see that anaconda as kicked up an error about this file. I would think that if you did an F10 install, updated all the F10 rpms, then tried to do an update to F11 without formating /var, you'd get the same error. I can't duplicate this at this time, but I can tell you that I ran into this error 3 times trying different DVDs in case there was an error on the DVD. Yes, I know about the DVD verification and such. When I told the F11 update to format /var, the problem went away. Hope this helps.
*** Bug 524236 has been marked as a duplicate of this bug. ***
*** Bug 487983 has been marked as a duplicate of this bug. ***
*** Bug 574049 has been marked as a duplicate of this bug. ***
*** Bug 601023 has been marked as a duplicate of this bug. ***
I also get this same error when trying to upgrade/reinstall a F13 installation (same hardware as before). The only thing unique/different about the hardware in this system is 3 pata drives and 2 sata drives. installation is going to the first pata drive. output from alt-f1: Running anaconda 13.42, the Fedora system installer - please wait. 20:57:27 Starting graphical installation. rpmdb: Thread/process 424/3079304896 failed. Thread died in Berkley DB library error: db3 error(-30974) from devenv-failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages databae in /mnt/sysimage/var/lib/rpm why is a bug like this "unfixable"?
When i removed the extra drives (LVM storage not part of hte linux installation/upgrade - leaving just 2 pata drives), the installation and upgrade process when through without a problem. Previously, i had 2 additional sata and 1 additional pata drive active in the system. hope this helps ...
*** Bug 626260 has been marked as a duplicate of this bug. ***
I experienced this error repeatedly when trying to install the f16 alpha on a system wth an existing LVM (debian+fedora) where I tried replacing the fedora instance. With the installer from f16 Beta RC1 this now seems to work fine.