Hardware scan for errors on Linux?

redrobred · 12-19-2021, 09:44 AM

Hi

Are there any tools, software, commands etc to do a hardware (harddrive,motherboard, graphics card ...) scan for errors?

TIA
Rob

pan64 · 12-19-2021, 10:13 AM

see for example smartmontools (smartctl) or memtest. You may find info also in log files.

redrobred · 12-19-2021, 10:56 AM

Quote:

Originally Posted by pan64

see for example smartmontools (smartctl) or memtest. You may find info also in log files.

thanks, looking into the softw. ...

redrobred · 12-19-2021, 11:15 AM

Quote:

Originally Posted by pan64

see for example smartmontools (smartctl) or memtest. You may find info also in log files.

Okay I installed and ran Smartmontools on my suspected HDD ... initially it said "passed"

Code:

sudo smartctl -H /dev/sdb2
[sudo] password for rob: 
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-43-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
190 Airflow_Temperature_Cel 0x0022   062   041   045    Old_age   Always   In_the_past 38 (1 223 38 37 0)

But doing a more indepth overall, it did show some errors from the passed, ... thing is I personally with no knowledge don't know what to make of this ... might there be anyone here who can?
TIA

Code:

$ sudo smartctl -x /dev/sdb2
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-43-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Momentus 7200.5
Device Model:     ST9750420AS
Serial Number:    5WS0NYJ1
LU WWN Device Id: 5 000c50 02fc2d5a5
Firmware Version: 0005DEM1
User Capacity:    750,156,374,016 bytes [750 GB]
Sector Sizes:     512 bytes logical, 4096 bytes 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:    Sun Dec 19 19:06:36 2021 SAST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

=== 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:                (    0) 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 159) minutes.
Conveyance self-test routine
recommended polling time:        (   3) minutes.
SCT capabilities:              (0x303f) 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--   115   095   006    -    97776664
  3 Spin_Up_Time            PO----   099   098   085    -    0
  4 Start_Stop_Count        -O--CK   089   089   020    -    11869
  5 Reallocated_Sector_Ct   PO--CK   100   100   036    -    0
  7 Seek_Error_Rate         POSR--   091   060   030    -    1571457433
  9 Power_On_Hours          -O--CK   062   062   000    -    34135
 10 Spin_Retry_Count        PO--C-   100   100   097    -    0
 12 Power_Cycle_Count       -O--CK   094   094   020    -    6717
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   008   008   000    -    92
188 Command_Timeout         -O--CK   100   098   000    -    132
189 High_Fly_Writes         -O-RCK   100   100   000    -    0
190 Airflow_Temperature_Cel -O---K   062   041   045    Past 38 (1 223 38 37 0)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    416
192 Power-Off_Retract_Count -O--CK   100   100   000    -    622
193 Load_Cycle_Count        -O--CK   001   001   000    -    332144
194 Temperature_Celsius     -O---K   038   059   000    -    38 (0 9 0 0 0)
195 Hardware_ECC_Recovered  -O-RC-   115   099   000    -    97776664
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    -    0
240 Head_Flying_Hours       ------   100   253   000    -    32236 (86 45 0)
241 Total_LBAs_Written      ------   100   253   000    -    1745037816
242 Total_LBAs_Read         ------   100   253   000    -    1183194593
254 Free_Fall_Sensor        -O--CK   001   001   000    -    35
                            ||||||_ 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     R/O      5  Ext. Comprehensive SMART error log
