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

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 04:20 +0100
Message-ID	<HRZXr-pB1-1@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>
Organization	occasionally

Show all headers | View raw

On Wed, 3 Jan 2024 00:29:42 +0000
Andy Smith <andy@strugglers.net> wrote:

> Hello,
> 
> On Tue, Jan 02, 2024 at 04:42:37PM -0700, Charles Curley wrote:
>  [...]  
> 
> If a SMART long self-test came back clean then it already has been
> re-mapped as a long self-test reads every user-accessible sector.

I'm not so sure about that. See the journalctl output at the bottom of
this email.


> 
> If you really want to reassure yourself, look back in your logs for
> the actual sector number and then read it with hdparm. Either it
> prints the raw data or it gives an error.
> 
> # hdparm --read-sector [sector number] /dev/sda
> 
> (generally safe as it's only a read)

I'll try that later. I don't want to take the time now to isolate the
relevant log entries.

> 
> It is annoying when a remapped bad sector doesn't seem to increment
> the "remapped" count and decrement the "pending" count, but I've had
> it happen. I wouldn't particularly worry about it unless the number
> keeps going up OR the actual sector is still unreadable (though the
> self-test should have spotted that).
> 
> You can reconfigure smartd so that it only warns you about error
> values that increase, not just the presence of the non-zero value
> every 30 minutes. That's discussed in the comments of
> /etc/smartd.conf and its man page.

Good thoughts, thank you.

> 
> > It's the only one on the computer.  
> 
> Like to live dangerously, huh…

No. That's what fast networks, good and multiple backup programs, a
good RAID array on another computer, and multiple off-site backups are
for.

> 
> Thanks,
> Andy
> 

root@tiassa:~# journalctl -b -u smartmontools.service 
Jan 02 12:37:39 tiassa systemd[1]: Starting smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon...
Jan 02 12:37:39 tiassa smartd[740]: smartd 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-amd64] (local build)
Jan 02 12:37:39 tiassa smartd[740]: Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
Jan 02 12:37:39 tiassa smartd[740]: Opened configuration file /etc/smartd.conf
Jan 02 12:37:39 tiassa smartd[740]: Drive: DEVICESCAN, implied '-a' Directive on line 21 of file /etc/smartd.conf
Jan 02 12:37:39 tiassa smartd[740]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jan 02 12:37:39 tiassa smartd[740]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Jan 02 12:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], opened
Jan 02 12:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], NS256GSSD330, S/N:W3ZK047027T, FW:V0823A0, 256 GB
Jan 02 12:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], not found in smartd database 7.3/5533.
Jan 02 12:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Jan 02 12:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.NS256GSSD330-W3ZK047027T.ata.state
Jan 02 12:37:39 tiassa smartd[740]: Monitoring 1 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Jan 02 12:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.NS256GSSD330-W3ZK047027T.ata.state
Jan 02 12:37:39 tiassa systemd[1]: Started smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.
Jan 02 13:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 13:07:39 tiassa smartd[740]: Sending warning via /usr/share/smartmontools/smartd-runner to root ...
Jan 02 13:07:39 tiassa smartd[740]: Warning via /usr/share/smartmontools/smartd-runner to root: successful
Jan 02 13:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 14:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 14:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 14:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], self-test in progress, 20% remaining
Jan 02 15:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 15:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], previous self-test completed without error
Jan 02 15:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 16:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 16:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 17:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 17:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 18:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 18:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 19:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 19:37:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Jan 02 20:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
root@tiassa:~# 

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

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