From: Joerg Sommrey <jo@sommrey.de>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: 2.6.11-rc5: Promise SATA150 TX4 failure
Date: Tue, 1 Mar 2005 02:45:14 +0100 [thread overview]
Message-ID: <20050301014514.GA10653@sommrey.de> (raw)
Hi all,
a problem that was introduced between 2.6.10-ac9 and 2.6.10-ac11 made
it's way into 2.6.11-rc5. While taking a backup onto a SCSI-streamer one
of my RAID1-arrays gets corrupted. Afterwards the system hangs and
isn't even bootable. Need to raidhotadd the failed partition in single
user mode to get the box working again. Error messages:
Mar 1 01:46:15 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:15 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:15 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:15 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:15 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:15 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:15 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:15 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:15 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:15 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:15 bear kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Mar 1 01:46:15 bear kernel: sdc: Current: sense key: Medium Error
Mar 1 01:46:15 bear kernel: Additional sense: Unrecovered read error - auto
reallocate failed
Mar 1 01:46:15 bear kernel: end_request: I/O error, dev sdc, sector 52694606
Mar 1 01:46:15 bear kernel: raid1: Disk failure on sdc2, disabling device.
Mar 1 01:46:15 bear kernel: ^IOperation continuing on 1 devices
Mar 1 01:46:15 bear kernel: raid1: sdc2: rescheduling sector 12499976
Mar 1 01:46:16 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:16 bear kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Mar 1 01:46:16 bear kernel: sdc: Current: sense key: Medium Error
Mar 1 01:46:16 bear kernel: Additional sense: Unrecovered read error - auto
reallocate failed
Mar 1 01:46:16 bear kernel: end_request: I/O error, dev sdc, sector 52694614
Mar 1 01:46:16 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:16 bear kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Mar 1 01:46:16 bear kernel: sdc: Current: sense key: Medium Error
Mar 1 01:46:16 bear kernel: Additional sense: Unrecovered read error - auto
reallocate failed
Mar 1 01:46:16 bear kernel: end_request: I/O error, dev sdc, sector 52694622
Mar 1 01:46:16 bear kernel: raid1: sdc2: rescheduling sector 12499984
Mar 1 01:46:16 bear kernel: ata2: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata2: called with no error (51)!
Mar 1 01:46:16 bear kernel: SCSI error : <2 0 0 0> return code = 0x8000002
Mar 1 01:46:16 bear kernel: sdc: Current: sense key: Medium Error
Mar 1 01:46:16 bear kernel: Additional sense: Unrecovered read error - auto
reallocate failed
Mar 1 01:46:16 bear kernel: end_request: I/O error, dev sdc, sector 52694630
Mar 1 01:46:16 bear kernel: raid1: sdc2: rescheduling sector 12500000
Mar 1 01:46:16 bear kernel: RAID1 conf printout:
Mar 1 01:46:16 bear kernel: --- wd:1 rd:2
Mar 1 01:46:16 bear kernel: disk 0, wo:0, o:1, dev:sdb2
Mar 1 01:46:16 bear kernel: disk 1, wo:1, o:0, dev:sdc2
Mar 1 01:46:16 bear kernel: RAID1 conf printout:
Mar 1 01:46:16 bear kernel: --- wd:1 rd:2
Mar 1 01:46:16 bear kernel: disk 0, wo:0, o:1, dev:sdb2
Mar 1 01:46:16 bear kernel: raid1: sdb2: redirecting sector 12499976 to another
mirror
Mar 1 01:46:16 bear kernel: raid1: sdb2: redirecting sector 12499984 to another
mirror
Mar 1 01:46:16 bear kernel: raid1: sdb2: redirecting sector 12500000 to another
mirror
Mar 1 01:46:16 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata1: called with no error (51)!
Mar 1 01:46:16 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata1: called with no error (51)!
Mar 1 01:46:16 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata1: called with no error (51)!
Mar 1 01:46:16 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata1: called with no error (51)!
Mar 1 01:46:16 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error }
Mar 1 01:46:16 bear kernel: ata1: called with no error (51)!
Mar 1 01:46:16 bear kernel: SCSI error : <1 0 0 0> return code = 0x8000002
Mar 1 01:46:16 bear kernel: sdb: Current: sense key: Medium Error
etc. until hard reboot.
The failing array consists of two partitions of two SATA disks connected
to a Promise SATA150 TX4 controller.
-jo
--
-rw-r--r-- 1 jo users 63 2005-03-01 02:26 /home/jo/.signature
next reply other threads:[~2005-03-01 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 1:45 Joerg Sommrey [this message]
2005-03-01 23:37 ` J.A. Magallon
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=20050301014514.GA10653@sommrey.de \
--to=jo@sommrey.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome