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

Do other owners of WD Gold disks hear a periodic plonk ?

Started by	"Thomas Schmitt" <scdbackup@gmx.net>
First post	2020-07-24 20:50 +0200
Last post	2020-07-25 00:50 +0200
Articles	20 on this page of 23 — 8 participants

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

  Do other owners of WD Gold disks hear a periodic plonk ? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-07-24 20:50 +0200
    Re: Do other owners of WD Gold disks hear a periodic plonk ? David Christensen <dpchrist@holgerdanske.com> - 2020-07-24 21:10 +0200
      Re: Do other owners of WD Gold disks hear a periodic plonk ? Thomas Amm <debili@open-email.net> - 2020-07-25 00:50 +0200
    Re: Do other owners of WD Gold disks hear a periodic plonk ? Dan Ritter <dsr@randomstring.org> - 2020-07-24 21:10 +0200
    Re: Do other owners of WD Gold disks hear a periodic plonk ? Reco <recoverym4n@enotuniq.net> - 2020-07-24 21:20 +0200
      Re: Do other owners of WD Gold disks hear a periodic plonk ? David Christensen <dpchrist@holgerdanske.com> - 2020-07-24 21:30 +0200
        Re: Do other owners of WD Gold disks hear a periodic plonk ? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-07-24 23:40 +0200
          Re: Do other owners of WD Gold disks hear a periodic plonk ? rhkramer@gmail.com - 2020-07-25 00:30 +0200
          Re: Do other owners of WD Gold disks hear a periodic plonk ? David Christensen <dpchrist@holgerdanske.com> - 2020-07-25 04:40 +0200
          Re: Do other owners of WD Gold disks hear a periodic plonk ? Reco <recoverym4n@enotuniq.net> - 2020-07-25 10:40 +0200
            Re: Do other owners of WD Gold disks hear a periodic plonk ? Stefan Monnier <monnier@iro.umontreal.ca> - 2020-07-25 15:40 +0200
              Re: Do other owners of WD Gold disks hear a periodic plonk ? Stefan Monnier <monnier@iro.umontreal.ca> - 2020-07-25 16:30 +0200
              Re: Do other owners of WD Gold disks hear a periodic plonk ? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-07-25 16:30 +0200
                Re: Do other owners of WD Gold disks hear a periodic plonk ? Reco <recoverym4n@enotuniq.net> - 2020-07-25 17:30 +0200
                  Re: Do other owners of WD Gold disks hear a periodic plonk ? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-07-25 17:40 +0200
                Re: Do other owners of WD Gold disks hear a periodic plonk ? David Christensen <dpchrist@holgerdanske.com> - 2020-07-25 23:20 +0200
                  Update: Do other owners of WD Gold disks hear a periodic plonk ? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-08-20 13:50 +0200
                    Re: Update: Do other owners of WD Gold disks hear a periodic plonk ? Dan Ritter <dsr@randomstring.org> - 2020-08-20 14:20 +0200
                    Re: Update: Do other owners of WD Gold disks hear a periodic plonk ? David Christensen <dpchrist@holgerdanske.com> - 2020-08-20 22:10 +0200
        Re: Do other owners of WD Gold disks hear a periodic plonk ? "Thomas Schmitt" <scdbackup@gmx.net> - 2020-07-25 11:20 +0200
          Re: Do other owners of WD Gold disks hear a periodic plonk ? Reco <recoverym4n@enotuniq.net> - 2020-07-25 11:50 +0200
          Re: Do other owners of WD Gold disks hear a periodic plonk ? David Christensen <dpchrist@holgerdanske.com> - 2020-07-25 22:40 +0200
    Re: Do other owners of WD Gold disks hear a periodic plonk ? elvis <elvis@dogonfire.com> - 2020-07-25 00:50 +0200

Page 1 of 2 [1] 2 Next page →

#225211 — Do other owners of WD Gold disks hear a periodic plonk ?

From	"Thomas Schmitt" <scdbackup@gmx.net>
Date	2020-07-24 20:50 +0200
Subject	Do other owners of WD Gold disks hear a periodic plonk ?
Message-ID	<AwaVA-2k5-5@gated-at.bofh.it>

Hi,

i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
observe a strange behavior with a provisory Debian 10 LXDE installation.

If the drive has power then i makes a plonking noise every 3 to 5
seconds. The plonk is louder when Debian runs, but can also be
heard (and felt by direct finger contact with the disk) if only EFI
is running. The sound is not really loud but well hearable when the
room is silent.

I began hearing it after about two hours of operating the computer.
My hardware provider reports about two installation attempts. XFCE
excluded him from using the screen after successful installation.
(He's a SuSE/KDE user.) So he installed again with LXDE.
During those (maybe 4 hours) he did not notice this sound.

Did others here recently purchase a WD Gold disk and hear similar
periodic single knocks.
I see a matching report in
  https://community.wd.com/t/hard-drive-idle-sounds/199915
but cannot judge whether it was finally accepted as hardware damage.


Have a nice day :)

Thomas

[toc] | [next] | [standalone]

#225214

From	David Christensen <dpchrist@holgerdanske.com>
Date	2020-07-24 21:10 +0200
Message-ID	<AwbeW-2Gh-9@gated-at.bofh.it>
In reply to	#225211

