Hi @jolexin
The error is typical of what may be presented when an NTFS volume has not been cleanly unmounted, or if there is damage. The dirty bit is set either way, until maintenance has been properly performed to reset the dirty bit and fix any possible damage.
Using chkdsk in a Windows environment is the recommended method to achieve this.
Simply being able to access the disk in Windows does not indicate that the volume is fine. You need to run chkdsk which will find and fix any damage and clear the dirty bit when successful. The ntfs3 kernel driver, when used, will not mount an NTFS volume suspected of being damaged, until this is done. This is a security measure of ntfs3, and it is by design.
You will find relevant information in the following link.
Note that there is no ‘TL;DR’;
Take some time to read through it and understand the content.
While I can’t comment on kernel 5.15.x regarding this particular issue, you could likely benefit generally from updating to (at minimum) kernel 6.1.x LTS.
I hope this helps.
Cheers.