Bug#543375: last superblock write time in future occurring sometimes
Hello! Thank you for your help. I've reinstalled all the packages using your script, and the problem hasn't occured since then (I rebooted the machine 5 times). It seems it has been fixed. B. Regards, Tomasz Grzelak
Bug#543375: Info received (Bug not solved)
2009/10/21 Gabriele Giacone losga...@libero.it Ok, solved. My boot/shutdown sequences were wrong. I reinstalled every package that owns a script under /etc/init.d. Not a simple reinstall. Before each reinstall, I did a update-rc.d -f script remove because, correct me if I'm wrong, if rcN links already exist, installation won't correct them, unless specified in preinst/postinst scripts. Now, in util-linux.postinst, for hwclock.sh and hwclockfirst.sh, there's a -f remove before start and it's ok. Reinstalling initscripts and many other packages, doing this cleanup, sequence numbers have significantly changed. Under /etc/rc6.d, before after S01sendsigsS20sendsigs S01umountnfs.shS31umountnfs.sh S01umountfsS40umountfs S01umountrootS60umountroot S01rebootS90reboot After fixing the scripts above, system booted fine. Then I fixed all the remaining. Hello, would it be enough to just manually correct symlinks as described above without reinstalling anything? I wouldn't like to render my system unusable because of messing with those critical packages. Besides, aren't any changes required in other rcX.d - is rc6.d enough? And what did you exactly mean by Then I fixed all the remaining? If you have corrected the problem could you please describe step by step what should be done to fix this? B. Regards, Tomasz Grzelak
Bug#543375: Info received (Bug not solved)
2009/10/21 Gabriele Giacone losga...@libero.it I started to modify the above ones then I continued with all the other ones. My goal was to get the official sequence number. Steps? For each init.d script, remove current rcN links and reinstall the package it belongs. Use the following script. It let you choose among /etc/init.d scripts and the reinstallation of the package they belong. Package reinstall implies reconfigure? My system is a desktop, I didn't do complex reconfiguration. Compare before and after sequence numbers and you should see a lot of differences. --- for i in /etc/init.d/* do _file=$(basename $i) echo -e File $_file OK? \c read _answ [ $_answ != y ] continue ### find to see current sequence numbers find /etc/rc*|grep $_file ### removing current links update-rc.d -f $_file remove ### from file to package dpkg -S $i _pkg=$(dpkg -S $i|cut -d: -f1) ### reinstall it? echo -e Reinstall package $_pkg OK? \c read _answ [ $_answ != y ] continue apt-get -y --reinstall install $_pkg ### find to see new sequence numbers find /etc/rc*|grep $_file done --- Hello! Thank you very much for your description the script. Actions to take look much clearer now for me. I'll try to 'implement' them in next few days. I'll let you know how it goes. B. Regards, Tomasz Grzelak
Bug#543375: initscripts: last superblock write time in future
Tomasz Grzelak pisze: 2009/10/16 Mader, Alexander auma...@gmx.net mailto:auma...@gmx.net Tomasz Grzelak schrieb: what is the status of the case - am I the only one experiencing the problem still? Is there anyone affected by this even with the new version of util-linux 2.16.1-4? As mentioned in an earlier e-mail everything works fine since I edited the hwclock-udev-rule as decribed in another e-mail in this bug report. Hello, I am sorry, but I'm still affected by this problem. I have added the lines to the file, so now it contains: m...@daemon:~$ cat /lib/udev/rules.d/85-hwclock.rules # Reset the System Clock to UTC if the hardware clock from which it was # copied by the kernel was in localtime. KERNEL==rtc0, RUN+=/lib/udev/hwclock-set $root/$name KERNEL==rtc0, RUN+=/bin/touch /dev/rtc0-appeared KERNEL==rtc0, RUN+=logger.agent but it does not change anything for me. Immediatelly after I had removed [options] buggy_init_scripts = 1 from e2fsck.conf file, and rebooted the machine, I got the error about last superblock write time in future (exactly the same as on the screenshots I attached previously). In my opinion the problem has not been solved. How about others? B. Regards, Tomasz Grzelak P.S. Before having made the test I updated all packages, so my system was fresh. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543375: initscripts: last superblock write time in future
Hi, what is the status of the case - am I the only one experiencing the problem still? Is there anyone affected by this even with the new version of util-linux 2.16.1-4? B. Regards, Tomasz Grzelak
Bug#543375: initscripts: last superblock write time in future
2009/10/16 Mader, Alexander auma...@gmx.net Tomasz Grzelak schrieb: what is the status of the case - am I the only one experiencing the problem still? Is there anyone affected by this even with the new version of util-linux 2.16.1-4? As mentioned in an earlier e-mail everything works fine since I edited the hwclock-udev-rule as decribed in another e-mail in this bug report. thank you, I'll check that during the weekend. Somehow I thought the change would have been done by a regular update, and not editing files manually. I'll let you know if that works for me. B. Regards, Tomasz Grzelak
Bug#543375: initscripts: last superblock write time in future, occurring sometimes
Hello, I'm still having the same issue. I made an update, and rebooted the machine which casued the error appeared again. I have a dual boot machine, but I have not run vista today yet. And there's a 'screenshot' what happend after the restart right after having updated all the packages: https://hellfire666.no-ip.org/~myst/deb_error_11.10.2009.jpg And my version of util-linux is 2.16.1-4 as depicted below. You had mentioned the bug should have been solved in this version of util-linux, but for me it does not work. Or maybe it's related to some other package/settings? Please help! :) B. Regards, Tomasz Grzelak --- m...@daemon:~$ dpkg -p util-linux Package: util-linux Essential: yes Priority: required Section: utils Installed-Size: 1968 Maintainer: LaMont Jones lam...@debian.org Architecture: amd64 Version: 2.16.1-4 Replaces: e2fsprogs, fdisk, linux32, miscutils, schedutils, setterm, sparc-utils Provides: linux32, schedutils Depends: lsb-base (= 3.0-6), tzdata (= 2006c-2), initscripts, dpkg (= 1.15.4) | install-info Pre-Depends: libblkid1 (= 2.16), libc6 (= 2.4), libncurses5 (= 5.6+20071006-3), libselinux1 (= 1.32), libslang2 (= 2.0.7-1), libuuid1 (= 2.16), zlib1g (= 1:1.1.4) Suggests: util-linux-locales, kbd | console-tools, dosfstools Conflicts: console-tools ( 1:0.2.3-21), fdisk, kbd ( 1.05-3), linux32, schedutils, setterm Size: 623322 Description: Miscellaneous system utilities This package contains a number of important utilities, most of which are oriented towards maintenance of your system. Some of the more important utilities included in this package allow you to partition your hard disk, view kernel messages, and create new filesystems. --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543375: initscripts: last superblock write time in future, occurring sometimes
Hello, like I was afraid, having used older versions of e2fslibs and progs did not change the situation, today (Sat 10.10.2009) I got the error again. Next I updated all packages, and while rebooting I got the same error again :( Please have a look at the picture I took with my camera: https://hellfire666.no-ip.org/~myst/deb_error.jpg This bug has not been fixed. How about others? Are you still affected by this problem? B. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543375: initscripts: last superblock write time in future occurring sometimes
Hello, this is my first post here, and I'd like to report the bug is also affecting me. I have been using Debian unstable (AMD64) for about two years (with regular updates every several days), and the issue started to occur around the beginning of August (never had this problem before). My first thought was it was my hardware malfunction, but fortunately I've found this topic, so hopefully it's not my machine :) My hardware is Intel Core Duo, Gigabyte GA-EP45T-UD3R; I have tried different kernels (distribution provided, and my own), but no difference. The problems has statistically occured once per a few reboots. But near a week ago I downgraded e2fslibs and e2fsprogs to the following versions: e2fslibs_1.41.3-1_amd64.deb e2fsprogs_1.41.3-1_amd64.deb and have not had this issue since then. I know it may be only a coincidence and a false positive, but maybe it could be worth a try... And maybe a clue (hopefully not a confusion). (of course I'll let you all know if this happens to me again using those downgraded libs). I hope this issue will be fixed soon. Good luck and keep the great work going on! B. Regards, Tomasz Grzelak
