Date: Mon, 26 Sep 2022 21:40:37 -0600 From: Gary Aitken <freebsd@dreamchaser.org> To: questions@freebsd.org Subject: Re: disk non-destructive bad-block write/fix? Message-ID: <0dfab0e7-e7bc-4277-c587-eec058f5626c@dreamchaser.org> In-Reply-To: <CAD2Ti2-wD3zo4SLttQh=uQoDZYj%2B23g9x2V_QeUZ206J2xS%2BvA@mail.gmail.com> 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> <CAD2Ti2-wD3zo4SLttQh=uQoDZYj%2B23g9x2V_QeUZ206J2xS%2BvA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/26/22 9:13 PM, grarpamp wrote: >> 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. Thanks, it did finally complete; posted no errors. Which might indicate the bad blocks were in some localized area and were remapped when writing the original backup, and the rest of the disk is "sorta" ok. But since this is a read only test, maybe not. Anyway, thanks all; will do some reformatting and other measures after I get another backup on different media. Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0dfab0e7-e7bc-4277-c587-eec058f5626c>