up vote 2 down vote favorite
1
share [g+] share [fb]

It seems fsck.ext4 quit very soon, I guess it only checks the journal logs, and do nothing if the journal is clean. Is it? How to force it to check the whole file system? I've tried the -f option, but it quits again said it's clean very quickly.

link|improve this question
69% accept rate
feedback

1 Answer

up vote 4 down vote accepted

Try: fsck -pvcf -- will force a verbose check for bad blocks and automatically repair. If you still have issues then your HDD might have physical problems.

link|improve this answer
1  
Make sure that the filesystem is NOT mounted before performing a fsck command. – mdpc Jul 23 '11 at 4:25
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.