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

Is my hard drive about to fail?


  • Please log in to reply
2 replies to this topic

#1 ThrowingChicken

ThrowingChicken

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:04:33 AM

Posted 05 January 2014 - 12:15 PM

So I posted a couple of months back about my Seagate hard drive that just suddenly stopped working and could not be detected by the system.  While troubleshooting it with you all I saw a few comments in other tutorials that the results of a disc check might give tell tell signs of a possible near failure.  My main hard drive, the one still working, is also a Seagate and since the other drive's failure I've been a bit paranoid about the brand.  Starting a couple of days ago I noticed that when I reboot the system Windows would try to do a disk check, even though nothing had happened that would normally trigger such a thing.  I didn't have time to let it run until today.  I will post the results below.  I understand that backing up your drive is a smart move regardless of having issues or not, but based on the results below are there any tell tell signs of a drive near failure? 

It's a Seagate Barracuda ST31000520AS.  Thanks!

 

 

 

Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 3)...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x122.
The multi-sector header signature in file 0xb5570 is incorrect.
42 41 41 44 30 00 03 00 76 cb 3b b0 1d 00 00 00  BAAD0...v.;.....
02 00 01 00 38 00 01 00 58 01 00 00 00 04 00 00  ....8...X.......
Deleting corrupt file record segment 742768.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xbb.
The multi-sector header signature in file 0xb5571 is incorrect.
42 41 41 44 30 00 03 00 48 62 6e de 1e 00 00 00  BAAD0...Hbn.....
0b 00 02 00 38 00 01 00 c0 01 00 00 00 04 00 00  ....8...........
Deleting corrupt file record segment 742769.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x122.
The multi-sector header signature in file 0xb5572 is incorrect.
42 41 41 44 30 00 03 00 73 af 78 84 1a 00 00 00  BAAD0...s.x.....
02 00 01 00 38 00 01 00 58 01 00 00 00 04 00 00  ....8...X.......
Deleting corrupt file record segment 742770.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xc6.
The multi-sector header signature in file 0xb5b6d is incorrect.
42 41 41 44 30 00 03 00 d4 6c 4c 99 1d 00 00 00  BAAD0....lL.....
5a 00 02 00 38 00 01 00 e8 01 00 00 00 04 00 00  Z...8...........
Deleting corrupt file record segment 744301.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xdf.
The multi-sector header signature in file 0xb5b6e is incorrect.
42 41 41 44 30 00 03 00 2c b0 7c 1c 1d 00 00 00  BAAD0...,.|.....
0d 00 02 00 38 00 01 00 10 02 00 00 00 04 00 00  ....8...........
Deleting corrupt file record segment 744302.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x85.
The multi-sector header signature in file 0xb5b6f is incorrect.
42 41 41 44 30 00 03 00 66 a7 7f 0b 1f 00 00 00  BAAD0...f.......
08 00 02 00 38 00 01 00 e8 01 00 00 00 04 00 00  ....8...........
Deleting corrupt file record segment 744303.
The segment number 0xbe673 in file 0xbee73 is incorrect.
Fixing incorrect information in file record segment 781939.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x129b07f for possibly 0x17 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xbee73 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 781939.
The segment number 0xbe678 in file 0xbee78 is incorrect.
Fixing incorrect information in file record segment 781944.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x3f2836 for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xbee78 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 781944.
The segment number 0xbe679 in file 0xbee79 is incorrect.
Fixing incorrect information in file record segment 781945.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x253496d for possibly 0x5 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xbee79 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 781945.
The segment number 0xbe67a in file 0xbee7a is incorrect.
Fixing incorrect information in file record segment 781946.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x2534972 for possibly 0x6 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xbee7a is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 781946.
The segment number 0xbe67b in file 0xbee7b is incorrect.
Fixing incorrect information in file record segment 781947.
Attribute record of type 0x80 and instance tag 0x4 is cross linked
starting at 0x45de358 for possibly 0x1b clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x4
in file 0xbee7b is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 781947.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x5b.
The multi-sector header signature in file 0xbf10e is incorrect.
42 41 41 44 30 00 03 00 3e 07 43 e8 20 00 00 00  BAAD0...>.C. ...
8e 00 02 00 38 00 01 00 10 02 00 00 00 04 00 00  ....8...........
Deleting corrupt file record segment 782606.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x5b.
The multi-sector header signature in file 0xbf10f is incorrect.
42 41 41 44 30 00 03 00 14 08 43 e8 20 00 00 00  BAAD0.....C. ...
45 00 02 00 38 00 01 00 10 02 00 00 00 04 00 00  E...8...........
Deleting corrupt file record segment 782607.
  834304 file records processed.                                          File verification completed.
