Bug 27689 - Drive Status Errors on bootup (UDMA66)
Drive Status Errors on bootup (UDMA66)
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-14 20:51 EST by Cliff Hairston
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-05 19:40:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Cliff Hairston 2001-02-14 20:51:28 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)


I seem to be getting constant errors on systems with UDMA66 or 100 drives. 
I've switched between standard, ATA-66, and ATA-100 cables and still 
recieve the errors. I'll try a new kernel within the next couple of days 
to confirm if it's the kernel or another problem

Reproducible: Always
Steps to Reproduce:
1. Restart system
2.
3.
	

Actual Results:  Drive Status Error (drive not ready) for about 5 seconds 
then everything goes on as normal.
Comment 1 Arjan van de Ven 2001-02-15 06:05:10 EST
Use only the 80 wire (66/100 Mhz cables)!!

What controller do you have ? (if unsure, please paste the lspci output)
What drives ? ("cat /proc/ide/hda/model" (or hdb etc) will tell you)
Are you using hdparm or something similar?
Do you have something "append"ed in lilo.conf regarding IDE?
Can you attach your dmesg output please?
Comment 2 Alan Cox 2001-05-19 15:50:00 EDT
Not ready, timeout, working isnt necessarily indicative of anything more than
very aggressive power management by the BIOS

Note You need to log in before you can comment on or make changes to this bug.