I tried to do a similar debugging process, and when I did chkdsk on Windows, I had a massive drive with tons of files, so it took about 8 hrs to check everything and report all was clean.
That's why I tried with a USB thumb drive with no files on the latest 6.6 as well and got the same error.
I tried clearing the dirty flag, too, for both the thumb drive and a Seagate Expansion drive, even though Windows said nothing was wrong. I even tried reinstalling NTFS-3G.
There is something between the latest Kernel and updates. I suspect the issue won't occur for a drive already mounted before a particular update, but after a reboot or sudden power cycle, this issue comes up.
It doesn't seem like an actual drive issue, more so something with the mount processing and flags.
I am not an expert here. I am just trying to share my observations. I'll circle back if I have more.
That's why I tried with a USB thumb drive with no files on the latest 6.6 as well and got the same error.
I tried clearing the dirty flag, too, for both the thumb drive and a Seagate Expansion drive, even though Windows said nothing was wrong. I even tried reinstalling NTFS-3G.
There is something between the latest Kernel and updates. I suspect the issue won't occur for a drive already mounted before a particular update, but after a reboot or sudden power cycle, this issue comes up.
It doesn't seem like an actual drive issue, more so something with the mount processing and flags.
I am not an expert here. I am just trying to share my observations. I'll circle back if I have more.
Statistics: Posted by user123rpi5 — Thu Apr 11, 2024 9:40 pm