On 2020-07-24 11:49, Thomas Schmitt wrote:
> Hi,
> 
> i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
> observe a strange behavior with a provisory Debian 10 LXDE installation.
> 
> If the drive has power then i makes a plonking noise every 3 to 5
> seconds. The plonk is louder when Debian runs, but can also be
> heard (and felt by direct finger contact with the disk) if only EFI
> is running. The sound is not really loud but well hearable when the
> room is silent.
> 
> I began hearing it after about two hours of operating the computer.
> My hardware provider reports about two installation attempts. XFCE
> excluded him from using the screen after successful installation.
> (He's a SuSE/KDE user.) So he installed again with LXDE.
> During those (maybe 4 hours) he did not notice this sound.
> 
> Did others here recently purchase a WD Gold disk and hear similar
> periodic single knocks.
> I see a matching report in
>    https://community.wd.com/t/hard-drive-idle-sounds/199915
> but cannot judge whether it was finally accepted as hardware damage.
> 
> 
> Have a nice day :)
> 
> Thomas

I assume your drive is 4 TB.

https://www.westerndigital.com/products/internal-drives/wd-gold-hdd

I do not own that make/model of drive.

My guess is that your drive has the "click of death":

https://en.wikipedia.org/wiki/Click_of_death

If you can return the drive, return it.

If you cannot return the drive, I would download, install, and run "Data 
Lifeguard Diagnostic for Windows":

https://support.wdc.com/downloads.aspx?DL#downloads

If the drive is within the warranty period and flunks the diagnostic, 
contact WD support, get and RMA, and replace it.

If the drive is within the warranty period and passes the diagnostic, 
contact WD support and describe the symptoms.  They might let you RMA it.

If the drive is outside the warranty period, recycle it.

David

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

#225229

From	Thomas Amm <debili@open-email.net>
Date	2020-07-25 00:50 +0200
Message-ID	<AweFP-4As-1@gated-at.bofh.it>
In reply to	#225214

On Fri, 2020-07-24 at 12:06 -0700, David Christensen wrote:
> On 2020-07-24 11:49, Thomas Schmitt wrote:
> > Hi,
> > 
> > i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0)
> > and
> > observe a strange behavior with a provisory Debian 10 LXDE
> > installation.
> > 
> > If the drive has power then i makes a plonking noise every 3 to 5
> > seconds. The plonk is louder when Debian runs, but can also be
> > heard (and felt by direct finger contact with the disk) if only EFI
> > is running. The sound is not really loud but well hearable when the
> > room is silent.
> > 
> > I began hearing it after about two hours of operating the computer.
> > My hardware provider reports about two installation attempts. XFCE
> > excluded him from using the screen after successful installation.
> > (He's a SuSE/KDE user.) So he installed again with LXDE.
> > During those (maybe 4 hours) he did not notice this sound.
> > 
> > Did others here recently purchase a WD Gold disk and hear similar
> > periodic single knocks.
> > I see a matching report in
> >    https://community.wd.com/t/hard-drive-idle-sounds/199915
> > but cannot judge whether it was finally accepted as hardware damage.
> > 
> > 
> > Have a nice day :)
> > 
> > Thomas
> 
> I assume your drive is 4 TB.
> 
> https://www.westerndigital.com/products/internal-drives/wd-gold-hdd
> 
> 
> I do not own that make/model of drive.
> 
> 
> My guess is that your drive has the "click of death":
> 
> https://en.wikipedia.org/wiki/Click_of_death
> 
> 
> If you can return the drive, return it.
> 
> 
> If you cannot return the drive, I would download, install, and run
> "Data 
> Lifeguard Diagnostic for Windows":
> 
> https://support.wdc.com/downloads.aspx?DL#downloads
> 
> 
> If the drive is within the warranty period and flunks the diagnostic, 
> contact WD support, get and RMA, and replace it.
> 
> 
> If the drive is within the warranty period and passes the diagnostic, 
> contact WD support and describe the symptoms.  They might let you RMA
> it.
> 
> 
> If the drive is outside the warranty period, recycle it.
> 
> 
> David
> 

Hardly the "original" Click Of Death as that applied to Iomega Zip
drives only. Anyway, sounds suspiciously like a poorly adjusted head
returning to zero position. I'd backup my data before trying anything
else, avoid writing new data on the drive and rely on smartctl's health
report and self tests for diagnosis.
A live USB- or DVD-image would be highly recommendable for that purpose.

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

#225215

From	Dan Ritter <dsr@randomstring.org>
Date	2020-07-24 21:10 +0200
Message-ID	<AwbeW-2Gh-13@gated-at.bofh.it>
In reply to	#225211

