Date: Sun, 29 Jul 2018 23:43:53 -0700 From: Robert Banz <rob@nofocus.org> To: Peter Jeremy <peter@rulingia.com> Cc: Robert Clausecker <fuz@fuz.su>, freebsd-fs@freebsd.org Subject: Re: badsect(8) is gone -- what now? Message-ID: <CA%2B-fWwBUZRTKdCUJJ1ikC_L6ZxOsLnBj2EN6Sj5xstp=of5Wcw@mail.gmail.com> In-Reply-To: <20180730063804.GA4409@server.rulingia.com> References: <20180727130743.GB45967@fuz.su> <20180730063804.GA4409@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
And if you=E2=80=99re just trying to recover your data from said disk, try = out =E2=80=98ddrescue=E2=80=99 and dump the partition to a file or another disk= . On Mon, Jul 30, 2018 at 2:38 AM Peter Jeremy <peter@rulingia.com> wrote: > On 2018-Jul-27 15:07:43 +0200, Robert Clausecker <fuz@fuz.su> wrote: > >Is there any way the kernel interface for badsect(8) or a utilitiy > >fulfilling a similar purpose is going to come back? I understand that > >kernel support was removed due to possible misuse of mknod(S_IFMT) > >leading to crashes [1], but there really ought to be some way to mark a > >sector as bad if the disk doesn't want to do it for you. > > All modern disks do bad sector mapping in the drive firmware. In general= , > if you disk reaches a point where it can't remap a visibly bad sector the= n > the drive's internal set of spare blocks is exhausted and the disk is abo= ut > to fail completely. The recommended solution is to replace the disk. Ha= ve > you looked at the disk's SMART stats (using eg > ports/sysutils/smartmontools)? > > One approach I've used in the past is to create a file covering the bad > sector(s), mark it immutable and stash it somewhere where you don't attem= pt > to read it. > > -- > Peter Jeremy >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B-fWwBUZRTKdCUJJ1ikC_L6ZxOsLnBj2EN6Sj5xstp=of5Wcw>