Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

HDD problem - hda: status timeout: status=0xd0 { Busy }



Replacing the cable didn't help; it's still giving the error.

I found a message through google where someone says the error indicates
that DMA got disabled.

    http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-11/0679.html

hdparm -I showed

        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
             Cycle time: min=120ns recommended=120ns

I tried

    sudo hdparm -d1 -X udma5 /dev/hda

to see what would happen; there was no change, the error still happens
every 30 seconds. Output was as follows:

    sudo hdparm -d1 -X udma5 /dev/hda

    /dev/hda:
     setting using_dma to 1 (on)
     HDIO_SET_DMA failed: Operation not permitted
     setting xfermode to 69 (UltraDMA mode5)
     using_dma    =  0 (off)



Ward Vandewege wrote:
> On Fri, Jun 23, 2006 at 02:50:49PM -0400, John Abreau wrote:
>> I'm setting up an HP ProLiant DL140 G2 server, and I'm seeing some
>> serious performance degradation. The logs are filling up with the
>> following error:
>>
>> Jun 23 14:40:20 shapieron kernel: hda: status timeout: status=0xd0 { Busy }
>> Jun 23 14:40:20 shapieron kernel:
>> Jun 23 14:40:20 shapieron kernel: ide: failed opcode was: unknown
>> Jun 23 14:40:20 shapieron kernel: hda: no DRQ after issuing WRITE
>> Jun 23 14:40:23 shapieron kernel: ide0: reset: success
>>
>> The error appears at roughly 30-second intervals.
>>
>> I found a suggestion through google to try fiddling with hdparm,
>> particularly with the -m option. hdparm -I showed
>> R/W multiple sector transfer: Max = 16, so I tried
>> "hdparm -m16 /dev/hda", but this didn't fix the problem.
>>
>> I'm looking at the hdparm man page now, but I can't figure out
>> what to try next. Any ideas?
> 
> Have you tried a different cable? This kind of error can be caused by bad
> cables.
> 
> Ward.
> 


-- 
John Abreau / Executive Director, Boston Linux & Unix
ICQ 28611923 / AIM abreauj / JABBER jabr at jabber.org / YAHOO abreauj
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org