From owner-freebsd-stable@FreeBSD.ORG Tue Apr 26 19:57:06 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DC7E106566B; Tue, 26 Apr 2011 19:57:06 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 185828FC12; Tue, 26 Apr 2011 19:57:05 +0000 (UTC) Received: by iyj12 with SMTP id 12so1121915iyj.13 for ; Tue, 26 Apr 2011 12:57:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qPKhoNDykm+0Z9bln2CJQBq1QeeKTITeKKC7ng7jiv4=; b=LJcJ3pW3KwjEpIx3u3U3hERX1fnwpxcGKJT4/o5LCoCeYH+JokGIA5SyHSIsZtMtdZ uuDEFthVGdSGozx3x1Bh1ii91QtPTo8DcY2sfbl+JLtvGjxQw287ALu8Hn9tc7pFRkFh aBBR6hW6uaZHdJ5wccUH23xWWyYXQ169pLzhw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=BKdnuIJumXGdgDXtYnn6ihwYmeNbDXAft0ruLOd9q0cyb/nVSrhllpVjQSpQmx4SyA RncZaH7ID8dJ68sG2pR9ZoOZx8rZSrqJQyX3fLrkDAHzdIV8xXdUTqI3yCqthuXKmBGD sTGXc3uDdYA9ASWqGm2yeNds+pM05RyiXoDGo= MIME-Version: 1.0 Received: by 10.42.96.65 with SMTP id i1mr1521632icn.274.1303847825350; Tue, 26 Apr 2011 12:57:05 -0700 (PDT) Received: by 10.231.35.2 with HTTP; Tue, 26 Apr 2011 12:57:05 -0700 (PDT) In-Reply-To: <4DB71F80.8030901@FreeBSD.org> References: <4DB71C65.7070700@FreeBSD.org> <4DB71F80.8030901@FreeBSD.org> Date: Tue, 26 Apr 2011 22:57:05 +0300 Message-ID: From: George Kontostanos To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable Subject: Re: Promise SATA controller issues... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 19:57:06 -0000 The system was up since April 21 when I upgraded to the latest world && kernel. There are 2 pools, a mirror with root on ZFS for the OS and a Raidz1 just for the data. hp# zpool status pool: tank state: ONLINE scrub: scrub completed after 1h30m with 0 errors on Tue Apr 26 22:48:32 2011 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1 ONLINE 0 0 0 label/zdisk1 ONLINE 0 0 0 label/zdisk2 ONLINE 0 0 0 label/zdisk3 ONLINE 0 0 0 errors: No known data errors pool: zroot state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 The server is a SOHO fileserver with a few other services: sshd_enable="YES" named_enable="YES" #Caching name server samba_enable="YES" dhcpd_enable="YES" squid_enable="YES" apcupsd_enable="YES" apache22_enable="YES" mysql_enable="YES" syslogd_flags="-a 10.10.10.1" #Cisco Pix logging snmpd_enable="YES" nagios_enable="YES" munin_node_enable="YES" bsdstats_enable="YES" smartd_enable="YES" There was nothing out of the ordinary before this except some repeated power failures that where handled by the UPS as you can see in the logs: Apr 24 20:33:53 hp apcupsd[870]: Power failure. Apr 24 20:33:55 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 20:38:03 hp apcupsd[870]: Power failure. Apr 24 20:38:04 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 21:45:47 hp apcupsd[870]: Power failure. Apr 24 21:45:49 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 22:43:56 hp apcupsd[870]: Power failure. Apr 24 22:43:57 hp apcupsd[870]: Power is back. UPS running on mains. Apr 24 23:05:46 hp apcupsd[870]: Power failure. Apr 24 23:05:47 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 00:20:32 hp apcupsd[870]: Power failure. Apr 25 00:20:33 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 01:23:22 hp apcupsd[870]: Power failure. Apr 25 01:23:23 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 06:26:40 hp apcupsd[870]: Power failure. Apr 25 06:26:42 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 11:05:03 hp apcupsd[870]: Power failure. Apr 25 11:05:04 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 13:05:20 hp apcupsd[870]: Power failure. Apr 25 13:05:21 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 13:32:48 hp apcupsd[870]: Power failure. Apr 25 13:32:50 hp apcupsd[870]: Power is back. UPS running on mains. Apr 25 13:35:06 hp apcupsd[870]: Power failure. Apr 25 22:08:35 hp kernel: ata4: SIGNATURE: ffffffff Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command Apr 25 22:08:35 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE command ......... On Tue, Apr 26, 2011 at 10:39 PM, Alexander Motin wrote: > George Kontostanos wrote: > > Please let me know what kind of information might be also useful. > > I don't know. What were the first messages before the problem? Was there > any specific activity? It would be most useful if you could reproduce > the problem in controllable environment. > > > There was no changes specific to the Promise controllers for a long > > time. Mostly because I have no any documentation for them. For the > same > > reason I hardly can say what could be wrong there. Some additional > > information is definitely required. > > -- > Alexander Motin > -- George Kontostanos aisecure.net