New
#1
How to recover 300gb of missing files?
I don’t see anywhere else this could go except here in the General section.
I have lost 279 gigabytes in 269 files on a hard drive. Sometime in the last month those files are no longer listed in file explorer or in an elevated command prompt.
D: looks like this:
$RECYCLE.BIN
PSAutoRecover
System Volume Information
pagefile.sys 10,240,000 KB
When looked at, all those Directories are empty – 0 bytes. Pagefile.sys is the only one which shows up.
Running ‘dir’ as Administrator:
D:\>dir
Volume in drive D is SATA_6_1TB
Volume Serial Number is B832-3DF8
Directory of D:\
12/18/2018 07:26 <DIR> PSAutoRecover
0 File(s) 0 bytes
1 Dir(s) 706,188,484,608 bytes free
Running 'chkdsk' as Administrator:
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure , 60672 file records processed.
File verification completed. 14 large file records processed. 0 bad file records.
Stage 2: Examining file name linkage
2 reparse records processed. 60734 index entries processed.
Index verification completed. 0
unindexed files scanned. 0 unindexed files recovered to lost and found.
2 reparse records processed.
Stage 3: Examining security descriptors. Security descriptor verification completed.
32 data files processed.
CHKDSK is verifying Usn Journal
96503120 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.
976760000 KB total disk space. ‘No problems heh.
300116640 KB in 275 files.
Rem Turns out those files are 275 .tmp files of 0 Bytes in one of the 12 $RECYCLE.BINs
Rem ‘Ex: S-1-5-21-1026165468-3402058731-3337345380-1000
752 KB in 33 indexes.
0 KB in bad sectors.
251124 KB in use by the system.
65536 KB occupied by the log file.
676391484 KB available on disk.
4096 bytes in each allocation unit.
244190000 total allocation units on disk.
169097871 allocation units available on disk
I have heard of this type of thing happening to others but can not remember the fix! Something to do with the Allocation table or mbr?
Anybody know who stole those 269 files?
Thanks for reading,
fb
Quote