From: Dave Chinner <david@fromorbit.com>
To: Luciano ES <lucmove@gmail.com>
Cc: XFS mailing list <linux-xfs@vger.kernel.org>
Subject: Re: File system corruption in two hard disks
Date: Wed, 3 Apr 2019 08:37:48 +1100 [thread overview]
Message-ID: <20190402213748.GV26298@dastard> (raw)
In-Reply-To: <20190402132357.0f72e3a9@lud1.home>
On Tue, Apr 02, 2019 at 01:23:57PM -0300, Luciano ES wrote:
> On Tue, 2 Apr 2019 08:32:26 +1100, Dave Chinner wrote:
> > At this point, I suspect your problems are the USB enclosure your
> > are using. Plug the disks directly into a SATA port and see if that
> > makes the IO errors go away. This looks like hardware problems, not
> > XFS issues...
>
> **************************
>
> Hi. Thank you for your kind attention again.
>
> I tested the disks directly connected to the SATA ports this time.
> One of them worked flawlessly.
That's good!
> Damn! It's the third USB enclosure that fails on me in one year!
That's about par for the course, I think. I simply don't trust USB
storage enclosures at all...
> The other disk failed again. Here is some dmesg:
....
> [ 3.790315] sd 1:0:0:0: [sdb] tag#12 Sense Key : Medium Error [current]
> [ 3.790318] sd 1:0:0:0: [sdb] tag#12 Add. Sense: Unrecovered read error - auto reallocate failed
Basically, this is saying the sector on the disk is bad, and there
is no spare sectors on the disk for recovery of that sector. i.e
the sector is now permanently dead. The drive is essentially
unusable at this point - it will only continue to get worse and
lose more data.
AFAICT, the only way you'll get anything off this drive is via
ddrescue to image it and then perform data recovery on the
decayed corpse it extracts....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-04-02 21:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 20:32 I got file system corruption with XFS Luciano ES
2018-12-11 20:57 ` Eric Sandeen
2018-12-11 22:54 ` Luciano ES
2018-12-12 1:01 ` Eric Sandeen
2018-12-11 21:27 ` Dave Chinner
2019-03-31 22:49 ` File system corruption in two hard disks Dave Chinner
2019-04-01 21:13 ` Luciano ES
2019-04-01 21:32 ` Dave Chinner
2019-04-02 16:23 ` Luciano ES
2019-04-02 16:42 ` Eric Sandeen
2019-04-02 18:54 ` Chris Murphy
2019-04-02 21:37 ` Dave Chinner [this message]
2019-08-03 0:53 ` XFS file system corruption, refuses to mount Luciano ES
2019-08-03 1:11 ` Darrick J. Wong
2019-08-03 1:53 ` Luciano ES
2019-08-03 5:35 ` Dave Chinner
2019-08-03 8:05 ` Luciano ES
2019-08-15 20:32 ` XFS file system " Luciano ES
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190402213748.GV26298@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lucmove@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).