How to prevent NTFS failure?

valkiyerie · 2017-08-14 19:08:29

Hi, I am a recovering lurker.

Please pardon me if this has been addressed and I've missed it. Skipping all the "usual system anomalies" of an HDD or memory module's iminent demise...

Discovered the problem backing up the 2.5" (broken?) drive a 2nd 3.5" HDD.

1. The ext4 partition seems to be FINE? Files are copying without error and rapidy. (regardless of destination media or filesystem) Even large files, 300+MB up to 2G, not one hitch.

BUT -- on the same HDD:

2. The NTFS partitions are borked.Oddly, many files that read "with pauses resumed" copied intact. Files that copy with NO LAG may also be truncated or corrupt. Copy fails over 50%, regardless of source file's type, and regardless of destination filesystem or media.

2,b: Copy failure is "Source File Dependent". e.g. if the source file = /dev/sda2/storage/000.tar.gz , 10mb
only copies a 2mb dest. file @ /dev/sdb1/storage/000.tar.gz, it will only EVER copy 2mb. No
matter what the destination. Renaming 000.tar.tgz to BLOB gets the same results. Other files in
/dev/sda2/storage copy fine.

HDD = 320g SATA in a Lenovo g650, used heavily over 6 months. When I got it I wiped the HDD, then gparted like:

|....80g......|......192g......|..40g..|.8g.|
sda1 = ext4, Arch
sda2 = ntfs, common storage
sda3 = ntfs, for m$
sda4 = swap

What is the CAUSE of this? I don't expect anyone to fix it, obviously it's too late -- But without knowing the cause I cannot prevent a repeat.

My sincere thanks for any input
V.

Last edited by valkiyerie (2017-08-19 18:39:54)

Arch Linux

#1 2017-08-14 19:08:29

How to prevent NTFS failure?

Board footer