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

Groups > linux.debian.user > #248181 > unrolled thread

smartctl puzzlement new disk

Started byghe2001 <ghe2001@pm.me>
First post2022-05-14 04:30 +0200
Last post2022-05-20 13:40 +0200
Articles 8 — 5 participants

Back to article view | Back to linux.debian.user

Contents

  smartctl puzzlement new disk ghe2001 <ghe2001@pm.me> - 2022-05-14 04:30 +0200
    Re: smartctl puzzlement new disk David <bouncingcats@gmail.com> - 2022-05-14 04:40 +0200
      Re: smartctl puzzlement new disk ghe2001 <ghe2001@protonmail.com> - 2022-05-14 06:00 +0200
        Re: smartctl puzzlement new disk David <bouncingcats@gmail.com> - 2022-05-14 06:10 +0200
          Re: smartctl puzzlement new disk ghe2001 <ghe2001@protonmail.com> - 2022-05-14 21:20 +0200
            Re: smartctl puzzlement new disk David <bouncingcats@gmail.com> - 2022-05-15 04:10 +0200
    Re: smartctl puzzlement new disk David Christensen <dpchrist@holgerdanske.com> - 2022-05-14 05:10 +0200
    Re: smartctl puzzlement new disk Darac Marjal <mailinglist@darac.org.uk> - 2022-05-20 13:40 +0200

#248181 — smartctl puzzlement new disk

Fromghe2001 <ghe2001@pm.me>
Date2022-05-14 04:30 +0200
Subjectsmartctl puzzlement new disk
Message-ID<EmPHz-fkxq-1@gated-at.bofh.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Supermicro workstation, Debian Buster, smartctl v 6.6

I bought a new 12TB Western Digital Gold SATA disk the other day.  After testing it, smartctl says, among other things:

 22 Unknown_Attribute       0x0023   001   001   025    Pre-fail  Always   FAILING_NOW 13

And it looks like the test is aborted when smartctl sees that error.  And there's lots of yelling all over my monitor.

I found some discussion of ID 22 on the 'Net -- it's often used to mean 'helium level' which makes some sense on a 12TB disk.  But testing the Seagate 12TB next to the Western Digital is OK -- sorta; there's no ID 22 in the output.

The Wikipedia article on S.M.A.R.T lists ID 22 as having to do with the helium.

On the web, it looked like there's a way of changing what ID 22's called so smartctl won't hurl.  I'd like the test to just keep going and tell me the other things it finds.

My questions:

Is this error on ID 22 anything to worry about?
(I'm guessing that it isn't, and smartctl and/or something in the Western Digital disk's firmware is mildly wrong)

Is there really a way to change 22 so smartctl will report the helium level?  How do I do that?

Is there a way to to get smartctl to finish the test?  If so, how do I do that?

TIA...

--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJifw2eACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor
VtFqq3cGBgf/TqUrTKRnKnAR0EcUTErj2uhrJuWZhMJCv73QMFKKk/NJVbJh
izQpLDDD441qM6gwTrFaLBkEtOIjzxb1VdIFSDvQWEz44eWUiBQsOb+T0TfZ
aAupvw46DcCVreG57hJ9esZDPK8ctUZHe4BbPF6KnjwKfRc5yFGNT2HifyXm
X71sF2EqlE2frvgo4Crtb5qkAQIu8ozvwYOuzNZc/BupHl/fck+5IPMHALVg
TaVr8+zsWIwSVndMN3BabaBNE337B/76m9/nlcRe5qinZ564A2MbqrQy2LAk
AOEkb6U7mMNMmvkA0bFdl3vwnNswruBOzEWwti2wmKoAikqBJQHvvQ==
=M1e1
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]

#248183

FromDavid <bouncingcats@gmail.com>
Date2022-05-14 04:40 +0200
Message-ID<EmPRf-fkAU-1@gated-at.bofh.it>
In reply to#248181
On Sat, 14 May 2022 at 12:21, ghe2001 <ghe2001@pm.me> wrote:

> Supermicro workstation, Debian Buster, smartctl v 6.6
>
> I bought a new 12TB Western Digital Gold SATA disk the other day.
> After testing it, smartctl says, among other things:
>
>  22 Unknown_Attribute       0x0023   001   001   025    Pre-fail  Always   FAILING_NOW 13
>
> And it looks like the test is aborted when smartctl sees that error.
[...]
> Is there a way to to get smartctl to finish the test?  If so, how do I do that?

Hi, you could try the more recent version of smartmontools
(7.2-1~bpo10+1) that is available in the buster-backports
repository.

Version 6.6 was released 2017-November-05.
Version 7.2 was released 2020-December-30.

[toc] | [prev] | [next] | [standalone]

#248187

Fromghe2001 <ghe2001@protonmail.com>
Date2022-05-14 06:00 +0200
Message-ID<EmR6F-fle7-3@gated-at.bofh.it>
In reply to#248183
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256




‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, May 13, 2022 8:37 PM, David <bouncingcats@gmail.com> wrote:

> Hi, you could try the more recent version of smartmontools
> (7.2-1~bpo10+1) that is available in the buster-backports
> repository.
>
> Version 6.6 was released 2017-November-05.
> Version 7.2 was released 2020-December-30.

I found out about 7.n a bit after I posted to the list.  I've never gone the backports route before, but I tried it and couldn't find the v7 deb in the pkg software.  I put the backports line in sources and update apt (and aptitude) -- smartmontools was still at 6.  I removed 6 and tried again.  I removed everything bue the backports from sources and updated apt.  6 was still in my package managers' lists.

Can you tell from that what I did wrong with backports?

--
Glenn English


-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJifyemACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDKL/gf/VNiNyPOTRbBVoizBoRBW0zKak4Er8+/ntQYP0997A7PWjh0G
YyUlRmsKREsYUm5CbPKWNSB5BectL/9gkliLOzPj2DdBdIkQdx4KVycLivjn
IFV44RMLBYMWQx/urSw60b3D4+QAX1DVrMvRkeJHB0cXOkYW4vLfAh9oEcXc
Q5+Zt6XF5l0w4fH2BSwdF7a3iXb0V8pF4GtJ1LvTOejaugSN9uTBPaOcxsH4
r6g4RIMG04pHhFtt7UVuuYHEjMQgD3IrtZZAaMDHWd7LXO+vS8KsD8sG6534
UivJP+KChJnk7bgUCCBDRbqbdL/3iHzi8trKJXnDaBns4LFBS+UnkA==
=yqxv
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#248188

FromDavid <bouncingcats@gmail.com>
Date2022-05-14 06:10 +0200
Message-ID<EmRgl-flwA-1@gated-at.bofh.it>
In reply to#248187
On Sat, 14 May 2022 at 13:54, ghe2001 <ghe2001@protonmail.com> wrote:
> On Friday, May 13, 2022 8:37 PM, David <bouncingcats@gmail.com> wrote:
>
> > Hi, you could try the more recent version of smartmontools
> > (7.2-1~bpo10+1) that is available in the buster-backports
> > repository.
> >
> > Version 6.6 was released 2017-November-05.
> > Version 7.2 was released 2020-December-30.
>
> I found out about 7.n a bit after I posted to the list.  I've never gone the backports route before, but I tried it and couldn't find the v7 deb in the pkg software.  I put the backports line in sources and update apt (and aptitude) -- smartmontools was still at 6.  I removed 6 and tried again.  I removed everything bue the backports from sources and updated apt.  6 was still in my package managers' lists.
>
> Can you tell from that what I did wrong with backports?

Have a look at this page:
  https://wiki.debian.org/Backports
in particular:
  https://wiki.debian.org/Backports#Installing_backports_on_the_command_line
"The backports repository is deactivated by default." ...

See also here:
  https://backports.debian.org/Instructions/#index3h2
"All backports are deactivated by default " ...

[toc] | [prev] | [next] | [standalone]

#248216

Fromghe2001 <ghe2001@protonmail.com>
Date2022-05-14 21:20 +0200
Message-ID<En5sZ-ftPf-5@gated-at.bofh.it>
In reply to#248188
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256





------- Original Message -------
On Friday, May 13th, 2022 at 10:08 PM, David <bouncingcats@gmail.com> wrote:

> See also here:
> https://backports.debian.org/Instructions/#index3h2
> "All backports are deactivated by default " ...

Got 7.2.  Now 22 is helium level, but it still says it fails.

--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJif/9EACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDLTuQf/SZtnhtupwYxBAygXSVaIPfKRvjwye45+EijwJkiHkB3kYrWE
FjbzGyXsSt5QONKv1PB56J9joNH+w5UUFZ9gK/f1tlcbOsMcA1CeGjThGFLH
ZQAVCqDWngUbryP3EmKRKlLCN+b7ncxcFwKPct2mNw/eZeCvPyrvLrfwVoSp
Mvs0YjmlvDONSdpqiLNGbV7OcNhYz0isJ8km6kCtljMdljxo+dIloqiEIS2a
SvafJKpRxGLoXIQ66iOLBn9lpE1I1aSqSN4FbQtzZHzYXEeKG+RGiEpVmTd/
I+qEEpZ4xkqId6z/KwN9prB5LtJJTUKIq1AJ5EWF2dhl+MrjVuYn9g==
=V/f/
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#248221

FromDavid <bouncingcats@gmail.com>
Date2022-05-15 04:10 +0200
Message-ID<EnbRL-fxAj-1@gated-at.bofh.it>
In reply to#248216
On Sun, 15 May 2022 at 05:13, ghe2001 <ghe2001@protonmail.com> wrote:

