WARNING - READ_DMA UDMA ICRC error

[Tamas (septi) Gal]

Yesterday I upgraded my hardware from a Pentium2 400mhz setup (running
freebsd 5.4) to a Sempron 2.8ghz and installed freebsd 6.1 on it (the
32bit version).
There are 4 harddisks attached to the IDE-controllers:

ad0: 6150MB  at ata0-master UDMA66
ad1: 38166MB  at ata0-slave UDMA100
ad2: 78167MB  at ata1-master UDMA133
ad3: 38166MB  at ata1-slave UDMA100

ad1 and ad3 are the same and both contain important data.
After the installation of freebsd I noticed a lot of UDMA-errors:

ad1: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63
ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63
ad1: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=63
ad3: WARNING - WRITE_DMA UDMA ICRC error (retrying request) LBA=63

After decreasing the speed of UDMA (on ad1 and ad3)  in the
BIOS-Setup, ad1 worked fine, without any errors, but ad3 still
produces the same error-messages and is not mountable:

(14:51) root (/home/septi) %mount /dev/ad3s1 /test
mount: /dev/ad3s1: Input/output error

Here the dmesg output:

ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=12063
ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=12063
ad3: FAILURE - READ_DMA status=51
error=84 LBA=12063
g_vfs_done():ad3s1[READ(offset=6144000, length=4096)]error = 5
ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63
ad3: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=63
ad3: FAILURE - READ_DMA status=51 error=84 LBA=63

I also replaced the IDE-cable but it changed nothing...

Does anybody have an idea?

--
everyone's pink on the inside - http://www.nuffinsirius.de
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Emanuel Strobl]

Am Mittwoch, 10. August 2005 19:48 CEST schrieb Unix:
> O. Hartmann wrote:
> > Mike Jakubik wrote:
> >> On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:
> >>> There are Maxtor MaXLine II and III, and perhaps several other
> >>> models, that are supposed to work 24/7.
> >>
> >> Right, i have a dead 250GB Maxline Plus II drive on my desk, only
> >> after about 1.5 years. At least its still on warranty.
> >
> > On the other hand: In the department for physics of the athmosphere,
> > where I built six years ago a server for meteorological data, a RAID-5
> > with 4 older IBM U160 SCSI discs still works - 24/7. Never had a
> > problem!
>
> I still own old 1-2 GB old SCSI disks and these are still working, I
> also had an old 500mb SCSI disk that was in an old Mac that also worked
> but I trashed it since it was that old and no longer of use...

I have an old 700 MB WD IDE drive that still works fine and has about 6 
years 24/7 survived. And I also had a 2000$ 73G SCSI IBM drive that lasted 
for about 5 monthas and was that damadged that Convar sent it back without 
one byte recovered! And I don't want to remember the 80GB WD drive that 
lasted for 2 months..
Please, don't discuss about SCSI/ATA reliability, there are bad 
designed/produced drives and there are good ones. You can't tell before, 
only experience counts.
I can say only good things about Seagates Barracuda 7200.8 drives for 
example. Some dozends are running for two years without _any_ single drive 
failed. Also the Samsung (p)ATA drives are still running without any 
single failure. And WDs once were perfect drices, but they also produced 
crap. So you can't even be sure by vendor!

-Harry

P.S.: I'm planning to bring up a FreeBSD site which reflects hardware 
compatibility experiences as well as long term experiences. I'll be back 
if I have more...


pgpKca9tdzt07.pgp
Description: PGP signature

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

O. Hartmann wrote:


Mike Jakubik wrote:


On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:



There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.




Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on warranty.



On the other hand: In the department for physics of the athmosphere, 
where I built six years ago a server for meteorological data, a RAID-5 
with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem!


I still own old 1-2 GB old SCSI disks and these are still working, I 
also had an old 500mb SCSI disk that was in an old Mac that also worked 
but I trashed it since it was that old and no longer of use...

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[O. Hartmann]

Mike Jakubik wrote:

On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:



There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.



Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on warranty.


On the other hand: In the department for physics of the athmosphere, 
where I built six years ago a server for meteorological data, a RAID-5 
with 4 older IBM U160 SCSI discs still works - 24/7. Never had a problem!

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

It's sad isn't it, Mike..I don't know what the hd manufacturers are 
doing to the HD drives..ok, the systems get faster, there's usually bad 
cooling unless you build your own system...but even if you get enough 
cooling that won't change a thing some hds are prone to die an early 
death such as the Maxtors..I used to love Maxtor and hated Seagate now 
it's the other way around but my #1 HD still is Western Digital...I have 
an old Maxtor drive here 6 gb that's still running perfectly, just like 
3 40gb Seagate Barracuda and Western Digital Caviar...I had a 120gb 
Hitachi that died after 1 yr of use...



Mike Jakubik wrote:


On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:

 


There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.
   



Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on warranty.



 



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Mike Jakubik]

On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:

> There are Maxtor MaXLine II and III, and perhaps several other models,
> that are supposed to work 24/7.

Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on warranty.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Igor Robul]

Joel Rees wrote:

I have two which reliably fail if you put TWO disks on them in a  
gmirror

config within minutes of starting a "make buildworld".



Pardon the interruption, but is this two drives on one channel?


Two drives can not be on one channel on SATA controller.
Also try "Sii3112 Windows trouble" on any search site  and you'll find 
many links to problem reports.
SII3112 IS NOT Server (even small-server) chipset. It does not work well 
with semi-heavy load.
Of course, you can install and use FreeBSD, Linux, Windows on it, just 
dont put load on it with 2 disks.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request)LBA=11441599

[Mathijs Brands]

On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:

>I thought the WD Raptors were supposed to replace the SCSI for that
>purpose. I used to run one in a Powermac and performance wise it behaved
>very well, unfortunately I haven't had the chance to test the 30 or 70
>GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7
>or server use anyway
>
I have a FreeBSD 6.0-BETA2 machine that's using a WD Raptor 36 GB using
the on-board controller (VIA 8237) of the Asus A7V880 motherboard and it
works perfectly. The most taxing thing it runs is the occasional
buildworld or (re)build of KDE3 though...

Cheers,

Mathijs
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Dmitry Mityugov wrote:


On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
 


Dmitry Mityugov wrote:

   


On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
...


 


I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't had the chance to test the 30 or 70
GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7
or server use anyway


   


...

There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.



 


Yes, but I don't like Maxtor drives, the ones I've used always failed
after a year or less than a year...
   



Western Digital produces similar drives as well - from
http://store.westerndigital.com/product.asp?sku=2700729: ..."24x7 100%
duty cycle–the highest available reliability rating on high capacity
drives"...

 


thanks, I need to get some new drives anyway...and WD was on my list...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Dmitry Mityugov]

On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
> Dmitry Mityugov wrote:
> 
> >On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
> >...
> >
> >
> >>I thought the WD Raptors were supposed to replace the SCSI for that
> >>purpose. I used to run one in a Powermac and performance wise it behaved
> >>very well, unfortunately I haven't had the chance to test the 30 or 70
> >>GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7
> >>or server use anyway
> >>
> >>
> >...
> >
> >There are Maxtor MaXLine II and III, and perhaps several other models,
> >that are supposed to work 24/7.
> >
> >
> >
> Yes, but I don't like Maxtor drives, the ones I've used always failed
> after a year or less than a year...

Western Digital produces similar drives as well - from
http://store.westerndigital.com/product.asp?sku=2700729: ..."24x7 100%
duty cycle–the highest available reliability rating on high capacity
drives"...

-- 
Dmitry Mityugov, St. Petersburg, Russia
I ignore all messages with confidentiality statements

"We live less by imagination than despite it" - Rockwell Kent, "N by E"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Dmitry Mityugov wrote:


On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
...
 


I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't had the chance to test the 30 or 70
GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7
or server use anyway
   


...

There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.

 

Yes, but I don't like Maxtor drives, the ones I've used always failed 
after a year or less than a year...

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Dmitry Mityugov]

