Bug 526597 - Changing system time, leaves system unbootable
Summary: Changing system time, leaves system unbootable
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: rawhide
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Blocker, F12FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2009-09-30 23:35 UTC by Eric Springer
Modified: 2009-10-19 18:46 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-19 18:46:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
It continually asking for password, each time a key is pressed. (193.75 KB, image/jpeg)
2009-09-30 23:35 UTC, Eric Springer
no flags Details

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.


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