SSD is showing max of 334GB and not 500GB (465GB)

[omagouch]

I upgraded my laptop with a samsung 500GB mSata SSD to increase boot time, etc. However, now that it's installed, Windows 10 is recognizing it as only being 334GB.

I'm using samsung magician to see that it's 465GB total. I've attempted to expand the volume in disk management, however it is not giving me that option.

Does anyone have any idea why windows isn't recognizing it?

 

[Boogieman_WD]

Hey there, omagouch.

Would you be so kind as to post a screenshot of what you see in Disk Management about the drive? Check the amount of space that has been left for OP (Over-Provisioning), you should be able to do that via the tool you've mentioned. Check the size that's recognized by your BIOS/UEFI as well.

What you could try is to connect the drive to a different computer, to see if the same thing happens and test it for errors. Although it seems like the issue might be something else.

I'll keep an eye for your response. Let me know if what happens.
Boogieman_WD

 

[omagouch]

Hey there, omagouch.

Would you be so kind as to post a screenshot of what you see in Disk Management about the drive? Check the amount of space that has been left for OP (Over-Provisioning), you should be able to do that via the tool you've mentioned. Check the size that's recognized by your BIOS/UEFI as well.

What you could try is to connect the drive to a different computer, to see if the same thing happens and test it for errors. Although it seems like the issue might be something else.

I'll keep an eye for your response. Let me know if what happens.
Boogieman_WD

https://imgur.com/T6zrhQN

Its ridiculously partitioned and I have no idea why. I'd nuke it if I knew it would fix everything.
It's not set up for being OP yet, and i'm not seeing an option to check how much space is left for it. It gives me the option to set it up and it would take 50MBs.

BIOS recognizes it as a 500GB SSD.

 

[omagouch]

Hey there, omagouch.

Would you be so kind as to post a screenshot of what you see in Disk Management about the drive? Check the amount of space that has been left for OP (Over-Provisioning), you should be able to do that via the tool you've mentioned. Check the size that's recognized by your BIOS/UEFI as well.

What you could try is to connect the drive to a different computer, to see if the same thing happens and test it for errors. Although it seems like the issue might be something else.

I'll keep an eye for your response. Let me know if what happens.
Boogieman_WD

Ok, I found another forum that included information about the command Diskpart. I used that to delete all the extra partitions on DIsk 0, so that's all fine and dandy.

However, the SSD is being recognized as only having 350GB on it. It simply added the 15GB from another partition.

Here's the updated disk management: https://imgur.com/QFF4DFe

It cleaned it up but didn't really help with my issue.

 

[drtweak]

Woah woah woah. First don't go off deleting partitions. You never know if you need them or not.

Second, How is Disk 0 1TB if you have a 500GB SSD? Are you use it isn't a 1TB?

Can we get exactly what you did when you installed the SSD? It looks like rather than mounting it as it's own letter you mounted it in a sub directly of the C drive almost.

 

[Boogieman_WD]

I'm with @drtweak on this one. It really seems like the SSD is Disk 1 and it corresponds to the size you are referring to. It seems like you've deleted a recovery partition of some sort and extended the D: partition's size. The label "SSD" actually means nothing and is misleading in this situation if you have a 1TB drive, as this would mean that this is not the SSD as @drtweak implied.

 

[USAFRet]

Agree with the above. Disk 1 is the physical SSD, showing the correct size (465GB)
That D drive is just a partition on the HDD, no matter what the volume label is.

 

[ArtPog]

As you have heard, your boot drive is obviously the 1 TB HDD. Anyway, you did well to pretty well recoup from that previous partitioning abomination you previously reported. I'm assuming, of course, that your system currently boots & functions without any problems.

I have no idea what that final partition on the SSD is all about - the one designated "SSD (D". In any event since it's devoid of data, delete the partition. Then use Disk Management to extend the C: partition to encompass the resulting unallocated disk-space so that your current system-boot partition will pretty well fill up that 1 TB HDD.

