From: Gerhard Wiesinger <lists@wiesinger.com>
To: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
Date: Mon, 7 Jul 2008 17:08:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0807071705490.2997@bbs.intern> (raw)
In-Reply-To: <alpine.LFD.1.10.0807071649340.1160@bbs.intern>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1747 bytes --]
Hello!
Missing logs attached ...
Ciao,
Gerhard
--
http://www.wiesinger.com/
On Mon, 7 Jul 2008, Gerhard Wiesinger wrote:
> Hello!
>
> I'm having a similar problem with a brand new Hardware under Fedora 9 x64
> 8GB RAM
> Motherboard: ASUS M3N-H/HDMI
> Chipset: NForce 8300/Nvidia 750a
> CPU: AMD AM2 5600+, 2.9GHz, Brisbane Dual Core
> Kernel: 2.6.25.9-76.fc9.x86_64
> Smartmontools: smartmontools-5.38-2.fc9.x86_64
> BIOS AHCI mode
> Power cables for ata3 and ata4 are on the same cable from an Enermax power
> supply.
>
> ata1.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
> ata2.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
> ata3.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
> ata4.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
> ata5.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
> ata6.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
> scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
> scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
> scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
> scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
> scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
> scsi 5:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
>
> Problem occours only on ata3, I've changed the disk Port 3 the third time
> (new disks) and changed the SATA cable, too. Problem still exists.
>
> Sometimes a RAID rebuild doesn't work at all.
>
> To get the drive to live I've to power down the system.
>
> Logs are attached.
>
> Can it be a bug on concurrent access of smartctl/smartd?
>
> Any ideas?
>
> Ciao,
> Gerhard
>
> --
> http://www.wiesinger.com/
>
>
[-- Attachment #2: Type: TEXT/plain, Size: 4333 bytes --]
Jul 7 15:56:22 big8 kernel: md: data-check of RAID array md0
Jul 7 15:56:22 big8 kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Jul 7 15:56:22 big8 kernel: md: using maximum available idle IO bandwidth (but not more than 80000 KB/sec) for data-check.
Jul 7 15:56:22 big8 kernel: md: using 128k window, over a total of 976759808 blocks.
Jul 7 15:56:26 big8 kernel: md: data-check of RAID array md1
Jul 7 15:56:26 big8 kernel: md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
Jul 7 15:56:26 big8 kernel: md: using maximum available idle IO bandwidth (but not more than 80000 KB/sec) for data-check.
Jul 7 15:56:26 big8 kernel: md: using 128k window, over a total of 976759808 blocks.
Jul 7 16:00:53 big8 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Jul 7 16:00:53 big8 kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jul 7 16:00:53 big8 kernel: res 40/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jul 7 16:00:53 big8 kernel: ata3.00: status: { DRDY }
Jul 7 16:00:53 big8 kernel: ata3: hard resetting link
Jul 7 16:01:00 big8 kernel: ata3: port is slow to respond, please be patient (Status 0x80)
Jul 7 16:01:03 big8 kernel: ata3: softreset failed (device not ready)
Jul 7 16:01:03 big8 kernel: ata3: hard resetting link
Jul 7 16:01:10 big8 kernel: ata3: port is slow to respond, please be patient (Status 0x80)
Jul 7 16:01:13 big8 kernel: ata3: softreset failed (device not ready)
Jul 7 16:01:13 big8 kernel: ata3: hard resetting link
Jul 7 16:01:20 big8 kernel: ata3: port is slow to respond, please be patient (Status 0x80)
Jul 7 16:01:48 big8 kernel: ata3: softreset failed (device not ready)
Jul 7 16:01:48 big8 kernel: ata3: limiting SATA link speed to 1.5 Gbps
Jul 7 16:01:48 big8 kernel: ata3: hard resetting link
Jul 7 16:01:53 big8 kernel: ata3: softreset failed (device not ready)
Jul 7 16:01:53 big8 kernel: ata3: reset failed, giving up
Jul 7 16:01:53 big8 kernel: ata3.00: disabled
Jul 7 16:01:53 big8 kernel: ata3: EH complete
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 29123647
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 29124927
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 29123903
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 1182894207
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 1139671639
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 1557222687
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 29123647
Jul 7 16:01:53 big8 kernel: raid5: Disk failure on sdc1, disabling device. Operation continuing on 2 devices
Jul 7 16:01:53 big8 kernel: sd 2:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul 7 16:01:53 big8 kernel: end_request: I/O error, dev sdc, sector 29124671
Jul 7 16:01:53 big8 kernel: md: md0: data-check done.
Jul 7 16:01:53 big8 kernel: RAID5 conf printout:
Jul 7 16:01:53 big8 kernel: --- rd:3 wd:2
Jul 7 16:01:53 big8 kernel: disk 0, o:1, dev:sda1
Jul 7 16:01:53 big8 kernel: disk 1, o:1, dev:sdb1
Jul 7 16:01:53 big8 kernel: disk 2, o:0, dev:sdc1
Jul 7 16:01:53 big8 kernel: RAID5 conf printout:
Jul 7 16:01:53 big8 kernel: --- rd:3 wd:2
Jul 7 16:01:53 big8 kernel: disk 0, o:1, dev:sda1
Jul 7 16:01:53 big8 kernel: disk 1, o:1, dev:sdb1
Jul 7 16:02:45 big8 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
next prev parent reply other threads:[~2008-07-07 15:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 16:57 Lots of con-current I/O = resets SATA link? (2.6.25.10) Justin Piszcz
2008-07-05 17:35 ` Jon Nelson
2008-07-05 17:35 ` Jon Nelson
2008-07-07 15:04 ` Gerhard Wiesinger
2008-07-07 15:08 ` Gerhard Wiesinger [this message]
2008-07-07 16:04 ` Justin Piszcz
2008-07-08 6:24 ` Gerhard Wiesinger
2008-07-08 6:59 ` Gerhard Wiesinger
2008-07-08 8:35 ` Justin Piszcz
2008-07-08 10:31 ` Gerhard Wiesinger
2008-07-08 8:34 ` Justin Piszcz
2008-07-08 10:33 ` Gerhard Wiesinger
2008-07-08 13:15 ` Justin Piszcz
2008-07-09 5:37 ` Gerhard Wiesinger
2008-07-10 1:27 ` Henrique de Moraes Holschuh
2008-07-12 8:29 ` Gerhard Wiesinger
[not found] <fa.u8J+BqAcxU1mg8ob9pMBJaAHBPo@ifi.uio.no>
2008-07-05 18:38 ` Robert Hancock
2008-07-05 18:54 ` Jon Nelson
2008-07-05 19:04 ` Robert Hancock
2008-07-05 19:28 ` Justin Piszcz
2008-07-05 23:22 ` Robert Hancock
2008-07-05 23:24 ` Justin Piszcz
2008-07-06 10:31 ` Justin Piszcz
2008-07-06 12:13 ` Justin Piszcz
2008-07-06 12:42 ` Justin Piszcz
2008-07-06 19:51 ` Justin Piszcz
2008-07-07 9:45 ` Mattias Wadenstein
2008-07-07 9:57 ` Justin Piszcz
2008-07-07 18:14 ` Michal Soltys
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=alpine.LFD.1.10.0807071705490.2997@bbs.intern \
--to=lists@wiesinger.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).