Bug 153032 – progress of fsck on boot not available in rhgb

Bug 153032 - progress of fsck on boot not available in rhgb

Summary:	progress of fsck on boot not available in rhgb

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	rhgb (Show other bugs)
Sub Component:
Version:	2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ray Strode [halfline]
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-31 21:23 EST by Tim Bingham
Modified:	2008-08-02 19:40 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-10-25 16:01:25 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Tim Bingham 2005-03-31 21:23:35 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040808 Firefox/0.9.3

Description of problem:
progress of fsck on boot not available in rhgb

If fsck runs during boot (e.g. "dev/hdb1 has gone 193 days without being checked, check forced.") this can take a long time. Unfortunately the fact that fsck is running is not visible in rhgb (even if you click "show details"). This makes it appear as if the boot process has hung.


Version-Release number of selected component (if applicable):
rhgb-0.11.2-6

How reproducible:
Always

Steps to Reproduce:
1. reboot with filesystem that needs to have fsck run
2. wait for rhgb screen
3. click "show details."


  

Actual Results:  no details are available - system appears to be hung

Expected Results:  progress of fsck command displayed


Additional info:

Comment 1 Matthew Miller 2005-04-26 11:42:13 EDT

Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 2 John Thacker 2006-10-25 16:01:25 EDT

Closed per above message and lack of response.  Note that FC2 is not even
supported by Fedora Legacy currently.

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