What's wrong with my hdd and these symptoms?

[Wodjanoi]

I currently copy all my important data from my 2nd external drive to a new backup drive, because the 2nd has issues and that's why I probably need several days now to rescue my files, but I can't explain what's wrong exactly. The external drive is a Toshiba 1TB 2.5 with integrated usb 3.0 adapter for the SATA port with 40GB free space/931GB and the drive is 3 years old.
I think I have the issues since the drive did this(my external hdd suddenly started to power on and crash power off frequently 10 times in 5 seconds, before I removed it).
After I booted into Windows 8.1 and attached the drive again, I could not copy files properly, because the copy process was simply stuck in Calculating... forever.
Then I did a Restart and Windows 8.1 did not detect the drive correctly, only as Local Disk F: or the drive was simply not visible with other usb ports.
First it took me 3 days to find out how to revive it so far that I can transfer and save the files. For some weird reason I could suddenly access the drive again after booting into Acronis True Image without doing any of the operations here, except collecting info about my drives and started drive cloning process which I canceled after 5 minutes.
The time before I did this, the hdd caused the following problems:
trying to access the drive in any way caused total freeze of Windows explorer and prevent shutdown/restart, the drive was only visible as Local Drive F: and I could not access it with Disk Management and Chkdsk troubleshooting can't proceed.
Now the drive is always normally visible when I boot into Windows, but if I run CCleaner file deletion tasks or delete something on F: for example, it goes in this state again where the drive changes to Local Drive F: and freezes everything, so I need hard reboot and make sure not attempt to delete things on the drive or touch CCleaner with the drive attached.
Now I can rescue my files at least which is great, but the process consumes much time, because the write speed goes often down to 0 bytes/s and pauses for 10 - 20 seconds every time. For some files/folders this happens very frequently for other less often or it works completely without pauses sometimes.
I wanted to know what's actually wrong with this drive(bad sectors or something else?) and if I can format it later and then use it again as backup drive or if this is a bad hardware failure and I should replace the drive in any case or if I can do something right now to repair it or speed up file backup process.

[Bad 💀 Motha]

Does it have an external power source? Like an AC Power Wall Adapter?
Or does it power completely off of the USB port?

Best bet is just open the external enclosure and remove the Drive, it should just be a standarad SATA drive inside. Then connect it directly to SATA and run diagnostics on it; if the enclosure is having power related issues.

[Wodjanoi]

No, it's a 2.5 inch drive and you can connect it with a Micro B usb cable.
It takes the power from the backside usb 2.0 port.
I already opened the enclosure carefully with a knife and a screwdriver.
The adapter will arrive today, then I can remove this additional "3.0 adapter" from the SATA port and connect the drive directly with SATA to usb port.
What should I run as diagnostics?

[Bad 💀 Motha]

What adapter are you even referring to? The drive is already USB on the enclosure side right?

For diagnostics:
> Command Prompt (Admin) > CHKDSK /F /R
> Crystal Disk Info > check the drive health

If CystalDiskInfo shows a disk health problem; then download either Seagate SeaTools -or- WD Diagnostics and use those, depending on the brand of your drive. If the drive is neither of these brands, try SeaTools on it, this generally works fine even on HDDs that are Samsung, HSGT, Hitachi...

Since the drive is going to be a different drive letter, after plugging in the drive, go to My Computer or This PC in Windows Explorer and see which drive letter the main volume of the other drive is. Here's an example:

[ C ] OS - Win10x64
[ D ] Empty - DVDRW
[ E ] System Reserved
[ F ] USB - Backup HDD (this being the drive in question)
To check this drive F for example, type CHKDSK /F /R F:
Now CHKDSK will run its disk check on F drive instead of C drive.

[Washell]

Wodjanoi の投稿を引用：

Now I can rescue my files at least which is great, but the process consumes much time, because the write speed goes often down to 0 bytes/s and pauses for 10 - 20 seconds every time. For some files/folders this happens very frequently for other less often or it works completely without pauses sometimes.
I wanted to know what's actually wrong with this drive(bad sectors or something else?) and if I can format it later and then use it again as backup drive or if this is a bad hardware failure and I should replace the drive in any case or if I can do something right now to repair it or speed up file backup process.

It reads a sector, does a CRC, sees it's wrong and reads again until it gets it "right". It's the repeated reading that takes time. But, the CRC being right isn't foolproof, the data may still be garbage. The stuff you "rescued" may still be degraded and useless.

https://en.wikipedia.org/wiki/Cyclic_redundancy_check

And no, you can't use it later.

[Wodjanoi]

Actually I was unsure if I should run Chkdsk right away, but I'm glad you suggested it again, Bad_Motha - this saved a lot of time. Thanks!

Bad sectors weren't the problem and after doing the Chkdsk fix repair the drive worked normally again and properly with all usb ports. Then I could transfer the rest of my files very fast without pauses. I had SeaTools and Crystal Disk Info already installed for my previous tests and after doing a in-depth format of the drive and testing with Crystal Disk and SeaTools, it turned out that the 3 years old drive is still in a good condition(same results when I compare it with another very new hdd).

This was the Chkdsk log file from the Event Viewer:
-----------------------------------------------------------------------------------

Chkdsk was executed in read/write mode.

Checking file system on F:
The type of the file system is NTFS.
Volume label is TOSHIBA EXT.

Stage 1: Examining basic file system structure ...


1274624 file records processed. File verification completed.


132 large file records processed.

0 bad file records processed.
Stage 2: Examining file name linkage ...
The object id index entry in file 0x19 points to file 0x100c1a
but the file has no object id in it.

