Bug 53478 - booting fails due to filesystem check
booting fails due to filesystem check
Status: CLOSED CURRENTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: e2fsprogs (Show other bugs)
1.0
alpha Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-09-10 02:38 EDT by Need Real Name
Modified: 2007-04-18 12:36 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-12 06:53:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2001-09-10 02:38:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
After upgrading to Kernel 2.4.7-2.9 and upgrading all the necessary 
packages, the boot hangs at the filesystem check, explaining an 
inconsistancy in the superblock.  After going into single user, I can 
mount the filesystems in question, and they are functional.  After running 
e2fsck on them, it warns that the superblock could be damaged, and asks if 
I'd like to continue.  If I continue, it shows up clean, yet will never 
mark the disk as clean.

Version-Release number of selected component (if applicable):e2fsprogs-
1.23-1, e2fsprogs-devel-1.23-1


How reproducible:
Didn't try

Steps to Reproduce:
1.Install Redhat 7.1 for alpha on AlphaStation 500
2.Upgrade required packages for kernel update.
3. Upon reboot, system will hang at filesystem check
	

Additional info:
Comment 1 Florian La Roche 2003-08-12 06:53:06 EDT
Must be something in older scripts. For an older installation might be
circumvented by mounting the disk read-only before rebooting?

Should in any case be fixed in newer versions, closing the bug-report.

Florian La Roche

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