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

Groups > linux.debian.user > #265573

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 09:40 +0100
Message-ID <HTanL-1aVH-7@gated-at.bofh.it> (permalink)
References (7 earlier) <HSiQp-BxU-1@gated-at.bofh.it> <HSZC1-13Mo-7@gated-at.bofh.it> <HT1Nv-155q-1@gated-at.bofh.it> <HT3FE-16fl-11@gated-at.bofh.it> <HT7gd-18SR-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On 1/5/24 21:10, Charles Curley wrote:
> On Fri, 5 Jan 2024 17:25:48 -0800
> David Christensen <dpchrist@holgerdanske.com> wrote:
> 
>> I would be curious to know if a secure erase forces the pending
>> sector issue and, if so, what the result is.
> 
> An interesting thought. Alas, I am far enough along on re-installing
> that I do not want to try it. Sorry.


I suggest taking an image (backup) with dd(1), Clonezilla, etc., when 
you're done.  This will allow you to restore the image later -- to 
roll-back a change you do not like, to recovery from a disaster, to 
clone the image to another device, to facilitate experiments, (such as 
doing a secure erase to see if it resolves the SSD pending sector 
issue), etc..


If you also keep your system configuration files in a version control 
system, restoring an image is faster than wipe/ fresh install/ 
configure/ restore data.


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