I have an external USB hard drive (WD Elements, 1TB), which is already partially filled (~370GB available):
$ mount | grep store17 /dev/sde1 on /store17 type ext4 (rw,nosuid,nodev,noexec,relatime,data=ordered,user,x-systemd.device-timeout=10)
I need to copy new files into the drive, but for a 18MB file (the file size seems to matter), here is what happens:
$ cd /store17 $ cp ~/my_18MB_file . $ ls [...] my_18MB_file [...] $ # WAITING A FEW SECONDS... $ ls ls: reading directory '.': Input/output error
Then all I can do is to umount/remount the device, but of course, after remounting the device, the new file has not been copied.
To be noticed:
The writing process is working well with small data, like
touch /store17/myemptyfile, or copying a 2kB file.
If the file to copy is 800MB big, the I/O error happens while copying:
cp: error writing './gum_src.tar.gz': Input/output error
I made a short health test with
smartmontools, which passed.
Question: What can I run on the command line to better understand what happens? May I consider this hard drive as dead, despite the reading process seems perfectly fine?