Next, clone the contents of the 1 TB HDD to your Samsung SSD. Since the total data contents residing on the 1 TB HDD is considerably less than the disk-space capacity of your SSD there shouldn't be a problem. Following a successful disk-cloning operation, temporarily disconnect the HDD from the system and boot to the SSD with no other drives installed. After working with the SSD to determine all is well you can reconnect the HDD and do what you will with it. I assume you're going to use it for storage/backup purposes.

 

[drtweak]

Can we get a screen shot of Device Manager with Hard Disk expanded so we can see exactly what drives are properly attached?

 

[omagouch]

I ended up doing pretty much what ArtPog said.

I ended up making a fresh copy of windows 10 on a usb
Backed up all my files
Switched the SSD to a different msata port on my laptop
Unplugged the HD
Copied windows to the SSD and started it up
Installed the HD back in
Copied all the files from the HD to the SSD
Made sure BIOS would boot from the SSD and the partitions were good

I now have all of my files, the laptop is ungodly fast now (I wish I had upgraded to a SSD years ago), and everything is in order.

I was hoping it would be a bit less time consuming, but it was worth it in the end. Thank you all for your help and time! You're the best!
Obligatory screenshot of disk management: https://imgur.com/QL75sVv

 

[ArtPog]

Frankly I'm at a complete loss to understand your process to return your system to a bootable, straightforward functional system. It seems to me you've traded one mish-mash configuration for another mish-mash configuration and I can't quite figure out why you have done this.

In any event the good news is that your Samsung 500 GB SSD is now the boot drive and apparently is functioning well.

But your 1 TB HDD that's serving as a secondary drive is a mess. Why in the world have you configured that drive as a dynamic disk? There's certainly no reason to do so and it will surely cause you grief at some future date. Since there's some data residing on that disk that I assume you want, copy all or whatever data you desire to your C:\ partition on the SSD (at least as a temporary situation) and then use Disk Management to delete the volume(s) and return that disk to a Basic disk.

Then create & format whatever number of partitions you desire on that secondary drive and transfer any data you wish from the SSD's C:\ partition to that secondary drive.

 

[omagouch]

The thing is, I've never done anything to it. When I went to check it the first time, it was a partitioned mess. How the hell that happened, i'm still wondering (I've never had to mess with partitions before, nor had a reason to). I cleaned it up as best as I could, and even now it's not letting me combine any of it; even after formatting the partitions and attempting to expand them doesn't work. I even used a program designed to work with partitions and I couldn't combine it. I don't know if its potentially damaged, corrupted, or what the deal is.

But to be honest, as long as it works as a backup and my SSD is fine, I don't really care. My problem is solved and all is well with my laptop.

 

[ArtPog]

I can understand your present reluctance to tamper any further with the present configuration of your system in view that you currently have a bootable, functional OS installed on your SSD.

But believe me...you can make book that by & by you're going to run into problems of one kind or another with your system because that 1 TB secondary HDD has been designated a dynamic disk. There is absolutely no reason for your secondary drive to be designated other than a Basic disk. And this is true for perhaps 99.9% of PC users.

Now fortunately there is no working OS installed on that dynamic disk so it's a relatively simple process to convert that disk to a Basic disk (just like your SSD boot drive) without causing any untoward problems with your present system. This is not brain surgery.

The only thing you have to contend with is that there is about 218 GB of data residing on the F: partition of the secondary HDD. You have available disk-space of only about 143 GB on your C: partition to accommodate additional data.

Is all of that 218 GB of data needed by you? Is any of that data duplicates of what already is contained on your C: partition? Or is there any data that can be deleted since it's no longer needed?

What I'm getting at is whether you could reduce that volume of data so that the available disk-space of the C: partition could accommodate that data should you transfer/copy the data to that partition (even as a temporary expedient). Or if you had another HDD available simply copy the data to that disk temporarily.

Once you clear the dynamic disk of any data that you might need it's a simple matter to use Disk Management to convert the disk back to a Basic disk. You would then be free to create one or more formatted volumes (partitions) on that disk and use it to your heart's content for storage/backup purposes.