Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Nov 2003 08:01:51 -0500
From:      stan <stanb@panix.com>
To:        Free BSD Questions list <freebsd-questions@freebsd.org>
Subject:   Re: Drive errors?
Message-ID:  <20031114130151.GA22833@teddy.fas.com>
In-Reply-To: <20031114153114.L87141@mail.trueafrican.com>
References:  <20031114002042.GA5077@teddy.fas.com> <20031114153114.L87141@mail.trueafrican.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 14, 2003 at 03:48:14PM +0300, Joseph Begumisa wrote:
> 
> On Thu, 13 Nov 2003, stan wrote:
> 
> > I've got a relativly recent STABLE machine that I', gettng errors like this
> > on:
> >
> >
> > Nov 12 20:00:01 black newsyslog[33912]: logfile turned over due to size>100K
> > Nov 12 20:00:07 black /kernel: ad3s1e: UDMA ICRC error writing fsbn 113202879 of 56601408-56601455 (ad3s1 bn 113202879; cn 7046 tn 141 sn 6) retrying
> > Nov 12 20:00:15 black /kernel: ad3s1e: UDMA ICRC error writing fsbn 114997439 of 57498688-57498943 (ad3s1 bn 114997439; cn 7158 tn 66 sn 11) retrying
> > Nov 12 20:00:16 black /kernel: ad3s1e: UDMA ICRC error writing fsbn 115000927 of 57500432-57500687 (ad3s1 bn 115000927; cn 7158 tn 121 sn 34) retrying
> > Nov 12 20:00:20 black /kernel: ad3s1e: UDMA ICRC error writing fsbn 115172415 of 57586176-57586335 (ad3s1 bn 115172415; cn 7169 tn 38 sn 36) retrying
> > Nov 12 20:00:22 black /kernel: ad3s1e: UDMA ICRC error writing fsbn 115188431 of 57594184-57594191 (ad3s1 bn 115188431; cn 7170 tn 37 sn 50) retrying
> >
> > The drive in question is an IBM/Hitachi 40H unit detected as:
> >
> > Nov 13 19:11:18 black /kernel: ad3: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata1-slave UDMA100
> >
> 
> Pasting the output from /var/run/dmesg.boot would be useful so that we can
> know what the controller is detected as and also see whether there is any
> other useful information concerning this problem.

OK, thnaks for the sugestion.


Copyright (c) 1992-2003 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 4.9-RC #13: Sun Oct 19 11:58:37 EDT 2003
    root@black.fas.com:/usr/obj/usr/src/sys/BLACK
Timecounter "i8254"  frequency 1193182 Hz
CPU: AMD Athlon(tm) processor (900.04-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x644  Stepping = 4
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
  AMD Features=0xc0440000<RSVD,AMIE,DSP,3DNow!>
real memory  = 805240832 (786368K bytes)
avail memory = 779059200 (760800K bytes)
Preloaded elf kernel "kernel" at 0xc03da000.
Preloaded elf module "agp.ko" at 0xc03da09c.
VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc03573c2 (1000022)
VESA: ATI RADEON
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 9 entries at 0xc00fdd90
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
agp0: <VIA 82C8363 (Apollo KT133A) host to PCI bridge> mem 0xc0000000-0xcfffffff at device 0.0 on pci0
pcib1: <VIA 8363 (Apollo KT133) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <ATI model 5144 graphics accelerator> at 0.0 irq 9
isab0: <VIA 82C686 PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686 ATA100 controller> port 0xa000-0xa00f at device 7.1 on pci0
atapci0: Correcting VIA config for southbridge data corruption bug
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <VIA 83C572 USB controller> port 0xa400-0xa41f irq 10 at device 7.2 on pci0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xa800-0xa81f irq 10 at device 7.3 on pci0
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
pci0: <unknown card> (vendor=0x1106, dev=0x3057) at 7.4
pcm0: <VIA VT82C686A> port 0xb400-0xb403,0xb000-0xb003,0xac00-0xacff irq 11 at device 7.5 on pci0
pcm0: <ICEnsemble ICE1232 AC97 Codec>
ahc0: <Adaptec 2902/04/10/15/20C/30C SCSI adapter> port 0xb800-0xb8ff mem 0xdb001000-0xdb001fff irq 11 at device 9.0 on pci0
aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs
ahc1: <Adaptec 2930CU SCSI adapter> port 0xbc00-0xbcff mem 0xdb000000-0xdb000fff irq 10 at device 11.0 on pci0
aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs
ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xc000-0xc01f irq 10 at device 13.0 on pci0
ed0: address 00:50:ba:52:69:f1, type NE2000 (16 bit) 
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xcc000-0xcc7ff on isa0
pmtimer0 on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
fdc0: ready for input in output
fdc0: cmd 3 failed at out byte 1 of 3
fd1: <1200-KB 5.25" drive> on fdc0 drive 1
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model MouseMan+, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata0-master UDMA100
ad1: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata0-slave UDMA100
ad2: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata1-master UDMA100
ad3: 39266MB <IC35L040AVER07-0> [79780/16/63] at ata1-slave UDMA100
Waiting 5 seconds for SCSI devices to settle
sa0 at ahc1 bus 0 target 4 lun 0
sa0: <Quantum DLT4000 CC37> Removable Sequential Access SCSI-2 device 
sa0: 10.000MB/s transfers (10.000MHz, offset 15)
sa1 at ahc1 bus 0 target 5 lun 0
sa1: <HP C1537A U610> Removable Sequential Access SCSI-2 device 
sa1: 10.000MB/s transfers (10.000MHz, offset 15)
sa2 at ahc1 bus 0 target 6 lun 0
sa2: <HP C1533A HP01> Removable Sequential Access SCSI-2 device 
sa2: 10.000MB/s transfers (10.000MHz, offset 8)
pass0 at ahc0 bus 0 target 2 lun 0
pass0: <HP C2520A 3503> Fixed Processor SCSI-2 device 
pass0: 3.300MB/s transfers
pass3 at ahc1 bus 0 target 5 lun 1
pass3: <HP C1557A U610> Removable Changer SCSI-2 device 
pass3: 10.000MB/s transfers (10.000MHz, offset 15)
Mounting root from ufs:/dev/ad0s1a
psmintr: out of sync (0000 != 0008).
psmintr: discard a byte (1).
link_elf: symbol linux_ioctl_register_handler undefined
cmd gdm-binary pid 260 tried to use non-present sched_yield
cmd gdm-binary pid 260 tried to use non-present sched_yield
cmd gdm-binary pid 260 tried to use non-present sched_yield
cmd gdm-binary pid 260 tried to use non-present sched_yield
cmd gdm-binary pid 260 tried to use non-present sched_yield
cmd gdm-binary pid 263 tried to use non-present sched_yield
cmd gdm-binary pid 263 tried to use non-present sched_yield
cmd gdm-binary pid 263 tried to use non-present sched_yield
cmd gdm-binary pid 263 tried to use non-present sched_yield
> 
> The last time I had such a problem, I solved it by using a 40 pin
> 80 wire ribbon cable in place of the 40 pin 40 wire ribbon cable.

I'll check that, but given that its a new drive I suspect it already has an
80 wire cable.

-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
						-- Benjamin Franklin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031114130151.GA22833>