Michael The interesting thing is that when I set the date back to to years prior to 2010 the problem does not show up. I even tried 1970 and it did not happen.
Regards Bill On Wed, 30 Oct 2013 12:59:05 -0400, Michael Duvall <michael.duv...@ccur.com> wrote: >Bill, > >My initial thought is that the CMOS battery is failing. Afterall, the >Lenovo T61p dates back to 2007. > >If there were a problem with fsck, I would think that it would be seen >by lots of people on lots of different platforms. > >Regards, >-- >Michael Duvall >Systems Analyst, Real-Time >michael.duv...@ccur.com > >(954) 973-5395 direct >(954) 531-4538 mobile > >CONCURRENT | 2881 Gateway Drive | Pompano Beach, FL 33069 | >www.real-time.ccur.com > >-----Original Message----- >From: Bill Askew <r.w.as...@boeing.com> >To: SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV ><SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV> >Cc: Bill Askew <r.w.as...@boeing.com> >Subject: Superblock last mount time (<date> now <date>) is in the >future. >Date: Wed, 30 Oct 2013 12:45:50 -0400 > > >Hi everyone > >I am running SL6.2 64bit on a Lenovo T61p. We don't always set the date >to the current date and sometimes the date is in the past. If the year is >2010 - 2012 I get the following message at boot up. > >Checking filesystem >/dev/mapper/VolGroup-lv_root: Superblock last mount time (Wed Oct 30 >12:11:30 2013, > now = Sat Oct 30 06:27:50 2010) is in the future. > >/dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. > > [FAILED] >*** An error occurred during the file system check. >*** Dropping you to shell; the system will reboot >*** when you leave the shell. >Give root password for maintenance >(or type Control-D to continue): > >This looks to me like a bug in fsck. I can work around the boot up >failure by modifying rc.sysinit to run fsck with the –y option. >Alternatively I have created /fsckoptions with –y (this gets removed by >rc.sysinit after boot up). > >I would appreciate any other suggestions on how to work around this >problem. > >Thanks >