On 09/01/2018 03:35 AM, Duncan wrote:
Chris Murphy posted on Fri, 31 Aug 2018 13:02:16 -0600 as excerpted:
If you want you can post the output from 'sudo smartctl -x /dev/sda'
which will contain more information... but this is in some sense
superfluous. The problem is very clearly a bad drive, the drive
explicitly report to libata a write error, and included the sector LBA
affected, and only the drive firmware would know that. It's not likely a
cable problem or something like. And that the write error is reported at
all means it's persistent, not transient.
Two points:
1) Does this happen to be an archive/SMR (shingled magnetic recording)
device? If so that might be the problem as such devices really aren't
suited to normal usage (they really are designed for archiving), and
btrfs' COW patterns can exacerbate the issue. It's quite possible that
the original install didn't load up the IO as heavily as the balance-
convert does, so the problem appears with convert but not for install.
2) Assuming it's /not/ an SMR issue, and smartctl doesn't say it's dying,
I'd suggest running badblocks -w (make sure the device doesn't have
anything valuable on it!) on the device -- note that this will take
awhile, probably a couple days perhaps longer, as it writes four
different patterns to the entire device one at a time, reading everything
back to verify the pattern was written correctly, so it's actually going
over the entire device 8 times, alternating write and read, but it should
settle the issue of the reliability of the device.
Or if you'd rather spend the money than the time and it's not under
warrantee still, just replace it, or at least buy a new one to use while
you run the tests on that one. I fully understand that tying up the
thing running tests on it for days straight may not be viable.
Thank you
sudo smartctl -x /dev/sda
finds 4 errors...
Thank you, I shall spend no more time o that and replace the HDD...
Anyway, I should expect a less cryptic message from btrfs...
PC
