Ubuntu
mountall package

Disk error when system time is in past

Bug #988369 reported by LaunchpadUser
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Triaged
Medium
Oliver Grawert

Bug Description

$ lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10

The cause for an error

"Errors while checking disk drive for /MyPartition"

can also be an earlier system time! It took a long time to find this out: when booting the kernel with noplymouth and without "quiet splash", I found the reason for the "disk errors":

"Der Zeitpunkt des letzten Schreibens von SuperBlock (Wed Apr 25 13:27:46 2012, jetzt: Mon Apr 23 09:46:10 2012) liegt in der Zukunft."

which is something like "superblock last write time is in the future". See Bug #268808 for a similar description.

As the normal Ubuntu boot screen just shows a message "disk error", and all the fixing like fsck doesn't help, it would be much clearer to have a message like "system time before max file system time! (Check system time in BIOS!)".

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/988369/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Daniel Letzeisen (dtl131) wrote :

I'm marking this as a plymouth bug, since that is what is producing the vague (and alarmist) error message.

affects: ubuntu → plymouth (Ubuntu)
Revision history for this message
Steve Langasek (vorlon) wrote :

Plymouth doesn't produce any messages, it just displays them. Reassigning to mountall which is responsible for the message.

mountall may or may not have enough information from fsck to be able to provide a better error message however. This needs looking into.

affects: plymouth (Ubuntu) → mountall (Ubuntu)
Changed in mountall (Ubuntu):
assignee: nobody → Oliver Grawert (ogra)
Revision history for this message
Steve Langasek (vorlon) wrote :

ogra, you're already familiar with this area due to the fixrtc work; do you know if mountall should be able to distinguish this error condition from others when checking the rootfs?

Steve Langasek (vorlon)
Changed in mountall (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.