Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Hard drive Health


  • Please log in to reply
4 replies to this topic

#1 hidetokun

hidetokun

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:26 AM

Posted 14 November 2016 - 06:21 PM

A little curious to how long you guys think it has til it  ceases to function.

 cause i have no clue how to read this.

 

On a Scale of 1 - 10  how dead is it?

artctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win7(64)-sp1] (sf-5.43-1)

Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net



=== START OF INFORMATION SECTION ===

Model Family:     Seagate Barracuda 7200.11

Device Model:     ST31500341AS

Serial Number:    9VS4YYJX

LU WWN Device Id: 5 000c50 02daa04c2

Firmware Version: HP23

User Capacity:    1,500,301,910,016 bytes [1.50 TB]

Sector Size:      512 bytes logical/physical

Device is:        In smartctl database [for details use: -P show]

ATA Version is:   8

ATA Standard is:  ATA-8-ACS revision 4

Local Time is:    Mon Nov 14 17:56:29 2016 EST



==> WARNING: There are known problems with these drives,

see the following Seagate web pages:

http://knowledge.seagate.com/articles/en_US/FAQ/207931en

http://knowledge.seagate.com/articles/en_US/FAQ/207951en

http://knowledge.seagate.com/articles/en_US/FAQ/207957en



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: FAILED!

Drive failure expected in less than 24 hours. SAVE ALL DATA.

See vendor-specific Attribute list for failed 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:         (  609) seconds.

Offline data collection

capabilities:              (0x5b) SMART execute Offline immediate.

                    Auto Offline data collection on/off support.

                    Suspend Offline collection upon new

                    command.

                    Offline surface scan supported.

                    Self-test supported.

                    No Conveyance Self-test supported.

                    Selective Self-test supported.

SMART capabilities:            (0x0003)    Saves SMART data before entering

                    power-saving mode.

                    Supports SMART auto save timer.

Error logging capability:        (0x01)    Error logging supported.

                    General Purpose Logging supported.

Short self-test routine

recommended polling time:      (   2) minutes.

Extended self-test routine

recommended polling time:      ( 291) minutes.

SCT capabilities:            (0x103f)    SCT Status supported.

                    SCT Error Recovery Control supported.

                    SCT Feature Control supported.

                    SCT Data Table supported.



SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate     0x002f   111   094   047    Pre-fail  Always       -       36104798

  3 Spin_Up_Time            0x0023   100   092   035    Pre-fail  Always       -       0

  4 Start_Stop_Count        0x0032   100   100   050    Old_age   Always       -       490

  5 Reallocated_Sector_Ct   0x0033   020   020   051    Pre-fail  Always   FAILING_NOW 3279

  7 Seek_Error_Rate         0x002f   088   060   047    Pre-fail  Always       -       671913910

  9 Power_On_Hours          0x0032   045   045   050    Old_age   Always   FAILING_NOW 48200

 10 Spin_Retry_Count        0x0033   100   100   051    Pre-fail  Always       -       0

 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       378

184 End-to-End_Error        0x0033   100   100   051    Pre-fail  Always       -       0

187 Reported_Uncorrect      0x0032   001   001   050    Old_age   Always   FAILING_NOW 384

188 Command_Timeout         0x0032   100   099   050    Old_age   Always       -       7

189 High_Fly_Writes         0x003a   001   001   058    Old_age   Always   FAILING_NOW 174

190 Airflow_Temperature_Cel 0x0022   060   047   034    Old_age   Always       -       40 (Min/Max 38/41)

194 Temperature_Celsius     0x0022   040   053   034    Old_age   Always       -       40 (0 15 0 0 0)

195 Hardware_ECC_Recovered  0x003a   040   027   058    Old_age   Always   FAILING_NOW 36104798

196 Reallocated_Event_Count 0x0032   020   020   050    Old_age   Always   FAILING_NOW 3279

197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       0

198 Offline_Uncorrectable   0x0030   100   100   048    Old_age   Offline      -       0

199 UDMA_CRC_Error_Count    0x003e   200   200   062    Old_age   Always       -       2

240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       195738839596099

241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       1220315607

242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1331066477



SMART Error Log Version: 1

