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

Sata Hard drive testing

Started by	Thomas Anderson <thomas.anderson@little-beak.com>
First post	2021-10-18 18:40 +0200
Last post	2021-10-18 21:30 +0200
Articles	20 on this page of 22 — 12 participants

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

  Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-18 18:40 +0200
    Re: Sata Hard drive testing Felix Miata <mrmazda@earthlink.net> - 2021-10-18 18:50 +0200
    Re: Sata Hard drive testing Reco <recoverym4n@enotuniq.net> - 2021-10-18 19:10 +0200
      Re: Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-18 19:30 +0200
      Re: Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-21 01:50 +0200
        Re: Sata Hard drive testing Gene Heskett <gheskett@shentel.net> - 2021-10-21 02:40 +0200
        Re: Sata Hard drive testing piorunz <piorunz@gmx.com> - 2021-10-21 03:20 +0200
          Re: Sata Hard drive testing Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-21 10:40 +0200
        Re: Sata Hard drive testing David Christensen <dpchrist@holgerdanske.com> - 2021-10-21 04:40 +0200
          Re: Sata Hard drive testing piorunz <piorunz@gmx.com> - 2021-10-21 16:30 +0200
        Re: Sata Hard drive testing Reco <recoverym4n@enotuniq.net> - 2021-10-21 07:50 +0200
        Re: Sata Hard drive testing Dan Ritter <dsr@randomstring.org> - 2021-10-21 14:40 +0200
          Re: Sata Hard drive testing Gene Heskett <gheskett@shentel.net> - 2021-10-21 15:00 +0200
            Re: Sata Hard drive testing David <bouncingcats@gmail.com> - 2021-10-21 15:10 +0200
              Re: Sata Hard drive testing Gene Heskett <gheskett@shentel.net> - 2021-10-21 16:30 +0200
              Re: Sata Hard drive testing Kenneth Parker <sea7kenp@gmail.com> - 2021-10-21 18:10 +0200
                Re: Sata Hard drive testing Thomas Anderson <thomas.anderson@little-beak.com> - 2021-10-24 17:00 +0200
            Re: Sata Hard drive testing Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-21 15:10 +0200
              Re: Sata Hard drive testing Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-21 15:20 +0200
    Re: Sata Hard drive testing basti <mailinglist@unix-solution.de> - 2021-10-18 19:50 +0200
    Re: Sata Hard drive testing David Christensen <dpchrist@holgerdanske.com> - 2021-10-18 20:40 +0200
    Re: Sata Hard drive testing Stefan Monnier <monnier@iro.umontreal.ca> - 2021-10-18 21:30 +0200

Page 1 of 2 [1] 2 Next page →

#241463 — Sata Hard drive testing

From	Thomas Anderson <thomas.anderson@little-beak.com>
Date	2021-10-18 18:40 +0200
Subject	Sata Hard drive testing
Message-ID	<D9DQ5-4X6-5@gated-at.bofh.it>

Hello Gurus,

I have been having problems with a drive (non-SSD) for a while now, but 
I would like to "identify" the problem specifically, so that I may 
perhaps be able to get the drive replaced.

Essentially, I have been experienced data loss, where nodes become 
unreadable, when I try to "fix it" with fdisk, it says it moves 
unreadable to the trash, basically deleting data.

I have tried reformatting the drive, writing zeros to it, and then 
temporarily the drive looks fine; but it's not! it's as if the drive is 
some how decaying: where it looks good, but then when you go to use it, 
the data later becomes unreadable.

Is there any kind of test I can execute on this drive to show it needs 
to be replaced??

Thanks!

[toc] | [next] | [standalone]

#241465

From	Felix Miata <mrmazda@earthlink.net>
Date	2021-10-18 18:50 +0200
Message-ID	<D9DZM-50C-9@gated-at.bofh.it>
In reply to	#241463

Thomas Anderson composed on 2021-10-18 18:25 (UTC+0200):

> I have been having problems with a drive (non-SSD) for a while now, but 
> I would like to "identify" the problem specifically, so that I may 
> perhaps be able to get the drive replaced.

> Essentially, I have been experienced data loss, where nodes become 
> unreadable, when I try to "fix it" with fdisk, it says it moves 
> unreadable to the trash, basically deleting data.

> I have tried reformatting the drive, writing zeros to it, and then 
> temporarily the drive looks fine; but it's not! it's as if the drive is 
> some how decaying: where it looks good, but then when you go to use it, 
> the data later becomes unreadable.

> Is there any kind of test I can execute on this drive to show it needs 
> to be replaced?? 																			
	man smartctl
-- 
Evolution as taught in public schools is, like religion,
	based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

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

#241466

From	Reco <recoverym4n@enotuniq.net>
Date	2021-10-18 19:10 +0200
Message-ID	<D9Ej8-5mk-9@gated-at.bofh.it>
In reply to	#241463

	Hi.

On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
> I have been having problems with a drive (non-SSD) for a while now,
> but I would like to "identify" the problem specifically, so that I may
> perhaps be able to get the drive replaced.

Assuming it's SATA/IDE drive, all you need to do is:

apt install smartmontools
smartctl -t long <ur_drive_here>
# wait for the test to finish
smartctl -a <ur_drive_here>

Please post the output of the last command.

Reco

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

#241468

From	Thomas Anderson <thomas.anderson@little-beak.com>
Date	2021-10-18 19:30 +0200
Message-ID	<D9ECt-5sK-1@gated-at.bofh.it>
In reply to	#241466

Cool, thanks Reco!

Will post again tomorrow =) Takes 987 minutes apparently.

On 10/18/21 6:52 PM, Reco wrote:
> 	Hi.
>
> On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
>> I have been having problems with a drive (non-SSD) for a while now,
>> but I would like to "identify" the problem specifically, so that I may
>> perhaps be able to get the drive replaced.
> Assuming it's SATA/IDE drive, all you need to do is:
>
> apt install smartmontools
> smartctl -t long <ur_drive_here>
> # wait for the test to finish
> smartctl -a <ur_drive_here>
>
> Please post the output of the last command.
>
> Reco
>

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

#241535

From	Thomas Anderson <thomas.anderson@little-beak.com>
Date	2021-10-21 01:50 +0200
Message-ID	<Datvk-2Va-1@gated-at.bofh.it>
In reply to	#241466

Here are the results, of my smartctl test:

I am trying to parse them myself, to see if I can learn anything. But,
immediate glance

and queries did not reveal anything that could help me determine if the
drive is good or not.

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

