Date: Tue, 19 Oct 1999 10:48:32 +0200 From: Gawel <gawel@unix.sim.com.pl> To: Doug White <dwhite@resnet.uoregon.edu> Cc: "freebsd-stable@FreeBSD.ORG" <freebsd-stable@FreeBSD.ORG> Subject: Re: ID CRC or ECC error Message-ID: <380C3060.34892209@unix.sim.com.pl> References: <Pine.BSF.4.10.9910181140410.567-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Dump reports: DUMP: read error from /dev/rda0s1f: Input/output error: [block 3312398]: count=1024 DUMP: read error from /dev/rda0s1f: Input/output error: [sector 3312399]: count=512 Can I find which files occupy bad sectors, which files are damaged? Gawel Doug White wrote: > On Mon, 18 Oct 1999, Gawel wrote: > > > FreeBSD 3.3-stable, > > ncr0: <ncr 53c875 fast20 wide scsi> rev 0x26 int a irq 10 on pci0.15.0 > > da0: <SEAGATE ST32430N 0510> Fixed Direct Access SCSI-2 device > > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enab > > da0: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) > > > > I receive it every day in messages log file: > > Oct 18 02:01:13 unix /kernel: (da0:ncr0:0:0:0): READ(10). CDB: 28 0 0 38 > > a6 2e 0 0 2 0 > > Oct 18 02:01:13 unix /kernel: (da0:ncr0:0:0:0): MEDIUM ERROR info:38a62f > > asc:10,0 > > Oct 18 02:01:13 unix /kernel: (da0:ncr0:0:0:0): ID CRC or ECC error > > field replaceable unit:d7 sks:8 > > Could you advise me what I have to do to correct it? > > Gawel > > You have a bad SCSI cable or a disk or controller with problems. If > replacing the cable doesn't fix it, replace the disk. If that doesn't fix > it, replace the controller :) > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?380C3060.34892209>