[Eisfair] fsck recommended - warum macht er es nicht selbst?
Holger Bruenjes
holgerbruenjes at gmx.net
So Sep 11 17:42:09 CEST 2022
Hallo Stefan
Am 11/09/2022 um 17.10 schrieb Stefan Puschek:
>>
>>> [ 10.099622] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro.
>>> Quota mode: none. [ 10.360285] EXT4-fs (sda1): warning: maximal
>>> mount count reached, running e2fsck is recommended
>> ...
>>> [10.481762] EXT4-fs (sda4): warning: maximal mount count reached,
>>> running e2fsck is recommended [ 10.613944] EXT4-fs (sda4): mounted
>>> filesystem with ordered data mode. Opts: errors=remount-ro. Quota
>>> mode: none.
das sollte eigentlich von dracut angestossen werden
gucke mal mit dmesg nach
dmesg | grep fsck
------------
eis:/ # dmesg | grep fsck
[ 4.495649] dracut: issuing e2fsck
-------------
dann kannst du Anhand des Zeitstempel gucken was da passiert ist
--------------------------------------
[ 4.494018] dracut: Checking ext4:
/dev/disk/by-uuid/70097adc-f1e0-438b-aadb-1fcac1a00538
[ 4.495649] dracut: issuing e2fsck -a
/dev/disk/by-uuid/70097adc-f1e0-438b-aadb-1fcac1a00538
[ 4.696093] e2fsck (2400) used greatest stack depth: 13200 bytes left
[ 4.698649] dracut:
/dev/disk/by-uuid/70097adc-f1e0-438b-aadb-1fcac1a00538: clean,
10229445/183123968 files, 229344296/732486000 blocks
--------------------------------------
Holger
Mehr Informationen über die Mailingliste Eisfair