Date: Mon, 26 Sep 2022 23:13:57 -0400 From: grarpamp <grarpamp@gmail.com> To: questions@freebsd.org Subject: Re: disk non-destructive bad-block write/fix? Message-ID: <CAD2Ti2-wD3zo4SLttQh=uQoDZYj%2B23g9x2V_QeUZ206J2xS%2BvA@mail.gmail.com> In-Reply-To: <50ee834e-60ef-badb-68ce-f9aa589cd3cc@dreamchaser.org> References: <d687eb29-a3fb-7d91-a2c6-c1e4e1dc7e31@dreamchaser.org> <1f639118-4bb2-acfd-ab8e-e3aab9a79c9e@holgerdanske.com> <4e864eaefcb7dbed7bdf59d40920a0ab9b964bf5.camel@riseup.net> <50ee834e-60ef-badb-68ce-f9aa589cd3cc@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> This one is harder because of blanks and other stupid characters in find -print0 xargs -0 > Or do you do the whole thing on the fly somehow and only worry about the > one overarching result? People often diff. Lots of ways and tools. And ZFS does checksums internally and emits error notices. >> dd if=/dev/da0 of=/dev/null bs=1m conv=noerror > Am I right in assuming this will skip remapped bad sectors? Just continues reading linear past errors. See manpage. Spares mapped in are transparent to user. Bad sectors mapped out are no longer accessible unless the vendor firmware modepages lets you play with them. FreeBSD might have some bad disk emulator GEOM device by now. > It's been running for several days now... If no output so far, send it a ctrl-t or kill -info, it maybe stuck or has read past end of media size already.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti2-wD3zo4SLttQh=uQoDZYj%2B23g9x2V_QeUZ206J2xS%2BvA>