I found some more info: http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks
The Linux on my Core i5 where I could reproduce the corruption so easily runs smartctl on all disks every 10 minutes, the AMD runs smartctl every hour, so this explains what I saw. It also says the...
I found out something new: if I disable the write cache of the drive with hdparm -W 0 /dev/sdb, the problem goes away. Before, I would get an error within a few minutes, and now it's been running for several hours with no errors at all.
This supports my theory that the problem is in the drive...
Hi,
I'm seeing a similar problem. Your post is the only thing I can find that
resembles what I see. I believe it is not a bug in Linux or badblocks, but a
problem with the drive.
hdd:
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG HD204UI
Serial Number...