=== START OF INFORMATION SECTION ===
Device Model:     ST8000DM004-2CX188
Serial Number:    ZCT1706V
LU WWN Device Id: 5 000c50 0c2b1cd83
Firmware Version: 0001
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5425 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Oct 20 14:36:49 2021 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:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
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:         (    0) seconds.
Offline data collection
capabilities:              (0x73) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    No 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:      ( 987) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x30a5)    SCT Status supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE UPDATED 
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   064   051   006    Pre-fail
Always       -       7226480
  3 Spin_Up_Time            0x0003   093   091   000    Pre-fail
Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age
Always       -       361
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail
Always       -       0
  7 Seek_Error_Rate         0x000f   080   060   045    Pre-fail
Always       -       104115990
  9 Power_On_Hours          0x0032   084   084   000    Old_age
Always       -       14558 (99 41 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age
Always       -       77
183 Runtime_Bad_Block       0x0032   095   095   000    Old_age
Always       -       5
184 End-to-End_Error        0x0032   100   100   099    Old_age
Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age
Always       -       1334
188 Command_Timeout         0x0032   100   100   000    Old_age
Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age
Always       -       0
190 Airflow_Temperature_Cel 0x0022   070   052   040    Old_age
Always       -       30 (Min/Max 28/33)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age
Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age
Always       -       25
193 Load_Cycle_Count        0x0032   099   099   000    Old_age
Always       -       3362
194 Temperature_Celsius     0x0022   030   048   000    Old_age
Always       -       30 (0 16 0 0 0)
195 Hardware_ECC_Recovered  0x001a   069   064   000    Old_age
Always       -       7226480
197 Current_Pending_Sector  0x0012   100   100   000    Old_age
Always       -       8
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age
Offline      -       8
199 UDMA_CRC_Error_Count    0x003e   200   198   000    Old_age
Always       -       15
240 Head_Flying_Hours       0x0000   100   253   000    Old_age
Offline      -       2368 (67 0 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age
Offline      -       54984038154
242 Total_LBAs_Read         0x0000   100   253   000    Old_age
Offline      -       185155335586

SMART Error Log Version: 1
ATA Error Count: 1334 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1334 occurred at disk power-on lifetime: 10525 hours (438 days +
13 hours)
  When the command that caused the error occurred, the device was active
or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00  15d+00:06:46.256  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00  15d+00:06:46.247  SET FEATURES [Enable SATA
feature]
  27 00 00 00 00 00 e0 00  15d+00:06:46.220  READ NATIVE MAX ADDRESS EXT
[OBS-ACS-3]
  ec 00 00 00 00 00 a0 00  15d+00:06:46.217  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  15d+00:06:46.205  SET FEATURES [Set transfer
mode]

Error 1333 occurred at disk power-on lifetime: 10525 hours (438 days +
13 hours)
  When the command that caused the error occurred, the device was active
or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00  15d+00:06:46.090  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00  15d+00:06:46.081  SET FEATURES [Enable SATA
feature]
  27 00 00 00 00 00 e0 00  15d+00:06:46.054  READ NATIVE MAX ADDRESS EXT
[OBS-ACS-3]
  ec 00 00 00 00 00 a0 00  15d+00:06:46.051  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  15d+00:06:46.039  SET FEATURES [Set transfer
mode]

Error 1332 occurred at disk power-on lifetime: 10525 hours (438 days +
13 hours)
  When the command that caused the error occurred, the device was active
or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00  15d+00:06:45.922  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00  15d+00:06:45.912  SET FEATURES [Enable SATA
feature]
  27 00 00 00 00 00 e0 00  15d+00:06:45.886  READ NATIVE MAX ADDRESS EXT
[OBS-ACS-3]
  ec 00 00 00 00 00 a0 00  15d+00:06:45.883  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  15d+00:06:45.871  SET FEATURES [Set transfer
mode]

Error 1331 occurred at disk power-on lifetime: 10525 hours (438 days +
13 hours)
  When the command that caused the error occurred, the device was active
or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00  15d+00:06:45.692  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00  15d+00:06:45.683  SET FEATURES [Enable SATA
feature]
  27 00 00 00 00 00 e0 00  15d+00:06:45.656  READ NATIVE MAX ADDRESS EXT
[OBS-ACS-3]
  ec 00 00 00 00 00 a0 00  15d+00:06:45.654  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  15d+00:06:45.641  SET FEATURES [Set transfer
mode]

Error 1330 occurred at disk power-on lifetime: 10525 hours (438 days +
13 hours)
  When the command that caused the error occurred, the device was active
or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 08 ff ff ff 4f 00  15d+00:06:45.526  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00  15d+00:06:45.517  SET FEATURES [Enable SATA
feature]
  27 00 00 00 00 00 e0 00  15d+00:06:45.491  READ NATIVE MAX ADDRESS EXT
[OBS-ACS-3]
  ec 00 00 00 00 00 a0 00  15d+00:06:45.488  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00  15d+00:06:45.475  SET FEATURES [Set transfer
mode]

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% 14551         -
# 2  Extended offline    Completed without error       00% 14530         -
# 3  Conveyance offline  Completed without error       00% 10165         -
# 4  Conveyance offline  Completed without error       00% 10165         -
# 5  Short offline       Completed without error       00% 10163         -
# 6  Extended offline    Completed without error       00% 9997         -
# 7  Short offline       Completed without error       00% 0         -

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.

On 10/18/21 6:52 PM, Reco wrote:
> 	Hi.
>
> On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
>> I have been having problems with a drive (non-SSD) for a while now,
>> but I would like to "identify" the problem specifically, so that I may
>> perhaps be able to get the drive replaced.
> Assuming it's SATA/IDE drive, all you need to do is:
>
> apt install smartmontools
> smartctl -t long <ur_drive_here>
> # wait for the test to finish
> smartctl -a <ur_drive_here>
>
> Please post the output of the last command.
>
> Reco
>

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

#241536

From	Gene Heskett <gheskett@shentel.net>
Date	2021-10-21 02:40 +0200
Message-ID	<DauhH-3qm-5@gated-at.bofh.it>
In reply to	#241535

On Wednesday 20 October 2021 19:45:52 Thomas Anderson wrote:

> Here are the results, of my smartctl test:
>
This would be much easier to decode if you turned off wordwrap, and 
repasted from that terminal screen.

> I am trying to parse them myself, to see if I can learn anything. But,
> immediate glance
>
> and queries did not reveal anything that could help me determine if
> the drive is good or not.
>
>
> smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-18-amd64] (local
> build) Copyright (C) 2002-17, Bruce Allen, Christian Franke,
> www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Device Model:     ST8000DM004-2CX188
> Serial Number:    ZCT1706V
> LU WWN Device Id: 5 000c50 0c2b1cd83
> Firmware Version: 0001
> User Capacity:    8,001,563,222,016 bytes [8.00 TB]
> Sector Sizes:     512 bytes logical, 4096 bytes physical
> Rotation Rate:    5425 rpm
> Form Factor:      3.5 inches
> Device is:        Not in smartctl database [for details use: -P
> showall] ATA Version is:   ACS-3 T13/2161-D revision 5
> SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
> Local Time is:    Wed Oct 20 14:36:49 2021 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:  (0x00)    Offline data collection
> activity was never started.
>                     Auto Offline Data Collection: Disabled.
> 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:         (    0) seconds.
> Offline data collection
> capabilities:              (0x73) SMART execute Offline immediate.
>                     Auto Offline data collection on/off support.
>                     Suspend Offline collection upon new
>                     command.
>                     No 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:      ( 987) minutes.
> Conveyance self-test routine
> recommended polling time:      (   2) minutes.
> SCT capabilities:            (0x30a5)    SCT Status supported.
>                     SCT Data Table supported.
>
> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE UPDATED 
> WHEN_FAILED RAW_VALUE
>   1 Raw_Read_Error_Rate     0x000f   064   051   006    Pre-fail
> Always       -       7226480
>   3 Spin_Up_Time            0x0003   093   091   000    Pre-fail
> Always       -       0
>   4 Start_Stop_Count        0x0032   100   100   020    Old_age
> Always       -       361
>   5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail
> Always       -       0
none is good
>   7 Seek_Error_Rate         0x000f   080   060   045    Pre-fail
> Always       -       104115990
>   9 Power_On_Hours          0x0032   084   084   000    Old_age
> Always       -       14558 (99 41 0)
relatively young
>  10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail
> Always       -       0
>  12 Power_Cycle_Count       0x0032   100   100   020    Old_age
> Always       -       77
this is the single most dangerous time for a spinning rust drive

> 183 Runtime_Bad_Block       0x0032   095   095   000    Old_age
> Always       -       5
> 184 End-to-End_Error        0x0032   100   100   099    Old_age
> Always       -       0
> 187 Reported_Uncorrect      0x0032   001   001   000    Old_age
> Always       -       1334
> 188 Command_Timeout         0x0032   100   100   000    Old_age
> Always       -       0
> 189 High_Fly_Writes         0x003a   100   100   000    Old_age
> Always       -       0
> 190 Airflow_Temperature_Cel 0x0022   070   052   040    Old_age
> Always       -       30 (Min/Max 28/33)
operating temps good
> 191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age
> Always       -       0
> 192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age
> Always       -       25
should normally match power cycle?
> 193 Load_Cycle_Count        0x0032   099   099   000    Old_age
> Always       -       3362
> 194 Temperature_Celsius     0x0022   030   048   000    Old_age
> Always       -       30 (0 16 0 0 0)
> 195 Hardware_ECC_Recovered  0x001a   069   064   000    Old_age
> Always       -       7226480
> 197 Current_Pending_Sector  0x0012   100   100   000    Old_age
> Always       -       8
> 198 Offline_Uncorrectable   0x0010   100   100   000    Old_age
> Offline      -       8
> 199 UDMA_CRC_Error_Count    0x003e   200   198   000    Old_age
> Always       -       15
> 240 Head_Flying_Hours       0x0000   100   253   000    Old_age
> Offline      -       2368 (67 0 0)
> 241 Total_LBAs_Written      0x0000   100   253   000    Old_age
> Offline      -       54984038154
> 242 Total_LBAs_Read         0x0000   100   253   000    Old_age
> Offline      -       185155335586
>
> SMART Error Log Version: 1
> ATA Error Count: 1334 (device log contains only the most recent five
> errors) CR = Command Register [HEX]
>     FR = Features Register [HEX]
>     SC = Sector Count Register [HEX]
>     SN = Sector Number Register [HEX]
>     CL = Cylinder Low Register [HEX]
>     CH = Cylinder High Register [HEX]
>     DH = Device/Head Register [HEX]
>     DC = Device Command Register [HEX]
>     ER = Error register [HEX]
>     ST = Status register [HEX]
> Powered_Up_Time is measured from power on, and printed as
> DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> SS=sec, and sss=millisec. It "wraps" after 49.710 days.
>
> Error 1334 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>   When the command that caused the error occurred, the device was
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   60 00 08 ff ff ff 4f 00  15d+00:06:46.256  READ FPDMA QUEUED
>   ef 10 02 00 00 00 a0 00  15d+00:06:46.247  SET FEATURES [Enable SATA
> feature]
>   27 00 00 00 00 00 e0 00  15d+00:06:46.220  READ NATIVE MAX ADDRESS
> EXT [OBS-ACS-3]
>   ec 00 00 00 00 00 a0 00  15d+00:06:46.217  IDENTIFY DEVICE
>   ef 03 46 00 00 00 a0 00  15d+00:06:46.205  SET FEATURES [Set
> transfer mode]
>
> Error 1333 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>   When the command that caused the error occurred, the device was
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   60 00 08 ff ff ff 4f 00  15d+00:06:46.090  READ FPDMA QUEUED
>   ef 10 02 00 00 00 a0 00  15d+00:06:46.081  SET FEATURES [Enable SATA
> feature]
>   27 00 00 00 00 00 e0 00  15d+00:06:46.054  READ NATIVE MAX ADDRESS
> EXT [OBS-ACS-3]
>   ec 00 00 00 00 00 a0 00  15d+00:06:46.051  IDENTIFY DEVICE
>   ef 03 46 00 00 00 a0 00  15d+00:06:46.039  SET FEATURES [Set
> transfer mode]
>
> Error 1332 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>   When the command that caused the error occurred, the device was
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   60 00 08 ff ff ff 4f 00  15d+00:06:45.922  READ FPDMA QUEUED
>   ef 10 02 00 00 00 a0 00  15d+00:06:45.912  SET FEATURES [Enable SATA
> feature]
>   27 00 00 00 00 00 e0 00  15d+00:06:45.886  READ NATIVE MAX ADDRESS
> EXT [OBS-ACS-3]
>   ec 00 00 00 00 00 a0 00  15d+00:06:45.883  IDENTIFY DEVICE
>   ef 03 46 00 00 00 a0 00  15d+00:06:45.871  SET FEATURES [Set
> transfer mode]
>
> Error 1331 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>   When the command that caused the error occurred, the device was
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   60 00 08 ff ff ff 4f 00  15d+00:06:45.692  READ FPDMA QUEUED
>   ef 10 02 00 00 00 a0 00  15d+00:06:45.683  SET FEATURES [Enable SATA
> feature]
>   27 00 00 00 00 00 e0 00  15d+00:06:45.656  READ NATIVE MAX ADDRESS
> EXT [OBS-ACS-3]
>   ec 00 00 00 00 00 a0 00  15d+00:06:45.654  IDENTIFY DEVICE
>   ef 03 46 00 00 00 a0 00  15d+00:06:45.641  SET FEATURES [Set
> transfer mode]
>
> Error 1330 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>   When the command that caused the error occurred, the device was
> active or idle.
>
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
>
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   60 00 08 ff ff ff 4f 00  15d+00:06:45.526  READ FPDMA QUEUED
>   ef 10 02 00 00 00 a0 00  15d+00:06:45.517  SET FEATURES [Enable SATA
> feature]
>   27 00 00 00 00 00 e0 00  15d+00:06:45.491  READ NATIVE MAX ADDRESS
> EXT [OBS-ACS-3]
>   ec 00 00 00 00 00 a0 00  15d+00:06:45.488  IDENTIFY DEVICE
>   ef 03 46 00 00 00 a0 00  15d+00:06:45.475  SET FEATURES [Set
> transfer mode]
>
> 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%
> 14551         - # 2  Extended offline    Completed without error      
> 00% 14530         - # 3  Conveyance offline  Completed without
> error       00% 10165         - # 4  Conveyance offline  Completed
> without error       00% 10165         - # 5  Short offline      
> Completed without error       00% 10163         - # 6  Extended
> offline    Completed without error       00% 9997         - # 7  Short
> offline       Completed without error       00% 0         -
>
> 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.

What color is the sata data cable? if "hot red" aka magenta, bump it with 
a pencil and note if the syslog log blows up with reset errors. If it 
does, replace the data cable with any other color but that hot red. That 
particular plastic dye leads to cable failures and has been a known part 
of the electronics jungle since the 1970's.

>
> On 10/18/21 6:52 PM, Reco wrote:
> > 	Hi.
> >
> > On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
> >> I have been having problems with a drive (non-SSD) for a while now,
> >> but I would like to "identify" the problem specifically, so that I
> >> may perhaps be able to get the drive replaced.
> >
> > Assuming it's SATA/IDE drive, all you need to do is:
> >
> > apt install smartmontools
> > smartctl -t long <ur_drive_here>
> > # wait for the test to finish
> > smartctl -a <ur_drive_here>
> >
> > Please post the output of the last command.
> >
> > Reco


Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

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

#241537

From	piorunz <piorunz@gmx.com>
Date	2021-10-21 03:20 +0200
Message-ID	<DauUq-3RI-1@gated-at.bofh.it>
In reply to	#241535

On 21/10/2021 00:45, Thomas Anderson wrote:
> Here are the results, of my smartctl test:

Five metrics from smartctl require attention:

     Device Model		ST8000DM004-2CX188
9   Power_On_Hours		14558

183 Runtime_Bad_Block		5
187 Reported_Uncorrect		1334
195 Hardware_ECC_Recovered	7226480
197 Current_Pending_Sector	8
198 Offline_Uncorrectable	8

I have similar Seagate drives (4), and they look like this:

     Device Model		ST2000DM006-2DM164
9   Power_On_Hours		20124,20125,23527,23511

183 Runtime_Bad_Block		2,3,1,1 yours 5
187 Reported_Uncorrect		0,0,0,0 yours 1334
195 Hardware_ECC_Recovered my HDDs don't have that field, yours 7226480
197 Current_Pending_Sector	0,0,0,0 yours 5
198 Offline_Uncorrectable	0,0,0,0 yours 5

Clearly you have problem with surface errors. 1334 reported bad sectors,
5 current pending sectors and so on. However, last full surface read
test SMART "long" test you performed at 14551 hrs (7 hours before
fetching this SMART data) has passed, meaning drive is still able to
read all sectors. That means it still has spares and/or it doesn't have
any more unknown bad sectors.

Another good news is, that SMART log has logged last error in 10525
power-on hours. You are on 14558 hrs. That's 4033 hrs or 168 days ago if
you run it 24/7. That means, drive is not discovering new bad sectors,
either because you don't read or write to certain surface spots where
undiscovered bad sectors are, or simply because remainder of the drive
is in good condition.

If your drive is still on warranty, you should return it, most likely it
will be accepted based solely on smartctl results. If not, you can do
following:

Change data cable first thing, as also Gene suggested

Watch these five metrics very closely:
183 Runtime_Bad_Block		5
187 Reported_Uncorrect		1334
195 Hardware_ECC_Recovered	7226480
197 Current_Pending_Sector	8
198 Offline_Uncorrectable	8

If any of these raise rapidly over time (maybe except ECC errors, which
are usually kinda normal nowadays), you may consider retiring it.

Also do smart "long" test every 1 month or so. Check SMART results after
each test.

Lastly, you should use it in RAID1 or similar mode, to ensure there is
always backup of data this drive keeps. You can try Btrfs raid1 or mdadm
raid1. Whatever you choose, try not to use this drive without any
backup, as you are not sure yet if damage are not progressing.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

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

#241545

From	Andrei POPESCU <andreimpopescu@gmail.com>
Date	2021-10-21 10:40 +0200
Message-ID	<DaBMd-86t-1@gated-at.bofh.it>
In reply to	#241537

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

On Jo, 21 oct 21, 02:12:25, piorunz wrote:
> 
> Lastly, you should use it in RAID1 or similar mode, to ensure there is
> always backup of data this drive keeps.

RAID is meant only for uptime, backup is something else, see: 
http://taobackup.com/.

> You can try Btrfs raid1 or mdadm raid1.

Mostly agreed with btrfs[1] (though ZFS is probably better, if you are 
fine with out-of-tree kernel modules[2]).

On the other hand mdadm can't detect silent corruption. In case a flaky 
drive (like the one discussed here) returns corrupted data claiming it 
is good mdadm RAID can't detect this, and in case it detects it, it has 
no way to determine which data is good.

Worst case it might even overwrite the good data with the bad one 
(because the bad data appears to be newer).

> Whatever you choose, try not to use this drive without any
> backup, as you are not sure yet if damage are not progressing.

Yep.

[1] https://arstechnica.com/gadgets/2021/09/examining-btrfs-linuxs-perpetually-half-finished-filesystem/
[2] DKMS makes this mostly painless

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#241539

From	David Christensen <dpchrist@holgerdanske.com>
Date	2021-10-21 04:40 +0200
Message-ID	<Daw9P-4CA-1@gated-at.bofh.it>
In reply to	#241535

 > On 10/18/21 6:52 PM, Reco wrote:
 >> 	Hi.
 >>
 >> On Mon, Oct 18, 2021 at 06:25:19PM +0200, Thomas Anderson wrote:
 >>> I have been having problems with a drive (non-SSD) for a while now,
 >>> but I would like to "identify" the problem specifically, so that I may
 >>> perhaps be able to get the drive replaced.
 >> Assuming it's SATA/IDE drive, all you need to do is:
 >>
 >> apt install smartmontools
 >> smartctl -t long <ur_drive_here>
 >> # wait for the test to finish
 >> smartctl -a <ur_drive_here>
 >>
 >> Please post the output of the last command.
 >>
 >> Reco


On 10/20/21 4:45 PM, Thomas Anderson wrote:
> Here are the results, of my smartctl test:


Please use inline posting style, not top posting.


> I am trying to parse them myself, to see if I can learn anything. But,
> immediate glance
> 
> and queries did not reveal anything that could help me determine if the
> drive is good or not.
> 
> 
> smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-18-amd64] (local build)
> Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
> 
> === START OF INFORMATION SECTION ===
> Device Model:     ST8000DM004-2CX188