Deleting orphan file record segment 732900.
Deleting orphan file record segment 732901.
Deleting orphan file record segment 732902.
Deleting orphan file record segment 732903.
Deleting orphan file record segment 732904.
Deleting orphan file record segment 732905.
Deleting orphan file record segment 732906.
Deleting orphan file record segment 732907.
Deleting orphan file record segment 733012.
Deleting orphan file record segment 733013.
Deleting orphan file record segment 733014.
Deleting orphan file record segment 733015.
Deleting orphan file record segment 733108.
Deleting orphan file record segment 733109.
Deleting orphan file record segment 733110.
Deleting orphan file record segment 733111.
Deleting orphan file record segment 733232.
Deleting orphan file record segment 733233.
Deleting orphan file record segment 733234.
Deleting orphan file record segment 733235.
Deleting orphan file record segment 733236.
Deleting orphan file record segment 733237.
Deleting orphan file record segment 733238.
Deleting orphan file record segment 733239.
Deleting orphan file record segment 733240.
Deleting orphan file record segment 733241.
Deleting orphan file record segment 733242.
Deleting orphan file record segment 733243.
Deleting orphan file record segment 734612.
Deleting orphan file record segment 734613.
Deleting orphan file record segment 734614.
Deleting orphan file record segment 734615.
Deleting orphan file record segment 734616.
Deleting orphan file record segment 734617.
Deleting orphan file record segment 734618.
Deleting orphan file record segment 734619.
Deleting orphan file record segment 734620.
Deleting orphan file record segment 734621.
Deleting orphan file record segment 734622.
Deleting orphan file record segment 734623.
Deleting orphan file record segment 735184.
Deleting orphan file record segment 735185.
Deleting orphan file record segment 735186.
Deleting orphan file record segment 735187.
Deleting orphan file record segment 735188.
Deleting orphan file record segment 735189.
Deleting orphan file record segment 735190.
Deleting orphan file record segment 735191.
Deleting orphan file record segment 737476.
Deleting orphan file record segment 737477.
Deleting orphan file record segment 737478.
Deleting orphan file record segment 737479.
Deleting orphan file record segment 738856.
Deleting orphan file record segment 738857.
Deleting orphan file record segment 738858.
Deleting orphan file record segment 738859.
Deleting orphan file record segment 738860.
Deleting orphan file record segment 738861.
Deleting orphan file record segment 738862.
Deleting orphan file record segment 738863.
Deleting orphan file record segment 742320.
Deleting orphan file record segment 742321.
Deleting orphan file record segment 742322.
Deleting orphan file record segment 742323.
Deleting orphan file record segment 742324.
Deleting orphan file record segment 742325.
Deleting orphan file record segment 742326.
Deleting orphan file record segment 742327.
Deleting orphan file record segment 742780.
Deleting orphan file record segment 742781.
Deleting orphan file record segment 742782.
Deleting orphan file record segment 742783.
Deleting orphan file record segment 742984.
Deleting orphan file record segment 742985.
Deleting orphan file record segment 742986.
Deleting orphan file record segment 742987.
Deleting orphan file record segment 742988.
Deleting orphan file record segment 742989.
Deleting orphan file record segment 742990.
Deleting orphan file record segment 742991.
Deleting orphan file record segment 744160.
Deleting orphan file record segment 744161.
Deleting orphan file record segment 744162.
Deleting orphan file record segment 744163.
Deleting orphan file record segment 744368.
Deleting orphan file record segment 744369.
Deleting orphan file record segment 744370.
Deleting orphan file record segment 744371.
Deleting orphan file record segment 744492.
Deleting orphan file record segment 744493.
Deleting orphan file record segment 744494.
Deleting orphan file record segment 744495.
Deleting orphan file record segment 744496.
Deleting orphan file record segment 744497.
Deleting orphan file record segment 744498.
Deleting orphan file record segment 744499.
Deleting orphan file record segment 782588.
Deleting orphan file record segment 782589.
Deleting orphan file record segment 782590.
Deleting orphan file record segment 782591.
Deleting orphan file record segment 794076.
Deleting orphan file record segment 794077.
Deleting orphan file record segment 794078.
Deleting orphan file record segment 794079.
Deleting orphan file record segment 794208.
Deleting orphan file record segment 794209.
Deleting orphan file record segment 794210.
Deleting orphan file record segment 794211.
Deleting orphan file record segment 794212.
Deleting orphan file record segment 794213.
Deleting orphan file record segment 794214.
Deleting orphan file record segment 794215.
Deleting orphan file record segment 795584.
Deleting orphan file record segment 795585.
Deleting orphan file record segment 795586.
Deleting orphan file record segment 795587.
Deleting orphan file record segment 795588.
Deleting orphan file record segment 795589.
Deleting orphan file record segment 795590.
Deleting orphan file record segment 795591.
Deleting orphan file record segment 795592.
Deleting orphan file record segment 795593.
Deleting orphan file record segment 795594.
Deleting orphan file record segment 795595.
Deleting orphan file record segment 796152.
Deleting orphan file record segment 796153.
Deleting orphan file record segment 796154.
Deleting orphan file record segment 796155.
Deleting orphan file record segment 796156.
Deleting orphan file record segment 796157.
Deleting orphan file record segment 796158.
Deleting orphan file record segment 796159.
  5415 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              92 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