Deleting an index entry from index $O of file 25.

Correcting error in index $I30 for file 62654.
Correcting error in index $I30 for file 62654.
The index bitmap $I30 in file 0xf4be is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 62654.
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 62654.

Correcting error in index $I30 for file 63036.
Correcting error in index $I30 for file 63036.
The index bitmap $I30 in file 0xf63c is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 63036.
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 63036.
The two index entries of length 0x68 and 0x68 are either identical
or appear in the wrong order.
12 42 0c 00 00 00 02 00 68 00 58 00 00 00 00 00 .B......h.X.....
11 42 0c 00 00 00 02 00 1c b5 e0 89 c6 cf d2 01 .B.......µà‰ÆÏÒ.
1c b5 e0 89 c6 cf d2 01 06 f4 1b 79 fd 84 d3 01 .µà‰ÆÏÒ..ô.yý„Ó.
8e 54 ad f4 fd 84 d3 01 88 00 00 00 00 00 00 00 ŽT­ôý„Ó.ˆ.......
81 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ....... .......
0b 03 64 00 65 00 73 00 6b 00 74 00 6f 00 70 00 ..d.e.s.k.t.o.p.
2e 00 69 00 6e 00 69 00 ?? ?? ?? ?? ?? ?? ?? ?? ..i.n.i.........
----------------------------------------------------------------------
58 74 00 00 00 00 05 00 68 00 52 00 00 00 00 00 Xt......h.R.....
11 42 0c 00 00 00 02 00 4f db 91 ce bd 4a d4 01 .B......O.‘.½JÔ.
4f db 91 ce bd 4a d4 01 4f db 91 ce bd 4a d4 01 O.‘.½JÔ.O.‘.½JÔ.
4f db 91 ce bd 4a d4 01 20 02 00 00 00 00 00 00 O.‘.½JÔ. .......
20 02 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ....... .......
08 03 24 00 49 00 38 00 43 00 4d 00 57 00 4a 00 ..$.I.8.C.M.W.J.
4a 00 69 00 6e 00 69 00 ?? ?? ?? ?? ?? ?? ?? ?? J.i.n.i.........

Sorting index $I30 in file 803345.
Unable to locate the file name attribute of index entry $RXWB6B7
of index $I30 with parent 0xc4211 in file 0xf6a7c.
Deleting index entry $RXWB6B7 in index $I30 of file 803345.


1461114 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.

Recovering orphaned file $I5FE8CE (17888) into directory file 803345.
Recovering orphaned file $IQ7TYKY (29785) into directory file 803345.
Recovering orphaned file $RL1QBLK (62650) into directory file 803345.

Recovering orphaned file xx~1.DLL (62655) into directory file 62654.
Recovering orphaned file xxx .dll (62655) into directory file 62654.
Recovering orphaned file xxxx.dll (62656) into directory file 62654.
Recovering orphaned file xxxxx.dll (62657) into directory file 62654.

Recovering orphaned file xxx.dll (62658) into directory file 62654.
Recovering orphaned file xx~1.SF2 (62659) into directory file 62654.
Recovering orphaned file xxxx.sf2 (62659) into directory file 62654.
Skipping further messages about recovering orphans.


370 unindexed files scanned.
CHKDSK is recovering remaining unindexed files.


1 unindexed files recovered.
Stage 3: Examining security descriptors ...
The security Id 0x271 of security descriptor entry at offset 0x11dd0
is a duplicate.
The security Id 0x272 of security descriptor entry at offset 0x11e90
is a duplicate.
The security Id 0x273 of security descriptor entry at offset 0x11f50
is a duplicate.
The security Id 0x271 of security descriptor entry at offset 0x11dd0
is a duplicate.
The security Id 0x272 of security descriptor entry at offset 0x11e90
is a duplicate.
The security Id 0x273 of security descriptor entry at offset 0x11f50
is a duplicate.
Repairing an index entry with id 625 in index $SII of file 9.
Repairing an index entry with id 626 in index $SII of file 9.
Repairing an index entry with id 627 in index $SII of file 9.
Repairing an index entry with id 628 in index $SII of file 9.
Inserting an index entry with Id 629 into index $SII of file 9.
Inserting an index entry with Id 625 into index $SDH of file 9.
Inserting an index entry with Id 626 into index $SDH of file 9.
Inserting an index entry with Id 627 into index $SDH of file 9.
Inserting an index entry with Id 628 into index $SDH of file 9.
Inserting an index entry with Id 629 into index $SDH of file 9.
Repairing the security file record segment.
Deleting an index entry with Id 626 from index $SDH of file 9.
Deleting an index entry with Id 627 from index $SDH of file 9.
Deleting an index entry with Id 628 from index $SDH of file 9.
Deleting an index entry with Id 625 from index $SDH of file 9.
Cleaning up 8 unused index entries from index $SII of file 9.
Cleaning up 8 unused index entries from index $SDH of file 9.
Cleaning up 8 unused security descriptors.
Security descriptor verification completed.


93246 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...


1274608 files processed. File data verification completed.

Stage 5: Looking for bad, free clusters ...


11987253 free clusters processed. Free space verification is complete.
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.
No further action is required.

976759510 KB total disk space.
926842588 KB in 1167933 files.
604624 KB in 93248 indexes.
0 KB in bad sectors.
1363282 KB in use by the system.
65536 KB occupied by the log file.
47949016 KB available on disk.

4096 bytes in each allocation unit.
244189877 total allocation units on disk.
11987254 allocation units available on disk.