Let's try reading these data:
Device Boot Start End Blocks Id System
/dev/sdb1 * 2048 8386559 4192256 b W95 FAT32
/dev/sdb2 8386560 488392703 240003072 f W95 Ext'd (LBA)
First partition (primary) STARTS on 2048 and ENDS on 8386559 <- this partition does NOT respect cylinder boundary BUT respects head one.
Of course it contains 8386559+1-2048=8384512 sectors (or 512 bytes blocks).
Second partition (extended) STARTS on 8386560 (i.e. END of previous +1, OK) and ENDS on 488392703 <- this partition does NOT respect cylinder boundary BUT respects head one.
Of course it contains 488392703+1-8386560=480006144 sectors (or 512 bytes blocks).
Since the WHOLE disk is 488395055 sectors there is an unallocated space of 488395055 - 488392703 = 2352 sectors.
255 heads, 63 sectors/track, 30401 cylinders, total 488395055 sectors
488395055-488392704=2351 sectors unallocated.
There must be an error in the above 48839505
5 as 30401*255*63=48839206
Let's see the contents of the Extended partition (they are what we highly specialized technicians call "a complete mess, a monkey throwing dices would have come out with far more sensible numbers"
) they simply make NO sense:
/dev/sdb3 20980953 225793574 102406311 b W95 FAT32
/dev/sdb5 8388608 10502143 1056768 b W95 FAT32
/dev/sdb6 225793638 488392064 131299213+ b W95 FAT32
The missing /dev/sd4 is corresponding to an empty EMBR and to the space that Disk management sees as 102.66 Gb.
The first volume inside extended should be one head (63 sectors) after the beginning of the extended, in this case 8386560+63=8386623, BUT you have instead one volume starting at a 2048 offset 8386560+2048=8388608 (this should be /dev/sdb3 and NOT /dev/sdb5).....
IF that partition starts at 8388608 and ends at 10502143 it is 10502143+1-8388608=2,113,536 sectors *512=1,082,130,432 which sounds exactly the size of the "Swap" partition as seen in the disk management.
Since after it we have the "hole" created by the missing /dev/sd4 there is no way to carry n the analysis sequentially.
The "next" partition (the one before last) is /dev/sdb3 which starts at 20980953 and ends at 225793574, 225793574+1-20980953=204,812,622*512=104,864,062,464 which sounds a lot like the "Programs" one.
Last partition is dev/sdb6 that starts at 225793638 and ends at 488392064 (it should start at 225793574+63 but seemingly starts at 225793574+64), 488392064+1-225793638=262,598,427*512=134,450,394,624 which sounds a lot like the "FILES" partition.
First issue is that you used different tools (and Operating Systems ) to fiddle with that partitioning.
NO XP will ever create a partition starting at 2048 (Vista
and later may) and any XP will also respect cylinder boundary for End of partition.
Gparted can use any of the above (and it is particularly easy to make confusion as it's interface is FAR from intuitive when it comes to "details" like this one).
The real issue here is that you are risking GREATLY
, if you ever use XP disk manager to do a trifling thing such as changing the active status of the primary, to loose volumes in the Extended, see:http://reboot.pro/to...itioning-issue/
How exactly you managed to "cross-link" the EMBR chain is a mistery, I never saw that happening with "automated" tools like gparted.
It is possible that the obsolete version of Gparted you used "GParted v0.13" right now we are at 0.16 (BUT DO NOT EVEN THINK of using it or 0.15):http://gparted.sourc...et/download.php
as there are NEW, SERIOUS issues with them.
So, be nice and get 0.14.1-6 instead:http://sourceforge.n...table/0.14.1-6/
There are no issues in solving that mess but you need to confirm that you are familiar with using a hex editor, the intended procedure is:
- correct the EMBR chain WITHOUT moving/resizing anything (by manually hexediting entries in the various EMBR's)
- once the above is done (and verified to be done correctly) use 0.14.1-6 to adjust size and position of the Extended partition and all volumes inside it (this time respecting partition cylinder boundaries)
Though there should be NO issues whatsoever in keeping the primary parittion "as is" , to have an entirely "kosher" partitioning you will also need a PE of some kind (or an alternate XP install or anyway *some* way to edit the Registry "offline") because if we move/resize the primary the already installed Windows XP won't likely boot due to the invalid offset in \DosDevices\
Let me know if you want to proceed and I'll give you instructions.