-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Again, please stop taking this conversation private; keep the mailing
list on the Cc.
On 11/19/2014 11:37 AM, Fennec Fox wrote:
well ive used spinrite and its found a few sectors and they
never move so obviously the drives firmware isnt dealing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please get in the habit of using your mail client's reply-to-all
button instead of reply; there is no need for us to take this
conversation private.
On 11/17/2014 10:15 PM, Fennec Fox wrote:
snip big smartctl output
i know the drive is dying and
Phillip Susi posted on Tue, 18 Nov 2014 10:36:14 -0500 as excerpted:
As I said before though, the errors you posted from dmesg don't indicate
that the drive failed to read sectors, but rather that it returned
incorrect data, and this is *NEVER* supposed to happen.
I'd suggest running a few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/17/2014 05:55 PM, Fennec Fox wrote:
well i am an arch linux user and machine owner using a failing
drive its still relyable enough for me but btrfs seems not to mark
bad blocks as unusable and continues to try to write to them.
On Nov 17, 2014, at 3:55 PM, Fennec Fox fennect...@gmail.com wrote:
well i am an arch linux user and machine owner using a failing drive
its still relyable enough for me but btrfs seems not to mark bad
blocks as unusable and continues to try to write to them.
It’s supposed to do try to
