Yes, as someone said, I do find obscure problems. Here is my latest:

I have a dock with a 5 1/4" drive in it, used for backups, and

Minitool Partition Wizard Free 12.8 shows with 3 partitions
System Reserved 955MB
HPWin10OS 82GB
HPWinData 145GB
unallocated 1635GB

But Macrium Reflect v8.0.7783 shows
System Reserved 955MB
HPWin10OS 82GB
HPWinData 1.74TB
no mention of unallocated space

It shows the 2nd and 3rd partitions in red, and indeed they are almost
full, but full for the 2nd is 82GM and for the 3rd is 145GB, no 1.7TB

AOMEI Partition Assistant Standard Edition v9.5 shows the same as
Macriumm Reflect in the bottom half, but in the top half of the screen
for the last patition, it has Capacity 145.67GB Free Space 37.93MB.
So in the top half, it doesn't claim the 3rd partition is 1.74TB, but it
does in the bottom half. No mention of unallocated space in eeither
half.

When I updated it to version: 10.2.1, the appearance of the page changed
some but it said the same things.

MS Computer Management / Disk Management shows less information than the
others above, but it too shows no mention of unallocated space, even
though most of the drive is unallocated and the legend at the bottom
shows that black means Unallocated space. Also, the Windows C:
partition on Drive 0 is only 3/4 full but the graph shows no Free Space,
even though the legend at the bottom shows that green means Free Space.

So of 4 similar programs, Minitool is the only that shows unallocated
space.

I don't think I've tried any others.

On Mon, 18 Dec 2023 19:33:37 -0500, micky <NONONOmisc07@fmguy.com> wrote:

>Yes, as someone said, I do find obscure problems. Here is my latest:
>
>I have a dock with a 5 1/4" drive in it

Is that a 5 1/4" floppy drive? I think the museum called. They want their
vintage exhibit back.

>used for backups, and
>
>Minitool Partition Wizard Free 12.8 shows with 3 partitions
> System Reserved 955MB
> HPWin10OS 82GB
> HPWinData 145GB
> unallocated 1635GB

Hmm, OK, not a floppy drive, but what other drive comes in a 5 1/4"?

In alt.comp.os.windows-10, on Mon, 18 Dec 2023 19:17:09 -0600, Char
Jackson <none@none.invalid> wrote:

>On Mon, 18 Dec 2023 19:33:37 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>
>>Yes, as someone said, I do find obscure problems. Here is my latest:
>>
>>I have a dock with a 5 1/4" drive in it
>
>Is that a 5 1/4" floppy drive? I think the museum called. They want their
>vintage exhibit back.

