From: David Greaves <david@dgreaves.com>
To: Chris Eddington <chrise@synplicity.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 assemble after dual sata port failure
Date: Sun, 11 Nov 2007 22:49:49 +0000 [thread overview]
Message-ID: <4737870D.5000906@dgreaves.com> (raw)
In-Reply-To: <47373EB9.9050408@synplicity.com>
Chris Eddington wrote:
> Yes, there is some kind of media error message in dmesg, below. It is
> not random, it happens at exactly the same moments in each xfs_repair -n
> run.
> Nov 11 09:48:25 altair kernel: [37043.300691] res
> 51/40:00:01:00:00/00:00:00:00:00/e1 Emask 0x9 (media error)
> Nov 11 09:48:25 altair kernel: [37043.304326] ata4.00: ata_hpa_resize 1:
> sectors = 976773168, hpa_sectors = 976773168
> Nov 11 09:48:25 altair kernel: [37043.307672] ata4.00: ata_hpa_resize 1:
> sectors = 976773168, hpa_sectors = 976773168
I'm not sure what an ata_hpa_resize error is...
It probably explains the problems you've been having with the raid not 'just
recovering' though.
I saw this:
http://www.linuxquestions.org/questions/linux-kernel-70/sata-issues-568894/
What does smartctl say about your drive?
IMO the spare drive is no longer useful for data recovery - you may want to use
ddrescue to try and copy this drive to the spare drive.
David
PS Don't get the ddrescue parameters the wrong way round if you go that route...
next prev parent reply other threads:[~2007-11-11 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 20:28 Raid5 assemble after dual sata port failure Chris Eddington
2007-11-08 10:33 ` David Greaves
2007-11-09 21:23 ` Chris Eddington
2007-11-10 0:28 ` Chris Eddington
2007-11-10 9:16 ` David Greaves
2007-11-10 18:46 ` Chris Eddington
2007-11-11 17:09 ` David Greaves
2007-11-11 17:41 ` Chris Eddington
2007-11-11 22:49 ` David Greaves [this message]
2007-11-12 1:01 ` Bill Davidsen
2007-11-17 6:31 ` Chris Eddington
2007-11-18 12:25 ` David Greaves
-- strict thread matches above, loose matches on Subject: below --
2007-11-07 20:23 chrise
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=4737870D.5000906@dgreaves.com \
--to=david@dgreaves.com \
--cc=chrise@synplicity.com \
--cc=linux-raid@vger.kernel.org \
/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).