Thomas Schmitt wrote: 
> If the drive has power then i makes a plonking noise every 3 to 5
> seconds. The plonk is louder when Debian runs, but can also be
> heard (and felt by direct finger contact with the disk) if only EFI
> is running. The sound is not really loud but well hearable when the
> room is silent.
> 
> I began hearing it after about two hours of operating the computer.
> My hardware provider reports about two installation attempts. XFCE
> excluded him from using the screen after successful installation.
> (He's a SuSE/KDE user.) So he installed again with LXDE.
> During those (maybe 4 hours) he did not notice this sound.

Drives should not make unexpected noises. Every time I've
noticed an odd noise from a drive, it meant something bad.

Request a replacement under warranty. 

-dsr-

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

#225219

From	Reco <recoverym4n@enotuniq.net>
Date	2020-07-24 21:20 +0200
Message-ID	<AwboC-2JD-9@gated-at.bofh.it>
In reply to	#225211

	Hi.

On Fri, Jul 24, 2020 at 08:49:42PM +0200, Thomas Schmitt wrote:
> Hi,
> 
> i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
> observe a strange behavior with a provisory Debian 10 LXDE installation.
> 
> If the drive has power then i makes a plonking noise every 3 to 5
> seconds.

That amount of time looks suspiciously familiar.
Have you tried to disable drive heads parking via hdparm?
What about smartctl long test, does it show anything suspicious?

Reco

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

#225222

From	David Christensen <dpchrist@holgerdanske.com>
Date	2020-07-24 21:30 +0200
Message-ID	<Awbyi-2MR-17@gated-at.bofh.it>
In reply to	#225219

On 2020-07-24 12:14, Reco wrote:
> 	Hi.
> 
> On Fri, Jul 24, 2020 at 08:49:42PM +0200, Thomas Schmitt wrote:
>> Hi,
>>
>> i got my new computer with a 4 GB WD Gold (WDC WD4003FRYZ-01F0DB0) and
>> observe a strange behavior with a provisory Debian 10 LXDE installation.
>>
>> If the drive has power then i makes a plonking noise every 3 to 5
>> seconds.
> 
> That amount of time looks suspiciously familiar.
> Have you tried to disable drive heads parking via hdparm?
> What about smartctl long test, does it show anything suspicious?
> 
> Reco

Does the drive make the same noise when the computer is running other 
operating systems, such as Windows?


David

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

#225226

From	"Thomas Schmitt" <scdbackup@gmx.net>
Date	2020-07-24 23:40 +0200
Message-ID	<AwdA5-3XR-1@gated-at.bofh.it>
In reply to	#225222

Hi,

David Christensen wrote:
> https://en.wikipedia.org/wiki/Click_of_death

But that's a different technology (and 20 years ago).

> If you cannot return the drive, I would download, install, and run
> "Data Lifeguard Diagnostic for Windows":
> https://support.wdc.com/downloads.aspx?DL#downloads

I live in a biotope where MS-Windows is not available for tests.
(Those whom i could ask have none. Those who have, i would not want
 to instigate to even press their Enter key.)

> Does the drive make the same noise when the computer is running other
> operating systems, such as Windows?

It does it without any OS while showing me its mainboard firmware status
page with processor temperature (31 C at 25 C room temperature), fan speeds,
and the list of storage devices.

> If the drive is within the warranty period and passes the diagnostic,
> contact WD support and describe the symptoms.  They might let you RMA it.

The disk was bought as new just a week ago.
I already urged my hardware provider to talk to his hardware provider.
The main question is: bug or feature.

(The regulars might remember that i have DVD drives with auto-pull-in
 feature after 200 seconds for which nobody wants to be responsible.
 So i am open to any insight here.)

Dan Ritter wrote:
> Drives should not make unexpected noises.

It has much in common with the well known and hated periodic disk accesses
of software watching the disk's content. But i excluded all possible
watching software by umount, swapoff, shutdown. The knocking only stays away
if i pull the disk's power plug (SATA).

Reco wrote:
> Have you tried to disable drive heads parking via hdparm?

hdparm -J ?
The man page says "The factory default is eight (8) seconds".
That would be about twice as long as what i experience.

  # hdparm -J /dev/sda

  /dev/sda:
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   wdidle3      = disabled

The sense data bear KEY=0x5, ASC= 0x21, ASCQ=0x04.
Key 5 means: "Illegal request".
From MMC-5 i read for ASC=0x21 only ASCQ 0 to 3:
  5 21 00 LOGICAL BLOCK ADDRESS OUT OF RANGE
  5 21 01 INVALID ELEMENT ADDRESS
  5 21 02 INVALID ADDRESS FOR WRITE
  5 21 03 INVALID WRITE CROSSING LAYER JUMP
In SPC-3 the ASC=0x21 list ends already at ASCQ=2.
SBC-2 lists no own error codes.
Without knowing the failed command, it is quite obscure what happened.

The man page of hdparm says about -J:
  "WD supply a WDIDLE3.EXE DOS utility for tweaking  this  setting,
   and you should use that program instead of hdparm if at all pos‐
   sible."

Well, it's not possible. But "wdidle3 = disabled" does not look like
i could get any larger setting for patience. So i refrain from trying
to set the proposed value of 30 for now.

> What about smartctl long test, does it show anything suspicious?

I never used smartctl up to now.
Shall i follow these instructions ?
  https://www.thomas-krenn.com/en/wiki/SMART_tests_with_smartctl#Test_procedure_with_smartctl

Have a nice day :)

Thomas

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

#225227

From	rhkramer@gmail.com
Date	2020-07-25 00:30 +0200
Message-ID	<Awemt-4tS-1@gated-at.bofh.it>
In reply to	#225226

On Friday, July 24, 2020 05:35:34 PM Thomas Schmitt wrote:
> David Christensen wrote:
> > https://en.wikipedia.org/wiki/Click_of_death
> 
> But that's a different technology (and 20 years ago).

You might not have read the entire article.

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

#225232

From	David Christensen <dpchrist@holgerdanske.com>
Date	2020-07-25 04:40 +0200
Message-ID	<Awigq-6RE-1@gated-at.bofh.it>
In reply to	#225226

