Bug 526597

Summary: Changing system time, leaves system unbootable
Product: [Fedora] Fedora Reporter: Eric Springer <erikina>
Component: plymouthAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: dougsland, fedora, gansalmon, itamar, kernel-maint, krh, mclasen, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-19 18:46:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 473303    
Attachments:
Description Flags
It continually asking for password, each time a key is pressed. none

Description Eric Springer 2009-09-30 23:35:30 UTC 
Created attachment 363263 [details]
It continually asking for password, each time a key is pressed.

Description of problem:

After my system clock was out from using another OS (10 hours fast to be more precise), NTP brought it back to the proper time. Then I incidentally rebooted my system, finding it was unbootable.


When booting, it bitches about the last file mount time being in the future, and wants to fsck my disk. It then asks for my root password to do this fisking, But every time I hit a single key, it asks for my password again .. not letting me enter one.

Apologies if this is posted for the wrong component. 


How reproducible:

100%, I tried setting the system clock back again and same problem.



Additional info:
http://www.smolts.org/client/show/pub_8a95a6e0-500c-460e-b53e-7962b6829a00
Comment 1 Eric Springer 2009-09-30 23:42:13 UTC 
Looks like it may be a KMS problem. Adding nomodeset to the grub boot line allows me to enter my root password.
Comment 2 Chuck Ebbert 2009-10-05 23:22:16 UTC 
Possibly a plymouth bug, reassigning.
Comment 3 Ray Strode [halfline] 2009-10-19 18:46:22 UTC 
This should be fixed now.