MultiDrive – free backup, clone & wipe disk utility from Atola Technology

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: Got bad sectors after a bad defragment
PostPosted: January 4th, 2014, 14:37 
Offline

Joined: January 4th, 2014, 14:00
Posts: 2
Location: Hooghly
Hello,
I'm on a bad situation. So, this is my story -
My laptop is ASUS K42JA with seagate 640GB HDD about 4 years old.
HDD Model: ST9640320AS; Capacity: 1250263728 LBAs; SN: 5WX12TAJ; FW: 0002SDM1
I installed windows 7 x64 about three years ago and its still running. My Hard Disk was about 90-95% full (I started backing it up). My HDD was absolutely fine until I was out of my mind and defragmented whole 640GB drive with tuneup disk defragment tool. (I didn't knew that 20% free space for each drive is must for disk defragment).
My laptop wasn't booting up - taking forever to boot. I've three partitions - C (149GB), D (149GB), E(298GB). I get into windows system recovery tools and run chkdsk and got 44kb in bad
sector in drive C. Drive D and E is fine, no bad sectors.

I boot into SeaTools DOS version did a short test. Got failure with test code 9FD8EC67. Then I did a long test and got test code 9FD8EC57.
Then I clicked on "Repair this one and all remaining" and it showed all got repaired successfully.

Now I can boot but it freezes often... I've started to backing it up.
Is it logical bad sector or physical bad sector?
Can smart be affected by logical bad sectors?
How about Resetting SMART and a Low Level Format?
What should I do now?

CHKDSK report, S.M.A.R.T status of my Hard Disk and SeaTools screenshots are given below.

chkdsk report (got from administrative tools > event viwer)
Code:
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


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)...
Attribute record of type 0xa0 and instance tag 0x59 is cross linked
starting at 0x6db for possibly 0x1 clusters.
Some clusters occupied by attribute of type 0xa0 and instance tag 0x59
in file 0x13c05 is already in use.
Deleting corrupt attribute record (160, $I30)
from file record segment 80901.
408320 file records processed. File verification completed.
20902 large file records processed. 0 bad file records processed.

2 EA records processed. 57 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
The index bitmap for index $I30 in file 0x13c05 is invalid or missing.
Correcting error in index $I30 for file 80901.
The index bitmap $I30 is present but there is no corresponding
index allocation attribute in file 0x13c05.
Correcting error in index $I30 for file 80901.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 73 df 44 f9 5f be cd 01 ........s.D._...
73 df 44 f9 5f be cd 01 c0 7e 02 31 d6 f5 ce 01 s.D._....~.1....
Sorting index $I30 in file 80901.
529368 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file GOOG-P~1.SB~ (81473) into directory file 80901.
Recovering orphaned file goog-phish-shavar.sbstore (81473) into directory file 80901.
Recovering orphaned file GOOG-M~1.PS~ (81523) into directory file 80901.
Recovering orphaned file goog-malware-shavar.pset (81523) into directory file 80901.
Recovering orphaned file GOOG-M~1.CA~ (81531) into directory file 80901.
Recovering orphaned file goog-malware-shavar.cache (81531) into directory file 80901.
Recovering orphaned file GOOG-P~1.PS~ (81533) into directory file 80901.
Recovering orphaned file goog-phish-shavar.pset (81533) into directory file 80901.
Recovering orphaned file GOOG-P~1.CA~ (81534) into directory file 80901.
Recovering orphaned file goog-phish-shavar.cache (81534) into directory file 80901.
Recovering orphaned file TEST-M~1.CA~ (81535) into directory file 80901.
Recovering orphaned file test-malware-simple.cache (81535) into directory file 80901.
Recovering orphaned file TEST-M~1.PS~ (81536) into directory file 80901.
Recovering orphaned file test-malware-simple.pset (81536) into directory file 80901.
Recovering orphaned file TEST-M~1.SB~ (81537) into directory file 80901.
Recovering orphaned file test-malware-simple.sbstore (81537) into directory file 80901.
Recovering orphaned file TEST-P~1.CA~ (81538) into directory file 80901.
Recovering orphaned file test-phish-simple.cache (81538) into directory file 80901.
Recovering orphaned file TEST-P~1.PS~ (81539) into directory file 80901.
Recovering orphaned file test-phish-simple.pset (81539) into directory file 80901.
Recovering orphaned file TEST-P~1.SB~ (81540) into directory file 80901.
Recovering orphaned file test-phish-simple.sbstore (81540) into directory file 80901.
12 unindexed files scanned. Recovering orphaned file GOOG-M~1.SB~ (81541) into directory

