From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 30 05:05:19 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E53B6106566C for ; Mon, 30 Nov 2009 05:05:19 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-98-108-131-11.ptldor.fios.verizon.net [98.108.131.11]) by mx1.freebsd.org (Postfix) with ESMTP id 45A0C8FC0C for ; Mon, 30 Nov 2009 05:05:18 +0000 (UTC) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 90C91B64F; Sun, 29 Nov 2009 20:41:51 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id FAA11837; Mon, 30 Nov 2009 05:01:11 GMT Message-Id: <200911300501.FAA11837@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org Date: Sun, 29 Nov 2009 21:01:11 PST From: Dieter Subject: Re: Marvell MV88SX6081 on FreeBSD 8.0-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2009 05:05:20 -0000 In message <4B13159D.9010504@darkbsd.org>, Stephane LAPIE writes: > On FreeBSD 8.0, attempting to scrub a ZFS pool results in a few I/O > bursts (confirmed with zpool iostat), before totally freezing down and > locking the ZFS pool (the system is still up and only ZFS based file > systems are unusable in this state), probably to avoid data corruption. > Occasionally I also witness a "READ_DMA48 soft error (ECC corrected)" > error message showing up, on a random hard disk. And there are these, which you didn't mention: > ad1: FAILURE - SET_MULTI status=3D51 error=3D4 > ad12: FAILURE - SET_MULTI status=3D51 error=3D4 (No, I don't know what that means, sorry.) > ad18: 1430799MB at ata9-master SATA300 > ad20: 1430799MB at ata10-master SATA300 How old is the SD1A disk? As you may know, Seagate had various troubles with the .11 firmware. I have some of the ST31500341AS CC1H and mine are new enough that they are supposed to be ok. > Therefore, I am inclined to think the motherboard/memory (a "TYAN > Thunder K8WE S2895") would be at fault here, I have been told that Tyan does a good job with memory, although even assuming that's true it could still be a memory problem. My Tyan board has a memory scrubbing feature that can be turned on in firmware, but I've never tried it. Also, you could try rotating the SIMMs and see if anything changes.