[SOLVED] 3TB on a 2TB drive, how to remove erroneous copy of Windows10 OS on SSD?

Jan 5, 2025
5
0
10
Hello all,

Some mistakes seem to have been made. I cloned my OS from a hard drive to new Samsung 2TB 990 PRO SSD using DiskGenius. After doing so I noticed my disk usage was always 100%. Looking into it, I find that the 2TB SSD has 3TB of OS partitioned. 1TB for my new C drive, and 2 for another E drive. The not real 1 TB 'magic' memory is called ST1000DM010-2EP102 if that means anything. See photo below and note that Disk 0 is a 1TB Samsung 980.

ZEa6uGb.png


I am not sure how I messed this up, but it is killing my ability to use my PC. As a part of the troubleshooting process I checked the following items on the PC:
- RAM ok
- Clean boot done
- error checked ssd's + check dive no errors
- quick start up disabled
- cant reset PC (windows encounters an error when trying a factory reset and aborts each time)

Could someone help me understand what the issue with my partitions is, how I may have botched the cloning process, and how to fix the issue?
 
I see 3 drives:

0, 1, and 2.

0 appears to be a 1 TB drive

1 appears to be a 2 TB drive

2 appears to be a 1 TB drive. The C partition is on this drive.

I'm not sure where you are seeing 3 TB.
Lafong, thanks for the reply. thats the thing, I only have two drives in the computer, the 1 tb 980 and the 2tb 990. I say 3TB because both drive 2 and drive 3 come from the 990. the ST1000DM010-2EP102 drive in the picture is the magic drive that I'm not sure where it came from
 
Can you still boot from the original configuration.....with the new drive totally removed?

If you can still boot with it, post another screen shot of it after you boot from it....with the new drive removed.

Did you ever attempt to boot with the OLD drive removed?

Can't help you with Disk Genius if it is part of the problem. But it may not be.
 
Last edited:
The not real 1 TB 'magic' memory is called ST1000DM010-2EP102 if that means anything.
There's no magic involved unless that 3.5" 1TB 7200rpm Seagate HDD isn't actually in your system. It's the old drive, which you were supposed to remove right after cloning and before the next boot, to see if the clone works..

By definition a Windows "reset" puts things back to the way they were when Windows was first installed. If you have since changed the hardware enough that this won't work, then the suggestion is a clean install
 
  • Like
Reactions: zprototype
Can you still boot from the original configuration.....with the new drive totally removed?

If you can still boot with it, post another screen shot of it after you boot from it....with the new drive removed.

Did you ever attempt to boot with the OLD drive removed?

Can't help you with Disk Genius if it is part of the problem. But it may not be.
the old drive is physically removed from the computer and is on my desk. it was wiped clean after the migration, so I have been booting from the new drive
 
There's no magic involved unless that 3.5" 1TB 7200rpm Seagate HDD isn't actually in your system. It's the old drive, which you were supposed to remove right after cloning and before the next boot, to see if the clone works..

By definition a Windows "reset" puts things back to the way they were when Windows was first installed. If you have since changed the hardware enough that this won't work, then the suggestion is a clean install
the hard drive was removed but I may not have done it in the correct order, would that potentially cause the phantom drive to stick around? I'll try a clean install tomorrow and get back to you