Quote:I appreciate your helpYou're welcome.
Quote:The disk is quite full and is 1TB, so i dont have anywhere big enough to transfer the data tooHope the data isn't too important then.
As your preference was not to have to use the command line, chkdsk remains an option to fix the problem properly. I was advising caution as without a current Windows system I can't be sure how Windows behaves when an NTFS/ext4 dual partitioned drive is plugged in.
I do recall older Windows immediately trying to re-format any ext4 drive that got plugged in which always worried me.
If you use the drive in a Windows system you'll know what happens.
Clearly you should be able to decline the Windows offer to reformat and then identify the NTFS partition and run chkdsk on it - provided you take due care.
An NTFS disk with dirty status indicates that the file system may be in an inconsistent state.
If it is mounted and used as though it is 'clean' the inconsistent state may cause data loss.
You may be fine, but there is a risk. On a USB stick used only to copy the odd file or two from one place to another you might accept the risk.
But if there's 1TB of important data that only exists on the Seagate drive then that's a different matter.
Refusing to mount a dirty NTFS disk is technically the correct behaviour.
If a system automatically mounts a dirty NTFS disk (or allows it to be mounted from the CLI without reporting the flag) it is hiding the risk.
Using ntfsfix with the -n option, is a dry run. 'Do not write anything, just show what would have been done.'
Since it is a Windows issue the correct thing is to get Windows to fix it.
ntfsfix can fix some NTFS inconsistencies but it is not chkdsk.
I'll move this thread to Hardware->Hard Drives and SSDs which is probably a better fit than Software->Support->Other
edit - added further information and explanation
stevef
clueless
clueless
