Date: Thu, 5 Jul 2018 19:03:30 +0200 (CEST) From: Wojciech Puchar <wojtek@puchar.net> To: Alan Somers <asomers@freebsd.org> Cc: Stefan Blachmann <sblachmann@gmail.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org>, George Mitchell <george+freebsd@m5p.com>, Lev Serebryakov <lev@freebsd.org>, Wojciech Puchar <wojtek@puchar.net> Subject: Re: Confusing smartd messages Message-ID: <alpine.BSF.2.20.1807051859250.34332@puchar.net> In-Reply-To: <CAOtMX2gG48jzWkPg3kGpSVDC89KY14ta3p-U%2BO5yExHZJfNL7w@mail.gmail.com> References: <dfccd275-954c-11da-1790-e75878f89ad1@m5p.com> <51eb8232-49a7-0b3a-2d0f-9882ebfbfa1d@FreeBSD.org> <alpine.BSF.2.20.1807051642090.17082@puchar.net> <CACc-My36jbL=WWpxOB24D_YLDMofSHAk9JgrP86LKd4MEct1mg@mail.gmail.com> <CAOtMX2gG48jzWkPg3kGpSVDC89KY14ta3p-U%2BO5yExHZJfNL7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Rewriting suspicious sectors is useless in this day and age. HDDs and SSDs > already do it internally and have for years. Even healthy sectors get unreadable sectors cannot be rewritten by drive electronics as it doesn't know what to rewrite. it may possibly remap it but still report read error until some data will be written - unless giving no error and returning meaningless data is an accepted behaviour. only on write it can be done properly. > that the HDD/SSD won't fix itself would be a checksum error. Those are yes and this will happen if you powerdown your disk on write. or get some power spike or other source of noise that would affect electronic components. performing full disk rewrite (so not zfs rebuilds) and THEN looking at smart stats and THEN performing regular smartctl -t long will tell the truth. which usually is "drive is fine" in my practice. really faulty drive will QUICKLY develop new problems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1807051859250.34332>