So, an 8 TB desktop drive.


Here is the datasheet:

https://www.seagate.com/www-content/datasheets/pdfs/3-5-barracudaDS1900-11-1806US-en_US.pdf


Here is the SMART attributes specification:

http://t1.daumcdn.net/brunch/service/user/axm/file/zRYOdwPu3OMoKYmBOby1fEEQEbU.pdf


> Serial Number:    ZCT1706V
> LU WWN Device Id: 5 000c50 0c2b1cd83
> Firmware Version: 0001
> User Capacity:    8,001,563,222,016 bytes [8.00 TB]
> Sector Sizes:     512 bytes logical, 4096 bytes physical
> Rotation Rate:    5425 rpm
> Form Factor:      3.5 inches
> Device is:        Not in smartctl database [for details use: -P showall]
> ATA Version is:   ACS-3 T13/2161-D revision 5
> SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
> Local Time is:    Wed Oct 20 14:36:49 2021 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


"PASSED" is a good thing.


> General SMART Values:
> Offline data collection status:  (0x00)    Offline data collection activity
>                      was never started.
>                      Auto Offline Data Collection: Disabled.
> Self-test execution status:      (   0)    The previous self-test
> routine completed
>                      without error or no self-test has ever
>                      been run.


No self-test errors ia a good thing.


