For your reference:
When using the /r
switch, the functionality of the /f
switch is already included; so this means it’s unnecessary; all that’s needed is:
chkdsk (x:) /r /x
…in order to scan for and repair the filesystem, and also check for and repair bad sectors. Nonetheless, that was 4 hours well spent, especially as it solved your issue.
Cheers.

After a full system update, I was getting the same error while opening my internal NTFS partition; which was automatically mounted every time before the update.
…
sudo fsck -y /dev/<your partition name here> sudo ntfsfix /dev/<your partition name here>
fsck
should not ever be run on an NTFS filesystem.
ntfsfix
does not repair an NTFS filesystem - using it will clear the dirty bit and usually prevent chkdsk from doing its job.

But this fix was temporary.
After every boot it didn’t automatically get mounted.
Understandable, because you did not actually fix anything with the commands you used. You cleared the dirty bit – but that does not repair an NTFS volume at all – to do that, you absolutely must use chkdsk from within a Windows environment.

So I searched on the internet and found this
https://www.linuxbabe.com/desktop-linux/how-to-automount-file-systems-on-linuxCaution: I don’t know if this fix is safe or not
Well, again, that was not a fix of any kind. The link is a basic walkthrough on how to auto mount various filesystem volumes, in this case using the /etc/fstab
file.
For what it’s worth, the instructions seem consistent with the intended purpose; though there are arguably better ways to do this using systemd mount / automount units.
The OP hasn’t bothered to report back to offer any closure on their original issue, though it seems likely that the [Primer] NTFS on Linux link would have also offered the solution for their problem.
Therefore marking the appropriate post as the solution for all concerned. Cheers.