New answers tagged

0

root@root:/media/eluhuj/_/lost+found# for file in $(cat /root/list.dir | awk -F ' ' '{print " " $1}' | sed "s/://g" | sed 's/#/\\#/g'); do echo $cmd $file; done > lost.sh root@root:/media/eluhuj/_/lost+found# cat lost.sh #! /bin/bash set -v sudo ls -lRas \#11272193 sudo ls -lRas \#12582913 sudo ls -lRas \#1310721 sudo ls -lRas \#14680065 sudo ls -lRas ...


3

When the partition is in clean state, there is no actual fsck run, which is why the date isn't updated. If you want to force it, the -f option does just that: sudo fsck -f /dev/sda1.


-2

Are you using Ubuntu? You could try booting into recovery mode, which gives you option to fsck your drive


2

First off, fsck'ing a mounted filesystem is expected to produce errors. The filesystem isn't consistent because the journal hasn't been replayed (nor has it been cleanly unmounted), and you can't replay the journal because that (like any other change) would corrupt the filesystem. If you're using LVM, you could take a snapshot and fsck the snapshot. touch ...



Top 50 recent answers are included