Bug 247296
Summary: | dmesg error messages for SATA drive. | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Roger Cowles <rojcowles> | ||||||||||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||
Priority: | low | ||||||||||||||
Version: | 6 | CC: | jonstanley | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | i386 | ||||||||||||||
OS: | Linux | ||||||||||||||
Whiteboard: | |||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2008-02-08 04:27:30 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Bug Depends On: | |||||||||||||||
Bug Blocks: | 427887 | ||||||||||||||
Attachments: |
|
Description
Roger Cowles
2007-07-06 18:37:25 UTC
Created attachment 158684 [details]
dmesg output
Created attachment 158723 [details]
A later dmesg log file, this time with timeout/retry message on the drive
I started seeing drive reset messages that make the SATA drive unavailable for
periods of time. This after I noticed that copying backup data from an attached
USB HD to the SATA drive had slowed from ~700Mb a minute down to ~70Mb/minute
or thereabouts (very unscientific measurement, I had a while loop doing df -k .
on the SATA drive with a sleep 60 to give a minutes pause)
Created attachment 158735 [details]
lspci log file
Created attachment 158736 [details]
lspci -vv log file
Created attachment 158737 [details]
uname -a ouput
Bought a Promise Technology, Inc. PDC40775 (SATA 300 TX2plus) (rev 02) to replace the Silicon Image, Inc. SiI 3512 Syba controller (working on the principle that I had a bad controller card) but the SATA errors persisted. Downloaded a 2.16.9 Kernel from kernel.org, used the FC6 config-2.6.18-1.2798.fc6 configuration to build the kernel and installed as my default kernel. The disk errors have vanished and I can now reliably access either SATA drive locally on the server or from Samba shares. Not sure how viable a workaround this is for most people though. I'd also tried kernels 2.6.18, 2.6.20 and 2.6.22 and all of these showed the above disk errors. (In reply to comment #8) > I'd also tried kernels 2.6.18, 2.6.20 and 2.6.22 and all of these showed the > above disk errors. Were the latest FC6 2.6.22 kernels tried, or just the vanilla ones? I tried an intermediate FC6 2.6.22 from updates-testing during the rebase from 2.6.20, 2.6.22.1-32.fc6, and then 2.6.22.2-42.fc6 from the standard updates area. The 2.6.16.9 is the only vanilla + FC6 config kernel I've tried so far. Having said all that I later got a ton of disk errors copying some data back from a backup onto one of the two WD SATA drives while running the 2.6.16.9 kernel so it looks like I jumped to a conclusion too early :( I'm planning on hooking these drives up to my Win XP box and using the Windows based WD diagnostic tools to check out both of my drives as it may be possible that both were either duff when I got them or went duff when they were in my server. If it turns out that they are bad (what are the odds ? Maybe not that high ...) I'll RMA them as they're both under warranty and start over with new drives. Maybe I can then see if its a kernel driver issue between 2.6.16 and 2.6.{18,20,22} or it was bogus hardware all along. (This is a mass-update to all current FC6 kernel bugs in NEW state) Hello, I'm reviewing this bug list as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug, however this version of Fedora is no longer maintained. Please attempt to reproduce this bug with a current version of Fedora (presently Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a few days if there is no further information lodged. Thanks for using Fedora! Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA, since no information has been lodged for over 30 days. Please re-open this bug or file a new one if you can provide the requested data, and thanks for filing the original report! |