From: Thomas Jackowski <aXe@hadiko.de>
To: linux-ide@vger.kernel.org
Subject: Errors on ICH10R with Seagate HDDs
Date: Thu, 02 Apr 2009 13:32:02 +0200 [thread overview]
Message-ID: <49D4A232.3090504@hadiko.de> (raw)
Hi,
I assume a problem between Seagate Drives and the ATA Drivers.
Chipset is a ICH10R, but this problems has been seen on a ICH9 also.
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.11
Device Model: ST31000340AS
Serial Number: 6QJ03QBN
Firmware Version: SD1A
User Capacity: 1,000,203,804,160 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Fri Mar 27 10:58:37 2009 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
This is /dev/sdc. /dev/sdd and /dev/sde is the same model with the same
Firmware. I'm using a RAID5 on these 3 HDDs.
Because of the Seagate Firmware Bug I had to upgrade the firmware from
'SD15' to 'SD1A'. The upgrade was successful.
Before the upgrade there were no problems, after the upgrade I have
trouble like this:
[14144.875924] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[14144.875931] ata4.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0
pio 512 in
[14144.875932] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask
0x4 (timeout)
[14144.875934] ata4.00: status: { DRDY }
[14144.875938] ata4: hard resetting link
[14145.362708] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[14145.526248] ata4.00: configured for UDMA/133
[14145.526261] ata4: EH complete
[14145.550243] sd 3:0:0:0: [sdd] 1953523055 512-byte hardware sectors
(1000204 MB)
[14145.550263] sd 3:0:0:0: [sdd] Write Protect is off
[14145.550265] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[14145.550282] sd 3:0:0:0: [sdd] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[507139.744594] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action
0x6 frozen
[507139.744602] ata5.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
[507139.744603] res 40/00:00:be:ac:54/00:00:1b:00:00/e0 Emask
0x4 (timeout)
[507139.744606] ata5.00: status: { DRDY }
[507139.744611] ata5: hard resetting link
[507140.247396] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[507140.251384] ata5.00: configured for UDMA/133
[507140.251384] ata5: EH complete
[507140.253668] sd 4:0:0:0: [sde] 1953523055 512-byte hardware sectors
(1000204 MB)
[507140.253681] sd 4:0:0:0: [sde] Write Protect is off
[507140.253683] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
[507140.253701] sd 4:0:0:0: [sde] Write cache: enabled, read cache:
enabled, doesn't suppo
rt DPO or FUA
[507453.049511] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action
0x6 frozen
[507453.049519] ata4.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0
[507453.049520] res 40/00:00:3e:e0:54/00:00:1b:00:00/e0 Emask
0x4 (timeout)
[507453.049523] ata4.00: status: { DRDY }
[507453.049529] ata4: hard resetting link
[507453.547144] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[507453.843855] ata4.00: configured for UDMA/133
[507453.843855] ata4: EH complete
[507453.871434] sd 3:0:0:0: [sdd] 1953523055 512-byte hardware sectors
(1000204 MB)
[507453.872475] sd 3:0:0:0: [sdd] Write Protect is off
[507453.872475] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[507453.872475] sd 3:0:0:0: [sdd] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
Where is the problem?
Bye, Thomas
next reply other threads:[~2009-04-02 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 11:32 Thomas Jackowski [this message]
2009-04-09 18:09 ` Errors on ICH10R with Seagate HDDs Tejun Heo
2009-04-17 9:10 ` Thomas Jackowski
2009-04-19 8:56 ` Tejun Heo
2009-04-25 10:22 ` Thomas Jackowski
2009-04-26 2:00 ` Tejun Heo
2009-06-16 1:59 ` Thomas Jackowski
2009-06-17 6:33 ` Tejun Heo
2009-06-22 18:40 ` Thomas Jackowski
2009-06-26 2:33 ` Tejun Heo
2009-06-29 8:17 ` Thomas Jackowski
2009-06-29 14:09 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2009-10-28 15:26 Thomas Jackowski
2009-11-09 15:02 ` Tejun Heo
2009-11-09 19:39 ` Thomas Jackowski
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=49D4A232.3090504@hadiko.de \
--to=axe@hadiko.de \
--cc=linux-ide@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.