Connected old storage drive to new rig, can't find old files

Aug 19, 2018
2
0
10
Hi guys,

I recently built up a new computer and carried over my new drives.

I had some issues starting up for the first time last night: I had both my drives (Boot SSD and Storage HDD) connected up and even though it recognised them under the SATA list in the BIOS, they weren't showing up in the Boot Priority list.

I messed around with some settings and I think I might've set it ended up booting up off the storage drive (Boot>CSM>Enabled Launch CSM>Boot from Storage Devices>UEFI Only(?)) and running Windows. Next I saw all these really old files cluttering up the desktop (the HDD used to be a boot drive before I upgraded and made it storage). So I just restarted the computer, and same thing, so I gave up and took a break.

Came back and unplugged the HDD but then got the "Reboot and Select proper Boot device etc." message. Found out it was the SSD partition not being set as active, and after some cmd stuff got it up and running.

Plugged in the HDD and all my Quick Access links weren't working so I checked the drive itself and it was filled with the Program Files, Program Files (x86) etc. files (my storage drive previously only had just folders in it). Also had a System Reserved drive in my sidebar as well, which I've never seen before. And I have 1.2TB free which doesn't feel right as I was nearing a storage cull to free up space before the transfer.

Just wondering if I screwed up when I was messing around in the BIOS and if it was possible to recover my storage.

Cheers in advance for any help you guys can give.
P.S. Sorry for the long post, just wanted to give as much info as I could.


 
Aug 19, 2018
2
0
10


Oops, yeah I meant: built up a new computer and carried over my new drives.

Update to the issue: was talking through it with a friend and I remembered that I had inserted a USB with Windows 10 on it and had run system repair. (My HDD used to be a boot drive before I used it for storage). It must've worked on the HDD so I guess that's the root of the issue.