> Total time to complete Offline
> data collection:         (    0) seconds.
> Offline data collection
> capabilities:              (0x73) SMART execute Offline immediate.
>                      Auto Offline data collection on/off support.
>                      Suspend Offline collection upon new
>                      command.
>                      No 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:      ( 987) minutes.
> Conveyance self-test routine
> recommended polling time:      (   2) minutes.
> SCT capabilities:            (0x30a5)    SCT Status supported.
>                      SCT Data Table supported.
> 
> SMART Attributes Data Structure revision number: 10


Decoding SMART attributes can be a challenge.  In addition to the 
Seagate spec above, see:

https://wiki.unraid.net/Understanding_SMART_Reports#SMART_attributes_section


> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE UPDATED
> WHEN_FAILED RAW_VALUE
>    1 Raw_Read_Error_Rate     0x000f   064   051   006    Pre-fail
> Always       -       7226480
>    3 Spin_Up_Time            0x0003   093   091   000    Pre-fail
> Always       -       0
>    4 Start_Stop_Count        0x0032   100   100   020    Old_age
> Always       -       361
>    5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail
> Always       -       0
>    7 Seek_Error_Rate         0x000f   080   060   045    Pre-fail
> Always       -       104115990
>    9 Power_On_Hours          0x0032   084   084   000    Old_age
> Always       -       14558 (99 41 0)


