Date: Tue, 24 Jul 2007 14:40:05 +0200 From: Sverre Svenningsen <ss.alert@online.no> To: freebsd-current@freebsd.org Subject: Re: Promise SATA300 TX4 card issues Message-ID: <1273412671.20070724144005@online.no> In-Reply-To: <468A9842.0@barryp.org> References: <4679CE35.8080907@fusiongol.com> <86wsxibxc2.fsf@dwp.des.no> <4689A7DC.1070604@fusiongol.com> <468A9842.0@barryp.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Barry, Tuesday, July 3, 2007, 8:41:06 PM, you wrote: > Nathan Butcher wrote: >> Dag-Erling Smørgrav wrote: >>> Nathan Butcher <n-butcher@fusiongol.com> writes: >>>> I've been having problems with my ZFS pool consisting of 4 drives hooked >>>> up to my Prmoise SATA 300TX4 controller. It had been working fine until >>>> to around the 19th of this month, and then I started seeing error >>>> messages whenever I tried to write lots of data to ZFS..... followed by >>>> a nasty lockup with no other debugging information of which to speak of. > I've noticed problems with this card too, running amd64 on a AthlonX2. > I've got a ZFS pool setup, and when scrubbing the pool it comes up with > erratic CKSUM errors (for example, scrub once and get 7 errors, scrub > again immediately and get 53 more). > Previously I had these drives (Seagate Barracuda ES ST3320620NS) plugged > into the motherboard SATA ports of the same machine, (nVidia nForce > MCP51 SATA300 controller) with no issues at all. > Barry > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" Hi, i want to report this same problem. Platform is a c2d with 1gb ram running i386. I updated my sources and installed a new kernel and world yesterday, July 23rd.(old world and kernel was built on 2nd of June) and now i'm seeing this problem too. Only difference is that i have two of these promise sata300 tx4 cards in my machine. Even trying to create a zfs raidz on disks attached to the controllers will hardlock the computer with no visible kernel panic, so it's hard to tell just what happens. The system disk is on another controller, and testing various zfs things on the onboard controller (intel ich) works fine. What broke the promise ata driver? -- Best regards, Sverre mailto:ss.alert@online.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1273412671.20070724144005>