If TKL is running inside a VM then the physical hard drive that the virtual filesystem resides on is also worth checking (using filesystem tools of the native OS). Sorry I haven't got time to explain more clearly step by step for you ATM but there is at least one other topic here that deals with this issue. Give you a hint for starters - you will need to boot with a Live CD (or ISO if running virtually) to be able to check the filesystem.

Did you fsck the PV (phyiscal volume - LVM) as well as the LV (logical volume)?

And as I said if it's a VM you may also need to do a chkdsk (assuming it's Windows) on the physical HDD. Personally I'd check the physical drive first, then the PV and finally the LV.

There's a few threads that may be of interest; here, here and your old thread here.

Speaking of your old thread is this a new problem or just trying some more to fix the old VM? If this is a new issue then I'd be looking carefully at the physical HDD. Unless these issues relate to 'dirty' shutdowns (ie not shutting down properly) then having this same (/similar) issue again would suggest to me that there is definately something wrong with physical storage.