[smartmontools-support] smartd mails different from smartctl results

Nicola Urbinati urbaman at gmail.com
Tue Mar 7 15:22:39 CET 2023


Hi,

One more insight, I'm seeing this:

Mar 07 12:05:11 pbs1 smartd[1236]: Device: /dev/nvme0, number of Error
Log entries increased from 41 to 42
Mar 07 13:05:12 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
unreadable (pending) sectors
Mar 07 13:35:11 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
unreadable (pending) sectors
Mar 07 14:05:12 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
unreadable (pending) sectors
Mar 07 14:35:12 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
unreadable (pending) sectors
Mar 07 15:05:11 pbs1 smartd[1236]: Device: /dev/sda [SAT], 1 Currently
unreadable (pending) sectors

And that's why I'm receiving all those emails, and I see no email reset.

Il giorno mar 7 mar 2023 alle ore 15:09 Nicola Urbinati
<urbaman at gmail.com> ha scritto:
>
> Hi,
>
> Thank you very much for pointing me in the right direction.
>
> I do have this drive:
>
> === START OF INFORMATION SECTION ===
> Device Model:     CT4000MX500SSD1
> Serial Number:    2204E602EAA2
> LU WWN Device Id: 5 00a075 1e602eaa2
> Firmware Version: M3CR044
>
> And smartmontools 7.2 (default I think with debian 11, even if it's a
> Proxmox Backup Server instance?).
>
> I tried to download the new database file for the same release (7.2)
> from github, but a diff command showed no difference at all.
> Is there a better way to use a newer database, if the device is there
> at all? I do not have the machine on the internet at the moment,
> probably in a few days.
>
> Thank you again.
>
> Il giorno mar 7 mar 2023 alle ore 12:21 Christian Franke
> <Christian.Franke at t-online.de> ha scritto:
> >
> > Hi,
> >
> > Nicola Urbinati wrote:
> > > Hi,
> > >
> > > I have a problem with a Crucial ssd.
> > > I am receiving e-mails almost once every hour with the same advice: 1
> > > pending block.
> >
> > If a problem persists, reminder emails would never be sent each hour
> > unless the new directive '-M always' is specified.
> > Please check syslog for messages like:
> > "Device /dev/... No more Currently unreadable (pending) sectors, warning
> > condition reset after 1 email"
> >
> > This suggests that the pending block count flips between 0 and 1. This
> > is a known issue with Crucial MX500:
> > https://www.smartmontools.org/ticket/1227
> >
> >
> > > If I do a smartctl test, 197 and 198 IDs (are they for bad/pending
> > > blocks?) say 0 blocks.
> >
> > If you do a smartctl test very often, you will occasionally see 1 as raw
> > value of attribute 197.
> >
> > Please update the drive database:
> > https://www.smartmontools.org/wiki/Download#Updatethedrivedatabase
> >
> > Attribute 197 should then be named "Current_Pending_ECC_Cnt". This also
> > suppresses the smartd warning EMails.
> > If this is not the case, see:
> > https://www.smartmontools.org/wiki/FAQ#MyATASATAdriveisnotinthesmartctlsmartddatabase
> >
> > You could also suppress the emails in smartd.conf with '-C 0' and enable
> > syslog monitoring of the raw value with '-R 197', see 'man smartd.conf'
> > for details.
> >
> > Regards,
> > Christian
> >


More information about the Smartmontools-support mailing list