On 2020-07-24 14:35, Thomas Schmitt wrote:
> Hi,

Hello.  :-)

> David Christensen wrote:
>> https://en.wikipedia.org/wiki/Click_of_death
> 
> But that's a different technology (and 20 years ago).

I have a few Zip drives on the shelf, but only rarely used them back 
when.  My recent "Click of death" experiences have been magnetic hard 
disk drives.  I may have heard it on floppy and/or optical drives.

>> If you cannot return the drive, I would download, install, and run
>> "Data Lifeguard Diagnostic for Windows":
>> https://support.wdc.com/downloads.aspx?DL#downloads
> 
> I live in a biotope where MS-Windows is not available for tests.

I always keep at least one Windows operational instance for  such needs. 
  My last Windows 7 Pro COA came from a recycled laptop for US$ 25 on 
eBay.  Windows 10 Pro COA's currently seem to start around US$ 30.

>> Does the drive make the same noise when the computer is running other
>> operating systems, such as Windows?
> 
> It does it without any OS while showing me its mainboard firmware status
> page with processor temperature (31 C at 25 C room temperature), fan speeds,
> and the list of storage devices.

Click of death.

David

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

#225237

From	Reco <recoverym4n@enotuniq.net>
Date	2020-07-25 10:40 +0200
Message-ID	<AwnSN-1PY-1@gated-at.bofh.it>
In reply to	#225226

	Hi.

On Fri, Jul 24, 2020 at 11:35:34PM +0200, Thomas Schmitt wrote:
> Reco wrote:
> > Have you tried to disable drive heads parking via hdparm?
> 
> hdparm -J ?
> The man page says "The factory default is eight (8) seconds".
> That would be about twice as long as what i experience.
> 
>   # hdparm -J /dev/sda
> 
>   /dev/sda:
>   SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>   SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>   SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>   SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>    wdidle3      = disabled
> 
> The sense data bear KEY=0x5, ASC= 0x21, ASCQ=0x04.
> Key 5 means: "Illegal request".
> From MMC-5 i read for ASC=0x21 only ASCQ 0 to 3:
>   5 21 00 LOGICAL BLOCK ADDRESS OUT OF RANGE
>   5 21 01 INVALID ELEMENT ADDRESS
>   5 21 02 INVALID ADDRESS FOR WRITE
>   5 21 03 INVALID WRITE CROSSING LAYER JUMP
> In SPC-3 the ASC=0x21 list ends already at ASCQ=2.
> SBC-2 lists no own error codes.
> Without knowing the failed command, it is quite obscure what happened.

It is its way of saying it's an unsupported feature and you cannot
disable drive heads parking this way. Was worth the shot.


> > What about smartctl long test, does it show anything suspicious?
> 
> I never used smartctl up to now.

It's simple:

smartctl -t long /dev/sda

# wait for the amount of time it says the test will go.

smartctl -a /dev/sda

Reco

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

#225245

From	Stefan Monnier <monnier@iro.umontreal.ca>
Date	2020-07-25 15:40 +0200
Message-ID	<Awsz8-4DA-3@gated-at.bofh.it>
In reply to	#225237

> It is its way of saying it's an unsupported feature and you cannot
> disable drive heads parking this way. Was worth the shot.

I guess it's still spin-down: WD drives support it but just ignore the
APM settings of "how long to wait before spin-down" and use their own
algorithm instead.


        Stefan

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

#225247

From	Stefan Monnier <monnier@iro.umontreal.ca>
Date	2020-07-25 16:30 +0200
Message-ID	<Awtlv-58H-3@gated-at.bofh.it>
In reply to	#225245

> Stefan Monnier wrote:
>> I guess it's still spin-down
                ^^^^^
                like

Sorry, my fingers didn't obey my brain,


        Stefan

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

#225248

From	"Thomas Schmitt" <scdbackup@gmx.net>
Date	2020-07-25 16:30 +0200
Message-ID	<Awtlv-58H-5@gated-at.bofh.it>
In reply to	#225245

Hi,

Reco wrote:
> It's all other lines that are interesting here.
> I.e. 'Vendor Specific SMART Attributes with Thresholds' section.

I wanted to wait with the long list until the self-test is done.
See below for the full output of smartctl -a.


Stefan Monnier wrote:
> I guess it's still spin-down

But it happens when the drive is writing and reading a "shred" file of
100 GB. It also happens when the firmware is the only software that is
up and running.


------------------------------------------------------------------------

#  smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-9-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD4003FRYZ-01F0DB0
Serial Number:    VBGD2GPF
LU WWN Device Id: 5 000cca 095c57dbd
Firmware Version: 01.01H01
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jul 25 16:05:24 2020 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x80) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (   87) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 454) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   158   158   024    Pre-fail  Always       -       370 (Average 392)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       18
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       19
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       18
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       19
193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       19
194 Temperature_Celsius     0x0002   181   181   000    Old_age   Always       -       33 (Min/Max 24/36)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%        18         -
# 2  Short offline       Completed without error       00%        11         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

------------------------------------------------------------------------

Have a nice day :)

Thomas

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

#225251

From	Reco <recoverym4n@enotuniq.net>
Date	2020-07-25 17:30 +0200
Message-ID	<Awuhz-5Hp-9@gated-at.bofh.it>
In reply to	#225248

