Date: Fri, 6 Jan 2012 07:39:38 -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.1201060737330.47888@wonkity.com> In-Reply-To: <4F069A44.7020600@ose.nl> References: <20120105144204.d419cca4.web@3dresearch.com> <6ABAC46B-6193-47B6-B173-94D060E01EC4@mac.com> <4F069A44.7020600@ose.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1201060737330.47888>