Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265563
| Path | csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | David Christensen <dpchrist@holgerdanske.com> |
| Newsgroups | linux.debian.user |
| Subject | Re: 1 Currently unreadable (pending) sectors How worried should I be? |
| Date | Sat, 06 Jan 2024 02:30:02 +0100 |
| Message-ID | <HT3FE-16fl-11@gated-at.bofh.it> (permalink) |
| References | <HRVK9-mRQ-1@gated-at.bofh.it> <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> <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> |
| X-Mailbox-Line | From debian-user-request@lists.debian.org Sat Jan 6 01:26:27 2024 |
| Old-Return-Path | <dpchrist@holgerdanske.com> |
| X-Amavis-Spam-Status | No, score=-7.11 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate: -4.6 |
| MIME-Version | 1.0 |
| User-Agent | Mozilla Thunderbird |
| Content-Language | en-US |
| Content-Type | text/plain; charset=UTF-8; format=flowed |
| Content-Transfer-Encoding | 7bit |
| X-Mailing-List | <debian-user@lists.debian.org> archive/latest/807379 |
| List-ID | <debian-user.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-user/> |
| List-Archive | https://lists.debian.org/msgid-search/28644e79-9931-4f51-b075-8633bce6ca5f@holgerdanske.com |
| Approved | robomod@news.nic.it |
| Lines | 28 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Fri, 5 Jan 2024 17:25:48 -0800 |
| X-Original-Message-ID | <28644e79-9931-4f51-b075-8633bce6ca5f@holgerdanske.com> |
| X-Original-References | <20240102154059.6eba754e@hawk.localdomain> <ZZSVzO6m2qDe1icL@framework.djph.net> <20240102164228.2b76bf5c@hawk.localdomain> <ZZSqdpH2EXBDJzST@mail.bitfolk.com> <20240102201755.2305d6aa@jhegaala.localdomain> <da3e4a06-a70a-42f6-8b6c-fc6602f19317@home.arpa> <20240103132526.65920843@hawk.localdomain> <20240103162754.25af2099@tsalmoth> <ZZhuKHoQV4Y3QVUb@mail.bitfolk.com> <20240105162019.1f8f3bfa@tsalmoth> |
| Xref | csiph.com linux.debian.user:265563 |
Show key headers only | 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
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