drive error confirmation

[Windows Central Question]

i was moving files from my old win7 laptop to my external drive when it suddenly disconnect (its 8 years old and tend to do that sometimes) and show the error cant locate disk. when i plug the external drive to my new win10 laptop it says it detected an error and recommend a scan. i thought kinda obvious considering what just happened so after i reconnect the drive several time to see if the notification persist im quite sure theres someting wrong so i ordered the scan (recommended) not scan and fix. apparently it found some errors like this:

Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on D:
Volume label is Seagate Expansion Drive.

Stage 1: Examining basic file system structure ...
Found corrupt basic file structure for "<0xb,0xebf>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xec9>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xeca>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xecb>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xecc>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xecd>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xece>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xecf>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed0>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed1>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed2>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed3>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed4>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed5>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed6>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed7>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed8>"
... repaired online.
Found corrupt basic file structure for "<0xa,0xed9>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xeda>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xedb>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xedc>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xedd>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xeec>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xeed>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xeee>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xeef>"
... repaired online.
Found 0x1 clusters allocated to file "<0x9,0xef0>" at offset "0" marked as free
... repaired online.
Found corrupt basic file structure for "<0x9,0xef0>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xef1>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xef2>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xef3>"
... repaired online.
Found corrupt basic file structure for "<0x9,0xef4>"
... repaired online.
Found corrupt basic file structure for "<0x8,0xefc>"
... repaired online.
19200 file records processed. File verification completed.
5 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
1775 reparse records processed. 21294 index entries processed. Index verification completed.

Found missing Index entry for file "<0x8,0xefc>" from index "\??\D:\found.000" of directory "$I30"
... repaired online.
Found 31 lost files (<0xb,0xebf>, <0xa,0xec9>, <0xa,0xeca>, ...); requesting reconnection to index "$I30" of directory "\??\D:\found.001"
... repaired online.
1775 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
1048 data files processed. CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.
Please run "chkdsk /f" to fix the issues.

1953512032 KB total disk space.
1916941252 KB in 7319 files.
5604 KB in 1051 indexes.
144772 KB in use by the system.
65536 KB occupied by the log file.
36420404 KB available on disk.

4096 bytes in each allocation unit.
488378008 total allocation units on disk.
9105101 allocation units available on disk.

----------------------------------------------------------------------

Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...
CHKDSK is scanning unindexed files for reconnect to their original directory.
0 unindexed files recovered to original directory.
CHKDSK is recovering remaining unindexed files.
Lost and found is located at \found.000

Stage 3: Examining security descriptors ...

and told me to close and repair. after that i use the win10 error checking tool but it says no error were found.

my question is:
1. did it just fix itself automatically? i run several more error check on the external drive but it doesn't found any error?
2. are the files i store are all ok?
3. is my drive ok?
4. is there something i should be worried about?

 

[Ryujingt3]

I get this when I disconnect my external USB HDD from my Android box and connect it to my laptop. I always run the scan and repair option. Usually it never finds any errors (so why do I get the pop-up saying that something is wrong with the drive?), but my files and drive are okay. Yours most likely is okay too. However, as the drive is so old, it's wise to invest in a new drive soon and copy the data from the old drive to the new one.