AIUI your drive had been powered up for a total of 14,558 hours over its 
lifetime when the report was generated.


Spec is 2,400 hours per year (8,760 hours).


>   10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail
> Always       -       0
>   12 Power_Cycle_Count       0x0032   100   100   020    Old_age
> Always       -       77
> 183 Runtime_Bad_Block       0x0032   095   095   000    Old_age
> Always       -       5


AIUI your drive has experienced 5 bad blocks.  I do not see any 
indication of data loss.  So, I would not worry.


> 184 End-to-End_Error        0x0032   100   100   099    Old_age
> Always       -       0
> 187 Reported_Uncorrect      0x0032   001   001   000    Old_age
> Always       -       1334


AIUI the drive has reported 1,334 uncorrectable errors to the host over 
its lifetime.  The VALUE of 001 is the worst possible rating (bad news). 
  But, it looks like they were ATA bus errors; not internal errors (good 
news).  See below.


> 188 Command_Timeout         0x0032   100   100   000    Old_age
> Always       -       0
> 189 High_Fly_Writes         0x003a   100   100   000    Old_age
> Always       -       0
> 190 Airflow_Temperature_Cel 0x0022   070   052   040    Old_age
> Always       -       30 (Min/Max 28/33)
> 191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age
> Always       -       0
> 192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age
> Always       -       25
> 193 Load_Cycle_Count        0x0032   099   099   000    Old_age
> Always       -       3362


Spec is 600,000 cycles.  You are well below that.


> 194 Temperature_Celsius     0x0022   030   048   000    Old_age
> Always       -       30 (0 16 0 0 0)
> 195 Hardware_ECC_Recovered  0x001a   069   064   000    Old_age
> Always       -       7226480


AIUI the value of 69 is getting close to the failure threshold of 64.


> 197 Current_Pending_Sector  0x0012   100   100   000    Old_age
> Always       -       8
> 198 Offline_Uncorrectable   0x0010   100   100   000    Old_age
> Offline      -       8
> 199 UDMA_CRC_Error_Count    0x003e   200   198   000    Old_age
> Always       -       15
> 240 Head_Flying_Hours       0x0000   100   253   000    Old_age
> Offline      -       2368 (67 0 0)
> 241 Total_LBAs_Written      0x0000   100   253   000    Old_age
> Offline      -       54984038154


AIUI 54,984,038,154 * 512 bytes = ~27 TB have been written to the drive.


> 242 Total_LBAs_Read         0x0000   100   253   000    Old_age
> Offline      -       185155335586


