Hi there.
OS version: FreeBSD 4.7-Stable FreeBSD #3
I just added a disk to my box and after playing with
fdisk and disklabel with this configuration:
fdisk:
****************************************************************
g c16383 h16 s63
p 1 165 0 39102336
****************************************************************
disklabel
****************************************************************
# /dev/ad1c:
type: ESDI
disk: ad1s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 16383
sectors/unit: 39102336
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 524288 0 4.2BSD 2048 16384 94 # (Cyl. 0 - 520*)
b: 524288 524288 4.2BSD 2048 16384 94 # (Cyl. 520*- 1040*)
c: 39102336 0 unused 0 0 # (Cyl. 0 - 38791*)
d: 524288 1048576 4.2BSD 2048 16384 94 # (Cyl. 1040*- 1560*)
e: 37529472 1572864 4.2BSD 2048 16384 94 # (Cyl. 1560*- 38791*)
****************************************************************
I have that (to me) crypted errore message..
can anybody tell me what does that UDMA ICRC error means?
May 24 19:58:30 saturn /kernel: ad0: DMA limited to UDMA33, non-ATA66 cable or
device
May 24 19:58:30 saturn /kernel: ad0: 9770MB <Maxtor 91021U2> [19852/16/63]
at
ata0-master UDMA33
May 24 19:58:30 saturn /kernel: ad1: 19092MB <Maxtor 2B020H1>
[38792/16/63] at
ata1-master UDMA33
May 24 19:58:30 saturn /kernel: Mounting root from ufs:/dev/ad0s1a
May 24 19:58:30 saturn /kernel: ad1s1a: UDMA ICRC error reading fsbn 32 of 16-31
(ad1s1 bn 32; cn 0 tn 0 sn 32) retrying
May 24 19:58:30 saturn last message repeated 2 times
May 24 19:58:30 saturn /kernel: ad1s1a: UDMA ICRC error reading fsbn 32 of 16-31
(ad1s1 bn 32; cn 0 tn 0 sn 32) falling back to PIO mode
Please, also send replies to my mailbox, as I'm not on
the list.
Thanks for your help.
Regards.
--
Roberto Nunnari -software engineer-
mailto:nunnari@die.supsi.ch
Scuola Universitaria Professionale della Svizzera Italiana
Dipartimento di Informatica e Elettronica
http://www.die.supsi.ch
SUPSI-DIE
Via Cantonale tel: +41-91-6108561
6928 Manno """ fax: +41-91-6108570
Switzerland (o o)
=======================oOO==(_)==OOo========================
Roberto Nunnari wrote:> Hi there. > > OS version: FreeBSD 4.7-Stable FreeBSD #3 > > <cliped>. > > can anybody tell me what does that UDMA ICRC error means? > > May 24 19:58:30 saturn /kernel: ad0: DMA limited to UDMA33, non-ATA66 > cable or device > May 24 19:58:30 saturn /kernel: ad0: 9770MB <Maxtor 91021U2> > [19852/16/63] at ata0-master UDMA33 > May 24 19:58:30 saturn /kernel: ad1: 19092MB <Maxtor 2B020H1> > [38792/16/63] at ata1-master UDMA33 > May 24 19:58:30 saturn /kernel: Mounting root from ufs:/dev/ad0s1a > May 24 19:58:30 saturn /kernel: ad1s1a: UDMA ICRC error reading fsbn > 32 of 16-31 (ad1s1 bn 32; cn 0 tn 0 sn 32) retrying > May 24 19:58:30 saturn last message repeated 2 times > May 24 19:58:30 saturn /kernel: ad1s1a: UDMA ICRC error reading fsbn > 32 of 16-31 (ad1s1 bn 32; cn 0 tn 0 sn 32) falling back to PIO modeHmm I've also hit this problem as well I've been thru the Mailing archive and numerous sites. The problem began with 4.7 - 4.8 stable and release.
Hi@all On Sunday 25 May 2003 09:15, David A Bestor wrote:> I hit this 2 weeks ago when moving an 8gig to a 60 gig... > I had the errors on the new 60gig. The errors went away > when I changed the cable. It was connected on the IDE100 > slot. I changed the cable to the proper cable for that > slot and that fixed it. I found the answer in a google > search.Yes, i can confirm that. I also changed the cables & found the answer on groups.google.com, too ;-) If you've bought a built pc-system it often happens that the cables are of poor quality what would result in a falling back to PIO mode. This seems to be the effect of the low data integrity that is reached in conjunction with those cables. Hernani
Hernani Marques Madeira wrote:> Hi@all > On Sunday 25 May 2003 09:15, David A Bestor wrote: > > >> I hit this 2 weeks ago when moving an 8gig to a 60 gig... >> I had the errors on the new 60gig. The errors went away >> when I changed the cable. It was connected on the IDE100 >> slot. I changed the cable to the proper cable for that >> slot and that fixed it. I found the answer in a google >> search. >> > > > Yes, i can confirm that. I also changed the cables & found the answer > on groups.google.com, too > If you've bought a built pc-system it often happens that the cables > are of poor quality what would result in a falling back to PIO mode. > This seems to be the effect of the low data integrity that is reached > in conjunction with those cables. > > Hernani > >Cable swapping did nothing to resolve my problem (that was the first thing I tried) I also tried setting the DMA mode manully in the BIOS ...no dice.