Bug 81403
Summary: | kernel-BOOT-2.4.18-19.8.0 causes { DriveReady SeekComplete Error } | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <redhat> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | karl+rhbugzilla, lamont_gilbert |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:22 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
Need Real Name
2003-01-09 01:49:39 UTC
I was geeting the following error using both 2.4.18-19.8.0 and 2.4.18-14 kernals Excert from the messages log file. Jan 26 11:38:08 localhost kernel: da: read_intr: status=0x51 { DriveReady SeekComplete Error } Jan 26 11:38:08 localhost kernel: hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=39118142, sector=15647114 Jan 26 11:38:08 localhost kernel: ide0: reset: success this would reperat a number of times before completeing the boot process. I am unable to mount any of the windows/dos partitions using. I am running a PII 350 with 384 meg Award bios and Intel 440BX chipset of memory hda is a 20g western digital and hdb is segate 40g hda is divided into 4 partitions and is running Windows 98SE hdb is running Red Hat 8 Bootloader GRUB I am unable to reproduce the error. I believe it may be a conflict/error in how windows reports the partion start/finsh points comparered to how linux reads the same disk geometry. It may also be that windows stores the partition information different to the BIOS and Linux ignores the bios and reads the drive information directly without referece to windows and that creates the conflic and the above error message. I receintly loaded Partition Magic 6 on the windows system and on first running this program it reported incorrect/overlapping? start finish sectors for each partition on the primary hard disk drive the program automaticly repaired/fixed each instance. The system still boots and windows runs without problem before and after the ? fix. I no longer have the error listing on booting or logging off and I am able to mount and read dev/hda1 without and problems. Had a similiar problem on a RH9.0 install. Fix was to put the CDrom and hard drive on seperate IDE channels. I also get this on a recently upgraded (from 7.3) RH9 install with kernel 2.4.20-19.9 hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } I am getting this on RH9 2.4.20-27.9, but I also experienced before I upgraded to this latest kernel. I have 3 drives and 1 cdrw. 2 of the drives are on a RAID controller but not in hardware raid mode. 1 of the drives shares its cable with a 2nd older larger slightly slower drive. the 2 main drives are software raided Maxtor 6E040L0 /dev/hde and /dev/hdg and /dev/hdg and /dev/hdh share a cable. (hdh Maxtor 32049H2) The cdrom is on a completely seperate IDE channel and mounted as SCSI /dev/scd0 havent solved the problem yet. all of the sudden while I slept the drives started having a fit. only lasted a few minutes before it appearantly locked. I have no dual booting, this is a dedicated box which is on runlevel 3. Jan 8 03:53:39 erasmus kernel: hdg: dma_timer_expiry: dma status == 0x61 Jan 8 03:53:39 erasmus kernel: hde: dma_timer_expiry: dma status == 0x21 Jan 8 03:53:50 erasmus kernel: hdg: error waiting for DMA Jan 8 03:53:50 erasmus kernel: hdg: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } Jan 8 03:53:50 erasmus kernel: Jan 8 03:53:50 erasmus kernel: hde: error waiting for DMA Jan 8 03:53:50 erasmus kernel: hde: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } Jan 8 03:53:50 erasmus kernel: Jan 8 03:53:50 erasmus kernel: blk: queue c03c664c, I/O limit 4095Mb (mask 0xffffffff) Jan 8 03:53:50 erasmus kernel: blk: queue c03c61e8, I/O limit 4095Mb (mask 0xffffffff) Almost forgot to add the very important fact that this is a custom built kernel from the RH kernel-source. Well its not actually custom, I just copied over the athlon.config and used that as is with simple open and close in menuconfig. RHL 8.0 is EOL. I don't know why is allowed to open bugzilla bugs for RHL 8 and 7.x after 31 Dec 2003. does not look like there was ever a formal solution. or any resolution. I get this problem on a RH9 kernel on occasion. but not on boot. and not related to kernel-BOOT appearantly. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |