Bug 426603 - UNEXPECTED INCONSISTENCY
UNEXPECTED INCONSISTENCY
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: fedora-release (Show other bugs)
8
x86_64 Linux
low Severity urgent
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-22 17:04 EST by Ruben Ho
Modified: 2013-01-09 20:46 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-02 17:20:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ruben Ho 2007-12-22 17:04:32 EST
Description of problem:
Cannot reboot after installation and package updates

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

How reproducible:
Twice. First time - server reboots continuosly.

Steps to Reproduce:
1. Install Fedora 8 from LIVE CD - Install to Harddisk
2. Download all 136 updates
3. Install all updates
4. Reboot  

Actual results:
Checking filesystems [FAILED]
Fedora-8-Live-x8: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
*** Warning -- SELinux is active
*** Disablind security enforcement for system recovery.
*** Run 'setenforce 1' to reenable.
Give root password for maintenance
(or type Control-D to continue):

Expected results:

Fedora boots up normally

Additional info:
Comment 1 Ruben Ho 2007-12-23 05:45:31 EST
*** POST Bug report ***
1. tried to do a :

touch /forcefsck at shell but read-only system.

2. did a manual fsck and system reports fixed and requested a reboot.

3. Server with Fedora 8 manage to reboot. Now checking power management options
and filesystem.

Question : Will the problem occur? As we took more than 3 hours to update all
the core packages. Reinstallation will take time and resources.

Thanks in advance.
Comment 2 Jesse Keating 2008-01-02 17:20:39 EST
This was probably just a coincidence in timing, and not anything to do with the
updates.

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