Date: Fri, 6 Jan 2012 12:32:14 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Bas Smeelen <b.smeelen@ose.nl> Cc: freebsd-questions@freebsd.org Subject: Re: Apparently conflicting smartctl output Message-ID: <alpine.BSF.2.00.1201061229020.49884@wonkity.com> In-Reply-To: <4F072484.9070100@ose.nl> References: <20120105144204.d419cca4.web@3dresearch.com> <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> <4F069A44.7020600@ose.nl> <alpine.BSF.2.00.1201060737330.47888@wonkity.com> <4F070CA6.5050803@ose.nl> <alpine.BSF.2.00.1201060830430.48656@wonkity.com> <4F072484.9070100@ose.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Jan 2012, Bas Smeelen wrote: > On 01/06/2012 04:37 PM, Warren Block wrote: >> On Fri, 6 Jan 2012, Bas Smeelen wrote: >> >>> On 01/06/2012 03:39 PM, Warren Block wrote: >>>> On Fri, 6 Jan 2012, Bas Smeelen wrote: >>>> >>>>> I have had this with a drive and multiple read errors would not remap >>>>> the >>>>> sector. >>>>> With write errors the sector would be remapped. This was a new Samsung >>>>> laptop drive though, not a Western Digital. >>>> >>>> That's standard. Sectors are only remapped to spares on a write error. >>>> >>>>> To get the sector remapped I had to fully write the drive and it was ok >>>>> after that. >>>> >>>> Just writing to the sector should be enough. Of course, when one sector >>>> goes bad, others often follow. >>> >>> I just hope it does not develop more bad sectors. >> >> That's the worrying thing. Was it just a loose flake of oxide, or was it a >> strip that peeled off the disk? > > No way to know I guess >> >>>> From what I read on the "Bad block HOWTO for smartmontools" on >>>> sourceforge >>> it's not trivial to just write to that sector and also it would destroy >>> the >>> filesystem? >> >> Finding the right block may not be too hard. /var/log/messages should show >> the block number, but then I don't know what tool is available to write to >> that specific block. Tools like that are not common because generally, >> growing bad sectors means the drive is starting to fail anyway. > > I could use dd if=/dev/random of=file seek=blocks_to_skip bs=100M the next > time Yes, if you're not worried about existing data. But use /dev/zero (faster and you can verify the value) and bs=1M count=100 (ties up only 1M of buffer space).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1201061229020.49884>