My laptop recently went down, presumably due to a hard disk error. It wouldn't boot completely and the error given was one of the type "read error", which indicated that there was a physical problem on the hard disk.

I ran fsck from a Knoppix live CD. When it finished, it didn't really provide any report as to what problems it found, or at least not that I noticed. It just told me it had completed the check. When I rebooted the laptop the boot process went without a hitch.

Does fsck drop logs anywhere I could find them? Obviously since I ran it from a live CD, likelyhood would be they were destroyed when I rebooted.

Hi,

fsck information normally are only written to console, they are not logged to any file if you mean this.

Basically, yes that is good information, and what I assumed.

It just strikes me weird that my laptop started working after running fsck, but I didn't see anything in the output that indicated problems were found.

If you didn't get asked to confirm action, the errors were probably simply "logical" errors rectifiable by re-running the journal. If there were bad (or shared) inode links that really needed fixing, you would have been asked - presuming you didn't use "-y".

It depends on how you started fsck There's the -v option for verbose output. You could have
redirected that to a file if you wanted to read all the details.
But I think it is too late now.