Bug 124152
Summary: | hda: drive not ready for command | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pavel Tsekov <ptsekov> | ||||||||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||||||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | medium | ||||||||||||
Version: | 2 | CC: | acosta, barryn, carstenmeyer, pfrields | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2005-04-16 05:40:27 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: | |||||||||||||
Attachments: |
|
Description
Pavel Tsekov
2004-05-24 15:20:40 UTC
Created attachment 100501 [details]
A snippet from /var/log/messsages at the time the errors start
Created attachment 100502 [details]
'dmes' output
Created attachment 100503 [details]
'mount' output
It must be the kernel. I did test the system with memtest86+ and badblocks again: 1) memtest86+ (3 passes, default test) no errors 2) badblocks (badblocks -c 16384 -o /tmp/hda?.bad -p 5 -n -s /dev/hda?) no errors badblocks is from the FC2T3 CD1. I boot with the CD and type 'linux rescue' at the boot prompt. Then when asked I choose not to mount the linux partitions. Then I run the above commands for all linux partitions (hda1, hda3, hda5 and hda6 which is the swap) and no errors are produced at all for all 5 passes. The kernel on the FC2T3 is 2.6.5-1.327. So I guess it must be the culprit. I am seeing this too, on my FC1 box. Here's pops up on /var/log/messages every once in a while: Jun 27 17:15:00 dali kernel: hda: status timeout: status=0x80 { Busy } Jun 27 17:15:00 dali kernel: Jun 27 17:15:00 dali kernel: hda: drive not ready for command Jun 27 17:15:03 dali kernel: ide0: reset: success Today, after a 5-day uptime, tons of errors were listed on the logs, and it looked like the harddisk had been unplugged; most commands resulted in I/O errors or bus errors; shutdown was uneffective (_tons_ of I/O errors), so I had to manually reset the box. I will try to shutdown APM on the harddisk to see if uptime improves, because we need this machine up (it's a server). However, this is far from ideal considering that disk lifetime will be reduced by dropping APM. I am sending attached my hda info as returned by hdparm -I Please let me know if I can help in anyway with additional info. Versions: motherboard: ABIT AT7 CPU: Pentium4 2.GHz HT-enabled kernel: 2.4.26 SMP kernel boot params: hdc=ide-scsi apm=off acpi=ht noapic Best regards, Andre Created attachment 101504 [details]
Output for 'hdparm -I /dev/hda'
(this is not exactly related, but, who knows, it might give you guys a clue...) I can't seem to be able to disable APM on the drive with 'hdparm -B255', it gives me these errors: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hda: drive_cmd: error=0x04 { DriveStatusError } I turned off standby on this drive (with 'hdparm -S0'), hoping this will improve things (although I doubt it will...) Pavel, try the latest FC2 update kernel (2.6.6-1.435.2.3, if I remember correctly). If you still have the problem, then try one of the kernels from the following sources and see if you still have your problem: + rawhide (a.k.a. FC-devel) + FC 3 test 1 + http://people.redhat.com/arjanv/2.6/ Andre (and maybe Pavel too), you may want to try running "/usr/sbin/smartctl -a /dev/hda" as root, to verify that your hard drive is working properly. (This command is part of the kernel-utils package, so it will only work if that package is installed.) fixed in 2.6.9 update kernel ? Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |