Intermittent File Corruption Copying To NTFS
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Intermittent File Corruption Copying To NTFS
Just an FYi, I did post this in the Ubuntu forums, but didn't get much feedback. One user suggested using ntfs-3g. It appears as though that's already installed, but I don't know how to verify whether or not that's what's being used when accessing, or, more specifically, writing to NTFS disks.
I'm relatively new to Linux, so bear with me. I'm about 38 days into my install...at least that's what uptime shows me right now.
Feel free to tell me if this is a known issue and I've been blissfully unaware of it up to this point.
I've copied a 7.9G file multiple times, and sometimes the destination file gets corrupted. Here's what I've done:
Same for all copies - copied using: Linux Mint 9 (isadora) Kernel 2.6.32.21-generic
GNOME 2.30.2
1 (bad)
---------------------------------
Source: WinXP machine on network
Destination: 32G AData thumb drive (NTFS)
Result: Corrupt, MD5 Hash doesn't match
2 (bad)
---------------------------------
Source: WinXP machine on network
Destination: 80G USB drive (NTFS)
Result: Corrupt, MD5 Hash doesn't match
3 (good)
---------------------------------
Source: WinXP machine on network
Destination: /$HOME/temp
Result: Fine, MD5 Hash matches
4 (bad - 1st copy to Data1)
---------------------------------
Source: /$HOME/temp
Destination: Data1 Internal SATA drive (NTFS)
Result: Corrupt, MD5 Hash doesn't match
5 (good - 1st copy to Data2)
---------------------------------
Source: /$HOME/temp
Destination: Data2 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
6 (good - 2nd copy to Data1)
---------------------------------
Source: /$HOME/temp
Destination: Data1 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
7 (good - 2nd copy to Data2)
---------------------------------
Source: /$HOME/temp
Destination: Data2 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
8 (good - 3rd copy to Data1)
---------------------------------
Source: /$HOME/temp
Destination: Data1 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
So, it appears to copy from an SMB share just fine, and to its own filesystem just fine, but intermittently has trouble writing to local NTFS partitions. Writing to an SMB NTFS share is also file, which makes sense since it isn't having to talk "directly" to NTFS.
Another point to note is that there aren't just two md5 hashes (one good, one bad). There's one good, and multiple bad.
I'm relatively new to Linux, so bear with me. I'm about 38 days into my install...at least that's what uptime shows me right now.
Feel free to tell me if this is a known issue and I've been blissfully unaware of it up to this point.
I've copied a 7.9G file multiple times, and sometimes the destination file gets corrupted. Here's what I've done:
Same for all copies - copied using: Linux Mint 9 (isadora) Kernel 2.6.32.21-generic
GNOME 2.30.2
1 (bad)
---------------------------------
Source: WinXP machine on network
Destination: 32G AData thumb drive (NTFS)
Result: Corrupt, MD5 Hash doesn't match
2 (bad)
---------------------------------
Source: WinXP machine on network
Destination: 80G USB drive (NTFS)
Result: Corrupt, MD5 Hash doesn't match
3 (good)
---------------------------------
Source: WinXP machine on network
Destination: /$HOME/temp
Result: Fine, MD5 Hash matches
4 (bad - 1st copy to Data1)
---------------------------------
Source: /$HOME/temp
Destination: Data1 Internal SATA drive (NTFS)
Result: Corrupt, MD5 Hash doesn't match
5 (good - 1st copy to Data2)
---------------------------------
Source: /$HOME/temp
Destination: Data2 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
6 (good - 2nd copy to Data1)
---------------------------------
Source: /$HOME/temp
Destination: Data1 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
7 (good - 2nd copy to Data2)
---------------------------------
Source: /$HOME/temp
Destination: Data2 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
8 (good - 3rd copy to Data1)
---------------------------------
Source: /$HOME/temp
Destination: Data1 Internal SATA drive (NTFS)
Result: Fine, MD5 Hash matches
So, it appears to copy from an SMB share just fine, and to its own filesystem just fine, but intermittently has trouble writing to local NTFS partitions. Writing to an SMB NTFS share is also file, which makes sense since it isn't having to talk "directly" to NTFS.
Another point to note is that there aren't just two md5 hashes (one good, one bad). There's one good, and multiple bad.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Intermittent File Corruption Copying To NTFS
I'm not sure what might be causing the corruption, but you can use ntfs-3g directly from the command line like this:
ntfs-3g /dev/sda1 /mnt/windows
It also works using the standard mount command
mount -t ntfs-3g /dev/sda1 /mnt/windows
Assuming sda1 is the divce where your NTFS partition is located. You can get more detailed information from the manual page by typing the following at a command line:
man ntfs-3g
ntfs-3g /dev/sda1 /mnt/windows
It also works using the standard mount command
mount -t ntfs-3g /dev/sda1 /mnt/windows
Assuming sda1 is the divce where your NTFS partition is located. You can get more detailed information from the manual page by typing the following at a command line:
man ntfs-3g
Re: Intermittent File Corruption Copying To NTFS
How can I
1 - figure out if ntfs or ntfs-3G is being used?
2 - force ntfs-3G to be used by the automount functionality?
1 - figure out if ntfs or ntfs-3G is being used?
2 - force ntfs-3G to be used by the automount functionality?
Re: Intermittent File Corruption Copying To NTFS
"ntfs" is symbolically linked to "ntfs-3g" internally so there is no difference.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Re: Intermittent File Corruption Copying To NTFS
Ok. From what I understand, that's the most stable NTFS driver. Given that it's proven to silently corrupt data, is there a filesystem that Windows & Linux can both share that supports large files (over 4G) that doesn't require installing anything extra in Windows?
Re: Intermittent File Corruption Copying To NTFS
Are things any better with Linux Mint 18.3?
Can I trust with NTFS partition where both Windows and Linux write to (Not at the same time though)?
Can I trust with NTFS partition where both Windows and Linux write to (Not at the same time though)?
Re: Intermittent File Corruption Copying To NTFS
I assume you mean better than Windows...
I dumped Windows 7 a year ago and am much happier with Mint. The learning curve is steep, but it is worth it.
Advantages (imo):
1) MUCH faster boot and shutdown times, plus faster in general.
2) NO MORE FRAGMENTED FILES!!! (ext4 has no fragmentation unless your drive is nearly full)
3) No OS telemetry
4) fewer viruses
5) better security
6) no users/dude/Documentsandsettings/local/roaming/appdata/blah/blah/blah/yada/yada/yada (I HATE that folder structure!)
Disadvanges:
1) steeper learning curve
2) fewer native programs (but this is getting better)
There is only one program I need Windows 7 for, so I installed VMWare player and Windows 7 runs fine as a virtual machine.
As far as the NTFS partition, I don't know if you can trust it or not (I reformatted all of my drives to ext4 last year, only my Windows 7 VM itself has ntfs.) I never had a problem with ntfs under linux other than the file fragmentation and slower speeds.
Re: Intermittent File Corruption Copying To NTFS
*edit*JohnFrumm wrote: ⤴Sun May 13, 2018 12:00 pmI assume you mean better than Windows...
I dumped Windows 7 a year ago and am much happier with Mint. The learning curve is steep, but it is worth it.
Advantages (imo):
1) MUCH faster boot and shutdown times, plus faster in general.
2) NO MORE FRAGMENTED FILES!!! (ext4 has no fragmentation unless your drive is nearly full)
3) No OS telemetry
4) fewer viruses
5) better security
6) no users/dude/Documentsandsettings/local/roaming/appdata/blah/blah/blah/yada/yada/yada (I HATE that folder structure!)
Disadvanges:
1) steeper learning curve
2) fewer native programs (but this is getting better)
There is only one program I need Windows 7 for, so I installed VMWare player and Windows 7 runs fine as a virtual machine.
As far as the NTFS partition, I don't know if you can trust it or not (I reformatted all of my drives to ext4 last year, only my Windows 7 VM itself has ntfs.) I never had a problem with ntfs under linux other than the file fragmentation and slower speeds.
BTW, did you verify your hdd is good? Linux Mint 18.3 has a "GSmartControl" program where you can check the disk smart data and test the hdd's.
Re: Intermittent File Corruption Copying To NTFS
I was talking about the reliability of the NTFS drive in Linux Mint.
I have an HD I would like both Windows 10 (18.3) and Linux Mint 18.3 will be able to access and share data on (Dual Boot).
It is not the Boot Drive of Windows 10.
I'm asking if the NTFS driver of Linux Mint (I guess NTFS-3G) is the latest one and if is it reliable enough to not make any issue with this shared partition.
As I wrote, they won't access it on the same time.
I have an HD I would like both Windows 10 (18.3) and Linux Mint 18.3 will be able to access and share data on (Dual Boot).
It is not the Boot Drive of Windows 10.
I'm asking if the NTFS driver of Linux Mint (I guess NTFS-3G) is the latest one and if is it reliable enough to not make any issue with this shared partition.
As I wrote, they won't access it on the same time.
Re: Intermittent File Corruption Copying To NTFS
I'd been doing
linux -> fat32 USB thumb-drive -> TV
with no problems until I copied a .txt file, then a win10 machine couldn't read it. But Linux and the TV still could.
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Your data and OS are backed up....right?
- AZgl1800
- Level 20
- Posts: 11170
- Joined: Thu Dec 31, 2015 3:20 am
- Location: Oklahoma where the wind comes Sweeping down the Plains
- Contact:
Re: Intermittent File Corruption Copying To NTFS
I have never had a problem with NTSF drives with Linux, my only regret is that when I bought my 6TB Seagate which comes native with NTSF that I was brand new to Linux and unaware of how much I would be using Linux relative to Win7
So, thinking that I would be needing to keep a lot of backups of 3 Win7 and 1 Win10 laptops, I miscued and made it into 4 gB NTSF and 2 gB ext4 partitions.
I now realize that should have been reversed, and I am now using Linux 99.88% of the time, and the Win7 desktop just sits there, waiting for someone to love it.
Oh well, at least I can use the NTSF to copy stuff back and forth between the two OS types.
So, thinking that I would be needing to keep a lot of backups of 3 Win7 and 1 Win10 laptops, I miscued and made it into 4 gB NTSF and 2 gB ext4 partitions.
I now realize that should have been reversed, and I am now using Linux 99.88% of the time, and the Win7 desktop just sits there, waiting for someone to love it.
Oh well, at least I can use the NTSF to copy stuff back and forth between the two OS types.