All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Resch <jr@xor.at>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Problem on SATA-disk with Promise SATAII 150 TX4 ("DriveReady SeekComplete Error")
Date: Wed, 09 Feb 2005 19:20:42 +0100	[thread overview]
Message-ID: <420A547A.4000008@xor.at> (raw)

Hi,

[please CC me on replies]

I've got a box running 2.6.10 (with the patch[0] needed to support the 
Promise SATAII 150 TX4 controller).
This box has three software raid1 partitions mirrored on a SATA disk on 
the Promise controller and a disk on the mainboard IDE controller (VIA 
vt8235).

Within 4 days running the raid1, I got those three errors pasted below, 
each marking the SATA-raidmember as faulty. After "raidhotremove" and 
"raidhotadd" the SATA-raidmember syncs again fine and works at least a 
day until it is marked as faulty again.

Any pointers where I could look at to resolve this problem?
The SATA drive is a new Seagate ST3250823AS.

Feb  6 04:49:04 mars kernel: ata4: status=0x51 { DriveReady SeekComplete 
Error }
Feb  6 04:49:04 mars kernel: SCSI error : <3 0 0 0> return code = 0x8000002
Feb  6 04:49:04 mars kernel: FMK Current sda: sense = 70 88
Feb  6 04:49:04 mars kernel: ASC=40 ASCQ=c0
Feb  6 04:49:04 mars kernel: end_request: I/O error, dev sda, sector 
311900096
Feb  6 04:49:04 mars kernel: raid1: Disk failure on sda2, disabling device.
Feb  6 04:49:04 mars kernel: ^IOperation continuing on 1 devices
Feb  6 04:49:04 mars kernel: raid1: sda2: rescheduling sector 302518136
Feb  6 04:49:04 mars kernel: RAID1 conf printout:
Feb  6 04:49:04 mars kernel:  --- wd:1 rd:2
Feb  6 04:49:04 mars kernel:  disk 0, wo:1, o:0, dev:sda2
Feb  6 04:49:04 mars kernel:  disk 1, wo:0, o:1, dev:hda2
Feb  6 04:49:04 mars kernel: RAID1 conf printout:
Feb  6 04:49:05 mars kernel:  --- wd:1 rd:2
Feb  6 04:49:05 mars kernel:  disk 1, wo:0, o:1, dev:hda2
Feb  6 04:49:05 mars kernel: raid1: hda2: redirecting sector 302518136 
to another mirror

Feb  7 06:25:18 mars kernel: ata4: status=0x51 { DriveReady SeekComplete 
Error }
Feb  7 06:25:18 mars kernel: SCSI error : <3 0 0 0> return code = 0x8000002
Feb  7 06:25:18 mars kernel: FMK Current sda: sense = 70 88
Feb  7 06:25:18 mars kernel: ASC=40 ASCQ=c0
Feb  7 06:25:18 mars kernel: end_request: I/O error, dev sda, sector 
364654755
Feb  7 06:25:18 mars kernel: raid1: Disk failure on sda5, disabling device.
Feb  7 06:25:18 mars kernel: ^IOperation continuing on 1 devices
Feb  7 06:25:18 mars kernel: raid1: sda5: rescheduling sector 3706272
Feb  7 06:25:18 mars kernel: RAID1 conf printout:
Feb  7 06:25:18 mars kernel:  --- wd:1 rd:2
Feb  7 06:25:18 mars kernel:  disk 0, wo:1, o:0, dev:sda5
Feb  7 06:25:18 mars kernel:  disk 1, wo:0, o:1, dev:hda5
Feb  7 06:25:18 mars kernel: RAID1 conf printout:
Feb  7 06:25:18 mars kernel:  --- wd:1 rd:2
Feb  7 06:25:18 mars kernel:  disk 1, wo:0, o:1, dev:hda5
Feb  7 06:25:18 mars kernel: raid1: hda5: redirecting sector 3706272 to 
another mirror

Feb  9 06:25:02 mars kernel: ata4: status=0x51 { DriveReady SeekComplete 
Error }
Feb  9 06:25:02 mars kernel: SCSI error : <3 0 0 0> return code = 0x8000002
Feb  9 06:25:02 mars kernel: FMK Current sda: sense = 70 88
Feb  9 06:25:02 mars kernel: ASC=40 ASCQ=c0
Feb  9 06:25:02 mars kernel: end_request: I/O error, dev sda, sector 
310063304
Feb  9 06:25:02 mars kernel: raid1: Disk failure on sda2, disabling device.
Feb  9 06:25:02 mars kernel: ^IOperation continuing on 1 devices
Feb  9 06:25:02 mars kernel: raid1: sda2: rescheduling sector 300681344
Feb  9 06:25:02 mars kernel: RAID1 conf printout:
Feb  9 06:25:02 mars kernel:  --- wd:1 rd:2
Feb  9 06:25:02 mars kernel:  disk 0, wo:1, o:0, dev:sda2
Feb  9 06:25:02 mars kernel:  disk 1, wo:0, o:1, dev:hda2
Feb  9 06:25:02 mars kernel: RAID1 conf printout:
Feb  9 06:25:02 mars kernel:  --- wd:1 rd:2
Feb  9 06:25:02 mars kernel:  disk 1, wo:0, o:1, dev:hda2
Feb  9 06:25:02 mars kernel: raid1: hda2: redirecting sector 300681344 
to another mirror


[0] http://marc.theaimsgroup.com/?l=linux-ide&m=110426005503319&q=raw


Best regards,
-jr


             reply	other threads:[~2005-02-09 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 18:20 Johannes Resch [this message]
2005-02-11 23:05 ` Problem on SATA-disk with Promise SATAII 150 TX4 ("DriveReady SeekComplete Error") Jeff Garzik
     [not found] <3w4M1-61S-27@gated-at.bofh.it>
     [not found] ` <3wS5k-5H5-13@gated-at.bofh.it>
2005-02-12 20:51   ` Joerg Sommrey

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=420A547A.4000008@xor.at \
    --to=jr@xor.at \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.