The object id index entry in file 0x19 points to file 0xb3030
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xb2f54
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
The object id index entry in file 0x19 points to file 0xb2f55
but the file has no object id in it.
Deleting an index entry from index $O of file 25.
Index entry MDF57B~1.INF of index $I30 in file 0x8eb points to unused file 0xb37d5.
Deleting index entry MDF57B~1.INF in index $I30 of file 2283.
Index entry mdmnis1u.inf_amd64_neutral_131acacf005e4310 of index $I30 in file 0x8eb points to unused file 0xb37d5.
Deleting index entry mdmnis1u.inf_amd64_neutral_131acacf005e4310 in index $I30 of file 2283.
Index entry AMBB6B~1.222 of index $I30 in file 0xdfa points to unused file 0xb3594.
Deleting index entry AMBB6B~1.222 in index $I30 of file 3578.
Index entry amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.1.7601.22296_none_760c8d5fd494972b of index $I30 in file 0xdfa points to unused file 0xb3594.
Deleting index entry amd64_microsoft-windows-tabletpc-journal_31bf3856ad364e35_6.1.7601.22296_none_760c8d5fd494972b in index $I30 of file 3578.
Index entry MSA23C~1.181 of index $I30 in file 0xdfa points to unused file 0xb37d7.
Deleting index entry MSA23C~1.181 in index $I30 of file 3578.
Index entry msil_system.data.linq_b77a5c561934e089_6.1.7601.18156_none_b564c792db1911a7 of index $I30 in file 0xdfa points to unused file 0xb37d7.
Deleting index entry msil_system.data.linq_b77a5c561934e089_6.1.7601.18156_none_b564c792db1911a7 in index $I30 of file 3578.
Index entry AM7BA0~1.MAN of index $I30 in file 0x264c points to unused file 0xb4629.
Deleting index entry AM7BA0~1.MAN in index $I30 of file 9804.
Index entry AM893E~1.MAN of index $I30 in file 0x264c points to unused file 0xb462e.
Deleting index entry AM893E~1.MAN in index $I30 of file 9804.
Index entry AMB650~2.MAN of index $I30 in file 0x264c points to unused file 0xb462b.
Deleting index entry AMB650~2.MAN in index $I30 of file 9804.
Index entry AMC3A8~1.MAN of index $I30 in file 0x264c points to unused file 0xb462a.
Deleting index entry AMC3A8~1.MAN in index $I30 of file 9804.
Index entry AMD0D6~2.MAN of index $I30 in file 0x264c points to unused file 0xb462c.
Deleting index entry AMD0D6~2.MAN in index $I30 of file 9804.
Index entry AMD118~1.MAN of index $I30 in file 0x264c points to unused file 0xb462d.
Deleting index entry AMD118~1.MAN in index $I30 of file 9804.
Index entry AMD319~3.MAN of index $I30 in file 0x264c points to unused file 0xb462f.
Deleting index entry AMD319~3.MAN in index $I30 of file 9804.
Index entry amd64_03d2d73e211116109135e870e97da3f2_31bf3856ad364e35_10.2.9200.16614_none_4fed608b1e28ba2b.manifest of index $I30 in file 0x264c points to unused file 0xb462f.
Deleting index entry amd64_03d2d73e211116109135e870e97da3f2_31bf3856ad364e35_10.2.9200.16614_none_4fed608b1e28ba2b.manifest in index $I30 of file 9804.
Index entry amd64_051c1e2a49d909669e0539136b86d48e_31bf3856ad364e35_10.2.9200.16614_none_cfc788ed0e97c228.manifest of index $I30 in file 0x264c points to unused file 0xb4629.
Deleting index entry amd64_051c1e2a49d909669e0539136b86d48e_31bf3856ad364e35_10.2.9200.16614_none_cfc788ed0e97c228.manifest in index $I30 of file 9804.
Index entry amd64_38f8ef1ab11d759514a5ea2539bdc7e2_31bf3856ad364e35_10.2.9200.16614_none_be19693b135bc0fe.manifest of index $I30 in file 0x264c points to unused file 0xb462d.
Deleting index entry amd64_38f8ef1ab11d759514a5ea2539bdc7e2_31bf3856ad364e35_10.2.9200.16614_none_be19693b135bc0fe.manifest in index $I30 of file 9804.
Index entry amd64_46efe8dede050e0fe0f608c511f20f19_31bf3856ad364e35_10.2.9200.16614_none_1eb02ea111fbe152.manifest of index $I30 in file 0x264c points to unused file 0xb462b.
Deleting index entry amd64_46efe8dede050e0fe0f608c511f20f19_31bf3856ad364e35_10.2.9200.16614_none_1eb02ea111fbe152.manifest in index $I30 of file 9804.
Index entry amd64_51269fe38b740d99a3ada4b0ae0ef157_31bf3856ad364e35_10.2.9200.20719_none_f4359091aff041fe.manifest of index $I30 in file 0x264c points to unused file 0xb462c.
Deleting index entry amd64_51269fe38b740d99a3ada4b0ae0ef157_31bf3856ad364e35_10.2.9200.20719_none_f4359091aff041fe.manifest in index $I30 of file 9804.
Index entry amd64_82c02a01307c1f7e5c34448707ea0054_31bf3856ad364e35_10.2.9200.20719_none_b2eabe49d704974d.manifest of index $I30 in file 0x264c points to unused file 0xb462e.
Deleting index entry amd64_82c02a01307c1f7e5c34448707ea0054_31bf3856ad364e35_10.2.9200.20719_none_b2eabe49d704974d.manifest in index $I30 of file 9804.
Index entry amd64_a44df176e266aaedece66b58f0038fe9_31bf3856ad364e35_10.2.9200.20719_none_848553fa5201024c.manifest of index $I30 in file 0x264c points to unused file 0xb4628.
Deleting index entry amd64_a44df176e266aaedece66b58f

 



