Date: Thu, 11 Mar 2010 14:47:25 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= <uqs@spoerlein.net> To: freebsd-current@freebsd.org Subject: Re: A tool for remapping bad sectors in CURRENT? Message-ID: <20100311134725.GU12229@acme.spoerlein.net> In-Reply-To: <20100308110919.GA31573@office.redwerk.com> References: <mailpost.1268044056.2992919.61277.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> <4B94D1FC.1050407@FreeBSD.org> <20100308105243.GA31468@office.redwerk.com> <20100308110919.GA31573@office.redwerk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 08.03.2010 at 13:09:19 +0200, Eugene Dzhurinsky wrote: > On Mon, Mar 08, 2010 at 12:52:43PM +0200, Eugene Dzhurinsky wrote: > > dd if=/dev/ad4 of=/dev/null skip=222342559 bs=512 count=1 > > dd: /dev/ad4: Input/output error > > 0+0 records in > > 0+0 records out > > 0 bytes transferred in 2.351940 secs (0 bytes/sec) > > > > dd if=/dev/zero of=/dev/ad4 seek=222342559 bs=512 count=1 > > dd: /dev/ad4: Operation not permitted > > > > Should I do it in single mode? > > sysctl kern.geom.debugflags=0x10 > > Did the trick, I was able to write directly to the sector, and now it seems to > work well. No remaps recorded thus, but no errors so far. It's too late now, but you really should have gone with something like # recoverdisk /dev/ad4 /dev/ad4 this will re-write all blocks on the disk, it may fail at reading block 222342559, but there's a chance that the disk error correction gets it right after a couple of times. Regards, Uli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100311134725.GU12229>