Re: whats an UDMA ICRC error ?
On Tue, 3 Jun 2003 11:32:06 +0200 Stefan Bethke [EMAIL PROTECTED] wrote: Am Dienstag, 03.06.03, um 07:57 Uhr (Europe/Berlin) schrieb Andreas Klemm: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? IDE disks have (hidden) spare sectors, and will transparently remap sectors as long as they have spare ones left. If the drive reports errors (hard error reading fsbn...), then it likely has run out of spare sectors, and probably will die soon. I have experienced the same problems with a VIA IDE controller using UDMA transfer mode with two perfectly healthy hard drives. Now I use a motherboard with SiS chipset and never had these problems again. Regards, Julian Stecklina -- Reboot America. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: whats an UDMA ICRC error ?
On Tue, Jun 03, 2003 at 01:23:35AM -0500, Dan Nelson wrote: In the last episode (Jun 03), Andreas Klemm said: Hi, my console today shows the following error message from my disk: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? An ICRC error is an error detected by the IDE controller. It usually means a cabling problem, as a disk error would be reported by the drive, not the controller. From the ATA spec: ICRC shall be set to one if an interface CRC error has occurred during an Ultra DMA data transfer. The content of this bit is not applicable for Multiword DMA transfers. There are other error bits that indicate uncorrectable media errors. ^^ Does this mean, that data corruption occurred ?? Strange. Didn't touch the hardware since months... One idea, the cables have been very short and have been a little bit under tension after installation. Maybe this is the result now, that I have problems with the cables or contacts Thanks for the info, will check cabling. Andreas /// -- Andreas Klemm - Powered by FreeBSD 4.8-STABLE Need a magic printfilter today ? - http://www.apsfilter.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: whats an UDMA ICRC error ?
On Tue, Jun 03, 2003 at 11:32:06AM +0200, Stefan Bethke wrote: Am Dienstag, 03.06.03, um 07:57 Uhr (Europe/Berlin) schrieb Andreas Klemm: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? IDE disks have (hidden) spare sectors, and will transparently remap sectors as long as they have spare ones left. If the drive reports errors (hard error reading fsbn...), then it likely has run out of spare sectors, and probably will die soon. o.k., but this is luckily not the case now ;-) On Tue, Jun 03, 2003 at 12:52:01PM +0200, Frank Nobis wrote: Andreas Klemm [EMAIL PROTECTED] writes: Hallo Andreas, Hi, my console today shows the following error message from my disk: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? ich hatte genau diese Fehler vor einiger Zeit, als ich auf ATA 100 Platten umgestiegen bin. Die Fehler sind sofort verschwunden als ich mit richtigen UDMA100 Kabeln die Platten angeschlossen hatte. Well, will have to check cabling, this was also an answer I got on this topic. Thanks to you all Andreas /// -- Andreas Klemm - Powered by FreeBSD 4.8-STABLE Need a magic printfilter today ? - http://www.apsfilter.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: whats an UDMA ICRC error ?
In the last episode (Jun 03), Andreas Klemm said: On Tue, Jun 03, 2003 at 01:23:35AM -0500, Dan Nelson wrote: In the last episode (Jun 03), Andreas Klemm said: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? An ICRC error is an error detected by the IDE controller. It usually means a cabling problem, as a disk error would be reported by the drive, not the controller. From the ATA spec: ICRC shall be set to one if an interface CRC error has occurred during an Ultra DMA data transfer. The content of this bit is not applicable for Multiword DMA transfers. There are other error bits that indicate uncorrectable media errors. ^^ Does this mean, that data corruption occurred ?? No; I'm just saying that the ATA spec has a lot of status/error bits :) If you had physical data corruption you'd see something other than ICRC. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
whats an UDMA ICRC error ?
Hi, my console today shows the following error message from my disk: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? Here the output of uname -a and dmesg FreeBSD titan.klemm.apsfilter.org 5.1-RC FreeBSD 5.1-RC #0: Sun Jun 1 14:21:32 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TITAN5 i386 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 5.1-RC #0: Sun Jun 1 14:21:32 CEST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/TITAN5 Preloaded elf kernel /boot/kernel/kernel at 0xc04b3000. Preloaded elf module /boot/kernel/acpi.ko at 0xc04b31f4. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 997461361 Hz CPU: Intel Pentium III (997.46-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 536854528 (511 MB) avail memory = 516313088 (492 MB) Pentium Pro MTRR support enabled VESA: v3.0, 32768k memory, flags:0x1, mode table:0xc03eb202 (122) VESA: NVidia npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS MED_2001 on motherboard pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00f0eb0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: VIA 82C691 (Apollo Pro) host to PCI bridge mem 0xfc00-0xfdff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGP_ - AE_NOT_FOUND pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C686A UDMA66 controller port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 5 at device 4.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 ulpt0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode umass0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2 ugen0: Syncrosoft Protected Executer, rev 1.10/1.01, addr 3 uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 5 at device 4.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 ahc0: Adaptec 2940 Ultra SCSI adapter port 0xb800-0xb8ff mem 0xed80-0xed800fff irq 9 at device 9.0 on pci0 aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs pci0: multimedia, audio at device 10.0 (no driver attached) fxp0: Intel 82557/8/9 EtherExpress Pro/100(B) Ethernet port 0xa000-0xa03f mem 0xec80-0xec8f,0xed00-0xed000fff irq 10 at device 11.0 on pci0 fxp0: Ethernet address 00:d0:b7:ba:c1:c2 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse Explorer, device ID 4 orm0: Option ROMs at iomem 0xd-0xd0fff,0xcc000-0xcc7ff,0xc-0xcb7ff on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% ad0: 76319MB ST380021A [155061/16/63] at ata0-master UDMA66 ad2: 38166MB ST340823A
Re: whats an UDMA ICRC error ?
In the last episode (Jun 03), Andreas Klemm said: Hi, my console today shows the following error message from my disk: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? An ICRC error is an error detected by the IDE controller. It usually means a cabling problem, as a disk error would be reported by the drive, not the controller. From the ATA spec: ICRC shall be set to one if an interface CRC error has occurred during an Ultra DMA data transfer. The content of this bit is not applicable for Multiword DMA transfers. There are other error bits that indicate uncorrectable media errors. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: whats an UDMA ICRC error ?
Am Dienstag, 03.06.03, um 07:57 Uhr (Europe/Berlin) schrieb Andreas Klemm: ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying ad2: UDMA ICRC error cmd=read fsbn 74689079 of 74689079-74689206 retrying What exactly does an UDMA ICRC error mean ? I think this is simply a read error. AFAIK an IDE disk doesn't have spare sectors or am I wrong ? How severe is this error ? What do you think ?? IDE disks have (hidden) spare sectors, and will transparently remap sectors as long as they have spare ones left. If the drive reports errors (hard error reading fsbn...), then it likely has run out of spare sectors, and probably will die soon. -- Stefan Bethke [EMAIL PROTECTED] Fon +49 170 346 0140 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]