Date: Sun, 21 Aug 2011 02:00:33 -0700 From: perryh@pluto.rain.com To: freebsd@jdc.parodius.com Cc: ml@os2.kiev.ua, freebsd-stable@freebsd.org, dan@langille.org Subject: Re: bad sector in gmirror HDD Message-ID: <4e50c931.gCNlQFqn5sVQXXax%perryh@pluto.rain.com> In-Reply-To: <20110820183456.GA38317@icarus.home.lan> References: <1B4FC0D8-60E6-49DA-BC52-688052C4DA51@langille.org> <20110819232125.GA4965@icarus.home.lan> <B6B0AD0F-A74C-4F2C-88B0-101443D7831A@langille.org> <20110820032438.GA21925@icarus.home.lan> <4774BC00-F32B-4BF4-A955-3728F885CAA1@langille.org> <4E4FF4D6.1090305@os2.kiev.ua> <20110820183456.GA38317@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremy Chadwick <freebsd@jdc.parodius.com> wrote: > ... using dd to find the bad LBAs is the only choice he has. or sysutils/diskcheckd. It uses a 64KB blocksize, falling back to 512 -- to identify the bad LBA(s) -- after getting a failure when reading a large block, and IME it runs something like 10x faster than dd with bs=64k. It would be advisable to check syslog configuration before using diskcheckd, since that is how it reports and there is reason to suspect that the as-shipped syslog.conf may discard at least some of diskcheckd's messages.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e50c931.gCNlQFqn5sVQXXax%perryh>