When I run fsck I get a message about 'the hardware clock'. (full transcript is below)
When I look at the clock (on the desk-top, lwr right) I see the correct time - corrected for daylight saving.
Are there two clocks? What's the drum? Give me the good oil!
Leslie
(transcript of command etc follows).
# fsck -n /dev/sda1
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
Superblock last mount time is in the future. (by less than a day, probably due to the hardware clock being incorrectly set).
Superblock last write time is in the future. (by less than a day, probably due to the hardware clock being incorrectly set)
(end of screen dump)
command-line - fsck - clock discrepancy
Hi Leslie.
You probably tried to do your disk check soon after boot? Wait a minute or two until the
time sync that occurs automatically at boot is finished, or run Psync manually and wait
til it's done.
In any case, fsck is giving you an info rather than a warning. Nothing catastrophic or
apocalyptic is going to happen if you proceed.
IHTH.
You probably tried to do your disk check soon after boot? Wait a minute or two until the
time sync that occurs automatically at boot is finished, or run Psync manually and wait
til it's done.
In any case, fsck is giving you an info rather than a warning. Nothing catastrophic or
apocalyptic is going to happen if you proceed.
IHTH.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
command-line - fsck - clock discrepancy (solved)
Hi Musher!
Yes, correct - I re-booted and ran fsck on storage device sda1 immediately after booting.
Now, hours later, ran the file system consistency check (fsck) and got NO error report. I find the command line (or bash, as many people call it) very useful but there are some "gotcha's" I must learn. For example, the parameter list in the fsck command varies between fsck and e2sfck. It is necessary to understand the consequences of these differences.
Thank you! - Leslie
Yes, correct - I re-booted and ran fsck on storage device sda1 immediately after booting.
Now, hours later, ran the file system consistency check (fsck) and got NO error report. I find the command line (or bash, as many people call it) very useful but there are some "gotcha's" I must learn. For example, the parameter list in the fsck command varies between fsck and e2sfck. It is necessary to understand the consequences of these differences.
Thank you! - Leslie
Hello Leslie.
As I mentioned in a related thread, fsck and e2fsck are different utilities from different
developers. Use one OR the other, never use both.
As a note, never use an fsck utility or similar on a Solid State Drive (SSD) or a
USB drive. They have their own utility for this function incorporated on the drive.
As for me, I always use e2fsck. I wrote a script 5-6 years back that uses it. It checks
all ext-something file systems and produces a report on screen as it does.
It's called < automverif-11b.pet >, and it's here.
I also provided a companion script using tune2fs (7th post down that page). This utility
sets, with your input, after how many mounts the partition should be checked.
e3fsck looks for this info.
I hope installing and using those two scripts on your Puppy will help you solve
your fsck problems.
Any questions, please let me know.
Bye for now.
As I mentioned in a related thread, fsck and e2fsck are different utilities from different
developers. Use one OR the other, never use both.
As a note, never use an fsck utility or similar on a Solid State Drive (SSD) or a
USB drive. They have their own utility for this function incorporated on the drive.
As for me, I always use e2fsck. I wrote a script 5-6 years back that uses it. It checks
all ext-something file systems and produces a report on screen as it does.
It's called < automverif-11b.pet >, and it's here.
I also provided a companion script using tune2fs (7th post down that page). This utility
sets, with your input, after how many mounts the partition should be checked.
e3fsck looks for this info.
I hope installing and using those two scripts on your Puppy will help you solve
your fsck problems.
Any questions, please let me know.
Bye for now.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)