[SOLVED] [SOLVED] Upgraded my Storage, now my PC confuses new disks with old

Jul 18, 2019
13
0
10
Hey there,
today I upgraded my Storage from 240GB SSD (Windows), 1TB (HDD) and 3TB (HDD) to 1TB (SSD)x2 and 3TB (HDD).
So I switched my small SSD and my old HDD for 2 new 1TB SSD's.
After cloning my old date onto my new SSD's with Macrium Reflect, everything looked fine. The data visible on my new SSD's.
Then, I was sure that everything was ok and I formated my old SSD and HDD.
When putting everything new together something was off. File Explorer and at WinDirStat both told me that i got 2 disks that are called "windows" and both have only 240GB space (just like my old SSD, which IS NOT in the PC anymore).
Now, Macrium Reflect for some reason sees the correct drives.
The ones my PC confuses for my old 240GB SSD are my 3TB HDD and one of my 1TB SSD's.

I've never heared of something like this before. Can someone help me fix this? I don't have access to my data that is on the new disks because my PC won't recognize them.

Heres what Macrium Reflect sees


Heres what WinDirStat sees

Heres what File Explorer sees (properties)

(I cant link the screenshots as images for some reason)

For more Information:
This is my current build
 
Solution
What do you mean "doesn't look better' ?

It booted up, right?
If so, we can work from there.

Still with this single drive connected, show us a screencap of your current Disk Management window.

USAFRet

Titan
Moderator
The "Windows" label is just the volume name.

However...at the end of the cloning process, the very first thing you needed to do was power off, disconnect all other drives, and power up with only the new SSD connected.

Try that now.
 
Jul 18, 2019
13
0
10
The "Windows" label is just the volume name.

However...at the end of the cloning process, the very first thing you needed to do was power off, disconnect all other drives, and power up with only the new SSD connected.

Try that now.
Hey thanks for the quick reply, so rn i have my 2 new SSD's and my old 3TB HDD connected. should i restart just without my HDD for now, or only with the new SSD that has windows on it?
 
Jul 18, 2019
13
0
10
What do you mean "doesn't look better' ?

It booted up, right?
If so, we can work from there.

Still with this single drive connected, show us a screencap of your current Disk Management window.
with it doesnt look better i mean that it booted up before too, the problem was just that im basically missing 3.5 TB of storage (and about half of that in old data).

heres the disk management
I noticed that it says a part of it is unallocated.
I haven't done this often (changing my storage, thats why i still used mostly HDD up until now), but I thought that allocating a disk once is enough... and i've done this one before already.

edit: grammar
 

USAFRet

Titan
Moderator
Right.
The clone process made a 212GB partition on this 1TB.
The exact size of the original C partition on the old drive.

There is a 707.94GB unallocated space.
You need to merge those.

Since the C partition is not right next to the unallocated space, you have 2 options.
Format that 707GB space to be its own partition with its own drive letter.
or
Use a 3rd party tool to manage those partitions, and merge the C partition(212GB) with the Unallocated 707GB.
 
Jul 18, 2019
13
0
10
Right.
The clone process made a 212GB partition on this 1TB.
The exact size of the original C partition on the old drive.

There is a 707.94GB unallocated space.
You need to merge those.

Since the C partition is not right next to the unallocated space, you have 2 options.
Format that 707GB space to be its own partition with its own drive letter.
or
Use a 3rd party tool to manage those partitions, and merge the C partition(212GB) with the Unallocated 707GB.

I'd definitively go with the merging option.
do I have to allocate the 707.94GB unallocated space first? I downloaded NIUBI and i dont get the option to merge those 2 together. it seems like i have to allocate it first, is that correct?
 
Jul 18, 2019
13
0
10
that looks exactly the same, its not movable either.

Sorry that was not correct. I dont have the option on the left to even get into the window to move it.
 
Jul 18, 2019
13
0
10
OK then....can you move the other ones?

Can you do any manipulation of the partitions on that drive?

No I wasn't able to move anything from that drive at all. But after thinking about it I made up my mind and decided to keep the other 707.94GB as a seperate partition.

So, now my problem still remains with the 3TB HDD that I think i cloned my windows onto aswell. But instead of using the free space on it (and it had enough) it wiped my disk and cloned windows on it.
I think my only option if a data recovery.. I looked for a free programm but most only let me look at the data but wont restore it if i dont buy a license. The only thing i found that kind of worked was Testdisk. The only issue with Testdisk is the way it restores the data. It also says it needs 1000+ hours to scan the drive, while others need like 6hours. Id need one that restores them sorted by data type and not by directory. Do you have know of free date recovery software except Testdisk?
 

USAFRet

Titan
Moderator
The Minitool also has a partition recovery function.

This is why my canned cloning steps states to disconnect ALL drives except for the source and target in question.
Reduces fatfinger mistakes.

-----------------------------
Specific steps for a successful clone operation:
-----------------------------
Verify the actual used space on the current drive is significantly below the size of the new SSD
Download and install Macrium Reflect (or Samsung Data Migration, if a Samsung SSD)
Power off
Disconnect ALL drives except the current C and the new SSD
Power up
Run the Macrium Reflect (or Samsung Data Migration)
Select ALL the partitions on the existing C drive
Click the 'Clone' button
Wait until it is done
When it finishes, power off
Disconnect ALL drives except for the new SSD
This is to allow the system to try to boot from ONLY the SSD
Swap the SATA cables around so that the new drive is connected to the same SATA port as the old drive
Power up, and verify the BIOS boot order
If good, continue the power up

It should boot from the new drive, just like the old drive.
Maybe reboot a time or two, just to make sure.

If it works, and it should, all is good.

Later, reconnect the old drive and wipe all partitions on it.
This will probably require the commandline diskpart function, and the clean command.

Ask questions if anything is unclear.
-----------------------------

Also, this is why full drive backups are so critical. You can recover from just about any 'oops'.