Boot into emergency mode after switching datetime from UTC to LOCAL

[douglarek]

Hello guys,

I think i have got trouble with booting, all things happend as bellow:

1. when i enter my os(openSUSE 12.2 x86_64 Tumbelweed upgraded from 12.2 rc2 for a long time), I found my datetime was not very right, so I switched it from UTC to LOCAL and synced time with ntp.

2. then reboot as root

3. booting and booting util this:

.===================
doing fast boot

create device nodes with udev

welcome to emergency mode…

Give root passwd to login:

and i logined in it with root,but all was not useable. such as nerwork…

can anybody explain it?

Thanks and BR,

lingchax

[hcvv]

There is a Tumbleweed forum here.

[douglarek]

@hcvv

There is a Tumbleweed forum here.

hcvv,

yeah, I know there is a Tumbleweed forum here, but it is not related to os version, it is booting problem

[hcvv]

That is your conclusion.

1. In any case what was wrong with your time/date? Entire hours off, allways the same? RRnning of correct time slowly?

2. Setting the switch to “store either local time or UTC to the hardware clock at shutdown” should be set to UTC normaly ad set to Local when cross booting with Windows. You do not mention what you do and if you hade oy wrong and thus corrected it.

3. Using NTP will keep your time/date fine and works when the system is running. But there is no connection to the UTC/Local setting mentioned above.

At 2), I can add that there is a bug in 12.2 that means that when you set the switch to Local, it will look like if it is done, but it isn’t. There are several thread here and a blog from @jmcdaniels.

You did thus two, only remotely connected actions, but neither can create the problem you hve imho.
Did you look at dmesg or in the logs?

[robin_listas]

On 2012-09-27 19:36, hcvv wrote:
>
> That is your conclusion.

Yes, tumbleweed has different problems.

> At 2), I can add that there is a bug in 12.2 that means that when you
> set the switch to Local, it will look like if it is done, but it isn’t.
> There are several thread here and a blog from @jmcdaniels.

What is UTC or GMT Time & a possible issue with openSUSE 12.2 and its solution.

> You did thus two, only remotely connected actions, but neither can
> create the problem you hve imho.

Another one: mkinitrd. It might be necessary.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

[douglarek]

@hcvv

That is your conclusion.

1. In any case what was wrong with your time/date? Entire hours off, allways the same? RRnning of correct time slowly?

2. Setting the switch to “store either local time or UTC to the hardware clock at shutdown” should be set to UTC normaly ad set to Local when cross booting with Windows. You do not mention what you do and if you hade oy wrong and thus corrected it.

3. Using NTP will keep your time/date fine and works when the system is running. But there is no connection to the UTC/Local setting mentioned above.

At 2), I can add that there is a bug in 12.2 that means that when you set the switch to Local, it will look like if it is done, but it isn’t. There are several thread here and a blog from @jmcdaniels.

You did thus two, only remotely connected actions, but neither can create the problem you hve imho.
Did you look at dmesg or in the logs?

maybe i do not say it clearly, but the fact is when i switch it from LOCAL to UTC again, it is fine…so maybe it is a kernel bug in 3.4.x…maybe it is my personal trouble only.

Did anyone get the same problem?

[hcvv]

@douglarek

maybe i do not say it clearly, but the fact is when i switch it from LOCAL to UTC again, it is fine…so maybe it is a kernel bug in 3.4.x…maybe it is my personal trouble only.

Did anyone get the same problem?

Not much information from you. I showed you when to use storing the Local time instead of UTC. You did not explain if you cross boot with Windows or not.