From: Jeff Garzik <jeff@garzik.org>
To: v.virvilis@biovista.com
Cc: linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: SATA disks resets in a md setup
Date: Sat, 09 May 2009 03:35:05 -0400 [thread overview]
Message-ID: <4A053229.5010406@garzik.org> (raw)
In-Reply-To: <200905081739.46206.v.virvilis@biovista.com>
Vassilis Virvilis wrote:
> [ 9351.377961] ata2: SError: { PHYRdyChg PHYInt 10B8B Dispar }
> [ 9351.377983] ata2.00: cmd b0/d5:01:09:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
> [ 9351.377985] res 50/00:00:b6:46:6a/00:00:13:00:00/e0 Emask 0x10 (ATA bus error)
[...]
> [10665.354196] ata2: SError: { UnrecovData Handshk }
> [10665.354196] ata2.00: cmd 35/00:00:27:ae:7a/00:04:01:00:00/e0 tag 0 dma 524288 out
> [10665.354196] res 50/00:00:26:ae:7a/00:00:01:00:00/e0 Emask 0x10 (ATA bus error)
[...]
> and my filesystem is dead. /dev/sdb is deleted from /dev. I have to reboot and even then linux can't find the ata2 /dev/sdb.
> I have to remove power for 1-2 min for the disk to become accessible again.
>
> Do you think the disk is bad or something?
For hardware details, see
http://ata.wiki.kernel.org/index.php/Libata_error_messages
The ATA bus is the cable connection, so an ATA bus error typically means
- problem with your cable, or
- your motherboard's SATA port, or
- your drive's SATA port, or
- "dirty power" supply, or
- some other cause for cable interference
Regards,
Jeff
next parent reply other threads:[~2009-05-09 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905081739.46206.v.virvilis@biovista.com>
2009-05-09 7:35 ` Jeff Garzik [this message]
2009-05-09 16:41 ` SATA disks resets in a md setup v.virvilis
2009-05-11 10:24 ` Vassilis Virvilis
2009-05-12 8:24 ` Tejun Heo
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=4A053229.5010406@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v.virvilis@biovista.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).