Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265451
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: 1 Currently unreadable (pending) sectors How worried should I be? |
| Date | 2024-01-03 21:30 +0100 |
| Message-ID | <HSg2d-zO6-3@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <HRW3v-ngX-3@gated-at.bofh.it> <HRWGd-ntk-1@gated-at.bofh.it> <HRXsB-nXk-1@gated-at.bofh.it> <HRZXr-pB1-1@gated-at.bofh.it> <HS7ih-u9n-11@gated-at.bofh.it> |
| Organization | occasionally |
On Wed, 3 Jan 2024 11:05:10 +0000
Michael Kjörling <2695bd53d63c@ewoof.net> wrote:
> Since both tests finished without
> finding any errors, there _should_ have been no unreadable sectors.
Agree.
>
> I'm inclined to believe that your drive is fibbing SMART data.
Sigh. I am inclined to agree. Obviously they didn't hire me to write
the firmware on the drive.
>
> As a background process, try running something like
>
> # ionice find / -xdev -type f -exec cat {} + >/dev/null
That would only reach files on the partition where it is run. Since
there is another operating system on this drive, and there are parts of
the drive normally inaccessible to any operating system, I decided
instead to boot to a USB stick and run badblocks. The read-only test
took 12 minutes and reported no errors.
I now have a writing test (-w) running. It has reported no failures on
its first pass.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-02 23:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Dan Ritter <dsr@randomstring.org> - 2024-01-03 00:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 00:40 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Dan Ritter <dsr@randomstring.org> - 2024-01-03 02:00 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Tixy <tixy@yxit.co.uk> - 2024-01-03 08:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Dan Purgert <dan@djph.net> - 2024-01-03 00:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 00:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Andy Smith <andy@strugglers.net> - 2024-01-03 01:40 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 04:20 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-03 12:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-03 21:30 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-04 00:30 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? <tomas@tuxteam.de> - 2024-01-04 12:00 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-04 15:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Andy Smith <andy@strugglers.net> - 2024-01-05 22:10 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-06 00:30 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? David Christensen <dpchrist@holgerdanske.com> - 2024-01-06 02:30 +0100
Secure erase [was: Re: 1 Currently unreadable (pending) sectors How worried should I be?] Max Nikulin <manikulin@gmail.com> - 2024-01-06 03:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Charles Curley <charlescurley@charlescurley.com> - 2024-01-06 06:20 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? David Christensen <dpchrist@holgerdanske.com> - 2024-01-06 09:40 +0100
Re: reinstallation and restore after catastrophic mistake or failure; was: 1 Currently unreadable (pending) sectors How worried should I be? Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-06 13:40 +0100
Re: reinstallation and restore after catastrophic mistake or failure; was: 1 Currently unreadable (pending) sectors How worried should I be? David Christensen <dpchrist@holgerdanske.com> - 2024-01-07 00:40 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Max Nikulin <manikulin@gmail.com> - 2024-01-04 16:20 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-04 17:50 +0100
Re: 1 Currently unreadable (pending) sectors How worried should I be? Andy Smith <andy@strugglers.net> - 2024-01-03 14:30 +0100
csiph-web