BC AdBot (Login to Remove)

 


#2 rotor123

rotor123

  • Moderator
  • 8,094 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:05:33 AM

Posted 05 January 2014 - 04:18 PM

Hi, From what I see, Chkdsk was fixing some drive corruption. It happens. I've had that happen on this computer too.

 

If You are worried run SeaTools for windows and test the drive for peace of mind.

 

SeaTools for Windows

SeaTools for Windows tests SATA, USB, 1394, ATA (PATA/IDE) and SCSI drives. It installs onto your system. SeaTools for Windows is completely data safe. If the drive passes SeaTools for Windows, your troubleshooting can move to other areas.

 

Good Luck

Roger


Fortune Cookie says: Fortune not Found: Abort, Retry, Ignore?

Sent from my All-In-One Desktop. Perfect for Internet, Not for heavy usage or gaming however.

How Does a computer get Infected? http://www.bleepingcomputer.com/forums/t/2520/how-did-i-get-infected/
Forum Rules,    The BC Welcome Guide

167 @ June 2015


#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,565 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:33 AM

Posted 08 January 2014 - 05:38 PM

Just a clarification.

 

Chkdsk /r is a tool which checks the file system/files/partition.  It does not check the hard drive for problems and should never be regarded as a "check of the hard drive" when it's really a check of the file system/files.

 

The automatic start upon boot version of chkdsk...occurs because a problem is detected with files.  The auto-chkdsk is a 3-stage process and is inferior to running the chkdsk /r command, which is a 5-stage process.  Rather than relying on the auto process to fix whatever might be wrong with the file system...it's wise to run the chkdsk /r command anytime after you see that the 3-stage chkdks has initiated/run.

 

To test functionality of the hard drive (not the file system)...you should run the suggested long/extended diagnostic tool mentioned by Roger.  Do not try any of the repair functions which may seem available in the SeaTools for DOS tool.

 

Guide, SeaTools For DOS - http://www.seagate.com/support/seatools/SeaToolsDOSguide.pdf

 

SeaTools for DOS Download - http://www.seagate.com/support/internal-hard-drives/consumer-electronics/ld25-series/seatools-dos-master/

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users