From owner-freebsd-questions@FreeBSD.ORG Sat Mar 28 10:03:13 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69B4FF15 for ; Sat, 28 Mar 2015 10:03:13 +0000 (UTC) Received: from smtp206.alice.it (smtp206.alice.it [82.57.200.102]) by mx1.freebsd.org (Postfix) with ESMTP id EF891D82 for ; Sat, 28 Mar 2015 10:03:12 +0000 (UTC) Received: from soth.ventu (87.18.56.84) by smtp206.alice.it (8.6.060.28) (authenticated as acanedi@alice.it) id 547D8AFA15DF92F3 for freebsd-questions@freebsd.org; Sat, 28 Mar 2015 11:03:05 +0100 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.15.1/8.14.9) with ESMTP id t2SA34G6087598 for ; Sat, 28 Mar 2015 11:03:04 +0100 (CET) (envelope-from ml@netfence.it) Message-ID: <55167C58.5000809@netfence.it> Date: Sat, 28 Mar 2015 11:03:04 +0100 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: smartctl References: <0LzskF-1ZWnak3ftL-0150PB@mail.gmx.com> In-Reply-To: <0LzskF-1ZWnak3ftL-0150PB@mail.gmx.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2015 10:03:13 -0000 On 03/28/15 06:05, CK wrote: > Regarding the unexpected loss of files from the filesystem under various > loads, is the appended 'smartctl' data sufficient to make the determination > that the loss of files while the operating system is in use could be due to > the condition of the drive? I half trust smartctl and I half trust the logs: if these give errors, the drive is bad (although it could possibly be repaired by the vendor tools). The only thing I really trust are the vendors testing tools (Ultimate Boor CD might be a good start), but you can't run them while the disk is mounted on a running system. > 1) I would expect a FreeBSD error to the effect of "unable to read/write > /dev/ada0" or "block checksum does not match block data". Usually I get read errors in the log when a drive is bad. > 2) I would expect that all data read/written to from a drive is verfied to be > correct by FreeBSD with checksums, and that it is guaranteed to be correct > if there are no serious and fatal errors reported by the operating system. Can't tell, sorry. > My past experience has only > taught me that when a drive begins to make very bad noises, this generally > accompanies obvious and serious problems When a drive starts making noises it's already too late; SMART was born to warn in advance. Whether it works (or to what extent) is an open issue. > and that a drive fails when the mechanical parts fail, I've also seen dead drive which were mechanically perfect: it was the electronics which died (although I admin this is less frequent). > SMART overall-health self-assessment test result: PASSED > ... > SMART Error Log Version: 1 > No Errors Logged This is a little reassuring, but don't trust it blindly. If you suspect something, run the tests. > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. Maybe it's normal, I don't know, but I would investigate this. > Self-test execution status: ( 0) The previous self-test routine completed > without error or no self-test has ever > been run. > ... > No self-tests have been logged. [To run self-tests, use: smartctl -t] If you cannot stop the system and run the vendor tools, I strongly suggest to at least run these tests. bye av.