Date: Tue, 12 Nov 2002 14:39:29 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Ed McGough <emcgough@sbcglobal.net> Cc: questions@FreeBSD.ORG Subject: Re: UDMA ICRC error's Message-ID: <20021112203929.GB93732@dan.emsphone.com> In-Reply-To: <HEECLIFMNNPIOOGJFBKMAEGMCDAA.emcgough@sbcglobal.net> References: <HEECLIFMNNPIOOGJFBKMAEGMCDAA.emcgough@sbcglobal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Nov 12), Ed McGough said: > What is the best way to resolve these? > > ad0s1e: UDMA ICRC error reading fsbn 897759 of 144-159 (ad0s1 bn 897759; cn 55 tn 225 sn 9) retrying > > ad0s1a: UDMA ICRC error reading fsbn 45439 of 22688-22719 (ad0s1 bn 45439; cn 2 tn 211 sn 16) retrying > > ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying > > ad0s1a: UDMA ICRC error reading fsbn 39391 of 19664-19695 (ad0s1 bn 39391; cn 2 tn 115 sn 16) retrying > > I've tried bringing the system down to single user mode, umounting > the filesystems and running fsck but it never finds anything wrong. > Next I'm going to switch out the ide cable, and i'm hoping that is > the problem as I'd prefer not to have my drive go out. > > What else can I do besides running fsck? Are there any other > utilites to check the disk, maybe something from the ports tree? An ICRC error means that the data was corrupted between the drive and the controller, and usually means cabling problems. -- Dan Nelson dnelson@allantgroup.com 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?20021112203929.GB93732>