Smartctl Question

CaffeineAddict

Well-Known Member
Joined
Jan 21, 2024
Messages
2,104
Reaction score
1,656
Credits
17,229
I am not a fan of mint but it should not be slow. it should be running circles around the win8. You may need to check your HDD using SMART and make sure no errors. That is the most common cause of slow down.
Hey, I check my HDD with SMART using smartctl yesterday...
It has no bad sectors apparently but there are some errors that are not self-explanatory, however the overall health is reported as "PASSED".

Can you tell me what you would do with this HDD? is it OK? and which fields to pay attention to?

Bash:
sudo smartctl -a /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.7.12+bpo-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA100
Serial Number:    28JMM7SNS
LU WWN Device Id: 5 000039 fd5e51a52
Firmware Version: MS2OA750
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.3/5319
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jul  3 20:12:24 2024 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:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        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:                ( 7167) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 120) 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   142   142   054    Pre-fail  Offline      -       70
  3 Spin_Up_Time            0x0007   119   119   024    Pre-fail  Always       -       192 (Average 193)
  4 Start_Stop_Count        0x0012   095   095   000    Old_age   Always       -       20276
  5 Reallocated_Sector_Ct   0x0033   074   074   005    Pre-fail  Always       -       519
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   115   115   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   096   096   000    Old_age   Always       -       28745
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       4349
192 Power-Off_Retract_Count 0x0032   084   084   000    Old_age   Always       -       20332
193 Load_Cycle_Count        0x0012   084   084   000    Old_age   Always       -       20332
194 Temperature_Celsius     0x0002   153   153   000    Old_age   Always       -       39 (Min/Max 9/46)
196 Reallocated_Event_Count 0x0032   054   054   000    Old_age   Always       -       1001
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
ATA Error Count: 28 (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 28 occurred at disk power-on lifetime: 3399 hours (141 days + 15 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 51 0a c0 d7 ca 00  Error: UNC at LBA = 0x00cad7c0 = 13293504

  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 40 88 38 5b 30 40 00      00:36:40.816  READ FPDMA QUEUED
  60 0a 80 c0 d7 ca 40 00      00:36:40.477  READ FPDMA QUEUED
  60 e1 78 58 a8 9f 40 00      00:36:40.456  READ FPDMA QUEUED
  60 10 70 f8 da 3f 40 00      00:36:40.446  READ FPDMA QUEUED
  60 00 68 f8 d9 3f 40 00      00:36:40.446  READ FPDMA QUEUED

Error 27 occurred at disk power-on lifetime: 3399 hours (141 days + 15 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 51 08 00 be 26 00  Error: WP at LBA = 0x0026be00 = 2539008

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 18 58 a8 68 40 00      00:34:17.098  WRITE FPDMA QUEUED
  60 08 10 58 a0 3c 40 00      00:34:17.021  READ FPDMA QUEUED
  60 08 08 00 be 26 40 00      00:34:16.931  READ FPDMA QUEUED
  60 10 f8 b8 6b 01 40 00      00:34:16.910  READ FPDMA QUEUED
  60 08 f0 c0 9b 3c 40 00      00:34:16.909  READ FPDMA QUEUED

Error 26 occurred at disk power-on lifetime: 1760 hours (73 days + 8 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 51 08 e0 4f 8a 02  Error: WP at LBA = 0x028a4fe0 = 42618848

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 30 b0 43 6b 40 00      06:25:48.601  WRITE FPDMA QUEUED
  60 08 28 e0 4f 8a 40 00      06:25:48.534  READ FPDMA QUEUED
  60 08 20 e8 4f 8a 40 00      06:25:48.533  READ FPDMA QUEUED
  61 08 18 b8 b2 68 40 00      06:25:48.098  WRITE FPDMA QUEUED
  60 08 10 f0 4f 8a 40 00      06:25:47.949  READ FPDMA QUEUED

Error 25 occurred at disk power-on lifetime: 1760 hours (73 days + 8 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 51 38 f0 4f 8a 02  Error: UNC at LBA = 0x028a4ff0 = 42618864

  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 40 88 e8 4f 8a 40 00      06:25:40.727  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      06:25:40.711  FLUSH CACHE EXT
  61 08 78 98 4a 66 40 00      06:25:35.993  WRITE FPDMA QUEUED
  61 10 70 90 5e df 40 00      06:25:35.992  WRITE FPDMA QUEUED
  60 40 68 28 50 8a 40 00      06:25:35.992  READ FPDMA QUEUED

Error 24 occurred at disk power-on lifetime: 1760 hours (73 days + 8 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 51 26 68 38 23 00  Error: UNC at LBA = 0x00233868 = 2308200

  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 48 88 6f 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 00 40 88 6e 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 00 38 88 6d 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 00 30 88 6c 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 80 28 0e 38 23 40 00      06:24:55.534  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.
 


Hey, I check my HDD with SMART using smartctl yesterday...
It has no bad sectors apparently but there are some errors that are not self-explanatory, however the overall health is reported as "PASSED".

Can you tell me what you would do with this HDD? is it OK? and which fields to pay attention to?

Bash:
sudo smartctl -a /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.7.12+bpo-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA100
Serial Number:    28JMM7SNS
LU WWN Device Id: 5 000039 fd5e51a52
Firmware Version: MS2OA750
User Capacity:    1.000.204.886.016 bytes [1,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database 7.3/5319
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Jul  3 20:12:24 2024 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:  (0x84) Offline data collection activity
                                        was suspended by an interrupting command from host.
                                        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:                ( 7167) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 120) 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   142   142   054    Pre-fail  Offline      -       70
  3 Spin_Up_Time            0x0007   119   119   024    Pre-fail  Always       -       192 (Average 193)
  4 Start_Stop_Count        0x0012   095   095   000    Old_age   Always       -       20276
  5 Reallocated_Sector_Ct   0x0033   074   074   005    Pre-fail  Always       -       519
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   115   115   020    Pre-fail  Offline      -       34
  9 Power_On_Hours          0x0012   096   096   000    Old_age   Always       -       28745
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       4349
192 Power-Off_Retract_Count 0x0032   084   084   000    Old_age   Always       -       20332
193 Load_Cycle_Count        0x0012   084   084   000    Old_age   Always       -       20332
194 Temperature_Celsius     0x0002   153   153   000    Old_age   Always       -       39 (Min/Max 9/46)
196 Reallocated_Event_Count 0x0032   054   054   000    Old_age   Always       -       1001
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
ATA Error Count: 28 (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 28 occurred at disk power-on lifetime: 3399 hours (141 days + 15 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 51 0a c0 d7 ca 00  Error: UNC at LBA = 0x00cad7c0 = 13293504

  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 40 88 38 5b 30 40 00      00:36:40.816  READ FPDMA QUEUED
  60 0a 80 c0 d7 ca 40 00      00:36:40.477  READ FPDMA QUEUED
  60 e1 78 58 a8 9f 40 00      00:36:40.456  READ FPDMA QUEUED
  60 10 70 f8 da 3f 40 00      00:36:40.446  READ FPDMA QUEUED
  60 00 68 f8 d9 3f 40 00      00:36:40.446  READ FPDMA QUEUED

Error 27 occurred at disk power-on lifetime: 3399 hours (141 days + 15 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 51 08 00 be 26 00  Error: WP at LBA = 0x0026be00 = 2539008

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 18 58 a8 68 40 00      00:34:17.098  WRITE FPDMA QUEUED
  60 08 10 58 a0 3c 40 00      00:34:17.021  READ FPDMA QUEUED
  60 08 08 00 be 26 40 00      00:34:16.931  READ FPDMA QUEUED
  60 10 f8 b8 6b 01 40 00      00:34:16.910  READ FPDMA QUEUED
  60 08 f0 c0 9b 3c 40 00      00:34:16.909  READ FPDMA QUEUED

Error 26 occurred at disk power-on lifetime: 1760 hours (73 days + 8 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 51 08 e0 4f 8a 02  Error: WP at LBA = 0x028a4fe0 = 42618848

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 08 30 b0 43 6b 40 00      06:25:48.601  WRITE FPDMA QUEUED
  60 08 28 e0 4f 8a 40 00      06:25:48.534  READ FPDMA QUEUED
  60 08 20 e8 4f 8a 40 00      06:25:48.533  READ FPDMA QUEUED
  61 08 18 b8 b2 68 40 00      06:25:48.098  WRITE FPDMA QUEUED
  60 08 10 f0 4f 8a 40 00      06:25:47.949  READ FPDMA QUEUED

Error 25 occurred at disk power-on lifetime: 1760 hours (73 days + 8 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 51 38 f0 4f 8a 02  Error: UNC at LBA = 0x028a4ff0 = 42618864

  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 40 88 e8 4f 8a 40 00      06:25:40.727  READ FPDMA QUEUED
  ea 00 00 00 00 00 a0 00      06:25:40.711  FLUSH CACHE EXT
  61 08 78 98 4a 66 40 00      06:25:35.993  WRITE FPDMA QUEUED
  61 10 70 90 5e df 40 00      06:25:35.992  WRITE FPDMA QUEUED
  60 40 68 28 50 8a 40 00      06:25:35.992  READ FPDMA QUEUED

Error 24 occurred at disk power-on lifetime: 1760 hours (73 days + 8 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 51 26 68 38 23 00  Error: UNC at LBA = 0x00233868 = 2308200

  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 48 88 6f 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 00 40 88 6e 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 00 38 88 6d 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 00 30 88 6c 50 40 00      06:24:55.534  READ FPDMA QUEUED
  60 80 28 0e 38 23 40 00      06:24:55.534  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.
SMART will say passed even with issues unless they are severe. You have errors showing and bad sectors which means you should look at replacing the drive. the reallocated sector count means bad sectors that are taken care of. The seek errors show the mechanics of the drive or the motor are starting to fail. This is seen with random slow down and freezing of system.

Once a drive starts with bad sectors it is time to replace. They are like a cancer and tend to spread. It could be hours til it is dead or years, you can't tell. But if you want things to run smooth then everything needs to be running error free. At this point you can recover all the data, maybe even clone the drive to another without issue. Just don't wait too long.
 
Looking at the serial number it appears to have been made in august 02, so it's getting very old and could pop its clogs at any time, euthanasia will be the best option saving any/all files to a new drive ASAP
 
The seek errors show the mechanics of the drive or the motor are starting to fail.
You mean "7 Seek_Error_Rate"? it's at zero currently

Looking at the serial number it appears to have been made in august 02
How did you determine this? are you're saying it's from year 2002?
 
You mean "7 Seek_Error_Rate"? it's at zero currently


How did you determine this? are you're saying it's from year 2002?
I am looking at value not raw value for seek error rate. The output is a bit messy I am used to seeing in in the GUI from the disk utility. I am fairly sure it has seek errors on it but if I read the messy output wrong, it still has bad sectors which are more serious and either one is cause for me to replace because either one will cause issue in operation.
 
28JMM7SNS 2= second year =8 august if it had been 911 it would be 9th year November, the numbering system changed in 2010
 
28JMM7SNS 2= second year =8 august if it had been 911 it would be 9th year November, the numbering system changed in 2010
I can't believe it's so old, I bought it together with my PC which is not more than 6-7 years old, but I guess the HDD was in store for long time before I purchased it.

I'm now seriously considering to learn interpreting SMART output and to eventually replace my drives.
Thank you for all help to both of you!
 
I can't believe it's so old, I bought it together with my PC which is not more than 6-7 years old,
In which case, I am wondering if it's something made for and not by Toshiba, either way at 6/7/yrs your still better than expectancy.
Can you run from that machine in the terminal inxi -D and copy/paste back the result
 
Can you run from that machine in the terminal inxi -D and copy/paste back the result
Bash:
inxi -D
Drives:
  Local Storage: total: 1.36 TiB used: 959.5 GiB (68.7%)
  ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
  ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB

I am wondering if it's something made for and not by Toshiba
Drive manufacturer is Toshiba, but my PC isn't Toshiba, it's not laptop
 
I have ploughed through pages of tech, so far I have found this drive was previously made by Hitachi, until the HDD division was carved up and sold on, the desktop drive factory went to Toshiba and the laptop drives went to Western Digital around 2012 so that may be why the age using the part number and your purchase age are not marrying up
 
It says:

lol, this is HDD but they say it's "Non-HDD" :D
Thanks for trying to help though.
there was zero chance of warranty still being active for any mechanical drive I know of. usually 3 years is the warranty period. But always good to check just in case.
 
I wasn't looking fo warranty...I was trying to copy brickwizards efforts at finding a manufacturing date
 
I have ploughed through pages of tech, so far I have found this drive was previously made by Hitachi, until the HDD division was carved up and sold on, the desktop drive factory went to Toshiba and the laptop drives went to Western Digital around 2012 so that may be why the age using the part number and your purchase age are not marrying up
I was going to say..! I'm darned sure 1 TB drives weren't around in 2002.....perhaps 10 or 20 GB, that I could believe.

The anciente Dell Inspiron 1100 we purchased new in 2002 came with a 20 GB, 4,200 rpm Hitachi Travelstar. It also came with just 128 MB of DDR1; how on EARTH Dell thought that was going to run Win XP Home, I'll never know. It DID (sort of), but boy, did it struggle.

Talk about thrashing; it pretty much RAN from the page file!
facepalm-small.gif



Mike. :p
 


Members online


Latest posts

Top