Date: Mon, 12 Nov 2001 09:24:12 -0500 From: "brain_damaged" <brain_damaged@florida-wireless.com> To: Nils Holland <nils@tisys.org> Cc: "freebsd-questions" <freebsd-questions@freebsd.org> Subject: Re: UDMA ICRC error Message-ID: <200111120924.AA4261806492@florida-wireless.com>
next in thread | raw e-mail | index | archive | help
i have two freebsd 4-3 machines that i get these errors on. now not sure if windows scandisk/chkdisk are as intense or indepth as fbsd but i never got any error reports when nt/98 was on the drives. and I don't get the error everytime. and sometimes there are more lines to the error than other times. i find it HARD to believe that two machines with 3 drives in it are all going back after being converted to freebsd. but then again never thought pet rocks would sell :-) md --------- Original Message ---------------------------------- From: Nils Holland <nils@tisys.org> Date: Mon, 12 Nov 2001 14:47:29 +0100 (CET) >On Mon, 12 Nov 2001, Josh Paetzel wrote: > >> On Sun, Nov 11, 2001 at 08:21:38PM -0800, chia an wrote: >> > hello friend_bsd; >> > 1 .i have a problem when booting my Freebsd 4.4, there >> > was an error appear like this : >> > >> > ad0s3a : UDMA ICRC error reading fsbn 1606628 of 64-79 >> > (ad0s3 bn 1606628; cn 100 tn 2 sn 2 ) retrying >> > ad0s3a : UDMA ICRC error reading fsbn 1606628 of 64-79 >> > (ad0s3 bn 1606628; cn 100 tn 2 sn 2 ) retrying >> > ad0s3a : UDMA ICRC error reading fsbn 1606628 of 64-79 >> > (ad0s3 bn 1606628; cn 100 tn 2 sn 2 ) falling back to >> > PIO mode >> > >> > what should i do? >> >> This looks like you have a bad cable perhaps. Does the disk seem to >> work ok after these errors come up? It could also be an indication >> that your disk is dying. > >I'd like to add a comment about this, as I just had it happen here the >other day as well. In short, I had two HDDs connected to the primary IDE >port. When heavy read access took place on the slave HDD, the above error >message tended to appear. It didn't seem to be connected to reading any >particular file, as the error seemed to appear totally random. > >As a solution, I put one HDD on the secondary IDE port, and ever since >then the problem has gone away. I'm pretty sure that this must be some >issue with the (somewhat dated) mainboard I'm using. Generally, it should >be possible to put two HDDs on the same IDE port, but bad cables, flawed >mainboards and certain HDDs may cause trouble, although this probably >happens only very rarely. > >I would recommend experimenting with the cabling as well as switching IDE >ports in order to track this problem down. If it doesn't want to go away, >the HDD should be tried in a different system, and if it still behaves >strange, it's probably indeed about to die. In that case, make a backup as >long as you still can and then try to get a new drive. > >Greetings >Nils > >Nils Holland >Ti Systems - FreeBSD in Tiddische, Germany >http://www.tisys.org * nils@tisys.org > > >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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111120924.AA4261806492>