> Got 7.2.  Now 22 is helium level, but it still says it fails.

Maybe it's faulty. I would ask vendor/manufacturer for advice,
who will probably advise to test it using manufacturer diagnostic
software.

[toc] | [prev] | [next] | [standalone]

#248186

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2022-05-14 05:10 +0200
Message-ID<EmQkh-fkZu-1@gated-at.bofh.it>
In reply to#248181
On 5/13/22 19:02, ghe2001 wrote:
> Supermicro workstation, Debian Buster, smartctl v 6.6
> 
> I bought a new 12TB Western Digital Gold SATA disk the other day.  After testing it, smartctl says, among other things:
> 
>   22 Unknown_Attribute       0x0023   001   001   025    Pre-fail  Always   FAILING_NOW 13
> 
> And it looks like the test is aborted when smartctl sees that error.  And there's lots of yelling all over my monitor.
> 
> I found some discussion of ID 22 on the 'Net -- it's often used to mean 'helium level' which makes some sense on a 12TB disk.  But testing the Seagate 12TB next to the Western Digital is OK -- sorta; there's no ID 22 in the output.
> 
> The Wikipedia article on S.M.A.R.T lists ID 22 as having to do with the helium.
> 
> On the web, it looked like there's a way of changing what ID 22's called so smartctl won't hurl.  I'd like the test to just keep going and tell me the other things it finds.
> 
> My questions:
> 
> Is this error on ID 22 anything to worry about?
> (I'm guessing that it isn't, and smartctl and/or something in the Western Digital disk's firmware is mildly wrong)
> 
> Is there really a way to change 22 so smartctl will report the helium level?  How do I do that?
> 
> Is there a way to to get smartctl to finish the test?  If so, how do I do that?
> 
> TIA...


I would download, install, and run the Western Digital WD Drive 
Utilities to test the drive:

     https://support.wdc.com/downloads.aspx?FW&lang=en&family=wdretailkits


If the tool finds a problem with the drive, it should provide the 
information needed to process a warranty claim with Western Digital. 
Or, if the purchase was recent enough, to get an RMA and refund from the 
seller.


David

[toc] | [prev] | [next] | [standalone]

#248354

FromDarac Marjal <mailinglist@darac.org.uk>
Date2022-05-20 13:40 +0200
Message-ID<Ep997-gJin-3@gated-at.bofh.it>
In reply to#248181

[Multipart message — attachments visible in raw view] — view raw

On 14/05/2022 03:02, ghe2001 wrote:
> Supermicro workstation, Debian Buster, smartctl v 6.6
>
> I bought a new 12TB Western Digital Gold SATA disk the other day. 
> After testing it, smartctl says, among other things:
>
>  22 Unknown_Attribute       0x0023   001   001   025    Pre-fail 
> Always   FAILING_NOW 13
>
> And it looks like the test is aborted when smartctl sees that error.  
> And there's lots of yelling all over my monitor.
>
> I found some discussion of ID 22 on the 'Net -- it's often used to 
> mean 'helium level' which makes some sense on a 12TB disk.  But 
> testing the Seagate 12TB next to the Western Digital is OK -- sorta; 
> there's no ID 22 in the output.
>
> The Wikipedia article on S.M.A.R.T lists ID 22 as having to do with 
> the helium.
>
> On the web, it looked like there's a way of changing what ID 22's 
> called so smartctl won't hurl.  I'd like the test to just keep going 
> and tell me the other things it finds.
>
> My questions:
>
> Is this error on ID 22 anything to worry about?
> (I'm guessing that it isn't, and smartctl and/or something in the 
> Western Digital disk's firmware is mildly wrong)
>
> Is there really a way to change 22 so smartctl will report the helium 
> level?  How do I do that?

Regardless of whether smartctl knows what ID 22 means, the error is 
actually because the _value_ of ID 22 is too low.

SMART entries show four values:

  * VALUE - This is a "normalised" value, between 0 and 255. The
    RAW_VALUE (shown as the last column) is scaled according to the
    manufacturer's algorithm such that 100 is the ideal value.
  * WORST - This represents the worst level of VALUE that the drive has
    seen.
  * THRESH - This is a level which the manufacturer has determined. If
    VALUE is less than THRESH, there is a problem
  * RAW_VALUE - This is some internal value which the manufacturer knows
    the meaning of (sometimes it might be obvious such as the number of
    hours online, but in the case of the helium level it's not obvious
    what 13 represents)

So, Smartctl might not know that the helium level is low, but it _does_ 
know that ID 22 is at 1, which is less than 25, so therefore the drive 
is failing.

As far as the firmware is concerned, the drive is failing. Whether that 
decision is justified, only the manufacturer can really say.

>
> Is there a way to to get smartctl to finish the test?  If so, how do I 
> do that?
>
> TIA...
>
 >

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web