Hi,
On 23-05-16 20:04, Manuel Bilderbeek wrote:
3. My BIOS told me at boot today that no RTC clock time was set. I guess
my RTC battery is dead. Will replace it.
Replaced it last night. Then booted again and set the hwclock. Then
booted Debian, no fsck, as I still have the e2fsck.conf in
Hi,
After a few days, reporting here what's going on now...
1. I haven't seen an fsck of my HDD's ever since I added that
e2fsck.conf file
2. When booting, I do get a message that superblock timestamps of my SSD
(/dev/sdf1) are too far in the future and I get a very quick fsck of the
SDD. It
Hi,
On 19-05-16 23:04, Michael Biebl wrote:
Looks like I need to have systemd-timesync run *before* systemd-fsck!?
If your hwclock drifts that much, maybe
/etc/e2fsck.conf:
[options]
broken_system_clock=1
(as referenced in my earlier reply) is an option.
Can you try that?
Hi,
Thanks for taking interest in this annoying problem. Today I again got
an fsck at boot...
On 18-05-16 23:35, Michael Biebl wrote:
fsck.ext[234] should no longer run an fsck because of that.
Which version of e2fsprogs have you installed?
Should be latest in testing:
ii e2fsprogs
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:
A start job is running... for sda1 (1min23 / no limit)
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 pre
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/fst
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 befo
Hi,
On 15-11-15 10:06, Michael Biebl wrote:
I'm afraid not. Not being able to reproduce this issue (on my side)
makes this harder.
Can you reproduce the issue reliably?
So far it happened all 3 boots since the boot count became high enough
to do an fsck. So I guess the answer is yes. Each
Hi,
On 14-11-15 14:09, Michael Biebl wrote:
And alternative could be, to attach the output of systemd-analyze and
"systemd-analyze blame" when such a long fsck happens.
I thought I had already done that, but here it is again in full.
$ systemd-analyze
Startup finished in 3.802s (kernel) + 9mi
Hi,
On 14-11-15 13:49, Michael Biebl wrote:
Please keep in mind, that fsck for / and /usr is run in the initramfs
nowadays and systemd is not yet involved.
Can you boot and removing "quiet" from the kernel command line.
This should give you more log messages from systemd.
OK, I'll try that.
I
11 matches
Mail list logo