On Sat, Jul 25, 2020 at 04:25:16PM +0200, Thomas Schmitt wrote:
>   4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       18
>   9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       19
>  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       18
> 192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       19
> 193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       19

The most interesting part of that output is here.
Once per hour on average drive performs head parking, which cannot
explain what you're seeing.

For the comparison, this is what I consider "normal" (head parking
completely disabled):

  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always -       57
  9 Power_On_Hours          0x0032   050   050   000    Old_age   Always -       20037
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always -       57
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always -       35
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always -       3130

Reco

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

#225252

From	"Thomas Schmitt" <scdbackup@gmx.net>
Date	2020-07-25 17:40 +0200
Message-ID	<Awurf-5Kr-5@gated-at.bofh.it>
In reply to	#225251

Hi,

i quoted smartctl:
> >   4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always -       18
> >   9 Power_On_Hours          0x0012   100   100   000    Old_age   Always -       19
> >  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always -       18
> > 192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always -       19
> > 193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always -       19

Reco wrote:
> The most interesting part of that output is here.
> Once per hour on average drive performs head parking,

The power cycles were intentional. The machine was rebooted several times
yesterday for various reasons.

(I wonder why yours reports 57 with Power_Cycle_Count but only 35 with
 Power-Off_Retract_Count.)

> which cannot explain what you're seeing.

Yeah. We'd need something that happened at least during the last 12 hours
of operation at least 900 times per hour.

I still did not find my loudspeakers to listen to the wikipedia audio
file whether it indeed plays a sedately periodic and somewhat thud-like
sound.

Have a nice day :)

Thomas

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

#225272

From	David Christensen <dpchrist@holgerdanske.com>
Date	2020-07-25 23:20 +0200
Message-ID	<AwzKh-zd-1@gated-at.bofh.it>
In reply to	#225248

On 2020-07-25 07:25, Thomas Schmitt wrote:

> See below for the full output of smartctl -a.

I saved one drive that had the click of death (and died shortly 
thereafter).  My notes indicated it passed the manufacturer diagnostic 
tests, but failed the manufacturer full erase procedure.  The last SMART 
report follows.


Unfortunately, my drive was Seagate and yours is Western Digital, so 
comparing SMART reports can be an apples-vs-oranges comparison.


I typically look at the "SMART Attributes Data Structure".  The 
"Seek_Error_Rate" and "Hardware_ECC_Recovered" parameters would seem to 
attract attention, but grep'ing for those fields across the SMART 
reports for all of my drives indicates nothing special.


Similarly, "SMART Extended Comprehensive Error Log".  Both of our 
reports say "No Errors Logged".


I suspect the "click of death" is orthogonal to manufacturer diagnostics 
and SMART reports.  Human ears seem to be the only diagnostic tool for 
this failure mode.  A recording could be informative in general, and 
submitted as proof for an RMA in specific cases.


David

--


June 5, 2019

+ smartctl -x /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-9-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST31500341AS
Serial Number:    xxxREDACTEDxxx
LU WWN Device Id: 5 000c50 00e361a80
Firmware Version: CC3H
User Capacity:    1,500,301,910,016 bytes [1.50 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Wed Jun  5 09:56:53 2019 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Disabled
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unknown

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine 
completed
					without error or no self-test has ever
					been run.
Total time to complete Offline
data collection: 		(  617) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 296) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
   1 Raw_Read_Error_Rate     POSR--   102   099   006    -    4636361
   3 Spin_Up_Time            PO----   100   090   000    -    0
   4 Start_Stop_Count        -O--CK   100   100   020    -    704
   5 Reallocated_Sector_Ct   PO--CK   100   100   036    -    6
   7 Seek_Error_Rate         POSR--   075   060   030    -    31372716
   9 Power_On_Hours          -O--CK   096   096   000    -    4058
  10 Spin_Retry_Count        PO--C-   100   100   097    -    3
  12 Power_Cycle_Count       -O--CK   100   037   020    -    386
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   100   100   000    -    0
188 Command_Timeout         -O--CK   100   100   000    -    0
189 High_Fly_Writes         -O-RCK   017   017   000    -    83
190 Airflow_Temperature_Cel -O---K   072   041   045    Past 28 (0 12 28 
26 0)
194 Temperature_Celsius     -O---K   028   059   000    -    28 (0 13 0 0 0)
195 Hardware_ECC_Recovered  -O-RC-   038   024   000    -    4636361
197 Current_Pending_Sector  -O--C-   100   100   000    -    0
198 Offline_Uncorrectable   ----C-   100   100   000    -    0
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    1
240 Head_Flying_Hours       ------   100   253   000    -    4013 (231 65 0)
241 Total_LBAs_Written      ------   100   253   000    -    220443025
242 Total_LBAs_Read         ------   100   253   000    -    3743498574
			    ||||||_ K auto-keep
			    |||||__ C event count
			    ||||___ R error rate
			    |||____ S speed/performance
			    ||_____ O updated online
			    |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01       GPL,SL  R/O      1  Summary SMART error log
