Bug 1678 - After fsck fails the boot continues as if nothing had happened
Summary: After fsck fails the boot continues as if nothing had happened
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 6.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-03-22 20:44 UTC by Pekka Pietikäinen
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-03-22 21:10:11 UTC


Attachments (Terms of Use)

Description Pekka Pietikäinen 1999-03-22 20:44:35 UTC
If fsck fails for some reason, the boot process continues
as normal, getty appears etc., but the system is still
in a single-userlike mode, partitions aren't mounted etc.

Comment 1 Cristian Gafton 1999-03-22 20:50:59 UTC
Bill, sholdn't this be already fixed ?

Comment 2 Bill Nottingham 1999-03-22 20:52:59 UTC
what version of initscripts are you running?

Comment 3 Bill Nottingham 1999-03-22 20:54:59 UTC
what version of initscripts are you running?

Comment 4 Pekka Pietikäinen 1999-03-22 21:05:59 UTC
3.96-2 from the 5.9 cd image on gribble (not 100% sure about the box I
saw the problem on, but it was installed from the same CD as this box,
so I suppose...)

Comment 5 Bill Nottingham 1999-03-22 21:10:59 UTC
upgrade to 3.96-4 or later, either on ftp.redhat.com/starbuck,
rawhide.redhat.com, or, if you need it, I'll mail it to you. ;)
This should fix the problem.

Comment 6 Pekka Pietikäinen 1999-03-22 21:11:59 UTC
3.96-2 from the 5.9 cd image on gribble (not 100% sure about the box I
saw the problem on, but it was installed from the same CD as this box,
so I suppose...)

Comment 7 Pekka Pietikäinen 1999-03-22 21:17:59 UTC
3.96-2 from the 5.9 cd image on gribble (not 100% sure about the box I
saw the problem on, but it was installed from the same CD as this box,
so I suppose...)


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