From owner-freebsd-stable@FreeBSD.ORG Fri Jul 28 13:37:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8708316A4DA for ; Fri, 28 Jul 2006 13:37:13 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (grimm.quip.cz [213.220.192.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C2D643D5D for ; Fri, 28 Jul 2006 13:37:09 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id 050EC56E7; Fri, 28 Jul 2006 15:37:06 +0200 (CEST) Message-ID: <44CA1302.2050600@quip.cz> Date: Fri, 28 Jul 2006 15:37:06 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cs, cz, en, en-us MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> <884C01BC-3E97-46EC-AA8B-E70C3931F3A4@stromnet.org> <36895211-2796-4213-B336-6279AB3AC3CB@stromnet.org> <20060713132357.Y61840@fledge.watson.org> <44B7EA39.4060509@quip.cz> <6.2.3.4.0.20060716185019.12a29240@64.7.153.2> <44BBAF52.9080007@quip.cz> <0B43BAB0-BBF0-4E2C-875D-6E1E00BAB1D4@stromnet.org> In-Reply-To: <0B43BAB0-BBF0-4E2C-875D-6E1E00BAB1D4@stromnet.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: =?ISO-8859-1?Q?Johan_Str=F6m?= Subject: Re: ATA problems again ... 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: Fri, 28 Jul 2006 13:37:13 -0000 Johan Ström wrote: [...] > On 17 jul 2006, at 17.40, Miroslav Lachman wrote: > >> Mike Tancsa wrote: >> [..] >> >>> Install the smartmontools from >>> /usr/ports/sysutils/smartmontools/ >>> and post the output of >>> smartctl -a /dev/ad8 >> >> >> smartmontools was previously installed and running as daemon without >> any bad reports. >> I can not run "smartctl -a /dev/ad8" now, because my server housing >> provider replaced HDD with the new one and after an hour of >> synchronization "ad8: FAILURE - device detached". So provider >> replaced whole server, only ad4 is original piece of HW. >> On new server synchronization was much faster then in previous server >> (1:30 hour compared to 5 hours in previous server) - so I think it >> was HW problem. >> Now I am running stresstest with copying /usr/ports to another >> partition in infinite loop. >> I will post results later. (On bad server, test failed after about 30 >> minutes. On another server the test is running fine second day, so I >> think if disk will not fail after 1 day, problem is solved) >> >> At last - now I think this was not GEOM/gmirror related. I tried >> remove ad8 provider from gmirror (gm0), boot up system from gm0 with >> one provider (ad4) and test ad8 mounted separately - ad8 failed again. > > > Just got another one.. > > Jul 25 13:30:47 elfi kernel: ad4: FAILURE - device detached > Jul 25 13:30:47 elfi kernel: subdisk4: detached > Jul 25 13:30:47 elfi kernel: ad4: detached > Jul 25 13:30:47 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad4s1 > disconnected. > Jul 25 13:30:47 elfi kernel: g_vfs_done():mirror/gm0s1f[READ > (offset=46318008320, length=2048)]error = 6 > Jul 25 13:30:47 elfi kernel: g_vfs_done():mirror/gm0s1f[READ > (offset=77269614592, length=16384)]error = 6 > > 6 days uptime when this occured... Both disks are tested with PowerMax > without a single problem (same with smartctl), both SATA cables are > new. So the only hwproblem that I cant rule out would be the mobo, but > that is quite new too... > > Solutions? Try RELENG_6 as recommended earlier? In my case, server (mobo) replacement solved the problem. In this time, I got same problem on the second server. :( You can try BIOS update first, then RELENG_6 (I do not thing it helps), at last - replace mobo. Please, send me info, if BIOS update solved your problem. Miroslav Lachman