0x02       GPL,SL  R/O      5  Comprehensive SMART error log
0x03       GPL,SL  R/O      5  Ext. Comprehensive SMART error log
0x06       GPL,SL  R/O      1  SMART self-test log
0x07       GPL,SL  R/O      1  Extended self-test log
0x09       GPL,SL  R/W      1  Selective self-test log
0x10       GPL,SL  R/O      1  SATA NCQ Queued Error log
0x11       GPL,SL  R/O      1  SATA Phy Event Counters log
0x21       GPL,SL  R/O      1  Write stream error log
0x22       GPL,SL  R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1       GPL,SL  VS      20  Device vendor specific log
0xa2       GPL     VS    2248  Device vendor specific log
0xa8       GPL,SL  VS     129  Device vendor specific log
0xa9       GPL,SL  VS       1  Device vendor specific log
0xb0       GPL     VS    2928  Device vendor specific log
0xbe-0xbf  GPL     VS   65535  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining 
LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      4048 
     -
# 2  Short offline       Completed without error       00%      3947 
     -
# 3  Short offline       Completed without error       00%      3658 
     -
# 4  Short offline       Completed without error       00%      3653 
     -
# 5  Short offline       Aborted by host               90%      3646 
     -
# 6  Short offline       Aborted by host               90%      3639 
     -
# 7  Short offline       Aborted by host               90%      3637 
     -
# 8  Short offline       Aborted by host               90%      3637 
     -
# 9  Short offline       Aborted by host               90%      3623 
     -
#10  Short offline       Aborted by host               90%      3621 
     -
#11  Short offline       Aborted by host               90%      3620 
     -
#12  Short offline       Aborted by host               90%      3619 
     -
#13  Short offline       Aborted by host               90%      3618 
     -
#14  Short offline       Aborted by host               90%      3614 
     -
#15  Short offline       Aborted by host               90%      3614 
     -
#16  Short offline       Aborted by host               90%      3611 
     -
#17  Short offline       Aborted by host               90%      3589 
     -
#18  Short offline       Aborted by host               90%      3589 
     -
#19  Short offline       Aborted by host               90%      3583 
     -

SMART Selective self-test log data structure revision number 1
  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
     1        0        0  Not_testing
     2        0        0  Not_testing
     3        0        0  Not_testing
     4        0        0  Not_testing
     5        0        0  Not_testing
Selective self-test flags (0x0):
   After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       522 (0x020a)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    28 Celsius
Power Cycle Min/Max Temperature:     26/28 Celsius
Lifetime    Min/Max Temperature:     13/59 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:     14/55 Celsius
Min/Max Temperature Limit:           10/60 Celsius
Temperature History Size (Index):    128 (6)

Index    Estimated Time   Temperature Celsius
    7    2019-06-05 07:49    52  *********************************
  ...    ..(  3 skipped).    ..  *********************************
   11    2019-06-05 07:53    52  *********************************
   12    2019-06-05 07:54    53  **********************************
   13    2019-06-05 07:55    53  **********************************
   14    2019-06-05 07:56    58  ***************************************
  ...    ..(  5 skipped).    ..  ***************************************
   20    2019-06-05 08:02    58  ***************************************
   21    2019-06-05 08:03    59  ****************************************
   22    2019-06-05 08:04    59  ****************************************
   23    2019-06-05 08:05    59  ****************************************
   24    2019-06-05 08:06    58  ***************************************
   25    2019-06-05 08:07    58  ***************************************
   26    2019-06-05 08:08     ?  -
   27    2019-06-05 08:09    57  **************************************
   28    2019-06-05 08:10    56  *************************************
   29    2019-06-05 08:11    56  *************************************
   30    2019-06-05 08:12    56  *************************************
   31    2019-06-05 08:13    55  ************************************
   32    2019-06-05 08:14     ?  -
   33    2019-06-05 08:15    22  ***
   34    2019-06-05 08:16    23  ****
   35    2019-06-05 08:17    24  *****
   36    2019-06-05 08:18    25  ******
   37    2019-06-05 08:19    26  *******
   38    2019-06-05 08:20    26  *******
   39    2019-06-05 08:21    27  ********
   40    2019-06-05 08:22    28  *********
   41    2019-06-05 08:23    29  **********
   42    2019-06-05 08:24    29  **********
   43    2019-06-05 08:25    30  ***********
   44    2019-06-05 08:26    31  ************
   45    2019-06-05 08:27    31  ************
   46    2019-06-05 08:28    32  *************
   47    2019-06-05 08:29    32  *************
   48    2019-06-05 08:30    33  **************
   49    2019-06-05 08:31    33  **************
   50    2019-06-05 08:32    34  ***************
   51    2019-06-05 08:33    34  ***************
   52    2019-06-05 08:34    35  ****************
   53    2019-06-05 08:35    35  ****************
   54    2019-06-05 08:36    36  *****************
   55    2019-06-05 08:37    36  *****************
   56    2019-06-05 08:38    37  ******************
   57    2019-06-05 08:39    37  ******************
   58    2019-06-05 08:40    38  *******************
   59    2019-06-05 08:41    38  *******************
   60    2019-06-05 08:42    38  *******************
   61    2019-06-05 08:43    39  ********************
   62    2019-06-05 08:44    39  ********************
   63    2019-06-05 08:45    39  ********************
   64    2019-06-05 08:46    40  *********************
  ...    ..(  2 skipped).    ..  *********************
   67    2019-06-05 08:49    40  *********************
   68    2019-06-05 08:50    41  **********************
  ...    ..(  3 skipped).    ..  **********************
   72    2019-06-05 08:54    41  **********************
   73    2019-06-05 08:55    42  ***********************
  ...    ..(  3 skipped).    ..  ***********************
   77    2019-06-05 08:59    42  ***********************
   78    2019-06-05 09:00    43  ************************
  ...    ..(  2 skipped).    ..  ************************
   81    2019-06-05 09:03    43  ************************
   82    2019-06-05 09:04    44  *************************
   83    2019-06-05 09:05    44  *************************
   84    2019-06-05 09:06    44  *************************
   85    2019-06-05 09:07     ?  -
   86    2019-06-05 09:08    30  ***********
   87    2019-06-05 09:09    30  ***********
   88    2019-06-05 09:10     ?  -
   89    2019-06-05 09:11    30  ***********
   90    2019-06-05 09:12    31  ************
   91    2019-06-05 09:13    31  ************
   92    2019-06-05 09:14    32  *************
   93    2019-06-05 09:15    33  **************
   94    2019-06-05 09:16    33  **************
   95    2019-06-05 09:17    34  ***************
   96    2019-06-05 09:18    35  ****************
   97    2019-06-05 09:19    35  ****************
   98    2019-06-05 09:20    36  *****************
   99    2019-06-05 09:21    36  *****************
  100    2019-06-05 09:22    37  ******************
  101    2019-06-05 09:23    37  ******************
  102    2019-06-05 09:24    38  *******************
  103    2019-06-05 09:25    38  *******************
  104    2019-06-05 09:26    39  ********************
  105    2019-06-05 09:27    39  ********************
  106    2019-06-05 09:28    39  ********************
  107    2019-06-05 09:29    40  *********************
  108    2019-06-05 09:30    40  *********************
  109    2019-06-05 09:31    40  *********************
  110    2019-06-05 09:32    41  **********************
  111    2019-06-05 09:33    41  **********************
  112    2019-06-05 09:34    41  **********************
  113    2019-06-05 09:35    42  ***********************
  ...    ..(  3 skipped).    ..  ***********************
  117    2019-06-05 09:39    42  ***********************
  118    2019-06-05 09:40    43  ************************
  ...    ..(  2 skipped).    ..  ************************
  121    2019-06-05 09:43    43  ************************
  122    2019-06-05 09:44    44  *************************
  ...    ..(  7 skipped).    ..  *************************
    2    2019-06-05 09:52    44  *************************
    3    2019-06-05 09:53     ?  -
    4    2019-06-05 09:54    26  *******
    5    2019-06-05 09:55    27  ********
    6    2019-06-05 09:56    28  *********

SCT Error Recovery Control:
	   Read: Disabled
	  Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x000a  2            2  Device-to-host register FISes sent due to a COMRESET
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS

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

#226325 — Update: Do other owners of WD Gold disks hear a periodic plonk ?

From	"Thomas Schmitt" <scdbackup@gmx.net>
Date	2020-08-20 13:50 +0200
Subject	Update: Do other owners of WD Gold disks hear a periodic plonk ?
Message-ID	<AFReV-7sO-5@gated-at.bofh.it>
In reply to	#225272

Hi,

a while ago i asked about the periodic knocking noise after each 4 seconds
of my freshly bought 4 TB HDD WD4003FRYZ. We came to the conclusion that
this was a reason to return the disk to the seller. "Click of Death" et.al.

I did and got a replacement disk. That one knocks less loudly, more like
every 6 seconds, sometimes double-knocking, sometimes skipping a 6 seconds
cycle.
After more discussion with involved people, the term "Preventive Wear
Leveling" came up. This feature seems to be old, but to now have been
intensified with the excuse that nobody hears it knocking in a server room.

Some quite unhappy Western Digital users can be seen at
  https://community.wd.com/t/periodic-noise-from-head-movement-wd-black-4tb/183096/2

One of those posts finally has a link to a company statement:
  https://support-en.wd.com/app/answers/detail/a_id/16309
  "Normal drive sounds include:
   ...
   Occasional drive clicks occurring at 4 or 5 second intervals, and the
   drive is functioning normally and passes diagnostics"

Now the discussion of my HDD tends towards giving it back for the reason
of neither warning of this feature and of the feature's effects being not
the same from individual drive to individual drive.

-----------------------------------------------------------------------

So my next question to recent HDD buyers:

What 4 TB HDD should i want for best reliability and no noises when idle ?
Any recent experiences ?


Have a nice day :)

Thomas

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

#226327 — Re: Update: Do other owners of WD Gold disks hear a periodic plonk ?

From	Dan Ritter <dsr@randomstring.org>
Date	2020-08-20 14:20 +0200
Subject	Re: Update: Do other owners of WD Gold disks hear a periodic plonk ?
Message-ID	<AFRHX-7RG-3@gated-at.bofh.it>
In reply to	#226325

Thomas Schmitt wrote: 
> -----------------------------------------------------------------------
> 
> So my next question to recent HDD buyers:
> 
> What 4 TB HDD should i want for best reliability and no noises when idle ?
> Any recent experiences ?

Toshiba and Hitachi (owned by WD but not produced in the same
plants) are doing quite well these days.

-dsr-

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

#226336 — Re: Update: Do other owners of WD Gold disks hear a periodic plonk ?

From	David Christensen <dpchrist@holgerdanske.com>
Date	2020-08-20 22:10 +0200
Subject	Re: Update: Do other owners of WD Gold disks hear a periodic plonk ?
Message-ID	<AFZ2O-3R4-7@gated-at.bofh.it>
In reply to	#226325

