Date: Wed, 03 Aug 2016 09:00:38 -0500 From: Brandon J. Wandersee <brandon.wandersee@gmail.com> To: Jon Radel <jon@radel.com> Cc: "William A. Mahaffey III" <wam@hiwaay.net>, FreeBSD Questions !!!! <freebsd-questions@freebsd.org> Subject: Re: Ominous smartd messages .... Message-ID: <8637mmdkah.fsf@WorkBox.Home> In-Reply-To: <117bb75c-aa6a-d562-c971-d0bab742f5ad@radel.com> References: <e5a65f8a-27a0-65e7-42db-28bef824e0c0@hiwaay.net> <117bb75c-aa6a-d562-c971-d0bab742f5ad@radel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jon Radel writes: > I've read reasonable sounding commentary from people running very, very > large collections of hard drives that there is a high enough correlation > between this error and the drive going to heck sooner rather than later > that they take this as a sign to replace. [Can't find reference right now.] While there's no way to know from the error message alone just what will happen to the disk in the coming days, the general reasoning is this: sectors are not physically segregated. They all sit on the same platter. Several bad sectors occuring in a short period might be a sign of physical fault in the platter, and if that fault is real then stress from the platter spinning will likely cause that fault to spread. So some people conclude that the appearance of several bad sectors in a short period should just be a signal to replace the disk immediately. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ----------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8637mmdkah.fsf>