Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #265563

Re: 1 Currently unreadable (pending) sectors How worried should I be?

From David Christensen <dpchrist@holgerdanske.com>
Newsgroups linux.debian.user
Subject Re: 1 Currently unreadable (pending) sectors How worried should I be?
Date 2024-01-06 02:30 +0100
Message-ID <HT3FE-16fl-11@gated-at.bofh.it> (permalink)
References (5 earlier) <HS7ih-u9n-11@gated-at.bofh.it> <HSg2d-zO6-3@gated-at.bofh.it> <HSiQp-BxU-1@gated-at.bofh.it> <HSZC1-13Mo-7@gated-at.bofh.it> <HT1Nv-155q-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On 1/5/24 15:20, Charles Curley wrote:
> On Fri, 5 Jan 2024 21:01:28 +0000 Andy Smith wrote:
>> So has this coaxed the drive into reducing its pending sector count
>> to zero or does that still say 1?
> 
> Last I looked, it was still at 1. When I finish my reinstallation, I
> will look again.


I like to do a secure erase before re-deploying an SSD.  The UEFI ROM 
firmware in my newer Dell computers provides an option to make secure 
erase easy.  Other choices include an SSD manufacturer toolkit or 
install/ live/ rescue media with the right tools.  It is also useful to 
have a hot-swap drive rack and matching port, as powering down, 
installing the target drive, powering up, and booting an OS (on 
different media) can result in locked drive security.


I save 'smartctl -x ...' output to text files and check them into a 
version control system.  This facilitates looking for changes and trends 
over time.


I would be curious to know if a secure erase forces the pending sector 
issue and, if so, what the result is.


David

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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