On 2020-08-20 04:39, Thomas Schmitt wrote:
> Hi,
> 
> a while ago i asked about the periodic knocking noise after each 4 seconds
> of my freshly bought 4 TB HDD WD4003FRYZ. We came to the conclusion that
> this was a reason to return the disk to the seller. "Click of Death" et.al.
> 
> I did and got a replacement disk. That one knocks less loudly, more like
> every 6 seconds, sometimes double-knocking, sometimes skipping a 6 seconds
> cycle.
> After more discussion with involved people, the term "Preventive Wear
> Leveling" came up. This feature seems to be old, but to now have been
> intensified with the excuse that nobody hears it knocking in a server room.
> 
> Some quite unhappy Western Digital users can be seen at
>    https://community.wd.com/t/periodic-noise-from-head-movement-wd-black-4tb/183096/2
> 
> One of those posts finally has a link to a company statement:
>    https://support-en.wd.com/app/answers/detail/a_id/16309
>    "Normal drive sounds include:
>     ...
>     Occasional drive clicks occurring at 4 or 5 second intervals, and the
>     drive is functioning normally and passes diagnostics"
> 
> Now the discussion of my HDD tends towards giving it back for the reason
> of neither warning of this feature and of the feature's effects being not
> the same from individual drive to individual drive.
> 
> -----------------------------------------------------------------------
> 
> So my next question to recent HDD buyers:
> 
> What 4 TB HDD should i want for best reliability and no noises when idle ?
> Any recent experiences ?
> 
> 
> Have a nice day :)
> 
> Thomas

Thanks for posting the update.  All the other drives I have diagnosed 
with "The Click of Death" were otherwise silent for years before the 
noise started.  I will keep the "Preventive Wear Leveling" feature in 
mind if and when I run into drives with similar symptoms.

I have been buying "revious-generation "Seagate Constellation ES2 3TB 
7200RPM SATA 6Gb/s 64MB 3.5" Enterprise Hard Drive", model number 
ST33000650NS, on eBay sold as "new".  The drives came in sealed 
electrostatic bags and the SMART reports indicated 0 hours of use.  The 
heads move only when disk activity is expected.  I believe the largest 
model in that series was 4 TB, and interface choices included SATA and 
SAS.  I am very happy with these drives.

Of 8 purchased over the past few years, one died after ~11 months -- 
SMART reports over-temperature, transfers are slow/
failing, and it smelled of burnt electronics.  Fortunately, I was 
careful to buy from a reputable seller who provided a 1 year warranty. 
They provided an RMA, return shipping label, and full refund.

David

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

#225238

From	"Thomas Schmitt" <scdbackup@gmx.net>
Date	2020-07-25 11:20 +0200
Message-ID	<Awovv-2iF-1@gated-at.bofh.it>
In reply to	#225222

Hi,

rhkramer@gmail.com wrote:
> You might not have read the entire [Click_of_death] article.

Indeed. Now i need to search my old loudspeakers in order to compare
the sound file on Wikipedia with the disk's sound.

D. R. Evans wrote:
> I can say that my experience (YMMV) is that 100% of the drives
> that exhibit this phenomenon have failed sometime not long after the
> phenomenon began

I will try to get it exchanged. Hopefully the hearable activity without
any operating system running is reason enough. Will see next week.

Thomas Amm wrote:
> I'd backup my data before trying anything else

There are no valuable data on it yet. I used "shred" to write two files
of 100 GB each. Knocking continues while the drive writes 180 MB/s and
while it reads at 240 MB/s. The knock is a bit louder than the normal
working sounds of moving heads.
(I should build up a tree of many files with scattered content to hear
 it being truely busy. For now it makes no other unusual noises.)

David Christensen wrote:
> Click of death.

At least this is the reality which i will present to the disk vendor
while negotiating about replacement.

But personally i still have doubts that it is this particular problem.
The knocking is not "Click-click-click" as described in the web, but
rather "Pok" ... 3 or 4 seconds ... "Pok" ...

Reco wrote:
> It's simple:
> smartctl -t long /dev/sda

The short test yielded
  Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
  # 1  Short offline       Completed without error       00%        11         -

The long test is expected to end in 5.5 hours. Progress report is fewly
entertaining because moving in steps of 10 percent:

  # smartctl -a /dev/sda | fgrep -A 1 'Self-test execution status' ; date
  Self-test execution status:      ( 246) Self-test routine in progress...
                                          60% of test remaining.
  Sat 25 Jul 2020 10:57:53 AM CEST

The disk is doing its klonkwork reliably. But today the rythm seems to
tend more towards 1 beat per 4 seconds. Yesterday it was more like 1/3 bps.

Have a nice day :)

Thomas

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

Page 1 of 2 [1] 2 Next page →

csiph-web

Do other owners of WD Gold disks hear a periodic plonk ?

Contents

#225211 — Do other owners of WD Gold disks hear a periodic plonk ?

#225214

#225229

#225215

#225219

#225222

#225226

#225227

#225232

#225237

#225245

#225247

#225248

#225251

#225252

#225272

#226325 — Update: Do other owners of WD Gold disks hear a periodic plonk ?

#226327 — Re: Update: Do other owners of WD Gold disks hear a periodic plonk ?

#226336 — Re: Update: Do other owners of WD Gold disks hear a periodic plonk ?

#225238