- I’m closing this thread because the original question has been answered, and the discussion was in danger of derailing from the factual solution.
The Final Answer:
The user’s problem was caused by an update to util-linux (version 2.42). This update changed the system’s behavior to prefer the in-kernel ntfs3 driver for mounting NTFS drives over the userspace ntfs-3g driver when fstab uses the auto option.
Because the kernel driver is stricter, it refused to mount a volume with a “dirty” bit set. The solution for anyone encountering this is to either:
- Run
chkdskon the drive from Windows to clear the dirty bit.- Or, change the mount type in
/etc/fstabfromautotontfs-3gto force the system to use the older driver.
Thank you to the following users for their helpful contributions: @milind, @bananamangodog, and @soundofthunder.
If any further help is required, please start a new thread.
Thank you.