From owner-freebsd-questions@freebsd.org Sun Apr 17 20:02:08 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 A187FB10D7E for ; Sun, 17 Apr 2016 20:02:08 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6714E1BF9 for ; Sun, 17 Apr 2016 20:02:08 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1arstR-0007Sm-1M for freebsd-questions@freebsd.org; Sun, 17 Apr 2016 22:02:05 +0200 Received: from pool-72-66-1-32.washdc.fios.verizon.net ([72.66.1.32]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Apr 2016 22:02:05 +0200 Received: from nightrecon by pool-72-66-1-32.washdc.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Apr 2016 22:02:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Subject: Re: tool for mapping away bad blocks on an external disk Date: Sun, 17 Apr 2016 16:03:03 -0400 Lines: 47 Message-ID: References: <20160417072641.GA2358@c720-r292778-amd64> <20160417093957.0b1acb4c37d7c15a4b06af88@sohara.org> Reply-To: nightrecon@hotmail.com Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-72-66-1-32.washdc.fios.verizon.net X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2016 20:02:08 -0000 Warren Block wrote: > On Sun, 17 Apr 2016, Michael Powell wrote: > >> Back in the day (Fixed Direct Access SCSI-2 device) you could use the >> controller BIOS to do what used to be known as a "low level format" of >> SCSI drives in order to attempt to squeak a little more life from them. >> And if new bad spots did not begin to pop again right away you might be >> good to go for a while. If they did it indicated mass media failure that >> would just avalanche. The old Adaptec 1540 and 2940 controllers come to >> mind (Ctrl-A to enter the controller BIOS during POST). >> >> Can't do this through a USB subsystem. > > Or to pretty much any drive any more. They will accept the low-level > format command, but return immediately. Or that's what happened the > last time I tried it, years ago. Most of the time when low-level format was discussed wrt to IDE drives it was fake. All it really did was fill the drive with zeros. It is possible to low-level an IDE, but generally the manufacturers would not release the ability to the public. They could low-level a drive but they didn't want end users doing it; they would rather sell you another drive. A true low-level regenerates the remap zone in tandem. It isn't that it isn't possible, per se, but that's it's so dangerous to actually try it with an IDE drive the mfr does not want the end user to be able to even try. Hence the 'fake' write zeros to all media and call it "low-level" as a marketing gimmick. When you low-level a SCSI drive it's the real thing. > It's been a long time since hard drives gave any direct access to the > media. Everything goes through the controller on the drive now, which > handles all that transparently. So blocks that appeared bad might be > already mapped out by the drive. In IDE the remap zone is finite. As long as it's not full the end user won't see errors as the drive is handling this behind the scene. Once the remap zone becomes full, then the errors have no place to remap to, and you begin to see the dead sectors. Low-leveling a SCSI drive wiped everything and reinitialized the bad sector table to reflect the current status, which could be repeated. To do this with an IDE drive it really can only be done by the manufacturer, and they won't. It's "buy a new drive time." -Mike