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

CrystalDiskInfo says my drive is not OK!


  • Please log in to reply
14 replies to this topic

#1 Etng03

Etng03

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 11 August 2013 - 06:36 AM

Hello!

 

I was instructed to post here from the topic at http://www.bleepingcomputer.com/forums/t/503704/windows-8-wont-boot/page-2. Apparently he asked me to run a hard disk test using CrystalDiskInfo. I did, and CrystalDiskInfo said that my drive is not OK, but instead, the drive status is caution. I think this is the right place to post my question.

 

This machine is an HP Pavilion dv7-6c43cl.

System specifications are:

Intel Core i7 2670QM

8 GB DDR3 RAM

Intel HD Graphics 3000

 

And probably, the moment you've been waiting for... the hard drive!

Toshiba MK7575GSX 750.1 GB

Firmware GT001C

Not telling you Serial Number

Interface is Serial ATA

Transfer Mode is SATA/300

Rotation Rate is 5400 RPM

Features are S.M.A.R.T., 48 bit LPA, APM, NCQ.

 

This entry is yellow:

ID C5

Attribute Name Current Pending Sector Count

Current 100

Worst 100

Threshold 0

Raw Values 000000000008

 

Thanks for all your help!

 

PS: I think this is where this question is supposed to be posted. If this is not where it is supposed to be, please move it. Also, you are free to look at the images from my referring topic. 
 



BC AdBot (Login to Remove)

 


#2 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 AM

Posted 12 August 2013 - 01:38 AM

How to obtain hard drive S.M.A.R.T data on a Windows system and then paste the report into a forum post

  • Download the GSmartControl installer application:
    • Go to the GSmartControl - Downloads page.
    • Scroll part way down the page to where the current version available for download will be displayed.
      gsmartcontrolwindowsdownload.jpeg
  • Double-click the downloaded application to run it and install GSmartControl on the computer.
    Note: Vista/Win7 users, right-click > Run as Administrator
  • When installation is complete, run GSmartControl:
    • Start GSmartControl from the Start > Programs menu.
  • When the interface has loaded and scanning for hard drives is complete, click on the hard drive icon to select the device.
  • Go to Device on the top menu > View Details, and a new Device Information window will open.
  • Click on the Attributes tab to display the S.M.A.R.T data values.
  • Near the bottom of the window, click on View Output and a new Smartctl Output window will open.
  • Right-click anywhere inside that window > Select All.
  • Again right-click in that selected area > Copy.
  • Now paste that in a reply to your topic.
    Note: Please enclose the pasted report in CODE tags so that the spacing/formatting is preserved (to make it easier for all to read).
    • Firstly, click on the "Insert code snippet" button insertcodesnippetdetail2.jpeg
    • You will then see the "start" and "end" code tags (highlighted in dark blue/selected in the image) in the text box.
    • Click between the two tags to insert the cursor between the tags and then press <Ctrl+V> to paste the report there.

Tekken
 


#3 Etng03

Etng03
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 12 August 2013 - 05:35 AM

Hello,

 

Here is the log you requested.

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win8(64)] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     TOSHIBA MK7575GSX
Serial Number:    12JEF1X2S
LU WWN Device Id: 5 000039 3c6e06602
Firmware Version: GT001C
User Capacity:    750,156,374,016 bytes [750 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Mon Aug 12 06:25:48 2013 EDT
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: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 165) 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     0x002f   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0027   100   100   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   100   100   002    Pre-fail  Always       -       2057
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       720
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       4732
 10 Spin_Retry_Count        0x0033   114   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       702
