From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: SATA disks resets in a md setup Date: Sat, 09 May 2009 03:35:05 -0400 Message-ID: <4A053229.5010406@garzik.org> References: <200905081739.46206.v.virvilis@biovista.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from srv5.dvmed.net ([207.36.208.214]:33801 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752848AbZEIHfH (ORCPT ); Sat, 9 May 2009 03:35:07 -0400 In-Reply-To: <200905081739.46206.v.virvilis@biovista.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: v.virvilis@biovista.com Cc: linux-kernel@vger.kernel.org, Linux IDE mailing list 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