From owner-freebsd-questions@FreeBSD.ORG Sat Mar 22 02:46:09 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 879E3F4A for ; Sat, 22 Mar 2014 02:46:09 +0000 (UTC) Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 59B0B361 for ; Sat, 22 Mar 2014 02:46:09 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id uo5so3176530pbc.10 for ; Fri, 21 Mar 2014 19:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qNWcfnZ+t06baHXQv0ZMYKwNK/VgCHsjBCz3O7c5YcM=; b=Ply8+aJwjyAetAOMyC9Ic9cALzs5TTNrg100UpaoFVvPluskZ7ZetLRVFIW8LUrhfU oitt/3ooRAmugaYAAZ8I/1QqZalr57f92+7JmkmP6XqYI+j+yYTfq9vyq5TPTCXOgwxu A4OikFW89rSNK5ASJdVRAsEJGSsN0OuA3fZOSZcOu3eHFrB/hNGb1FijNAKHQSsmADcX HAmObZ9Mxpd7CdiYp2721jiTSxvV8VDy1L6KAThrXm5rEGHLCU/Oe2FX8WrWZ2wooTs7 TM/zw7c3r0DWV1Jg58qSWUcZLCJYaU8Un26HKbIrjo+hvNX5uWx/qs7Ffhr89bOZJAmB 2PBQ== MIME-Version: 1.0 X-Received: by 10.66.5.135 with SMTP id s7mr137277pas.154.1395456369034; Fri, 21 Mar 2014 19:46:09 -0700 (PDT) Received: by 10.68.157.73 with HTTP; Fri, 21 Mar 2014 19:46:08 -0700 (PDT) In-Reply-To: <20140322100424.05f163fc@X220.alogt.com> References: <20140316130936.3f2d18e0@X220.alogt.com> <20140316134309.2edc258a@X220.alogt.com> <5325E71D.30800@bluerosetech.com> <20140317082308.29cc140a@X220.alogt.com> <20140322092336.23aeffe9@X220.alogt.com> <20140322100424.05f163fc@X220.alogt.com> Date: Fri, 21 Mar 2014 21:46:08 -0500 Message-ID: Subject: Re: Another case of the vanishing disk From: cruxpot To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Mar 2014 02:46:09 -0000 I was referring to enabling AHCI in the BIOS. Right now the disks are in some kind of PATA or mixed mode and I do not have ahci_enable enabled in the rc.conf. I don't know if turning that on will help or not but it's something I could try. On Fri, Mar 21, 2014 at 9:04 PM, Erich Dollansky wrote: > Hi, > > On Fri, 21 Mar 2014 20:54:30 -0500 > cruxpot wrote: > >> I can do that but it was disk 4 this time. Last time it was disk 3 and >> before that it was it was something else. That is why I suspect the >> controller or AHCI more than the disks since they all have the same >> error accrual. >> >> I could move the disks to the backup server and see if I get a drop >> and check error rate there. That is an idea. > > yes, just change something. You can also move all disks. This way you > see if the disks are the source of the problem. AHCI? If this would be > the problem, there would be a very basic problem with FreeBSD or the > drives. > > Erich > >> On Mar 21, 2014 8:23 PM, "Erich Dollansky" >> wrote: >> >> > Hi, >> > >> > I would test the disks in a different setup. Can you connect them >> > to a different machine? Not in one go but disk by disk. >> > >> > Can you run the original machine just with one disk using UFS? >> > >> > As and example: I have here one disk from a broken machine which >> > gives problems in my new machine. I do not think that the disk also >> > got broken the moment the other machine died. So, I will keep the >> > disk until I can use it in a different environment. >> > >> > With other words: strange things happen ones in a while. >> > >> > Erich >> > >> > >> > >> > On Fri, 21 Mar 2014 20:03:43 -0500 >> > cruxpot wrote: >> > >> > > Well, it happened again five days after the first time. Does >> > > anyone think that turning on AHCI in the BIOS and the rc.conf >> > > options will help? BIOS has the latest firmware. Otherwise I am >> > > going to start replacing hardware. Not sure if I will replace the >> > > disks or motherboard first since it's so old (circa 2008, >> > > A8R-MVP). >> > > >> > > On Sun, Mar 16, 2014 at 9:47 PM, cruxpot >> > > wrote: >> > > > According to my logs the first occurrence was on July 3rd of >> > > > last year but that is also as far back as my logs go. I have >> > > > four logged incidents since that time with the most recent on >> > > > March 13th, which caused my zfs pool to become corrupt thus >> > > > bringing it to my attention. I remember this server locking up >> > > > before that, but I didn't do much investigation and just cold >> > > > cycled it. I did not really look into it until December which >> > > > is also when I replaced the PSU and it did not solve the >> > > > problem. It is possible it has been doing this since the >> > > > beginning but I am uncertain. >> > > > >> > > > On Mar 16, 2014 7:23 PM, "Erich Dollansky" >> > > > wrote: >> > > >> >> > > >> Hi, >> > > >> >> > > >> On Sun, 16 Mar 2014 16:29:43 -0500 >> > > >> cruxpot wrote: >> > > >> >> > > >> > I guess I did shoot myself in the foot on buying these >> > > >> > drives, but they were $75/each at Best Buy on a sale about >> > > >> > two years ago and I thought it was too good to pass up. >> > > >> > >> > > >> so, you have the problems since two years then? >> > > >> >> > > >> Erich >> > > _______________________________________________ >> > > freebsd-questions@freebsd.org mailing list >> > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > > To unsubscribe, send any mail to >> > > "freebsd-questions-unsubscribe@freebsd.org" >> > >> > >