[SOLVED] Do the partition setup of the C drive "look right"?

[jaged]

Excuse my ignorance on this but should Disk 1 have that many partitions and be set up like that?

Disk 2 is how I picture 1 looking as well with an extra that's the master boot maybe? again sorry if I have it all wrong.

Can someone look at Disk 1 and let me know if anything needs to be done.

Thanks

J

https://imgur.com/a/XYsLHXm

View: https://imgur.com/a/XYsLHXm

 

[Lutfij]

Excuse my ignorance on this but should Disk 1 have that many partitions and be set up like that?
If Disk 1 is entirely setup using the mechanism within the OS installation windows, then you're all good. If you manipulated any of the partitions, I'd advise you to undo said changes on your Disk manipulation tool(assuming it's EASEUS).

Though I would've installed the OS onto a smaller SSD entirely. Large SSD's are often used as game library drives or huge scratch disks, so if you intend to install all your games on C after installing the OS, then chances are you're going to have to do it all over again when the OS decides to conk out or even the drive.

Can someone look at Disk 1 and let me know if anything needs to be done.
To reiterate, if these partitions are the result of the OS creating them during an OS install, then you're good, nothing needs tampering with.

 

[TerryLaze]

Excuse my ignorance on this but should Disk 1 have that many partitions and be set up like that?

If you did it yourself no, unless you did it for a reason.
If this is from a prebuild then it could be ok.

1 is to boot uefi
2 is fat32 which could be used by your mobo/laptop/prebuild to start recovery or whatever
3 is left free for alignment

 

[SkyNetRising]

Excuse my ignorance on this but should Disk 1 have that many partitions and be set up like that?
Can someone look at Disk 1 and let me know if anything needs to be done.

What are you trying to accomplish there?
If everything is working, then nothing needs to be done.

 

[jaged]

Excuse my ignorance on this but should Disk 1 have that many partitions and be set up like that?
If Disk 1 is entirely setup using the mechanism within the OS installation windows, then you're all good. If you manipulated any of the partitions, I'd advise you to undo said changes on your Disk manipulation tool(assuming it's EASEUS).

Though I would've installed the OS onto a smaller SSD entirely. Large SSD's are often used as game library drives or huge scratch disks, so if you intend to install all your games on C after installing the OS, then chances are you're going to have to do it all over again when the OS decides to conk out or even the drive.

Can someone look at Disk 1 and let me know if anything needs to be done.
To reiterate, if these partitions are the result of the OS creating them during an OS install, then you're good, nothing needs tampering with.

Yeah I should have gotten a 250gb or something just for the OS but wasn't thinking.

Maybe down the road I'll do that but I assume it'll be a big mess to sort out.

Installing the new drive as C: and then installing Windows on that.

Unless there's a way that you know of to put the smaller drive in and clone/copy just the windows files over to the new drive.

Thanks for the reply

 

[USAFRet]

Yeah I should have gotten a 250gb or something just for the OS but wasn't thinking.

Maybe down the road I'll do that but I assume it'll be a big mess to sort out.

Installing the new drive as C: and then installing Windows on that.

Unless there's a way that you know of to put the smaller drive in and clone/copy just the windows files over to the new drive.

Thanks for the reply

There is no way to clone that existing C drive into anything smaller than another 1TB.
You can't split out 'only the OS'.

 

[Misgar]

Looks good to me. Nothing to worry about.

When you select GPT instead of MBR after fitting a blank disk, Windows creates a small 16MB hidden partition. Both of your drives are GPT, so both have 16MB partitions. If you don't like it, delete all the partitions and change GPT to MBR. The 16MB partition should disappear (along with all your data).

The first partition (509MB) on your boot drive looks like a normal hidden Windows Recovery partition. Checking some of my MBR (not GPT) bootable SSDs, I've got a 544MB Recovery and a 529MB Recovery partition. Your 509MB is close enough to be a Recovery partition.

Your second (100MB) partition is another standard feature on my Win10 SSDs and I think this is the boot partition. One of my SSDs shows 100MB Healthy, Active, System Reserved. Another shows 100MB Healthy, EFI System Partition (I've got three bootable SSDs in the system, including Windows 7, just to make life more interesting).

As I said earlier, the third (16MB) GPT partition on your boot drive is perfectly normal.

The fourth partition 1.82TB is your standard (visible) Windows C: drive.

 

[jaged]

Looks good to me. Nothing to worry about.

When you select GPT instead of MBR after fitting a blank disk, Windows creates a small 16MB hidden partition. Both of your drives are GPT, so both have 16MB partitions. If you don't like it, delete all the partitions and change GPT to MBR. The 16MB partition should disappear (along with all your data).

The first partition (509MB) on your boot drive looks like a normal hidden Windows Recovery partition. Checking some of my MBR (not GPT) bootable SSDs, I've got a 544MB Recovery and a 529MB Recovery partition. Your 509MB is close enough to be a Recovery partition.

Your second (100MB) partition is another standard feature on my Win10 SSDs and I think this is the boot partition. One of my SSDs shows 100MB Healthy, Active, System Reserved. Another shows 100MB Healthy, EFI System Partition (I've got three bootable SSDs in the system, including Windows 7, just to make life more interesting).

As I said earlier, the third (16MB) GPT partition on your boot drive is perfectly normal.

The fourth partition 1.82TB is your standard (visible) Windows C: drive.

That is a great in-depth explanation. Thank you.

I don’t recall anything about a recovery partition being set up when I installed the drive and windows but whatever.