AIUI 185,155,335,586 * 512 bytes = ~92 TB have been read from the drive.


The drive is rated for 55 TB/year.


> SMART Error Log Version: 1
> ATA Error Count: 1334 (device log contains only the most recent five errors)


Note that the value "1334" matches the 187 Reported_Uncorrect attribute, 
above.  AIUI this means 1,334 data transfers over the ATA bus failed, 
indicating a bad drive interface, a bad drive-cable connection, a bad 
cable, a bad cable-adapter connection, and/or a bad adapter.


>      CR = Command Register [HEX]
>      FR = Features Register [HEX]
>      SC = Sector Count Register [HEX]
>      SN = Sector Number Register [HEX]
>      CL = Cylinder Low Register [HEX]
>      CH = Cylinder High Register [HEX]
>      DH = Device/Head Register [HEX]
>      DC = Device Command Register [HEX]
>      ER = Error register [HEX]
>      ST = Status register [HEX]
> Powered_Up_Time is measured from power on, and printed as
> DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> SS=sec, and sss=millisec. It "wraps" after 49.710 days.
> 
> Error 1334 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>    When the command that caused the error occurred, the device was active
> or idle.
> 
>    After command completion occurred, registers were:
>    ER ST SC SN CL CH DH
>    -- -- -- -- -- -- --
>    40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
> 
>    Commands leading to the command that caused the error were:
>    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>    -- -- -- -- -- -- -- --  ----------------  --------------------
>    60 00 08 ff ff ff 4f 00  15d+00:06:46.256  READ FPDMA QUEUED
>    ef 10 02 00 00 00 a0 00  15d+00:06:46.247  SET FEATURES [Enable SATA
> feature]
>    27 00 00 00 00 00 e0 00  15d+00:06:46.220  READ NATIVE MAX ADDRESS EXT
> [OBS-ACS-3]
>    ec 00 00 00 00 00 a0 00  15d+00:06:46.217  IDENTIFY DEVICE
>    ef 03 46 00 00 00 a0 00  15d+00:06:46.205  SET FEATURES [Set transfer
> mode]
> 
> Error 1333 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>    When the command that caused the error occurred, the device was active
> or idle.
> 
>    After command completion occurred, registers were:
>    ER ST SC SN CL CH DH
>    -- -- -- -- -- -- --
>    40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
> 
>    Commands leading to the command that caused the error were:
>    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>    -- -- -- -- -- -- -- --  ----------------  --------------------
>    60 00 08 ff ff ff 4f 00  15d+00:06:46.090  READ FPDMA QUEUED
>    ef 10 02 00 00 00 a0 00  15d+00:06:46.081  SET FEATURES [Enable SATA
> feature]
>    27 00 00 00 00 00 e0 00  15d+00:06:46.054  READ NATIVE MAX ADDRESS EXT
> [OBS-ACS-3]
>    ec 00 00 00 00 00 a0 00  15d+00:06:46.051  IDENTIFY DEVICE
>    ef 03 46 00 00 00 a0 00  15d+00:06:46.039  SET FEATURES [Set transfer
> mode]
> 
> Error 1332 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>    When the command that caused the error occurred, the device was active
> or idle.
> 
>    After command completion occurred, registers were:
>    ER ST SC SN CL CH DH
>    -- -- -- -- -- -- --
>    40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
> 
>    Commands leading to the command that caused the error were:
>    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>    -- -- -- -- -- -- -- --  ----------------  --------------------
>    60 00 08 ff ff ff 4f 00  15d+00:06:45.922  READ FPDMA QUEUED
>    ef 10 02 00 00 00 a0 00  15d+00:06:45.912  SET FEATURES [Enable SATA
> feature]
>    27 00 00 00 00 00 e0 00  15d+00:06:45.886  READ NATIVE MAX ADDRESS EXT
> [OBS-ACS-3]
>    ec 00 00 00 00 00 a0 00  15d+00:06:45.883  IDENTIFY DEVICE
>    ef 03 46 00 00 00 a0 00  15d+00:06:45.871  SET FEATURES [Set transfer
> mode]
> 
> Error 1331 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>    When the command that caused the error occurred, the device was active
> or idle.
> 
>    After command completion occurred, registers were:
>    ER ST SC SN CL CH DH
>    -- -- -- -- -- -- --
>    40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
> 
>    Commands leading to the command that caused the error were:
>    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>    -- -- -- -- -- -- -- --  ----------------  --------------------
>    60 00 08 ff ff ff 4f 00  15d+00:06:45.692  READ FPDMA QUEUED
>    ef 10 02 00 00 00 a0 00  15d+00:06:45.683  SET FEATURES [Enable SATA
> feature]
>    27 00 00 00 00 00 e0 00  15d+00:06:45.656  READ NATIVE MAX ADDRESS EXT
> [OBS-ACS-3]
>    ec 00 00 00 00 00 a0 00  15d+00:06:45.654  IDENTIFY DEVICE
>    ef 03 46 00 00 00 a0 00  15d+00:06:45.641  SET FEATURES [Set transfer
> mode]
> 
> Error 1330 occurred at disk power-on lifetime: 10525 hours (438 days +
> 13 hours)
>    When the command that caused the error occurred, the device was active
> or idle.
> 
>    After command completion occurred, registers were:
>    ER ST SC SN CL CH DH
>    -- -- -- -- -- -- --
>    40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
> 
>    Commands leading to the command that caused the error were:
>    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>    -- -- -- -- -- -- -- --  ----------------  --------------------
>    60 00 08 ff ff ff 4f 00  15d+00:06:45.526  READ FPDMA QUEUED
>    ef 10 02 00 00 00 a0 00  15d+00:06:45.517  SET FEATURES [Enable SATA
> feature]
>    27 00 00 00 00 00 e0 00  15d+00:06:45.491  READ NATIVE MAX ADDRESS EXT
> [OBS-ACS-3]
>    ec 00 00 00 00 00 a0 00  15d+00:06:45.488  IDENTIFY DEVICE
>    ef 03 46 00 00 00 a0 00  15d+00:06:45.475  SET FEATURES [Set transfer
> mode]


AIUI it looks like you had a rash of data transfer errors at a lifetime 
hours of 10,525.  As the drive now has over 14,558 hours, whatever the 
problem was, it went away.  Perhaps this was when you moved the drive 
between computers and/or re-patched the cables?


