[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <462C441F.1070506@garzik.org>
Date: Mon, 23 Apr 2007 01:29:03 -0400
From: Jeff Garzik <jeff@...zik.org>
To: alex=lists-linux-kernel@...iev.com
CC: linux-kernel@...r.kernel.org
Subject: Re: SATA errors/messages after upgrade to 2.6.20.7
alex=lists-linux-kernel@...iev.com wrote:
>
> It is a Samsung HD501LJ SATA drive connected to 631xESB/632xESB controller.
> Reading and writing every block of the drive does not generate any other
> errors/failures. This is observed in 2.6.20.7 like a clockwork on any
> badblocks -v run or rebuild of a MD raid1 array onto the disk.
>
> It, however, was not observed on 2.6.18 in 182 badblocks -v runs followed by
> rebuild of MD raid1 array.
>
> Any idea what it might be?
>
> Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4.00: (irq_stat 0x40000008)
> Apr 23 14:45:34 stdsrv-x86-64bit kernel: ata4.00: cmd 60/80:00:14:16:c4/00:00:05:00:00/40 tag 0 cdb 0x0 data 65536 in
> Apr 23 14:45:34 stdsrv-x86-64bit kernel: res 51/40:00:40:16:c4/6f:00:05:00:00/40 Emask 0x9 (media error)
Does 'smartctl -d ata -t long /dev/XXXXX' return errors?
Media error is typically just that...
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists