When fsck is ran on a mounted filesystem that is mounted read/write, the fs is always reported a potentially still having problems, because it isn't really safe to run fsck
on the fs when it is mounted.
Although, when useing the -n flag (which essentially is a read only fsck (no writes are done)) then fsck could consider the fs to be sane once complete.