Set a storage space too small for my 2TB SSD

[Daniel Davis]

Basically, when I was setting up my SSD I was being a goof, wasnt paying attention and made a partition that is only 2GB instead of two TB.

[Windows7ge]

I prefer to do this from CMD:

diskpart
list disk
select disk [#]
clean
convert gpt
create partition primary
format fs=ntfs quick
assign

If all you want to do is fill the drive with one large partition this will correct your error and do it.

[Daniel Davis]

5 minutes ago, Windows7ge said:

I prefer to do this from CMD:

diskpart
list disk
select disk [#]
clean
convert gpt
create partition primary
format fs=ntfs quick
assign

If all you want to do is fill the drive with one large partition this will correct your error and do it.

For some reason its just a PrimaryPartition with the same ammount of storage, with still no option to increase to 1.80 TB 

[Windows7ge]

9 minutes ago, Daniel Davis said:

For some reason its just a PrimaryPartition with the same ammount of storage, with still no option to increase to 1.80 TB 

When you run list disk does it tell you there's still available space to use? You can select the volume and extend it. If it doesn't say there's more space available then something else must be going on here.

[Daniel Davis]

4 minutes ago, Windows7ge said:

When you run list disk does it tell you there's still available space to use? You can select the volume and extend it. If it doesn't say there's more space available then something else must be going on here.

Something else is definately going on here then, and Im not sure what it is... 

[Windows7ge]

4 minutes ago, Daniel Davis said:

Something else is definately going on here then, and Im not sure what it is... 

So it looks like by creating a volume 2GB in size the computer now thinks the whole drive is 2GB in size. The clean command should have cleared all the configuration information so I'm not sure why the 2GB volume is persisting.

 

Did you try deleting the volume from Disk Manager? Right-click the volume -> delete volume?

[Daniel Davis]

8 minutes ago, Windows7ge said:

So it looks like by creating a volume 2GB in size the computer now thinks the whole drive is 2GB in size. The clean command should have cleared all the configuration information so I'm not sure why the 2GB volume is persisting.

 

Did you try deleting the volume from Disk Manager? Right-click the volume -> delete volume?

When I delete the volume from the disk manager the partition goes from primary to Unallocated.  

[Windows7ge]

8 minutes ago, Daniel Davis said:

When I delete the volume from the disk manager the partition goes from primary to Unallocated.  

Wait. You said storage space. Are we talking about Windows Storage Spaces or are we talking about you tried to partition this one drive in Disk Management and it went awry.

 

If the latter I'm currently lost for thought. I've seen this issue one other time and it was convoluted for me to fix. I'll have to look this up again. I'm not certain all you did was mistakenly set a volume to 2GB. The Disk should still report it's full size.

[Daniel Davis]

25 minutes ago, Windows7ge said:

Wait. You said storage space. Are we talking about Windows Storage Spaces or are we talking about you tried to partition this one drive in Disk Management and it went awry.

 

If the latter I'm currently lost for thought. I've seen this issue one other time and it was convoluted for me to fix. I'll have to look this up again. I'm not certain all you did was mistakenly set a volume to 2GB. The Disk should still report it's full size.

If windows storage space = hard drive: c/ then no 

We are talking about this one specific drive that I wanted to set up, where I mistakenly set the volume significantly lower than what it really is.

[Windows7ge]

51 minutes ago, Daniel Davis said:

If windows storage space = hard drive: c/ then no 

We are talking about this one specific drive that I wanted to set up, where I mistakenly set the volume significantly lower than what it really is.

I'm trying to look-up the problem and I'm not having any luck. Normally what you'd see is your 2GB partition and to the right of it would be a block that says unallocated space but your whole drive is showing up as 2GB...

 

Lets try something dumb simple. Is the drive still unallocated? Clean the drive again (only clean it). If you shut the computer down, pull the drive, turn it on again, off again, and reconnect the drive does it still show up as an unallocated 2GB disk?

 

If it does I'm out of ideas...sorry. Did the drive say ~1.8TB when you first connected it?

[Daniel Davis]

16 minutes ago, Windows7ge said:

I'm trying to look-up the problem and I'm not having any luck. Normally what you'd see is your 2GB partition and to the right of it would be a block that says unallocated space but your whole drive is showing up as 2GB...

 

Lets try something dumb simple. Is the drive still unallocated? Clean the drive again (only clean it). If you shut the computer down, pull the drive, turn it on again, off again, and reconnect the drive does it still show up as an unallocated 2GB disk?

 

If it does I'm out of ideas...sorry. Did the drive say ~1.8TB when you first connected it?

Doing what you said with an extra shut down step instead of just two we got the following results... [Note the "Not Initialized" and 2GB instead of 1.98, sadly still not TB]

[Windows7ge]

1 minute ago, Daniel Davis said:

Doing what you said with an extra shut down step instead of just two we got the following results... [Note the "Not Initialized" and 2GB instead of 1.98, sadly still not TB]

Hmn...I'm out of ideas. The clean command fixes most config mess-up 

issues.

 

@wkdpaul Have you ever troubleshooted this before? The full 1.8TB disk appears as 2GB with no unallocated space.

1. Tried diskpart clean command
2. Tried deleting the volume from Disk Management
3. Tried unplugged and plugging it back in.

It's been a long time since I've had a go fixing this kind of issue. I'm about ready to tell him to whip up Linux and try fdisk or gparted .

[WkdPaul]

That's some weird shit right there, personally I would boot into Hirens Boot CD and check the drive using Partition Wizard or Gparted. Because as it is, Windows sees it as a 2GB drive (not a partition)

[Kilrah]

Did you set up something special in the BIOS such as RAID?

As it is Windows sees a drive that is only 2GB, so nothing you can do in Windows will show more. Need to fix it at a lower level.

[Daniel Davis]

9 hours ago, wkdpaul said:

That's some weird shit right there, personally I would boot into Hirens Boot CD and check the drive using Partition Wizard or Gparted. Because as it is, Windows sees it as a 2GB drive (not a partition)

Sadly I know very little/have very little experince when it comes to doing software troubleshooting... Would you be able to help me with that, if not does returning the SSD and getting a new one even though its the same model works as well?

[Daniel Davis]

Im just concerned about wasting my money in all honesty... if buying a new one after returning it can fix it I will do It, Im just not sure if it will label the SSD the same as my current one?

 

[Mark Kaine]

Guys,  isn't this just the thing where you need to "expand" the drive in disk management? 

I remember I had the same issue and that fixed it (was 1TB, should have been 2TB) 

 

Are we sure OP tried this yet? 

 

If yes, then I'm sorry,  it was just a thought I got when reading this thread... 

 

PS: I also had a brand-new 64GB USB stick that Windows saw as 32GB...  I had to do some command then it suddenly saw it as 64GB, I was thinking for months the store I bought it from scammed me lol.

 

Well,  I think there's definitely a solution to this problem.  Going to look up what I did with that USB stick later. 

[Daniel Davis]

I sorta cheated my way out of the problem, by just returning it and getting a new one, that its functioning 100% normal so far.