![]() If it ends up in occupied disk space, it will show up inside an existing file (old or new) and you'll see it as a checksum error. If it ends up in unused disk space, it will not affect your files and you won't see it as an error. In either case, because of the incorrect addresses, the metadata gets written to somewhere where it should not go. Then either (1) the SATA controller is the problem and it issues commands with incorrect/malformed addresses or (2) the controller is okay but the addresses suffer some bit flips on their way to the hard drive, due to some faulty connection, and ECC fails to detect and correct these errors. The SATA controller then issues a series of low-level commands to the hard drive (the drive also has its own disk controller, which is another level of complexity, but let's ignore that). I'm assuming Windows/NTFS tries to create some filesystem metadata, which gets fired off to the SATA controller. ![]() The small size of the corruption does suggest to me that it's a low-level hardware/controller issue. I'm not at all well-versed with NTFS details or controller level stuff, so take what I say with a grain of salt. Is bad RAM a possibility? (I've used the same motherboard/CPU/memory sticks/etc for 2+ years) ![]() I've used it for many years and never had any problems, so it's a little surprising that issues are cropping up now. It was set to auto-defrag on idle, but I've since disabled it as a precaution. I'm using Auslogics Disk Defrag and my suspicion is that this might be the culprit. There are no SMART errors on either of the drives, and I've owned them for some time (over a year, but under 2 years). and then had a CRC mismatch a few days later. Most recently, I CRC checked a file after downloading and after transferring to the Seagate drive (both were correct). I did a hex compare between good and corrupt versions of the files and I found blocks of data missing and instead replaced with hex that represent the strings "Microsoft reserved partition" or "Basic data partition" (each character being separated by 0x00, or ".") followed by nulls (0x0). #AUSLOGICS DISK DEFRAG PRO SSD RAID WINDOWS 7#I'm using Windows 7 so the drives are NTFS, single volume per physical drive (no RAID). ![]() #AUSLOGICS DISK DEFRAG PRO SSD RAID SOFTWARE#This happened on both a WD20EARS and ST4000DM000, so I believe the issue is at the software level. I've noticed a few (read: 2 or 3 of 2000+) video files on different HDDs becoming silently corrupt after some time. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |