This bug was fixed in the package update-notifier - 0.136
---
update-notifier (0.136) saucy; urgency=low
[ Steve Langasek ]
* If the /var/lib/update-notifier/fsck-at-reboot stamp file is older than
the current uptime, any information about fscking at "next boot" is
definit
** Changed in: update-notifier (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
To manage notifica
On Mon, May 13, 2013 at 09:27:06AM -, maletin wrote:
> Steve Langasek (vorlon) wrote on 2013-05-11:#24
> > Which means this is working exactly as designed.
> correct. but why does my vmware not start a fsck after reboot (even with
> /forcefsck)?
I don't know, but that seems to be describ
Steve Langasek (vorlon) wrote on 2013-05-11:#24
> Which means this is working exactly as designed.
correct. but why does my vmware not start a fsck after reboot (even with
/forcefsck)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
> # dumpe2fs -h /dev/sdb1 | grep 'ount count'
> dumpe2fs 1.42 (29-Nov-2011)
> Mount count: 23
> Maximum mount count: 20
Which means this is working exactly as designed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
$ grep 'home' /etc/fstab
# /home was on /dev/sda4 during installation
#UUID=cf9c1b11-5604-4b67-80bc-e9a2a082b220 /home ext4defaults
0 2
/dev/sdb1 /home autodefaults0 2
--
You received this bug notification because you are a member of U
# dumpe2fs -h /dev/sdb1 | grep 'ount count'
dumpe2fs 1.42 (29-Nov-2011)
Mount count: 23
Maximum mount count: 20
~$ sudo sh -x /usr/lib/update-notifier/update-motd-fsck-at-reboot
[...]
Mount count: 23
Maximum mount count: 20
[...]
+ next_check_date= Tue J
** Tags added: rls-s-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
To manage notifications about this bug go to:
https://bugs.launchp
If you want to remove the message from motd without rebooting here is
the command to delete the file that has the problem message cached and
fully regenerate the motd:
sudo bash -c 'rm /var/lib/update-notifier/fsck-at-reboot && for file in
/etc/update-motd.d/*; do $file; done > /var/run/motd' && c
Having the same problem here on 12.10 with all updates installed. I fixed my
fstab (one filesystem didn't have the check set) and did a touch /forcefsck.
After the reboot, the message is still there, stating that my filesystems will
be checked on reboot. However, I checked my filesystems, and th
Still a problem on 12.04.1. Removing /var/lib/update-notifier/fsck-at-
reboot and logging out, then back in works. The /etc/motd is updated and
no longer contains this misleading and wrong message about pending
fscks.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Same here with Ubuntu Server 12.04.
I tried rm'ing the file, but it did not fix it. I didn't run 'touch
/forcefsck' because I am using LVM with a RAID1 config and not sure if
that would mess everything up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I have the same issue on Ubuntu 12.10.
[cluehr@: /] $ uname -a
Linux D-TXL-00429084 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
[cluehr@: /] $ lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core
Still there with:
$ uname -a
Linux merlin 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.1 LTS
Release:12.04
Codename: precise
--
You re
Upgraded from 10.04.4 to 12.04.1 yesterday and now i am getting these
error messages as well. I have done an manual fsck but that does not
help.
System seems fine.
thorre@ida:~$ uname -a
Linux ida 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
thorre@
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
To manage notifications about this bug go to:
https://bugs.launchpad.net/
hello,
(Ubuntu 11.10 "server")
it is not a big issue but it is a bit scary at first but the filesystem is not
compromised!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't
I had this issue with my logical filesystems after upgrading to 12.04 as
well... fsck was mysteriously skipping filesystems at boot.
I fixed it by making sure each entry in /etc/fstab had the option
'errors=remount-ro', executed 'touch /forcefsck', and rebooted... To my
delight, fsck ran and up
Server 12.04. It is an upgrade from 11.10, which was installed via CD. I have
tried setting FSCKFIX to "yes", no change. The
/var/lib/update-notifier/fsck-at-reboot file has a date/time stamp set to May
22.
Touched /boot/forcefsck and rebooted - file still there.
will be checked for errors at
I performed a remote server package upgrade (over SSH) to 12.04 from
10.04. I am effected by this bug too. I have no direct console access to
the machine since it's 50+ miles away, only SSH.
Please take this into consideration when you troubleshoot this problem.
Thanks.
--
You received this bug
On my media computer, I am running the latest updates for Ubuntu 11.10
and this fix is not released. Can we expect this to be back-ported to
11.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Looks like the bug is here in /usr/lib/update-notifier/update-motd-fsck-
at-reboot:
# check time when we did the last check
stamp="/var/lib/update-notifier/fsck-at-reboot"
if [ -e "$stamp" ]; then
stampt=$(stat -c %Y $stamp)
else
stampt=0
fi
now=$(date +%s)
if [ $(($stampt + 3600)) -lt $n
This bug still seems to exist in Ubuntu 12.04 LTS
Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-24-generic-pae i686)
* Documentation: https://help.ubuntu.com/
*** /dev/sdb1 will be checked for errors at next reboot ***
*** /dev/sdc1 will be checked for errors at next reboot ***
Last login:
This bug was fixed in the package update-notifier - 0.118ubuntu1
---
update-notifier (0.118ubuntu1) precise; urgency=low
* fix "fsck doesn't update system info on login" LP: #692355
Thanks to Paul McEnery
-- Michael VogtMon, 09 Jan 2012 12:58:55 +0100
** Branch linked: lp:
** Changed in: update-notifier (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
To manage notifica
** Changed in: update-notifier (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't up
It's actually update-notifier that provides update-motd-fsck-at-reboot.
** Package changed: e2fsprogs (Ubuntu) => update-notifier (Ubuntu)
** Changed in: update-notifier (Ubuntu)
Importance: Undecided => Medium
** Changed in: update-notifier (Ubuntu)
Status: Confirmed => Triaged
--
Y
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
To manage notifications about
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
After applying the above patch; either reboot, or regenerate /var/lib
/update-notifier/fsck-at-boot as follows:
$ sudo -s
# run-parts --lsbsysinit /etc/update-motd.d > /var/run/motd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
I was affected by this and bug and discovered that it appears to be
caused when the file /var/lib/update-notifier/fsck-at-reboot has a
datestamp in the future. This will never rectify itself unless the
actual date passes the datestamp on the file.
The attached patch fixes the problem.
** Patch ad
I'm seeing this on an upgraded Natty vmware instance.
Relevant fstab entry:
UUID=cbdda93e-2d89-47be-9bee-ce24bf1376ce /boot ext3relatime
0 2
touched /boot/forcefsck and rebooted - file still there.
boot.log says:
/sbin/fsck.xfs: XFS file system.
/sbin/fsck.xfs: XFS fi
No, I don't think it's an e2fsprogs issue. It looks like it's an init
scripts issue. Fsck should always run on boot, regardless of whether
or not /forcefsck is set. What forcefsck should do is set the -f flag,
to request a forced check even though the file system appears clean.
--
You receive
Assign to e2fsprogs as it seems a fsck issue
** Package changed: ubuntu => e2fsprogs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692355
Title:
fsck doesn't update system info on login
-
34 matches
Mail list logo
