Chkdsk problems with Ext HDD

I have a Sony HD E1 2.5 Inch 1 TB External Hard Drive bought 7 months ago.. On connecting it to Windows 8.1 Pro x64, it says "There's a problem with this drive, click here to run a scan and fix this drive" on the top right corner.. Clicking on it opens a window and asks two things, "Scan and fix now" and "continue without scanning".. I clicked on Scan and fix now, then chkdsk runs and in a while it says "chkdsk failed, click here to close this box and run chkdsk again".. On clicking this it takes me again to "Scan and fix now" and "continue without scanning" window the problem recycles..

I have no problem in accessing my files, but once in a blue moon my hard drive hangs while accessing to some folder, then it takes long time to respond and I can access the file without any problems. So, I'm afraid it'll lead to future problems like disk failure, so that I planned to chkdskk and it shows this error message:

Chkdsk was executed in read/write mode.

Checking file system on H:
Volume label is Sony HD-E1.

Stage 1: Examining basic file system structure ...

134912 file records processed. File verification completed.

2 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
Read failure with status 0xc0000010 at offset 0x3bb8dbe000 for 0x1000 bytes.
The index buffer at VCN 0x0 of index $I30 in file 0x138d7
cannot be read.
Correcting error in index $I30 for file 80087.
The index bitmap $I30 in file 0x138d7 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 80087.
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 ?? ?? ?? ?? ?? ?? ?? ?? ÿÿÿÿÿÿÿÿ........
Sorting index $I30 in file 80087.
The VCN 0xffffffffffffffff of index $I30 in file 0x13999 is already in use.
Correcting error in index $I30 for file 80281.
The index bitmap $I30 in file 0x13999 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 80281.
The down pointer of current index entry with length 0xc0 is invalid.
56 00 00 00 00 00 05 00 c0 00 a6 00 01 00 00 00 V.........¦.....
99 39 01 00 00 00 01 00 97 ee 41 f5 e9 78 cf 01 ™9......—îA.éx..
52 90 66 24 5e 59 cf 01 28 b0 b7 b3 8a 8c cf 01 Rf$^Y..(...ŠŒ..
97 ee 41 f5 e9 78 cf 01 00 f0 01 00 00 00 00 00 —îA.éx..........
e2 ea 01 00 00 00 00 00 20 00 00 00 00 00 00 00 âê...... .......
32 01 31 00 30 00 32 00 35 00 37 00 39 00 33 00 2.1.0.2.5.7.9.3.
35 00 5f 00 35 00 36 00 36 00 34 00 39 00 31 00 5._.5.6.6.4.9.1.
39 00 39 00 33 00 34 00 36 00 33 00 37 00 39 00 9.9.3.4.6.3.7.9.
35 00 5f 00 38 00 31 00 38 00 38 00 36 00 33 00 5._.8.1.8.8.6.3.
36 00 38 00 39 00 33 00 33 00 32 00 32 00 33 00 6.8.9.3.3.2.2.3.
33 00 32 00 32 00 30 00 37 00 5f 00 6f 00 2e 00 3.2.2.0.7._.o...
6a 00 70 00 67 00 00 00 ff ff ff ff ff ff ff ff j.p.g...ÿÿÿÿÿÿÿÿ
An unspecified error occurred (696e647863686b2e 808).
 
Solution
Long flie name paths are a problem so the trick is when you move a file from the main internal drive to the external, immediately rename it by taking out the system path - documents and settings/user/foldername/otherfoldername and all the other bits so it's just namled by the external's driver letter and one containing folder name.

The only other important thing to remember is to give time after writing files to an external before removing it and also to use the "Safely remove hardware" facility in Windows.
ISTM that your drive may have a problem with bad sectors. I would examine its SMART report with a tool such as CrystalDiskInfo. Look for reallocated, pending, or uncorrectable sectors.

As for the CHKDSK errors, the following error is suggesting that there is an unreadable physical sector (4096 bytes) at about the 256GB mark.

"Read failure with status 0xc0000010 at offset 0x3bb8dbe000 for 0x1000 bytes"

0x3bb8dbe000 = 256 504 487 936

http://www.google.com/search?q=0x3bb8dbe000+in+decimal

0x1000 = 4096

There also seems to be corruption in the file structure of file numbers 80087 (= 0x138D7) and 80281 (= 0x13999). The latter appears to be a JPG file (210257935_566491993463795_8188636893322332207_o.jpg.

 


But sir, there no such JPG file in my whole system with the hard disk.. Also, Can I find the location of those corrupted structures/files?
 
Open a command form by pressing your Windows key and R together then typing cmd and pressing Enter. At the prompt, type
fsutil dirty query X
where X is whatever drive letter the external drive has. Make sure it is plugged in first.

Post back what the form shows next. It may say the drive is clean - hopefully.
 
I installed CrystalDiskInfo and found this. How can I get rid of these caution? There is only one line with yellow circle..
e5b2a9.jpg
 


Volume-H is DIRTY :(
 
OK so its back to the Command Prompt and this time type
chkdsk x: /r
then hit Enter. The five stage process could take hours but be patient. Third party software is fine sometimes but nothing fixes things that Windows screws up better than Windows itself.
 
Everybody!!! I found a possible problem.. The disk is now affected (like these kind of problems) after I've copied some photos (actually downloaded from facebook from my internal hard disk to external one.. I've many other sub folders in the main folder named PICTURES including my family and friends photos.. Now what I've found is that, as fzabkar I can delete any folder other than those I've added recently (those facebook stuff).. I can't delete the files one-by-one or even at a whole of them.. When I press/choose delete, the explorer mini window appears stating preparing to delete files...discovering 2 files,etc etc and it takes so much times to discover those little size files and suddenly the window disappears and nothing is deleted.. I don't really need that crap when it comes to hard disk health..
 


I know chksdk f and r commands, but I saw in forums many people having problems with those commands that they delete their files and for someone those commands emptied the drive.. What if chkdsk H: /r (check disk and repair) deletes some of my priceless memories (images and videos)?? :( Or they don't do anything like that?
 
Checkdisk has never done that to me and I probably use it three times a week on one customer's system or another. However, it's a real concern for you so you might like to download a Linux operating system and burn it to a bootable CD, then run it as a LiveCD. It doesn't impact on your system at all, but runs purely in RAM. It will offer you the chance to transfer all your personal files from the external to another then once they've gone, the disk might perform normally under Windows.

At that stage, Checkdisk can run and not harm anything. If you use Cut and Paste rather than Copy, the drive can be cleaned up completely ready for future use. If FSUTIL declares it Clean at that stage, it's safe to use again.

Download PCLinuxOS from http://www.pclinusox.com and burn it using ImgBurn or similar. Nero tends to make hard work of it.
 
That should be the case. If Checkdisk finds a bad sector or cluster of sectors, it isolates it or them so they don't get used again. It probably also moves the files to another sector but I can't be sure of that but I've never lost a file to my knowledge. Undelete software might be able to recover it after the event if that does happen, so long as nothing has overwritten it.
 
Hi there, today morning I tried one thing.. Plugged in my external HDD and started windows in safe mode, then the system restarted, the windows logo appeared, then came a phrase Scanning and Repairing drive G: 1% complete after the process got completed fully, the system went into safe mode.. There I can delete the corrupted folder easily.. Now, booted the system in normal mode and the "fix this drive now" message on plugging the hard disk in is GONE ! To make sure, I right clicked on the drive, went to Properties-->Tools-->Error Checking--->Check.. Ha! windows said there were no problems found on this drive :wahoo::love: I thank you all for your time for answering me.. Now I want to prevent this drive from future problems like these.. So, can anybody guide me to DO's and DONT's of internal/external hard drive? I saw in some other forums that windows NTFS restricts file/folder path to 260 characters..Facebook photos have lengthy file name and so I think that folder in my ext HDD got corrupted? Is it so?
 
Long flie name paths are a problem so the trick is when you move a file from the main internal drive to the external, immediately rename it by taking out the system path - documents and settings/user/foldername/otherfoldername and all the other bits so it's just namled by the external's driver letter and one containing folder name.

The only other important thing to remember is to give time after writing files to an external before removing it and also to use the "Safely remove hardware" facility in Windows.
 
Solution
Yes, I always remove every drive with safely remove hardware facility.. When I download files, I set it to save in C:\Users\username\Downloads\Chrome\ So, can I rename the files (with less than 5 characters) within that folder itself on one day and copy them to the ext. HDD on another day?