"Drive not ready for command" message in RH 7.2

"Drive not ready for command" message in RH 7.2

Post by Steve Brow » Tue, 27 Nov 2001 18:05:58



Hi all,

I've been having sporadic failures of my Gnome installation in the
RedHat 7.2 installation I just did on my PIII system.  I'm wondering
if it is related to the above message I'm seeing in the dmesg text.

My Gnome problem is, briefly, that sometimes the desktop comes
up just fine with all the icons and startup programs, but at other
times I get panel crash messages, taskbar fails to appear, icons
fail to appear, or nautilus fails to start up.  This can happen at a
fresh boot and run of startx.  Sometimes rebooting will set things
right, sometimes not.  I did not have this problem with RH 6.x and
Gnome on this machine previously.

Installation of 7,2 was a completely fresh install, repartition of the
HD, no hardware changes.  I selected the ext2fs for all HD partitions
on installation and did the check for bad blocks with reformat of each
partition.


Linux omega.msc.home 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686
unknown

Anyway, the problem I see in the dmesg is as follows:
at the end of dmesg I see the following:

   .
   .
  .
ide-floppy driver 0.97
hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hda: drive not ready for command
hdb: ATAPI 32X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
smb_trans2_request: result=-104, setting invalid
smb_retry: successful, new pid=2300, generation=2
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
<end of dmesg>

It's the second, third and eighth lines that worry me.  What are they
trying to tell me?  What corrective action is necessary?

I was going to post the entire dmesg, but it is really too long for a
post here I would imagine (148 lines).  I'm not sure what is most
pertinent, but I'd be happy to post further relevant info.  Here's
part of the dmesg about the IDE (about 1/2 way thru):

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz PCI bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 21
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:pio
hda: IBM-DJNA-371350, ATA DISK drive
hdb: CD-ROM 45X, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: 26520480 sectors (13578 MB) w/1966KiB Cache, CHS=1650/255/63,
UDMA(33)
ide-floppy driver 0.97
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 >

Thanks for any help and/or insight you can provide.

Steve Brown
(remove NOSPAM for direct e-mail)

 
 
 

"Drive not ready for command" message in RH 7.2

Post by Yan Seine » Tue, 27 Nov 2001 21:00:18


I seem to remember something about this.  I had a drive that was doing
this at one time.  Basically, it's refusing to talk to the computer.
Why?  It may be dying,  it may not like DMA or other hdparm settings, it
may be going to sleep and not waking up properly.

Disable DMA, APM, and make sure you are not using any fancy stuff with
hdparm.  Also make sure that you are using the appropriate IDE contrller
driver in the kernel.

If all of the above checks out, replace the drive.

--Yan



> Hi all,

> hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hda: drive not ready for command


 
 
 

"Drive not ready for command" message in RH 7.2

Post by Steve Brow » Wed, 28 Nov 2001 14:25:38


Thank you Yan!

I went into the BIOS setup and disabled the UltraDMAMode setting and
left it at PIO Mode 4, per your recommendation.  Here's what the
relevant part of the dmesg now shows:
   .
   .
   .
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz PCI bus speed for PIO modes; override with
idebus=xx
PIIX4: IDE controller on PCI bus 00 dev 21
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:pio
hda: IBM-DJNA-371350, ATA DISK drive
hdb: CD-ROM 45X, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: 26520480 sectors (13578 MB) w/1966KiB Cache, CHS=1650/255/63,
UDMA(33)
ide-floppy driver 0.97
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 >
   .
   .
   .
Odd that the ide0 shows hda:DMA though, as that's the drive for
which I turned off Ultra DMA in the BIOS settings...  Also the line:
hda: 26520480 sectors (13578 MB) w/1966KiB Cache, CHS=1650/255/63,
UDMA(33)
confuses me, but then I am easily confused.

I will watch this over the next several bootups to make sure the
"drive not ready" doesn't come back.  So far Gnome has been
behaving too, for the last two boots...

Thanks again for your help.

Gratefully,

Steve Brown

On Mon, 26 Nov 2001 07:00:18 -0500, "Yan Seiner"


>I seem to remember something about this.  I had a drive that was doing
>this at one time.  Basically, it's refusing to talk to the computer.
>Why?  It may be dying,  it may not like DMA or other hdparm settings, it
>may be going to sleep and not waking up properly.

>Disable DMA, APM, and make sure you are not using any fancy stuff with
>hdparm.  Also make sure that you are using the appropriate IDE contrller
>driver in the kernel.

>If all of the above checks out, replace the drive.

>--Yan



>> Hi all,

>> hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>> hda: drive not ready for command

 
 
 

1. "DRIVE NOT READY" trying to boot up RedHat 7.2 /w GRUB

I had an old Pentium 100, 1GB IDE hard drive with Win95 previously
installed on it.  Formatted the thing and decided to install RH 7.2.

I went through the install numerous times without problems.  But at
the end of the install, when it would try to boot off the hard disk,
I'd *ALWAYS* get the following message:

DRIVE NOT READY
Insert BOOT diskette in A:
Press any key when ready

When I'd boot off the RH installation floppy and used the "rescue"
option, I could mount the partitions and see the entire hard disk.
But for some reason, it would refuse to boot off the hard drive.

Finally figured out the problem.  In the AMI BIOS (1994), the
"graphical" BIOS setup screen had been configured so the first hard
disk was set to "SCSI"!  I simply had to select "Setup -> Standard ->
Master Disk -> USER" instead of "Setup -> Standard -> Master Disk ->
SCSI" which had somehow gotten selected.  Once I did this, I
re-installed one last time, and I no longer have any problems booting.

(I'm posting this not to get replies, but for the purpose of logging
what happend in case anyone else happens to do a usenet search of this
scenario.)

Stephane Charette

2. 'bounce' utility for OpenBSD

3. command not found after RH 7.2 kernel upgrade via "Upgrade Agent"

4. LPI question

5. ps command failed and produced "Bus error" or "Segmentation fault" messages

6. Just where IS my printer?

7. GETSERVBYNAME()????????????????????"""""""""""""

8. How to Embed Perl into Unix?

9. constant "Device not ready" messages

10. "atapi1.0:controller not ready for cmd" CD ROM error message

11. "find" and "locate" commands not working, linux RH5.2

12. Enterprise 450 down "Drive Not Ready"

13. "brctl" command not working, how to create "brctl" file?