On 12/08/2021 15:03, Bev Nicolson wrote:
Oh yes I can. Figured it out. Ran a fsck, which I expected to take hours. Nothing. All fine.
Well done! :-)
OK, if it was suspiciously short, it could be that it assumed that disk was OK and didn't really check (if I recall, some versions of fdisk check for a flag that says "there's something wrong" and if it's not set, don't do anything.
If you're using fsck, I'm not aware of a way of overriding this behaviour. If you know what type of filesystem that partition is using, you can use a varaint of fsck instead. E.g you can use fsck.ext3 or fsck.ext4 if you're using ext3 or ext4 file system respectively.
If you don't know what file system the partition is, use
fsck -N /dev/sda2
but replace /dev/sda2 with the right partition that you want to check.
I got [/usr/sbin/fsck.ext4 (1) -- /] fsck.ext4 /dev/sda2
That tells me it's ext4.
So, I can use
fsck.ext4 -f /dev/sda2
This forces a check on the drive, even if it seems OK.
If it's still amazingly quick, then either you have a very fast drive, or double check you're checking the correct partition.
If it's still OK, which, to be honest it's likely to be, then try running the machine from the live cd for a while and see it it stays OK.
If it still seems OK, then it would look like some sort of software misconfiguration or corruption on your machine, which may be hard to locate. If that's the case, it's trawling through log files I think...
Good luck!
Steve