Bug 62897

Summary: Failure - READ_DMA
Product: Base System Reporter: Thomas Draney <tdraney>
Component: kernAssignee: Søren Schmidt <sos>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Thomas Draney 2004-02-16 03:40:18 UTC 
kernel panics when booting up and says

mounting root from ufs:/dev/ad0s2a
ad0:Warning - READ_DMA UDMA ICRC error(retrying request) LBA=40974006
ad0:Warning - READ_DMA UDMA ICRC error(retrying request) LBA=40974006 
ad0:Failure - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=40974006    
ad0:Warning - READ_DMA UDMA ICRC error(retrying request) LBA=1
ad0:Warning - READ_DMA UDMA ICRC error(retrying request) LBA=1
ad0:Failure - READ_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED> LBA=40974006    
root mount failed

I have a Via KT333 VT8367 NB, VT8233A SB Board with a Athlon 1800+ proc.  The drive in question is a Ultra DMA 1000 atapi device.  Works under windows 2000 and NetBSD.

How-To-Repeat: restart in default mode, safe mode works but writing to disk is very slow.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2004-02-16 04:49:49 UTC 
Responsible Changed
From-To: freebsd-bugs->sos

Assign to ATA maintainer
Comment 2 rik 2004-02-28 22:12:26 UTC 
Hi,
 
    It seems that I have almost the same probelms.
On my home machine that I plan to use as a home
file-server I can't set up FreeBSD 5.2 and 5.2.1
In both cases installation hangs with trap 11, during file
system cunstructure. Nothing happens, cause I still can
run linux from that disk, where I expected to have FreeBSD.

    During fdisk I get message about wrong geomentry, as usual.
After I run commit, I get:

FAILURE READ_DMA status=51<READY,DSC,ERROR>
error=10<NID_NOT_FOUND> LBA=245529601

The reason cause my disk does not have LBA 245529601
It is only 80GB size.

Best regards,
                                Roman Kurakin
Comment 3 Søren Schmidt freebsd_committer freebsd_triage 2004-08-16 12:58:01 UTC 
State Changed
From-To: open->closed

ICRC errors are almost certainly because of cable/connector problems. 
Make sure you have spec'd 80conductor cables and have turned them 
the right way around (blue connector in controller ned, grey/black  
for the slave/master device.
Comment 4 noisex 2006-02-09 13:22:37 UTC 
I also get the similiar problem:
 
Feb  9 15:17:53 dreamland kernel: ad6: FAILURE - READ_DMA
status=61<READY,DMA_READY,ERROR> error=4<ABORTED> LBA=125440
Feb  9 15:17:53 dreamland kernel:
g_vfs_done():stripe/data[READ(offset=192806912, length=16384)]error = 5

It's a probem with HDD or partitions geometry?