183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       65535
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       300
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   001    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   065   047   040    Old_age   Always       -       35 (Min/Max 25/35)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       144
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       196611
193 Load_Cycle_Count        0x0032   094   094   000    Old_age   Always       -       60648
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       8
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 300 (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 300 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 e2 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 f8 e8 68 53 44 40 00      05:27:22.860  READ FPDMA QUEUED
  60 20 e0 60 b4 8d 40 00      05:27:22.847  READ FPDMA QUEUED
  60 20 d8 80 84 98 40 00      05:27:22.847  READ FPDMA QUEUED
  60 00 d0 00 05 34 40 00      05:27:22.847  READ FPDMA QUEUED
  60 20 c8 87 6b 7f 40 00      05:27:22.847  READ FPDMA QUEUED

Error 299 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 5a 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 90 00 04 34 40 00      05:27:18.773  READ FPDMA QUEUED
  61 08 88 78 bf f4 40 00      05:27:18.750  WRITE FPDMA QUEUED
  61 08 80 30 37 85 40 00      05:27:18.750  WRITE FPDMA QUEUED
  61 08 78 98 d4 27 40 00      05:27:18.750  WRITE FPDMA QUEUED
  61 10 70 80 29 62 40 00      05:27:18.750  WRITE FPDMA QUEUED

Error 298 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 ea 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 08 e0 53 44 40 00      05:27:14.731  READ FPDMA QUEUED
  60 40 00 20 54 44 40 00      05:27:14.731  READ FPDMA QUEUED
  61 40 f8 20 54 44 40 00      05:27:14.730  WRITE FPDMA QUEUED
  61 40 f0 e0 53 44 40 00      05:27:14.727  WRITE FPDMA QUEUED
  60 20 e8 60 b4 8d 40 00      05:27:14.692  READ FPDMA QUEUED

Error 297 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 9a 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 f8 b0 68 53 44 40 00      05:27:10.664  READ FPDMA QUEUED
  61 40 a8 a0 53 44 40 00      05:27:10.659  WRITE FPDMA QUEUED
  61 08 a0 c0 43 69 40 00      05:27:10.648  WRITE FPDMA QUEUED
  60 20 98 60 b4 8d 40 00      05:27:10.647  READ FPDMA QUEUED
  60 08 90 60 53 44 40 00      05:27:10.647  READ FPDMA QUEUED

Error 296 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 3a 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 30 50 d0 03 34 40 00      05:27:06.616  READ FPDMA QUEUED
  60 00 48 d0 02 34 40 00      05:27:06.616  READ FPDMA QUEUED
  60 08 40 60 53 44 40 00      05:27:06.605  READ FPDMA QUEUED
  60 20 38 60 b4 8d 40 00      05:27:06.603  READ FPDMA QUEUED
  61 08 30 f0 8f 4a 40 00      05:27:06.603  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      2347         -

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.

Thank you!



#4 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 AM

Posted 12 August 2013 - 08:03 AM


197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 8

The unstable sectors are not yet reallocated which means, http://en.wikipedia.org/wiki/S.M.A.R.T.

a. They may be recovered using the windows error checking tool or checkdisk repair to map them on good spare sectors or

b. Some sectors would not be remapped after running the windows utility thus reflected on the reallocation event count.

It is best to keep an updated backup of your files and monitor these Pending Sector counts as they could sometimes unknowingly increase which would mean that the drive is failing. Try running Windows error checking tool and checkmark both options. Post a new Gsmart log after.


Tekken
 


#5 Etng03

Etng03
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 12 August 2013 - 10:02 AM

Hello,

 

For some reason, when I right-clicked C drive and went to Tools > Check, it did not give me the option to choose which options, instead it says:

 

You don't need to scan this drive

 

We haven't found any errors on this drive. You can still scan the drive for errors if you want.

 

> Scan Drive

You can keep using the drive during the scan. If errors are found, you can decide if you want to fix them.

 

I think this is Windows 8 specific... on the website, it says it applies to Windows 7.



#6 hamluis

hamluis

    Moderator


  • Moderator
  • 55,387 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:09 PM

Posted 12 August 2013 - 12:56 PM

Properties/Tools...Error Checking, push Check Now.

 

Put check marks in two boxes...Automatiically Fix and Scan For...push Start.

 

If a box comes up which states that scan cannot be completed because partition is currently in use...yes, you want to scan upon reboot and yes, you want to reboot now.

 

Louis


Edited by hamluis, 12 August 2013 - 01:00 PM.


#7 Etng03

Etng03
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 12 August 2013 - 01:30 PM

There IS no checkbox. The below link is to a set of pictures that I took of the computer.

 

http://sdrv.ms/13TdLUl

 

Also, the Check Now button is Check.

 

PS: I am running Windows 8.



#8 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 AM

Posted 13 August 2013 - 01:43 AM

I don't have Windows 8, my apology for the confusion on the particular link instructions. It seems that the sector attempt recovery option is not available on the new Windows OS. Let us know if there is a scheduled scan after the checking proceeds and on next restart.

 

Walk us through the results on how you were able to proceed and succeed with the error checking and checkdisk /r by following the link below.

http://www.eightforums.com/tutorials/6221-chkdsk-check-drive-errors-windows-8-a.html


Tekken
 


#9 Etng03

Etng03
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 13 August 2013 - 02:48 PM

Hello,

 

This morning when I turned on my computer there was no disk check happening. Since I am doing something today, I can't run chkdsk, but I'll be home in time to run it. I'll show you the results tomorrow.

 

Thank you!



#10 Etng03

Etng03
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 14 August 2013 - 07:57 AM

All right, my computer is now running checkdisk. But there is a problem: it has been on 28% forever. There is disk activity. The loading wheel is just spinning. I'll provide more information as time goes on.

#11 dpunisher

dpunisher

  • BC Advisor
  • 2,234 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:South TX
  • Local time:02:09 PM

Posted 14 August 2013 - 08:20 AM

Just scanned through the thread, and in case no one has said it..............................back up your data now, before you run anymore diagnostics on your hard drive.  Chances are the more you thrash your drive testing it, the sooner it will take a dirt nap.

 

The original error (Current Pending Sector Count) is one of the most benign SMART data related errors you can get.  Just because it is a very early indicator of possible problems doesn't mean you can fix it with a scan, or that the problem will go away.  From my experience, once you see data errors creeping up, there is a larger problem on the horizon.  If you do have your data backed up, then by all means treat this as a learning experience.

 

Good luck with it.


I am a retired Ford tech. Next to Fords, any computer is a piece of cake. (The cake, its not a lie)

3770K @4.5, Corsair H100, GTX780, 16gig Samsung, Obsidian 700 (yes there is a 700)


#12 Etng03

Etng03
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 14 August 2013 - 10:13 AM

Hello...

 

My computer just booted up and finished the disk check! Here's a GSmartControl Log:

smartctl 5.43 2012-06-30 r3573 [i686-w64-mingw32-win8(64)] (sf-5.43-1)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     TOSHIBA MK7575GSX
Serial Number:    12JEF1X2S
LU WWN Device Id: 5 000039 3c6e06602
Firmware Version: GT001C
User Capacity:    750,156,374,016 bytes [750 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Aug 14 11:05:20 2013 EDT
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: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x51) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 165) 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     0x002f   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0027   100   100   050    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0023   100   100   002    Pre-fail  Always       -       2067
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       722
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   089   089   000    Old_age   Always       -       4768
 10 Spin_Retry_Count        0x0033   114   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       704
