Systemd-fsck's contradiction: should I be worried?

Support
1

Hi,

Today, by looking at the journal logs, for curiosity I wanted to check the logs of fsck about the SSD, I executed the following command:

journalctl -u systemd-fsck*
Which spited out:

nov 22 22:18:03 manjaro systemd[1]: Starting File System Check on /dev/disk/by-uuid/0d37cf27-2ff0-4234-a80e-4be323299166...
nov 22 22:18:03 manjaro systemd-fsck[176]: sda1: fsck.ext4 doesn't exist, not checking file system.
nov 22 22:18:03 manjaro systemd[1]: Finished File System Check on /dev/disk/by-uuid/0d37cf27-2ff0-4234-a80e-4be323299166.
nov 22 21:18:04 Probook systemd-fsck[243]: servicedisk: clean, 311/15269888 files, 10415536/61049344 blocks

On the second line complains about the fact that fsck.ext4 doesn’t exist (instead exists: /usr/bin/fsck.ext4), so no file system check has been performed, but on the fourth line states:
servicedisk: clean, 311/15269888 files, 10415536/61049344 blocks

The strange fact is not only this contradiction, but also that: dev/disk/by-uuid/0d37cf27-2ff0-4234-a80e-4be323299166 is the main SSD where Manjaro is installed, and servicedisk (UUID 8412b438-5d7b-48bd-bfb1-46666bb7ac64) is the second SSD where I keep my data; by judging from this log seems that only the second SSD has been checked by fsck, is right? And if so, why?

My SSDs in /etc/fstab:

UUID=0d37cf27-2ff0-4234-a80e-4be323299166 / ext4 defaults,noatime,commit=60 0 1

UUID=8412b438-5d7b-48bd-bfb1-46666bb7ac64 /home/dave/mounts/servicedisk/ ext4 defaults,noatime,commit=60 0 2

2

Well, I’m feel stupid :smiley:

In /etc/mkinitcpio.conf I was missing BINARIES=(fsck fsck.ext4) :
I had BINARIES=() ; as I added them, all is ok:

nov 23 16:29:17 manjaro systemd[1]: Starting File System Check on /dev/disk/by-uuid/0d37cf27-2ff0-4234-a80e-4be323299166...
nov 23 16:29:18 manjaro systemd-fsck[175]: /dev/sda1: clean, 701024/30531584 files, 10354282/122096128 blocks
nov 23 16:29:18 manjaro systemd[1]: Finished File System Check on /dev/disk/by-uuid/0d37cf27-2ff0-4234-a80e-4be323299166.
nov 23 15:29:18 Probook systemd-fsck[238]: servicedisk: clean, 311/15269888 files, 10415536/61049344 blocks
1 Like
3

Weird, I’ve never had to extend that BINARIES array for systemd-fsck to work.

4

So, the binary section in your mkinitcpio.conf is BINARIES=() ?

5

Yes, it is empty on my machine(s).

I adjusted the HOOKS-array to for a systemd init however.

6

So you have the fsck hook, I bet.
I tried by removing the two fsck’s from binaries and adding only the fsck hook, but oddly, this cause a longer boot time (obviously, after mkinitcpio modification, I run mkinitcpio -P)

7 
HOOKS=(base systemd autodetect modconf block keyboard sd-vconsole sd-lvm2 fsck filesystems)
8

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.