Installing new SSD & keeping Win7 on HDD

C: is the new 512GB SSD with Windows 7 which I now use. I have over-provisioned it for 10% (default). I formatted it to ntfs & partitioned it by using diskpart commands by hitting Shift/F10 during the OS install before installing the OS, because I didn't want a separate part for 'system reserved', but how can I tell if the E: system reserved part is indeed the one that is safe to delete that was for the Win7 boot on the F: drive? I know it should be because it was there before installing new ssd, but in disk management I cannot find out how or where to check if the E: is indeed for the F: hdd os boot part?

What I want to do, now that I'm satisfied that the new SSD is stable is delete E: & F: then extend the G: to it's full 1TB size in disk management. And is there a way to tell for certain that the E:system reserved is for the F: hdd part os boot?

Everything looks good for booting with only Disk 0 connected.
To be absolutely sure, can you turn off the PC, disconnect Disk 1, re-boot, and make sure it boots and runs Windows with Disk 0 only ?

Personally i would extend C to include all the unallocated space.
10% free space is the minimum before getting a warning.
I would not let my OS drive get down to 20% free space before doing something.
MS updates will use space, so for the next Patch Tuesday updates, expect to have less than 10%.
I don't store User data on my C drive.

Thanks for the quick replies. David, you said "Personally i would extend C to include all the unallocated space. 10% free space is the minimum before getting a warning." That is for over-provisioning the SSD in the Samsung Magician software, so I would not want to change it because it allows improved performance and extends the life of the sdd, correct? What do you mean by 'before getting a warning'? And as I asked, can I now safely delete E: & F: and then extend the new unallocated spaces into G: partition using disk management to have the whole part as the original 1Tb WD hdd, since I will not be using the hdd as any boot drive?

7isntheaven said:

What do you mean by 'before getting a warning'?

In Windows (file) Explorer if a partition is RED that's the warning i see.
There may be better ways to get a warning, but i check my space often enough in Explorer, so this works for me.
I copied enough to my Data partition to show this warning - this partition now has less than 10% free space.

My print below is while Running Win 10, so I clicked on "This PC".
In Win 7 open Windows (file) Explorer and click on "Computer" to see a similar display.

If you see RED, it's a warning.
For an OS partition, some programs may not work correctly, or at all, with less than 10% free space.

Thanks, I should never get to the point where it shows red, I'm just installing limited programs & data to the OS part & monitor it daily. Is the system reserved part still marked 'active' because I simply disconnected it when installing Win7 on the new ssd? And can't I simply use an elevated command prompt & use diskpart commands to mark it inactive before I delete & expand it through disk management?

I couldn't mark it as inactive in DM, 'mark as active' was the only option in there. I did get it marked as inactive using the diskpart inactive command at the prompt. I rebooted & all is well. The SSD & OS is stable (a week running now) & the performance increase (boot times, opening programs, browsing, etc.) really is jaw-dropping compared to the sata HDD. I did go from IGP to a 950 GTX and installed 8GB more RAM before installing the new SSD a week earlier, so my 5+ year old mobo/system seems (to me) like it's brand new now. I guess by the time I get Win7 tweaked & know it like the back of my hand, it'll be time to move on once again.

Would you all just back up the data on the HDD & use diskpart clean command on it to remove all traces of the OS & system reserved parts or will just deleting & expanding them both into G: remove all traces of the OS? DavidE mentioned earlier that just deleting OS & system reserved parts instead of reformatting will not get rid of 'all' traces & may cause problems if I decide use it to boot/dual-boot with in the future? Thanks again.