Bug#788050: systemd-fsck : Check disks at each reboot

[Axel Ludszuweit]

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 following while booting, which
> wasn't visible before:
>

This solutions works on my computer but systemctl -b says


- Dez 20 17:18:55 kruemel systemd[1]: systemd-fsckd.socket: Cannot add 
dependency job, ignoring: Unit systemd-fsckd.socket is masked.


several times

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788050: systemd-fsck : Check disks at each reboot

[Axel Ludszuweit]

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

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788050: systemd-fsck : Check disks at each reboot

[Axel Ludszuweit]

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.




___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788050: (no subject)

[Axel Ludszuweit]

Dear maintainer,


Konsole output

axel@kruemel:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.1.0-2-amd64 root=/dev/mapper/OS_1-root ro
axel@kruemel:~$

Therefore I think, that I am not using the splash option.

Plymouth is not installed.
Maybe the fstab is helpful:


Konsole output
axel@kruemel:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
#
proc /proc   proc   defaults 
   0  0
/dev/mapper/OS_1-root/   ext3errors=remount-ro 
 0  1
/dev/md0 /boot   ext3defaults 
  0  2
/dev/mapper/data_1-home  /files1 ext3defaults 
  0  2
/dev/mapper/data_2-files /files2 ext3defaults 
  0  2
/dev/mapper/data_1-files /home   ext3defaults 
  0  2
/dev/mapper/OS_1-opt /optext3defaults 
  0  2
/dev/mapper/OS_1-tmp /tmpext3defaults 
  0  2
/dev/mapper/OS_1-usr /usrext3defaults 
  0  2
/dev/mapper/OS_1-var /varext3defaults 
  0  2
/dev/mapper/data_1-swap  noneswapsw 
0  0
/dev/scd0/media/cdrom0   udf,iso9660 user,noauto 
   0  0
/dev/fd0 /media/floppy0  autorw,user,noauto 
0  0

## usbfs is the USBUSERS group in fstab file:
# none /proc/bus/usb   usbfs 
  devgid=126,devmode=664 0 0


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#788050: systemd-fsck : Check disks at each reboot

[Axel Ludszuweit]

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 
successfull and on the next boot-ups no errors appear until new fsck is 
triggered by reaching boot count limit.


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers