Date: Wed, 19 Oct 2016 19:54:05 -0400 From: Anton Yuzhaninov <citrin@citrin.ru> To: freebsd-questions@freebsd.org Subject: Re: Drive Read Errors Message-ID: <0916225e-d618-d08a-df98-778e9ed23642@citrin.ru> In-Reply-To: <7353bec4-4a98-7e86-bda9-4c401bb2ad71@fastmail.com> References: <7353bec4-4a98-7e86-bda9-4c401bb2ad71@fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/17/16 13:02, Jason C. Wells wrote: > I recently used smartmontools long test and discovered that the drive > had read errors. > > In your experience, is there any value in trying to use drive by mapping > bad sectors or partitioning around the errors? 1. There is a value if your plan to use this HDD for not important data and downtime is also tolerable. 2. FYI: Remapping of bad sectors nowadays is done by disk's firmware. To make it happen just write any data to a all bad sectors. If disk is clean just run: dd if=/dev/zero of=/dev/adaX bs=256k then rerun SMART slef-test (and or dd if=/dev/adaX of=/dev/null). 3. Many people suggest to throw drive with bad sectors away. Such disk will likely have new pending sectors in future and probability of complete fail is higher than for drive with good SMART, but they can work for years after bad sectors are remapped. All depends on requirements for reliability and budget your have. At home I've used HDD which had slef-test fail and Current_Pending_Sector > 0 in past (for temporary data). See also: https://www.backblaze.com/blog/what-smart-stats-indicate-hard-drive-failures/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0916225e-d618-d08a-df98-778e9ed23642>