UDMA ICRC Read Errors

[Mars G.Miro]

Hi all,

I have a 20Gig Maxtor IDE HD that's acting as a secondary master
(/dev/ad3c) where /home is mounted and is also used to back up everything (so
it's one big UFS slice)
$ cat fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/ad0s2b none swap sw 0 0
/dev/ad0s2a / ufs rw 1 1
/dev/ad3c /home ufs rw 2 2
/dev/ad0s2f /usr ufs rw 2 2
/dev/ad0s2e /var ufs rw 2 2
/dev/acd0c /cdrom cd9660 ro,noauto 0 0
proc /proc procfs rw 0 0

I still kept encountering these errors even when I have upgraded (just a
few hours ago) to 4.2-Stable:
Feb 12 13:36:00 x kernel ad3: UDMA ICRC READ ERROR blk# 35848256 retrying
Feb 12 13:36:00 x kernel ad3: UDMA ICRC READ ERROR blk# 33882176 retrying
I first encountered them after installing the HD(by way of fbsd handbook
section 10.3.2.2, alternative method) circa Jan13 , but that time there was a
discussion on the same type of errors and that a patch(Soren) was to be MFC'ed
that was gonna fix them all. I was not able to upgrade it that time but only
now.
Do the above errors tell that the HD may be broken? It's only about 1
month old.
Attached is a verbose dmesg.

cheers
mars

To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

[Soren Schmidt]

It seems Mars G.Miro wrote:
> I still kept encountering these errors even when I have upgraded (just a
> few hours ago) to 4.2-Stable:
> Feb 12 13:36:00 x kernel ad3: UDMA ICRC READ ERROR blk# 35848256 retrying
> Feb 12 13:36:00 x kernel ad3: UDMA ICRC READ ERROR blk# 33882176 retrying
> I first encountered them after installing the HD(by way of fbsd handbook
> section 10.3.2.2, alternative method) circa Jan13 , but that time there was a
> discussion on the same type of errors and that a patch(Soren) was to be MFC'ed
> that was gonna fix them all. I was not able to upgrade it that time but only
> now.
> Do the above errors tell that the HD may be broken? It's only about 1
> month old.

Hmm, are you sure your cabling is OK ?
Do you use disk drawers ? there is a lot of them that are not ata66 ready
even if they claim so, ATA100 is even worse..

-Søren

[Yan V. Batuto]

> I still kept encountering these errors even when I have upgraded (just a
> few hours ago) to 4.2-Stable:
> Feb 12 13:36:00 x kernel ad3: UDMA ICRC READ ERROR blk# 35848256 retrying
> Feb 12 13:36:00 x kernel ad3: UDMA ICRC READ ERROR blk# 33882176 retrying
> I first encountered them after installing the HD(by way of fbsd handbook
> section 10.3.2.2, alternative method) circa Jan13 , but that time there was a
> discussion on the same type of errors and that a patch(Soren) was to be MFC'ed
> that was gonna fix them all. I was not able to upgrade it that time but only
> now.
> Do the above errors tell that the HD may be broken? It's only about 1
> month old.

I encountered the same troubles with my transport Seagate ST32110 hdd.
It works fine as UDMA/2 under OS/2, but FreeBSD 4.2-RELEASE #1 says:

atapci0: <VIA 82C586 ATA33 controller> port 0xf000-0xf00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
[lines skipped]
ad0: 8063MB <FUJITSU MPE3084AE> [16383/16/63] at ata0-master UDMA33
ad1: 2014MB <ST32110A> [4092/16/63] at ata0-slave UDMA33
acd0: CDROM <BCD 24XM CD-ROM> at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s3a
ad1: UDMA ICRC READ ERROR blk# 1024129 retrying
ad1: UDMA ICRC READ ERROR blk# 1024223 retrying
ad1: UDMA ICRC READ ERROR blk# 1024231 retrying
ad1: UDMA ICRC READ ERROR blk# 1024231 retrying
ad1: UDMA ICRC READ ERROR blk# 1024231 retrying
ad1: UDMA ICRC READ ERROR blk# 1024231 falling back to PIO mode

The same happens when this drive connected as a secondary (single) master
instead of primary slave.
But Fujitsu drive works fine as UDMA2 under both OS/2 and FreeBSD systems.
What's wrong?

Yan V. Batuto
bat...@mailru.com