[resolved?] Don't Update!

[dibl]

Re: Don't Update!

it would block any posts mentioning 'Koala' until 22 October, thereby keeping us safe from temptation...

The filesystem timestamp problem is an upstream Debian issue, related to udev. For me the difference is 4 hours. No fix available yet.

[kubicle]

Re: Don't Update!

it would block any posts mentioning 'Koala' until 22 October, thereby keeping us safe from temptation...

The filesystem timestamp problem is an upstream Debian issue, related to udev. For me the difference is 4 hours. No fix available yet.

Something says this is an UTC vs. local time issue, which would explain the (different) time offsets.

As a temporary solution, you could try switching to UTC time if you're using local time hwclock, the setting can be found in /etc/default/rcS. (Then try booting your machine...and adjust the time if necessary).

The only drawback with using UTC time is dual booting with windows, which uses localtime, so you'll likely have to adjust your clock when switching OS.

[personman]

Re: Don't Update!

This reminds me of "Jaws!"...

OK, whose going to be the first to dip their toe into the digital pool tomorrow night?

You know, I knew there was a reason I was hearing that ominous John Williams bass score while the updates were installing, but I shrugged it off...

I have about 4 machines running Karmic, so I'll keep tracking updates on a couple of them.

I seem to be back to a functional system thanks to updates, networking is working again, though I still get some strange messages on boot.

I'll post when everything seems to be resolved, and maybe someone could update a test box to confirm, and let us know how it goes.

mando_hacker: My sh link is intact, and my updates are current and configured. Most symptoms seem to point to problems with the initialization scripts, as far as I can tell.

-Andy

[dibl]

Re: Don't Update!

Something says this is an UTC vs. local time issue, which would explain the (different) time offsets.

sidux devs say it is a problem of system clock failing to sync with hardware clock during early boot phase (race between udev rule triggering hwclock and non-event based boot system - sysvinit/sysv-rc). Part of the "new boot experience", I guess -- but this part isn't working well so far.

[personman]

Re: Don't Update!

I've installed the ntp daemon as sort of a work-around to try to keep the clock somewhere close to synced.

Interest thing is, according to the bios, the hardware clock has been accurate the whole time. I suspect it might still be related to initialization script changes...like it's interpreting the time incorrectly. hopefully some updates today will correct things.

[dibl]

Re: Don't Update!

This would appear to be competent guidance to handle the current Karmic breakage:

http://ubuntuforums.org/showthread.php?t=1267657

I have not tested it on my system -- I'm not dist-upgrading until I see signs of stability in the forums.

[GreyGeek]

Re: Don't Update!

The shark is gone, the water is safe and I have all my toes intact!

I chose the recovery mode of my latest kernel and picked the "root with networking".

I did "apt-get -f install" repeatedly until it did nothing.

Then I did
apt-get update
apt-get upgrade
apt-get dist-upgrade

I did NOT do
apt-get install kdm kubuntu-desktop

I get some wild udev errors early in the boot, and they don't leave any log messages, but my system seems to be working OK.

Oh, maybe it's me, but the boot up is REALLY fast. 15 seconds to the KDE4 login screen.

[olembe]

Re: Don't Update!

I also see all those udev messages flash past during boot-up and can't find them in the logs. Isn't that weird? I thought Linux logged everything?

[GreyGeek]

Re: Don't Update!

Perhaps those messages are before write access to the HD?

[GreyGeek]

Re: Don't Update!

....
I have not tested it on my system -- I'm not dist-upgrading until I see signs of stability in the forums.

As my flight instructor used to say, "There are OLD pilots, there are BOLD pilots, but there are NO OLD, BOLD pilots!"

[dibl]

Re: Don't Update!

"There are OLD pilots, there are BOLD pilots, but there are NO OLD, BOLD pilots!"

Right he is! He probably also informed you about the two most useless statistics in the world, when you're flying:

1. The altitude above you.
2. The length of runway behind you.




OK, regarding the udev / "filesystem superblock in future" issue:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540575

[kubicle]

Re: Don't Update!

OK, regarding the udev / "filesystem superblock in future" issue:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540575

Reading the comments, seems switching to UTC clock should work (until properly fixed)...the reason I suggested it was that I have clock set to UTC and didn't suffer from the issue.

[GreyGeek]

Re: Don't Update!

solution seems to be to change the order of init scripts (set clock _before_ doing fsck

mmm... Not being THAT BOLD of a pilot, I'm not going to be re-sequencing file names in /etc/init.d or /etc/rcn.d

[personman]

Re: Don't Update!

Should I go ahead and mark this solved? or wait till the errors clear up just in case?

[dibl]

Re: Don't Update!

Sure. I'm not sure "solved" is the appropriate term -- perhaps "OBE" (Overtaken By Events) or something. Hopefully most of the Kubuntu breakage issues will be resolved by later package versions during the balance of the Karmic development cycle. I'm not sure the fsck/hwclk issue is going to be fixed near term, since that is from Debian.