From owner-freebsd-questions@freebsd.org Mon Oct 17 17:02:36 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5763C152DF for ; Mon, 17 Oct 2016 17:02:36 +0000 (UTC) (envelope-from jasoncwells@fastmail.com) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E99B67E for ; Mon, 17 Oct 2016 17:02:36 +0000 (UTC) (envelope-from jasoncwells@fastmail.com) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 5D240206E6 for ; Mon, 17 Oct 2016 13:02:29 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 17 Oct 2016 13:02:29 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=VIb 01IdhvOIaLgbBQM7Xo0NhxeY=; b=4Y0QhezYoPMrx3/dwrp9Hq4pLmi3JriJB/Y 1Y/xB53w0U1AR1uoBmgNmAgZ9Z4AsdHe0ykTG6sTzZDBIYfkj3p/vwgKdzXrU5ku Fy81E79bsS/r1uHpUyKGRweRxFUT+DNNXd7SGhfU7MVFWb/DExdKHc3Z5jVzk6e3 EW25hFMI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=VIb01IdhvOIaLgbBQM7Xo0NhxeY=; b=SzFnv Y12WGRC3W4vIQeAElH1ad83UqBDA1B9IflVDAkGzcZzVFwocICqEEtGm0c0ckbEb G0Syh24C0YxDWb8IoNBx+5YpDcf+gim3iLscxNWCZBMR/Jm3NKv6zYnspD+1B8tt ti8tp0Fubea9xkec7hPlgXb+frfEgvDD3FF1O4= X-Sasl-enc: 2Hlk/VKyNAyZglrD0qXcbXGrfFd9ZVuS9wyzl5GPKh3X 1476723749 Received: from [192.168.1.195] (174-31-141-127.tukw.qwest.net [174.31.141.127]) by mail.messagingengine.com (Postfix) with ESMTPA id E2716CC0C4 for ; Mon, 17 Oct 2016 13:02:28 -0400 (EDT) To: freebsd-questions@freebsd.org From: "Jason C. Wells" Subject: Drive Read Errors Message-ID: <7353bec4-4a98-7e86-bda9-4c401bb2ad71@fastmail.com> Date: Mon, 17 Oct 2016 10:02:28 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 17:02:36 -0000 I have a drive that has always been troublesome. My first indication was that the gmirror would end up degraded and restoring it would be extremely time consuming. (Excuse the terminology, it has been a while since I did that part.) I gave up on the drive and removed it from the mirror permanently. 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? Thanks, Jason C. Wells