183 Runtime_Bad_Block       0x0032   100   100   001    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
185 Unknown_Attribute       0x0032   100   100   001    Old_age   Always       -       65535
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       300
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   001    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   049   046   040    Old_age   Always       -       51 (Min/Max 25/54)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       145
192 Power-Off_Retract_Count 0x0022   100   100   000    Old_age   Always       -       196611
193 Load_Cycle_Count        0x0032   094   094   000    Old_age   Always       -       60652
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       8
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 300 (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 300 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 e2 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 f8 e8 68 53 44 40 00      05:27:22.860  READ FPDMA QUEUED
  60 20 e0 60 b4 8d 40 00      05:27:22.847  READ FPDMA QUEUED
  60 20 d8 80 84 98 40 00      05:27:22.847  READ FPDMA QUEUED
  60 00 d0 00 05 34 40 00      05:27:22.847  READ FPDMA QUEUED
  60 20 c8 87 6b 7f 40 00      05:27:22.847  READ FPDMA QUEUED

Error 299 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 5a 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 90 00 04 34 40 00      05:27:18.773  READ FPDMA QUEUED
  61 08 88 78 bf f4 40 00      05:27:18.750  WRITE FPDMA QUEUED
  61 08 80 30 37 85 40 00      05:27:18.750  WRITE FPDMA QUEUED
  61 08 78 98 d4 27 40 00      05:27:18.750  WRITE FPDMA QUEUED
  61 10 70 80 29 62 40 00      05:27:18.750  WRITE FPDMA QUEUED

Error 298 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 ea 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 08 e0 53 44 40 00      05:27:14.731  READ FPDMA QUEUED
  60 40 00 20 54 44 40 00      05:27:14.731  READ FPDMA QUEUED
  61 40 f8 20 54 44 40 00      05:27:14.730  WRITE FPDMA QUEUED
  61 40 f0 e0 53 44 40 00      05:27:14.727  WRITE FPDMA QUEUED
  60 20 e8 60 b4 8d 40 00      05:27:14.692  READ FPDMA QUEUED

Error 297 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 9a 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 f8 b0 68 53 44 40 00      05:27:10.664  READ FPDMA QUEUED
  61 40 a8 a0 53 44 40 00      05:27:10.659  WRITE FPDMA QUEUED
  61 08 a0 c0 43 69 40 00      05:27:10.648  WRITE FPDMA QUEUED
  60 20 98 60 b4 8d 40 00      05:27:10.647  READ FPDMA QUEUED
  60 08 90 60 53 44 40 00      05:27:10.647  READ FPDMA QUEUED

Error 296 occurred at disk power-on lifetime: 4722 hours (196 days + 18 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 41 3a 68 b4 8d 65  Error: UNC at LBA = 0x058db468 = 93172840

  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 30 50 d0 03 34 40 00      05:27:06.616  READ FPDMA QUEUED
  60 00 48 d0 02 34 40 00      05:27:06.616  READ FPDMA QUEUED
  60 08 40 60 53 44 40 00      05:27:06.605  READ FPDMA QUEUED
  60 20 38 60 b4 8d 40 00      05:27:06.603  READ FPDMA QUEUED
  61 08 30 f0 8f 4a 40 00      05:27:06.603  WRITE FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      2347         -

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.

Thank you!


Edited by Etng03, 14 August 2013 - 10:23 AM.


#13 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 AM

Posted 14 August 2013 - 07:18 PM

Just scanned through the thread, and in case no one has said it..............................back up your data now,

Thanks for the follow-up suggestion dpunisher. :)
 

 

It is best to keep an updated backup of your files and monitor these Pending Sector counts as they could sometimes unknowingly increase which would mean that the drive is failing

 

 

Should have highlighted that and asked the OP back if its completed. :grinner: Previous A.I.I. thread included.

 

To Etng03,

 

1.) If the computer or parts is still under warranty, please check online or call them if available.