On 8/10/05, Unix <[EMAIL PROTECTED]> wrote:
...
> I thought the WD Raptors were supposed to replace the SCSI for that
> purpose. I used to run one in a Powermac and performance wise it behaved
> very well, unfortunately I haven't had the chance to test the 30 or 70
> GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7
> or server use anyway
...

There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.

-- 
Dmitry Mityugov, St. Petersburg, Russia
I ignore all messages with confidentiality statements

"We live less by imagination than despite it" - Rockwell Kent, "N by E"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Unix]

Joel Rees wrote:



On 平成 17/08/10, at 7:36, O. Hartmann wrote:


[...] When is SCSI back for desktops?



I vote for that.

In my opinion, ATA is primarily for home media systems, if that.

Joel Rees   <[EMAIL PROTECTED]>
digitcom, inc.   株式会社デジコム
Kobe, Japan   +81-78-672-8800
**  **




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

I thought the WD Raptors were supposed to replace the SCSI for that 
purpose. I used to run one in a Powermac and performance wise it behaved 
very well, unfortunately I haven't had the chance to test the 30 or 70 
GB WD Raptor SATA in FreeBSD..S/ATA drives should never be used for 24/7 
or server use anyway, they die after a while, in my case, two 80gb 
seagate drives after 1.5 yrs with proper cooling...thing is that SCSI 
drives are not affordable to the regular home server user...if they 
were, I bet more people would use them so that's why the current 
alternatives are ATA and SATA and SATA Raptors.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Joel Rees]

On 平成 17/08/10, at 7:36, O. Hartmann wrote:


[...] When is SCSI back for desktops?


I vote for that.

In my opinion, ATA is primarily for home media systems, if that.

Joel Rees   <[EMAIL PROTECTED]>
digitcom, inc.   株式会社デジコム
Kobe, Japan   +81-78-672-8800
**  **




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[O. Hartmann]

Chuck Swiger wrote:


O. Hartmann wrote:
[ ... ]

One of  my SATA disks, the SAMSUNG SP2004C seems to show errors 
during operation (and also showd under 5.4-RELEASE-p3).

Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely.

Is this a operating system bug or is this message an evidence of 
defective hardware?


You can also run a "dd if=/dev/ad10 of=/dev/null bs=8192" to do a full 
read test under FreeBSD, and see how many CRC errors show up.



I did so and I ran into a crash of the system ...

I changed the cabling, did it again and until now nothing happend ... 
hope it was only a cabling issue. The first time I use ATA/SATA and now 
these experiences ... When is SCSI back for desktops?

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Chuck Swiger]

O. Hartmann wrote:
[ ... ]
One of  my SATA disks, the SAMSUNG SP2004C seems to show errors during 
operation (and also showd under 5.4-RELEASE-p3).

Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely.

Is this a operating system bug or is this message an evidence of 
defective hardware?


Back up any data you care about now.  Use the smartmontools port or hunt down a 
utility from Samsung which'll do a surface test (read only, nondestructive).


You can also run a "dd if=/dev/ad10 of=/dev/null bs=8192" to do a full read 
test under FreeBSD, and see how many CRC errors show up.


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[O. Hartmann]

Mike Tancsa wrote:

At 08:25 PM 08/08/2005, O. Hartmann wrote:


Hello.

My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 
boxed (see dmesg).
One of  my SATA disks, the SAMSUNG SP2004C seems to show errors during 
operation (and also showd under 5.4-RELEASE-p3).

Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely.

Is this a operating system bug or is this message an evidence of 
defective hardware?



You can probably confirm a hardware issue with the smartmon tools.  
(/usr/ports/sysutils/smartmontools).


It was quite handy the other day for us to narrow down a problem between 
a drive tray and the actual drive.  We started to see


Aug  3 02:02:49 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=391423
Aug  3 02:03:00 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=2304319
Aug  3 02:03:10 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=2312927
Aug  3 02:03:17 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=2308639
Aug  3 02:03:26 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=2309855
Aug  3 02:03:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=2348359
Aug  4 12:12:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=1528639
Aug  4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 
retries left) LBA=1530031
Aug  4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (1 
retry left) LBA=1528639

