My system locked up on my and I was forced to do a hard reset to unjam it. When it booted up it gave me some file system errors and told me to run e2fsck with -v -y option to fix it. I did that and I wrote down most of the output results. Among othe things the output was: 0 bad blocks, free inodes count wrong (1406195, counted=1406237) I'm assuming that that's because of the reset and not a sign of possible hard drive failure (no drive clicking yet) but I wanted to check with others with more experience with Linux just to be sure.