On Fri, 2019-03-01 at 11:46 +0000, Tim Waugh wrote:
> On Fri, 1 Mar 2019 at 00:42, Jonathan Ryshpan <[email protected]>
> wrote:
> > The drive also produces an occasional beeping sound: pitch about
> > 340 cps (my best guess using a tuner), lasting about 250 msec.  The
> > beeps happen when the drive is in use, particularly when it's busy,
> > and never when the drive is starting up.
> 
> Have you looked at the SMART data for these drives? It might be worth
> paying particular attention to the "Reallocation Event Count" and
> "Reallocated Sectors Count". If the first is larger than the second
> (i.e. there were failed reallocation attempts), it could explain the
> filesystem corruption.

I don't think smart data is available for this drive, but I'd like to
be proved wrong.  Advice is welcome:
# smartctl -a -d scsi /dev/sdb
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.20.11-200.fc29.x86_64]
(local build)

Copyright (C) 2002-17, Bruce Allen, Christian Franke, 
www.smartmontools.org



=== START OF INFORMATION SECTION ===

Vendor:               Seagate

Product:              Ultra Slim GD

Revision:             0108

Compliance:           SPC-4

User Capacity:        2,000,398,933,504 bytes [2.00 TB]

Logical block size:   512 bytes

LU is fully provisioned

Logical Unit id:      0x3e4137565731325a

Serial number:        NA7VW12Z

Device type:          disk

Local Time is:        Fri Mar  1 12:18:40 2019 PST

SMART support is:     Unavailable - device lacks SMART capability.



=== START OF READ SMART DATA SECTION ===

Current Drive Temperature:     0 C

Drive Trip Temperature:        0 C



Error Counter logging not supported



No self-tests have been logged




_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to