Aug  4 12:13:04 verify1 kernel: ad0: FAILURE - READ_DMA timed out
Aug  4 12:13:04 verify1 kernel: spec_getpages:(ad0s1a) I/O read failure: 
(error=5) bp 0xd630b4fc vp 0xc2640d68


Yet when we read the actual error info off the drive via smartctl -a 
ad0, it was clean.  So it pointed to the drive tray which we swapped and 
all was well.  In other situations however, the smart info will often 
tell you if the drive is starting to fail.  Its not 100% reliable, but 
since we started using it, it generally gave us some sort of heads up as 
to whether or not a drive is in trouble.



---Mike


Dear Mike.
Thanks a lot for this info.
I will use this tool and try to report what I found out.

I also use trays for my drives (like I did with SCSI and SCA2 on our 
servers at the lab). Maybe this could be an issue.


Oliver
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[Mike Tancsa]

At 08:25 PM 08/08/2005, O. Hartmann wrote:

Hello.

My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 boxed 
(see dmesg).
One of  my SATA disks, the SAMSUNG SP2004C seems to show errors during 
operation (and also showd under 5.4-RELEASE-p3).

Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely.

Is this a operating system bug or is this message an evidence of defective 
hardware?


You can probably confirm a hardware issue with the smartmon 
tools.  (/usr/ports/sysutils/smartmontools).


It was quite handy the other day for us to narrow down a problem between a 
drive tray and the actual drive.  We started to see


Aug  3 02:02:49 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=391423
Aug  3 02:03:00 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=2304319
Aug  3 02:03:10 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=2312927
Aug  3 02:03:17 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=2308639
Aug  3 02:03:26 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=2309855
Aug  3 02:03:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=2348359
Aug  4 12:12:37 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=1528639
Aug  4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries 
left) LBA=1530031
Aug  4 12:13:04 verify1 kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry 
left) LBA=1528639

Aug  4 12:13:04 verify1 kernel: ad0: FAILURE - READ_DMA timed out
Aug  4 12:13:04 verify1 kernel: spec_getpages:(ad0s1a) I/O read failure: 
(error=5) bp 0xd630b4fc vp 0xc2640d68


Yet when we read the actual error info off the drive via smartctl -a ad0, 
it was clean.  So it pointed to the drive tray which we swapped and all was 
well.  In other situations however, the smart info will often tell you if 
the drive is starting to fail.  Its not 100% reliable, but since we started 
using it, it generally gave us some sort of heads up as to whether or not a 
drive is in trouble.



---Mike 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599

[O. Hartmann]

Hello.

My box is a FreeBSD 6.0-BETA2 driven ASUS A8N-SLI Deluxe based AMD64 
boxed (see dmesg).
One of  my SATA disks, the SAMSUNG SP2004C seems to show errors during 
operation (and also showd under 5.4-RELEASE-p3).

Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely.

Is this a operating system bug or is this message an evidence of 
defective hardware?


By the way, DMA support is enabled:
hw.ata.ata_dma: 1
hw.ata.atapi_dma: 1


Thanks in advance,\
Oliver
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.0-BETA2 #23: Sun Aug  7 23:32:03 UTC 2005
[EMAIL PROTECTED]:/usr/backup/obj/usr/src/sys/THOR
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3500+ (2211.34-MHz K8-class CPU)
  Origin = "AuthenticAMD"  Id = 0x10ff0  Stepping = 0
  
Features=0x78bfbff
  AMD Features=0xe2500800,LM,3DNow+,3DNow>
real memory  = 2147418112 (2047 MB)
avail memory = 2064375808 (1968 MB)
ACPI APIC Table: 
ioapic0  irqs 0-23 on motherboard
netsmb_dev: loaded
acpi0:  on motherboard
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi0: Power Button (fixed)
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
acpi_bus_number: can't get _ADR
pci_link0:  irq 10 on acpi0
pci_link1:  on acpi0
pci_link2:  irq 5 on acpi0
pci_link3:  on acpi0
pci_link4:  on acpi0
pci_link5:  irq 5 on acpi0
pci_link6:  on acpi0
pci_link7:  irq 11 on acpi0
pci_link8:  irq 3 on acpi0
pci_link9:  on acpi0
pci_link10:  irq 11 on acpi0
pci_link11:  irq 3 on acpi0
pci_link12:  on acpi0
pci_link13:  irq 11 on acpi0
pci_link14:  irq 10 on acpi0
pci_link15:  on acpi0
pci_link16:  irq 0 on acpi0
pci_link17:  irq 0 on acpi0
pci_link18:  irq 0 on acpi0
pci_link19:  irq 0 on acpi0
pci_link20:  irq 16 on acpi0
pci_link21:  irq 0 on acpi0
pci_link22:  irq 0 on acpi0
pci_link23:  irq 0 on acpi0
pci_link24:  irq 0 on acpi0
pci_link25:  irq 0 on acpi0
pci_link26:  irq 0 on acpi0
pci_link27:  irq 0 on acpi0
pci_link28:  irq 0 on acpi0
pci_link29:  irq 0 on acpi0
pci_link30:  irq 0 on acpi0
pci_link31:  irq 0 on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci_link26: BIOS IRQ 11 for -2145766612.1.INTA is invalid
pci_link21: BIOS IRQ 5 for -2145766612.2.INTA is invalid
pci_link27: BIOS IRQ 3 for -2145766612.2.INTB is invalid
pci_link23: BIOS IRQ 11 for -2145766612.10.INTA is invalid
pci_link24: BIOS IRQ 3 for -2145766612.4.INTA is invalid
pci_link29: BIOS IRQ 11 for -2145766612.7.INTA is invalid
pci_link30: BIOS IRQ 10 for -2145766612.8.INTA is invalid
pci0:  on pcib0
pci_link26: Unable to choose an IRQ
pci_link21: Unable to choose an IRQ
pci_link27: Unable to choose an IRQ
pci_link24: Unable to choose an IRQ
pci_link29: Unable to choose an IRQ
pci_link30: Unable to choose an IRQ
pci_link23: Unable to choose an IRQ
pci0:  at device 0.0 (no driver attached)
isab0:  at device 1.0 on pci0
isa0:  on isab0
ichsmb0:  port 0xe400-0xe41f,0x4c00-0x4c3f,0x4c40-0x4c7f irq 
20 at device 1.1 on pci0
ichsmb0: [GIANT-LOCKED]
smbus0:  on ichsmb0
smb0:  on smbus0
ohci0:  mem 0xd8104000-0xd8104fff irq 21 at 
device 2.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0:  on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 10 ports with 10 removable, self powered
ehci0:  mem 0xfeb0-0xfeb000ff irq 22 at 
device 2.1 on pci0
ehci0: [GIANT-LOCKED]
usb1: EHCI version 1.0
usb1: companion controller, 4 ports each: usb0
usb1:  on ehci0
usb1: USB revision 2.0
uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub1: 10 ports with 10 removable, self powered
pcm0:  port 0xdc00-0xdcff,0xe000-0xe0ff mem 
0xd8103000-0xd8103fff irq 23 at device 4.0 on pci0
pcm0: [GIANT-LOCKED]
pcm0: 
atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0
ata0:  on atapci0
ata1:  on atapci0
atapci1:  port 
0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 
0xd8102000-0xd8102fff irq 21 at device 7.0 on pci0
ata2:  on atapci1
ata3:  on atapci1
atapci2:  port 
0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 
0xd8101000-0xd8101fff irq 22 at device 8.0 on pci0
ata4:  on atapci2
ata5:  on atapci2
pcib1:  at device 9.0 on pci0
pci_link17: BIOS IRQ 21 for 0.7.INTA is invalid
pci_link18: BIOS IRQ 22 for 0.8.INTA is invalid
pci_link19: BIOS IRQ 23 for 0.10.INTA is invalid
pci5:  on pcib1
pci_link16: Unable to choose an IRQ
fwohci0:  mem 
0xd8004000-0xd80047ff,0xd800-0xd8003fff irq