Thank you k-doug for placing the suggested workaround here!
I would also like to mention that with regards to Xenial (16.04) and any
Ubuntu release using systemd, the mechanism for forcing filesystem
checks on startup is presently unable to display the results of the
filesystem check on the
After discussing the issue with Adam Blomberg (paradox606), he suggested
enabling the verbose option to get more information regarding the scan.
He indicated that this can be done by modifying /etc/default/rcS to
include "VERBOSE=yes", and that it is also possible to force the repair
of errors
Tested reboot with forcefsck file in root on Xenial [Ubuntu 16.04.1
LTS], with following results:
# cat /var/log/fsck/checkfs
(Nothing has been logged yet.)
# cat /var/log/fsck/checkroot
(Nothing has been logged yet.)
# cat /var/log/upstart/mountall.log
cat: /var/log/upstart/mountall.log: No such
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage notifications about this bug go to:
I'm sorry, guys, but this sucks. Critical bug unsolved for six years -
the responsible person should get spanked bare bottom.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not
Critical bug, please fix!
Having a log would help a lot when doing remote check disk.
At the very least, telling why it's not important would be a first step
instead of just ignoring this bug for the past 6 years.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Bump
Oh, for God's sake and in the name of all that's holy.
Bump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
It's pretty ignorant to assume that this is a wishlist item. This is an
essential log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
This is Critical, not Wishlist... Please change the importance so that
this gets fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
even windows store ntfs chkdsk boot logs in the logs db, is windows
more professionnal than ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in
** Tags added: amd64 i386 jaunty karmic trusty
** 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/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
Can confirm still present in 14.04 - NOT Triaged.
** Changed in: mountall (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck
** Changed in: mountall (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
There is some terse fsck info being logged on my 14.04 Trusty desktop in
/var/log/upstart/mountall.log. Usually, it says something like this:
fsck from util-linux 2.20.1
grubboot: clean, 520/51200 files, 98181/204800 blocks
When I force checking by setting Maximum mount count to 1, it looks
How is this bug still here after 4.5 years?
I mean, I'd rather lose the whole rest of /var/log than my fsck logs --
and I may even be about to!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
** Changed in: mountall (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
** Changed in: mountall (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
Any workaround the user can do to force the results to be logged in any
file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
Marcelo: You could make /sbin/fsck a shell script that wraps the real
fsck binary, and logs the output as desired. Doing this with a dpkg
diversion might even keep things from breaking when the util-linux
package is upgraded
--
You received this bug notification because you are a member of
Ehm, this bug is still here in trusty, more than four years after it was
originally reported. And it does seem to be quite an essential thing,
being able to see the output of your file system repair. Can it really
be so hard to have fsck save the output somewhere?
--
You received this bug
Tristan, I agree with you, but unfortunately would have to recommend
using Debian instead of Ubuntu for server applications. Not only was
this bug the result of an oversight in switching to mountall, mountall
itself made the system less admin-friendly by doing away with several
boot-time shell
This is a critical bug. One of those bugs you find when everything is in
danger, and about to be lost. As I gently type, I'm trying to find ways
to recover my server. I know there has to be a disk about to fail, I've
seen the strange behavior on boot and because I was there I know
something is
** Changed in: mountall (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
** Changed in: mountall (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
To manage
Even on MS Windows you can dig out fsck messages with the eventviewer.
This is stupid, lazy and arrogant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations
Uh, how can this possibly be considered a 'wishlist' item? This is core
functionality, and it's broken. Far as my company is concerned, this is
an URGENT BUG. Please escalate.
Linux gr 3.0.0-13-virtual #22-Ubuntu SMP Wed Nov 2 17:10:19 UTC 2011
i686 i686 i386 GNU/Linux
--
You received this
This also affects me.
Linux fs 3.2.0-35-generic #55-Ubuntu SMP Wed Dec 5 17:42:16 UTC 2012 x86_64
x86_64 x86_64 GNU/Linux
Over three years later and this is unassigned still?
I question the wishlist categorization of this as well. Ubuntu remains
a sub-par choice for server distros because of
This affects me too, in precise (12.04.3). Just ran an fsck on three
drives, which was carried out (I looked at the xx% completed message
for each of the drives. Unfortunately /var/log/fsck only shows two
default files that are only 31 characters long.
--
You received this bug notification
I'm affected by this bug too.
Linux gurke 2.6.32-29-generic #58-Ubuntu SMP Fri Feb 11 20:52:10 UTC
2011 x86_64 GNU/Linux
I'd also like to question the Importance category. For me, and maybe
other server operators too, it's very important to be able to review the
logs of bootup filesystem checks.
I am affected too.
'~$ uname -a; Linux T43 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01
UTC 2011 i686 GNU/Linux'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log
** Changed in: mountall (Ubuntu)
Status: New = Triaged
** Changed in: mountall (Ubuntu)
Importance: Undecided = Wishlist
--
Does not log fsck invocations in /var/log/fsck/
https://bugs.launchpad.net/bugs/513644
You received this bug notification because you are a member of Ubuntu
31 matches
Mail list logo
