Control: tags -1 + pending
Am 07.09.2016 um 18:31 schrieb Michal Schmidt:
> systemd-fsckd's event loop terminates if nothing happens for 30 seconds
> (IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently
> than that, but the interval is not guaranteed. So systemd-fsckd may
Processing control commands:
> tags -1 + pending
Bug #788050 [systemd] systemd-fsck : Check disks at each reboot
Added tag(s) pending.
--
788050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with probl
systemd-fsckd's event loop terminates if nothing happens for 30 seconds
(IDLE_TIME_SECONDS). Usually fsck writes progress updates more frequently
than that, but the interval is not guaranteed. So systemd-fsckd may exit
by itself while fsck is busy working. When this happens, fsck will
receive
Have the same problem since upgrading from ubuntu 14.04 to 16.04.
HDD 600 GB ext3 partition
systemd-fsck is checking approx. 1 minute (approx 15% checked), then
systemd-fsck is aborted and a line appears saying:
[***] A startup task for ... is running
What does this "A startup task for ... is
I think I just ran into this problem.
systemd-fsck seemed to be choking on a ~1.8T LVM volume with an ext3
filesytem - the volume's group is on an encrypted primary partion on a
HDD. I'm running stretch.
Before attempting to remedy the problem:
* systemd-fsck tried to run on the volume ever
Hi,
Discovered this bug while researching trouble i'm having with systemd
boot and (forced) fscks. All that has been said in this bug, i'm seeing
the same. Since this bug was last updated december 20th 2015, i'm
wondering what the state of this is atm.
I'm running Ubuntu 16.04 though, systemd
Hi,
On Tue, 1 Dec 2015 23:23:52 +0100 Manuel Bilderbeek
wrote:
> Hi,
>
> On 29-11-15 01:28, Michael Biebl wrote:
> > Does the problem go away if you use "systemctl mask
> > systemd-fsckd.service systemd-fsckd.socket"
>
> Yes, it does. Using this I got to see the
Hi,
On 29-11-15 01:28, Michael Biebl wrote:
Can you boot with systemd.debug-shell on the kernel command line, and
then switch to tty9 while the fsck is running and attach strace to the
fsckd and fsck process?
I want to try this, but for some reason, grub always boots, even if I
keep SHIFT
I also have this problem. I have no LVM, no RAID, no graphical boot,
just a plain old disk partition.
The "mount count" has passed "maximum mount count", systemd runs fsck
but it never finishes, it gets interrupted by SIGPIPE. It all starts
again next boot.
Output from cat /proc/cmdline is:
On 29-11-15 01:28, Michael Biebl wrote:
Am 29.11.2015 um 00:12 schrieb Manuel Bilderbeek:
How can I help?
Describe your setup in as much detail as possible. LVM, RAID, fstab etc.
No RAID, no LVM. I've got a HDD and an SSD. I'm now booting from the SSD.
$ cat /etc/fstab
# /etc/fstab: static
Hey Michael,
Michael Biebl [2015-09-24 18:32 +0200]:
> Am 24.09.2015 um 17:46 schrieb hannu@pp.inet.fi:
> > This works for me:
> >
> > copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system
> >
> > edit /etc/systemd/system/systemd-fsckd.service, add TimeoutStartSec under
> >
Hi again,
On 15-11-15 10:06, Michael Biebl wrote:
I saw some workaround and suggestions, but is there already a direction of a
solution of this issue?
I'm afraid not. Not being able to reproduce this issue (on my side)
makes this harder.
Can you reproduce the issue reliably?
As I wrote
Might have been a red herring
Am 28. November 2015 15:36:12 MEZ, schrieb Martin Pitt :
>Hey Michael,
>
>Michael Biebl [2015-09-24 18:32 +0200]:
>> Am 24.09.2015 um 17:46 schrieb hannu@pp.inet.fi:
>> > This works for me:
>> >
>> > copy
Am 29.11.2015 um 00:12 schrieb Manuel Bilderbeek:
> How can I help?
Describe your setup in as much detail as possible. LVM, RAID, fstab etc.
Can you reproduce the issue with arbitrary mounts?
Can you reproduce the issue with a minimal setup? On a different system?
Do you have any hints how we
Dear Maintainer,
I have converted my ext3 filesystem to ext4 to reduce time needed by fsck.
But the behaviour is still unchanged, fsck of big partition fails.
--
Axel Ludszuweit
In der Horst 28E
D-30900 Wedemark
Telefon: +49 (0) 5130 373093
Mobil: +49 (0) 170 2736589
Dear maintainer,
according to the suggestion from message #65 I have increased the
timeout to 30min.
But fsck still ends with error 13 checking big partitions. Manually fsck
ends succeesfully.
It seems to be the same behaviour described in message #70.
This was not enough on my system, fsck exited with signal 13 after 60s
anyway. This worked for me:
# systemctl mask systemd-fsckd.service systemd-fsckd.socket
At next boot, fsck ran for some minutes and then completed successfully.
Note that `systemctl disable` did not work because these units
I edited the /etc/default/grub file, removed splash from
"GRUB_CMDLINE_LINUX_DEFAULT" and ran update-grub2. To force the fsck I used:
sudo tune2fs -C 30
and had to reboot twice. I saw the fsck progress, but it still stopped
at the same time and gave an operation error / sigpipe.
On
This works for me:
copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system
edit /etc/systemd/system/systemd-fsckd.service, add TimeoutStartSec under
[Service]
[Service]
TimeoutStartSec=60min
___
Pkg-systemd-maintainers mailing list
Am 24.09.2015 um 17:46 schrieb hannu@pp.inet.fi:
> This works for me:
>
> copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system
>
> edit /etc/systemd/system/systemd-fsckd.service, add TimeoutStartSec under
> [Service]
>
> [Service]
> TimeoutStartSec=60min
Hm, good point.
I can confirm that this fix works on my system.
On 09/24/2015 11:32 AM, Michael Biebl wrote:
Am 24.09.2015 um 17:46 schrieb hannu@pp.inet.fi:
This works for me:
copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system
edit /etc/systemd/system/systemd-fsckd.service, add
I can confirm that this fix works on my system.
On 09/24/2015 11:32 AM, Michael Biebl wrote:
Am 24.09.2015 um 17:46 schrieb hannu@pp.inet.fi:
This works for me:
copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system
edit /etc/systemd/system/systemd-fsckd.service, add
Am 23.09.2015 um 18:08 schrieb Allen Webb:
> On Fri, 14 Aug 2015 10:13:25 +0200 Axel Ludszuweit
> wrote:
> > Dear maintainer,
> >
> > I also think there is is a timeout problem.
> > I Use lvm2 with md software raid based on ext3.
> > Systemd file system checks at
On Fri, 14 Aug 2015 10:13:25 +0200 Axel Ludszuweit
wrote:
> Dear maintainer,
>
> I also think there is is a timeout problem.
> I Use lvm2 with md software raid based on ext3.
> Systemd file system checks at boot-up on small partitions finish
> successfull on big
Dear maintainer,
I also think there is is a timeout problem.
I Use lvm2 with md software raid based on ext3.
Systemd file system checks at boot-up on small partitions finish
successfull on big partitions end with error 13.
Manual executed file system check on these big partitions end
Hi,
For a few days now each time the computer boots it forces a
file system check on two of my disks.
[...]
I am still experiencing this error in Debian Sid/unstable. Could
the cause be pinpointed? Please tell me, if you need more debug
information from an affected system.
Just
Dear Debian folks,
Am Sonntag, den 05.07.2015, 15:28 +0200 schrieb Paul Menzel:
Am Montag, den 08.06.2015, 10:48 +0200 schrieb Michael Biebl:
Am 08.06.2015 um 10:26 schrieb Michael Biebl:
Am 08.06.2015 um 08:01 schrieb Ludovic Lebègue:
For a few days now each time the computer
Dear Debian folks,
Am Montag, den 08.06.2015, 10:48 +0200 schrieb Michael Biebl:
Am 08.06.2015 um 10:26 schrieb Michael Biebl:
Am 08.06.2015 um 08:01 schrieb Ludovic Lebègue:
For a few days now each time the computer boots it forces a file
system
check on two of my disks.
Package: systemd
Version: 220-4
Severity: important
Dear maintainer.
For a few days now each time the computer boots it forces a file system
check on two of my disks.
Here is the relevant journalctl entry :
Jun 08 07:48:19 leonardo kernel: input: PS/2 Generic Mouse
as
Am 08.06.2015 um 10:26 schrieb Michael Biebl:
Am 08.06.2015 um 08:01 schrieb Ludovic Lebègue:
For a few days now each time the computer boots it forces a file system
check on two of my disks.
Here is the relevant journalctl entry :
Jun 08 07:48:19 leonardo kernel: input: PS/2 Generic
30 matches
Mail list logo