Bug 51004 - On 1st reboot RedHat 7.2 beta 3 reports root filesystem not cleanly unmounted, fsck forced.
On 1st reboot RedHat 7.2 beta 3 reports root filesystem not cleanly unmounted...
Status: CLOSED DUPLICATE of bug 51208
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-06 10:16 EDT by Bryan Leopard
Modified: 2007-04-18 12:35 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-09 17:19:16 EDT
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 Bryan Leopard 2001-08-06 10:16:02 EDT
OS: RedHat 7.2 2.96-94 (beta 3) Roswell
Kernel: 2.4.6-3.1smp
Boot controller: ROC

After completing the installation & rebooting the server the OS reports 
that the root system was not cleanly unmounted. It then forces fsck to 
clean the fs.

The root fs should be properly unmounted prior to rebooting the system.
Comment 1 Glen Foster 2001-08-06 18:29:08 EDT
This defect is considered SHOULD-FIX for Fairfax.
Comment 2 Matt Wilson 2001-08-06 18:49:57 EDT
is this reproducible?
Comment 3 Bryan Leopard 2001-08-09 10:07:34 EDT
Yes, this happens on every install with two seperate engineers and two seperate 
systems.
Comment 4 Matt Wilson 2001-08-09 10:46:49 EDT
Which ROC do these systems have?
Comment 5 Bryan Leopard 2001-08-09 14:06:07 EDT
Go look in the system in your lab.
Comment 6 Bryan Leopard 2001-08-09 17:14:36 EDT
This also happens on a qlogic card, so it is not hardware related.
Comment 7 Matt Wilson 2001-08-09 17:18:58 EDT
what package set are you installing?  Everything?
Comment 8 Bill Nottingham 2001-08-23 22:27:29 EDT

*** This bug has been marked as a duplicate of 51208 ***

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