On Fri, Nov 02, 2018 at 07:27:41PM -0700, David Christensen wrote:
1. Backup your data and configuration settings.
never a bad idea
3. Download and run the manufacturer's diagnostic utility (Windows
may be required):
this is basically going to be the equivalent of smartctl -H, no need to
try to figure out how to run windows.
4. Most likely, the manufacturer diagnostic will say the drive is
good. This means the the problem is software -- e.g. bugs,
misconfiguration, incompatible packages, cruft, gremlins, etc.. Find
a disk benchmarking tool. I use dbench:
Running a full blown disk benchmark isn't going to add anything at this
point.
On Fri, Nov 02, 2018 at 02:56:06PM -0400, Stefan Monnier wrote:
Using what command line?
Various, tried from/to different partitions, with different
block sizes.
Well, it would be helpful to actually see one next time someone says
"with what command line". :) What is the output if you run the following
from a suitably large partition?
dd if=/dev/zero of=testfile.bin bs=64k count=300000 conv=fsync
dd if=testfile.bin of=/dev/null bs=64k
remember to delete testfile.bin when you're done. That creates an 18GiB
file; if you have more than 16GiB RAM you should increase the count.
