From: Danilo Godec <danilo.godec@agenda.si>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: SATA errors?
Date: Wed, 01 Oct 2008 11:25:53 +0200 [thread overview]
Message-ID: <48E34221.1000008@agenda.si> (raw)
[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]
Hi,
I've been searching the web, Google, mailing lists for a while now, but
can't really find the answer - so I'm hoping for a 'SATA guru' here...
On one of my server, I use 4 drive RAID5 Linux raid. One of the drives
keeps reporting these errors:
> Oct 1 10:11:29 bigxen2 kernel: ata1.00: exception Emask 0x10 SAct 0x0
> SErr 0x10002 action 0x2 frozen
> Oct 1 10:11:29 bigxen2 kernel: ata1.00: (irq_stat 0x04400000, PHY RDY
> changed)
> Oct 1 10:11:29 bigxen2 kernel: ata1.00: cmd
> 25/00:08:5c:be:60/00:00:14:00:00/e0 tag 0 cdb 0x0 data 4096 in
> Oct 1 10:11:29 bigxen2 kernel: res
> 50/00:00:6b:6a:60/00:00:14:00:00/e0 Emask 0x10 (ATA bus error)
> Oct 1 10:11:30 bigxen2 kernel: ata1: waiting for device to spin up (7
> secs)
> Oct 1 10:11:40 bigxen2 kernel: ata1: soft resetting port
> Oct 1 10:11:41 bigxen2 kernel: ata1: softreset failed (1st FIS failed)
> Oct 1 10:11:41 bigxen2 kernel: ata1: softreset failed, retrying in 5 secs
> Oct 1 10:11:46 bigxen2 kernel: ata1: hard resetting port
> Oct 1 10:11:47 bigxen2 kernel: ata1: SATA link up 3.0 Gbps (SStatus
> 123 SControl 300)
> Oct 1 10:11:47 bigxen2 kernel: ata1.00: configured for UDMA/133
> Oct 1 10:11:47 bigxen2 kernel: ata1: EH complete
> Oct 1 10:11:47 bigxen2 kernel: SCSI device sda: 976771055 512-byte
> hdwr sectors (500107 MB)
> Oct 1 10:11:47 bigxen2 kernel: sda: Write Protect is off
> Oct 1 10:11:47 bigxen2 kernel: sda: Mode Sense: 00 3a 00 00
> Oct 1 10:11:47 bigxen2 kernel: SCSI device sda: drive cache: write back
As far as I can tell these happen randomly - sometimes it's 8 hours
between two, sometimes it's a couple of minutes. There are about 5-20 of
those per day, however Linux raid never kicks the drive out of the
array. There are also no other signs of drive not functioning properly
(such as filesystem corruption or similar).
Any ideas? Can anyone 'decode' the above errors?
Thanks, Danilo
--
Danilo Godec, sistemska podpora
Predlog! Obiscite prenovljeno spletno stran http://www.agenda.si
ODPRTA KODA IN LINUX
STORITVE : POSLOVNE RESITVE : UPRAVLJANJE IT : INFRASTRUKTURA IT : IZOBRAZEVANJE : PROGRAMSKA OPREMA
Visit our updated web page at http://www.agenda.si
OPEN SOURCE AND LINUX
SERVICES : BUSINESS SOLUTIONS : IT MANAGEMENT : IT INFRASTRUCTURE : TRAINING : SOFTWARE
[-- Attachment #2: danilo_godec.vcf --]
[-- Type: text/x-vcard, Size: 316 bytes --]
begin:vcard
fn:Danilo Godec
n:Godec;Danilo
org:Agenda OpenSystems
adr:;;Ul. Pohorskega bataljona 49;Maribor;;2000;Slovenia
email;internet:danilo.godec@agenda.si
tel;work:+386 2 4216138
tel;fax:+386 2 4216141
tel;cell:+386 40 618802
x-mozilla-html:FALSE
url:http://www.agenda.si/
version:2.1
end:vcard
next reply other threads:[~2008-10-01 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 9:25 Danilo Godec [this message]
2008-10-01 10:08 ` SATA errors? Wolfgang Denk
2008-10-01 10:41 ` Danilo Godec
2008-10-01 11:48 ` David Lethe
2008-10-01 12:17 ` David Greaves
2008-10-01 13:11 ` David Lethe
2008-10-01 21:36 ` Danilo Godec
2008-10-01 22:03 ` Justin Piszcz
2008-10-03 9:52 ` Danilo Godec
2008-10-03 16:13 ` Iustin Pop
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=48E34221.1000008@agenda.si \
--to=danilo.godec@agenda.si \
--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).