Date: Mon, 14 Oct 2002 20:04:51 -0700 From: "Jonas Fornander" <jonas@netwood.net> To: "'FreeBSD LIST'" <FreeBSD-Questions@freebsd.org> Subject: RE: Drive/DMA issuse Message-ID: <011a01c273f7$a129c220$0800a8c0@master> In-Reply-To: <NGBBIILBAKIFGHHCHOHPEENCFJAA.maildrop@qwest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG] On Behalf Of Maildrop > Sent: Monday, October 14, 2002 8:29 AM > To: Maildrop; Jonas Fornander; 'FreeBSD LIST' > Subject: RE: Drive/DMA issuse > > > > Any ideas on this, is it a hardware issuse, hardware config > issuse, softare issuse? > > Jack > > > -----Original Message----- > > From: owner-freebsd-questions@FreeBSD.ORG > > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Maildrop > > Sent: Saturday, October 12, 2002 12:22 AM > > To: Jonas Fornander; 'FreeBSD LIST' > > Subject: Drive/DMA issuse > > > > > > > > > > Everytime I boot up, I see this in my log files: > > > > > > ad0: 4112MB <SAMSUNG SV0432A> [8912/15/63] at ata0-master UDMA33 > > ad2: 95396MB <WDC WD1000BB-00CAA0> [193821/16/63] at ata1-master > > UDMA33 > > ad3: 78167MB <Maxtor 98196H8> [158816/16/63] at ata1-slave UDMA33 > > ad0s1a: UDMA ICRC error reading fsbn 11199 of 5568-5571 (ad0s1 bn > > 11199; cn > > 0 tn 177 sn 48) retrying > > ad0s1a: UDMA ICRC error reading fsbn 255 of 96-127 (ad0s1 bn 255; > > cn 0 tn 4 > > sn 3) retrying > > ad0s1a: UDMA ICRC error reading fsbn 255 of 96-127 (ad0s1 bn 255; > > cn 0 tn 4 > > sn 3) retrying > > ad0s1a: UDMA ICRC error reading fsbn 255 of 96-127 (ad0s1 bn 255; > > cn 0 tn 4 > > sn 3) retrying > > ad0s1a: UDMA ICRC error reading fsbn 255 of 96-127 (ad0s1 bn 255; > > cn 0 tn 4 > > sn 3) falling back to PIO mode > > > > > > I tried switch IDE cables (used 3 differant cables on the > drive) and > > played around with the PIO/bits in the BIOS (tried PIO 4, > PIO 1, none, > > auto and both 16-bit and 32-bit and all combinations of these). I > > have ran fsck on the drive many times. > > > > Sometimes the server crashes, I think it might be related > to this hard > > drive (if a hard drive fails to save data, could/would this cause a > > kernel panic?) > > > > Any suggestions? It appears the other drives are working fine. > > > > ad0s1a is my root slice/drive, btw. (this drive has a root slice, > > /var slice and a swap slice). > > > > > > Regards, > > Jack > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message I guess any and all of the above. I solved it by getting a new HD and/or motherboard. Don't remember exactly what I replaced but anything until the error vanished. My hunch is that it's a failing HD. Jonas Fornander - System Administrator Netwood Communications, LLC - www.netwood.net Find out why we're better - 310-442-1530 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?011a01c273f7$a129c220$0800a8c0>