From owner-freebsd-questions@freebsd.org Tue Nov 17 17:23:44 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 851BAA314F2 for ; Tue, 17 Nov 2015 17:23:44 +0000 (UTC) (envelope-from will.senn@gmail.com) Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 44E7412E2 for ; Tue, 17 Nov 2015 17:23:44 +0000 (UTC) (envelope-from will.senn@gmail.com) Received: by ykfs79 with SMTP id s79so17766474ykf.1 for ; Tue, 17 Nov 2015 09:23:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=4znJatoomwyqMxioLoMoghiD0d83Datdd4LB7poOC5s=; b=fmWxwep6Zuu2xGsZKO2O1A02RBbQybLqjzMtD8fPzBuPO8ydFk2wPCdadKhmVcK7Lc FINMyndfcnQEfVi5agy2gm0sdO0UCQjaZlEvRZ3c3D9fDxuGyWB7w7JwaX21Ic/4nrxQ 2EJ9+mKhr103YRpu77UR6FueJW9odY1BUnC7W/fuBgqzwSVyrBeQRmFoJMa7EVBw14rZ r93kfJ7xQmCzek0HP7iAkvJm3HsQGHocY4FGMhljyK5181TDWcyVk1srVBKvNKbQaT3Y QIePMXO7p7rOs89ZBOYvmrjT6BxyuRh8TSA9hGpNrZKIw/DPh8WzREDkyOoa0E06gOw6 jalQ== X-Received: by 10.129.106.193 with SMTP id f184mr45919740ywc.157.1447781023448; Tue, 17 Nov 2015 09:23:43 -0800 (PST) Received: from [192.168.0.4] ([206.251.219.82]) by smtp.gmail.com with ESMTPSA id i141sm40161737ywc.2.2015.11.17.09.23.42 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 Nov 2015 09:23:42 -0800 (PST) Subject: Re: Kernel panic and hard disk failure To: CyberLeo Kitsana , freebsd-questions@freebsd.org References: <5649F4D1.8070105@gmail.com> <564B4062.30301@cyberleo.net> From: Will Senn Message-ID: <564B629D.4060909@gmail.com> Date: Tue, 17 Nov 2015 11:23:41 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <564B4062.30301@cyberleo.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 17:23:44 -0000 On 11/17/15 8:57 AM, CyberLeo Kitsana wrote: > You'll notice the crashdump files are named with .0, .1, .2 suffixes. > This file contains the next available number. If you leave the bounds > file with a '3' in it, but delete the crashdump files, the next > crashdump will have the suffix .3 . This ensures it will not > inadvertently overwrite a previous crashdump. Consult the savecore > manpage for further information. >> 2. What is minfree? > From savecore(8): > > The savecore utility also checks the available disk space before > attempting to make the copies. If there is insufficient disk space in > the file system containing directory, or if the file directory/minfree > exists and the number of free kilobytes (for non-superusers) in the > file system after the copies were made would be less than the number in > the first line of this file, the copies are not attempted. > >> 3. What does it mean that the device went missing? > The hard drive stopped responding and the controller decided it was no > longer connected. > >> 4. Does the information above sound like a faulty hard drive or are >> there additional tests that will tell me more about the failure? > Could be a failing hard drive; but it could also be a bad data cable or > weak or failing power supply. > Thanks for the pointer to savecore and for the answers. I'll keep an eye out for additional failures and if there are any with the replacement drive, I'll check into cables and such. -will