kilimanjaro Posted October 25, 2003 Report Share Posted October 25, 2003 I was trying to rebuild my urpmi data base and I got the following error messages. error: rpmdb: damaged header instance #682 retrieved, skipping. error: rpmdb: damaged header instance #694 retrieved, skipping. I ran rebuilddb again and I didn't get the error agian. Does anybody understand this? Link to comment Share on other sites More sharing options...
Cannonfodder Posted October 25, 2003 Report Share Posted October 25, 2003 I was trying to rebuild my urpmi data base and I got the following error messages. error: rpmdb: damaged header instance #682 retrieved, skipping. error: rpmdb: damaged header instance #694 retrieved, skipping. I ran rebuilddb again and I didn't get the error agian. Does anybody understand this? What were the exact commands you typed in? Did you follow the Faq? http://www.mandrakeusers.org/viewtopic.php?t=4937 Link to comment Share on other sites More sharing options...
kilimanjaro Posted October 26, 2003 Author Report Share Posted October 26, 2003 I typed <rm -f /var/lib/rpm/__db* && rpm --rebuilddb> Link to comment Share on other sites More sharing options...
Cannonfodder Posted October 26, 2003 Report Share Posted October 26, 2003 Try doing an advance google search for "damaged header instance" and rpm urpmi There's a bunch of entries on this topic. Most seem to have something to do with mismatches between rpm and db3. One mention of doing a rpm --initdb Let us know what you find out :) Link to comment Share on other sites More sharing options...
kilimanjaro Posted October 26, 2003 Author Report Share Posted October 26, 2003 I found this on http://www-level3.experts-exchange.com/Ope...Q_20659517.html If Packages really is toast, you've got your work cut out for you:-). First try to rebuild/save the db like this: mv /var/lib/rpm /var/lib/rpm.sav mkdir /var/lib/rpm rpm --initdb cp /var/lib/rpm.sav/Packages /var/lib/rpm rpm --rebuilddb With luck, your db is sane after this. Without luck, you need to get a listing of what is installed, and "fake" the installation for each and every package into a clean (se above less the copy of Package file) database. This might sound bad, but it can be ... eased a bit. In /var/log/rpmpkgs* you have listings of all rpm packages installed. These are generated by a cron.weekly script by default IIRC. Mount the first install CD, cd to the RPMS directory, and run something like for i in $(cat /var/log/rpmpkgs) do j=${i}* if [ -f $j ] then rpm -ivh --justdb --nodeps $j fi done and repeat with the rest of the installation CDs... and any update repository (or just DL all the updates... again:-). When done, verify that the rpmpkgs logfile and rpm -qa seem to be the same. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now