Date: Sat, 8 Sep 2001 22:36:53 -0400 From: Randall Hopper <aa8vb@nc.rr.com> To: stable@FreeBSD.ORG Subject: Re: UDMA ICRC error reading fsb (?) Message-ID: <20010908223653.A762@nc.rr.com> In-Reply-To: <20010908202004.A1101@nc.rr.com>; from aa8vb@nc.rr.com on Sat, Sep 08, 2001 at 08:20:04PM -0400 References: <20010906204356.A4116@nc.rr.com> <auto-000028388966@dc-mx05.cluster1.charter.net> <20010907180403.A1472@nc.rr.com> <auto-000027449537@dc-mx04.cluster1.charter.net> <3B994E08.FF3BE9C4@ntlworld.com> <20010908202004.A1101@nc.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
| |> ad0s2a: UDMA ICRC error writing fsbn 3283483 of 396704-396713 | |> (ad0s2 bn 3283483; cn 204 tn 98 sn 49) retrying | |Just replaced the 18" ATA66 cable with a new 20" ATA66 cable. No CRC |errors yet but I'll keep an eye out for more, and do a mfgr drive-test run |just to be safe. | |I've attached a dmesg. This is an ASUS A7M266 MB with two UltraDMA 100 |hard disks on the primary controller: a Maxtor DiamondMax 60 60GB master, |and an IBM Desktar 60GXP 60GB slave. The Maxtor is the new one, and the |one that had the CRC errors. A datapoint: After replacing the cable, I just did a first "Maxtor PowerMax" disk test run. Both the 90 sec QuickTest (including S.M.A.R.T. self-test) and the Advanced Test (sector-by-sector) certify the drive error free. Hopefully it was the cabling (and not the drive, a driver bug, or some hw chipset quirk). I'll keep an close eye on my syslog though... Thanks for all the advice! Randall -- Randall Hopper aa8vb@nc.rr.com 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?20010908223653.A762>