This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 193003 - "rpmDb: PANIC: fatal region error detected; run recovery" on installation
"rpmDb: PANIC: fatal region error detected; run recovery" on installation
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-05-24 14:08 EDT by Sarah Prelutsky
Modified: 2015-01-04 17:27 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-24 18:05:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Dmesg (18.67 KB, text/plain)
2006-05-24 14:08 EDT, Sarah Prelutsky
no flags Details

  None (edit)
Description Sarah Prelutsky 2006-05-24 14:08:32 EDT
Description of problem:
"rpmDb: PANIC: fatal region error detected; run recovery" on installation

Version-Release number of selected component (if applicable):

How reproducible:

Every time

Steps to Reproduce:
1. Install system with 3ware-8506 raid card
Actual results:

When you install the system at somepoint during the rpm installation it scrolls
"rpmDB: PANIC: fatal region error detected, run recovery" with a 3ware 8506 raid
card. The system completes the install and reboots but the system does not boot
in init 5 or even seem to complete the first boot things like set ntp server and
user logins etc.

Expected results: reboot from install and see firstboot questions like the EULA,
and other configuration options to finalize the install

Additional info: I can install fc5 fine with out the 8506 card or use a
3ware-9550 and there is no error on install. it is using the 3w-xxxx module.
attached is my dmesg output.
Comment 1 Sarah Prelutsky 2006-05-24 14:08:32 EDT
Created attachment 129956 [details]
Comment 2 Dave Jones 2006-09-10 20:36:53 EDT
Installation problems like this are a pain, as we can't easily get an updated
driver onto the installation media.  Even if this bug is fixed in the 2.6.17
based update, it's really convoluted still to create an update.

The Fedora Unity project ( does respin ISOs of
FC5+updates every so often, maybe find the latest one they have to offer, and
give that a try ?
Comment 3 Dave Jones 2006-10-16 20:38:48 EDT
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.
Comment 4 Dave Jones 2006-11-24 18:05:28 EST
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.

Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.

If you can reproduce this bug after installing all the
current updates, please reopen this bug.

If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.

Thank you.

Note You need to log in before you can comment on or make changes to this bug.