Bug 636628 - root password not accepted to run fsck after system crash
Summary: root password not accepted to run fsck after system crash
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 15
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 644057 651254 (view as bug list)
Depends On:
Blocks: 702814
TreeView+ depends on / blocked
 
Reported: 2010-09-22 18:31 UTC by Afom T. Michael
Modified: 2013-01-10 06:14 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 702814 (view as bug list)
Environment:
Last Closed: 2012-08-07 20:17:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Legacy) 46774 0 None None None Never

Description Afom T. Michael 2010-09-22 18:31:57 UTC
Description of problem:
When a Lenovo T500 is re-booted after it crashed (battery run out is one reason), the machine hangs because its root filesystem needs to go through fsck (BZ 558851). When "rhgb quite" is removed from grub, it reports: 

/dev/mapper/vg0-root contains a file system with errors, check forced.
/dev/mapper/vg0-root: inodes that were part of a corrupted orphan linked list found.
/dev/mapper/vg0-root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY   [FAILED]
...
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
*** Warning -- SELinux is active
*** Disabling security enforcement for system recovery.
*** Run 'setenforce 1' to reenable
Give root password for maintenance
(or type Control-D to continue):

At this stage, at every second key stroke, it reports "Login incorrect." and repeats the above "Give root password...". 

The only way I have been able to recover from this is to reboot the machine with a Live image and run "fsck.ext4 /dev/mapper/vg0-root" and reboot.

Version-Release number of selected component (if applicable):
Fedora 13

How reproducible:
All the time on my laptop

Steps to Reproduce:
1. Install Fedora 13 on T500
2. Boot to Fedora 13
3. Press power button
4. watch get to the above state
  
Actual results:


Expected results:
To not get to above state. At the worst, to be able to run fsck

Additional info:

Comment 1 Bill Nottingham 2010-11-29 19:49:47 UTC
*** Bug 651254 has been marked as a duplicate of this bug. ***

Comment 2 Bill Nottingham 2010-11-29 19:49:53 UTC
*** Bug 644057 has been marked as a duplicate of this bug. ***

Comment 3 Sandro Bonazzola 2010-12-02 15:10:08 UTC
Try adding rd_NO_PLYMOUTH in your kernel line and retry.

Comment 4 Mack Stanley 2010-12-03 06:37:33 UTC
Yes! That fixes the problem for me.  

I filed the duplicate bug concerning this problem with an ext2 filesystem.  (Sorry about that.  I did search but obviously wasn't smart enough about it.)

With rd_NO_PLYMOUTH I don't get a prompt for the password for the root filesystem encryption, but that's a minor matter relative to the problem itself.

Unless I hear there's reason not to, I'll post this as a workaround to Fedora Forum for other end users.

Thanks very much!

Comment 7 Bug Zapper 2011-05-31 12:50:40 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Sandro Bonazzola 2011-06-01 06:19:06 UTC
Still present in Fedora 14 and Fedora 15.

Comment 9 Geeky 2011-06-04 13:02:40 UTC
Also present in RHEL6.1 ! paid, licensed, commercial support :(

Comment 10 Bug Zapper 2011-06-28 12:28:56 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 12 Bug Zapper 2011-06-29 12:36:33 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 13 Tim Jackson 2011-07-06 06:10:58 UTC
Changing version to Fedora 15 as per comment #8

Comment 14 Robert Story 2011-08-15 14:45:45 UTC
I ran into this today with F14.. I always remove 'rhgb quiet' from grub, and I tried rebooting adding 's' to get to single user mode. I was shocked to find that I was still getting the password prompt in single-user mode!

The really interesting thing I noticed was that keys alternated between the repeating password prompt and being sent to the shell. That is, if I typed "llss<CR><CR>", it would run ls and show me the directory contents.

What exactly does rd_NO_PLYMOUTH do? Is there any harm in leaving it in my grub line all the time?

Comment 15 David Tonhofer 2011-09-09 13:45:53 UTC
Observed with RHEL 6.1

-> Boot in single user mode to fix some filesystem trouble
-> Impossible to enter password, only the return key seems to do anything

-> Boot with rd_NO_PLYMOUTH on the command line
-> Password can be entered 

This being a problem with the console input, maybe the title of the bug should be changed?

Comment 16 Fedora End Of Life 2012-08-07 20:17:13 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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