Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265512
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: 1 Currently unreadable (pending) sectors How worried should I be? |
| Date | 2024-01-04 17:50 +0100 |
| Message-ID | <HSz4R-MvE-1@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <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> <HSg2d-zO6-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 3 Jan 2024 13:25 -0700, from charlescurley@charlescurley.com (Charles Curley):
>> 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.
I covered that on the next few lines, which you choose not to quote.
> Since there is another operating system on this drive,
That kind of information might be helpful to include up front.
> and there are parts of
> the drive normally inaccessible to any operating system,
That's true, but it would have told you about any error in any
accessible data _and_ also told you which file or directory was
affected if that was the case. If the error is in an inaccessible
portion of the drive and the system is working normally aside from a
note in SMART data, then it would stand to reason that the error would
be in an unused location; thereby not likely to affect usage (because
a known bad spot would be reallocated elsewhere by the firmware on the
next write).
Also, badblocks too will only deal with user-accessible blocks; if the
drive already had remapped a bad location, for example as a part of a
write to an identified bad block, the original error would be
invisible to badblocks even if it still was an error.
On 3 Jan 2024 16:27 -0700, from charlescurley@charlescurley.com (Charles Curley):
> OOPS! -w is the destructive test. I now have a hard drive full of 0x00s.
After restoring your most recent backup, consider doing a fstrim to
TRIM unused blocks.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
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