Haiku's partition map representation looks weird.
|Reported by:||bga||Owned by:||bonefish|
|Has a Patch:||no||Platform:||All|
This is more obvious when looking at DriveSetup but I think the problem is in our disk manager. For example, I have this 500 Gb disk it has one single primary partition created (465.8 Gb of usable size). But due to what is probably some kind of block alignment, there is a bit of free space before the partition (around 5 kb) and this is reported as a different partition in Haiku. So I have:
The 0_0 one is the 5 Kb partition. Although it is there, it is not reported by any other OS (not Linux nor Windows) that I have in the same machine.
With DriveSetup it even looks a bit weirder as it markes the partition exactly like it would mark a extended/logical partition so the /0 partition (the real 465.8 Gb one) looks like it is a logical partition and it is not.
Is this intended; This can get things confusing I guess. What if when DriveSetup can create partitions people try to remove that 0_0 partition?