I'm not good with numbers. I guess it's not that big. ;-(
>
>>used for backups, and
>>
>>Minitool Partition Wizard Free 12.8 shows with 3 partitions
>> System Reserved 955MB
>> HPWin10OS 82GB
>> HPWinData 145GB
>> unallocated 1635GB
>
>Hmm, OK, not a floppy drive, but what other drive comes in a 5 1/4"?

Let's give up on 5 1/4. What's the most common HDD used in desktop
machines?

On Mon, 18 Dec 2023 20:52:53 -0500, micky <NONONOmisc07@fmguy.com> wrote:

>In alt.comp.os.windows-10, on Mon, 18 Dec 2023 19:17:09 -0600, Char
>Jackson <none@none.invalid> wrote:
>
>>On Mon, 18 Dec 2023 19:33:37 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>>
>>>Yes, as someone said, I do find obscure problems. Here is my latest:
>>>
>>>I have a dock with a 5 1/4" drive in it
>>
>>Is that a 5 1/4" floppy drive? I think the museum called. They want their
>>vintage exhibit back.
>
>I'm not good with numbers. I guess it's not that big. ;-(
>>
>>>used for backups, and
>>>
>>>Minitool Partition Wizard Free 12.8 shows with 3 partitions
>>> System Reserved 955MB
>>> HPWin10OS 82GB
>>> HPWinData 145GB
>>> unallocated 1635GB
>>
>>Hmm, OK, not a floppy drive, but what other drive comes in a 5 1/4"?
>
>Let's give up on 5 1/4. What's the most common HDD used in desktop
>machines?

They've been 3 1/2" for a very long time now, if you're asking about physical
size of desktop HDDs. Since physical size is standardized, capacity is more
often discussed these days. Yours is a 2 TB model? 1635+145+82 = 1862, which is
exactly what a formatted 2 TB drive would give.

On 12/18/2023 8:52 PM, micky wrote:
> In alt.comp.os.windows-10, on Mon, 18 Dec 2023 19:17:09 -0600, Char
> Jackson <none@none.invalid> wrote:
>
>> On Mon, 18 Dec 2023 19:33:37 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>>
>>> Yes, as someone said, I do find obscure problems. Here is my latest:
>>>
>>> I have a dock with a 5 1/4" drive in it
>>
>> Is that a 5 1/4" floppy drive? I think the museum called. They want their
>> vintage exhibit back.
>
> I'm not good with numbers. I guess it's not that big. ;-(
>>
>>> used for backups, and
>>>
>>> Minitool Partition Wizard Free 12.8 shows with 3 partitions
>>> System Reserved 955MB
>>> HPWin10OS 82GB
>>> HPWinData 145GB
>>> unallocated 1635GB
>>
>> Hmm, OK, not a floppy drive, but what other drive comes in a 5 1/4"?
>
> Let's give up on 5 1/4. What's the most common HDD used in desktop
> machines?
>

Let's do mine.

[Picture]

https://i.postimg.cc/KYBPvHY7/my-boot-drive.gif

*******

Disktype is here. NOT compiled for Windows, but available in Cygwin.

https://disktype.sourceforge.net/

PS disktype> .\disktype.exe /dev/sda # Cygwin build of disktype

--- /dev/sda
Block device, size 3.639 TiB (4000787030016 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 3.639 TiB (4000787030016 bytes, 7814037168 sectors)
Disk GUID CD4D6752-BAC8-B446-90A7-662721F0DD2D
Partition 1: 100 MiB (104857600 bytes, 204800 sectors from 2048)
Type EFI System (FAT) (GUID 28732AC1-1FF8-D211-BA4B-00A0C93EC93B)
Partition Name "EFI system partition"
Partition GUID BE145A8D-FC87-9B45-AFB1-8959CB4D727A
FAT32 file system (hints score 4 of 5)
Volume size 96 MiB (100663296 bytes, 98304 clusters of 1 KiB)
Partition 2: 16 MiB (16777216 bytes, 32768 sectors from 206848)
Type MS Reserved (GUID 16E3C9E3-5C0B-B84D-817D-F92DF00215AE)
Partition Name "Microsoft reserved partition"
Partition GUID B000A1BB-661C-7541-AF97-88BB60627F66
Partition 3: 118.7 GiB (127481675776 bytes, 248987648 sectors from 239616)
Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)
Partition Name "Basic data partition"
Partition GUID 6A16D60B-3608-4140-891C-792DF2C72ABD
NTFS file system
Volume size 118.7 GiB (127481675264 bytes, 248987647 sectors)
Partition 4: 646 MiB (677380096 bytes, 1323008 sectors from 249227264)
Type Unknown (GUID A4BB94DE-D106-404D-A16A-BFD50179D6AC)
Partition Name ""
Partition GUID B15ABCC3-F0C5-AE4D-838C-751EF868E237
NTFS file system
Volume size 646.0 MiB (677379584 bytes, 1323007 sectors)
Partition 5: 129.4 GiB (138979404288 bytes, 271444149 sectors from 250556416)
Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)
Partition Name "Basic data partition"
Partition GUID BC694DBD-BB6F-124F-B804-F32C6B9E828C
NTFS file system
Volume size 129.4 GiB (138979403776 bytes, 271444148 sectors)
Partition 6: 577 MiB (605028352 bytes, 1181696 sectors from 522002432)
Type Unknown (GUID A4BB94DE-D106-404D-A16A-BFD50179D6AC)
Partition Name ""
Partition GUID CF6B38AF-C016-3F48-A84B-B310CC27C8E8
NTFS file system
Volume size 577.0 MiB (605027840 bytes, 1181695 sectors)
Partition 7: 682.0 GiB (732331769856 bytes, 1430335488 sectors from 523186176)
Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)
Partition Name "Basic data partition"
Partition GUID DA97834F-DF61-974A-B913-9BD526C13C9A
NTFS file system
Volume size 682.0 GiB (732331769344 bytes, 1430335487 sectors)
Partition 8: unused

We will look at GPT partition number 7.

Outside envelope 732,331,769,856 bytes (698406 Megabytes)

Filesystem length 732,331,769,344 (512 bytes short of 698406 Megabytes)

<----------------- 732,331,769,856 ---------------->
+----------------------------------------------------+
| "NTFS" | | 3584 bytes |
| header | 178791935 * 4096 clusters | of slack |
+----------------------------------------------------+

You will notice there is a tendency for the NTFS file system, to not quite
touch the end of the partition.

If the file system, when "formatted" is made too long, it hangs over
the end. Corruption is then possible. You will occasionally run into
both cases. File system way way too short. Or, file system hanging
over the end of the partition envelope.

You can use FSUTIL (on Win10) to try to dump particulars. Let's try that on my example.
It doesn't tell us about the slack at the end, just the working bits as Total Sectors.

PS disktype> fsutil fsinfo ntfsinfo S:
NTFS Volume Serial Number : 0x8a04733a04732879
NTFS Version : 3.1
LFS Version : 2.0
Total Sectors : 1,430,335,487 (682.0 GB)
Total Clusters : 178,791,935 (682.0 GB) <=== see how lucky I am? I calc'ed that without cheating.
Free Clusters : 24,488,803 ( 93.4 GB)
Total Reserved Clusters : 1,024 ( 4.0 MB)
Reserved For Storage Reserve : 0 ( 0.0 KB)
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096 (4 KB)
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 4.75 MB
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x0000000008c6c140
Mft Zone End : 0x0000000008c6d0e0
MFT Zone Size : 15.63 MB
Max Device Trim Extent Count : 512
Max Device Trim Byte Count : 0xffffffff
Max Volume Trim Extent Count : 62
Max Volume Trim Byte Count : 0x40000000
Resource Manager Identifier : A1E10F15-C5B7-11ED-A0B0-2CF05DD9F734

Now, we can use HxD and look at the GPT Table

Can't parse GPT table by sight. 0x400 to 0x780 primary table, 0x80 per entry
Secondary table is about 16K from the end of the disk drive or so. 128*128=16K
128 partition entries of 128 bytes (0x80) each.

0 (0x00) 16 bytes Partition type GUID (mixed endian[12])
16 (0x10) 16 bytes Unique partition GUID (mixed endian)
32 (0x20) 8 bytes First LBA (little endian) \_____ take difference to get length
40 (0x28) 8 bytes Last LBA (inclusive, usually odd) /
48 (0x30) 8 bytes Attribute flags (e.g. bit 60 denotes read-only)
56 (0x38) 72 bytes Partition name (36 UTF-16LE code units)

00000000720 00 30 2F 1F 00 00 00 00 FF 5F 70 74 00 00 00 00 .0/.....ÿ_pt....

74705FFF - 1F2F3000 + 1 = 55413000 or 1,430,335,488

The envelope is one sector bigger than the FS "Total Sectors" of 1,430,335,487 .
This means we can rely on FSUTIL for NTFS details, but not for GPT partition size.
The GPT partition size is displayed in disktype.exe , or can be extracted
with HxD from the physical drive (run HxD as administrator to access the drive).

Fun, eh?

Paul

In alt.comp.os.windows-10, on Mon, 18 Dec 2023 21:24:56 -0600, Char
Jackson <none@none.invalid> wrote:

>On Mon, 18 Dec 2023 20:52:53 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>
>>In alt.comp.os.windows-10, on Mon, 18 Dec 2023 19:17:09 -0600, Char
>>Jackson <none@none.invalid> wrote:
>>
>>>On Mon, 18 Dec 2023 19:33:37 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>>>
>>>>Yes, as someone said, I do find obscure problems. Here is my latest:
>>>>
>>>>I have a dock with a 5 1/4" drive in it
>>>
>>>Is that a 5 1/4" floppy drive? I think the museum called. They want their
>>>vintage exhibit back.
>>
>>I'm not good with numbers. I guess it's not that big. ;-(
>>>
>>>>used for backups, and
>>>>
>>>>Minitool Partition Wizard Free 12.8 shows with 3 partitions
>>>> System Reserved 955MB
>>>> HPWin10OS 82GB
>>>> HPWinData 145GB
>>>> unallocated 1635GB
>>>
>>>Hmm, OK, not a floppy drive, but what other drive comes in a 5 1/4"?
>>
>>Let's give up on 5 1/4. What's the most common HDD used in desktop
>>machines?
>
>They've been 3 1/2" for a very long time now, if you're asking about physical
>size of desktop HDDs. Since physical size is standardized, capacity is more
>often discussed these days. Yours is a 2 TB model? 1635+145+82 = 1862, which is
>exactly what a formatted 2 TB drive would give.

Yes, but that was never the problem. If you look at the list of 4
partition managers in the first post, only one of them points out that
there is a whole bunch of unallocated space in the drive. 85% or so. The
other 3 are misleading. Two or of them make it look the drive if full.
The other one makes it look full in the bottom half of the screen and
hints that it's not in the top half. Why do they do that? Only
Minitools describes it accurately. If Minitools can get it right, why
not the others? I explained it better in the first post,

On Mon, 18 Dec 2023 23:15:40 -0500, micky <NONONOmisc07@fmguy.com> wrote:

>In alt.comp.os.windows-10, on Mon, 18 Dec 2023 21:24:56 -0600, Char
>Jackson <none@none.invalid> wrote:
>
>>On Mon, 18 Dec 2023 20:52:53 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>>
>>>In alt.comp.os.windows-10, on Mon, 18 Dec 2023 19:17:09 -0600, Char
>>>Jackson <none@none.invalid> wrote:
>>>
>>>>On Mon, 18 Dec 2023 19:33:37 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>>>>
>>>>>Yes, as someone said, I do find obscure problems. Here is my latest:
>>>>>
>>>>>I have a dock with a 5 1/4" drive in it
>>>>
>>>>Is that a 5 1/4" floppy drive? I think the museum called. They want their
>>>>vintage exhibit back.
>>>
>>>I'm not good with numbers. I guess it's not that big. ;-(
>>>>
>>>>>used for backups, and
>>>>>
>>>>>Minitool Partition Wizard Free 12.8 shows with 3 partitions
>>>>> System Reserved 955MB
>>>>> HPWin10OS 82GB
>>>>> HPWinData 145GB
>>>>> unallocated 1635GB
>>>>
>>>>Hmm, OK, not a floppy drive, but what other drive comes in a 5 1/4"?
>>>
>>>Let's give up on 5 1/4. What's the most common HDD used in desktop
>>>machines?
>>
>>They've been 3 1/2" for a very long time now, if you're asking about physical
>>size of desktop HDDs. Since physical size is standardized, capacity is more
>>often discussed these days. Yours is a 2 TB model? 1635+145+82 = 1862, which is
>>exactly what a formatted 2 TB drive would give.
>
>Yes, but that was never the problem.

I know. I was just trying to help establish what you're working with.

>If you look at the list of 4
>partition managers in the first post, only one of them points out that
>there is a whole bunch of unallocated space in the drive. 85% or so. The
>other 3 are misleading. Two or of them make it look the drive if full.
>The other one makes it look full in the bottom half of the screen and
>hints that it's not in the top half. Why do they do that? Only
>Minitools describes it accurately. If Minitools can get it right, why
>not the others? I explained it better in the first post,

I think Paul is helping to answer those questions. I've never seen such extreme
disagreements among partition managers before.

On 12/18/2023 11:30 PM, Char Jackson wrote:

>
> I think Paul is helping to answer those questions. I've never seen such extreme
> disagreements among partition managers before.
>

I don't have any theories to offer either.

I've had malformed partitions before. Some situations
do not warn (you can receive corruption later, if the
conditions are right for it). Some situations, I could not
fix, so I had to copy data off and make a new partition.

Some of it, involved some partition tool that didn't
put partitions on proper boundaries while doing "Move/Resize".

And later, other (brittle) tools would declare
all sorts of calamities.

Paul

On Tue, 19 Dec 2023 01:52:20 -0500, Paul <nospam@needed.invalid> wrote:

>On 12/18/2023 11:30 PM, Char Jackson wrote:
>
>>
>> I think Paul is helping to answer those questions. I've never seen such extreme
>> disagreements among partition managers before.
>>
>
>I don't have any theories to offer either.
>
>I've had malformed partitions before. Some situations
>do not warn (you can receive corruption later, if the
>conditions are right for it). Some situations, I could not
>fix, so I had to copy data off and make a new partition.
>
>Some of it, involved some partition tool that didn't
>put partitions on proper boundaries while doing "Move/Resize".
>
>And later, other (brittle) tools would declare
>all sorts of calamities.

All I can think of is that the dock might be doing something funky. I don't know
anything about it, including what limitations it might have. If nothing better
comes along, I'd pull the drive out of the dock and temporarily connect it to an
internal SATA port. If all of the partition managers suddenly agree on what
they're seeing, then we might learn something.

I was assuming that the drive itself is a 2TB model, but I guess I don't know
that for sure, either. Maybe it's actually bigger, but the dock is old enough
that it doesn't know how to report on anything bigger than 2TB. I'm back to
temporarily bypassing the dock to see if anything changes.

On 12/19/2023 5:55 AM, Char Jackson wrote:
> On Tue, 19 Dec 2023 01:52:20 -0500, Paul <nospam@needed.invalid> wrote:
>
>> On 12/18/2023 11:30 PM, Char Jackson wrote:
>>
>>>
>>> I think Paul is helping to answer those questions. I've never seen such extreme
>>> disagreements among partition managers before.
>>>
>>
>> I don't have any theories to offer either.
>>
>> I've had malformed partitions before. Some situations
>> do not warn (you can receive corruption later, if the
>> conditions are right for it). Some situations, I could not
>> fix, so I had to copy data off and make a new partition.
>>
>> Some of it, involved some partition tool that didn't
>> put partitions on proper boundaries while doing "Move/Resize".
>>
>> And later, other (brittle) tools would declare
>> all sorts of calamities.
>
> All I can think of is that the dock might be doing something funky. I don't know
> anything about it, including what limitations it might have. If nothing better
> comes along, I'd pull the drive out of the dock and temporarily connect it to an
> internal SATA port. If all of the partition managers suddenly agree on what
> they're seeing, then we might learn something.
>
> I was assuming that the drive itself is a 2TB model, but I guess I don't know
> that for sure, either. Maybe it's actually bigger, but the dock is old enough
> that it doesn't know how to report on anything bigger than 2TB. I'm back to
> temporarily bypassing the dock to see if anything changes.
>

That sounds like a good plan.

That gets rid of one variable.

Paul

In alt.comp.os.windows-10, on Tue, 19 Dec 2023 04:55:48 -0600, Char
Jackson <none@none.invalid> wrote:

>On Tue, 19 Dec 2023 01:52:20 -0500, Paul <nospam@needed.invalid> wrote:
>
>>On 12/18/2023 11:30 PM, Char Jackson wrote:
>>
>>>
>>> I think Paul is helping to answer those questions. I've never seen such extreme
>>> disagreements among partition managers before.
>>>
>>
>>I don't have any theories to offer either.
>>
>>I've had malformed partitions before. Some situations
>>do not warn (you can receive corruption later, if the
>>conditions are right for it). Some situations, I could not
>>fix, so I had to copy data off and make a new partition.
>>
>>Some of it, involved some partition tool that didn't
>>put partitions on proper boundaries while doing "Move/Resize".
>>
>>And later, other (brittle) tools would declare
>>all sorts of calamities.
>
>All I can think of is that the dock might be doing something funky. I don't know
>anything about it, including what limitations it might have. If nothing better
>comes along, I'd pull the drive out of the dock and temporarily connect it to an
>internal SATA port.

The small desktop I'm using now doesn't have an empty one. I'm still
hoping to fix up an old tower that I have but that will have to wait
until February at the earliest.

>If all of the partition managers suddenly agree on what
>they're seeing, then we might learn something.
>
>I was assuming that the drive itself is a 2TB model, but I guess I don't know

Yes, that's right. Western Digital blue label, but of course it should
still get it right. It's an Xiaobi dock.

>that for sure, either. Maybe it's actually bigger, but the dock is old enough

I actually have an older dock, with a famous name in docks that I can't
remember now, but I'm running out of time to pack etc. before a trip to
Florida and Guatemala, and I don't even have time to try the other dock.
I bought the second one because it said** it would spin down the drives
when they weren't in use, but then they said it doesn't do that.

>that it doesn't know how to report on anything bigger than 2TB. I'm back to
>temporarily bypassing the dock to see if anything changes.

**Off topic but I also once bought a modem that it said would let me
take phone calls while I was using dial-up, and after I got it and
called up, the guy on the phone said, "Yes, it doesn't do that."

I also once paid for software that would do backups and instead it
destroyed, made disappear, 2gb out of the 7gb I had then. I had used it
right out of the box instead of checking the webpage for updates. I
guess the updated version wouldn't have done that.

In alt.comp.os.windows-10, on Tue, 19 Dec 2023 06:21:09 -0500, Paul
<nospam@needed.invalid> wrote:

>On 12/19/2023 5:55 AM, Char Jackson wrote:
>> On Tue, 19 Dec 2023 01:52:20 -0500, Paul <nospam@needed.invalid> wrote:
>>
>>> On 12/18/2023 11:30 PM, Char Jackson wrote:
>>>
>>>>
>>>> I think Paul is helping to answer those questions. I've never seen such extreme
>>>> disagreements among partition managers before.
>>>>
>>>
>>> I don't have any theories to offer either.
>>>
>>> I've had malformed partitions before. Some situations
>>> do not warn (you can receive corruption later, if the
>>> conditions are right for it). Some situations, I could not
>>> fix, so I had to copy data off and make a new partition.
>>>
>>> Some of it, involved some partition tool that didn't
>>> put partitions on proper boundaries while doing "Move/Resize".
>>>
>>> And later, other (brittle) tools would declare
>>> all sorts of calamities.
>>
>> All I can think of is that the dock might be doing something funky. I don't know
>> anything about it, including what limitations it might have. If nothing better
>> comes along, I'd pull the drive out of the dock and temporarily connect it to an
>> internal SATA port. If all of the partition managers suddenly agree on what
>> they're seeing, then we might learn something.
>>
>> I was assuming that the drive itself is a 2TB model, but I guess I don't know
>> that for sure, either. Maybe it's actually bigger, but the dock is old enough
>> that it doesn't know how to report on anything bigger than 2TB. I'm back to
>> temporarily bypassing the dock to see if anything changes.
>>
>
>That sounds like a good plan.
>
>That gets rid of one variable.
>
> Paul

I put in another HDD, of unknown physical dimensions, 1.5T, WD green,
and this one had 10gb unallocated in the middle of two used partitions
ane more unallocated space at the end.
And Macrium Reflect free showed both of them in the bar graph (which
is all I see)
AND MS disk management** did too.
And AOMEI showed them in both the bar graph and the table.

Maybe the prior HDD was unusual in some way, having all its unallocated
space at the end? No, that would be typical. ???

** MS DM marked the unallocated space with a black bar at the top, like
the legend says. I guess maybe green for free space would only be used
if the entire allocated partition was empty. It would be of value to
have such a partition highlighted.

On 19/12/2023 00:33, micky wrote:
> Minitool Partition Wizard Free 12.8 shows with 3 partitions
> System Reserved 955MB
> HPWin10OS 82GB
> HPWinData 145GB
> unallocated 1635GB
>
> But Macrium Reflect v8.0.7783 shows
> System Reserved 955MB
> HPWin10OS 82GB
> HPWinData 1.74TB
> no mention of unallocated space

Could it be that it's a 1.74TB partition but the file system in it is
only 145GB?

Perhaps an backed up image of a 145GB partition was restored into the
1.74TB partition?

--
Brian Gregory (in England).

On 12/19/2023 3:24 PM, micky wrote:
> In alt.comp.os.windows-10, on Tue, 19 Dec 2023 06:21:09 -0500, Paul
> <nospam@needed.invalid> wrote:
>
>> On 12/19/2023 5:55 AM, Char Jackson wrote:
>>> On Tue, 19 Dec 2023 01:52:20 -0500, Paul <nospam@needed.invalid> wrote:
>>>
>>>> On 12/18/2023 11:30 PM, Char Jackson wrote:
>>>>
>>>>>
>>>>> I think Paul is helping to answer those questions. I've never seen such extreme
>>>>> disagreements among partition managers before.
>>>>>
>>>>
>>>> I don't have any theories to offer either.
>>>>
>>>> I've had malformed partitions before. Some situations
>>>> do not warn (you can receive corruption later, if the
>>>> conditions are right for it). Some situations, I could not
>>>> fix, so I had to copy data off and make a new partition.
>>>>
>>>> Some of it, involved some partition tool that didn't
>>>> put partitions on proper boundaries while doing "Move/Resize".
>>>>
>>>> And later, other (brittle) tools would declare
>>>> all sorts of calamities.
>>>
>>> All I can think of is that the dock might be doing something funky. I don't know
>>> anything about it, including what limitations it might have. If nothing better
>>> comes along, I'd pull the drive out of the dock and temporarily connect it to an
>>> internal SATA port. If all of the partition managers suddenly agree on what
>>> they're seeing, then we might learn something.
>>>
>>> I was assuming that the drive itself is a 2TB model, but I guess I don't know
>>> that for sure, either. Maybe it's actually bigger, but the dock is old enough
>>> that it doesn't know how to report on anything bigger than 2TB. I'm back to
>>> temporarily bypassing the dock to see if anything changes.
>>>
>>
>> That sounds like a good plan.
>>
>> That gets rid of one variable.
>>
>> Paul
>
> I put in another HDD, of unknown physical dimensions, 1.5T, WD green,
> and this one had 10gb unallocated in the middle of two used partitions
> ane more unallocated space at the end.
> And Macrium Reflect free showed both of them in the bar graph (which
> is all I see)
> AND MS disk management** did too.
> And AOMEI showed them in both the bar graph and the table.
>
> Maybe the prior HDD was unusual in some way, having all its unallocated
> space at the end? No, that would be typical. ???
>
>
> ** MS DM marked the unallocated space with a black bar at the top, like
> the legend says. I guess maybe green for free space would only be used
> if the entire allocated partition was empty. It would be of value to
> have such a partition highlighted.
>

Sometimes GPT partitions end up out of spatial order.

+------+-------------------------+--------- - - -
| #1 | #6 | #2
+------+-------------------------+--------- - - -

This does not hurt anything, except in cases (as mentioned previously),
where one partition overlaps another partition. I've never seen any
response from the OS regarding this situation being present. Like a
warning that corruption is possible, with the current partition table metadata.

While I can move legacy partitions around (somewhat) with PTEDIT32.exe (free),
I don't have anything to do it for GPT. Linux gparted, will automatically mess
around with partition numbers. Again, might cause an issue, might not. Some
of Linux is based on UUIDs, so the partition numbers don't matter. Except for
one of the boot phases, which is on a numbered partition, and you can break that.
This is one reason, on a mixed Windows/Linux multiboot, you "try to stay away
from the partitions on the left", as the further left you go, the more danger
there is. Sometimes a data partition ends up over there (grrr...).

+------+-------------------------+--------- - - -
| #1 | #2 | #3 gparted may do this, after a partition operation
+------+-------------------------+--------- - - -

You might need forensic tools to satisfy your curiosity. Boot a Linux
and use "disktype" there, if you cannot be bothered to get the Cygwin one.
At one time, the Cygwin was nice, in that you copied the EXE and two DLLs
and a Cygwin executable would be portable (you can throw the rest of Cygwin away).
But the current Cygwin for some reason, has around a dozen DLLs, and that's
more stuff to copy and put next to the EXE.

Disktype gives you a "supply of numbers" to work with. You have to
do the arithmetic to determine whether something is broken or not.
If I had a trustworthy utility that would do the arithmetic for you,
I'd tell you. I don't know if Macrium gets upset at bad metadata on
a drive or not. Macrium certainly does some amount of checking, before
it agrees to do a backup, and that's so the backup is assumed to be
a "good thing that is re-usable". Backing up a corrupt structure, does
no one any good. Better to fix a structure, and then back it up.

Paul

On Tue, 19 Dec 2023 11:05:40 -0500, micky <NONONOmisc07@fmguy.com> wrote:

>In alt.comp.os.windows-10, on Tue, 19 Dec 2023 04:55:48 -0600, Char
>Jackson <none@none.invalid> wrote:
>
>>All I can think of is that the dock might be doing something funky. I don't know
>>anything about it, including what limitations it might have. If nothing better
>>comes along, I'd pull the drive out of the dock and temporarily connect it to an
>>internal SATA port.
>
>The small desktop I'm using now doesn't have an empty one. I'm still
>hoping to fix up an old tower that I have but that will have to wait
>until February at the earliest.

I know you're packing for a trip, but I'll toss this out anyway. I'd like to say
that technically you don't need an empty SATA port to do this experiment. You
just a need a SATA port that isn't being used for your boot drive. You can
temporarily unplug a CD/DVD drive or a data drive so that you can do this
experiment.

In alt.comp.os.windows-10, on Tue, 19 Dec 2023 20:44:32 -0600, Char
Jackson <none@none.invalid> wrote:

>On Tue, 19 Dec 2023 11:05:40 -0500, micky <NONONOmisc07@fmguy.com> wrote:
>
>>In alt.comp.os.windows-10, on Tue, 19 Dec 2023 04:55:48 -0600, Char
>>Jackson <none@none.invalid> wrote:
>>
>>>All I can think of is that the dock might be doing something funky. I don't know
>>>anything about it, including what limitations it might have. If nothing better
>>>comes along, I'd pull the drive out of the dock and temporarily connect it to an
>>>internal SATA port.
>>
>>The small desktop I'm using now doesn't have an empty one. I'm still
>>hoping to fix up an old tower that I have but that will have to wait
>>until February at the earliest.
>
>I know you're packing for a trip, but I'll toss this out anyway. I'd like to say
>that technically you don't need an empty SATA port to do this experiment. You
>just a need a SATA port that isn't being used for your boot drive. You can
>temporarily unplug a CD/DVD drive or a data drive so that you can do this
>experiment.

I appreciate being told that. Let me read it again and see how close I
came to knowing this.... (reading it a second time) ..... ..... .....
I was between 1/3 and 1/2 of the way to knowing it! All I have is a
laptop and what's the name of the small format desktop, and it has the
laptop sitting on it, and there is no other place to put it. I think
it will have to wait until Feburary, when I intend to clean the whole
desk and build a spare desktop. I had a spare once but the main or the
spare failed after only 2 or 3 months, and I never got much use out of
the spare (like installing Linux in one partition, etc.)