Date: Tue, 27 Mar 2018 07:32:59 -0700 From: Chuck Tuffli <chuck@tuffli.net> To: Mark Saad <nonesuch@longcount.org> Cc: Michael Dexter <editor@callfortesting.org>, freebsd-fs@freebsd.org Subject: Re: smart(8) Call for Testing Message-ID: <CAM0tzX32v2-=saT5iB4WVcsoVOtH%2BXE0OQoP7hEDB1xE%2Bxk%2Bsg@mail.gmail.com> In-Reply-To: <CAMXt9NYMrtTNqNSx256mcYsPo48xnsa%2BCCYSoeFLzRsc%2BfQWMw@mail.gmail.com> References: <4754cb2f-76bb-a69b-0cf5-eff4d621eb29@callfortesting.org> <CAMXt9NbdN119RrHnZHOJD1T%2BHNLLpzgkKVStyTm=49dopBMoAQ@mail.gmail.com> <CAM0tzX1oTWTa0Nes11yXg5x4c30MmxdUyT6M1_c4-PWv2%2BQbhw@mail.gmail.com> <CAMXt9NYMrtTNqNSx256mcYsPo48xnsa%2BCCYSoeFLzRsc%2BfQWMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 26, 2018 at 1:59 PM, Mark Saad <nonesuch@longcount.org> wrote: ... > I was thinking more along the lines of when smartctl reports the overall-health > which is always a good time to read; and very Monty Python-eske > > SMART overall-health self-assessment test result: FAILED! > Drive failure expected in less than 24 hours. SAVE ALL DATA. > > https://serverfault.com/questions/114196/smart-warns-me-but-i-dont-trust-it This app is different from others in that it only reports the values; it is up to the user / script / etc. to provide analysis. In the serverfault example, spin-up time is attribute ID 3. One of my drives shows: $ smart -t da0 | grep "208 3" 208 3 39 0 100 100 1029 smartctl shows it as follows $ smartctl -A /dev/da0 ... 3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1029 It would be up to the user or script to decide at what point this might indicate an imminent failure. --chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM0tzX32v2-=saT5iB4WVcsoVOtH%2BXE0OQoP7hEDB1xE%2Bxk%2Bsg>