Bug 492232 (ATA, errors, mult-disks)
Summary: | 2.6.18-128.el5.3_x86_64 reports some ATA errors with multi-disks | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Grace <sysolve> |
Component: | kernel | Assignee: | David Milburn <dmilburn> |
Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | dzickus, jane.lv |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-03-30 17:05:09 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: |
Description
Grace
2009-03-26 01:39:08 UTC
Hi, The RHEL 5.3 ahci driver added support for enclosure management which manipulates the drive LEDs, we are actually working on BZ 488471 were drive LEDs are reporting incorrect status for ich9r and ich10 when configured in ahci mode (though we haven't seen any device errors in dmesg). Would you please attach you full dmesg log after booting and the output of "lspci -xxvvv"? Also would you try disabling ahci_em_messages in your /etc/modprobe.conf and rebuild your initrd? (Or, I can build you a test kernel). options ahci ahci_em_message=0 Thanks for your prompt response. Just as you said, the error status reports of LEDs also existed for my drives. About the original issue I reported based on my several times of OS-reinstalling experiments, it seems that I have fixed it although I am not sure what's the cause of the fix. My solution to bypass the reported issue as follows: I pulled the 2nd SATA drive out and rebooted the OS, the problem was still there. Then I re-inserted the 2nd SATA drive back and re-installed the OS image, the problem went away. From my experience, the root cause should not be in the kernel which was my initial thought. Thanks again for your time and help. Ok, thank you for the update. |