See Related Support Links

 

2.) Please create your recovery by USB or DVDs ASAP. In the event that your drive failed or becomes unusable, the recovery discs will be able to restore your original system factory settings on a new hard drive (same HD capacity as much as possible). If there is a chance of parts (hard drive) or a laptop replacement, the created recovery discs will also be handy.

 

3.) If you need to image or clone the drive using the built-in Windows 8 image recovery or a 3rd party software, the hard drive must be atleast of the same or higher capacity to be able to complete the procedure.

Free : http://www.macrium.com/reflectfree.aspx

Paid : http://www.acronis.com/homecomputing/products/trueimage/

http://www.techrepublic.com/blog/windows-and-office/restore-windows-8-with-system-image-recovery/


Tekken
 


#14 Etng03

Etng03
  • Topic Starter

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 PM

Posted 16 August 2013 - 08:07 PM

Okay, my computer is still under warranty, and I have created a) backup and B) recovery disks. I am not cloning the drive, that is kinda stupid. Cloning your Windows installation will keep all the stuff. I would much rather start fresh. Anyway, should I consider replacing the hard drive?



#15 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:03:09 AM

Posted 17 August 2013 - 02:22 AM

It is best to replace the hard drive. Is it going to be warranty part (hard drive) or a laptop replacement?


Tekken
 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users