> 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% 14551         -
> # 2  Extended offline    Completed without error       00% 14530         -
> # 3  Conveyance offline  Completed without error       00% 10165         -
> # 4  Conveyance offline  Completed without error       00% 10165         -
> # 5  Short offline       Completed without error       00% 10163         -
> # 6  Extended offline    Completed without error       00% 9997         -
> # 7  Short offline       Completed without error       00% 0         -
> 
> 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 you tested your cables, adapters, and/or other drives?


The red SATA cable issue is real.  I migrated my data from desktop 
hardware with a single data drive to server hardware with RAID a few 
years ago, and had a rash of storage issues.  Once replaced all of my 
SATA cables with new, black, 6 Gbps cables with locking connectors, was 
able to troubleshoot everything else.  Since then, storage has been stable:

https://www.amazon.com/dp/B018Y2LF5O/ref=twister_B07D556K66?_encoding=UTF8&psc=1

https://www.amazon.com/dp/B018Y2LDGK/ref=twister_B07D581GYH?_encoding=UTF8&psc=1


David

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

#241560

From	piorunz <piorunz@gmx.com>
Date	2021-10-21 16:30 +0200
Message-ID	<DaHeW-34n-15@gated-at.bofh.it>
In reply to	#241539

On 21/10/2021 03:34, David Christensen wrote:

Very detailed analysis, better than mine! Much appreciated.

-- 
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

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

#241543

From	Reco <recoverym4n@enotuniq.net>
Date	2021-10-21 07:50 +0200
Message-ID	<Daz7H-6pe-1@gated-at.bofh.it>
In reply to	#241535

	Hi.

On Thu, Oct 21, 2021 at 01:45:52AM +0200, Thomas Anderson wrote:
> I am trying to parse them myself, to see if I can learn anything. But,
> immediate glance and queries did not reveal anything that could help
> me determine if the drive is good or not.

It's not. You have a Seagate, after all, and those are good only as long
as trash can is considered :)


But anyway, it's not new.

>   9 Power_On_Hours          0x0032   084   084   000    Old_age  Always       -       14558 (99 41 0)

It has bad sectors, a small amount compared to the drive size.

> 183 Runtime_Bad_Block       0x0032   095   095   000    Old_age  Always       -       5
> 187 Reported_Uncorrect      0x0032   001   001   000    Old_age  Always       -       1334
> 197 Current_Pending_Sector  0x0012   100   100   000    Old_age  Always       -       8
> 198 Offline_Uncorrectable   0x0010   100   100   000    Old_age  Offline      -       8


And you had some problems with the drive in the past, which could be a
bad SATA cable, but could be the drive itself:

> Error 1334 occurred at disk power-on lifetime: 10525 hours (438 days + 13 hours)
>   When the command that caused the error occurred, the device was active or idle.
> 
>   After command completion occurred, registers were:
>   ER ST SC SN CL CH DH
>   -- -- -- -- -- -- --
>   40 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
> 
>   Commands leading to the command that caused the error were:
>   CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
>   -- -- -- -- -- -- -- --  ----------------  --------------------
>   60 00 08 ff ff ff 4f 00  15d+00:06:46.256  READ FPDMA QUEUED
>   ef 10 02 00 00 00 a0 00  15d+00:06:46.247  SET FEATURES [Enable SATA feature]
>   27 00 00 00 00 00 e0 00  15d+00:06:46.220  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
>   ec 00 00 00 00 00 a0 00  15d+00:06:46.217  IDENTIFY DEVICE
>   ef 03 46 00 00 00 a0 00  15d+00:06:46.205  SET FEATURES [Set transfer mode]


Assuming you make backups, I'd call this drive servicable. I'd replace
it sooner or later, because it has bad sectors, but it won't be the
first priority.

Reco

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

#241552

From	Dan Ritter <dsr@randomstring.org>
Date	2021-10-21 14:40 +0200
Message-ID	<DaFwu-1Sm-5@gated-at.bofh.it>
In reply to	#241535

Thomas Anderson wrote: 
> Here are the results, of my smartctl test:
> 
> I am trying to parse them myself, to see if I can learn anything. But,
> immediate glance
> 
> and queries did not reveal anything that could help me determine if the
> drive is good or not.
> 
> 
> smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-18-amd64] (local build)
> Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
> 
> === START OF INFORMATION SECTION ===
> Device Model:     ST8000DM004-2CX188


You should be able to return this drive without proving that it
is defective; this is one of Seagates' SMR drives that they did
not disclose were SMR.

-dsr-

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

#241553

From	Gene Heskett <gheskett@shentel.net>
Date	2021-10-21 15:00 +0200
Message-ID	<DaFPQ-1Zq-1@gated-at.bofh.it>
In reply to	#241552

On Thursday 21 October 2021 08:13:26 Dan Ritter wrote:

> > === START OF INFORMATION SECTION ===
> > Device Model:     ST8000DM004-2CX188
>
> You should be able to return this drive without proving that it
> is defective; this is one of Seagates' SMR drives that they did
> not disclose were SMR.
>
> -dsr-

And what does this SMR acronym mean, Dan?

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

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

#241555

From	David <bouncingcats@gmail.com>
Date	2021-10-21 15:10 +0200
Message-ID	<DaFZv-2j7-3@gated-at.bofh.it>
In reply to	#241553

On Thu, 21 Oct 2021 at 23:53, Gene Heskett <gheskett@shentel.net> wrote:

> And what does this SMR acronym mean, Dan?

Questions like this can be answered with an
internet search engine. Search for "Seagate SMR".
For fun you can add search terms like
"controversy guilty dreaded bad press" etc.

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

#241561

From	Gene Heskett <gheskett@shentel.net>
Date	2021-10-21 16:30 +0200
Message-ID	<DaHeW-34n-17@gated-at.bofh.it>
In reply to	#241555

On Thursday 21 October 2021 09:02:01 David wrote:

> On Thu, 21 Oct 2021 at 23:53, Gene Heskett <gheskett@shentel.net> 
wrote:
> > And what does this SMR acronym mean, Dan?
>
> Questions like this can be answered with an
> internet search engine. Search for "Seagate SMR".
> For fun you can add search terms like
> "controversy guilty dreaded bad press" etc.

Very Interesting and most informative Dan, and thank you.

Carefully reading between the lines of several hits also explains why I 
stopped having major failures of amanda, the backup software, when I 
replaced a 1Tbyte seagate with a 240 gig series 860 samsung SSD, used as 
a holding disk while amanda is collecting its data to be written to tape 
w/o shoeshining the tape while at the same time cutting the time to do a 
20 gig backup from 3 or 4 hours, to 20 minutes.

This post is also being sent to the amanda-users list to alert the users 
who are currently being affected by this and not finding a definitive 
answer.

