Bug 14500 - /1 not cleanly unmounted, check forced
Summary: /1 not cleanly unmounted, check forced
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
high
high
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard: Winston rc1
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-23 23:02 UTC by Jan Carlson
Modified: 2014-03-17 02:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-07-31 14:44:42 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jan Carlson 2000-07-23 23:02:07 UTC
The root filesystem is fscked EVERY time Beta4 boots,
except possibly the first time.  Messages on screen
during boot:

  Checking root filesystem  
  /1 not cleanly unmounted, check forced.
  [followed by the fsck output]

This is a fresh "Custom" install of Beta4 with the default package set.
The behavior is the same when all optional packages are excluded.

To exclude other factors, I rebooted several times immediatly after
installing, without logging in.  Same results -  fsck each time.

RH6.2 agrees that this Beta4 root partition needs checking:

When RH6.2 is booted on this multiboot machine, 
it gives the SAME messages about the Beta4 root partition.
Here is the RH6.2 fstab entry:
  /dev/hda7  /betaroot  ext2  defaults,noauto  1 2  # Beta4 root
RH6.2 does the fsck only once after each Beta4 bootup.

Comment 1 Glen Foster 2000-07-30 19:33:53 UTC
This defect is considered MUST-FIX for Winston Release-Candidate #1
... I think this was fixed for beta-5, but I'm flagging it so we make sure.

Comment 2 Bill Nottingham 2000-07-31 14:44:40 UTC
Does beta5 work for you?  It should...

Comment 3 Jan Carlson 2000-08-02 03:59:38 UTC
This bug does appear to be fixed in Beta 5!
Jan


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