Date: Thu, 29 Mar 2018 16:43:28 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: Chuck Tuffli <chuck@tuffli.net> Cc: Rainer Duffner <rainer@ultra-secure.de>, Charles Sprickman <spork@bway.net>, Tom Evans via freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: smart(8) Call for Testing Message-ID: <be4d85ef-1bd4-d666-42cb-41ad1bc67dd8@FreeBSD.org> In-Reply-To: <CAM0tzX3RanY=vZbCXTAHB3=kv6aVkuzO5pmwr9g%2BZQoe%2BN1hVg@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> <CAM0tzX32v2-=saT5iB4WVcsoVOtH%2BXE0OQoP7hEDB1xE%2Bxk%2Bsg@mail.gmail.com> <1d3f2cef-4c37-782e-7938-e0a2eebc8842@quip.cz> <A548BC90-815C-4C66-8E27-9A6F7480741D@bway.net> <7ED27465-1BC2-4522-873E-9ECE192EB7A2@ultra-secure.de> <e54ab9a7-835d-16c7-1fdd-9f8285c0642b@FreeBSD.org> <CAM0tzX3RanY=vZbCXTAHB3=kv6aVkuzO5pmwr9g%2BZQoe%2BN1hVg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29.03.2018 16:27, Chuck Tuffli wrote: >>> Maybe one of the vendors who sells FreeBSD as part of an appliance has shown some interest in this? >>> >>> If you’re hardware is well-defined and thus the output is consistent, I could imagine it’s not too difficult to parse this. >> smartd is very important part of smartmontools, smartctl is not so. >> >> And periodic self-test triggering & check is most important feature of >> smartd, IMHO. >> >> Modern HDDs are liers in SMART. And only regular self-test discover >> real errors on surfaces in my experience. >> >> So, tool without support for HDD self-tests is of little usage for >> appliances, IMHO. > Thank you for the feedback! As I don't have any experience with > smartd, can you help me better understand which parts of it are most > useful to you? Is it just periodically triggering the self test or > are there other features as well? For example, logging the SMART > values, emailing / triggering notifications when certain criteria are > met, monitoring the self tests, reading the error logs, etc.? Triggering of short and full self-tests and alerting (via e-mail) when test failed. Monitoring of values and alerting is VERY important (number of Relocations is main indicator of spinning HDD health and when it raises it must be known ASAP), but it could be implemented with simple smart(8) utility and some scripting, so this is not problem. But all my dead HDDs were replaced on self-test fail — it is what allows me to replace them BEFORE data were lost. -- // Lev Serebryakov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?be4d85ef-1bd4-d666-42cb-41ad1bc67dd8>