From owner-freebsd-questions@freebsd.org Thu Jun 1 10:27:28 2017 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 BCCEEAF95FC for ; Thu, 1 Jun 2017 10:27:28 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp206.alice.it (smtp206.alice.it [82.57.200.102]) by mx1.freebsd.org (Postfix) with ESMTP id 54E93745BB for ; Thu, 1 Jun 2017 10:27:28 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (79.26.54.44) by smtp206.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 592F7DE10076DF1E for freebsd-questions@freebsd.org; Thu, 1 Jun 2017 12:21:29 +0200 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id v51ALTrK084662 for ; Thu, 1 Jun 2017 12:21:29 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: Advice on kernel panics To: freebsd-questions@freebsd.org References: <20170529092043.GA89682@erix.ericsson.se> <20170601051030.GA39861@geeks.org> <20170601082749.GA80543@erix.ericsson.se> From: Andrea Venturoli Message-ID: <7372da18-cebf-ab0b-abfa-6dd8b8503b6a@netfence.it> Date: Thu, 1 Jun 2017 12:21:29 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170601082749.GA80543@erix.ericsson.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 10:27:28 -0000 On 06/01/17 10:27, Raimo Niskanen wrote: > Any further hints on how to "Check your drive hardware"? Try and change the PSU. I found out some PSU, when getting older, don't provide as much power as they used to do. Disk tests will work because they stress one disk at a time, but when all disks work together, they'll choke due to not getting enough power. Also memtest86+ checks memory when all other components are idle: again when disks and CPUs start playing, the memory banks may fail due to insufficient power. bye av.