[Mageia-discuss] New kernel cant boot and it killed MCC update

KevinO kevin at kevino.org
Fri Aug 24 21:24:04 CEST 2012


On 08/24/2012 11:21 AM, Jim Whitby wrote:
> On 08/24/2012 06:45 AM, Marc Paré wrote:
>> Yikes! I just did the update, but my screen froze, so, I rebooted and could not
>> boot. Something about "Startign wait for Plymouth boot screen to quit".
>>
>> So I rebooted into the previous kernel 3.3.6 and tried to do updates, but now
>> my MCC updates is munched! It says "couldn't open RPM DB() AT
>> USR/LIB/PERL5/VENDOR". --
>>
>> I tried "rpm --rebuilddb" in Konsole but it says:
>>
>> erreur: rpmdb: Thread/process 25894/139895115867904 failed: Thread died in
>> Berkeley DB library
>> erreur: erreur db4(-30974) de dbenv->failchk: DB_RUNRECOVERY: Fatal error, run
>> database recovery
>> erreur: ne peut ouvrir l'index Packages en utilisant db4 -  (-30974)
>>
>>
>> Any ideas on how to fixed this?
>>
>> Also, when I boot into safe mode and I do Drakconf, it says to update task-x11
>> and the system offers to download it; but when I try to do this it doesn't work.
>>
>> Cheers,
>>
>> Marc
>>
>>
> In English mine says:
> error: rpmdb: Thread/process 7815/140102385239808 failed: Thread died in Berkeley
> DB library
> error: db4 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run
> database recovery
> error: cannot open Packages index using db4 -  (-30974)
> 
> 
> 
I fixed the second problem by executing (as root):

rm -f /var/lib/rpm/__db*
rpm --rebuilddb

This allowed urpmi and the graphical package management applications to work again.

I am running the 3.3.6 kernel to make the NVidia driver work, though.

-- 
KevinO


More information about the Mageia-discuss mailing list