ATA Error Count: 259 (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 259 occurred at disk power-on lifetime: 47914 hours (1996 days + 10 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 00 a8 d6 1b 00  Error: WP at LBA = 0x001bd6a8 = 1824424



  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 00 08 a8 0f 63 40 00  12d+08:14:21.914  WRITE FPDMA QUEUED

  61 00 08 50 f3 5f 40 00  12d+08:14:21.895  WRITE FPDMA QUEUED

  61 00 48 f0 8c 1b 40 00  12d+08:14:21.894  WRITE FPDMA QUEUED

  61 00 10 88 0f 63 40 00  12d+08:14:21.893  WRITE FPDMA QUEUED

  61 00 08 40 9c 79 40 00  12d+08:14:21.892  WRITE FPDMA QUEUED



Error 258 occurred at disk power-on lifetime: 47914 hours (1996 days + 10 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 00 a8 d6 1b 00  Error: WP at LBA = 0x001bd6a8 = 1824424



  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 00 08 b8 ee 0f 40 00  12d+08:14:16.141  WRITE FPDMA QUEUED

  61 00 08 98 ee 0f 40 00  12d+08:14:16.141  WRITE FPDMA QUEUED

  61 00 08 88 ee 0f 40 00  12d+08:14:16.140  WRITE FPDMA QUEUED

  61 00 08 70 ed 0f 40 00  12d+08:14:16.140  WRITE FPDMA QUEUED

  61 00 08 ff ff ff 4f 00  12d+08:14:16.139  WRITE FPDMA QUEUED



Error 257 occurred at disk power-on lifetime: 47914 hours (1996 days + 10 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 00 a8 d6 1b 00  Error: WP at LBA = 0x001bd6a8 = 1824424



  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 00 08 ff ff ff 4f 00  12d+08:14:13.194  WRITE FPDMA QUEUED

  61 00 08 ff ff ff 4f 00  12d+08:14:13.174  WRITE FPDMA QUEUED

  61 00 08 ff ff ff 4f 00  12d+08:14:13.173  WRITE FPDMA QUEUED

  61 00 08 ff ff ff 4f 00  12d+08:14:13.173  WRITE FPDMA QUEUED

  61 00 08 ff ff ff 4f 00  12d+08:14:13.172  WRITE FPDMA QUEUED



Error 256 occurred at disk power-on lifetime: 47914 hours (1996 days + 10 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 00 a8 d6 1b 00  Error: WP at LBA = 0x001bd6a8 = 1824424



  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 00 08 28 fe 28 40 00  12d+08:14:07.278  WRITE FPDMA QUEUED

  61 00 08 00 28 63 40 00  12d+08:14:07.278  WRITE FPDMA QUEUED

  61 00 03 70 14 05 40 00  12d+08:14:07.276  WRITE FPDMA QUEUED

  61 00 08 98 0f 5f 40 00  12d+08:14:07.274  WRITE FPDMA QUEUED

  61 00 08 ff ff ff 4f 00  12d+08:14:07.274  WRITE FPDMA QUEUED



Error 255 occurred at disk power-on lifetime: 47914 hours (1996 days + 10 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 00 a8 d6 1b 00  Error: WP at LBA = 0x001bd6a8 = 1824424



  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 00 07 40 ee 04 40 00  12d+08:14:04.507  WRITE FPDMA QUEUED

  61 00 08 40 b6 03 40 00  12d+08:14:04.503  WRITE FPDMA QUEUED

  61 00 08 00 1b 29 40 00  12d+08:14:04.502  WRITE FPDMA QUEUED

  61 00 18 80 f1 5f 40 00  12d+08:14:04.502  WRITE FPDMA QUEUED

  61 00 25 a8 28 07 40 00  12d+08:14:04.502  WRITE FPDMA QUEUED



SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Extended offline    Interrupted (host reset)      90%         1         -



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.


BC AdBot (Login to Remove)

 


#2 Chris Cosgrove

Chris Cosgrove

  • Moderator
  • 6,891 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Scotland
  • Local time:12:26 PM

Posted 14 November 2016 - 07:29 PM

At the very least this is a FIRM warning to back up any data you have on this drive to another !  I would make this your first priority. Without backups your data cannot be replaced.

 

SMART reports are somewhat opaque and, following a discussion I had elsewhere on BC, a subject requiring considerable study in its own right. However one fact in the report jumps out at you - the disk power on lifetime. This is given as 1996 days + which equates to about five and a half years continuous service. This is a fairly old drive and due replacement.

 

Having said that it could soldier on for another five years, or turn its toes up the next time you power on. It is impossible to give any firm indication of when any one particular device is going to fail. A commonly quoted spec is MTBF (Mean Time Before Failure). This is no more than a combination of engineers' guesswork and product life experience and is an average not related to any one device.

 

On your 1-10 scale I would put it in the 2-3 region.

 

Chris Cosgrove



#3 hidetokun

hidetokun
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:26 AM

Posted 14 November 2016 - 07:43 PM

Alrighty was just curious, I have a drive on the way.  My PC decided to tell me Saturday that failure was imminent.  So I went out and got stuff to back up my stuff and ..make a recovery media cause my computer is OEM Window 7 with a recovery partition.



#4 JohnC_21

JohnC_21

  • Members
  • 24,295 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:07:26 AM

Posted 14 November 2016 - 08:44 PM

Backing up a failing hard drive is not an optimal solution. Download Advanced Token Manager, Unzip the file to a folder on your desktop. Click the Backup button. This will store your activation in the unzipped folder. Copy the folder you unzipped to a Flash drive.

 

You can download an iso of your Windows 7 version using Windows iso downloader available here. Your AV may flag it but it's a false positive. Burn the iso to a DVD by right clicking the iso and selecting Burn Disk Image.

 

Do a install to your new disk. Copy your the Advanced Token Manager to the desktop and click on the Restore Activation button. If activation fails you can still use the key on the COA sticker and phone activation. Restoring your disk image would be the last option. 



#5 hidetokun

hidetokun
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:26 AM

Posted 14 November 2016 - 11:57 PM

Alrighty I already had burnt a Windows 7 ISO just incase... Was a back up option  if the recovery media I used with the HP crap didnt work.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users