How Do I Move my System Reserved Partition from my HDD to my SSD after Data Migration?

Toggle sidebar Toggle sidebar
T

tenggyteng

Reputable
Dec 29, 2015
4
0
4,510
So, basically, I purchased an SSD, Samsung 850 EVO, did a data migration using the Samsung Data Migration tool. Cloned everything on my 2 Terabyte Seagate Barracuda HDD to my SSD and everything is working fine (I am using the SSD as a boot drive and the HDD as storage; I am able to boot my PC off the SSD while the HDD was not plugged in).

However, I noticed that my System Reserved Partition still resides within my HDD and not within the SSD. On Device Management, it lists the SSD as Disk 0 under Drive letter C, the HDD as Disk 1 under Drive letter F, and then System Reserved is listed within Disk 1 under letter E.

-System Reserved has 350 MB NTFS
>>Healthy (Active, Primary Partition)

The issue and concern here is, how do I move the System Reserved to the SSD? And is it normal for my SSD, Disk 0, to have 100 MB NTFS Partition?
 
Solution
A
My advice to you is to leave well enough alone and refrain from moving the SR partition from your HDD (now serving as a secondary drive) to your SSD boot drive.

For obscure reasons it sometimes develops that when a Win 8.1 OS installation is cloned to another drive, the otherwise successful operation creates a SR partition of 100 MB on the destination disk rather than the original 350 MB SR partition that exists on the source disk, i.e., your HDD.

I've never come across a clear explanation as to why this happens, but it does, albeit rarely. In any event there's no need for a user to be concerned. As long as the cloned disk - your SSD - boots & functions without any problems (and does so whether or not the HDD is connected) there is...
Sort by date Sort by votes
drtweak

drtweak

Illustrious
Sep 17, 2012
6,342
75
38,640
1) Depeneds on windows on the system reserved size. Windows 7 it was 100. 8 it was 350 8.1 i think it was 450 and on win 10 it is 500.
2) Do you really need it? No. If you aren't using Bitlocker or some other form of preboot security you don't need to worry about it. If it boots just fine when the HDD is not plugged in and just the SSD just remote it from the HDD
 
Upvote 0 Downvote
T

tenggyteng

Reputable
Dec 29, 2015
4
0
4,510


I am running windows 8.1 and I'm not using any other form of preboot security. With that said, deleting it will not affect my system? Also, is it normal for these partitions to be assigned a drive letter? They should not show up as "local disk" or "system reserved" when I open the folder "This PC", right? The 100 mb partition within the SSD is assigned drive letter G, while the System Reserved partition within the HDD is assigned drive letter E.
 
Upvote 0 Downvote
drtweak

drtweak

Illustrious
Sep 17, 2012
6,342
75
38,640
When the System reserved is on another drive that is NOT the OS it WILL show up with a drive letter. If your PC start's up just fine with with out the HDD and no system reserved partition then just delete it.

You can read up on it here

https://technet.microsoft.com/en-us/magazine/gg441289.aspx

Just if you have it, and you want to get rid of it, you have to go in and rewrite the MBR to boot directly to the OS partition and not the system reserved partition.
 
Upvote 0 Downvote
T

tenggyteng

Reputable
Dec 29, 2015
4
0
4,510


How do I go about rewriting the MBR to boot directly to the OS partition? >.< lol I'm still relatively new to this.

 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
My advice to you is to leave well enough alone and refrain from moving the SR partition from your HDD (now serving as a secondary drive) to your SSD boot drive.

For obscure reasons it sometimes develops that when a Win 8.1 OS installation is cloned to another drive, the otherwise successful operation creates a SR partition of 100 MB on the destination disk rather than the original 350 MB SR partition that exists on the source disk, i.e., your HDD.

I've never come across a clear explanation as to why this happens, but it does, albeit rarely. In any event there's no need for a user to be concerned. As long as the cloned disk - your SSD - boots & functions without any problems (and does so whether or not the HDD is connected) there is no need to do anything further. The only time there IS a problem is if the HDD needs to be connected in order for the system to boot.

So don't start manipulating the MBR or make any other system configuration modifications re this situation. And leave alone the 350 MB SR partition on your HDD; it's utilizing a trifling amount of disk-space on the 2 TB disk and just as a precaution (although probably unnecessary) leave it be.

What should concern you is to maintain a backup system re your boot drive. Seriously consider a disk-cloning program which you can routinely use to clone the contents of your SSD boot drive so that you maintain a reasonably up-to-date comprehensive backup of your system.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom