View Single Post
  #5  
Old March 24th 21, 09:01 AM posted to alt.comp.os.windows-10,comp.sys.ibm.pc.hardware.storage
Jeff Barnett
external usenet poster
 
Posts: 6
Default Why is it not letting me extend the partition?

On 3/24/2021 12:14 AM, Paul wrote:
Yousuf Khan wrote:
So one of my oldest SSD's just finally had a bad misfire. One of its
memory cells seems to have gone bad, and it happened to be my boot
drive, so I had to restore to a new SSD from backups. That took a fair
bit of time to restore, but the new drive is twice as large as the old
one, but it created a partition that is the same size as the original.
I expected that, but I also expected that I should be able to extend
the partition after the restore to fill the new drive's size. However
going into disk management it doesn't allow me to fill up that entire
drive. Any idea what's going on here?

Â*Â*Â* Yousuf Khan


It's GPT and you need to find a utility that does a
better job of showing the partitions.

The Microsoft Reserved partition has no recognizable
file system inside, and the information I can find suggests
it is used as a space when something needs to be adjusted. It
is a tiny supply of "slack". But, it might also function as
a "blocker" when Disk Management is at work. And then, not
every utility lists it properly. Some utilities try to "hide"
things like this, and only show data partitions.

Try Linux GDisk or Linux GParted, and see if you can
spot the blocker there. The disktype utility might work,
but the only edition available there is the Cygwin one.

disktype.exe /dev/sda

--- /dev/sda
Block device, size 2.729 TiB (3000592982016 bytes)
DOS/MBR partition map
Partition 1: 2.000 TiB (2199023255040 bytes, 4294967295 sectors from 1)
Â* Type 0xEE (EFI GPT protective)
GPT partition map, 128 entries
Â* Disk size 2.729 TiB (3000592982016 bytes, 5860533168 sectors)
Â* Disk GUID EE053214-E191-B343-A670-D3A712F353DB
Partition 1: 512 MiB (536870912 bytes, 1048576 sectors from 2048)
Â* Type EFI System (FAT) (GUID 28732AC1-1FF8-D211-BA4B-00A0C93EC93B)
Â* Partition Name "EFI System Partition"
Â* Partition GUID 0CF3D241-6DA1-764C-AE0F-559E55314B8C
Â* FAT32 file system (hints score 5 of 5)
Â*Â*Â* Volume size 511.0 MiB (535805952 bytes, 130812 clusters of 4 KiB)
Partition 2: 20 GiB (21474836480 bytes, 41943040 sectors from 1050624)
Â* Type Unknown (GUID AF3DC60F-8384-7247-8E79-3D69D8477DE4)
Â* Partition Name "MINT193"
Â* Partition GUID 0647492B-0C78-DC4E-914C-E210AB6FF5A5
Â* Ext3 file system
Â*Â*Â* Volume name "MINT193"
Â*Â*Â* UUID E96B501E-23B5-4F80-A41C-CEE6A5E1D59C (DCE, v4)
Â*Â*Â* Last mounted at "/media/bullwinkle/MINT193"
Â*Â*Â* Volume size 20 GiB (21474836480 bytes, 5242880 blocks of 4 KiB)
Partition 3: 16 MiB (16777216 bytes, 32768 sectors from 123930624)
=== not visible,
Â* Type MS Reserved (GUID
16E3C9E3-5C0B-B84D-817D-F92DF00215AE)Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* diskmgmt.msc
Â* Partition Name "Microsoft reserved partition"
Â* Partition GUID 0C569E59-E917-AC40-B336-E7B2527D77AD
Â* Blank disk/medium
Partition 4: 300.4 GiB (322502360576 bytes, 629887423 sectors from
123963392)
Â* Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)
Â* Partition Name "Basic data partition"
=== actually,
Â* Partition GUID
65A1A4E6-4F11-7944-874A-B3A515F131DEÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â* "WIN10"
Â* NTFS file system
Â*Â*Â* Volume size 300.4 GiB (322502360064 bytes, 629887422 sectors)
Partition 5: 514 MiB (538968064 bytes, 1052672 sectors from 753854464)
Â* Type Unknown (GUID A4BB94DE-D106-404D-A16A-BFD50179D6AC)
Â* Partition Name ""
Â* Partition GUID 99242951-459E-1144-BF88-61517A280CCA
=== recovery
Â* NTFS file
systemÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â*Â*Â* partition
Â*Â*Â* Volume size 514.0 MiB (538967552 bytes, 1052671 sectors)

HTH,
Â*Â* Paul


There may be another issue. I'm thinking of Samsung over provisioning
(or is over something else?) where about 10% of disk free space is used
by the disk firmware to shuffle blocks in use in order to level wear. If
I wanted to change my SSD, I'd probably need to use the Samsung Magician
to first undo that block; then I could do my partition management; then
use Samsung again to enable the wear leveling. I presume that that more
than Samsung implements such a scheme.

This is not my area of expertise and I'm generalizing from my limited
experience using a few Samsung SSD on my systems. Perhaps someone more
knowledgeable can either poo poo my observation or, if it sounds right,
flesh out what is going on.
--
Jeff Barnett