0x06       GPL,SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09       GPL,SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     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      65  Device vendor specific log
0xa9       GPL,SL  VS       1  Device vendor specific log
0xab       GPL     VS       1  Device vendor specific log
0xae       GPL     VS       1  Device vendor specific log
0xb0       GPL     VS    2864  Device vendor specific log
0xbd       GPL     VS     252  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)
Device Error Count: 91 (device log contains only the most recent 20 errors)
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
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 91 [10] occurred at disk power-on lifetime: 29040 hours (1210 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 08 00 00 02 33 52 70 40 00     01:52:06.638  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 34 2a 18 40 00     01:52:06.636  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 33 52 78 40 00     01:52:06.634  WRITE FPDMA QUEUED
  61 00 00 00 18 00 00 02 34 2a 00 40 00     01:52:06.630  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 34 29 f8 40 00     01:52:06.624  WRITE FPDMA QUEUED

Error 90 [9] occurred at disk power-on lifetime: 29040 hours (1210 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 08 00 00 07 11 25 f8 40 00     01:52:03.236  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 33 52 78 40 00     01:52:03.235  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 07 11 25 e0 40 00     01:52:03.235  WRITE FPDMA QUEUED
  61 00 00 00 20 00 00 02 34 27 58 40 00     01:52:03.234  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 01 d8 06 30 40 00     01:52:03.234  WRITE FPDMA QUEUED

Error 89 [8] occurred at disk power-on lifetime: 29040 hours (1210 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 08 00 00 02 33 52 78 40 00     01:52:00.468  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 07 11 25 48 40 00     01:52:00.467  WRITE FPDMA QUEUED
  60 00 00 00 80 00 00 56 21 13 c0 40 00     01:52:00.467  READ FPDMA QUEUED
  61 00 00 00 10 00 00 02 34 27 48 40 00     01:52:00.466  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 01 f8 d9 50 40 00     01:52:00.466  WRITE FPDMA QUEUED

Error 88 [7] occurred at disk power-on lifetime: 29039 hours (1209 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 08 00 00 07 11 24 70 40 00     01:51:57.648  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 34 27 40 40 00     01:51:57.647  WRITE FPDMA QUEUED
  61 00 00 00 18 00 00 07 11 24 30 40 00     01:51:57.646  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 07 11 25 38 40 00     01:51:57.646  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 34 27 38 40 00     01:51:57.646  WRITE FPDMA QUEUED

Error 87 [6] occurred at disk power-on lifetime: 29039 hours (1209 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 10 00 00 01 f1 a5 a0 40 00     01:51:54.892  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 01 d8 b7 98 40 00     01:51:54.891  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 1d e8 44 73 40 00     01:51:54.891  WRITE FPDMA QUEUED
  60 00 00 00 80 00 00 56 21 13 c0 40 00     01:51:54.890  READ FPDMA QUEUED
  61 00 00 00 08 00 00 02 33 52 78 40 00     01:51:54.889  WRITE FPDMA QUEUED

Error 86 [5] occurred at disk power-on lifetime: 29039 hours (1209 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 08 00 00 1d e8 44 63 40 00     01:51:52.128  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 33 52 70 40 00     01:51:52.128  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 34 27 00 40 00     01:51:52.127  WRITE FPDMA QUEUED
  61 00 00 00 22 00 00 1d e8 44 41 40 00     01:51:52.127  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 01 dd 25 58 40 00     01:51:52.126  WRITE FPDMA QUEUED

Error 85 [4] occurred at disk power-on lifetime: 29039 hours (1209 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 08 00 00 02 29 c8 80 40 00     01:51:49.351  WRITE FPDMA QUEUED
  61 00 00 00 10 00 00 02 11 51 20 40 00     01:51:49.351  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 33 52 70 40 00     01:51:49.350  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 01 d9 63 78 40 00     01:51:49.350  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 29 b6 98 40 00     01:51:49.349  WRITE FPDMA QUEUED

Error 84 [3] occurred at disk power-on lifetime: 29039 hours (1209 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 56 21 13 d8 00 00  Error: WP at LBA = 0x562113d8 = 1445008344

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 00 00 08 00 00 02 33 52 78 40 00     01:51:46.609  WRITE FPDMA QUEUED
  61 00 00 00 08 00 00 02 4d d0 f8 40 00     01:51:46.609  WRITE FPDMA QUEUED
  60 00 00 00 80 00 00 56 21 13 c0 40 00     01:51:46.608  READ FPDMA QUEUED
  61 00 00 00 08 00 00 07 11 24 b8 40 00     01:51:46.607  WRITE FPDMA QUEUED
  61 00 00 00 10 00 00 04 18 04 90 40 00     01:51:46.607  WRITE FPDMA QUEUED

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%     31627         -
# 2  Short offline       Completed without error       00%     27325         -
# 3  Short offline       Completed: read failure       90%     12722         1321281224
# 4  Short offline       Completed without error       00%     12626         -
# 5  Short offline       Completed without error       00%     12605         -
# 6  Short offline       Completed without error       00%     12593         -
# 7  Short offline       Completed without error       00%     12576         -
# 8  Short offline       Completed without error       00%     12536         -
# 9  Short offline       Completed without error       00%     12432         -
#10  Short offline       Completed without error       00%     12398         -
#11  Short offline       Completed without error       00%       487         -
#12  Short offline       Completed without error       00%        93         -
#13  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.

SCT Status Version:                  3
SCT Version (vendor specific):       522 (0x020a)
Device State:                        Active (0)
Current Temperature:                    38 Celsius
Power Cycle Min/Max Temperature:     37/38 Celsius
Lifetime    Min/Max Temperature:      9/59 Celsius
Specified Max Operating Temperature:    44 Celsius
Under/Over Temperature Limit Count:   0/0

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

business_kid · 12-19-2021, 02:39 PM

Smartmontools is good for disks. I think I know what you are looking for and as an ex-hardware head, let me tell you it doesn't exist. You need to get analogue information from digital parts, and nothing provides that. Even then, there's errors at sub-microscopic level and a host of outside influences that affect hardware reliability.

To illustrate: On one project, a 3 or 4 component snubber circuit would randomly blow the fuse. (It was finally traced to this). A capacitor would go short circuit, blow a diode, then the fuse, and as things cooled the capacitor would self heal. So you couldn't tell it was the issue, because it was fine. But after an hour, it would go again.

Here's another one: Trucks would lose their brakes on New York's Brooklyn Bridge, and a few other places, but they worked elsewhere. Truck Component supply companies lost between $10Million & $25 Million in the 1970s. Hardware is like that. Any guesses why?

The best you can hope for is a decent post mortem analysis. Good design largely prevents these issues, but price pressure is in constant conflict with that.

computersavvy · 12-19-2021, 09:14 PM

Looking at the errors reported there, I see repeated read errors on one block, several times at 29029 hours and then repeated twice more one hour later at 29030 hours. That is one block only and if not already marked as a badblock it should be. Otherwise I see nothing in that report of major concern. In fact the drive has operated for an additional 5000+ hours since those errors so the errors are not a serious issue.

That disk is old and has had 34135 hours (almost 4 years) actual power on time with 6717 power cycles (over 6 years averaging 3 power cycles per day 365 days per year). I would consider planning for replacement solely based on the age of the device, not because of large numbers of errors.

In my experience drives with that age will usually fail suddenly and totally at some point with little to no advance warning, usually due to catastrophic hardware failure.

business_kid · 12-20-2021, 03:49 AM

+1 on the failure mode certainly. It goes dodgy and you might read some, but can't get your data off.

redrobred · 12-21-2021, 04:14 AM

Quote:

Originally Posted by business_kid

Smartmontools is good for disks. I think I know what you are looking for and as an ex-hardware head, let me tell you it doesn't exist. You need to get analogue information from digital parts, and nothing provides that. Even then, there's errors at sub-microscopic level and a host of outside influences that affect hardware reliability.

To illustrate: On one project, a 3 or 4 component snubber circuit would randomly blow the fuse. (It was finally traced to this). A capacitor would go short circuit, blow a diode, then the fuse, and as things cooled the capacitor would self heal. So you couldn't tell it was the issue, because it was fine. But after an hour, it would go again.

Here's another one: Trucks would lose their brakes on New York's Brooklyn Bridge, and a few other places, but they worked elsewhere. Truck Component supply companies lost between $10Million & $25 Million in the 1970s. Hardware is like that. Any guesses why?

The best you can hope for is a decent post mortem analysis. Good design largely prevents these issues, but price pressure is in constant conflict with that.

You lost me a bit there

... basically what I'm trying to find is is just whether it may be a software issue I'm having or if it might be my old HDD causing issues. But thanks for read

redrobred · 12-21-2021, 04:17 AM

Quote:

Originally Posted by computersavvy

Looking at the errors reported there, I see repeated read errors on one block, several times at 29029 hours and then repeated twice more one hour later at 29030 hours. That is one block only and if not already marked as a badblock it should be. Otherwise I see nothing in that report of major concern. In fact the drive has operated for an additional 5000+ hours since those errors so the errors are not a serious issue.

That disk is old and has had 34135 hours (almost 4 years) actual power on time with 6717 power cycles (over 6 years averaging 3 power cycles per day 365 days per year). I would consider planning for replacement solely based on the age of the device, not because of large numbers of errors.

In my experience drives with that age will usually fail suddenly and totally at some point with little to no advance warning, usually due to catastrophic hardware failure.

Yeah I agree ... the HDD is actually over a decade old lol ... think it's time to replace.
On that note ... might you say an entry level SSD is fine fore extra storage internally on the laptop? I know they age quicker the more one uses it read/write ... but if its cheapish but performs better and faster maybe go that way rather than another HDD?

pan64 · 12-21-2021, 05:05 AM

yes, ssd is a good choice.