by less than a day probably due to the hardware clock being incorrectly set

Posted 09-28-2012 at 01:25 AM by ted_chou12

When I run e2fsck/fsck, I find that the following message appears:

Code:

blah~~~~~~~~~~~~~~~~~~~~~~~~~
by less than a day probably due to the hardware clock being incorrectly set)
blah~~~~~~~~~~~~~~~~~~~~~~~~~

If you run tune2fs:

Code:

ted:$ tune2fs -l /dev/sda1
tune2fs 1.41.14 (22-Dec-2010)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          65da4171-080d-4fd4-a967-7e0792513aad
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype n
eeds_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              244320
Block count:              975940
Reserved block count:     48797
Free blocks:              89342
Free inodes:              63407
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      238
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8144
Inode blocks per group:   509
Filesystem created:       Wed Jan  1 08:14:57 2003
Last mount time:          Fri Sep 28 21:10:13 2012
Last write time:          Fri Sep 28 14:10:13 2012
Mount count:              8
Maximum mount count:      32
Last checked:             Fri Sep 28 03:50:57 2012
Check interval:           15552000 (6 months)
Next check after:         Wed Mar 27 03:50:57 2013
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
First orphan inode:       158182
Default directory hash:   half_md4
Directory Hash Seed:      3947b720-0cab-44d9-b48e-53db41bedbd0
Journal backup:           inode blocks

You will most likely find last mount time is indeed in a future time. And the key is by less than a day. This gives you a clue that the hwclock is probably set to a different timezone. Thus you probably have to check if your OS (linux) time and your hardware time are in different time sets. One is probably in localtime and the other in UTC, the only thing you need to do is add UTC to your /etc/hardwareclock file.
Ted

Posted in Uncategorized

Views 9161 Comments 1

« Prev Main Next »

Total Comments 1

Comments

reload sound card
fuser -k /dev/dsp

Posted 09-28-2012 at 03:30 AM by ted_chou12