file 80901.
Recovering orphaned file goog-malware-shavar.sbstore (81541) into directory file 80901.
0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
408320 file SDs/SIDs processed. Cleaning up 20 unused index entries from index $SII of

file 0x9.
Cleaning up 20 unused index entries from index $SDH of file 0x9.
Cleaning up 20 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 81456.
60526 data files processed. CHKDSK is verifying Usn Journal...
35174816 USN bytes processed. Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

156256255 KB total disk space.
122822668 KB in 257895 files.
136204 KB in 60526 indexes.
44 KB in bad sectors.
514515 KB in use by the system.
65536 KB occupied by the log file.
32782824 KB available on disk.

4096 bytes in each allocation unit.
39064063 total allocation units on disk.
8195706 allocation units available on disk.

Internal Info:
00 3b 06 00 df db 04 00 9f 21 08 00 00 00 00 00 .;.......!......
54 07 00 00 39 00 00 00 00 00 00 00 00 00 00 00 T...9...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

smart status of my HDD
Image
seatools screenshots
Image
Image

Any help would be appreciated :)
Thanks in advance...


Top
 Profile  
 
 Post subject: Re: Got bad sectors after a bad defragment
PostPosted: January 4th, 2014, 15:43 
Offline

Joined: July 18th, 2006, 3:05
Posts: 7476
Location: ITALY
Worn out and according to symptom and , for what is worth because you could not diagnose it professionally , the collected data, any DIY idea is cosmetic and in a while the problem will be back with a vengeance.

Option 1 : find someone in your area who can professionally refurb the drive - you can squeeze out some more life out of it for a comparably smaller fee than ...

Option 2 ... get a new drive, replace and carry on.

If you were here I could help with plan 1. Too far, sorry.


Top
 Profile  
 
 Post subject: Re: Got bad sectors after a bad defragment
PostPosted: January 4th, 2014, 16:18 
Offline

Joined: January 4th, 2014, 14:00
Posts: 2
Location: Hooghly
Thanks BlackST,
I understand...
But believe me, it was absolutely fine before the defragment - had no problem at all.

That night I started tuneup defragment and slept. I forget that my laptop was set to turn off HD after 20 minutes and sleep after 15 minutes. In the morning I found it was just finished analyzing or something else - but the main defragment s not started at all. I started the defragment process and it got finished within 15 minutes which is not normal (all drives ware more than 95% full). Even it was fine before the reboot after tuneup defragment completed.

I was thinking about logical bad sectors.
How could a software cause to physical damage?

BTW, I started backing it up :)


Top
 Profile  
 
 Post subject: Re: Got bad sectors after a bad defragment
PostPosted: January 4th, 2014, 16:30 
Offline

Joined: July 18th, 2006, 3:05
Posts: 7476
Location: ITALY
You think it was fine but the problem was latent. When you defragged the drive something critical was allocated on a now bad area. That's all.
Or the drive has suffered some degradation between two power cycles.
Anyway it is not important to understand what happened, just find what to do now.
P.s. Hdds fail out of the blue . It happens.


Top
 Profile  
 
 Post subject: Re: Got bad sectors after a bad defragment
PostPosted: January 4th, 2014, 21:52 
Offline

Joined: July 2nd, 2011, 14:16
Posts: 463
Location: England
More than likely that this drive might have hidden bad sectors at the end of the drive, or at the end of drive C:'s partition. When you did the disk defrag the program will copy a chuck of data to the end of the drive and then move stuff around. I guess it copied important windows files to the end of your drive, then renamed its location, then attempted to copy windows files to a new location it suddenly realized that the area it copied to was a bad sector. Odvously your disk SMART management would record the bad areas and your drive would have tried to relocate the data to a spare pool area, thats why the smart errors jumped up.

I suggest you reinstall windows from a cd, copy all your files to a new disk and then fun a full scandisk on surface test. This will take a long time but should locate all the bad sectors and make the SMART test go crazy.

Looks like you had a hidden cluster that is now showing its ugly face.

Shane


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 161 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group