@GM,
I did not know fsck misbehaved like that on GPT disks. Have they fixed it yet?
Never used GPT myself, though.
As for the Windows dirty bit, I have had the most infuriating "luck" whenever I touched a Windows computer with an external/usb drive/Kindle.
Windows is extremely trigger-happy and the first time you remove a device without Safely Remove Hardware it gives it the scarlet letter.
Supposedly chkdsk will verify everything then unset the dirty bit, but noooooooo, I have tried chkdsk'ing thumb drives and Kindles 6 or 7 times in a row and doing Safely Remove Hardware just like Windows wants, and it
never goes away. I don't know what I could be doing wrong, maybe the claim that chkdsk will fix the dirty bit is a lie?
But apparently the location has been discovered, and you can fix the drive by editing the raw drive with a hex editor. Go Microsoft!
https://www.raymond.cc/blog/manually...kdsk/view-all/
...
I rather think it is slightly safer on Linux.
