Windows 10: Windows 10 Installation- old windows data in secondary drive

Here is the result of chkdsk
Code: C:\Windows\system32>chkdsk D: /F The type of the file system is NTFS. Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) Y Volume dismounted. All opened handles to this volume are now invalid. Stage 1: Examining basic file system structure ... 213248 file records processed. File verification completed. 4341 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 278572 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 32663 data files processed. CHKDSK is verifying Usn Journal... 39605976 USN bytes processed. Usn Journal verification completed. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. No further action is required. 312568831 KB total disk space. 36386016 KB in 135331 files. 112744 KB in 32664 indexes. 0 KB in bad sectors. 329231 KB in use by the system. 65536 KB occupied by the log file. 275740840 KB available on disk. 4096 bytes in each allocation unit. 78142207 total allocation units on disk. 68935210 allocation units available on disk.[/quote]

 

[/quote] This part could possibly cause Recuva to choke. Do you want to try that again? Deep Scan? See if it hangs at the same spot? I know it's almost 1:30 in the morning where you are (according to your time zone).

CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.

 

@f14tomcat and @axe0, do you think that at this point it would be wise for Riz to get another hard drive and clone his D drive to the new hard drive? In case there is damage to his D drive, the recovery drive could kill it and there would be no way to recover files. If he had a clone of the drive, there would be a copy of everything on a healthy drive to continue the process.

The resident expert in this is probably Jumanji. I could try to contact him and see if he can help. It will probably be tomorrow as I think it is around 1 A.M. where he is located.

 

It's 1:30 AM but it's night here not morning. So, I'll try it again at morning and let you know.

 

Ok, Riz. Meanwhile, we're looking at other options. Have a good night. TC

 

Steve, that would be excellent. Thanks you. TC

 

Done

 

Thank you essenbe for the call. I slept off the whole day unusually both AM and PM and just logged in to see your call.

I have just given a quick read. I need clarifications from the OP as well as Windows 10 experts here to understand the problem first.

Questions to the OP:

1. You said your 500GB disk was the secondary drive which had two partitions D and E. What was the extent of these two partitions in GB? What was in Partition D of that 500GB disk and what was in Partition E of that 500GB disk? Specifically where exactly was your 200GB data you want to recover?

2. Now looking at your Windows Disk Management screenshot at post #3, I see that the 500GB Disk has an unallocated 353 MB space, a C: partition of 270.10GB and E: partition of 195.31 GB. Is this C: Partition your original D: partition from which you want to recover the 200GB data?

Question to the Windows experts who have been on this thread:

Is the OP currently booting into Windows 10 from Disk 1 298.09 GB and current partition D: in it? Or is he booting from Disk 0, 465.76GB, current C: partition - where perhaps his original D: partition was there?

 

I would at first guess that Disk 0 is the one he boots from, but the partitioning doesn't make sense with the problem description.

If my logic is correct, from point of view of the problem description, he'd boot from Disk 1 and wants to recover data from C: and E:.

 

@jumanji this is the screenshot of DM from post # 3. (Windows 10 Installation- old windows data in secondary drive)





As best as I can tell, Disk 1 Partition D has the System and active flags and therefore the boot files. Disk 0 is the OS drive. He states he forgot to disconnect the old system drive when he did a clean install, and his description of events sounds like he is in somewhat of a dual boot. On startup he states he is asked if he wants to boot into Volume 1 or Volume 2.

He tried to do a file recovery of partition D with Recuva and from the picture posted in post 22 it appears it found quite a few files, but the process hung and had to be aborted.




@Riz, please read Jumanji's posts slowly and follow his instructions exactly. If you do that he will be ablke to help you recover your files, if they are recoverable.

It seems as @axe0 and I posted at the same time. He was quicker, as usual.