Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265430
| 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 00:50 +0100 |
| Message-ID | <HRWGd-ntk-1@gated-at.bofh.it> (permalink) |
| References | <HRVK9-mRQ-1@gated-at.bofh.it> <HRW3v-ngX-3@gated-at.bofh.it> |
| Organization | occasionally |
On Tue, 2 Jan 2024 18:01:32 -0500 Dan Purgert <dan@djph.net> wrote: > On Jan 02, 2024, Charles Curley wrote: > > I have a brand new NVME device, details below, in a brand new > > computer. smartd just started returning pending sector errors. > > Means you've got "N" bad sector(s) on the drive. It happens, even on > new drives. Good to know. > > > > > A recent extended (long) test run since the first reported pending > > sector returned no errors. > > > > How worried should I be? > > I wouldn't be "very" worried; but I'd keep an eye on it (especially > with regards to any warranties you may have on the machine) OK, will do. If I understand that entry in the SMART report, the offending sector should eventually be re-mapped or else marked as unrecoverable. If the latter, I'll get really concerned. > > > Device Model: NS256GSSD330 > > Serial Number: W3ZK047027T > > You kinda removed the important bits out of this report with regards > to the drive health. Sorry. See my recent reply to Dan Ritter <dsr@randomstring.org>. > That being said, this drive is not an NVMe -- > did you check the right one? It's the only one on the computer. Dan Ritter <dsr@randomstring.org> corrected that. https://smarthdd.com/database/Netac-SSD-256GB/S0626A0/ -- 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