Bottom line for amanda users is, do not use todays spinniing rust drives 
as holding disks. They are simply not trustworthy for short term buffer 
storage.

Symptoms are reported to the user as crc errors in the holding disk. That 
particular DiskList Entry is then repeated until a good crc is obtained. 
But that also leaves the bad crc data left on the holding disk 
eventually using up its capacity without manual intervention to clean up 
the mess. A genuine PITA for us, and leaves the drive makers in an 
unfavorable, bad dog, no biscuit light.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

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

#241563

From	Kenneth Parker <sea7kenp@gmail.com>
Date	2021-10-21 18:10 +0200
Message-ID	<DaINI-4cC-5@gated-at.bofh.it>
In reply to	#241555

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

On Thu, Oct 21, 2021, 9:02 AM David <bouncingcats@gmail.com> wrote:

> On Thu, 21 Oct 2021 at 23:53, Gene Heskett <gheskett@shentel.net> wrote:
>
> > And what does this SMR acronym mean, Dan?
>
> Questions like this can be answered with an
> internet search engine. Search for "Seagate SMR".
> For fun you can add search terms like
> "controversy guilty dreaded bad press" etc
>

What?  Seagate Magnetic Recording caught Shingles?  (Sorry!)

Kenneth Parker

>

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

#241633

From	Thomas Anderson <thomas.anderson@little-beak.com>
Date	2021-10-24 17:00 +0200
Message-ID	<DbN8B-2Dm-1@gated-at.bofh.it>
In reply to	#241563

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

Thank you everyone that helped me with this issue.

I learned a great deal.

Namely, for my particular use case, SMR drives are sub-optimal.

It is VERY difficult to even find out if drives are SMR or CMR, because

apparently the manufacturers try to put it all out the door. As mentioned

by Mr. Ritter, the information of writing technology is not disclosed 
easily,

and in some cases, bordering on deceptive.

I will replace this drive since I have little faith in it, as it was 
originally purposed,

important backup. I will just use it as a redundant backup or just a 
short term/temporary

storage drive - and monitor it.

On 10/21/21 6:08 PM, Kenneth Parker wrote:
>
>
> On Thu, Oct 21, 2021, 9:02 AM David <bouncingcats@gmail.com 
> <mailto:bouncingcats@gmail.com>> wrote:
>
>     On Thu, 21 Oct 2021 at 23:53, Gene Heskett <gheskett@shentel.net
>     <mailto:gheskett@shentel.net>> wrote:
>
>     > And what does this SMR acronym mean, Dan?
>
>     Questions like this can be answered with an
>     internet search engine. Search for "Seagate SMR".
>     For fun you can add search terms like
>     "controversy guilty dreaded bad press" etc
>
>
> What?  Seagate Magnetic Recording caught Shingles?  (Sorry!)
>
> Kenneth Parker

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

#241556

From	Andrei POPESCU <andreimpopescu@gmail.com>
Date	2021-10-21 15:10 +0200
Message-ID	<DaFZw-2j7-13@gated-at.bofh.it>
In reply to	#241553

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

On Jo, 21 oct 21, 08:53:10, Gene Heskett wrote:
> On Thursday 21 October 2021 08:13:26 Dan Ritter wrote:
> 
> > > === START OF INFORMATION SECTION ===
> > > Device Model:     ST8000DM004-2CX188
> >
> > You should be able to return this drive without proving that it
> > is defective; this is one of Seagates' SMR drives that they did
> > not disclose were SMR.
> >
> > -dsr-
> 
> And what does this SMR acronym mean, Dan?

Wikipedia is quite helpful for such queries.

Searching for 'SMR' brings one to a fairly long disambiguation page, but 
there is only one entry mentioning hard drives ;)

The first two paragraphs of the article is already quite informative on 
why one might want to avoid SMR drives.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#241557

From	Andrei POPESCU <andreimpopescu@gmail.com>
Date	2021-10-21 15:20 +0200
Message-ID	<DaG9c-2ny-9@gated-at.bofh.it>
In reply to	#241556

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

On Jo, 21 oct 21, 16:02:43, Andrei POPESCU wrote:
> On Jo, 21 oct 21, 08:53:10, Gene Heskett wrote:
> > On Thursday 21 October 2021 08:13:26 Dan Ritter wrote:
> > 
> > > > === START OF INFORMATION SECTION ===
> > > > Device Model:     ST8000DM004-2CX188
> > >
> > > You should be able to return this drive without proving that it
> > > is defective; this is one of Seagates' SMR drives that they did
> > > not disclose were SMR.
> > >
> > > -dsr-
> > 
> > And what does this SMR acronym mean, Dan?
> 
> Wikipedia is quite helpful for such queries.
> 
> Searching for 'SMR' brings one to a fairly long disambiguation page, but 
> there is only one entry mentioning hard drives ;)
> 
> The first two paragraphs of the article is already quite informative on 
> why one might want to avoid SMR drives.

And let's not forget about
https://www.truenas.com/community/resources/list-of-known-smr-drives.141/

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#241470

From	basti <mailinglist@unix-solution.de>
Date	2021-10-18 19:50 +0200
Message-ID	<D9EM9-5vK-1@gated-at.bofh.it>
In reply to	#241463

Have a look at "smartctl". It will print some info about the drive and
can also "test" your drive known as S.M.A.R.T-test.

First of all i would have a look what "smartctl -a /dev/sdX" will say.

Am 18.10.21 um 18:25 schrieb Thomas Anderson:
> Hello Gurus,
> 
> I have been having problems with a drive (non-SSD) for a while now, but
> I would like to "identify" the problem specifically, so that I may
> perhaps be able to get the drive replaced.
> 
> Essentially, I have been experienced data loss, where nodes become
> unreadable, when I try to "fix it" with fdisk, it says it moves
> unreadable to the trash, basically deleting data.
> 
> I have tried reformatting the drive, writing zeros to it, and then
> temporarily the drive looks fine; but it's not! it's as if the drive is
> some how decaying: where it looks good, but then when you go to use it,
> the data later becomes unreadable.
> 
> Is there any kind of test I can execute on this drive to show it needs
> to be replaced??
> 
> Thanks!
>

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

Page 1 of 2 [1] 2 Next page →

csiph-web

Sata Hard drive testing

Contents

#241463 — Sata Hard drive testing

#241465

#241466

#241468

#241535

#241536

#241537

#241545

#241539

#241560

#241543

#241552

#241553

#241555

#241561

#241563

#241633

#241556

#241557

#241470