Boot failure

RhnBlack · 02-07-2012, 11:24 PM

When I change the system time.. this happens

"dracut warning : e2fsck returned with 4
dracut warning : /dev/disk/..n some id.. superblodk last mount time ... 'sumtime'
an error occurred during the file check
droppinf yout to a shell, the system will try to mount the file system, when you leave the shell"

When I change the system time to present date..then it boots properly.
I guess the last mount point time is creating the problem.
But guys Wat if i change the time to sumwhere in future and again change it to present day ..
and how to avoid this time constraint??
thnx

H_TeXMeX_H · 02-08-2012, 03:45 AM

I know these is this kernel option that may prevent this:

Code:

  ┌──────────── Set system time from RTC on startup and resume ─────────────┐
  │ CONFIG_RTC_HCTOSYS:                                                     │  
  │                                                                         │  
  │ If you say yes here, the system time (wall clock) will be set using     │  
  │ the value read from a specified RTC device. This is useful to avoid     │  
  │ unnecessary fsck runs at boot time, and to network better.              │  
  │                                                                         │  
  │ Symbol: RTC_HCTOSYS [=y]                                                │  
  │ Type  : boolean                                                         │  
  │ Prompt: Set system time from RTC on startup and resume                  │  
  │   Defined at drivers/rtc/Kconfig:20                                     │  
  │   Depends on: RTC_CLASS [=y]                                            │  
  │   Location:                                                             │  
  │     -> Device Drivers                                                   │  
  │       -> Real Time Clock (RTC_CLASS [=y])                               │

RhnBlack · 02-08-2012, 05:11 AM

I'm using fedora 16.
And the funny thing is .. I just tried to test if it was really time that is playing around.
I changed my time to somewhere in dec 2012 and started the system. But now If i put today's date, its showing the same error.
And yeah off course "can u just give more details for eliminating this time constraint".
A huge thank u to u. I was just waiting some one to answer this..as u can see after hours there was no help.
thanx.

RockDoctor · 02-08-2012, 02:08 PM

I had this problem for a while. Not sure what fixed it, but I did run system-config-date from the GUI and selected Synchronize date and time over the network

RhnBlack · 02-08-2012, 09:20 PM

Well I'm also not sure what is the actual fix. But since I'v changed my date to sumwhere in future.. So my computer is running in future.
Actually I' posted the same issue in Fedora forum also.. but till now no one has answered. :-(

H_TeXMeX_H · 02-09-2012, 02:37 AM

I recommend using ntpd to keep the time synchronized. The fsck should only appear once if you change the time and don't have the kernel option enabled. The next boot everything will be normal.

RhnBlack · 02-09-2012, 03:01 AM

Ya i think ntdp would work but I'm sorry to say. This is a standalone system, I mean no network connection is provided because of the thing called "security"... :-(
any other methods.. plizz help

jschiwal · 02-09-2012, 03:27 AM

How old is the computer? Could the battery be dead?

If the time-last-checked of the file system is in the future, you could modify the value using the tune2fs program.

RhnBlack · 02-09-2012, 04:43 AM

Its a brand new PC, not even 2 months old.