[wplug] help interperting errors in messages log

[Mike Griffin]

A google search came up with this from a post on a forum. Maybe this  
will be an indication? The forum ended here and never stated if the fix  
worked or not, might be worth the try though.

  	 > i found this in an older messages file and never caught it
   	>
   	> messages.1:Nov 22 02:06:25 fang kernel: zone DMA has max 32 cached  
pages.
   	> messages.1:Nov 22 02:06:25 fang kernel: ide0: BM-DMA at  
xb800-0xb807, BIOS
   	> settings.1: hda:DMA, hdb:DMA messages.1:Nov 22 02:06:25 fang  
kernel: ide1: BM-DMA
   	> at xb808-0xb80f, BIOS settings: hdc:pio, hdd:pio messages.1:Nov 22  
02:06:25 fang
   	> kernel: hda: 160086528 sectors (81964
   	> MB) w/2048KiB Cache, CHS=9964/255/63, UDMA(33) messages.1:Nov 22  
02:06:25 fang
   	> kernel: hdb: 60036480 sectors (30739
   	> MB) w/1916KiB Cache, CHS=3737/255/63, UDMA(33)
   	>
   	>
   	> and recently caught this:
   	>
   	> messages:Dec 21 08:55:21 fang kernel: hdd: dma_intr: error=0x84 {  
DriveStatusError
   	> BadCRC } messages:Dec 21 08:55:23 fang kernel: hdd: dma_intr:  
status=0x51 {
   	> DriveReady SeekComplete Error } what do you think, guys?

	Your device at hdd is not responding in a timely manner. This can  
often be attributed
	to a bad ide cable.





On Tuesday, August 19, 2003, at 11:30  AM, John Harrold wrote:

> Sometime in August Vanco, Donald assaulted the keyboard and produced:
>
> | squeegy-wplug at squeegy.org wrote:
> | > I have been getting errors daily like the below:
> | >
> | > 3 Time(s): end_request: I/O error, dev 03:02 (hda), sector 1017689
> | > 14 Time(s): hda: read_intr: error=0x01 { AddrMarkNotFound },
> | > LBAsect=1226534, sector=1017689
> | > 2 Time(s): hda: read_intr: error=0x40 { UncorrectableError },
> | > LBAsect=1226534, sector=1017689
> | > 16 Time(s): hda: read_intr: status=0x59 { DriveReady SeekComplete
> | > DataRequest Error }
> | > 3 Time(s): ide0: reset: success
> | 	
> | 	It means your hard drive is very likely dying.  While there are
> | steps that can be taken from a filesystem and manufacturer bad block  
> level,
> | but the fact is that the physical media on the drive is likely  
> breaking
> | down.  You can put off the inevitable for a while, but your disk is  
> dying.
> |
> | 	If hda is simply a CD - it's bad media.
> |
>
> on a similar note. i've had this error for a couple years on a  
> workstation
> in our lab. since all the important data is nfs mounted i didn't really
> care so much if the drive died.
>
> Aug 18 kernel: had: dma_intr: status=0x51 { DriveReady SeekComplete  
> Error }
> Aug 18 kernel: had: dma_intr: error=0x84  { DriveStatusError BadCRC }
>
> can anyone shed some light on what this might be?
>
>
> --  
> ----------------------------------------------------------------------- 
> ---
>                                                | /"\
>  john harrold                                  | \ / ASCII ribbon  
> campaign
>       jmh at member.fsf.org                    |  X  against HTML mail
>            the most useful idiot               | / \
> ----------------------------------------------------------------------- 
> ---
>  What difference does it make to the dead, the orphans, and the  
> homeless,
>  whether the mad destruction is brought under the name of  
> totalitarianism or
>  the holy name of liberty and democracy?
>  --Gandhi
> ----------------------------------------------------------------------- 
> ---
> gpg --keyserver keys.indymedia.org --recv-key F65A739E
> ----------------------------------------------------------------------- 
> ---
> <mime-attachment>