> On Mo, 24.08.20 12:39, Benjamin Beckmeyer ([email protected]) wrote: > >> root@em-switch:~ systemctl status systemd-fsck* >> ● >> systemd-fsck@dev-disk-by\x2duuid-1073706a\x2da8c1\x2d4d59\x2db701\x2d73b07f603 >> Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; >> vendor >> Active: active (exited) since Sat 2018-12-01 01:00:07 CET; 2min 3s ago >> Docs: man:[email protected](8) >> Process: 210 ExecStart=/usr/lib/systemd/systemd-fsck >> /dev/disk/by-uuid/1073706 >> Main PID: 210 (code=exited, status=0/SUCCESS) >> >> Dec 01 01:00:07 em-switch systemd[1]: Starting File System Check on >> /dev/disk/by >> Dec 01 01:00:07 em-switch systemd-fsck[210]: read_bad_blocks_file: No such >> file > LMGTFY: > > https://www.mail-archive.com/[email protected]/msg114560.html > > Please see README, we require the util-linux mount command. If you > don't use that, you are on your own. > > Lennart > > -- > Lennart Poettering, Berlin > Thanks, for your hint Lennart, I fixed our build environment.
Cheers, Benjamin _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
